Request For Proposal
Wireless Broadband System
For
[The User]
Technical Requirements
Date: Aug 12, 2014
Request for Proposal
[Propsal No.]
Table of Contents
1.
2.
3.
4.
5.
6.
7.
Introduction ............................................................................................ 4
1.1 Scope ................................................................................................ 4
Service Background ..............................................................................4
2.1 Service Overview ............................................................................. 4
Service Configuration ...........................................................................4
3.1 Outdoor Coverage ......................................................................... 5
3.2 Indoor Coverage ............................................................................. 6
3.2.1
Wireless Backhaul with CPE .............................................. 6
3.2.2
Wired Backhaul with Indoor AP (Optional) .................... 6
3.3 Data Center...................................................................................... 6
Ethernet Switch....................................................................................... 7
4.1 Network Connectivity ..................................................................... 7
4.1.1
Fast Ethernet Interface ...................................................... 7
4.2 Operation Support ........................................................................... 7
4.2.1
802.1Q (VLAN) .................................................................... 7
4.2.2
802.1p (QoS) and Traffic Prioritization ............................. 7
Access Point (AP) .................................................................................. 7
5.1 Network Connectivity Requirements ............................................ 7
5.1.1
WAN Interface .................................................................... 7
5.2 Wireless Network Features .............................................................. 8
5.2.1
Operation Mode Support ................................................. 8
5.2.2
Radio Frequency Setting .................................................. 8
5.2.3
Multiple SSID Support ......................................................... 8
5.2.4
Wireless Security ................................................................. 9
5.2.5
Encryption support ............................................................. 9
5.3 Authentication Support .................................................................. 9
5.3.1
UAM (Universal Access Method) ..................................... 9
5.3.2
802.1x Mutual Authentication .......................................... 9
5.3.3
RADIUS Support .................................................................. 9
5.3.4
EAP Support ...................................................................... 10
5.4 System Operation Features .......................................................... 10
5.4.1
Per SSID Operation ........................................................... 10
5.4.2
VLAN Configuration ......................................................... 10
5.4.3
Bridge Mode ..................................................................... 10
5.4.4
Quality of Service (QoS) Support................................... 11
802.11e WMM .................................................................................. 11
Wireless Bridge ..................................................................................... 11
6.1 Network Connectivity Requirements .......................................... 12
6.1.1
Network Interface ............................................................ 12
6.2 Wireless Network Features ............................................................ 12
Wireless CPE ......................................................................................... 12
7.1 Network Connectivity Requirements .......................................... 12
7.1.1
WAN Interface .................................................................. 12
7.1.2
LAN Interface.................................................................... 13
Request for Proposal
[Propsal No.]
7.2 Security Features ............................................................................ 13
7.3 Networking Features ..................................................................... 13
7.4 Management Features ................................................................. 13
8. Service Control System .......................................................................14
8.1 System Capacity ............................................................................ 14
8.2 Functions and Features ................................................................. 14
8.2.1
Bandwidth Controller ...................................................... 14
8.2.2
Access Controller ............................................................. 14
8.2.3
Backbone Router ............................................................. 14
8.2.4
Firewall ............................................................................... 15
8.2.5
VPN Server ......................................................................... 15
8.2.6
DHCP and Proxy Servers ................................................. 15
8.2.7
Tools.................................................................................... 15
9. Management & System Support Tools ............................................... 15
9.1 Remote Monitoring ........................................................................ 16
9.2 Administration................................................................................. 16
9.3 Management Security Configurations ....................................... 16
9.4 Remote Firemare Upgrade .......................................................... 16
10. Network Management System .......................................................... 16
10.1 Network Capacity ......................................................................... 17
10.2 Functions and Features ................................................................. 17
10.2.1 Fault Management.......................................................... 17
10.2.2 Configuration Management ......................................... 17
10.2.3 Administration Management......................................... 17
10.2.4 Performance Management........................................... 17
10.2.5 Security Management .................................................... 18
10.2.6 RF Management .............................................................. 18
10.2.7 Bridge-Link Management ............................................... 18
10.2.8 Network Map Management .......................................... 18
10.2.9 GUI Languages Support.................................................. 18
11. Hardware Specifications .....................................................................18
11.1 Mechanical Requirements (For All Equipment) ........................ 18
11.2 Reset Button (For AP and Switch) ................................................ 19
11.3 LED (For AP)..................................................................................... 19
11.4 LED (For Switch) .............................................................................. 19
11.5 Operating Environments ............................................................... 19
11.6 Non-operating Environments ....................................................... 19
11.7 Power Environments (For Switch) ................................................ 19
11.8 Power Requirements (For AP) ...................................................... 20
11.9 Power Requirments (For Wireless Bridge) ................................... 20
11.10
Power and Reliablity Requirments (For SCS) ....................... 20
11.11
External Antenna (For AP) ...................................................... 20
11.12
Mounting Support ................................................................... 21
11.13
Size and Weight (For AP) ........................................................ 21
11.14
EMC Requirement ................................................................... 21
Request for Proposal
[Propsal No.]
1. Introduction
1.1 Scope
This document is a technical specification for the requirements of the Wireless
Broadband System comprises of Access Point (AP), Wireless Bridge, Wireless CPE,
Service Controller System (SCS), Ethernet Switch and other accessories for deploying
wireless broadband network service in [The User].
The requirements for the Wireless Broadband System cover the following areas:

