zte gpon rfp template_20150320

ZTE GPON RFP Template

For International Market


ZTE Confidential & Proprietary 1


Version Date Author Reviewer Notes

V1.0 2009/5/23 Wang

Xinsheng Not open to the Third Party

V2.00 2009/11/23 Wang

Xinsheng Not open to the Third Party

V3.00 2010/517 Yuan Ning,

Zhang Hui

Wang Xinsheng,

Dai Chi Not open to the Third Party

V3.10 2011/2/23 Yuan Ning,

Zhang Hui

Wang Xinsheng,

Dai Chi Not open to the Third Party

V3.20 2012/8/22 Qin Yewen Wang Xinsheng Not open to the Third Party




V4.2 2014/10/21 Qin Yewen

Shi Ying Wang Xinsheng Not open to the Third Party


V5.0 2014/12/17

Qin Yewen

Meng Qing

Zhu Zhenghua

Bao Yintao

Wang Xinsheng Not open to the Third Party

© 2015 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used

without the prior written permission of ZTE.

Due to update and improvement of ZTE products and technologies, information in this document is subjected to

change without notice.


2 ZTE Confidential & Proprietary

TABLE OF CONTENTS

1 General Introduction ............................................................................................ 5

1.1 Introduction ............................................................................................................. 5

1.2 Scope of the specification ....................................................................................... 5

1.3 Referred Standards ................................................................................................ 7

2 General Technical Requirements ....................................................................... 9

2.1 OLT System Specification ...................................................................................... 9

2.1.1 Transmission Requirements ................................................................................... 9

2.1.2 Physical layer ....................................................................................................... 11

2.1.3 Uplink interface ..................................................................................................... 13

2.1.4 Optical Fiber Protection Switchover Requirements .............................................. 14

2.1.5 GTC layer ............................................................................................................. 16

2.1.6 OLT - ONT/ONU interoperability .......................................................................... 16

2.1.7 Ethernet OAM ....................................................................................................... 17

2.2 ONT/ONU Specific Requirements ........................................................................ 18

2.2.1 Basic requirement for GPON ONT/ONU .............................................................. 18

2.2.2 GPON Interface Function ..................................................................................... 18

2.2.3 GPON Transmission Convergence ...................................................................... 19

2.2.4 Upstream .............................................................................................................. 20

2.2.5 Downstream ......................................................................................................... 21

3 Service Functionality Requirements ................................................................ 21

3.1 OLT Service Specific Requirements ..................................................................... 21

3.1.1 User Side Requirements of OLT .......................................................................... 21

3.1.2 Network side requirements of OLT ....................................................................... 22

3.1.3 IPv6 ...................................................................................................................... 27

3.1.4 TDM Service ......................................................................................................... 27

3.1.5 Complete Time and Clock Synchronization .......................................................... 28

3.1.6 Security ................................................................................................................. 28

3.1.7 OLT Management Requirements ......................................................................... 30

3.2 ONT/ONU Service Specific Requirements ........................................................... 35

3.2.1 Requirements of GPON ONT (FTTH) .................................................................. 35

3.2.2 Requirements of GPON ONU ............................................................................... 40

4 EMS Requirements ............................................................................................ 53

4.1 Management System Architecture ....................................................................... 53

4.2 EMS Platform Requirements ................................................................................ 53

4.3 EMS Fault and Alarm Management ..................................................................... 55

4.4 EMS Configuration Management ......................................................................... 56



4.4.1 Presentation of Equipment Configuration ............................................................. 56

4.4.2 Configuration and Release Changes .................................................................... 56

4.4.3 Software Download EMS ...................................................................................... 57

4.5 EMS Performance Management .......................................................................... 57

4.6 EMS Testing ......................................................................................................... 58

4.7 PON Detecting System ......................................................................................... 58

5 Environment and Working Requirements ....................................................... 59

5.1 Environmental Requirements ............................................................................... 59

5.1.1 Environmental Conditions Specification ............................................................... 59

5.2 Power Supply ....................................................................................................... 61

5.2.1 OLT Devices ......................................................................................................... 61

5.2.2 ONT / ONU / Servers ............................................................................................ 62

5.3 EMC Requirements .............................................................................................. 62

5.4 Safety Requirements ............................................................................................ 63

5.4.1 General safety requirements ................................................................................ 63

5.4.2 Electrical Safety Requirements ............................................................................ 64

5.4.3 Laser Safety Requirements .................................................................................. 64

5.5 Reliability and Availability Requirements .............................................................. 65

5.5.1 Maintainability ....................................................................................................... 65

5.5.2 Availability ............................................................................................................. 65

5.5.3 Reliability .............................................................................................................. 65

5.6 Installation Conditions .......................................................................................... 65

5.6.1 General requirement ............................................................................................. 65

5.6.2 Cables .................................................................................................................. 67

6 Acronyms ........................................................................................................... 67



FIGURES

Figure 1-1 GPON Network Topology ..................................................................................... 6

Figure 2-1 GPON Backbone Optical Fiber Protection Switchover Mode ............................. 14

Figure 2-2 GPON Full Optical Fiber Protection Switchover Mode ....................................... 15

TABLES

Table 3-1 FTTx MDU service cards requirement ................................................................. 45

Table 6-1 Acronyms ............................................................................................................. 67



1 General Introduction

1.1 Introduction

XXX have a key objective to enhance the level of telecommunications services and

solutions. The integrated triple-play solutions already in operation offer multimedia

services as well, although the significant growth of bandwidth demands is forecasted.

Optical systems among the new possibilities and the passive solutions, the PON networks,

in optical infrastructure will play an increasing role.

The main target of this technical specification is to functionally define the requirements of

the services for GPON network as FTTx configuration. The basic scenarios are taken into

consideration:

FTTP --- FTTH, FTTO, Fiber to subscriber’s premise

FTTN --- FTTB, FTTC, Fiber to about 1K-5K feet of subscriber’s premise; last mile is

copper-based (VDSL2)

1.2 Scope of the specification

The specification covers the requirement of the following equipment and elements:

GPON OLT

GPON ONT/ONU

Connectorized optical splitters for indoor and outdoor environment with the following

splitting ratio: 1:2; 1:4; 1:8; 1:16; 1:32; 1:64 and 1:128

Management system and principles for GPON system

Figure 1-1 shows a schematic representation of the system reference configuration.



Figure 1-1 GPON Network Topology

Legend:

ONT: Optical Network Termination

ODN: Optical Distribution Network

OLT: Optical Line Termination

WDM: Wavelength Division Multiplexing (Optional)

NE: Network Element using different Wavelengths for OLT and ONU/ONT

AF: Adaptation Function

SNI : Service Node Interface

UNI : User Interface – Network

Optical Line Termination (OLT): OLT provides an interface to PDN network side

(Optical Access Network) and sends the signal through one or more ODNs, which is

distributed to a certain number of ONU s

Optical Distribution Network (ODN): An Optical Distribution Network provides a

transmission mean between OLT and users in both transmission directions. It uses

passive optical components (optical fibers, cables, optical connectors, filters, splitters,

attenuators and splices).



Optical Network Unite (ONU): Optical Network Unit provides the user side interface of

the Optical Access Network and it is connected to ODN. All system’s ONU receives the

same signal and each one of them extracts the corresponding information according to

an access protocol. In the reverse sense (downstream), data are transmitted according

to an OLT control mechanism using TDMA (Time Division Multiple Access) protocol that

allocates a transmission time to each ONU.

Optical Network Termination (ONT): Optical Network Terminal is an UN used for the

FTTH (Fiber To The Home) architecture and includes user's port functions

1.3 Referred Standards

1. The GPON solutions offered must comply, but not limited to the following

International Standards

ITU-T G.984.1: GPON General characteristics

ITU-T G.984.2: GPON Physical Media Dependent (PMD) layer specification

ITU-T G.984.3: GPON Transmission convergence layer specification

ITU-T G.984.4: GPON ONT management and control interface specification

ITU-T G.987.1 XG-PON General requirements

ITU-T G.987.2 XG-PON Physical media dependent (PMD) layer specification

ITU-T G.987.3 XG-PON Transmission convergence (TC) specification

ITU-T G.988 ONU management and control interface (OMCI) specification

2. The proposed equipments should support IEEE 802.1ad Provider Bridges

3. The proposed equipments should support IEEE 802.1D Spanning Tree Protocol

4. The proposed equipments should support IEEE 802.1p VLAN prioritization

5. The proposed equipments should support IEEE 802.1Q VLAN tagging



6. The proposed equipments should support IEEE 802.1w Rapid Spanning Tree

Protocol of at least 8 ports, based on port-based, address-based, and round robin

7. The proposed equipments should support IEEE 802.3u 100 Mbps Fast Ethernet

8. The proposed equipments should support IEEE 802.3ad Ethernet Link Aggregation

9. The proposed equipments should support IEEE 802.3ae 10 Gigabit Ethernet

10. The proposed equipments should support IEEE 802.3z Gigabit Ethernet

11. The proposed equipments should support IEEE 802.3x Flow Control

12. The proposed equipments should support IETF RFC 2131: DHCP

13. The proposed equipments should support IETF RFC 2236: Internet Group

Management Protocol, Version 2

14. The proposed equipments should support IETF RFC 3376: Internet Group

Management Protocol, Version 3

15. The proposed equipments should support IETF RFC 3046: DHCP Relay Agent Info

Option (Option 82)

16. The proposed small-capacity OLT must have possessed of a MEF CE2.0

authentication

17. The proposed system should support SIP and H.248 for Voice providing

18. The Bidder must ensure that the compliance to any standards specified above is

