MODULE FUNCTION

General

Bridge data model

Router data model
LAN interface

CFM

Multicast

IGMP snooping & ONT signaling

OMCI
 OMCI

IGMP proxy

VLAN manulation

P-bit/DSCP manipulation

802.1p Mapper
Queue scheduler (DS/US)
VLAN filter
Eth UNI loopback

Eth UNI PM counter

T-Cont/GEM
GEM/ANI PM Counter

Dying gasp

ALU propretary SSH

Turbo SW Download
Bundle rate

Hardware NAT

PPPoE passthrough

Other Switch Function

Bridge
Other Switch Function

Bridge

Metafile
Management Dual image
Data Source
OMCI ME
U-boot env

LED

Watchdog

VLAN manulation

TCP/IP Stack
TCP/IPv4 & Routing/NAT
NetFilter
VLAN in Linux

SPI Firewall

IPv6
 IPv6

802.1D Spanning Tree

PPPoE Client

DHCP Client

DHCP Server

IGMP Proxy

DNS Server/Relay
Wifi Supplicant

Wifi Driver
 Agent
Standard MIB-2
SNMP Trap
Standard MIB-2
Private MIB

Protocol
TR-069

Middleware
Httpd & CGI core
Middleware
Web page
Multiple user level
Password

Web GUI
Multiple WAN-Bridge

Multiple WAN-Router

CLI engine
CLI menu
CLI
Telnet
SSH
TFTP Server
Calibration Tool
UPnP
 Description BMT Owner

TC-03
TC-19

1:MP TC-04
1 VEIP as a WAN interface TC-12
eth0 (or br0) for LAN access 6.5.1
TC-12

TC-21

At least 5 VLAN TC-08

Snooping

IGMP v2
TC-04
TC-08
TC-18

Fast Leave
Need to forward IGMP to IP stack?? TC-18

Port based VLAN 6.5.2.7

Protocol based VLAN

Protocol based VLAN by EtherType

802.1Q VLAN TC-04
TC-11
TC-12
Q in Q VLAN
1:1 VLAN
N:1 VLAN
TLS VLAN
Transparent VLAN

TC-11

6.5.2.8
TC-05
TC-11 6.5.2.8

TC-20

802.11n PM Counter??
TC-04
TC-09
TC-20

TC-02 6.5.1

TC-19
TC-19
TC-05
Forwarding rate
TC-09

6.5.2.12
TC-09 6.5.1
TC-06 6.5.2.9
 TC-11

default values TC-19

TC-19

6.5.3

6.5.2.7

IP -> VLAN ?? TC-11

IP -> VLAN ??
Specific IP to VLAN ??

Multiple WAN-router TC-12

Port forwarding
TC-13

ALG
Policy based routing ??

Static routing
NAPT TC-12
IP/ARP
ICMP

TC-16

TC-12
 6.5.2.9

TC-12
TC-14

6.5.2.17
6.5.2.13

TC-15
6.5.2.7

TC-11
TC-15

TC-18

6.5.2.10
6.2.4
TC-10

6.2.4

TC-10
 6.5.1
TC-12
TC-19

TC-19
6.5.2.4

TC-12 6.5.2.4

6.5.1

6.5.2.9

6.5.2.10

6.5.2.12
6.5.2.16

TC-12 6.5.2.4
TC-12 6.5.2.4
TC-12 6.5.2.4
TC-17
 CHT Spec.
5.4.1.1 The ONU shall support the ranging function in the discovery procedure and normal
5.4.1.2 The ONU shall support the activation procedure based on discovered and configure
5.4.1.3 The ONU shall support the initial provisioning function:
(1) Shall support the local setting of a registration ID via Ethernet UNI or CIT of MDU.
(2) Shall support the registration ID approach and retain the registration ID indefinitely.
(3) Shall support the security capabilities, such as login authorization, to prevent unauthor
8.1.14 The Network shall at least support following Managed Entities (MEs) of the GPON in
(1) Requirement MEs: ONT-G, ONT2-G, ONT data, T-CONT, Software Image.
(2) Conditional Requirement MEs: Circuit Pack, Cardholder, Priority Queue-G, Traffic Sched