Network Connectivity

Wireless Network Features

Authentication Support

System Operation Features

Service Control Features

Management & System Support Tools

Network Management System

Hardware Specifications

Operating Environmental Requirements
2. Service Background
2.1 Service Overview
[The Buyer] is going to deploy a wireless broadband service in [the User]. Users will use
the 802.11b/g/n client devices to connect to the Wireless Broadband System located
at [The Location] and then connect to the Internet through [The Buyer] network
infrastructure.
3. Service Configuration
Typical configuration for Wireless Broadband Service is shown in the diagram below.
The network is divided into 3 parts:

Outdoor coverage

Indoor coverage

Data center
Request for Proposal
[Propsal No.]
Data Center
Outdoor Areas
Building Indoor Areas
Inner
Peripheral
Internet
Outdoor Coverage
Service
Control
System
Outdoor AP/
Wireless Bridge
Floor
Indoor Coverage
Indoor AP
Indoor CPE
Wireless
Bridge/ Switch
Outdoor CPE
Core
Ethernet
Switch
IDC
Indoor Coverage
Network
Management
Server
RADIUS
Server
Application
Servers
Tier-2
Ethernet
Switch
Tier-1
Ethernet
Switch
Indoor AP
Fiber with resilience
Fiber
Cat 5e for data
Wireless backhaul 802.11a/n
3.1 Outdoor Coverage
For the outdoor coverage, APs will be mounted on building roof top or lamp post.
The Seller should mark clearly the locations and state the mounting method and the
necessary provision of power supply and backhaul connection for each AP in the site
diagram provided.
The outdoor AP should be weatherproof without the need for additional cabinet or
enclosure.
All outdoor APs will use the physical Ethernet backhaul or the 802.11a/n wireless
backhaul to connect to the backend network proposed by the Seller. In case of
physical Ethernet backhaul, the AP location will be supplied with wired Ethernet
connection and connect to the Internet via the backend network. The outdoor AP
should preferably provide a large Wi-Fi signal coverage, so fewer number of
installation sites will be acquired and resulted in lower total cost of ownership (TCO) in
network deployment and faster network provision. The Seller should state the
maximum range of access coverage of the AP in LOS condition with a standard
laptop and with a CPE.
All outdoor APs should have interference mitigation features such that they can be
co-located at the mobile cellular site in order to save site acquisition costs and share
the power supply, Internet outlet and other facilities. The Seller should state the
minimum distance that their AP can be deployed in close proximity to a cellular base
station antenna.
Request for Proposal
[Propsal No.]
3.2 Indoor Coverage
There are 2 kinds of network provisioning for indoor coverage depending on the
building size and structure:


Wireless backhaul with CPE (outdoor and indoor)
Wired backhaul with indoor AP (optional)
3.2.1 Wireless Backhaul with CPE
The CPE should extend the outdoor 802.11b/g/n signal coverage to indoor areas and
provide 802.11b/g/n access coverage to users. The CPE should have outdoor
weatherproof capability compliant to at least IP-55 standards. The CPE shall be
located at rooftop, outside window or inside window areas of the building and each
CPE shall be back-to-back connected to another AP for indoor coverage. CPE
should be used whenever possible to minimize the cabling works.
CPE and the back-to-back connected AP should be set at different frequency
channels to minimize the interference to the outdoor AP. Using the same CPE as an
AP using single frequency channel (repeater) should be avoided. Multiple CPE-AP
pairs shall be used to provide complete indoor coverage of each floor as specified.
However, further repeat of signal from one AP to another should be avoided.
The cable length between CPE and AP should be designed to be as short as possible.
In case that a long cable is designed, the use of another CPE at the intended AP’s
location is preferable, and minimum cabling is desirable in the overall design.
The Seller should mark clearly the location of each CPE in the floor plans.
3.2.2 Wired Backhaul with Indoor AP (Optional)
For building with large partitioned floor areas where CPEs are unable to cover all
necessary areas directly, internal wired network should be laid and indoor AP should
be used to provide the wireless access.
Generally speaking, the Ethernet switch should be in 2-tier structure for multi-storey
buildings. The tier-1 Ethernet switches are located at each floor to connect to
multiple APs. The tier-2 Ethernet switch is located at the IDC equipment room or the
closet area to connect all the tier-1 Ethernet switches.
External broadband connection (wired backhaul) is connected to the tier-2 Ethernet
switch. The Seller shall state their resilience method for this connection if required. Cat.
5e cables should be used for the connection between tier-1 and tier-2 Ethernet
switches, and also between the APs and tier-1 Ethernet switch.
3.3 Data Center
All Internet access should be concentrated at the data center service control system.
The Seller should state clearly the bandwidth for the Internet line connected to the
service controller.
The network management server, RADIUS authentication server and other necessary
application servers should be installed at the data center.
Request for Proposal
[Propsal No.]
4. Ethernet Switch
4.1 Network Connectivity
The Ethernet switch should provide Gigabit Ethernet (Cat5e) network interfaces.
4.1.1 Fast Ethernet Interface
The switch should provide sufficient GE interfaces (Cat 5e RJ45). For each port, it
should support the following configurations:

Auto-negotiation

Manually selectable at 10 Mbps full duplex

Manually selectable at 100 Mbps full duplex

Manually selectable at 1,000 Mbps full duplex
4.2 Operation Support
4.2.1 802.1Q (VLAN)
The Switch should support 802.1Q (VLAN tagging) in all the interfaces. The ports can
be configured to access or trunk ports. VLANs allowed on the trunk ports should be
configurable.
4.2.2 802.1p (QoS) and Traffic Prioritization
The Switch should support 802.1p for QoS. Traffic can be marked to different QoS
types in both uplink and downlink directions. The marking can be based on one
and/or more of the following criteria.

Port-based QoS (TCP/UDP Port)

VLAN ID

IP Precedence of IP packet
5. Access Point (AP)
5.1 Network Connectivity Requirements
5.1.1 WAN Interface
The AP should provide a Gigabit Ethernet port and an 802.11a/n wireless backhaul
for WAN connection.
The WAN interface and the networking features should support:

VLAN

IPv4/IPv6 dual-stack

Switch (bridge) and gateway mode
Request for Proposal
[Propsal No.]











DHCP client/Server/Relay and fixed IP address assignment
NAT
PPPoE client, PPPoE pass-through
VPN pass-through
Bandwidth control per VAP/client
Multiple rate filter
IGMP snooping
Spanning tree protocol
Backhaul link integrity check, checking the backhaul status up to application
servers
Backhaul redundancy with auto switching and recovery
Auto turn down on radio in case of radio failure
5.2 Wireless Network Features
5.2.1 Operation Mode Support
The wireless network should support the following wireless standards.