kept up-to-date with the latest version available.

19. The version of hardware and software of the equipment should be provided

20. The proposed equipment must use a highly flexible, modular, scalable, and

non-blocking platform at all level/part of the design without any restriction.

21. The Bidder shall submit the detail chipset type, manufacturer, and version of the

proposed Equipment including the ONT.



22. The version of hardware and software of the equipment should be provided.

2 General Technical Requirements

2.1 OLT System Specification

2.1.1 Transmission Requirements

1. The bit rates downstream (2488, 32Mbit/s), upstream (1244,16Mbit/s) of optical

interfaces of the offered GPON system must comply with the requirements of clause

8.2.3.1 – 8.2.3.2 of ITU-T G.984.2 (03/2003) Recommendations.

2. The architecture of the offered GPON system must be single fiber.

3. The logical reach of the offered GPON system shall be minimum 60km.

4. The offered GPON system must support minimum 1:64 split ratio.

5. The physical reach of the offered GPON system must be minimum 20km.

6. The differential fiber distance of the offered GPON system must be minimum 20km.

7. The offered GPON system must support downstream security: AES conformity to

clause 12.2 of ITU-T Rec. G.984.3 (02/2004). GPON system should be able to

switch the encryption on/off

8. GPON system must be able to establish AES encryption per ONT/ONU basis

9. The size of the OLT shelf should fit in a standard 19” inch or ETSI 21” rack

10. The shelf should not be more than 10U high

11. The rack should be 300mm deep rack

12. The shelf should meet 300mm deep rack

13. The rack should not be higher than 2200mm



14. GPON system should be at least 8 ports per GPON board

15. GPON system should provides 16 ports per GPON board

16. GPON system should provides low power consumption 8/16 ports GPON board

17. GPON system should provides 8 ports per XG-PON1 board

18. GPON system should provides not less than 128/256 PON ports per shelf in ETSI

21’ rack

19. GPON system should support smoothing migration to XG-PON1

20. GPON system should support smoothing migration to NG-PON2

21. GPON system should support 160G slot bandwidth for XG-PON1

22. GPON system should support 6.4T Backplane data bus capacity

23. GPON system should support optical link and breakpoint diagnosing function.

24. GPON system should support separate control bus.

25. Switching capacity of the GPON and XG-PON1 system should be at least

2.56Tbps.

26. Main control board should support 1+1 or 1:1 protection mode

27. The GPON OLT should provide 1+1 redundancy protection with different power

supply cards.

28. OLT should provide clock (1PPS+TOD), BITS/HZ, and environment interfaces in

the same board

29. The GPON OLT should have the option to provide the P2P GE/FE interface board.

30. GPON system should provides 24/48 GE/FE ports per P2P board

31. GPON system should provides not less than 768 PON ports per shelf in ETSI 21’

rack



2.1.2 Physical layer

1. The type of the offered GPON system must support 28dB and 32 dB link budgets

according to ITU-T Rec. G.984.2 Amendment 1. (02/2006).

2. System must support GPON Class B+ and Class C+ optical budget

2.1.2.1 Downstream direction: OLT transmitter

1. Operating wavelength range: 1480 to 1500nm

2. Line code: Scrambled NRZ

3. Mask of the transmitter eye diagram: Figure 2/G.984.2

4. Minimum ORL of ODN at Olu and Old: 32dB

5. Main launched power: min. +1,5dBm

6. Main launched power: max. +5dBm

7. Extinction ratio: min. 10dB

2.1.2.2 Downstream direction: ONT/ONU Receiver

1. Maximum reflectance of equipment, measured at receiver wavelength: -20dB

2. Minimum sensitivity: -27dBm (Bit error ratio <1x10-10)

3. Minimum overload: -8dBm (Bit error ratio <1x10-10)

4. Consecutive identical digit immunity: > 72bit

5. Jitter tolerance: Figure 5/G.984.2

6. Tolerance to the reflected optical power: Less than min. receiver sensitivity -10dB

2.1.2.3 Upstream direction: ONT/ONU Transmitter

1. Operating wavelength: 1260nm to 1360nm



2. Line code: Scrambled NRZ

3. Mask of the transmitter eye diagram: Figure 3/ITU-T Rec.G.984.2 (03/2003)

4. Maximum reflectance of equipment, measured at transmitter wavelength: Less than

min. launched power - 6dB

5. Minimum ORL of ODN at Oru and Ord: 32dB

6. Main launched power: min.+0,5dBm

7. Main launched power: max. +5dBm

8. Launched optical power in case of without optical input signal: Less than min.

receiver sensitivity -10dB.

9. Extinction ratio: min. 10dB

10. Jitter transfer: Figure 4/G.984.2 see clause 8.2.8.9.1 of ITU-T Rec.G.984.2

(03/2003).

11. Jitter generation from 4.0 kHz to 10.0 kHz: 0.33UIpp.

2.1.2.4 Upstream direction: OLT Receiver

1. Equipment, measured at receiver wavelength: - 26dB

2. Minimum sensitivity: -28dBm (Bit error ratio <1x10-10)

3. Minimum overload: -8dBm (Bit error ratio <1x10-10)

4. Consecutive identical digit immunity: > 72bit

5. Tolerance to the reflected optical power: Less than min. receiver sensitivity -10dB



2.1.3 Uplink interface

2.1.3.1 Optical Gigabit Ethernet

1. The offered GPON system must support 1000Base-LX (Long Wavelength Laser)

and 1000Base-SX (Short Wavelength Laser) optical uplink interfaces corresponding

to the provisions of Chapter 38 of the Standards IEEE 802.3 2005.

2. The GE interface must be interchangeable SFP module.

3. The uplink card support mixed plug, uplink card shall separate with control switch

card.

4. The bidder shall give the number of pieces of interfaces implemented on one unit

(card).

5. The optical modules insert on the uplink port should be an oblique type.

2.1.3.2 10 GbE

1. The offered GPON system must support 10GBase-LR (1310nm, LAN PHY) optical

uplink interface. The parameters of the 10 GbE interfaces of the offered equipment

shall comply with the parameters corresponding to the provisions of Chapter 52 of

the Standards IEEE 802.3 2005.

2. The 10 GbE optical interface must be SFP+ module.

3. The offered GPON system must have 10GBase-LR optical uplink interface.

4. The offered GPON system must have 10GBase-ER optical uplink interface.

5. GPON system uplink cards should support at least 8*10GE uplink interfaces in the

case of full user slots were configured.

2.1.3.3 E1

1. The offered GPON system must support E1 Standards ITU-T G.703



2. 16/32 E1 ports per board are needed.

2.1.3.4 STM-1/STM/4

1. The offered GPON system must support STM-1/STM-4 Standards ITU-T G.707

2. STM-N card should support mixed plug in.

2.1.4 Optical Fiber Protection Switchover Requirements

The GPON system can adopt the optical fiber protection switchover mechanism to

improve the network reliability and viability. The optical fiber protection switchover can be

implemented in the following two modes:

1. Automatic switchover: It is triggered by faults, including signal loss or signal

deterioration.

2. Forced switchover: It is triggered by management events.

2.1.4.1 Types

There are mainly two types of optical fiber protection switchover: backbone optical fiber

protection switchover (TYPE B) and full optical fiber protection switchover (TYPE C), as

shown in Figure 2-1 and Figure 2-2 respectively:

Figure 2-1 GPON Backbone Optical Fiber Protection Switchover Mode



Figure 2-2 GPON Full Optical Fiber Protection Switchover Mode

1. The offered GPON system must support LACP for uplink protection.

2. The offered GPON system must support MSTP for uplink protection.

3. The offered GPON system must support G.8032 for ring protection.

2.1.4.2 Criteria

In the GPON system, the optical fiber protection switchover must be implemented in one

of the following condition:

1. Input optical signal loss (LOS)

2. Input channel deterioration

Too high or too low input optical signal power

BER exceeding the threshold

Other conditions to be specified

2.1.4.3 Protection Time

When the GPON system implements optical fiber protection switch over, the optical

channel protection time is recommended to be as follows:

1. The TYPE B fiber protection: The service interruption is no longer than 100ms.



2. The TYPE C Full fiber protection: The service interruption period is no longer than

50ms.

3. The Uplink card protection: switchover time of 1+1 mode must no longer than

200ms.

2.1.5 GTC layer

1. The offered GPON system must support GPON Encapsulation Method (GEM)

mapping conformity to clauses 8.1 … 8.3 of ITU-T Rec.G.984.3 (02/2004).

2. The offered GPON system shall support optical leveling conformity clause 8.3.2. of

ITU-T Rec. G.984.2 (03/2003).

3. The offered GPON system must support Dynamic Bandwidth Assignment (DBA)

payload processing conformity to clauses 7.7, 8.4 of ITU-T Rec.G.984.3 (02/2004).

4. The offered GPON system shall support DBA Type: SR-DBA and NSR-DBA. The

minimum bandwidth allocation granularity shall be no more than 64kbit/s.

5. The offered GPON system shall support FEC functionalities conformity to clause 13

of ITU-T Rec.G.984.3 (02/2004).

6. The activation procedure in the ONT/ONU must comply with clause 10.2 of ITU-T

Rec.G.984.3 (02/2004).

2.1.6 OLT - ONT/ONU interoperability

（Use for the scenario that requires the IOT, if has no requirement, delete this

chapter）

1. The inviter of this RFQ intends to open the optical interface in order to achieve

interoperability between OLT and ONT of different vendors. To ensure the required

interoperability between multiple OLT and/or ONT the bidder must commit to open

the GPON interface (incl. OMCI) and to share this information with other selected

vendors.