(a) An Ethernet interface for web-based operation.

6.5.2.2 Shall support at least two configurable LAN IP addresses.
6.5.2.17 ◎ Connectivity fault management functional requirements
(1) Shall comply with the IEEE 802.1ag or later version.
(2) Shall support the capability of customer and access link maintenance domain levels.
(3) The maintenance levels value shall be configurable and shall be able to configure the v
(4) Shall at least support the following function for customer maintenance domain level:
(a) Shall support MEP on per VLAN basis.
(b) Shall support LTR and LBR for each MEP.
(c) MEP shall support the capability to receive both unicast and multicast LBMs from MEP(s
(d) MEP shall support the capability to receive a LTM from MEP(s) that originated the LTM,
(e) MEP shall support the capability to initiate the LBM and LTM to target MP(s).
(f) MEP shall support the capability to receive a CCM from MEP(s) that originated the CCM.
(g) MEP shall support the capability to transmit CCMs and shall be enabled and disabled v
(5) Shall at least support the following function for access link maintenance domain level:
(a) Shall support MEP on per VLAN basis.
(b) Shall support LTR and LBR for each MEP.
(c) MEP shall support the capability to receive both unicast and multicast LBMs from MEP(s
(d) MEP shall support the capability to receive a LTM from MEP(s) that originated the LTM,
(e) MEP shall support the capability to initiate the LBM and LTM to target MP(s).
(f) MEP shall support the capability to receive a CCM from MEP(s) that originated the CCM.
(g) MEP shall support the capability to transmit CCMs and shall be enabled and disabled v
8.3.28 ◎ The IEEE 802.1ag Ethernet CFM Loopback function shall be able to be enabled/di

6.5.2.3 IGMP snooping function: Shall support the IGMP snooping function specified in IETF
5.4.2.4 IGMP controlled multicast functional requirements
(1) Shall support IGMPv2 as specified in RFC 2236 or later version.
(2) Shall support the IGMP snooping function as specified in RFC 4541 or later version.

(3) The multicast clients of ONT shall be able to join up to 5 dedicated multicast VLANs.
(4) Shall support the IGMP filtering function.
(5) Shall support the function of IGMP immediate leave.
6.5.2.6 VLAN function: Shall at least support the configurable IEEE 802.1Q VLANs and port
(1) Shall support configurable port-based VLANs.
(2) Shall support configurable protocol-based VLAN as follows:
(a) Shall support the upstream traffic classification according to the following information
(i) Ethertype field (at least IPoE, PPPoE and IPv6).
(b) The classified packets shall be able to be tagged with VLAN ID and Ethernet priority bit
(c) The number of classification entries shall be at least 6.
(3) Shall support IEEE 802.1Q VLAN pass-through functions.

6.5.2.8 802.1p function:

(1) Shall support IEEE 802.1p Ethernet priority function.
(3) ◎ Shall be able to read Differentiated Service Code Point (DSCP) bits as specified in RF
(2) Shall be able to read Ethernet priority bit, and classify packets into different priority qu

(4) The priority queue shall at least support Strict Priority (SP) scheme with at least four pr

6.5.2.1 Shall be able to display transmitted and received traffic for LAN Ethernet interface
8.1.9 The Network shall support following transmitted and received traffic information disp
(1) Display type:
(a) Total packet count and total byte count.
(b) Broadcast, multicast and unicast packet or byte count.
(c) Traffic rate (byte/sec or bit/sec).
(2) Display position:
(b) Per ONT or per UNI of ONT.
(d) ◎ Per HGW/RG and per IEEE 802.11n wireless AP of HGW/RG.

5.4.1.4 The ONU shall be able to notify OLT system via Dying gasp message when the ONU
(8) Shall have the ability to detect the defect when the HGW-O electrical supply power dro
8.1.5 When an unrecoverable remote failure such as electric power outage occurs, the ON

6.5.2.15 Forwarding rate:

(1) The packet forwarding rate for downstream/upstream shall be supported up to:
(2) The packet forwarding rate for downstream/upstream, by using test packet of 1518 by
(9) If using PPPoE client function actively, the HGW-O shall be able to forward PPPoE sessio
(1) Forwarding rate: Shall support 1,488,000/1,488,000 pps for downstream/upstream.
(2) Shall at least support the capability of MAC learning addresses up to 512.
(3) Shall support the Ethernet MAC address filtering function about the upstream traffic, a
(4) The WAN interface shall support multiple WAN connections, and each WAN connection
(5) Each WAN connection with bridging function shall be able to display transmitted and re
6.5.3.2 Shall support the capability of MAC learning addresses up to 512.
8.1.10 The Network shall support the function to display upstream source MAC addresses
(2) ONT: Based on per ONT, per VLAN, or per UNI of ONT.
8.3.1 The OLT system, ONU and HGW/RG shall support the capability to configure the Buy
8.3.2 The OLT system, ONU, and HGW/RG shall support remote firmware upgrade function
8.3.3 ◎ The OLT system, ONU and HGW/RG shall support two complete boot images and o

(3) Shall provide different status indicators on the front panel:

(a) Power.
(b) Alarm.
(c) LAN (also UNI) connectivity for each LAN port.
(d) Wireless connectivity and data Transmit/Receive for HGW-Oew and HGW-Oewv.

(2) Shall support configurable protocol-based VLAN as follows:

(a) Shall support the upstream traffic classification according to the following information
(ii) Source IP address and subnet mask.
(iii) ◎ Destination IP address and subnet mask.
(iv) ◎ DHCP option 60/61/125 identifier value.
6.5.2.10 Shall support the IP Routing (IPR) function and the requirements are described as
(1) The IPR function relies on standard IP routing for its forwarding and HGW-O LAN port sh
(2) The WAN interface shall support multiple WAN connections, and each WAN connection
(3) Each WAN connection with IPR function shall support the configured untagged and tag
(4) Each WAN connection with IPR function shall be able to display transmitted and receive
6.5.2.11 NAT capability:
(1) Network address translation function shall be supported.
(2) ◎ This function shall be configured per WAN connection basis and at least support two
(3) Shall support the TCP/UDP port forwarding function. The Server hosting applications su
(4) The capability of address translation shall at least allow the number of hosts, which is t
(5) The address translation function shall comply with IETF RFC 1631 or RFC 2663 or later
(6) Shall support the NAT ALG (Application Level Gateway) function specified in IETF RFC 3
(7) ◎ Shall support the capability to classify the traffic to different NAT session according t
6.5.2.19 Routing function:
(1) Shall support static routing function, and the routing rule shall at least support by dest
(2) Internet access sharing:
(a) IETF RFC 791 for IP and IETF RFC 826 for ARP protocols shall be complied.
(b) ICMP protocol shall be complied.
6.5.2.20 Firewall function
(1) Source/Destination IP address(es) with subnet mask.
(2) Source/Destination MAC address(es).
(3) Protocol type.
(4) Source /Destination port.
6.5.2.5 Management Control List (MCL) function: Shall support the MCL capability which ca
27.規格第10.4 項IPv6 補充說明(for HGW-O)：
(1)Shall support “MUST” requirements for IPv6 customer edge routers specified
in RFC6204.
(2)Shall support RFC 6204 WLL-1, WLL-2 and WLL-3 requirements.
(3)Shall support IPv6 address and DNS manual configuration.
(1) Shall operate as a self-learning bridge as specified in the IEEE 802.1D - full protocol tra
6.5.2.12 PPPoE function:
(1) Shall be enabled and disabled via configuration.
(2) Shall comply with the functions defined in IETF RFC 2516.
(3) Shall support automatic connection setup and tear down functions.
(4) Shall be able to support users to configure time intervals parameters for HGW-O to tea
(5) Shall establish a PPPoE connection automatically when no PPPoE connection exists in t
(6) Shall be able to support users to configure the username and password in order to logi
(7) Shall be able to assign some specific VLAN to run PPPoE, especially when the HGW-O is
(8) Shall at least support two PPPoE sessions capability.
(9) If using PPPoE client function actively, the HGW-O shall be able to forward PPPoE sessio
(1) Support user authentication function, at least PAP and CHAP, with PPP as specified in IE
(7) DHCP client function:
(a) The WAN connection with DHCP client function shall support the configured untagged a
(b) Shall at least support two DHCP client sessions capability.
(2) Shall support configurable protocol-based VLAN as follows:
(a) Shall support the upstream traffic classification according to the following information
(iv) ◎ DHCP option 60/61/125 identifier value.
6.5.2.13 DHCP function:
(1) Shall support the DHCP server, relay, and client functions specified in IETF RFC 2131 an
(2) ◎ Shall support DHCP option 61 node-specific client identifiers specified in IETF RFC 43
(3) ◎ Shall support DHCP option 60 vendor class identifier specified in IETF RFC 2132. The
(4) ◎ Shall support DHCP option 125 vendor-specific information specified in IETF RFC 392
(5) ◎ If enabling DHCP client function, the DHCP option identifier of HGW-O shall be config
(a) DHCP option 61: same as item 6.5.2.13(2).
(b) DHCP option 60: same as item 6.5.2.13(3).
(c) DHCP option 125: same as item 6.5.2.13(4).
(6) ◎ DHCP server function:
(a) Shall support the functions
(i) Shall support the capability to assign IP address, subnet mask, default gateway and DN
(ii) Shall support the capability to assign a specific IP address based on source MAC addres
(iii) Shall support the capability to assign a specific IP address and subnet mask based on
(b) Shall support the following operation based on DHCP option 60/61/125 identifier and ca
(i) Shall support the capability to assign a specific IP address and subnet mask based on D
(ii) Shall support the capability to forward the DHCP session initiated from LAN device to W
(iii) Shall support the capability to forward the DHCP session initiated from LAN device to W
6.5.2.14 Multicasting function:
(1) Shall support Internet Group Management Protocol (IGMP) version 2 specified in IETF R
(2) IGMP proxy function: Shall support the IGMP proxy function specified in IETF RFC4605 o
(3) The multicast stream shall be worked well when enabling IGMP proxy with NAT and fire
(2) The WAN interface shall support multiple WAN connections, and each WAN connection
(11) Authentication and encryption functions per SSID (Service Set Identifier) basis:
(a) Shall support WEP (Wired Equivalent Privacy) data encryption with configurable 64/128
(b) Shall support WPA-Personal (Wi-Fi Protected Access) and WPA2-Personal authentication
(c) Shall support AES (Advanced Encryption Standard) hardware encryption.
(d) Shall support TKIP (Temporal Key Integrity Protocol).
(e) Shall support IEEE 802.1X function:
(i) Shall support the function to act as an Authenticator.
(ii) Shall be able to respond to an appropriate IEEE 802.1X request and provide certificate
(iii) Shall support EAP-MD5 username and password type authentication.
(iv) Shall support EAP-TTLS /MS-CHAPv2 security function.
(12) Shall support the multicast traffic pass-through function.
(13) Shall at least support SSIDs:
(b) ■ ≧ 4.
(1) The Ethernet packet shall comply with IEEE 802.3u Fast Ethernet standard.
(2) Shall backward compatible with 802.11g and 802.11b devices.
(3) RF frequency range: ISM band, 2.4GHz~2.4835GHz.
(4) Modulation technology: OFDM (Orthogonal Frequency Division Multiplexing).
(5) Channel bandwidth:
(b) ■ 20MHz and 40MHz (Auto or user configurable).
(6) MIMO (Multiple Input Multiple Output) type:
(b) ■2 X 2 (2T2R).
(7) Data rate: With auto fallback function.
(a) In conditions at MIMO Nss (Number of Spatial Streams) =1 and 20MHz channel ban
(b) In conditions at MIMO Nss=1 and 40MHz channel bandwidth, the relation between da
(c) In conditions at MIMO Nss=2, 3 or 4, the maximum data rate shall be at least 300, 450
(8) OFDM operating parameters:
(9) Transmitter:
(a) Max. transmit power(In conditions at MCS=64QAM 5/6 and channel bandwidth=40MHz
(ii) ■≧14 dBm.
(b) The transmit power shall at least support 3 adjustable levels, and shall at least support
(c) The transmitter center frequency tolerance shall be ± 25 ppm maximum for the 2.4 GH
(d) Transmit spectrum mask shall comply with the definitions of IEEE 802.11n standard.
(10) Receiver:
(a) In conditions at MIMO Nss=1, PSDU length=4096 bytes, and PER(Packet Error Rate) ≦
(b) Receiver maximum input level: ≧-20dBm.
(14) Shall support the function to enable/disable the broadcasting of SSID.
(15) Shall be able to configure IEEE 802.1Q VLAN and Ethernet priority bit per SSID basis.
(16) Shall be able to configure the maximum users per SSID basis.
(17) Shall be able to configure the maximum data rate per SSID basis.
(18) Shall support the MAC address filter function about the upstream traffic, and the filter
(19) Shall be able to display transmitted and received traffic in bytes and packets counter
(a) ■ Per wireless AP interface basis.
(b) ■ Per SSID basis.
(20) Shall be able to display transmitted and received traffic in bytes and packets counter
(a) ■ 32-bit counter.
(21) Shall support Wi-Fi WMMTM (Wi-Fi Multimedia) function.
(22) Shall support the function to enable/disable the inter-client communication directly th
(23) Antennas:
(a) ■ Built-in Omni antenna, Antenna Gain ≥ 2 dBi.
(24) Shall support UAPSD (Unscheduled Automatic Power Save Delivery) function.
(25) Shall support static and dynamic SMPS (Spatial Multiplexing Power Saving) function w
(26) Shall support Wireless Schedule function, and shall be able to enable/disable Wireless
(7) SNMP (Simple Network Management Protocol) function:

(a) Shall support the SNMP agent and IETF RFC1213 MIB II (at least System and Interface G
(b) Shall support LAN and WAN MIBs for transmitted and received traffic.
(c) ■ ◎ Shall support MIBs for cold and warm start trap and link up and down trap.
(d) ■ ◎ Shall support LAN and WAN MIBs for transmitted and received error traffic and tra
(e) ■ ◎ The system performance of HGW-O shall not be downgraded by SNMP operations.
(f) The SNMP MIBs of all functions of the HGW-O that mentioned in the Specification should
(4) SNMP agent function: Shall support the SNMP agent function specified in IETF RFC 115
6.5.2.21 TR-069 remote management function:
(1) The Bidder shall commit to adopt CHT’s TR-069 remote management client solutions to
(3) In case of the TR-069 remote firmware upgrade fails, the HGW-O shall be able to opera
(三)TR-069 整合：
1. 本案售方需配合購方完成以下Home Gateway (HGW-O)設備之TR-069 Client 軟體整合功能開發：
(1) HGW-O 設備與OLT 間必需具有遠端軟體升級功能，待中華電信研究院與售方整合TR-069 功能後，可採OLT 遠端軟體升級方式將已建置於用戶端
(2) 投標廠商之HGW-O 設備，須於決標日次日起四個月(120 天)內完成與本公司提供之授權TR-069 軟體整合。
(3) HGW-O 設備與本公司TR-069 Client 軟體整合工作由售方負責，本公司安排人力配合整合。軟體整合過程中，雙方有義務互相配合完成整合工作。
(4) 購方依客戶需求，將持續修改TR-069 軟體，並將改版之TR-069 軟體交給售方進行HGW-O 之軟體整合與HGW-O 設備更新，售方須無償為
(5) 經中華電信研究院授權TR-069 軟體整合後，後續約交之HGW-O 設備須具備TR-069 功能。
2. 購方得依現場環境需要，於指定之上層網路設備作連通測試，有關測試項目由購方指定，售方應配合辦理。
8.3.22 The HGW/RG shall support remote enable/disable functions to control IEEE 802.11n
(3) Web server function: Shall support the Web Server function specified in IETF RFC 1945

(6) Password length: Shall support the capability to configure the password and the passw
6.5.2.1 Shall be able to display transmitted and received traffic for LAN Ethernet interface
6.5.2.2 Shall support at least two configurable LAN IP addresses.
(3) Shall support the Ethernet MAC address filtering function about the upstream traffic, a
(4) The WAN interface shall support multiple WAN connections, and each WAN connection
(2) The WAN interface shall support multiple WAN connections, and each WAN connection
(3) Each WAN connection with IPR function shall support the configured untagged and tag
(4) Each WAN connection with IPR function shall be able to display transmitted and receive
(4) Shall be able to support users to configure time intervals parameters for HGW-O to tea
(2) Except that the parameters specified in item 6.5.2.12(4) and (6) can be configured by

(1) Telnet server function: Shall support the Telnet Server function specified in IETF RFC 85
(5) Secure Shell (SSH) function: Shall support the SSH protocol specified in draft-ietf-secsh
(2) TFTP server function: Shall support the TFTP Server function specified in IETF RFC 1350
6.5.2.18 UPnP function:
(1) Shall support UPnP device identification function and shall be able to display the follow
(a) Manufacturer name.
(b) Modem name.
(c) Model number.
(d) Description.
(e) Device address.
(2) Shall support UPnPTM Forum Internet Gateway Device (IGD) 1.0 Device Control Protoco
(3) Shall support UPnP NAT Traversal function.
(4) Shall not forwarding UPnP traffic to the WAN interface.
d normal state
configured Serial Number methods in compliance with ITU-T Rec. G.984.3.

unauthorized intrusion.
GPON in compliance with ITU-T Rec. G.984.4.:

ffic Scheduler-G, GEM traffic descriptor, Threshold data 1/2, GEM Interworking Termination Point, GEM

ure the value of the customer level to 5 and the value of the access link level to 1.

om MEP(s) that originated the LBM, and initiate the associated LBR.
he LTM, and initiate the associated LTR.

sabled via configuration.

om MEP(s) that originated the LBM, and initiate the associated LBR.
he LTM, and initiate the associated LTR.

sabled via configuration.

abled/disabled.

d in IETF draft-ietf-magma-snoop-04 or later version. The number of supported concurrent multicast

and port-based VLAN functions. The number of the IEEE 802.1Q VLANs shall be ≧ 8.

rmation as an option:

iority bit, and be assigned to priority queues.

ed in RFC 2475, and classify packets into different Ethernet priority queues according to DSCP value
iority queues according to Ethernet priority bit.

st four priority levels.

tion display functions on demand on the follows:

the ONU is in power failure

ower drops to a level equal to or below the minimum power level required to ensuring proper opera
, the ONU and HGW/RG shall have the ability to send the loss of power message to the OLT system.

1518 bytes packet size shall be supported up to 500M/500M when PPPoE and NAT functions are bot
oE sessions initiated from LAN devices as additional PPPoE sessions to the WAN interface (PPPoE pa

traffic, and the filtering function shall be able to permit and deny the user traffic based on source M
nnection with bridging function shall support the configured untagged and tagged VLAN capability.
ed and received traffic.

dresses learned information on following:

the Buyer’s default configuration.

function.
es and one configuration file. In case remote firmware upgrade fails, the ONU and HGW/RG shall be

rmation as an option:

ribed as follows:
N port shall be assigned IP address under IPR operation.
nnection with IPR function shall support the capability to assign the IP statically or dynamically, and
and tagged VLAN capability.
d received traffic.

port two NAT sessions capability.

ations such as Web, FTP, Mail, etc shall be supported.
which is the same as the number of the supported MAC learning addresses specified in 6.5.2.9(2), to
or later version.
TF RFC 3235, and at least support SIP, H.323 (Microsoft NetMeeting) and IPSec applications.
cording to the source IP address, source MAC address and TCP/UDP port number.

by destination IP address(es) and subnet mask.

which can be at least assigned 16 IP addresses for managing HGW-O, and HGW-O shall be configure
 tocol transparent bridging function.

O to tear down PPPoE connection. While PPPoE connection is active and the idle time duration for th
xists in the HGW-O and the subscriber would like to send traffic to the ISP.
er to login in ISP.
HGW-O is with multiple VLANs.

oE sessions initiated from LAN devices as additional PPPoE sessions to the WAN interface (PPPoE pa
fied in IETF RFC 1334.

tagged and tagged VLAN capability.

rmation as an option:

2131 and RFC 2132.

F RFC 4361 and support configurable DUID (DHCP Unique Identifier) and IAID (Identity Association Id
132. The identifier of DHCP option 60 sent from LAN device shall be mapped to the same and differe
RFC 3925 and support configurable manufacturer OUI, product class, model name and serial numbe
be configured and mapped to the 802 1Q VLAN and Ethernet priority bit while the following DHCP op

and DNS server to LAN device automatically.

C address.
ased on LAN Ethernet interface.
er and can be configured as any one of the following functionalities.
sed on DHCP option 60/61/125 identifier matched with HGW-O configuration. If unmatched, HGW-O
vice to WAN interface based on the DHCP option 60/61/125 identifier matched with HGW-O configur
vice to WAN interface based on the DHCP option 60/61/125 identifier unmatched with HGW-O config

n IETF RFC2236 or later version.

FC4605 or later version.
T and firewall features.
nnection with IPR function shall support the capability to assign the IP statically or dynamically, and
 e 64/128-bits data encryption.
entication and data encryption.

rtificate information using Extensible Authentication Protocol-Transport Layer Security (EAP/TLS).

annel bandwidth, the relation between data rate and MCS (Modulation and Coding Scheme) of OFDM
ween data rate and MCS of OFDM is described below:
300, 450 or 600Mb/s.

=40MHz.) shall be:

t support 3dB difference between each level.

he 2.4 GHz band.

or Rate) ≦10%:

the filter function shall be able to permit/deny the wireless client traffic based on source MAC addre
counter format:

rectly through Wi-Fi AP.

 nction when MIMO Nss ≥ 2.
Wireless AP interface by schedule.

terface Groups).

c and transmitted and received discarded traffic.

on should be supported.
RFC 1157 or later version and shall be able to be enabled/disabled for the LAN and WAN, via configu

utions to support the TR-069 remote management functions within specified period which is specifi
to operate well during and after restarting.

已建置於用戶端HGW-O進行軟體升級。

，售方須無償為購方進行相關之整合與更新。

802.11n wireless AP interface, PPPoE function, Network Address Translation (NAT) function, and Ser
FC 1945 or later version and shall be able to be enabled/disabled for the LAN and WAN, via configur

he password length shall be at least 16 Alphanumerics.

traffic, and the filtering function shall be able to permit and deny the user traffic based on source M
nnection with bridging function shall support the configured untagged and tagged VLAN capability.
nnection with IPR function shall support the capability to assign the IP statically or dynamically, and
and tagged VLAN capability.
d received traffic.
O to tear down PPPoE connection. While PPPoE connection is active and the idle time duration for th
ured by users freely, the HGW-Oe shall be able to support a secure mechanism to prevent users fro

F RFC 854 and shall be able to be enabled/disabled for the LAN and WAN, via configuration. If the T
etf-secsh-connect-16.txt or later version, which can create a secure connection between HGW-O and
RFC 1350 and shall be able to be enabled/disabled for the LAN and WAN, via configuration.If the TFT
he following information:

l Protocol (DCP).
rmination Point, GEM Port Network CTP, MAC Bridge Configuration Data, Extended VLAN tagging ope

oncurrent multicast groups shall be at least 4.

ording to DSCP values.

suring proper operation of the HGW-O. In this case, the HGW-O shall provide the LPR (or Dying gasp
to the OLT system.

AT functions are both enabled.

interface (PPPoE pass-through).

based on source MAC addresses.

 d VLAN capability.

nd HGW/RG shall be able to operate well during and after restarting.

or dynamically, and shall at least support two DNS servers capability.

fied in 6.5.2.9(2), to work well concurrently.

applications.

-O shall be configured and managed by devices with the MCL IP addresses only.
 time duration for the connection is over the configured time interval, HGW-O shall disconnect the P

interface (PPPoE pass-through).

entity Association Identifier) portions. The identifier(s) of DHCP option 61 sent from LAN device shal
he same and different 802 1Q VLAN(s) and different Ethernet priority bits. If the identifier of DHCP o
me and serial number portions. The information(s) of DHCP option 125 sent from LAN device shall be
e following DHCP option(s) is required:

nmatched, HGW-O shall assign an IP address and subnet mask automatically,

ith HGW-O configuration. If unmatched, HGW-O shall assign an IP address and subnet mask automa
d with HGW-O configuration. If matched, HGW-O shall assign an IP address and subnet mask automa

or dynamically, and shall at least support two DNS servers capability.

ecurity (EAP/TLS).

g Scheme) of OFDM is described below:

n source MAC addresses.

nd WAN, via configuration, and shall be able to configure SNMP read/write communities. If the SNMP

riod which is specified in Procurement Specification.

T) function, and Server and agent functions.

d WAN, via configuration. If the Web Server function is disabled, the TCP port number of Web Serve

based on source MAC addresses.

d VLAN capability.
or dynamically, and shall at least support two DNS servers capability.

time duration for the connection is over the configured time interval, HGW-O shall disconnect the P
to prevent users from configuring and displaying the relative parameters associated with the other f

onfiguration. If the Telnet Server function is disabled, the TCP port number of Telnet Server function
between HGW-O and a remote client. The SSH function shall be able to be enabled/disabled via confi
figuration.If the TFTP Server function is disabled, the UDP port number of TFTP Server function shall
ed VLAN tagging operation configuration data, UNI-G, Multicast GEM interworking termination point,
LPR (or Dying gasp) indicator to OLT system.
all disconnect the PPPoE automatically.

om LAN device shall be mapped to the same and different 802 1Q VLAN(s) and different Ethernet pr
identifier of DHCP option 60 sent from LAN device is not configured, the default VLAN and Ethernet
LAN device shall be mapped to the same and different 802 1Q VLAN(s) and different Ethernet priori

ubnet mask automatically (DHCP pass-through function),

subnet mask automatically (DHCP pass-through function).
munities. If the SNMP agent function is disabled, the UDP port number of SNMP agent function shall b

mber of Web Server function shall be closed.

all disconnect the PPPoE automatically.

ated with the other functions specified in item 6.5.1 and 6.5.2.

net Server function shall be closed.

ed/disabled via configuration.
erver function shall be closed.
g termination point, Physical Path Termination Point Ethernet UNI.
different Ethernet priority bits. If the identifier(s) of DHCP option 61 sending from LAN device is not c
VLAN and Ethernet priority bit shall be assigned in the HGW-O.
erent Ethernet priority bits. If the information(s) of DHCP option 125 sending from LAN device is not
gent function shall be closed.
m LAN device is not configured, the default VLAN and Ethernet priority bit shall be assigned in the HG

m LAN device is not configured, the default VLAN and Ethernet priority bit shall be assigned in the H
e assigned in the HGW-O.

e assigned in the HGW-O.