802.11b/g/n for access

802.11a/n for backhaul connection or dual-band dual concurrent access

Dedicated radio(s) should be provided for access and backhaul

Interference mitigation capability

Throughput optimization capability
For 802.11g/n, the following should be supported

Settings for 802.11g/n higher speed should be enabled

“Short time slot” should be enabled

Radio preamble should be set to short

An 802.11b client will NOT force the wireless connections of other devices to fall
back to 802.11b for the same SSID(AP)
5.2.2 Radio Frequency Setting
The RF setting should support the following:

AP model with multiple radios is preferred

Comply US FCC standard (Channel 1-11)

Allow 2.4 GHz channel scan to show the signal and noise figures on all channels

Allow manual/automatic channel selection

Allow scheduling in channel selection

Support band steering
5.2.3 Multiple SSID Support
The wireless interface should have the following SSID supports:

16 SSIDs per radio or 32 SSIDs per AP

Each SSID can be in broadcast or suppressed mode

Each SSID can have independent wireless encryption setting, e.g. no encryption,
WEP, WPA, WPA2 or AES etc. and that will not affect other SSIDs

Each SSID can have independent QoS configuration (fixed profiles include “Very
High”, “High”, “Normal”, “Low” as well as profiles according to TCP/UDP ports,
TOS or WMM priority values)

Each SSID can limit the maximum number of users

Support WDS
Request for Proposal
[Propsal No.]
5.2.4 Wireless Security
The wireless interface should supports:

Rogue AP detection

MAC-based access control (including white list and black list)

Inter-VAP/ Intra-VAP client communication client

SSID suppression

RADIUS accounting

RADIUS client (PAP and CHAP)
5.2.5 Encryption support
Per SSID, the wireless interface should support the following encryption modes:

No encryption

128-bit WEP (shared key and dynamic WEP)

128-bit TKIP-MIC

128-bit AES-CCMP
The above is ONE profile. Each SSID can have its own profile and it will not affect the
operation of the other SSIDs.
5.3 Authentication Support
Besides wireless security (encryption), the AP should have:

WPA (PSK or dynamic key by 802.1x)

WPA2 (PSK or dynamic key by 802.1x)

Universal access method (UAM)

802.1x mutual authentication support
5.3.1 UAM (Universal Access Method)
In this access mode, no authentication is needed and the PC can associate to the
wireless interface of the AP freely.
5.3.2 802.1x Mutual Authentication
For each SSID configured to use 802.1x authentication, the client PC cannot
associate to the wireless interface unless the client is authenticated successfully with
802.1x standard.
5.3.3 RADIUS Support
RADIUS is used in the 802.1x support. The AP should have the following RADIUS client
support

Support RADIUS server IP and port configuration

Support backup RADIUS server

Support request timeout configuration

Support RADIUS authentication

Support RADIUS re-authentication based on timeout setting from RADIUS server
The above is ONE RADIUS profile. For each SSID with 802.1x standard support, an
independent profile can be configured and used. The different profiles will not affect
Request for Proposal
[Propsal No.]
each other.
5.3.4 EAP Support
In the 802.1x authentication, EAP is used in the authentication between the client
and the RADIUS server. The following EAP types should be supported:

PEAP

EAP-TLS

EAP-TTLS

EAP-SIM

EAP-AKA
5.4 System Operation Features
The AP should support the following features.
5.4.1 Per SSID Operation
The AP should allow independent configuration per SSID. The following configuration
per SSID should be supported:

Maximum number of users can be associated with

Wireless operation mode (broadcast or closed), see section 5.2.1

Wireless security (encryption), see section 5.2.4

Authentication, see section 5.3

EAP type in case of 802.1x, see section 5.3.4

Radius server in case of 802.1x, see section 5.3.3