2. The bidder shall provide information of already tested interoperability between

GPON systems of the vendors invited to this RFQ.

2.1.7 Ethernet OAM

1. GPON system should support Ethernet OAM functionalities conform to IEEE

802.1ag, ITU-T Y.1731 and IEEE 802.3 Section 57.

2. GPON system should support creation of Maintenance Assosiations (MA) and

Maintenance Domains (MD).

3. GPON system should support configuration of the OAM level of MDs.

4. GPON system should support creation of MEP and MIP.

5. GPON system should support Continuity check (CCM) and Frame Delay

Measurement (DM) functions.

6. GPON system should support Loopback (LB) and Link trace (LT) functions.

7. GPON system should support configuration of Multicast MAC address.

8. GPON system should provide tc configuration of the following variables for

Continuity Check (CC):

The Continuity Check (CC) frequency

9. GPON system should provide tc configuration of the following variables for Frame

Delay Measurement (DM):

The frequency of sending DM frames (time between DM frames)

P bits in VLAN tag for frames carry DM messages



2.2 ONT/ONU Specific Requirements

2.2.1 Basic requirement for GPON ONT/ONU

1. The ONT/ONU is fully comply with ITU-T G.984.1~G.984.4.

2. The chipset for ONT/ONU must be SoC(System-on-a-Chip) designed and

manufactured by main stream broadband chipset Tenderer (like Broadcom, Marvell

and Lantiq, etc.)

3. Specify if the ONU support line card Flexible plug in and pull out, and specify the

number of slots that ONU have.

4. Specify if the ONT have the design of fiber coil.

5. Specify if the ONT have the design of fiber hiding.

2.2.2 GPON Interface Function

Describe the following characteristics.

1. The number of GPON interface

2. The number of T-CONT

3. The number of GEM Port

4. FEC decoding

5. DBA reporting in status indications in the PLOu, and by piggyback reports in the

DBRu

6. The maximum transmit distance

7. Transmission Wavelength

8. Support dying gasp function



2.2.3 GPON Transmission Convergence

1. The ONT/ONU supports a GTC that is composed by a "Framing Sublayer" and an

"Adaptation Sublayer" in conformance with ITU-T G.984.3.

2. The ONT/ONU realizes the mapping of GEM frames into GTC payload (and

inversely extracts GEM frames from GTC payload) in conformance with ITU-T

G.984.3.

3. The ONT/ONU realizes the mapping of Ethernet frames into GEM frames (and

inversely extracts Ethernet frames from GEM frames) in conformance with ITU-T

G.984.3.

4. The ONT/ONU is able to send frames according to a static allocation provisioned at

the OLT.

5. The ONT/ONU supports the Non Status Reporting mode in conformance with ITU-T

G.984.3.

6. The ONT/ONU is able to provide the information to the DBA function at the OLT in

order to optimize bandwidth allocation between ONUs when needed.

7. The ONT/ONU supports the Status Reporting mode in conformance with ITU-T

G.984.3.

8. The ONT/ONU supports DBRu mode 0 in conformance with ITU-T G.984.3.

9. The ONT/ONU implements the principle of T-CONT (identified by "Alloc-ID") as the

basic control unit for upstream direction in conformance with ITU-T G.984.3.

10. Option 1: Single T-CONT per ONU

The ONT/ONU is able to support a single T-CONT.

11. Option 2: Multiple T-CONTs per ONU

The ONT/ONU is able to support up to 4 T-CONTs i.e. 1 T-CONT per CoS.

12. The ONT/ONU can support 8 T-CONTs (Alloc-IDs).



13. The ONT/ONU can support 32 GEM-Ports (Port-IDs).

14. The ONT/ONU supports several ways for GEM-Ports mapping into T-CONTs as

following.

15. All GEM ports are mapped into the same T-CONT.

16. Each GEM port is mapped into a single T-CONT.

17. It can be supported that all GEM ports corresponding to CoS1, CoS2 or CoS3 are

mapped into the same T-CONT, but each GEM port corresponding to CoS4 is

mapped into a single T-CONT.

18. The ONT/ONU is able to use the activation Discovered SN method in conformance

with ITU-T G.984.3.

19. The ONT/ONU is able to use the activation Configured SN method in conformance

with ITU-T G.984.3.

20. The ONT/ONU uses the encryption system (128 bits AES) and the Key Exchange

mechanism in conformance with ITU-T G.984.3.

21. The ONT/ONU implements an "embedded OAM channel", a "PLOAM channel" and

an "OMCI channel" in conformance with ITU-T G.984.4.

2.2.4 Upstream

1. Nominal line rate:

The ONT/ONU supports a 1.244 Gbps line rate

2. Optical performances

The ONT/ONU supports Class B+ (Optical budget, source type, transmitter range,

mean launched power min, mean launched power max, extinction ratio…) as

defined in ITU-T G.984.2 Amd1



2.2.5 Downstream

1. Nominal line rate:

The ONT/ONU supports a 2.488 Gbps line rate

2. Optical performances:

The ONT/ONU supports Class B+ (Optical budget, receiver type, maximum

reflectance, BER, minimum sensitivity…) as defined in ITU-T G.984.2 Amd1

3 Service Functionality Requirements

3.1 OLT Service Specific Requirements

3.1.1 User Side Requirements of OLT

3.1.1.1 GPON Layer

1. GEM Port IDs must be assigned automatically (default) and manually by the OLT.

2. A GEM Port must identify one or more traffic flows of a specific class of service

going to a specific U interface on a specific ONT/ONU.

3. Support service flow and GEM PORT mapping

3.1.1.2 Traffic management and QoS

1. The GPON OLT must be able to prioritize traffic based on service VLAN in the

downstream direction.

2. The GPON OLT must provide traffic shaping on per service basis in downstream

direction.

3. The GPON OLT must be able to prioritize traffic based on service VLAN forwarding

to the uplink interface.



4. The GPON OLT must support at least 4 queues per interface (including GPON

ports and Ethernet uplink interfaces), one per traffic class.

5. The GPON OLT must support at least 4 traffic classes for Ethernet frames, and

shall support configurable mapping to these classes from the 8 possible values of

the Ethernet priority field.

6. The GPON OLT must support strict priority queuing (SP).

7. The GPON OLT should support Weighted Round Robin (WRR).

8. The GPON OLT should support combined queuing (strict for the highest queue and

weighted to the other queues).

9. The GPON system must support traffic shaping in both directions

10. The bidder should provide information about traffic limit; minimum rate limit step,

available rate limit values, is limitation on L2 or L3 packets

11. The GPON OLT must support Hierarchical QoS.

12. The GPON OLT should support the controllable bandwidth accuracy not more

than±1%.

3.1.2 Network side requirements of OLT

3.1.2.1 Functionality

1. The Ethernet interfaces must conform to IEEE 802.1q VLAN trunking standard.

2. The Ethernet interfaces should provide double-tagged VLAN capabilities conform to

IEEE 802.1ad standard.

3. GPON OLT must support defining of 802.1p priority at VLAN level.

4. If the equipment has more than one Ethernet uplink interface, the interfaces must

support link aggregation according to IEEE 802.3ad standard.

5. The Ethernet interface should support Ethernet frame MTU at least 9000 Bytes.



3.1.2.2 VLAN Considerations

1. GPON OLT must support mapping of user VLANs of a given GPON port to different

service VLANs.

2. Corresponding to the guidelines of DSL Forum TR-101, GPON OLT must support

simultaneously the following mappings of User VLANs and Service VLANs:

Mapping multiple User VLANs (of same or different GPON ports) to a single

Service VLAN,

Mapping multiple (m) User VLANs (of same or different GPON ports) to

multiple (n) Service VLANs, where m=n and n≥1.

(Remark: A given User VLAN shall not be bound to more than one Service VLAN.)

3. The GPON OLT must be able to translate the VLAN tag received from customer to

the Service VLAN tag in the upstream direction.

4. The GPON OLT must be able to translate the Service VLAN tag to User VLAN tag

in the downstream direction.

5. The GPON OLT must support untagged frames received from the customer and

must be able to add the Service VLAN tag in the upstream direction.

6. The GPON OLT must be able to detach the Service VLAN tag and forward

untagged frames in downstream direction in case of single tagged frame.

7. The GPON OLT must be able to accept both tagged and untagged frames from the

customer and must attach the service VLAN tag to the frames.

8. The GPON OLT should support selective QinQ (double stacking) encapsulation

Ethernet frames received from the customer should be dropped, forwarded without

change of the VLAN field, forwarded with QinQ encapsulation or forwarded with

translated VLAN field based on configuration.

9. The GPON OLT must conform to N:1 VLAN forwarding defined in TR-101 of DSL

Forum.



3.1.2.3 Multicast Considerations

1. IGMPv2 operation must be in conformance to RFC2236.

2. IGMPv3 operation should be in conformance to RFC3376.

3. GPON OLT must support IGMP snooping function.

4. GPON OLT must support IGMP proxy function.

5. GPON OLT should support configurable filtering of IGMP Membership Report

messages.

6. The GPON OLT must support dropping of all IGMP messages received on a

subscriber port.

7. The GPON OLT must support an IGMP v2 (IGMP v3) transparent snooping function.

This feature shall be configurable on a per VLAN basis.

8. The GPON OLT must support IGMP immediate leave (Fast Leave) as part of the

IGMP function.

9. The GPON OLT must support IGMP join delay below 50ms.

10. The GPON OLT should be able to configure per GPON port the maximum number

of simultaneous multicast channels allowed.

11. GPON OLT must support the Globally Scoped Multicast Addresses (224.0.1.0 –

238.255.255.255).

