Preview only show first 10 pages with watermark. For full document please download

1. Technical Requirements 1.1. Introduction 1.1.1

   EMBED


Share

Transcript

1. TECHNICAL REQUIREMENTS 1.1. INTRODUCTION 1.1.1. Pakistan Telecommunication Company Limited (PTCL) is Pakistan’s largest converged services carrier providing all telecommunications services from basic voice telephony to data, internet, video-conferencing and carrier services to consumers and businesses all over the country. 1.1.2. PTCL being the leading integrated information & telecom service provider has transformed its customers experience from narrowband to broadband with proven fixed/wireless technologies and multimedia applications. 1.1.3. PTCL fixed broadband network comprises of multi-vendor and multi technology environment. Access and core network components comprises of DSLAM, ONU/MSAG, BRAS, AAA, policy server, routers etc. 1.1.4. CDMA2000 1x, EVDO Rev.A/B technology is used to provide wireless broadband services throughout the country. PTCL is expanding its Wireless broadband network and services by the introduction of new access technologies including WiFi. 1.1.5. PTCL intend to build Wireless WiFi hot spot infrastructure throughout the country. 1.1.6. The objective of this specification is to define and fix standards for equipment/services required for Wireless WiFi hotspot solution. 1.2. GENERAL 1.2.1. The wireless hotspot solution is to be deployed at different locations throughout the country for consumer and enterprise segments including indoor and outdoor sites. 1.2.2. Consumer segment shall include the public places with high number of visitors like shopping malls, super markets, diners, and stations etc. and enterprise segment shall constitute high-rise buildings, offices and residential flats etc. 1.2.3. The vendor shall be responsible to design, supply, install, test, commission and integrate the offered solution to PTCL existing network. The bidder shall offer complete WiFi hotspot solution, comprising of at least the following components: i). Indoor Wi-Fi Access Points ii). Outdoor Wi-Fi Access Points iii). Wireless LAN Controller (WLC) iv). LAN Switches v). Network Management System (NMS) vi). Network planning and Performance Monitoring Systems/tools 1.2.4. The vendor shall provide the solution dimensioning on the basis of survey to be carried out by him. 1.2.5. The vendor shall be responsible for complete Integration of Wireless AP’s/WLC’s with existing PTCL Network. 1.2.6. The offered solution shall be scalable and modular to accommodate future expansion. 1.2.7. The vendor shall offer high availability and redundancy features for the offered solution with respect to hardware & software. A single component failure should not affect the overall system performance. 1.2.8. The offered solution shall be scalable in design, permitting incremental growth in capacity. The ultimate capacities of the solution components shall be stated. 1.2.9. The offered solution shall be upgradeable to support new features. 1.2.10. The offered solution shall have security mechanisms to protect the network resources from attacks; details of the same shall be provided. 1.2.11. The offered solution shall be “3G offload solution ready”. Any additional components required shall be stated exclusively as optional items in the offered BoQ. 1.2.12. The offered solution shall be complied with IEEE 802.11a, 802.11b, 802.11g and 802.11n. 1.3. SOLUTION FEATURES 1.3.1. The proposed solution shall have the following features: i). Carrier grade solution ii). Modular and scalable solution iii). No single point of failure iv). 3G offload solution support 1.4. INDOOR WIFI AP Following are the technical requirements: 1.4.1. Wi-Fi certified: 802.11a/b/g/n 1.4.2. Dual band support 1.4.3. MIMO support 1.4.4. QoS features support: i). Support voice, video and data using the same SSID ii). Prioritize voice over data for both tagged and untagged traffic iii). 802.11e, WMM 1.4.5. Security feature support: 802.1X, WPA, WPA2, 802.11i and AES 1.4.6. RF Management i). Automatic transmit-power and channel-management control ii). Spectrum analysis to identify sources of RF interference 1.4.7. Interfaces i). 10/100/1000 Base T Ethernet 1.4.8. Environmental Conditions i). Temperature: 0º C to 50º C ii). Relative humidity: 10% to 95% non-condensing 1.4.9. Mounting: Preferably standard wall mount 1.4.10. Plug and play operation 1.4.11. The access point shall have GE interface with POE support. 1.5. 1.5.1. 1.5.2. 1.5.3. 1.5.4. 1.5.5. 1.5.6. 1.5.7. 1.5.8. OUTDOOR WIFI AP Following are the technical requirements: Wi-Fi certified: 802.11a/b/g/n Dual band support MIMO support QoS features support: iv). Support voice, video and data using the same SSID v). Prioritize voice over data for both tagged and untagged traffic vi). 802.11e, WMM Security feature support: 802.1X, WPA, WPA2, 802.11i and AES RF Management i). Automatic transmit-power and channel-management control ii). Spectrum analysis to identify sources of RF interference Interfaces i). Network: 1 x 10/100/1000BASE-T Ethernet (RJ45) Environmental Conditions iii). Temperature: -30º C to 70º C iv). Relative humidity: 5% to 95% non-condensing Page 2 of 5 1.5.9. The access point shall have GE interface with POE support. 1.6. WIRELESS LAN CONTROLLER (WLC) 1.6.1. Following details shall be stated: i). Indoor/outdoor APs supported per controller ii). Remote/ mesh APs supported per controller 1.6.2. Following Interfaces shall be available: i). Gigabit Ethernet ports ii). 10 Gigabit Ethernet ports 1.6.3. High availability: i). Redundant power ii). Redundant fans 1.6.4. The offered WLC shall be managed through SNMP, Web, CLI using SSH, Telnet and console port. 1.6.5. Preferably clustering support 1.7. 1.7.1. 1.7.2. 1.7.3. 1.7.4. 1.7.5. 1.7.6. 1.7.7. 1.7.8. LAN SWITCH Modular architecture Redundant power and hot swappable components PoE support, low power consumption Voice and video support NTP support QoS features Security features including access control GE and 10 GE interface support 1.8. NETWORK MANAGEMENT SYSTEM 1.8.1. The bidder shall offer comprehensive NMS with Fault, Configuration, Accounting, Performance and Security (FCAPS) functionalities that can manage the offered solution. 1.8.2. The offered Network Management System (NMS) shall be based on North-Bound architecture and interface with the PTCL Central Management NOC/Integrated NMS. It shall support the standard interfacing protocols, like, CORBA, SNMP, etc. 1.9. NETWORK PLANNING AND PERFORMANCE MONITORING SYSTEMS/TOOLS 1.9.1. The bidder shall offer network planning, performance monitoring and reporting tool. 1.9.2. The network planning tool shall provide: i). Detailed network and capacity planning etc. ii). Indoor and outdoor network plan iii). Configuration and verification iv). RF planning 1.9.3. Following features shall be available in the performance monitoring and reporting system: i). Web interface ii). Device discovery iii). Real-time monitoring iv). Root cause analysis and event correlation v). Site planning for precise deployment Page 3 of 5 vi). Automated alerts and reports vii). History and archive feature viii). Monitoring and reporting by user, radio, AP, WLC and SSID ix). Location aware (search by location, roaming history and geo fencing etc.) 1.9.4. The offered solution shall have interference detection and mitigation feature. 1.10. CHARGING METHODOLOGY, ACCESS CONTROL AND BILLING SYSTEM 1.10.1. Following charging options shall be available in the offered solution: i). Existing Broadband and EVO users on discount rate using existing postpaid account with regular charging. ii). All PSTN customers may avail this service on standard tariff using their postpaid PSTN accounts (Account IDs). iii). All V-Fone customers may avail this service subject to their V-Fone accounts debited as they opt in for relevant package. iv). Voucher based charging system and kiosk’s on all hotspots and regular PTCL customer touch points; wherefrom any user can buy voucher of available denomination and avail relevant offer. v). Billing via credit card may also be an option. A customer may purchase a voucher through his/ her credit card available as an option in the Captive Portal. 1.10.2. Portal/web based authentication is proposed as access control method. A typical portal system consists of four basic components including authentication client (portal client), portal server, broadband remote access server (BRAS) and authentication/authorization/accounting (AAA) server. i). Portal client: Client system that triggers authentication requests on a portal network. It can be a browser using the Hypertext Transfer Protocol (HTTP). ii). Portal server: Server system that listens to authentication requests from portal clients and exchanges client identity information with the BRAS. It provides free portal services and a web-based authentication interface. iii). BRAS: Broadband remote access server, used to redirect HTTP requests to the portal server, and cooperate with the portal server and AAA server to implement authentication/authorization/accounting for users. iv). AAA server: Authentication/authorization/accounting server, used to cooperate with the BRAS to perform authentication/authorization/accounting for users. 1.10.3. Following is the call flow: i). When an unauthenticated user enters a website address in the address bar of the IE to access the Internet, an HTTP request is created and sent to the BRAS, which redirects the HTTP request to the web authentication homepage of the portal server. ii). On the authentication homepage/authentication dialog box, the user enters and submits the authentication information, which the portal server then transfers to the BRAS. iii). Upon receipt of the authentication information, the BRAS communicates with the AAA server for authentication and accounting. iv). After successful authentication, the BRAS opens a path for the user to access the Internet. 1.10.4. The bidder shall provide details of offered billing system, its implementation and integration with PTCL billing and AAA systems. Page 4 of 5 1.11. MISCELLANEOUS REQUIREMENTS 1.11.1. The bidder/vendor shall describe the architecture of proposed solution, its elements and integrations. 1.11.2. The offered solution shall have support structure for offered solution including team size, general response times etc. 1.11.3. The bidder shall state that if the solution requires any other component to operate. e.g. storage, platform, third-party licenses etc. or is it a complete standalone offering. 1.11.4. The bidder response shall include a description of how the architecture scales from the initial deployment to support the entire IT infrastructure. 1.11.5. The bidder response shall include the upper sizing limits of proposed solution. 1.11.6. The bidder shall provide the solution upgrade roadmap and general strategy and timeframes for including / supporting new versions of monitored elements. 1.11.7. The bidder shall describe if the proposed solution uses PTCL provided storage or internal storage. Provide calculations for the required storage amount and performance required. Describe how the data events are stored and the options for configuring storage. 1.11.8. The bidder shall also calculate and provide the network overhead for the proposed solution. 1.11.9. The bidder shall provide list of built-in reports with samples. 1.11.10. The bidder shall describe the steps and time required to replace a failed component of the provided solution. 1.11.11. The bidder shall describe the steps / additions required for high availability support for the provided solution. 1.11.12. The bidder shall describe the licensing model for all components of the provided solution. 1.11.13. The bidder shall provide the proposed deployment / implementation diagram also specifying the data flows. 1.11.14. The bidder shall specify the infrastructure required from PTCL such as network, rack-space, power, cooling etc. 1.11.15. The bidder shall clearly state any exclusion from scope / requirements. 1.11.16. The bidder should assess and specify the requirements including hardware, software, licenses and network components, etc. of the offered solution to meet the specified functions. All functional requirements are to be translated and made part of offered BOQ. All critical requirements are necessary to meet business objectives of PTCL and hence any proposed solution must comply with these requirements. 1.11.17. The offered solution shall support seamless mobility in accordance with relevant standards including IEEE 802.11u. 1.11.18. IP67 compliance. Page 5 of 5