VLAN ID for outgoing trunk traffic, see section 5.4.2
Each SSID should have its configuration independent of the others. They should not
affect the operation of each other as well.
5.4.2 VLAN Configuration
For single SSID, the AP should allow VLAN configuration. In the case of no VLAN, the
WAN port should be an access port. In case of VLAN assignment, the WAN port
should be a .1Q trunk port.
For multiple SSID case, the AP should allow VLAN assignment to each SSID, e.g.
VLAN1 for SSID1 and VLAN2 for SSID2 etc. The WAN port should be a .1Q trunk port.
In case of multiple SSID and VLAN configuration, traffic between different SSIDs
should be transported in the assigned VLAN only and will not affect that of the other
VLANs.
In case of a VLAN configuration, the AP should support management VLAN. The
management VLAN is a separate VLAN and should be confined to one SSID. Through
the management VLAN, the administrator can access and do administration on the
AP by accessing the AP.
5.4.3 Bridge Mode
Bridge mode should be supported in the AP.
Request for Proposal
[Propsal No.]
In bridge mode, the AP will form a layer 2 bridge link with the remote bridge
equipment.
The AP should run as Access Point and support bridge mode at the same time.
The bridge mode should support both point-to-point and point-to-multiple-point
operation.
The AP should equip with backhaul link integrity/resilience features to provide
network redundancy.
5.4.4 Quality of Service (QoS) Support
The AP should support the following QoS profiles for both WMM and non-WMM clients:

Fixed QoS Policy
− Very High (for voice)
− High
− Normal
− Low

ToS / 802.1q / 802.11e

Port-based QoS (QoS for non-WMM clients)
QoS support is required for the real-time voice and video traffic. The following should
be supported:
802.11e WMM
For the Wireless interface, the AP should support the WMM QoS standard, based on
802.11e. For those clients without WMM support, port-based QoS profile can be
created.
This is a Per SSID Configuration. That means some SSIDs can be configured to support
802.11e WMM and some to support fixed priorities.
Traffic prioritization
By configuring the AP, the AP should allow the voice and video traffic to have a
higher priority and being transmitted first. This is to ensure the jitter and delay within a
tolerable threshold for the human interaction.
802.1q/1p VLAN Traffic Marking
In the trunk mode, 802.1p Traffic marking on voice and video traffic should be
allowed.
This is a Per VLAN based. That is some VLANs can be configured to support 802.1p but
some are not.
6. Wireless Bridge
Request for Proposal
[Propsal No.]
6.1 Network Connectivity Requirements
6.1.1 Network Interface
The wireless bridge serves the purpose of connecting the outdoor AP to the backend
network through the wireless link, either in point-to-point or point-to-multipoint
configuration. It should provide a Gigabit Ethernet port and a 802.11a/n radio for
network connection.
The network interface should support:

DHCP client

VPN pass-through
6.2 Wireless Network Features
The wireless bridge should support the following 5 GHz frequency bands:

5.15 – 5.35 GHz

5.47 – 5.725 GHz

5.725 – 5.825 GHz
Depends on network requirement, 2 types of antenna configuration are required. The
wireless bridge should support the version of either built-in antenna or the external
antenna.
Antenna gain of built-in 5 GHz antenna should be at least 16 dBi.
The radio should support 802.11 a/n high throughput transmissions.
The wireless bridge is preferable to have extra 802.11b/g/n access radio such that it
can be operated as small area coverage AP.
The wireless link encryption scheme should include 64/128/152-bit WEP/AES.
7. Wireless CPE
7.1 Network Connectivity Requirements
7.1.1 WAN Interface
The functionality of the wireless CPE is to extend the outdoor Wi-Fi signal to indoor
coverage. The WAN interface should be standard 802.11b/g/n or 802.11a/n.
The wireless CPE should be capable to work in client mode – repeat the outdoor
802.11b/g/n or 802.11a/n signal to Ethernet signal.
Built-in cross-polarized patch antenna is preferred for the 2.4 GHz interface to provide
high antenna gain and transmit and receive diversity.
Separate CPE models can be used to support 802.11b/g/n and 802.11a/n frequency
bands.
Request for Proposal
[Propsal No.]
The wireless CPE should support the following networking features:

16 SSID

WDS

Throughput optimization feature

Automatic channel selection

Scheduling on channel selection

WMM