12. GPON OLT must support the Limited Scoped Multicast Addresses (239.0.0.0/8).

13. The GPON OLT must support a mechanism to prevent a user port from becoming a

multicast router port by blocking IGMP query messages.

14. The GPON OLT must support mechanisms to stop user ports injecting unauthorized

multicast traffic into the aggregation network.

15. The GPON OLT must be able to rate limit the number of IGMP messages per user

port.



16. Multicast packets transported between RG (Routing Gateway) and GPON OLT is

using IPoE encapsulation.

17. The desired goal is to support multicast optimization by controlling the flooding of

Ethernet multicast frames making use of IGMP agents in intermediate (L2) devices

(e.g. GPON OLT, Ethernet aggregation).

18. N:1 VLANs forwarding mode should be used in order allow efficient forwarding of

multicast traffic. (It is to be noted that other types of traffic (data, voice, unicast video)

could be delivered via N:1 VLANs as well.)

19. Dedicated Multicast VLAN model should be supported. (This is a model where a

dedicated N:1 VLAN is used to send some multicast groups from a multicast router /

BNG to one or several access nodes (GPON OLT), over an aggregation network.

Other traffic is sent across different VLANs, where these VLANs could be 1:1 or

N:1.)

20. Integrated Multicast VLAN model should be supported. (This is a model where

multicast traffic is inserted into one of the N:1 VLANs that are terminated at a

subscriber GPON port, or alternatively dot1q trunked to the RG. This effectively

means multicast and unicast share a VLAN.)

21. GPON OLT should support 8K multicast groups, and support 1K multicast groups

per PON port.

3.1.2.4 Access Methods

1. GPON OLT must support PPPoE connection methods.

2. GPON OLT must support DHCP connection methods.

3. GPON OLT must support filtering options in order to prevent L2 traffic between

customers connected to the same GPON OLT considering PPPoE and DHCP

environment (Intra-GPON filtering).

4. GPON OLT should support filtering options in order to prevent L2 traffic between

customers connected to different GPON OLTs considering PPPoE and DHCP

environment (Inter-GPON filtering) considering N:1 VLAN forwarding.



5. Intra-GPON and Inter-GPON filters of the GPON OLT must be capable to be

disabled partly or entirely on VLAN basis.

6. The OLT shall support ONU MAC address authentication based on PON port and

ONU logic identification authentication and their hybrid mode. The ONU logic

identification mode is the best choice. To authenticate the ONU legality, the OLT

shall refuse the illegal ONU access. It shall support to enable and disable the

function, and reduce the bad effect caused by ONU’s continual authentication trial.

In consideration of construction convenience, the ONU should have a certain

chances of authentication trial.

3.1.2.5 Additional Functional Requirements

1. GPON OLT must support configurable Ethertype filter for upstream direction.

2. The bidder should provide the MAC address capacity in their documents.

3. GPON OLT should support configurable Destination MAC (single address or a

range) filter in upstream direction.

4. GPON OLT should support configurable Source MAC (single address or a range)

filter in upstream direction.

5. GPON OLT must support configurable Broadcast (blocking/enabling) filter for


6. GPON OLT must support configurable Multicast (enabling, disabling, and prefix

specific enabling) filter for upstream direction.

7. GPON OLT must be able to store at least K*8 MAC addresses, where "K=Maximum

number of GPON-ports multiplied by the maximum splitting ration supported by

GPON ports".

8. In order to prevent source MAC flooding attacks the GPON OLT must be able to

limit the number of source MAC addresses learned from a user VLAN

9. MAC addresses learning on the Network Side Ethernet interface should be

configurable per Service VLAN (enable/disable) if implemented



10. GPON OLT must support Virtual MAC address and MAT (MAC Address

Translation).

11. Virtual MAC address and MAT must be configurable (enable/disable).

12. GPON OLT must support L2 marking (802.1p) of the traffic coming from the User

VLANs.

13. Binding management traffic to a dedicated VLAN must be provided.

3.1.3 IPv6

1. The OLT shall support an option to migrate to IPv6 without any hardware upgrade

2. OLT should support IPv6 SW upgrade, although IPv4 will be used in the initial

phase of the implementation

3. The GPON OLT MUST support IPv6 and IPv4 dual stack function.

3.1.4 TDM Service

1. When the GPON system bears E1 dedicated line service, it shall adopt MEF TDM

over Ethernet or IETF PWE3 mode in compliant with MEF’s MEF8 or IETF

RFC3985 (2005), RFC4197 (2005) specifications. It configures its encapsulation

mode by the OLT local NM to be MEF8, RFC4553 (SATOP mode) or

Draft-left-pwe3-cesopn-02.txt (CESOPSN) mode).

2. The GPON system born TDM service shall adopt self-adaptive clock recovery mode.

That’s to recover the clock through the clock stamp in the packet.

3. To ensure the interoperability requirements based on TDM service, the OLT

equipment shall respectively set the adopted standard, the encapsulated E1

numbers, the corresponding CESOP IP address, MAC address, VLAN, etc.

4. The OLT equipment to bear the TDM service shall support TDM (E1) service

transparent transmission, STM-1/STM-4 protection. The bidder shall elaborate the

STM-1/STM-4 protection mechanism and performance, and provide the application

instances in the existing network.



5. TDM service process in OLT system only in less 3 boards

3.1.5 Complete Time and Clock Synchronization

The system shall support the following functions to implement time and clock

synchronization to provide flexible and various time synchronization modes for the

operators and to meet the networking and service requirements for movable backhaul,

etc:

1. BITS input and output

2. 1PPS + TOD

3. IEEE 1588 V2

4. Synchronization Ethernet

3.1.6 Security

1. Please describe PON security features. Both logical and physical security should be

addressed.

2. The proposed Equipment must be equipped with the security features to prevent

malicious DOS attack to the network and to other users.

3. The proposed Equipment must support broadcast suppression per VLAN.

4. L2 and L3 ACL should be supported on your OLT

5. Support MAC and IP Address Anti Spoofing

6. Support MAC and IP Address binding

7. Support Anti ICMP/IP Attacking

8. The proposed Equipment should support the IP address filtering function. Details

explanation shall be given on how the user traffic is permitted and denied based on

source and/or destination IP addresses.



9. The proposed Equipment must support the Ethernet MAC address filtering function.

10. The proposed Equipment must support the following, but not limited to:

IP anti-spoofing

DHCP snooping

11. Support MAC address registration capability to limit the number of MAC address per

port that can access that port

12. Prevention of IP/MAC Spoofing for DHCP user s Prevention of MAC spoofing for

PPPOE users

13. Limited MAC address based on the traffic stream

14. Static MAC address configuration based on the traffic stream

15. IP address binding based on the traffic stream\

16. MAC address filtering on the user side

17. Support unknown unicast packet suppression

18. Support broadcast packet suppression

19. DHCP Source Guard based on MAC and IP

20. Support downstream 128-bit advantage encryption standard (AEC) encryption

21. Support remote device management through Telnet

22. Support remote service configuration and device management through OMCI

23. Black List and White List for IP Address Segment is configurable

24. Ethernet uplink protection, Support LACP, MSTP and G.8032 for protection

25. Support STM-1, STM-4 uplink interface protection



3.1.6.1 IP Address

1. Support user ports source IP binding

2. Support DHCP Snooping

3. Support IP source guard

4. Support anti DHCP spoofing

3.1.6.2 Anti DOS-Attacking

1. Support anti ARP attacking

2. Support ARP Relay Agent

3. Support ARP Proxy

4. Support anti ICMP/IP attacking

3.1.7 OLT Management Requirements

3.1.7.1 General Requirements

1. Please describe the NE level :

Alarm management

Provisioning

Performance detecting

Troubleshooting

Inventory

Backup & restore

Software upgrade



Security (access right)

2. The interface description of the equipment and the SNMP MIBs, NBI (TL1, XML),

API description of NB interface and other types of interfaces must be submitted.

3. The NEs must have inband management interface

4. The NEs shall have out of band management interface.

5. The NEs must have command line terminal access capability for initial

configurations and debug purposes.

6. The NEs must have different user levels like read only, operator, system

administrator

7. The NEs command line capability must cover the complete range of management

features and functions.

8. The NEs must store all configuration parameters non-volatile, and must run in

service without any management system connection.

3.1.7.2 NE Interfaces

1. The NE shall have a SNMPv3 for management.

2. The proposed equipment shall have a command line IF via remote SSH access for

NE management.

3. Please describe the management interfaces of the proposed equipment.

4. The NE shall provide north-bound interface. Its protocol is in TL1, XML, FTP modes,

preferably TL1 mode.

5. For all the offered NE an alarm, fault and performance interface must be proposed.

6. For all the offered NE an inventory interface must be proposed.

7. For all the offered NE provisioning interface must be proposed.

8. For all the offered NE testing interface shall be proposed.



3.1.7.3 NE Fault and Alarm Management (FM)

1. The NEs of the offered system must be able to send alarm information to an existing

“consolidated event management system” via SNMP (GET-Request and Trap)

2. The NEs of the offered system shall be able to send alarm information to an existing

“consolidated event management system” via syslog interface for real-time alarm

management.

3. Supplier must hand over the list of the equipment events and alarms and their

severity.

4. Please describe the FM (event and alarm management) features, functions and

operation of the proposed equipments.

5. The NE must support ability of sending messages in form of SNMP Traps to at least

two specified destination. It's necessary to list all supported messages and MIBs.

3.1.7.4 NE Configuration Management (CM)

1. The NEs of the offered system shall be able to be configured or managed via

SNMPv3 for any wanted changes eg. Configuration for operation of the network

