Request for Proposal
Wireless Broadband System
for
[The User]
Technical Requirement
Date: Mar 12, 2010
Request for Proposal [Proposal No.]
TABLE OF CONTENTS
1.
2.
3.
4.
5.
INTRODUCTION........................................................................................ 5
1.1 SCOPE ................................................................................................. 5
SERVICE BACKGROUND .......................................................................... 5
2.1 SERVICE OVERVIEW............................................................................ 5
SERVICE NETWORK CONFIGURATION ..................................................... 5
3.1 OUTDOOR COVERAGE ........................................................................ 6
3.2 INDOOR COVERAGE ............................................................................ 6
3.3 DATA CENTRE ...................................................................................... 8
ETHERNET SWITCH ................................................................................. 8
4.1 NETWORK CONNECTIVITY .................................................................. 8
4.1.1 FAST ETHERNET INTERFACE................................................................ 8
4.2 OPERATION SUPPORT......................................................................... 8
4.2.1 802.1Q (VLAN) ............................................................................... 8
4.2.2 802.1P (QOS) AND TRAFFIC PRIORITIZATION ......................................... 9
ACCESS POINT (AP)................................................................................. 9
5.1 NETWORK CONNECTIVITY REQUIREMENTS ...................................... 9
5.1.1 WAN INTERFACE .............................................................................. 9
5.2 WIRELESS NETWORK FEATURES ....................................................... 9
5.2.1 OPERATION MODE SUPPORT............................................................... 9
5.2.2 RADIO FREQUENCY SETTING ............................................................ 10
5.2.3 MULTIPLE SSID SUPPORT ................................................................ 10
5.2.4 W IRELESS SECURITY ....................................................................... 10
5.2.5 ENCRYPTION SUPPORT .................................................................... 11
5.3 AUTHENTICATION SUPPORT ............................................................. 11
5.3.1 UAM (UNIVERSAL ACCESS METHOD) ................................................. 11
5.3.2 802.1X MUTUAL AUTHENTICATION ..................................................... 11
5.3.3 RADIUS SUPPORT ........................................................................... 11
6.
5.3.4 EAP SUPPORT ............................................................................... 12
5.3.5 ACCESS CONTROL SYSTEM .............................................................. 12
5.4 SYSTEM OPERATION FEATURES ...................................................... 12
5.4.1 PER SSID OPERATION..................................................................... 13
5.4.2 VLAN CONFIGURATION .................................................................... 13
5.4.3 BRIDGE MODE ................................................................................ 13
5.4.4 QUALITY OF SERVICE (QOS) SUPPORT ............................................... 14
WIRELESS BRIDGE ................................................................................ 15
Page 2
Request for Proposal [Proposal No.]
7.
8.
9.
6.1 NETWORK CONNECTIVITY REQUIREMENTS .................................... 15
6.1.1 NETWORK INTERFACE ...................................................................... 15
6.2 WIRELESS NETWORK FEATURES ..................................................... 15
WIRELESS CPE ...................................................................................... 16
7.1 NETWORK CONNECTIVITY REQUIREMENTS .................................... 16
7.1.1 WAN INTERFACE ............................................................................ 16
7.1.2 LAN INTERFACE ............................................................................. 16
7.2 SECURITY FEATURES ........................................................................ 16
7.3 NETWORKING FEATURES ................................................................. 17
7.2 MANAGEMENT FEATURES................................................................... 17
Management & System Support Tools .................................................... 17
8.1 REMOTE MONITORING ...................................................................... 17
8.2 ADMINISTRATION ............................................................................... 18
8.3 MANAGEMENT SECURITY CONFIGURATION ..................................... 18
8.4 REMOTE FIRMWARE UPGRADE ........................................................ 19
NETWORK MANAGEMENT SYSTEM ....................................................... 19
9.1 NETWORK CAPACITY......................................................................... 19
9.2 FUNCTIONS AND FEATURES ............................................................... 19
9.2.1 CONFIGURATION MANAGEMENT ......................................................... 19
9.2.2 FAULT MANAGEMENT ....................................................................... 20
9.2.3 SOFTWARE MANAGEMENT ................................................................ 20
9.2.4 SECURITY MANAGEMENT .................................................................. 20
9.2.5 PERFORMANCE MANAGEMENT .......................................................... 20
9.2.6 W IRELESS BRIDGE-LINK MANAGEMENT .............................................. 20
9.2.7 W IFI CLIENT MANAGEMENT .............................................................. 21
9.2.8 NETWORK MAP MANAGEMENT .......................................................... 21
9.2.9 GUI LANGUAGES SUPPORT .............................................................. 21
10.
HARDWARE SPECIFICATIONS ......................................................... 21
10.1 MECHANICAL REQUIREMENTS (FOR ALL EQUIPMENT) .................... 21
10.2 RESET BUTTON (FOR AP AND SWITCH) ............................................ 22
10.3 LED (FOR AP) ..................................................................................... 22
10.4 LED (FOR SWITCH) ............................................................................ 22
10.5 OPERATING ENVIRONMENT .............................................................. 22
10.6 NON-OPERATING ENVIRONMENT ..................................................... 22
10.7 POWER REQUIREMENTS (FOR SWITCH) .......................................... 23
10.8 POWER REQUIREMENTS (FOR AP) ................................................... 23
10.9 POWER REQUIREMENTS (FOR WIRELESS BRIDGE)......................... 23
Page 3
Request for Proposal [Proposal No.]
10.10 EXTERNAL ANTENNA (FOR AP) ........................................................ 23
10.11 MOUNTING SUPPORT ...................................................................... 24
10.12 SIZE AND WEIGHT (FOR AP) ............................................................ 24
10.13 EMC REQUIREMENT ........................................................................ 24
Page 4
Request for Proposal [Proposal 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, 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

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 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 NETWORK 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 centre
Page 5
Request for Proposal [Proposal No.]
Data Centre
Outdoor Areas
Building Indoor Areas
Inner
Peripheral
Internet
Access
Gatewa
y
Floor
Outdoor Coverage
Outdoor AP/
Wireless Bridge
Wireless
Bridge/ Switch
Indoor Coverage
Indoor AP
Indoor CPE
Outdoor CPE
Core
Ethernet
Switch
IDC
Network
Management
Server
Indoor Coverage
Indoor AP
RADIUS
Server
Tier-2
Ethernet
Switch
Application
Servers
Tier-1
Ethernet
Switch
Fibre with resilience
Fibre
Cat 5 for data
Wireless backhaul 802.11a
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 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 WiFi 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.
3.2 INDOOR COVERAGE
Page 6
Request for Proposal [Proposal No.]
There are 2 kind of network provisioning for indoor coverage depends 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 signal coverage to indoor areas and provide
802.11b/g 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 area 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 at short as possible. In case
that long cable to an AP 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.
Page 7
Request for Proposal [Proposal No.]
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. 5 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 CENTRE
All Internet access should be concentrated at the Data Centre Access Gateway. The Seller
should state clearly the bandwidth for the Internet line connected to the Access Gateway.
The Network Management Server, RADIUS authentication server and other necessary
application servers should be installed at the Data Centre.
4. ETHERNET SWITCH
4.1 NETWORK CONNECTIVITY
The Ethernet Switch should provide Fast Ethernet (Cat5) Network Interfaces.
4.1.1 FAST ETHERNET INTERFACE
The Switch should provide sufficient FE interfaces (Cat 5 RJ45). For each port, it should
support the following configurations:

Auto-Negotiation

Manually selectable at 10Mbps full duplex

Manually selectable at 100Mbps 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.
Page 8
Request for Proposal [Proposal No.]
4.2.2 802.1P (QOS) AND TRAFFIC PRIORITIZATION
The Switch should support 802.1p for QoS. Traffic can be marked to different QoS type 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 Fast Ethernet port or a 802.11a wireless backhaul for WAN
connection.
The WAN Interface and the networking features should support:

DHCP client/Server/Relay and fixed IP address assignment.

PPPoE client, PPPoE pass-through

VPN pass-through

NAT

VLAN

Switch and gateway mode

Backhaul link integrity check, checking the backhaul status up to application servers

Backhaul redundancy with auto switching and recovery
5.2 WIRELESS NETWORK FEATURES
5.2.1 OPERATION MODE SUPPORT
The wireless network should support the following wireless standards.

802.11b/g dual mode for access
Page 9
Request for Proposal [Proposal No.]

802.11a for backhaul connection

Dedicated radio should be provided for access and backhaul
For 802.11g, the following should be supported

Settings for 802.11g 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.4GHz channel scan to show the signal and noise figures on all channels

Allow manual/automatic channel selection
5.2.3 MULTIPLE SSID SUPPORT
The wireless interface should have the following SSID supports:

16 SSIDs

Each SSID can be in broadcast or suppressed mode

Each SSID can have independent wireless encryption setting, e.g. no encryption, WEP,
WPA and WPA2 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
5.2.4 WIRELESS SECURITY
The wireless interface should supports:

Rogue AP detection

MAC based access control
Page 10
Request for Proposal [Proposal No.]

Inter-VAP/ Intra-VAP client communication client
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
Page 11
Request for Proposal [Proposal No.]
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 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
5.3.5 ACCESS CONTROL SYSTEM
The AP should implement Access Control System (ACS) to provide the system a user level
AAA protocol: Authentication, Authorization, and Accounting.
It allows users to login to the
system through HTML-based and MAC-based authentication in addition to 802.1x-based
authentication.
Different users may have different access rights, defined as a set of access
rules (eg. 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.
HTML-based and MAC-based authentication mode can be configured as local authentication,
remote authentication or both. User credentials are validated using either a local database
(Local Authentication) or a third-party RADIUS server (Remote Authentication). If more than
one option is active, the remote accounts are always checked first.
5.4 SYSTEM OPERATION FEATURES
The AP should support the following features.
Page 12
Request for Proposal [Proposal No.]
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. VLAN 1 for
SSID 1 and VLAN 2 for SSID 2 etc. The WAN port should be a .1Q trunk port.
In case of multiple SSID and VLAN configuration, traffic between different SSID 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
Page 13
Request for Proposal [Proposal No.]
Bridge mode should be supported in the AP.
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
o
Very High (for voice).
o
High.
o
Normal.
o
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
Page 14
Request for Proposal [Proposal No.]
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
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 Fast Ethernet port and a 802.11a 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 5G 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 5G antenna should be at least 16dBi.
Page 15
Request for Proposal [Proposal No.]
Turbo mode should be supported to increase the link throughput if required
The radio is preferable to support 802.11 a/n for high throughput transmission.
The wireless bridge is preferable to have extra 802.11b/g/n access radio such that it can be
operated for 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 WiFi signal to indoor coverage.
The WAN interface should be standard 802.11b/g.
The wireless CPE should be capable to work in Client Mode – repeat the outdoor 802.11b/g
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.
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 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 base access control and SSID suppression.
Page 16
Request for Proposal [Proposal No.]
7.3 NETWORKING FEATURES
The wireless CPE should support the following networking features:

Bandwidth control (per client or VAP)

DHCP client/server/relay

Dynamic NAT

PPPoE client, PPPoE pass-through

VPN pass-through

Bridge/router mode

WDS

Preferred AP association

Site survey/Channel scan

Click to connect

Auto ACK timeout calculation by distance input
7.2 MANAGEMENT FEATURES
The wireless CPE should support the following management features:

Web-based administration tool

Remote firmware upgrade

SNMP

Performance statistics

TR-069 remote management
8. Management & System Support Tools
The following sections should be applied to the Ethernet Switch, the AP and the wireless
bridge.
8.1 REMOTE MONITORING
The equipment should support the following monitoring tools.

Allow ICMP PING
Page 17
Request for Proposal [Proposal No.]

SNMP v1/2c support (SNMP GET/WALK)

Support SNMP Trap includes detail MIB explanation
8.2 ADMINISTRATION
The equipment should support the following administration methods:

Web administration

CLI- telnet and console

Ftp

SNMP v1/2c

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.
8.3 MANAGEMENT SECURITY CONFIGURATION
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.
Page 18
Request for Proposal [Proposal No.]
8.4 REMOTE FIRMWARE UPGRADE
The equipment should allow remote firmware upgrade through HTTP/FTP.
9. NETWORK MANAGEMENT SYSTEM
The following sections should be applied to the network management of APs and wireless
bridges.
9.1 NETWORK CAPACITY
The Network Management System should support 30 network elements at initial stage, and
can be expandable to 500 network elements in future. It should support 4 concurrent
administrators to access the system.
Network elements should include AP and wireless
bridge.
The Seller should state the hardware and software specification for the server(s) required to
set up the Network Management System.
9.2 FUNCTIONS AND FEATURES
The Network Management System should support the following management functions:
9.2.1 CONFIGURATION MANAGEMENT

Single network element configuration

Template-based multiple network element configuration

Schedule-based configuration

Network element grouping

Network element registration

Automatic network element detection and provisioning

Network configuration resynchronization and consistency check

Configuration through network map
Page 19
Request for Proposal [Proposal No.]
9.2.2 FAULT MANAGEMENT

Real-time alarm collection and reporting

Visual network fault alerts via network map

Alarm acknowledgement and forced deletion

Event logging

Historical alarm tracking and reporting

Email alert for alarms
9.2.3 SOFTWARE MANAGEMENT

On-demand and schedule based firmware upgrade

Multiple firmware image
9.2.4 SECURITY MANAGEMENT

System user security management

WEP/WPA setting

MAC address access control
9.2.5 PERFORMANCE MANAGEMENT

Network element performance statistics

Network element traffic load statistics

Network element communication quality statistics
9.2.6 WIRELESS BRIDGE-LINK MANAGEMENT

Link discovery

Link inventory

Link connection status monitoring
Page 20
Request for Proposal [Proposal No.]
9.2.7 WIFI CLIENT MANAGEMENT

Client session notification and reporting

Client association summary

Client association reporting
9.2.8 NETWORK MAP MANAGEMENT

Outdoor map with GPS alignment

Indoor map alignment

Network element location with GPS alignment
9.2.9 GUI LANGUAGES SUPPORT
The Network Management System should support English, traditional Chinese and simplified
Chinese.
10. HARDWARE SPECIFICATIONS
Unless specified, the following requirements apply to the AP equipment.
10.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
Page 21
Request for Proposal [Proposal No.]
10.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
10.3 LED (FOR AP)
The AP should have LEDs to show its status, e.g. healthiness and port states.

Power

WAN link activity
10.4 LED (FOR SWITCH)
The Switches should have LEDs to show its status, e.g. healthiness and port states.

Power

Link status

Link activity
10.5 OPERATING ENVIRONMENT

Ambient Temperature : -40oC to +60oC (Ambient)

Relative Humidity: 0% to 100 %, condensing

Dust proof

IP67 Weatherproof for outdoor equipment

Outdoor equipment should support survival wind loading up to at least 200 km per hour

Outdoor equipment should comply with EN61000-4-5 lightning protection
10.6 NON-OPERATING ENVIRONMENT

Temperature: -40oC to +85oC

Relative Humidity: 0% to 100 %, condensing
Page 22
Request for Proposal [Proposal No.]
10.7 POWER REQUIREMENTS (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.
10.8 POWER REQUIREMENTS (FOR AP)

AC Voltage: 220V Single Phase 50 Hz +/- 6%, optional 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.
10.9 POWER REQUIREMENTS (FOR WIRELESS BRIDGE)

PoE, 48V DC

The Seller should state the maximum power consumption of the AP
The Seller should provide copies of the related certificates with the bidding document.
10.10 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.
Page 23
Request for Proposal [Proposal No.]

2.4G Hz Omni or Panel antennas support 802.11b and 802.11g with multiple or smart
antenna types preferred

Coaxial lead length is required at least 1 meter

2 -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° to avoid coverage for prohibited areas

Option to offer various antenna down-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
10.11 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.
10.12 SIZE AND WEIGHT (FOR AP)
The total weight of AP, antennas, cables and mounting kit should be less than 10 kg.
10.13 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 -
Page 24