Preferred AP association
7.1.2 LAN Interface
To provide the network connection to the indoor devices, the wireless CPE should
support Fast Ethernet RJ-45 port and 802.11b/g/n or 802.11a/n access as the LAN
interface.
7.2 Security Features
It should support 64/128-bit WEP, WPA, WPA2, 802.11i security mode.
It should support MAC-based access control and SSID suppression.
It should support inter/intra-client isolation.
7.3 Networking Features
The wireless CPE should support the following networking features:

VLAN

IPv4/ IPv6 dual-stack

Switch (bridge) and gateway mode

DHCP client/server/relay

NAT

PPPoE client, PPPoE pass-through

VPN pass-through

Bandwidth control (per client or VAP)

Multicast rate filter

IGMP snooping

Port forwarding

Click to connect

Auto ACK timeout calculation by distance input
7.4 Management Features
The wireless CPE should support the following management features:

Standalone mode (managed by network management system)

Thin AP mode (managed by ACS/CAPWAP protocol)

Web user interface

Command line interface

At least 3 levels for user login

Remote firmware upgrade

SNMP v1/v2c

Performance statistics

Alarm information display
Request for Proposal
[Propsal No.]


Wi-Fi client association and disassociation status
Syslog
8. Service Control System
A service control system (SCS) is required to provide the system the functions of
bandwidth control and access control. It can also support the functions of backbone
router, firewall and VPN server. It allows users to login to the system through captive
portal and MAC-based authentication in addition to 802.1x-based authentications.
Different users may have different access rights, defined as a set of access rules (e.g.
allow TCP packets only) linked with the user account and the SSID to which the user
associated. The user account can be defined locally or remotely in RADIUS server.
The following sections should be applied to the service control system.
8.1 System Capacity
The service control system should support up to 16 Gbps throughput and 2,500 users.
Standard forwarding should support 8 mpps and Fastpath forwarding should support
24 mpps. The chassis should support rack mount. The network interface should
support 12 GE ports and 4 SFP ports.
8.2 Functions and Features
The service control system should support the following features:
8.2.1 Bandwidth Controller








Network traffic control
Limit data rate for all traffic passing through
Hierarchical HTB QoS system with burst
Per IP/ Protocol/ subnet/ port/ firewall mark
PCQ, RED, SFQ, FIFO queues
CIR, MIR, contention ratios,
Dynamics client rate equalizing (PCQ)
Bursts, peer-to-peer protocol limitation
8.2.2 Access Controller






Captive portal
MAC address authentication
RADIUS support
True plug-n-play access for network users
Authentication of local network clients
User accounting
8.2.3 Backbone Router

Static routing, VRF
Request for Proposal
[Propsal No.]







Failover backup and load sharing
Policy-based routing
Interface routing
Equal cost multi-path (ECMP) routing
IPv4 RIP v1/v2, OSPFv2, BGPv4
IPv6 RIPng, OSPFv3, BGP
Bidirectional forwarding detection (BFD)
8.2.4 Firewall







Stateful packet filtering; peer-to-peer protocol filtering
Source and destination NAT
NAT helper (H323, PPTP, quake3, SIP, FTP, IRC, TFTP)
Classification by source MAC, IP address, address range (network or a list of
network), address type, port, port range, IP protocols, DSCP
Protocol options (ICMP, TCP and MSS); interfaces
Internal connection, routing and packet marks
ToS (DSCP) byte; content; matching sequence/ frequency; packet size, time
8.2.5 VPN Server







IPSec – tunnel and transport mode, certificate or PSK, AH and ESP security
protocols
Point-to-point tunneling (OpenVPN, PPTP, PPPoE, L2TP)
Advanced PPP features (MLPPP, BCP)
Simple tunnels (IPIP, EoIP)
6to4 tunnel support (IPv6 over IPv4 network)
VLAN – IEEE 802.1q virtual LAN support, Q-in-Q support
MPLS based VPNs
8.2.6 DHCP and Proxy Servers