elements, adaptation to planned operational modifications or user requirements.

2. All the parameters and settings of the proposed NEs must be configurable remotely

(without any local assistance).

3. It shall be possible to query the position of cards and interfaces via SNMP

(Entity-MIB, RFC4133).

4. It shall be possible to query the type, own serial number and state of equipment

interfaces via SNMP (Entity-MIB, RFC4133).

5. It shall be possible to query free resources (ports, cards, interfaces, positions) via

SNMP (Entity-MIB, RFC4133).



6. It shall be possible to query all the equipment status parameters (e.g.

node/card/port/interface; subscriber service parameters; connections; ) via SNMP

(IF-MIB, RFC2863; Entity-MIB, RFC4133).

7. It must be possible to query all the equipment status parameters (e.g.

node/card/port/interface; subscriber service parameters; connections ;) via SSH.

8. The NE id (serial number) reported by the NE and printed on the surface of the NE

must be identical (both in semantics and syntactic).

9. It shall be possible to change the configuration in the equipment with remote

process via SNMP.

10. Supplier must hand over the list of the possible equipment configuration

parameters.

11. It must be possible to upload the configuration parameters from equipment.

12. It must be possible to download the configuration parameters to the equipment.

13. The configuration fails shall be detected and the changes shall be refused.

14. It shall be possible to restore the previous good configuration in all NE.

15. It shall be possible to reset the previous good configuration in all NE.

16. It must be possible to change the software releases in the equipment with remote

processes via SNMP or CLI.

17. The date of change shall be stored in the equipment.

18. It must be possible to read the software version(s) from equipment via SNMP or

CLI.

19. It must be possible to download the appropriate software/firmware to equipment.

20. The download fails shall be detected and the changes shall be refused. The NE

shall continue to work with the old software. The fail cause shall be reported to the

Management system.



21. It shall be possible to restore the previous good software release in all managed

equipment.

22. It shall be possible to reset the previous good software release in all managed

equipment.

3.1.7.5 NE Performance Management (PM)

1. The NEs must provide performance data via SNMP, Telnet.

2. The NEs shall provide performance data via TL1 interface

3. The NE must provide traffic counter for both the incoming and outgoing traffic on all

the possible interfaces (on the OLT as well as on the ONT).

4. Supplier must hand over the list of the retrievable performance data of the proposed

equipment.

3.1.7.6 Local Craft Terminal/LCT

1. Local Terminal (LCT) must be supplied for NE management.

2. LCT must be able to manage each type of the offered equipment.

3. The same LCT and unified interface shall be provided to connect to the different

type of equipment. Comment: 10/100BaseT Ethernet with R-J45 plug as unified

interface is proposed.

4. The access priority to the equipment from the LCT shall be higher than from the

EMS.

5. The LCT access shall operate independent from the EMS access.

6. Each configuration change carried out through the LCT must automatically be

synchronized with the EMS.

7. The LCT access to the equipment shall be reported to the EMS.



8. The LCT must provide for configuring the default settings (default VLAN, IP address,

etc.).

3.2 ONT/ONU Service Specific Requirements

3.2.1 Requirements of GPON ONT (FTTH)

3.2.1.1 Requirement of GPON ONT type

GPON ONT should support user interfaces as following:

10/100/1000Base-T Ethernet interfaces with RJ-45 connector

POTS interfaces with RJ-11 connector

USB host interface, 2.0 standard

Wi-Fi

RF overlay

3.2.1.2 Uplink interface

1. GPON uplink: SC/APC interface for fiber connection.

2. Fully compliant to ITU-T G.984.x GPON standards

3.2.1.3 Access protocols

1. GPON ONT must support bridging of 802.1q tagged Ethernet frames between its

LAN and WAN interfaces.

2. GPON ONT must support bridging PPPoE over the encapsulated Ethernet as

defined in IETF RFC 2516 and support up 4 PPPoE sessions.

3. GPON ONT must be able to bridge IP over Ethernet.



4. GPON ONT must support oversized Ethernet frames at least 1934 bytes.

5. The ONT must support bridged Ethernet and routed Ethernet

6. The ONT must support DHCP client

7. The ONT must support NAT/NATP

8. The ONT must support DNS

3.2.1.4 Traffic management and QoS

1. The ONT must support mapping traffic into individual GEM Ports based on user port

/ VLAN priority bits / VLAN ID in the upstream direction.

2. In the downstream direction, the ONT must support at least 4 queues per user

facing port, one per traffic class.

3. In the upstream direction, the ONT must support at least 4 user queues, one per

traffic class

4. The ONT must support scheduling of user queues according to strict priority among

at least 4 queues.

5. The ONT must support at least 4 network facing T-CONTs, one per traffic class.

6. The ONT should support all 5 defined T-Cont types.

3.2.1.5 Multicast support

1. The ONT should support dropping of all IGMP messages received on a user port

and/or VLAN.

2. The ONT must support IGMPv2 snooping or proxy function.

3. The ONT must support IGMP immediate leave as part of the IGMP transparent

snooping function.

4. The ONT must support IGMP join delay below 20ms.



5. The ONT MUST support IGMP explicit host tracking as part of the IGMP

transparent snooping function

3.2.1.6 LAN (UNI) Interface

1. The ONT supports at least one, to four 10/100/1000M interfaces in conformance

with IEEE 802.3z, with RJ45 connectors.

2. The Ethernet UNI(s) support(s) by default auto-negotiation of speed and duplex

mode.

3. For each Ethernet UNI, it is possible to configure manually duplex mode as half or

full.

4. The ONT supports Auto MDI / MDI-X feature.

5. For each Ethernet UNI, the ONT supports "Flow Control" (in conformance with IEEE

802.3 Annex 31B) with PAUSE functionality1

3.2.1.7 Voice (UNI) Interface

1. The ONT supports at least one, to two POTS interfaces with RJ11 connectors.

2. Protocol: SIP/H.248

3. The following codecs should be supported: G.711 A-law, µ-law, G.723, G.722.

4. Shall offer fax operation according to ITU-T recommendation T.38.

3.2.1.8 USB(UNI) Interface

1. The ONT supports at least one USB host interface in conformance with USB2.0

standard.

2. Support 3G dongle

3. Support file sharing and print server



4. Support USB fast recovery and profile quick backup

3.2.1.9 Wi-Fi (UNI) Interface

1. Support 802.11a, 802.11b, 802.11g and 802.11n.

2. Support 2*2 MIMO

3. Support 4 SSIDs

4. Each SSID can be allocated for home network connection, WEB portal for public

hot-spot access exclusively, each scenario can bundle with one WAN.

5. The ONT should support Wireless security features:

i. WEP encryption (64bit/128bit)

ii. MAC based access control list

Wireless Access Control (SSID)

Option for closed (hidden) SSID must be available

Wi-Fi Protected access (WPA2) compatible

Pre-shared Key

Remote management

3.2.1.10 RF Overlay

(Depends on the ONU type features)

1. The ONT shall comply with ITU-T Recommendation G.984.5

2. The enhancement band used for video shall be according with option 3 of G.984.5

Recommendation, from 1550nm to 1560nm

3. The ONT shall comply with ITU-T Recommendation J.186



4. The ONT shall be able to convert optical signals with modulation format is Intensity

Modulation (IM) in FDM analogue AM-VSB and/or digital video signals.

5. The RF connector shall be 75ohms F connector

6. RF level at the F connector: maximum 17 dBmV/ch

7. RF Passband: 47 MHz~870 MHz

8. Flatness : -1~1dB

3.2.1.11 Management requirements

1. ONT must be manageable through Network Element manager of OLT

2. The possibility for Local management for ONT (PON part), it must be disabled.

3. Management of GPON ONU should based on OMCI or OMCI+TR-069

4. The equipment must have dying gasp functionality.

3.2.1.12 IPV6

1. The ONT shall support an option to migrate to IPv6 without any hardware upgrade

2. Support IPv4/v6 Dual Stack

3. Support DS-Lite

3.2.1.13 Security

1. Support AES security mechanism defined in G.984.3.

2. The ONT should support verification by SN、 password、 SN+password

3. ONT should has built-in capability for management, including management,

detecting, and maintenance.



4. Standard compliant OMCI (the embedded operations channel) interface as defined

by ITU-T G.984.4 and G.983.2

5. Alarming and AVC report, performance detecting

6. Remotely software image download over OMCI, as well as activation and rebooting

3.2.1.14 Power supply

1. Rated 12V DC (through the external AC/DC adapter)

3.2.1.15 Other requirements

1. All physical ports (POTS and GE) shall have a link integrity indicator LED (one for

each port).

2. The equipment shall have a reset button, in order to reset the equipment

configuration to the default factory settings. The reset button may be labeled as

"reset" so a help desk can more easily identify it to a user.

3.2.2 Requirements of GPON ONU

3.2.2.1 General Service requirement

3.2.2.1.1 Traffic management and QoS

1. GPON ONU should support service traffic classification:

Classifies the upstream service traffic based on physical ports, source MAC

address, destination MAC address, VLAN ID, VLAN priority (IEEE 802.1p),

Ethernet type (such as IP, PPPoE, ARP/RARP), destination IP address,

source IP address, IP protocol type (TCP, UDP, ICMP, IGMP), IP DSCP,

TCP/UDP protocol port, and implements in-depth packets detection (the first

128 bytes).

It should support the mapping relations between 802.1p priority and services.



2. GPON ONU should support service traffic Marking:

Priority marking of the upstream services based on the traffic classification

Reusing, adding, modification of 802.1p user priority marking

Modification of ToS/DSCP priority marking

Configuring the service priority marking of each user port

3. GPON ONU should support queue scheduling:

Mapping upstream/downstream services to queues with different priority

based on 802.1Q user priority marking, and scheduling the queues

Scheduling the upstream services locally according to the OLT bandwidth

authorization, PON port supporting 8 queues

SP/WRR/SP+WRR scheduling algorithm.

Supporting network side/user side queues 8/8

4. GPON ONU should support Tail-Drop and WRED algorithm.

5. GPON ONU should support status reporting DBA, schedules the upstream service

traffic according to the DBA authority of the OLT to limit the upstream service traffic

rate.

6. The Ethernet interface at the user side supports rate limit of the upstream and

downstream service port.

3.2.2.1.2 VLAN considerations

1. GPON ONU must support VLAN protocols:

IEEE 802.1q VLAN with the Q-VLAN ranging from 1 to 4094

IEEE 802.1ad VLAN Stacking, with the C-VLAN ID and S-VLAN ID ranging

from 1 to 4094



VLAN definition and application in TR-101 of Broadband Forum

2. GPON ONU must support VLAN translation list:

The system configures a VLAN translation list for the specific VLAN membership list.

The VLAN translation list configures possible translation for each VID in the VLAN

membership list as follows:

Translation and counter-translation between Q-VID and S-VID

Translation and counter-translation between Q-VID and C-VID

Translation and counter-translation between Q-VID and C-VID/S-VID pair

3. GPON ONU must be able to translate the VLAN tag received from customer to the

Service VLAN tag in the upstream direction.

4. GPON ONU must be able to translate the Service VLAN tag to User VLAN tag in the


5. GPON ONU must support untagged frames received from the customer and must

be able to add the Service VLAN tag in the upstream direction.

6. The GPON ONU must be able to detach the Service VLAN tag and forward

untagged frames in downstream direction in case of single tagged frame.

7. The GPON ONU must be able to accept both tagged and untagged frames from the

customer and must attach the service VLAN tag to the frames.

3.2.2.1.3 Multicast support

1. IGMPv2 operation must be in conformance to RFC2236

2. GPON ONU must support IGMP immediate or fast leave (<10ms).

3. Detection of IGMP messages on Layer 2 or Layer 3 at the ONU.

4. GPON ONU should support configurable filtering of IGMP membership reports



5. GPON ONU should be able to configure per user port the maximum number of

simultaneous multicast channels allowed.

6. GPON ONU must be able to rate limit the number of group records per second per

user port.

7. The "rate limit" function should be configurable.

3.2.2.1.4 Security

1. Specify if the ONU supports the AES security mechanism defined in G.984.3.

2. The ONU should support verification by SN、 password、 SN+password

3. ONU should has built-in capability for management, including management,

detecting, and maintenance.

4. Standard compliant OMCI (the embedded operations channel) interface as defined

by ITU-T G.984.4 and G.983.2

5. Alarming and AVC report, performance detecting

6. Remotely software image download over OMCI, as well as activation and rebooting

3.2.2.2 Requirements of GPON ONU in FTTB/C

3.2.2.2.1 System Architecture requirement

1. The Tender must describe the general architecture and functional block diagram of

the proposed GPON ONU, which used as MDU (Multi-Dwelling Unit) equipment in

FTTB/C scenario.

2. The Tender must indicate which buses are dedicated and which are shared by

different parts of the MDU as well as the bandwidth.

3. Software roll-back to the old version shall be supported in case of update failure.



4. Please indicate the number of MDU slots. Please breakdown into slots for

subscriber's cards, network cards, etc.

3.2.2.2.2 Module and capacity

1. The proposed system should be 5U or less height and can be plug into 19 inch

standard rack.

2. The proposed system should be in general consist of the following service interface

and all service line card can be mixed plugged in the same shelf:

ADSL2+ interface

VDSL2 interface

SHDSL interface

SHDSL.bis interface

VoIP interface

ISDN PRI and BRI interface

FE and GE interface

3. The proposed system should be in general consist of the following network

interface:

FE electric and optical

GE electric and optical

GPON uplink

4. ADSL2+ line card recommended to be per-card 32 port and splitter-embedded line

card is preferred

5. VDSL2+ line card recommended to be per-card 32 and above port and

splitter-embedded line card is preferred



6. SHDSL line card recommended to be per-card 24 port

7. ISDN PRI line card recommended to be 4 port

8. ISDN BRI line card recommended to be 8 port

9. VoIP line card recommended to be 64 port

10. The Tender should state the capacity figures of the system, if the proposed

equipment include several types, For each type, please fill the table respectively :

Table 3-1 FTTx MDU service cards requirement

Description

Max Quantity of

cards Per

System

Quantity of ports

Per card

ADSL2+

VDSL2

POTS

FE

SHDSL

ISDN(BRI)

ISDN(PRI)

GE uplink

FE uplink

GPON uplink

11. The backplane capacity of MDU should be more than 20G

12. The switching capacity of MDU should be more than 10G

3.2.2.2.3 VoIP service

1. MDU should support built-in VoIP management module.

2. MDU should support single IP and dual IP mechanism for VOIP

3. MDU should support H.248 protocol: Version1 / Version2 / Version3.



4. MDU should support SIP; it is in compliance with IETF RFC 3435.

5. MDU should support Voice signal coding and encoding:

MDU supports G.711 (A/U).

MDU supports G.729A/B.

MDU supports G.723.1.

3.2.2.2.4 Ethernet (UNI) interface

1. The ONU Ethernet interfaces must support Auto-MDI(X) functionality.

2. The connector must be RJ45 female and shall conform to IEC 60603-7 standard.




5. The Ethernet interfaces must conform to IEEE 802.1p standard.

6. GPON ONU must support defining of 802.1p priority at VLAN level.

7. The Ethernet interface must support oversized Ethernet frames at least 1526 byte.

3.2.2.2.5 Power supply

1 MDU should support power supply mode: AC (220V), DC (-48V), AC (220V) +DC

(-48V).

DC rated voltage -48 V with the range of -40 VDC to -57 VDC

AC rated voltage 110 VAC/220 VAC with the range of 88 VAC to 290 VAC



3.2.2.3 Requirements of GPON ONU in FTTM



the proposed GPON ONU, which used as CBU (Cellular Basic Unit) equipment in

FTTM scenario.


3. CBU should support Type C protection.


1. The proposed system should be 2U height and can be plug into 19 inch standard

rack.

2. The proposed system should be in general consist of the following UNI: FE

interface/E1 interface

3.2.2.3.3 SyncE Service

1. SyncE specifications and requirements are bounded by four primary standards:

ITU-T G.8261: Timing and synchronization aspects in packet network

ITU-T G.8262: Timing characteristics of Synchronous Ethernet equipment

slave clock

ITU-T G.8264: Distribution of timing through packet networks

ITU-T G.781: Synchronization layer functions

2. Synchronous clocking support should be provided when the device is operating in

the following modes: 1000BASE-T, 1000BASE-X, 100BASE-TX, or 100BASE-FX

on the line interface.



3. There should be two components to synchronous clocking support. The first is to

output a recovered clock. The second is to select between the local reference clock

and a cleaned up recovered clock.

3.2.2.3.4 Time & Clock synchronization

1. GPON ONU should support two 1PPS+TOD ports and two 1PPS ports.

2. GPON ONU should support 1588V2.

3. GPON ONU should fulfill the requirements of all kinds of mobile base stations.

3.2.2.3.5 E1 emulation service and E1 (UNI) Interface

1. GPON ONU should support the built-in E1 emulation processing module to

implement E1 emulation on the L2 Ethernet/IP/MPLS network.

2. GPON ONU should support the E1/T1 emulation service protocols as follows:

MEF 8.0 protocol: TDMoIP over MPLS.

IETF RFC4553 protocol: SAToP over IP or MPLS.

IETF RFC5086 protocol: CESoPSN over IP or MPLS

3. Specify the kind of connector and the impedance (75 Ohm or 120 Ohm) used for the

E1s

4. Specify if the interface it’s configurable as unframed (G.703) or framed (G.704)

5. Support no less than 8* E1 ports.

6. Specify if the E1 has transparent clock (adaptive mode) or if it works as

Master/Slave.

7. Specify the different types of loop back supported for maintenance and

troubleshooting




1. CBU should support power supply as:



2. CBU should support LiFePO4 battery for power backup when AC fails.

Support AC power supply and -48V DC power backup

Support -48V DC power supply and -48V DC power backup.

3.2.2.4 Requirements of GPON ONU in FTTW



the proposed GPON ONU, which used as MDU (Multi-Dwelling Unit) equipment in

FTTW scenario.




rack.

2. The proposed system should be in general consisting of UNI interface: 8/16

10/100/1000Base-T with RJ45 interface.

3.2.2.4.3 Ethernet Power Supply

1. GPON ONU in FTTW scenario should support built-in PoE/PoE+ processing

module and complies with standard PSE specified in PoE/PoE+ protocol.



2. GPON ONU in FTTW should support PoE management function, all the functions

listed below can be queried through CLI/TELNET/SNMP. POE management

function includes the following

Port control management function

PoE/PoE+ working mode setting

Standard and non-standard PD detection

Interconnection with Cisco special PD devices

Enabling and disabling of port power output

Power management mode (dynamic) setting

Whether to disconnect power supply of the port on controlling the soft resetting

of the device

Remote PD resetting

Port protection and alarm function

Over-current protection for the ports and generating alarms in case of

over-current

Over-voltage protection for the ports and generating alarms in case of

over-voltage

Over-temperature protection for the whole device and generating alarms in