DHCP – Per interface DHCP server; DHCP client and relay; static and dynamic
DHCP leases; RADIUS support; custom DHCP options
Proxy – HTTP caching proxy server; transparent HTTP proxy; SOCKS protocol
support, DNS static entries; support for caching on a separate drive; parent
proxy support; access control list; caching list
8.2.7 Tools








Ping, traceroute
Bandwidth test, ping flood
Packet sniffer, torch
Telnet, SSH
E-mail and SMS send tools
Automated script execution tools
CALEA
File fetch tool
9. Management & System Support Tools
The following sections should be applied to the Ethernet Switch, the AP and the
wireless bridge.
Request for Proposal
[Propsal No.]
9.1 Remote Monitoring
The equipment should support the following monitoring tools:

Allow ICMP PING

SNMP v1/v2c support (SNMP GET/WALK)

Support SNMP Trap includes detail MIB explanation
9.2 Administration
The equipment should support the following administration methods:

Web administration

CLI- telnet and console

Ftp

SNMP v1/v2c

MIB

Syslog
Administration should support the following functions:

Equipment configuration for all the functions

Configuration provisioning by equipment group

Remote firmware upgrade

Check event/error logs/statistics

Check current (real time) traffic status etc.

Check RF settings (e.g. power, channel)

Access control (password protected)
The Web administration through the AP wireless interface should be configured as
enabled/disabled option.
9.3 Management Security Configurations
For administration methods in section 8.2, security configuration should be allowed so
that for each administration mode, administration through the following interfaces
can be allowed:

Wired and wireless (for AP)

Login password protected
If the AP equipment is managed through SNMP, the AP should be accessed by the
authorized SNMP host only.
9.4 Remote Firemare Upgrade
The equipment should allow remote firmware upgrade through HTTP/FTP.
10. Network Management System
Request for Proposal
[Propsal No.]
The following sections should be applied to the network management of APs and
wireless bridges.
10.1 Network Capacity
The Network Management System should support 20 network elements at initial stage,
and can be expandable to 4,000 network elements in future. It should support 8
concurrent administrators to access the system. Network elements should include AP,
wireless bridge and CPE.
The Seller should state the hardware and software specifications for the server(s)
required to set up the Network Management System.
10.2 Functions and Features
The Network Management System should support the following management
functions:
10.2.1 Fault Management








Real-time alarm collection and reporting
Visual network fault alerts via network map
Alarm acknowledgement and forced deletion
Alarm email alert
Alarm SMS alert
Event logging
Historical alarm tracking and reporting
Alarm SNMP trap for Northbound integration
10.2.2 Configuration Management








Single or mass network element configuration
Template-based configuration
Network element grouping
Automatic network element detection and provisioning
Network configuration resynchronization and consistency check
Configuration through network map
On-demand schedule-based firmware upgrade
Multiple firmware images
10.2.3 Administration Management





Wi-Fi client association summary
Wi-Fi client detailed information registration
Wi-Fi client searching by user identity
Wi-Fi client association summary history searching
Wi-Fi Client IP detection
10.2.4 Performance Management


Real time system performance statistics
Real time system/ network element traffic statistics
Request for Proposal
[Propsal No.]



Real time client traffic statistics
Hourly/weekly/monthly system/network element performance reporting
Hourly/weekly/monthly client performance reporting
10.2.5 Security Management





System user security management
WEP/WPA setting
MAC address access control
Rogue AP detection
Different login levels for AWMS client
10.2.6 RF Management


On-demand/schedule-based channel scanning
Channel scan summary
10.2.7 Bridge-Link Management



Link discovery
Link inventory
Link connection status monitoring
10.2.8 Network Map Management




Outdoor map with GPS alignment
Indoor map alignment
Network element location with GPS alignment
Network element logical view
10.2.9 GUI Languages Support
The Network Management System should support English, traditional Chinese and
simplified Chinese.
11. Hardware Specifications
Unless specified, the following requirements apply to the AP equipment.
11.1 Mechanical Requirements (For All Equipment)