case of over-temperature with configurable threshold value

Under-voltage protection of the ports and generating alarms in case of

under-voltage

Abnormal logs of each port

Abnormal power down notification of the port

Port status querying



Querying the power, voltage, current of each PoE/PoE+ port

Querying the working status of each PoE/PoE+ port

Collecting the total current, voltage and power of the all PoE/PoE+ ports of the

overall device

Querying the working temperature of the PoE/PoE+ module

3. Ethernet interfaces with POE/POE+ function should be Gigabit Ethernet interface.

3.2.2.4.4 Ethernet (UNI) interface

1. The ONU Ethernet interfaces must support Auto-MDI(X) functionality.

2. The connector must be RJ45 female and shall conform to IEC 60603-7 standard.




5. The Ethernet interfaces must conform to IEEE 802.1p standard.

6. GPON ONU must support defining of 802.1p priority at VLAN level.

7. The Ethernet interface must support oversized Ethernet frames at least 1526 byte.


1. MDU should support power supply as:



2. MDU should support LiFePO4 battery for power backup when AC fails.

Support AC power supply and – 48V DC power backup



3.2.2.5 Requirements of GPON ONU in FTTO


1. The Tenderer must describe the general architecture and functional block diagram

of the proposed GPON ONU, which used as MDU (Multi-Dwelling Unit) equipment

in FTTO scenario.


3. Please indicate the number of MDU slots. Please breakdown into slots for

subscriber's cards, network cards, etc.



rack.

2. The proposed system should be in general consist of following UNI interface:

E1 interfaces

10/100Base-T interfaces.

3.2.2.5.3 E1 emulation service and E1 (UNI) Interface

1. GPON ONU should support the built-in E1 emulation processing module to

implement E1 emulation on the L2 Ethernet/IP/MPLS network.

2. GPON ONU should support the E1/T1 emulation service protocols as follows:

MEF 8.0 protocol: TDMoIP over MPLS.

IETF RFC4553 protocol: SAToP over IP or MPLS.

IETF RFC5086 protocol: CESoPSN over IP or MPLS



3. Specify the kind of connector and the impedance (75 Ohm or 120 Ohm) used for the

E1s

4. Specify if the interface it’s configurable as unframed (G.703) or framed (G.704)

5. Support minimum 8* E1 ports per board.


1. MDU should support power supply as:



2. MDU should support LiFePO4 battery for power backup when AC fails.

Support AC power supply and – 48V DC power backup

4 EMS Requirements

4.1 Management System Architecture

Pleased describe the quoted EMS and all the technical limitations related to the

proposed hardware and software configuration

4.2 EMS Platform Requirements

1. High reliability and platform redundancy solution shall be offered.

2. The Supplier must support a 1:1 EMS redundancy architecture in which the Primary

(Active) and Secondary (Standby) EMS are geographically distributed.

3. With 1:1 EMS redundancy architecture, please explain the method through which

the EMS Primary and EMS Secondary database synchronization will be maintained.



4. With 1:1 EMS redundancy architecture, please explain the method by which the

switchover occurs from the EMS Primary to the EMS Secondary.

5. The proposed EMS must provide multi-user access.

6. The proposed EMS must have different user levels like read only, operator, and

system administrator - with different access rights.

7. The proposed EMS must provide concurrent EMS access.

8. The proposed EMS shall support concurrent NE access.

9. The proposed EMS shall have a client server architecture.

10. A single instance of the EMS must support at least 50 users/ session

simultaneously.

11. The data communication solution between the EMS and the NE must be IP.

12. Management System shall have open API(s) that supports:

Fault Management,

Performance Management,

Configuration Management,

Inventory Management,

Security Management

13. Management System servers must be 19" rack mountable. It is necessary to

provide standard racks and rack mount kits for servers.

14. The interface modules towards higher order management and support systems

shall be installed on Management System. API interfaces shall be implemented

using standard protocols, e.g. TL1 or SNMP.

15. Provide change request mechanism and procedures

16. The EMS shall support an option to migrate to IPv6 without any hardware upgrade



17. EMS should support IPv6 SW upgrade, although IPv4 will be used in the initial

phase of the implementation

4.3 EMS Fault and Alarm Management

1. The proposed EMS must provide for fault and alarm management.

2. Please describe the FM (event and alarm management) features, functions and

operation of the proposed equipments.

3. Each alarm with its accompanied attributes, forming an alarm record, shall be

logged automatically. Alarm records shall be kept in the log for some time (e.g. 30

days) and alarm retrieval shall be supported. The same presentation, filter and

sorting functions shall be available for retrieved alarm records as they are for actual

alarms.

4. All other events such as Alarm Acknowledgement, Alarm Severity setting, and

Alarm Collection allow/inhibit or Threshold settings shall be also logged.

5. The report generation tool shall be available for Event Log records using filter

capabilities. Event Logging presentation shall allow the user to manage and analyze

the Event Log records.

6. The event collection processes shall run continuously according to user defined

characteristic, even if all users are logged out.

7. It shall be possible to archive any log file both manually and automatically.

8. It shall be possible to retrieve any log file manually.

9. It shall be possible to set archiving parameters including delete criteria by the

administrator.



4.4 EMS Configuration Management

4.4.1 Presentation of Equipment Configuration

1. It must be possible to query the position of cards and interfaces via the SNMP

Interface.

2. It must be possible to query the type, own serial number and state of equipment and

the type and state of the interfaces.

3. It shall be possible to query free resources (ports, cards, interfaces, positions).

4. It must be possible to query all the equipment status parameters (e.g.

node/card/port/interface; subscriber service parameters; connections).

5. The NE id (serial number) reported by the NE and printed on the surface of the NE

must be identical (both in semantics and syntactic).

4.4.2 Configuration and Release Changes

1. It must be possible to change the configuration in the equipment.

2. It must be possible to upload the configuration parameters of the equipment.

(backup function)

3. It must be possible to download the configuration parameters to the equipment.

(restore function)



Management system.

5. It must be possible to restore the previous good configuration in all NE.

6. It must be possible to reset the previous good configuration in all NE.



4.4.3 Software Download EMS

1. It must be possible to change the software releases in the equipment.

2. The date of change shall be stored and sent as a trap to the Management system.

3. It must be possible to read the software version(s) from equipment via SNMP.

4. It must be possible to download the appropriate software/firmware to equipment.



Management system.

6. It must be possible to restore the previous good software release in all managed

equipment.

7. It must be possible to reset and the previous good software release in all managed

equipment.

4.5 EMS Performance Management

1. The EMS must provide equipment level performance information.

2. The EMS must provide traffic counter for both the incoming and outgoing traffic on

all possible interfaces (on the OLT as well as on the ONT). These counters must be

available in the NE.

3. The Management System shall provide data collection, processing and

presentation capabilities required to perform performance management (PM) on

various NEs and services.

4. Supplier must hand over the list of the supported performance information,

parameters of the proposed EMS and NE. Information shall be easy readable,

printable and exportable to other systems.



4.6 EMS Testing

1. The EMS shall provide functions for performing equipment level testing.

2. The EMS shall perform test functions for the optical and DSL performance of the

GPON network.

3. The EMS shall provide functions for activating and deactivating temporary

loop-back connections.

4.7 PON Detecting System

1. PON detecting System is collection of software and hardware equipments capable

to detect and provide statistics and alarms for the PON.

2. The system must provide the following functionalities:

3. Detect and locate any fault along the fiber optic cable (fault management)

4. Detect FO deterioration (pro-active maintenance)

5. Continuous detecting of FO network (real-time detecting)

6. Precise notification of any network problem automatically, without user intervention

7. System interoperability:

Capability of sending alarms over a standard interface (SNMP) to another

management system

8. Alarm management

9. Multi-user capability



5 Environment and Working Requirements

5.1 Environmental Requirements

5.1.1 Environmental Conditions Specification

5.1.1.1 Operating

1. OLT:

The equipment are supposed to be placed at normal living or working areas shall

comply with the Standard ETSI EN 300 019-1-3 Class 3.1. (Temperature-controlled

locations) which is a combination of classes 3K3/3Z2/3Z4/3B1/3C2(3C1)/3S2/3M1

of the Standard EN 60721-3-3.

Specified temperature limits: +5....+40 °C

Relative humidity: 5....85 %

2. The proposed connectorized optical splitters (splitting ratio: 1:2; 1:4; 1:8; 1:16; 1:32

and 1:64) must have the environment conditions:

Operating Temperature (C) = -40 to +85 °C

Operating humidity ≤ 95% and frozen-free

Air pressure = 70 KPa to 106 KPa

3. We kindly ask you to specify for each proposed connectorized optical splitters the

following data:

Operating Temperature °C"

Stationary operating temperature limits

4. For outdoor ONUs:



The equipment is supposed to be placed at garages, cellars, entrances and

staircases of buildings.

Temperature limits: -40 °C....+65 °C

Relative humidity: 10 %....95 %

5. For indoor ONUs:

Temperature limits: 0 °C....+40 °C

Acoustic noise emission limits: Daytime 50dBA, Night-Time 35dBA"

6. LED status indication is supported for power, PON link status and UNI status.

7. The indoor ONU is mounted either inside building or placed (stand alone) on a desk.

8. The ONU can be equipped with maintenance-free backup battery that will operate

the system in case of AC failure as an option.

5.1.1.2 Environmental Protection Requirements

1. The bidder must make a declaration that the offered equipments not contain

components, materials and fittings that cause negative environmental impact during

transportation, storage installation or operation.

2. The equipment must be provided in accordance with the Directive 2002/95/EC of

the European Parliament and of the Council on the restriction of the use of certain