The Seller should provide color photos of external view and mechanical
specifications (weight, dimensions, casing material) of all offered equipment
(switch, AP, antenna, mounting kits) with the bidding document
Technical drawings to show how mounting kits are assembled and associated
cabinet, if required
If the offer includes any cubicle and cabinet, the specifications should be
supplied
If the offer of equipment includes any cabling external to the equipment (e.g.
power, data, RF), the specifications should be supplied
Request for Proposal
[Propsal No.]
11.2 Reset Button (For AP and Switch)


Hardware button to restore to the factory default configuration
To restore to the factory settings through telnet/CLI
11.3 LED (For AP)
The AP should have LEDs to show its status, e.g. healthiness and port states.

Power

WAN link activity
11.4 LED (For Switch)
The Switches should have LEDs to show its status, e.g. healthiness and port states.

Power

Link status

Link activity
11.5 Operating Environments






Ambient Temperature : -40 ºC to +60 ºC (Ambient) for AP, -10 ºC to +40 ºC for
PoE injector, and -15 ºC to +60 ºC for ACS
Relative Humidity: 5% to 100 % condensing for AP and bridge, 5% to 95 % noncondensing for CPE, and 10% to 95% non-condensing for ACS
Dust proof
IP67 Weatherproof for outdoor equipment
Outdoor equipment should support survival wind loading up to at least 200 km/h
Outdoor equipment should comply with EN 61000-4-5 lightning protection
11.6 Non-operating Environments


Temperature: -40 ºC to +80 ºC
Relative Humidity: 5% to 100 % condensing for AP and bridge, 5% to 95 % noncondensing for CPE
11.7 Power Environments (For Switch)




AC Voltage: 220V Single Phase 50 Hz +/- 6%
The Seller should state the maximum power consumption and heat dissipation of
the equipment
Power plug shall be [British standard 3-rectanglar-pins 13A plug]
The power supply unit of the equipment must comply with the Specification for
“Safety of Information Technology Equipment, Including Electrical Business
Equipment”: EN 60950 or IEC 950 or UL1950
The Seller should provide copies of the related certificates with the bidding
document.
Request for Proposal
[Propsal No.]
11.8 Power Requirements (For AP)



PoE injector
The Seller should state the maximum power consumption of the AP
The power supply unit of the AP must comply with the Specification for “Safety of
Information Technology Equipment, Including Electrical Business Equipment” : EN
60950 or IEC 950 or UL1950
The Seller should provide copies of the related certificates with the bidding
document.
11.9 Power Requirments (For Wireless Bridge)


PoE injector
The Seller should state the maximum power consumption of the AP
The Seller should provide copies of the related certificates with the bidding
document.
11.10Power and Reliablity Requirments (For SCS)


110/220 VAC power supply
The Seller should state the maximum power consumption of the ACS
The Seller should provide copies of the related certificates with the bidding
document.
11.11 External Antenna (For AP)
External antenna (no power supply needed) can be attached to the AP in order to
extend the coverage of the AP. It should be able to extend to 6 m from the AP. The
antenna should be able to mount onto the wall, roof top or pole with associated
mounting kit.










2.4 GHz omni, sector or panel antennas support 802.11b/g/n with multiple or
smart antenna types preferred
Coaxial lead length is required at least 1 meter
2 to 14 dBi gain for omni directional coverage
Up to 19 dBi gain for directional coverage
The Seller should specify the antenna length
Option to offer various antenna type
Option to offer various horizontal beamwidth coverage including 90°, 180°, 270°
and 360°
Option to offer various antenna down-tilt and up-tilt angle and orientation
adjustment for different ground level coverage varying by range and direction
Cross-polarization antenna is preferred for better signal reception
The Seller is required to provide the specifications with RF antenna gain patterns
Request for Proposal
[Propsal No.]
11.12 Mounting Support
Associated mounting kit should be supplied so that the equipment can be mounted
on to the wall, roof top, pole or indoor premises where applicable.
11.13 Size and Weight (For AP)
The total weight of AP, antennas, cables and mounting kit should be less than 10 kg.
11.14 EMC Requirement
All the supplied equipment should comply with the FCC specifications Part 15B, 15C
and 15E.
The Seller should provide copy of the related certificate with the bidding document.
- End of Document -