hazardous substances in electrical and electronic equipment (RoHS).

3. The bidder shall give a list for wrapping materials. Only recycling materials shall be

used for wrapping.

4. In case if the bidder (manufacturer) of the equipment has a certificate of EN ISO

14001 or other environmental management system, a copy of the certificate shall be

attached to the Bid.



5.2 Power Supply

5.2.1 OLT Devices

1. The power supply interface of the equipment supplied with 48 V nominal DC must

satisfy the requirements stipulated in the Standard ETSI EN 300 132-2. (The

positive side should be grounded.)

2. The bidder shall attach the test report of the power supply interface according to the

ETSI EN 300-132-2 to prove that all the equipment meet the above requirements.

3. After returning to normal supply voltage, the telecommunication equipment must

continue normal operation, WITHOUT any external intervention (e.g. reset,

administrator command).

4. The bidder should declare whether the equipment complies the European “Code of

Conduct on Energy Consumption of Broadband Equipment”. The energy

consumption is measured and compared according to ETSI TS 102 533 (2008-05).

5. Supplier must give the power consumption of the equipment relevant to all modes of

operation.

6. All powering components of the equipment should be redundant. The switch

between the redundant powering components SHALL be automatic and cause no

disruption of service.

7. The equipment should be protected against inversion of the polarity of the power

supply. Similarly, the power connector of the equipment shall be construed in a way

that it is provided against inversion of the polarity.

8. The equipment must have remote management (remote checking feature) which

will inform the operator about discrepancies at the internal power supply.

9. The power supply unit of the equipment (including the remote feeding circuits) shall

have a protection against overload and thermal runaway of the lead acid battery.



10. The normal service voltage must be within the range: -48 V ± 20%. The equipment

must operate at a voltage within this range.

11. The bidder shall specify the maximum power consumption for the OLT

12. The bidder shall describe the maximum overall power consumption of the OLT

equipment in full configuration with dual main control cards + dual power supply +

fan + dual 4GE uplink + GPON card.

13. GPON OLT should support 1+1 power supply redundancy protection.

5.2.2 ONT / ONU / Servers

1. Provide details of heat dissipation information for the ONT/ONU/Servers

2. Vendors should also provide LiFePO4 battery for power backup.

3. Specify if the ONT/ONU Support POE (Power over Ethernet) and what is the

capability?

4. The power supply interface of the equipment supplied with 230 V nominal AC must

satisfy the requirements stipulated in the Standard ETSI ETS 300 132-1 or ETSI

EN 300 132-3.

5. Power supply: nominal voltage 90~230 V AC, 50Hz and Continental European plug.

6. The equipments shall be tolerant of power fluctuations 230 VAC +15%, -25% @ 50

Hz ±0.1%, continuing to operate normally and maintaining its configuration after

these events.

7. Specify if the ONU support power saving mode for idle interface, and how?

8. Does the version or model support 120VAC powering?

5.3 EMC Requirements

1. In case of the RF emission the equipment must satisfy the class "B" limit of the EN

55022.



2. The bidder must attach the Statement of Compliance (according to the Directive

2004/108/EC) to the Bid.

3. The equipment must comply with the ITU-T recommendations K.20/K.21.

4. The bidder must attach the EMC Test Report to prove that all the equipment meet

the above requirements, or shall hand the EMC Test Report over to the Technical

Conformance Tests.

5.4 Safety Requirements

5.4.1 General safety requirements

1. The equipments, its sub-systems and accessories must comply with the general

life- and material safety requirements.

2. The bidder must guarantee that precautions must be taken in order to prevent any

injuries or damages due to the following hazards according to standard EN 60950-1,

2.0 Ed.:

Electric shock,

Energy hazards,

Fire,

Mechanical or heat hazards,

Radiation hazards,

Chemical hazards.

3. Only equipment must be allowed for installation that comply with the relevant

requirements in safety Standards (compliance evaluation procedure: according to

Directive 2006/95/EC and Directive 1999/5/EC of the European Parliament and of

the Council of 9 March 1999 on radio equipment and telecommunications terminal

equipment and the mutual recognition of their conformity ). The safety test reports of



the exchange and subscriber side units (the power supply of the subscriber’s unit if

exits too) according to EN 60950 must be attached to the bid.

4. Markings and/or identity labels shall be placed on the equipments and on their

subsystems. The labels have to be placed on a visible place and should contain

durably the following information:

Type and manufacturer’s name, equipments release,

Power supply data,

Classes of equipment - protection against electric shock (at class II. equipment

the symbol, too),

CE marking.

5. All the delivered materials and equipments shall be free of defects (such as sharp

edges, burrs etc) that could represent a safety hazard to personnel involved in its

assembly, installation, use or maintenance.

5.4.2 Electrical Safety Requirements

1. With respect to electrical safety, the equipments and its power supply (if exists)

must comply with specifications in Standard EN 60950-1.

2. The system of protection against electric shock, requirements for earthing and

equipotential bonding shall be established according to EN 60950-1, 2.0 Ed., and

ETSI EN 300 253 series of standards.

3. The degree of protection of the equipment, depending on their placing shall be

established according to specifications described in standard EN 60529.

5.4.3 Laser Safety Requirements

1. Product must be in line with EN60825-1 standard; Safety of Laser products

2. According to Standards ISO 3864-1 and ISO 3864-2 should be used on equipment

parts and housings where laser beam exist.



5.5 Reliability and Availability Requirements

5.5.1 Maintainability

1. GPON OLT and ONT equipment shall operate 24 hours a day, and every day of the

year. GPON OLT equipment shall be designed to meet an operational lifetime over

10 years with normal parts replacement.

2. The bidder is obliged to ensure spare parts for offered platform for at least 10 year

period

5.5.2 Availability

Availability of the GPON OLT and ONU equipment shall be annually 99.99% for all nodes

5.5.3 Reliability

1. MTBF of the GPON equipment used in the system should be more than 28 years.

2. GPON PON cards MTBF min. = 30 years,

3. The MTTR of OLT should not be more than 30 minutes

4. The bidder must show evidence to demonstrate that the predicted

availability/reliability of the proposed equipment is better than 99.999%.

5. The bidder must state the maximum environmental operating temperature of the

fully equipped OLT in order to provide an availability/reliability of better than

99.999%.

5.6 Installation Conditions

5.6.1 General requirement

1. Installation, operation and maintenance shall not require the use of special,

non-standard tools.



2. All necessary materials for the installation shall be provided within the ONT, ONU,

OLT Kits

3. The Bid shall be made for:

19" with ETSI adapters rack-mountable OLT

19" with ETSI adapters rack-mountable ONU

Desktop and wall-mountable ONT.

4. Installation materials shall be quoted for each OLT based on the following

assumptions

All patch-cord lengths for OLT shall be of 20m;

5. The ODF is assumed as SC/PC type for quotation purpose

Power and grounding cables for OLT shall be of 30m for quotation purpose

The actual values of installation materials will be determine on site-survey for each

OLT site; the site-survey data will be provided

6. The proposed connectorized optical splitters (splitting ratio: 1:2; 1:4; 1:8; 1:16; 1:32

and 1:64) for indoor locations shall be 19" rack-able.

7. The connectorized optical splitters installation must assure the eyes protection and

easy cabling.

8. Each connectorized optical splitters shall have clear identification marks

9. The outer cover of the offered unit(s) shall be resisting to mechanical damaging

impacts that may occur during implementation/installation and operation.

10. The outer cover of the offered units should meet the requirements of Flammability

Class V-1 according to Standard EN 60950-1, 2.0 Ed..

11. The structural design (construction) of the offered equipment and the materials

chosen shall not cause injury to persons, or damage, or deterioration to objects, if

properly used. The technical characteristics of the basic components used shall



comply with the requirements undertaken in or deriving from the technical

specifications of the product.

5.6.2 Cables

1. The proposal shall include all the required tie cables from VDSL2 interfaces to the

MDF.

2. The bidder shall offer quotation for the following tie cables lengths:

5m

10m

20m

6 Acronyms

Table 6-1 Acronyms

Acronym Expansions

CP Communications Provider

DoS Denial of Service (hacker attack)

EMS Element Management System

FSAN Full Service Access Network

FTTB Fiber To The Building typically basement or communications

room.

FTTC Fiber to the Cabinet , also known as Fiber to the Curb, Fiber to

the Node.

FTTH Fiber To The Home

GA General Availability

GEA Generic Ethernet Access

GEPON Gigabit Ethernet Passive Optical Network [IEEE/ITU-T]

GPON Gigabit Passive Optical Network [FSAN/ITU-T]

IEEE Institute of Electronic and Electrical Engineers [USA]



Acronym Expansions

ISP Internet Service Provider

ITU-T International Telecommunication Union - Telecommunications

Standardization Sector

MDU Multiple Dwelling Unit

MSAN Multi-Service Access Node

OF Optical Fiber

OFCOM OFfice of COMmunications [UK regulator]

OLT Optical Line Termination

ONT Optical Network Termination

OOB Out of Band

OSS Operational Support System

PON Passive Optical Network

POTS Plain Old Telephony Service (Analogue Telephony)

SIP Session Initiation Protocol

SME Small Medium Enterprise

SoR Statement Of Requirements

T&D Test and Diagnostics

TDM Time Division Multiplexing

TSR Telecommunications Strategic Review

USO Universal Service Obligation

VLAN Virtual Local Area Network

WDM Wavelength Division Multiplexing

zte gpon rfp template_20150320

Documents

qin yewen wang xinsheng

party v4

party v3

zhang hui wang xinsheng

zte corporation

party v5

party v2

proprietary information