Module
V800R010C00
Feature Description
Issue 01
Date 2011-10-30
Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129
People's Republic of China Website: http://www.huawei.com
About This Document
Intended Audience
This document describes the key features (including ADSL,VDSL2, SHDSL, GPON, VoIP, ISDN, FoIP, MoIP, P2P Access, Layer 2 Protocol Handling, Layer 3 Features, VLAN, ACL, QoS, Multicast and security features) of the SmartAX MA5600T/MA5603T (hereinafter referred to as the MA5600T/MA5603T) in detail from the following aspects:
l Definition l Purpose l Specification l Availability l Principle l Reference
After reading this document, you can learn about the definitions and purposes of the various features of the MA5600T/MA5603T, and also the support of these features by the MA5600T/ MA5603T and the references on these features. In this way, you can know the feature list of the MA5600T/MA5603T and understand the implementation of these features on the MA5600T/ MA5603T.
This document is intended for: l Network planning engineers l System maintenance engineers l Configuration engineers l NM administrators
Symbol Conventions
The following symbols may be found in this document. They are defined as follows
Symbol Description
Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury.
Module
Symbol Description
Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save your time.
Provides additional information to emphasize or supplement important points of the main text.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Updates in Issue 01 (2011-10-30)
This is the first release of V800R010C00. Compared with issue 01 (2011-07-15) of V800R009C00, this issue has the following changes:
The following information is added:
l 12 IPv6
l 20.8 ONT DHCP Simulation
l 14.8 Type C Protection of GPON Lines
l 7 MPLS
The following information is modified:
l Updated the specifications of 4 VDSL2 Access, 1 GPON, and 13 Multicast.
l Modified the content of 9.3 1:1 VMAC, 21.3 Ethernet CFM OAM, and 9.8 Bridging. l Modified the structure and the content of 17.9 Service Overload Control.
Module
Contents
About This Document...ii
1 GPON...1
1.1 Introduction...2
1.2 Specifications...2
1.3 Reference Standards and Protocols...4
1.4 Availability...4
1.5 Overview of the GPON System...5
1.6 GPON Principle...7
1.7 Key GPON Technologies...13
1.8 GPON Terminal Authentication and Management...16
1.9 Continuous-Mode ONU Detection...25
1.10 GPON Network Applications...28
1.11 Glossary, Acronyms, and Abbreviations...29
2 P2P Optical Access...30
2.1 P2P FE Optical Access...31
2.1.1 Introduction...31
2.1.2 Specifications...31
2.1.3 Reference Standards and Protocols...31
2.1.4 Availability...31
2.1.5 Principle...32
2.2 GE P2P Optical Access...33
2.2.1 Introduction...33
2.2.2 Specifications...36
2.2.3 Reference Standards and Protocols...40
2.2.4 Availability...40 2.2.5 Network Applications...41
3 ADSL2+ Access...44
3.1 Introduction...45 3.2 Specifications...45 3.3 Reference...46 3.4 Availability...46 3.5 Principle...46 Module3.6 Glossary, Acronyms, and Abbreviations...53
4 VDSL2 Access...55
4.1 Introduction...56
4.2 Specifications...56
4.3 Reference Standards and Protocols...57
4.4 Availability...57
4.5 VDSL2 Architecture...58
4.6 Features of the VDSL2 System...60
4.7 Support for Multiple Spectrum Profiles...61
4.8 Flexible PSD Control Methods...63
4.9 Improvement of Line Performance...66
4.10 VDSL2 Network Applications...73
5 SHDSL Access...75
5.1 ATM SHDSL Access...76 5.1.1 Introduction...76 5.1.2 Specifications...76 5.1.3 Availability...77 5.1.4 Reference...77 5.1.5 Principle...775.1.6 Acronyms and Abbreviations...79
5.2 EFM SHDSL Access...79 5.2.1 Introduction...79 5.2.2 Specifications...80 5.2.3 Availability...80 5.2.4 Reference...81 5.2.5 Principle...81
5.2.6 Glossary, Acronyms, and Abbreviations...83
5.3 TDM SHDSL Feature...83
5.3.1 Introduction...83
5.3.2 Specifications...84
5.3.3 Reference Standards and Protocols...85
5.3.4 Availability...85
5.3.5 Principle...86
5.3.6 Narrowband Data Private Line Service Applications...87
5.3.7 PRA Carrying Applications...89
5.3.8 Glossary, Acronyms, and Abbreviations...90
6 ATM Access...92
6.1 Introduction...93
6.2 Specifications...94
6.3 Reference Standards and Protocols...94
6.4 Availability...94
Module
6.5 Principle...95
7 MPLS...97
7.1 Overview...98
7.2 Reference Standards and Protocols...98
7.3 Availability...100 7.4 MPLS...100 7.4.1 Introduction...101 7.4.2 Specifications...101 7.4.3 Principle...102 7.5 MPLS RSVP-TE...108 7.5.1 Introduction...108 7.5.2 Specifications...109 7.5.3 Principle...109 7.6 MPLS OAM...111 7.6.1 Introduction...111 7.6.2 Specifications...112 7.6.3 Principle...112
7.7 Glossary, Acronyms, and Abbreviations...114
8 Layer 2 VPN...120
8.1 PWE3...121
8.1.1 Introduction...121
8.1.2 Specifications...121
8.1.3 Reference Standards and Protocols...123
8.1.4 Availability...123
8.1.5 Enhanced Feature...123
8.1.6 Principle...124
8.1.6.1 Basic Principle of PWE3...124
8.1.6.2 Principle of TDM PWE3...130
8.1.6.3 ATM PWE3 Principle...135
8.1.6.4 Principle of ETH PWE3...141
8.1.6.5 Traffic Label Principle...143
8.1.6.6 PW Redundancy...144
8.1.6.7 PW OAM (VCCV)...145
8.1.7 Network Applications...148
8.1.8 Glossary, Acronyms, and Abbreviations...150
8.2 Native TDM...152 8.2.1 Introduction...152 8.2.2 Specifications...152 8.2.3 Reference...152 8.2.4 Availability...153 8.2.5 Principle...153
8.3 Glossary, Acronyms, and Abbreviations...155
Module
9 Layer 2 Protocol Handling...157
9.1 Overview...158
9.2 MAC Address Management...158
9.2.1 Introduction...158 9.2.2 Specifications...159 9.2.3 Availability...160 9.2.4 Principle...160 9.3 1:1 VMAC...161 9.3.1 Introduction...161 9.3.2 Specifications...162 9.3.3 Availability...162 9.3.4 Feature Enhancement...163 9.3.5 Principle...163
9.3.6 Glossary, Acronyms, and Abbreviations...167
9.4 N:1 VMAC...168 9.4.1 Introduction...168 9.4.2 Specifications...169 9.4.3 Availability...169 9.4.4 Principle...170 9.5 VLAN Management...172 9.5.1 VLAN Overview...172 9.5.2 Specifications...173
9.5.3 Reference Standards and Protocols...173
9.5.4 Availability...173
9.5.5 Types of VLAN...174
9.5.6 VLAN Attribute...176
9.5.7 VLAN Processing...178
9.5.8 VLAN Aggregation...179
9.5.9 Special Applications of VLANs...180
9.6 VLAN Switching Policy...180
9.6.1 Introduction...180
9.6.2 Specifications...181
9.6.3 Availability...181
9.6.4 VLAN Tag Transforming of Traffic Streams...181
9.7 Forwarding Policy...192 9.7.1 Introduction...192 9.7.2 Specifications...193 9.7.3 Availability...193 9.7.4 Principle...194 9.8 Bridging...195 9.8.1 Introduction...195 9.8.2 Specifications...196 Module
9.8.3 Reference Standards and Protocols...196
9.8.4 Availability...196
9.8.5 Principle...197
9.9 Glossary, Acronyms, and Abbreviations...200
10 QoS...202
10.1 QoS Processing...203 10.2 Traffic Classification...204 10.2.1 Overview...204 10.2.2 Specifications...205 10.2.3 Availability...207 10.2.4 Principle...207 10.3 Priority Processing...208 10.3.1 Overview...208 10.3.2 Specifications...208 10.3.3 Availability...209 10.3.4 Principle...210 10.4 Traffic Policing...212 10.4.1 Overview...212 10.4.2 Specifications...213 10.4.3 Availability...21310.4.4 Traffic Policing Principle...213
10.4.5 DBA Principle...216 10.5 ACL Policy...217 10.5.1 Introduction...218 10.5.2 Specifications...218 10.5.3 Availability...219 10.5.4 Principle...220
10.6 Congestion Avoidance and Management...222
10.6.1 Overview...222
10.6.2 Specifications...222
10.6.3 Availability...222
10.6.4 Congestion Avoidance Principle...223
10.6.5 Congestion Management Principle...224
10.7 HQoS...227
10.7.1 Overview...227
10.7.2 Specifications...228
10.7.3 Reference Standards and Protocols...228
10.7.4 Availability...228
10.7.5 Principle of Priority-based HQoS...228
10.7.6 Principle of HQoS Based on CAR Group...230
10.8 QoS Network Application...235
10.8.1 Typical QoS Application in an FTTH/P2P Network...235
Module
10.8.2 Typical QoS Application in an FTTB/FTTC Network...237
10.9 Glossary, Acronyms, and Abbreviations...238
11 Layer 3 Features...241
11.1 ARP...242
11.1.1 Introduction...242
11.1.2 Specifications...242
11.1.3 Reference Standards and Protocols...242
11.1.4 Availability...242
11.1.5 Principle...243
11.2 ARP Proxy...244
11.2.1 Introduction...244
11.2.2 Specifications...244
11.2.3 Reference Standards and Protocols...244
11.2.4 Availability...244
11.2.5 Principle...245
11.3 DHCP Relay...246
11.3.1 Introduction...246
11.3.2 Specifications...246
11.3.3 Reference Standards and Protocols...247
11.3.4 Availability...247
11.3.5 DHCPv4 Layer 2 Relay Principle...248
11.3.6 DHCPv4 Layer 3 Relay Principle...248
11.3.7 Networking Application...249
11.4 DHCP Proxy...250
11.4.1 Introduction...250
11.4.2 Specifications...251
11.4.3 Reference Standards and Protocols...251
11.4.4 Availability...251 11.4.5 Principle...251 11.5 IP-aware Bridge...255 11.5.1 Introduction...255 11.5.2 Specifications...255 11.5.3 Availability...255 11.5.4 Principle...256 11.6 VRRP Snooping...260 11.6.1 Introduction...260 11.6.2 Specifications...261
11.6.3 Reference Standards and Protocols...261
11.6.4 Availability...261
11.6.5 Principle...262
11.6.6 Glossary, Acronyms, and Abbreviations...264
11.7 Routing...265
Module
11.7.1 Introduction...265
11.7.2 Reference Standards and Protocols...265
11.7.3 Availability...265
11.7.4 Specifications...266
11.7.5 Principle...266
11.7.6 Static Route...271
11.7.6.1 Introduction to Static Routes...271
11.7.6.2 Specifications...271
11.7.6.3 References...271
11.7.6.4 Components of Static Routes...271
11.7.6.5 Applications of Static Routes...272
11.7.6.6 BFD for Static Routes...274
11.7.6.7 Terms and Abbreviations...274
11.7.7 RIP...275 11.7.7.1 Introduction to RIP...275 11.7.7.2 Specifications...275 11.7.7.3 References...275 11.7.7.4 RIP-1...276 11.7.7.5 RIP-2...276 11.7.7.6 Timer...277 11.7.7.7 Split Horizon...277 11.7.7.8 Poison Reverse...278 11.7.7.9 Triggered Update...278 11.7.7.10 Route Aggregation...279
11.7.7.11 Multi-process and Multi-instance...280
11.7.7.12 Hot Backup...280
11.7.7.13 Terms and Abbreviations...280
11.7.8 IS-IS...281
11.7.8.1 Introduction to IS-IS...281
11.7.8.2 Specifications...281
11.7.8.3 References...281
11.7.8.4 Basic Concepts of IS-IS...283
11.7.8.5 IS-IS Multi-instance and Multi-process...300
11.7.8.6 IS-IS Route Leaking...300
11.7.8.7 IS-IS Fast Convergence...302
11.7.8.8 Priority-based IS-IS Convergence...303
11.7.8.9 IS-IS LSP Fragment Extension...303
11.7.8.10 IS-IS Administrative Tag...306
11.7.8.11 Dynamic Hostname Exchange Mechanism...307
11.7.8.12 IS-IS HA...308
11.7.8.13 IS-IS 3-Way Handshake...309
11.7.8.14 IS-IS GR...309
Module
11.7.8.15 IS-IS Wide Metric...317
11.7.8.16 BFD for IS-IS...318
11.7.8.17 IS-IS Authentication...321
11.7.8.18 Terms and Abbreviations...323
11.7.9 OSPF...325 11.7.9.1 Introduction to OSPF...325 11.7.9.2 Specifications...326 11.7.9.3 References...326 11.7.9.4 Fundamentals of OSPF...327 11.7.9.5 OSPF GR...338 11.7.9.6 OSPF NSSA...341 11.7.9.7 BFD for OSPF...342 11.7.9.8 OSPF Smart-discover...344 11.7.9.9 OSPF-BGP Association...344
11.7.9.10 OSPF Database Overflow...345
11.7.9.11 OSPF Fast Convergence...346
11.7.9.12 OSPF Mesh-Group...348
11.7.9.13 Priority-based OSPF Convergence...350
11.7.9.14 Terms and Abbreviations...350
11.7.10 BGP...350 11.7.10.1 Introduction to BGP...350 11.7.10.2 Specifications...352 11.7.10.3 References...352 11.7.10.4 Basic Principle of BGP...353 11.7.10.5 Route Import...360 11.7.10.6 Route Aggregation...360 11.7.10.7 Route Dampening...360 11.7.10.8 Community Attribute...361 11.7.10.9 BGP Confederation...363 11.7.10.10 BGP GR...364 11.7.10.11 BGP Tracking...365
11.7.10.12 BGP Dynamic Update Peer-Groups...366
11.7.10.13 4-Byte AS Number...368
11.7.10.14 Terms and Abbreviations...371
11.7.11 VRF...372
11.7.11.1 Introduction...372
11.7.11.2 Specifications...373
11.7.11.3 Principle...373
11.7.12 Routing Policies...374
11.7.12.1 Introduction to Routing Policies...374
11.7.12.2 References...375
11.7.12.3 Basic Principle of Routing Policies...375
Module
11.7.12.4 Application Environment...376
11.7.12.5 BGP to IGP...377
11.7.12.6 Terms and Abbreviations...378
11.7.13 ECMP...378 11.7.13.1 Introduction...378 11.7.13.2 Specifications...378 11.7.13.3 Principle...379
12 IPv6...380
12.1 Introduction to IPv6...38112.2 Reference Standards and Protocols...382
12.3 Availability...383
12.4 Principles...384
12.4.1 IPv6 Addresses...384
12.4.2 IPv6 Characteristics...387
12.4.3 IPv6 Packet Format...389
12.4.4 ICMPv6...392
12.4.5 Neighbor Discovery...393
12.4.6 Path MTU...396
12.4.7 Dual Protocol Stacks...396
12.4.8 TCP6...397
12.4.9 UDP6...398
12.4.10 RawIP6...398
12.5 IPv6 Features Supported by the MA5600T/MA5603T...399
12.5.1 Routing...400
12.5.2 ACLv6...401
12.5.3 DHCPv6 Relay...403
12.5.4 MAC Address Binding...405
12.5.5 Anti-IP Spoofing...406
12.5.6 DAD Proxy...407
12.5.7 ARP/ND Proxy Response...408
12.6 Application...409
12.7 Terms and Abbreviations...410
13 Multicast...412
13.1 Introduction...413
13.2 Specifications...413
13.3 Reference Standards and Protocols...414
13.4 Availability...415
13.5 Multicast Overview...415
13.6 Implementation Principle of Multicast...420
13.6.1 Basic Managed Objects...420
13.6.2 Forwarding Framework on the Device...422
13.6.3 IGMP Control Framework...423
Module
13.6.4 Multicast Forwarding Flow...425
13.7 Advanced Multicast Technologies...428
13.7.1 Multicast Service...428
13.7.2 Protocol Interoperation...440
13.7.3 Network-side Interoperating Technologies...448
13.7.4 User-side Interoperating Technologies...460
13.7.5 Interoperating Technologies Between Specific Ends...466
13.8 Multicast Fault Diagnosis...470
13.9 Multicast QoS...472
13.10 Network Application...473
14 Network Protection Features...474
14.1 Ethernet Link Aggregation...475
14.1.1 Introduction...475
14.1.2 Specifications...476
14.1.3 Reference Standards and Protocols...477
14.1.4 Availability...477
14.1.5 Feature Enhancements...479
14.1.6 Principle...479
14.1.6.1 Introduction to LACP...479
14.1.6.2 Principle of Implementing Link Aggregation...481
14.1.6.3 Principle of Implementing Inter-Board Aggregation...483
14.1.7 Network Applications...483
14.1.8 Term, Acronyms, and Abbreviations...488
14.2 Protection Group of Uplink Ports...489
14.2.1 Introduction...489
14.2.2 Specifications...490
14.2.3 Availability...490
14.2.4 Principle...490
14.3 Smart Link and Monitor Link...492
14.3.1 Introduction...492 14.3.2 Specifications...492 14.3.3 Availability...493 14.3.4 Principle...493 14.3.4.1 Smart Link...493 14.3.4.2 Monitor Link...496 14.3.5 Network Applications...498
14.3.6 Glossary, Acronyms, and Abbreviations...499
14.4 MSTP...499
14.4.1 Introduction...500
14.4.2 Specifications...500
14.4.3 Reference Standards and Protocols...500
14.4.4 Availability...501
Module
14.4.5 Principle...501
14.5 RRPP...505
14.5.1 Introduction...505
14.5.2 Specifications...506
14.5.3 Reference Standards and Protocols...507
14.5.4 Availability...507 14.5.5 Principle...508 14.5.5.1 RRPP Network Topology...508 14.5.5.2 RRPP Packet...510 14.5.5.3 RRPP Basic Principle...513 14.5.5.4 Working Principle of RRPP...516 14.5.6 Network Applications...518
14.5.7 Glossary, Acronyms and Abbreviations...520
14.6 BFD...521 14.6.1 Overview...521 14.6.2 Specifications...521 14.6.3 References...521 14.6.4 Key Concepts...522 14.6.5 BFD for IP...525 14.6.6 Application Environment...525 14.6.6.1 BFD for USR...525 14.6.6.2 BFD for OSPF...526 14.6.6.3 BFD for IS-IS...526
14.6.7 Glossary, Acronyms, and Abbreviations...527
14.7 STM-1 Port Protection Switching...528
14.7.1 Introduction...528
14.7.2 Specifications...528
14.7.3 Reference Standards and Protocols...529
14.7.4 Availability...529
14.7.5 Principle...529
14.7.6 Glossary, and Acronyms and Abbreviations...530
14.8 Type C Protection of GPON Lines...531
14.8.1 Introduction...531
14.8.2 Specifications...531
14.8.3 Reference Standards and Protocols...532
14.8.4 Availability...532
14.8.5 Principle...533
14.9 GPON Port 1+1 Backup...534
14.9.1 Introduction...534
14.9.2 Specifications...534
14.9.3 Reference Standards and Protocols...535
14.9.4 Availability...535
Module
14.9.5 Principle...535
15 Voice Feature...538
15.1 Introduction...539 15.2 Specifications...539 15.3 Availability...542 15.4 ISDN...542 15.4.1 Introduction...54315.4.2 Reference Standards and Protocols...544
15.4.3 Basic principles...545
15.4.4 The Principles of ISDN BRA...548
15.5 MGCP Voice Services...549
15.5.1 Introduction...549
15.5.2 Reference Standards and Protocols...550
15.5.3 Principle...551 15.5.3.1 MGCP-Based VoIP...551 15.5.3.2 MGCP-Based MoIP...553 15.5.3.3 MGCP-Based FoIP...554 15.6 H.248 Voice Services...556 15.6.1 Introduction...556
15.6.2 Reference Standards and Protocols...557
15.6.3 Working Principle ...557
15.6.3.1 Mechanism of the H.248 Protocol...557
15.6.3.2 H.248-Based VoIP...561
15.6.3.3 H.248-Based MoIP...563
15.6.3.4 H.248-Based FoIP...563
15.7 SIP Voice Services...563
15.7.1 Introduction...564
15.7.2 Reference Standards and Protocols...566
15.7.3 Principle...566
15.7.3.1 SIP User Identification...566
15.7.3.2 SIP Message Format...567
15.7.3.3 User Registration Flow...568
15.7.3.4 Call Flow of the VoIP (SIP) Calling Party...570
15.7.3.5 Call Flow of the VoIP (SIP) Called Party...572
15.7.3.6 Call Releasing Flow...574
15.7.3.7 SIP-Based FoIP...574
15.7.3.8 SIP-Based MoIP...580
15.8 Key Voice Feature...581
15.8.1 Introduction...582
15.8.2 Codec and Packetization Duration ...582
15.8.3 Echo Canceller...583
15.8.4 Non-Linear Processor...584
Module
15.8.5 VAD...585
15.8.6 Packet Loss Concealment...585
15.8.7 Jitter Buffer...586
15.8.8 Dual Tone Multi Frequency...586
15.8.9 Tone Playing...587
15.8.10 Voice Quality Enhancement...588
15.8.11 Fax/Modem Quality Enhancement...588
15.8.12 RFC2833 Encryption...590
15.8.13 RTCP XR...591
15.9 Voice Interface Feature...591
15.9.1 Introduction...591
15.9.2 Ringing...591
15.9.3 Interface Protection...592
15.9.4 Features of the Voice Line Interface...593
15.10 Voice Test and Maintenance...596
15.10.1 Introduction...596
15.10.2 Loop Line Test and Circuit Test...596
15.10.3 Search Tone...601
15.10.4 Signal Tone Test...601
15.10.5 Call Emulation Test...602
15.10.6 RTCP Statistics...602
15.10.7 Remote Packet Capture...603
15.10.8 ToolBox...604 15.10.9 QoS Alarm...606 15.11 Voice Reliability...606 15.11.1 Introduction...606 15.11.2 Working Principle ...606 15.11.2.1 H.248/MGCP Dual Homing...607 15.11.2.2 H.248 Multi-homing...608 15.11.2.3 Emergency Standalone...611
15.11.2.4 SIP Dual Homing...613
15.11.2.5 H.248/SIP over SCTP...613
15.11.2.6 SIP over TCP...614
15.11.2.7 Voice QoS...614
16 Device Management Security...618
16.1 Introduction...620
16.2 Relevant Standards and Protocols...620
16.3 Availability...621
16.4 SNMP...622
16.4.1 Introduction...622
16.4.2 Specifications...623
16.4.3 SNMP Network Management Model...624
Module
16.4.4 SNMP MIB...625
16.4.5 SNMP SMI...625
16.4.6 Working Principle of SNMPv1...625
16.4.7 Working Principle of SNMPv2c...629
16.4.8 Working Principle of SNMPv3...629
16.4.9 Comparison Between SNMP Protocols in Security...630
16.5 Inband Management VPN...631 16.5.1 Introduction...632 16.5.2 Principles...632 16.6 SSH...633 16.6.1 Introduction...633 16.6.2 Specifications...634 16.6.3 SSH Working Principle...634
16.6.4 SSH-based Encryption for Remote Management Connection...635
16.6.5 SSH-based Encryption for File Transfer...635
16.7 User Management...636
16.7.1 Introduction...637
16.7.2 Specifications...637
16.7.3 Principle...637
16.8 Remote Connection Security...638
16.8.1 Introduction...638 16.8.2 Specifications...638 16.8.3 Principle...639 16.9 Log Management ...639 16.9.1 Introduction...639 16.9.2 Principle...639
16.10 Version and Data Management...640
16.10.1 Introduction...640
16.10.2 Specifications...640
16.10.3 Principle...641
16.11 Alarm and Event Management...643
16.11.1 Introduction...643
16.11.2 Specifications...643
16.11.3 Principle...643
16.12 Glossary, Acronyms, and Abbreviations...644
17 Network Security...645
17.1 Introduction...646 17.2 Availability...646 17.3 Anti-DoS Attack...647 17.3.1 Introduction...647 17.3.2 Specifications...648 17.3.3 Principle...648 Module17.4 Anti-ICMP/IP Attack...648
17.4.1 Introduction...648
17.4.2 Principle...649
17.5 Source Route Filtering...649
17.5.1 Introduction...649
17.5.2 Principle...649
17.6 MAC Address Filtering...649
17.6.1 Introduction...650 17.6.2 Specifications...650 17.6.3 Principle...650 17.7 Firewall Blacklist...650 17.7.1 Introduction...650 17.7.2 Specifications...651 17.7.3 Principle...651
17.8 Configuration of Acceptable or Refused Address Segments...651
17.8.1 Introduction...651
17.8.2 Specifications...652
17.8.3 Principle...652
17.9 Service Overload Control...652
17.9.1 Introduction...652
17.9.2 Availability...653
17.9.3 Principle...653
17.10 Acronyms and Abbreviations...658
18 Application Security...659
18.1 Introduction...661
18.2 Relevant Standards and Protocols...661
18.3 Availability...662 18.4 HWTACACS...664 18.4.1 Introduction...664 18.4.2 Specifications...664 18.4.3 Principle...665 18.5 RAIO...667 18.5.1 Introduction...667 18.5.2 Specifications...668 18.5.3 Principle...668 18.6 PITP...676 18.6.1 Introduction...676 18.6.2 Specifications...677 18.6.3 Principle...677 18.7 DHCP option82...679 18.7.1 Introduction...679 18.7.2 Specifications...680 Module
18.7.3 Principle...680
18.8 802.1X...682
18.8.1 Introduction...682
18.8.2 Specifications...682
18.8.3 Principle...683
18.9 Anti MAC Spoofing...684
18.9.1 Introduction...685
18.9.2 Specifications...685
18.9.3 Impact of MAC Spoofing...686
18.9.4 MAC Address Binding...686
18.9.5 Anti MAC Duplicate...687
18.10 Anti-IP Spoofing...687 18.10.1 Introduction...687 18.10.2 Specifications...688 18.10.3 Principle...688 18.11 User Isolation...689 18.11.1 Introduction...689 18.11.2 Specifications...689 18.11.3 Principle...689
18.12 Line Security of the GPON System...690
18.12.1 Introduction...690
18.12.2 Specifications...690
18.12.3 Principle...690
18.13 Glossary, Acronyms, and Abbreviations...691
19 Line Optimization and Line Test...692
19.1 Line Optimization...693 19.1.1 Introduction...693 19.1.2 Specifications...693 19.1.3 Reference...694 19.1.4 Availability...694 19.1.5 Principle...695
19.1.6 Glossary, Acronyms, and Abbreviations...696
19.2 SELT Test...697 19.2.1 Introduction...697 19.2.2 Specifications...697 19.2.3 Availability...698 19.2.4 Principle...698 19.3 MELT...699 19.3.1 Introduction...699 19.3.2 Specifications...700 19.3.3 Availability...701 19.3.4 Principle...701 Module
20 Operation and Maintenance...703
20.1 Introduction...704
20.2 Reference Standards and Protocols...704
20.3 Remote Operation...704 20.3.1 Introduction...704 20.3.2 Principle...705 20.4 Ring Check...705 20.4.1 Introduction...705 20.4.2 Specifications...706 20.4.3 Availability...706 20.4.4 Principle...706 20.5 ANCP...709 20.5.1 Introduction...709 20.5.2 Specifications...709
20.5.3 Reference Standards and Protocols...710
20.5.4 Availability...710
20.5.5 Principle...711
20.5.6 Glossary, Acronyms, and Abbreviations...720
20.6 Environment Monitoring...720
20.6.1 Introduction...720
20.6.2 Specifications...721
20.6.3 Availability...721
20.6.4 Principle...721
20.7 Power Saving and Maintenance...724
20.7.1 Overview of the Power Saving and Maintenance Feature...724
20.7.2 Power Saving...724 20.7.2.1 Introduction...724 20.7.2.2 Availability...725 20.7.2.3 Principle...725 20.7.3 Maintenance...728 20.7.3.1 Introduction...729 20.7.3.2 Principle...729 20.7.4 Glossary...730 20.8 ONT DHCP Simulation...730 20.8.1 Introduction...731 20.8.2 Specifications...732
20.8.3 Reference Standards and Protocols...732
20.8.4 Availability...732
20.8.5 Principle...734
21 Ethernet OAM...736
21.1 Introduction...737
21.2 Reference Standards and Protocols...737
Module
21.3 Ethernet CFM OAM...737 21.3.1 Introduction...737 21.3.2 Specifications...738 21.3.3 Availability...739 21.3.4 Principle...741 21.4 Ethernet EFM OAM...745 21.4.1 Introduction...745 21.4.2 Availability...747 21.4.3 Principle...747 21.5 Glossary, Acronyms, and Abbreviations...750
22 Redundancy Backup of the Control Boards...753
22.1 Introduction...754 22.2 Specifications...754 22.3 Availability...754 22.4 Principle...754
23 Clock Feature...756
23.1 NTP...757 23.1.1 Introduction...757 23.1.2 Specifications...757 23.1.3 Reference Standards and Protocols...757 23.1.4 Availability...758 23.1.5 Principle...758 23.2 Clock and Time System...759 23.2.1 Introduction...759 23.2.2 Specifications...760 23.2.3 Reference Standards and Protocols...761 23.2.4 Availability...763 23.2.5 Enhancement...763 23.2.6 Principle of the Clock and Time System...763 23.2.6.1 Clock/Time Synchronization Source...764 23.2.6.2 Configuring the System Phase-Locked Loop...765 23.2.6.3 Clock/Time Output...765 23.2.6.4 Working Principle of Clock...767 23.2.7 Scenarios of Clock/Time Synchronization...768 23.2.7.1 Applications of Clock Output...768 23.2.7.2 Clock Synchronization of the Native TDM Service...769 23.2.7.3 SAToP Clock Synchronization...772 23.2.7.4 Clock Synchronization of the Synchronization Ethernet Service...776 23.2.8 Glossary, Acronyms, and Abbreviations...77824 The Feature of LAN Interface Boards...781
24.1 ETHB Board Feature...782
Module
24.1.1 Introduction...782 24.1.2 Specifications...783 24.1.3 Reference Standards and Protocols...783 24.1.4 Availability...783 24.1.5 Principle...784 24.2 SPUA...786 24.2.1 Introduction...786 24.2.2 Specifications...787 24.2.3 Principle...788 24.3 GIU Board Feature...792 24.3.1 Introduction...792 24.3.2 Specifications...792 24.3.3 Reference Standards and Protocols...792 24.3.4 Availability...793 24.3.5 Principle...793 24.3.6 Glossary, Acronyms, and Abbreviations...800
Module
1
GPON
About This Chapter
Gigabit passive optical network (GPON) is one of the PON technologies. A GPON-capable device supports high-bandwidth transmission. GPON effectively solves the bandwidth bottleneck problem in the twisted-pair access and meets users demands on high-bandwidth services.
1.1 Introduction 1.2 Specifications
1.3 Reference Standards and Protocols 1.4 Availability
1.5 Overview of the GPON System 1.6 GPON Principle
1.7 Key GPON Technologies
1.8 GPON Terminal Authentication and Management 1.9 Continuous-Mode ONU Detection
The GPON system supports detection of a continuous-mode ONU to ensure that the GPON system runs properly and does not get into disorder because of the continuous-mode ONU.
1.10 GPON Network Applications
1.11 Glossary, Acronyms, and Abbreviations
Module
1.1 Introduction
Definition
xPON is a type of point to multi-point (P2MP) passive optical network (PON). The gigabit-capable passive optical network (GPON) is standardized by the ITU-T Recommendations G. 984.x. It supports the upstream rate of 1.25 Gbit/s and downstream rate of 2.5 Gbit/s. A typical PON system consists of:
l Optical line terminal (OLT) l Optical network unit (ONU) l Optical distribution network (ODN) The ODN connects the OLT to the ONU.
Purpose
GPON adopts the passive optical transmission technology and is mainly applicable to such scenarios as fiber to the home (FTTH), fiber to the building (FTTB), fiber to the office (FTTO), and fiber to the mobility base station (FTTM) to provide various services:
l Voice l Data l Video l Leased line l Distributed service
GPON supports high-bandwidth transmission. This helps break the bandwidth bottleneck of the access over twisted pairs and achieve bandwidth-eating services, such as high-definition TV (HDTV) and live programs.
In addition, GPON supports long-reach access, which helps extend the coverage and reduce network nodes.
1.2 Specifications
The specifications of the GPON boards and ports are as follows:
l The system supports the service shelf to be fully configured with the GPBC/GPBD board (every GPBC board supports four GPON ports and every GPBD board supports eight GPON ports).
l Every GPBC/GPBD supports up to 8K service streams. l Every GPON port on GPBC supports up to 64 ONUs. l Every GPON port on GPBD supports up to 128 ONUs. l The system supports up to 8,192 ONUs.
l The GPON port supports maximum downstream and upstream rates of 2.5 Gbit/s and 1.25 Gbit/s respectively.
Module
l The system supports a maximum physical transmission distance of 20 km and a maximum logical transmission distance of 60 km.
l The GPON board supports the query of the CPU usage.
l The system supports the query of the alarm information about a PON port on the GPON board through the CLI.
l The system supports five types of power budget for the GPON port: CLASS A,CLASS B,CLASS B+,CLASS C, and CLASS C+. CLASS B+ is in most common use and CLASS C+ is used in some long-distance transmission scenarios. CLASS B+ achieves the optical power budget of 28.5 dB, slightly smaller than that of CLASS C+ (up to 32 dB).
The system supports the following GEM port and T-CONT specifications:
l The system supports the GEM encapsulation. Every GPON port supports up to 4096 GEM ports and the maximum number of GEM ports supported in the system is 32K.
l The system supports up to 512 DBA profiles and 32K T-CONTs.
l The system supports the loop line detection for the remote GEM port and the line detection for the ONT UNI port.
l The system can automatically allocate GEM port IDs.
The system supports the following GPON terminal management specifications: l Supports activating/deactivating ONU.
l Supports resetting ONU.
l Supports automatically issuing the configuration of the ONUs that go online again. l Supports obtaining the version information about ONUs.
l Supports displaying the status of the physical ports of ONUs.
l Supports monitoring the optical fiber receive and transmit power of ONUs. l Supports reporting the alarms of ONUs.
l Supports displaying the information about the optical transceiver of the ONT.
l Supports time synchronization between the ONT and the OLT through the extended OMCI. l Supports enabling/disabling the BPDU transparent transmission function for an ONT or an
Ethernet port of an ONT.
l Supports VLAN and priority switching for a port of an ONT. l Supports VLAN switching for upstream IGMP packets of an ONT. l Supports configurable ONT queue scheduling modes.
l Supports setting the multicast snooping mode for an ONT.
l Supports enabling/disabling the MAC address learning function for an ONT through the extended OMCI.
l Supports the standard OMCI protocol defined by the ITU-T and also the GPON interoperability standard defined by China Telecom.
l Supports loopback on the ETH port and the E1 port of the ONU.
The system supports the following GPON QoS specifications:
H805GPBD, H802GPBD, H802EPBC, H802EPBD and H805EPBD support ONU-based CAR. (H805GPBD supports ONU-based CAR by ONU-based traffic shaping.)
Module
1.3 Reference Standards and Protocols
GPON technical standards are researched by Full Service Access Networks (FSAN) and officially released by ITU-T. FSAN is established in 1995 in response to the initiatives of seven major network carriers, and aims to propose an optical access solution and formulate standards associated with the optical access equipment, so that the standard-compliant equipment can provide the voice, data, and video services.
GPON standards mainly include:
l ITU-T G.984.1: General Characteristics. This protocol mainly describes the basic features and major protection modes of GPON.
l ITU-T G.984.2: Physical Media Dependent (PMD) Layer Specification. This protocol mainly describes the PMD layer parameters, including physical parameters (such as the transmit optical power, receiver sensitivity, and overload optical power) of optical transceivers, and also defines optical budget of different levels, for example, the most common Class B+.
l ITU-T G.984.3: Transmission Convergence Layer Specification. This protocol mainly describes the TC layer specifications, including the upstream and downstream frame structures and GPON principle.
l ITU-T G.984.4: ONT Management And Control Interface Specification. This protocol mainly describes the GPON management and maintenance protocols, such as OAM, PLOAM, and OMCI.
l ITU-T G.984.5: Enhancement Band. This protocol mainly describes the GPON wavelength planning, including reserving bands for next-generation PON.
l ITU-T G.984.6: Reach Extension. This protocol mainly describes several long reach PON schemes for extending GPON transmission distance.
l TR-156: Using GPON Access in the context of TR-101.
1.4 Availability
License Support
The number of remote ONT ports supported by the MA5600T/MA5603T is licensed. Therefore, the corresponding service is also licensed.
Version Support
Table 1-1 Version Support
Product Version
MA5600T/ MA5603T
V800R006C02 and later versions Module
Hardware Support
l Boards supporting this feature are GPBC and GPBD. l The terminals must support GPON upstream transmission.
1.5 Overview of the GPON System
Introduction to the PON System
PON is the short form for passive optical network. It adopts a point-to-multipoint (P2MP) network architecture. A PON network consists of three parts: the optical line terminal (OLT), optical distribution network (ODN), and optical network units (ONUs).
l The OLT is an aggregation device located at the central office (CO) for terminating the PON protocol.
l ONUs are located on the user side, providing various types of ports for connecting to user terminals. The OLT and ONUs are connected through a passive ODN for communication. l The ODN is composed of passive optical components such as optical fibers, and one or
more passive optical splitters. The ODN provides optical channels between the OLT and ONUs. It interconnects the OLT and ONUs and is highly reliable.
Figure 1-1 shows the architecture of a PON network. A PON network differs from the traditional
broadband access network in that PON transmits data using optical fibers. Also, a PON network can connect a large number of access users, requires less optical fiber resources, and supports a high access rate.
Figure 1-1 PON network
Passive Optical Network
Passive Optical Splitter Passive Optical Splitter OLT ONU
Mainstream PON technologies include broadband passive optical network (BPON), Ethernet passive optical network (EPON), and gigabit passive optical network (GPON). Adopting the ATM encapsulation mode, BPON is mainly used for carrying ATM services. With the
obsolescence of the ATM technology, BPON also drops out. EPON is an Ethernet passive optical network technology. GPON is a gigabit passive optical network technology and is to date the most widely used mainstream optical access technology.
Module
Introduction to the GPON System
GPON is a PON technology. GPON supports an upstream rate of 1.25 Gbit/s and downstream access rate of 2.5 Gbit/s, and also supports ultra-long transmission with a maximum physical reach of 20 km and maximum logical reach of 60 km. At the same time, GPON supports a 1:64 split ratio, which can be extended to 1:128 and enables GPON to support a large number of users and cover a wide area. Figure 1-2 shows the working principle of the GPON network.
Figure 1-2 Working principle of the GPON network
OLT ODN
ONU/ONT
1490nm
1310nm
In the GPON network, the OLT is connected to the optical splitter through a single optical fiber, and the optical splitter is then connected to ONUs. Different wavelengths are adopted in the upstream and downstream directions for transmitting data. The upstream wavelength is 1310 nm and downstream wavelength is 1490 nm. The GPON adopts WDM to transmit data of different upstream/downstream wavelengths over the same ODN. Data is broadcast in the downstream direction and transmitted in the TDMA mode (based on timeslots) in the upstream direction.
All data is broadcast to all ONUs from the OLT. The ONUs then select and receive their respective data and discard the other data. Figure 1-3 shows the details.
Figure 1-3 Downstream communication principle of GPON
3 2 1 3 2 1 3 2 1 3 2 1 3 2 1 OLT ONU1 ONU2 ONU3 Splitter Module
In the upstream direction, each ONU can send data to the OLT only in the timeslot permitted and allocated by the OLT. This ensures that each ONU sends data in a given sequence, thus avoiding upstream data conflicts. Figure 1-4 shows the details.
Figure 1-4 Upstream communication principle of GPON
3 2 1 1 2 3 3 2 1 OLT ONU1 ONU2 ONU3 Splitter
1.6 GPON Principle
Basic GPON Concepts
In the GPON system, a GPON encapsulation mode (GEM) frame is the smallest service-carrying unit and the most basic encapsulation structure. All service streams are encapsulated into the GEM frame and transmitted over GPON lines. The service streams are identified by GEM ports and every GEM port is identified by a unique Port-ID. The Port-ID is globally allocated by the OLT. That is, the ONUs connected to the OLT cannot use GEM ports that have the same Port-ID. The GEM port is used to identify the virtual service channel that carries the service stream between the OLT and the ONU. It is similar to the VPI/VCI of the ATM virtual connection. T-CONT: a service carrier in the upstream direction in the GPON system. All GEM ports are mapped to T-CONTs. Then, service streams are transmitted upstream by means of the OLT's DBA scheduling. T-CONT is the basic control unit of the upstream service stream in the GPON system. Every T-CONT is identified by Alloc-ID. The Alloc-ID is globally allocated by the OLT. That is, every T-CONT can be used by only one ONU connected to the OLT.
There are five types of T-CONT; therefore, T-CONT selection varies during the scheduling of different types of upstream service streams. Every T-CONT bandwidth type has its own quality of service (QoS) feature. QoS is mainly represented by the bandwidth guarantee, which can be classified as fixed, assured, non-assured, best-effort, and hybrid mode (corresponding to type 1-type 5 in Table 1-2).
Module
Table 1-2 T-CONT types Bandwidth
Type T-CONT Type
Type 1 Type 2 Type 3 Type 4 Type 5
Fixed Bandwidth X No No No X Assured Bandwidth No Y Y No Y Maximum Bandwidth Z = X Z = Y Z > Y Z Z ≥ X + Y NOTE
In Table 1-2, X indicates the fixed bandwidth value, Y the assured bandwidth value, and Z the maximum bandwidth value.
Figure 1-5 shows the principle of service multiplexing in the GPON system. On ONUs, all
service streams are mapped to different GEM ports and then to different types of T-CONTs for upstream transmission (the T-CONT is the basic carrier in the upstream direction over GPON lines). On the OLT, the T-CONT demodulates GEM ports therein and sends them to the GPON MAC chip. The MAC chip demodulates service streams in the GEM port payload and then sends them to a proper service processing unit for processing. In the downstream direction, all service streams are encapsulated by the GPON service processing unit into GEM ports and then GEM ports are broadcast to all ONUs connected to the GPON port. Then, every ONU filters data according to GEM port ID, reserving the GEM port corresponding to itself. After that, every ONU decapsulates service streams from the GEM port and sends them to the user-side equipment through the service interface of the ONU.
Figure 1-5 Principle of service multiplexing in the GPON system
ONU OLT
T-CONT
GEM port
T-CONT
GEM port
Figure 1-6 and Figure 1-7 shows the mapping between service stream, GEM port, and T-CONT.
The GEM port is the smallest service unit in the GPON system. Every GEM port can carry one Module
or more types of service stream. The GEM port, after carrying service streams, must be mapped to a T-CONT before upstream service scheduling. Every ONU supports multiple T-CONTs and can be configured with different service types. A T-CONT can be bound with one or more GEM ports, depending on the user's configuration. On the OLT, GEM ports are demodulated from the T-CONT and then service streams are demodulated from the GEM port payload for further processing.
Figure 1-6 GPON service mapping relationship (Downstream)
Port
Port
Port
Port
Port
Port
PON
OLT
Port
Port
Port
Port
ONU
ONU
G
E
M
P
o
rt
f
ilt
er
G E M P or t f ilt erONU
G E M P o rt fi lte r ModuleFigure 1-7 GPON service mapping relationship (Upstream) Port Port Port Port Port Port T-CONT PON ONU ONU ONU Identified by ONU-ID Identified by Alloc -ID Identified by Port-ID T-CONT T-CONT T-CONT Port Port Port
GPON Frame Structure
Figure 1-8 shows the GPON frame structure. The GPON downstream frame is invariably 125
µs long and it comprises Physical Control Block downstream (PCBd) and Payload. PCBd mainly consists of the GTC header and the upstream bandwidth map (BWmap). The GTC header is mainly used for performing frame delimitation, clock synchronization, and FEC. The BWmap is mainly used for notifying every ONU of its upstream bandwidth allocation, thereby
determining the start and end timeslots of the T-CONT corresponding to every ONU in the upstream transmission process. In this way, all ONUs send data according to timeslots uniformly specified by the OLT and data collision is avoided. In the upstream direction, service scheduling is performed in the TDMA mode according to T-CONT. All ONUs connected to a GPON port share the upstream bandwidth and send their data upstream at their own timeslots according to the BWmap requirements. At the same time, every ONU reports its status of data to be sent to the OLT through the upstream frame. Then, the OLT uses DBA to allocate upstream timeslots to ONUs and sends updates in every frame.
Module
Figure 1-8 GPON frame structure T-CONT1 (ONT 1) T-CONT 2 (ONT 2) 257 100 200 258 300 500
AllodID Start End AllodID Start End
Payload 125 µs
Downstream framing
PLOu PLOAMu PLSu DBRu Payload x DBRu Y Payload y Upstream framing
Upstream Bandwidth Map Physical Control Block
Downstream (PCBd) Slot 100 Slot 200 Slot 300 Slot 500 OLT ONU NOTE
l PLOu: Physical Layer Overhead upstream l PLOAM: Physical Layer OAM
l PLOAMu: PLOAM upstream
l PLSu: Power Levelling Sequence upstream l DBRu: Dynamic Bandwidth Report upstream l The current application is:
l GPBC: Alloc-ID = T-CONT ID x 256 + ONU ID
l GPBD: When T-CONT ID < 8, Alloc-ID = T-CONT ID x 256 + ONU ID. When T-CONT ID ≥ 8, Alloc-IDs are assigned automatically from the first idle Alloc-ID.
The lengths of the upstream frame and downstream frame at each GPON rate are the same. Every upstream frame contains the content carried by one or more T-CONTs. The BWmap in each downstream frame identifies the start time and end time of each T-CONT transmission. An ONU must send a PLOu each time before the ONU receives the media access right to PON from another ONU. If an ONU is allocated two consecutive Alloc-IDs (the end time of one is smaller by 1 than the start time of the other), the ONU must not send the PLOu of the second Alloc-ID. The payload of an upstream frame may contain three types of content: the ATM cell, the GEM frame, and the DBA report.
Figure 1-9 shows the GPON upstream frame structure.
Module
Figure 1-9 GPON upstream frame structure PLOu DB RuX PLSu Payload X DB RuYPayload Y ONU A ONU B Upstream Frame PLO AMu PLOu DB RuZ Payload Z
The GPON upstream frame consists of the PLOu, PLOAMu, PLSu, DBRu, and Payload fields and the meanings of these fields are described as follows:
l PLOu: physical control header, mainly used for frame delimitation, synchronization, and indication of which ONU the current frame targets at.
l PLOAMu: PLOAM message of upstream data, mainly used for reporting management information such as ONU maintenance and management status. (Not every frame has such a field. This field may not be sent but needs to be negotiated.)
l PLSu: Power Levelling Sequence upstream. It is a 120-byte field and is used for power control measurements by the ONU.
l DBRu: mainly used for reporting the T-CONT status for applying for bandwidth and completing dynamic bandwidth allocation for ONUs next time. (Not every frame has such a field. This field may not be sent but needs to be negotiated.)
l Payload: DBA status report or data frame. The data frame may be GEM header or frame. l GEM header: mainly used for differentiating data of different GEM ports. The GEM port is the smallest unit for data transmission in the GPON system, which is similar to the PVC of ATM. Every type of upstream service stream must be mapped to the GEM port and then to the T-CONT for transmission. The GEM header field consists of PLI, Port ID, PTI, and HEC.
– PLI: Indicates the length of data payload. – Port ID: Uniquely identifies a GEM port.
– PTI: Identifies the payload type. It is mainly used for identifying the status and type of data that is being transmitted (for example, whether the OAM message is being transmitted and whether data transmission is complete).
– HEC: Provides the FEC function and transmission quality.
GPON supports a downstream transmission rate of 2.488 Gbit/s, a frame length of 38880 bytes, and a frequency of one frame every 125 µs, as shown in Figure 1-10 and Figure 1-11. Module
Figure 1-10 GPON downstream frame structure Payload n = PCBd n+1 Payload n+1 PCBdn+2 PCBd n
TDM & Data Fragments over GEM Section
N * 53 bytes "Pure" ATM cells Section
T
125us
Figure 1-11 PCBd structure US BW Map N*8bytes PSync 4 bytes Ident 4 byte Payload PCBdCoverage of next BIP Coverage of this BIP
PLOAMd 13 bytes BIP 1 byte PLend 4 bytes PLend 4 bytes
The OLT broadcasts PCBd to all ONUs. Every ONU receives the entire PCBd and then acts upon the relevant information contained therein.
A PCBd contains information such as frame synchronization information, physical layer OAM information, and BIP check field. US BWMap (upstream bandwidth map) is the upstream transmission bandwidth map sent to each T-CONT by the OLT. The bandwidth map is transmitted through the US BW Map field in the PCBd of the downstream frame. In this way, MAC control is implemented.
GPON uses TDM for the upstream transmission. Therefore, when multiple ONUs transmit data upstream concurrently, transmission conflicts occur. The avoidance mechanism for such a conflict is that the OLT sends a notification through the downstream frame, informing each ONU of its corresponding timeslot for upstream transmission.
1.7 Key GPON Technologies
Key GPON technologies include the burst optical/electrical technology, ranging, forward error correction (FEC), line encryption, and dynamic bandwidth allocation (DBA).
Burst Optical/Electrical Technology
The GPON system is a point to multi-point (P2PM) network. A GPON port on the OLT side can connect to 64 ONUs through optical splitters. In the GPON system, all data is broadcast Module
downstream to ONUs. This requires not only OLT-side optical transceivers to send optical signals continuously but ONU-side optical transceivers to receive optical signals continuously. In the upstream direction, the GPON system uses the time division multiple access (TDMA) technology. That is, every ONU sends data at its own allocated timeslot and disables its optical transceiver (that is, stop sending optical signals) at timeslots allocated to other ONUs, thereby avoiding affecting other ONUs. The OLT then receives the upstream data of every ONU in a burst manner according to timeslots. Hence, to ensure the normal running of the GPON system, OLT-side optical transceivers must support the burst receiving of upstream data sent by ONUs, and ONU-side optical transceivers are able to send data upstream in a burst manner.
Ranging
Generally, ranging is enabled when an ONU is registered for the first time. In a GPON system, TDMA is adopted when multiple ONUs send data to an OLT. That is, only one ONU under a PON port can send data to the OLT at a time; otherwise, data collisions occur. To avoid such collisions, the logical distance between each ONU and the OLT must be measured to calculate the equalization delay (EqD) of each ONU so that the time for ONUs to send data is controlled by the OLT.
By ranging, the OLT obtains the RTD of each ONU and then calculates their EqDs to ensure that Teqd = RTD + EqD for each ONU. Teqd is short for the equalized round trip delay, which is preset in the system and is equal to or larger than the RTD of the logically farthest ONU. Each ONU delays the upstream data transmission, in reference to the downstream phase, based on the value of the assigned EqD. This is to avoid the collisions between the upstream data of different ONUs. Figure 1-12 shows the ranging method.
Figure 1-12 GPON ranging
Module
l Pre-assigned EqD: default EqD preset on an ONU
l Zero-distance equalization delay: Teqd preset in the system
l Assigned equalization delay: EqD when an ONU functions properly
FEC
Forward error correction (FEC) is mainly used for improving the transmission quality of a line. FEC uses RS (255, 239), performing an FEC encoding of all downstream packets every 255 bytes. This ensures the correctness of data received by the ONUs. By using the FEC algorithm at the transport layer, the GPON system achieves the reduced bit error rate (from 10-3 to 10-12) of line transmission, avoids data retransmission, and improves the optical power budget by 2-3 dB. Upstream FEC and downstream FEC are supported in the GPON system.
Line Encryption
In the GPON system, downstream data is broadcast to all ONUs. As a result, downstream data destined for certain ONUs or all ONUs may be intercepted by illegal users. At the same time, the GPON system is uniquely and highly data-directional. Therefore, almost every ONU cannot intercept the upstream data of other ONUs, thus allowing some private information (such as key) to be safely transmitted in the upstream direction. The GPON system uses the line encryption technology to solve the security issues.
l Encryption system
The GPON system uses AES128 encryption for line security control, thereby effectively preventing security issues such as data embezzlement. In the AES128 encryption system, the OLT supports key exchange and switchover.
l Key exchange
The key exchange is initiated by the OLT. The OLT does so by sending a key exchange request. The ONU responds by generating and sending the key to the OLT. Because the PLOAM (Physical Layer OAM) message is limited in length, the key is sent in two parts. The two parts of the key are sent three times repeatedly. If the OLT has not received the key for any of the three times, it will re-send the key exchange request until it receives the same key all three times the key is sent. When the OLT receives a new key, it starts the key switching. The OLT notifies the ONU by sending a command containing the frame number of the new key. This command will be sent for three times. As long as the ONU receives the command once, it will switch the check key on proper data frames.
DBA
In the GPON system, the OLT controls an ONU's upstream data traffic by sending authorization signals to the ONU. PON requires an effective TDMA mechanism to control the upstream traffic, so that data packets from multiple ONUs do not collide when packets are transmitted upstream. Nevertheless, the collision-based mechanism requires QoS management in an optical
distribution network (ODN), a passive network. This is physically impossible, or causes severe efficiency decrease. Due to the above-mentioned reason, a mechanism for management of the upstream GPON traffic has been a primary focus in standardization of GPON traffic
management. It drives the development of the ITU-TG.983.4 Recommendation, which defines the dynamic bandwidth allocation (DBA) protocol for management of the upstream PON traffic.
Figure 1-13 shows the DBA principle. The GPON system controls the upstream traffic by
allocating data authorization to each transmission container (T-CONT) inside the ONU. The OLT needs to know the traffic status of a T-CONT to determine the authorized amount to be Module
allocated to the T-CONT. By using the DBRu field or the Payload field in the upstream frame, the ONUs report their data statuses to the OLT. After receiving ONUs' data statuses, the OLT uses DBA to periodically update the upstream BWmap information according to the status of ONU data waiting to be sent and notifies all ONUs of the updates through the downstream frame. Thus, every ONU can dynamically adjust its upstream bandwidth according to the actual data traffic to be sent, thereby improving the utilization of upstream bandwidth.
Figure 1-13 DBA principle
DBA algorithm logic ONU Control plane OLT Data plane Scheduler T-CONT DBA report BW Map Time slot
1.8 GPON Terminal Authentication and Management
GPON Terminal Authentication
GPON terminal authentication is a mechanism in which an OLT authenticates an ONU according to the authentication information reported by the ONU and in this way denies access to unauthorized ONUs. In the GPON system, only authenticated ONUs can access the system. Implementing authentication meets the carriers' requirements for flexible management and easy maintenance.
ONUs to be authenticated can be classified into two types: ONUs (automatically discovered ONUs) that are not preconfigured on the OLT and ONUs that are preconfigured on the OLT.
Figure 1-14 shows the authentication process of an ONU that is not preconfigured.
Module
Figure 1-14 Authentication process of an ONU that is not preconfigured
OLT DS Frame with valid Psync
Upstream_Overhead PLOAM SN _Request(BWMap) Serial_Number_ONU PLOAM
O1: Initial state O2: Standby state
O3: Serial number state
The ONU returns to the O2 state.
Assign ONU_ID
Ranging request Ranging response
Ranging time
O4: Ranging state
O5: Operation state The OLT assigns a
temporary ONU ID when the SN is not configured on the OLT.
Request password
Password
The OLT sends a deregister message to the ONU when the password is not configured on the OLT and automatic discovery is not enabled on the PON port. ONU
As shown in the preceding figure, after receiving downstream traffic following its power-on, the ONU responds to the SN request message sent from the OLT. The OLT, upon receiving the SN from the ONU, finds that the SN is not configured and assigns a temporary ONU ID to the ONU. After the ONU enters the operation state, the OLT sends a password request message to the ONU. The ONU then responds with a password. When finding that the password is not configured on the OLT and that the automatic discovery function is not enabled on the PON port Module
to which the ONU is connected, the OLT sends a deregister message to the ONU. Upon receiving this message, the ONU sends a register request message to the OLT.
A preconfigured ONU can be authenticated in five modes: SN, SN+password, password, logical ONU ID (LOID), and LOID+CheckCode (CC).
l SN authentication
In SN authentication, the OLT matches only the ONU SN. Figure 1-15 shows the process of SN authentication.
Figure 1-15 SN authentication
Normal-state ONU
OLT DS Frame with valid Psync
Upstream_Overhead PLOAM SN _Request(BWMap) Serial_Number_ONU PLOAM
O1: Initial state O2: Standby state
O3: Serial number state Assign ONU_ID
Ranging request Ranging response
Ranging time
O4: Ranging state SN is matched.
ONU
Normal-state OLT
– After receiving the SN response message from the ONU, the OLT checks whether an ONU with the same SN is already online. If yes, the OLT reports an SN conflict alarm to the CLI or NMS. If no, the OLT directly assigns the user-defined ONU ID to the ONU.
Module
– After the ONU enters the operation state, the OLT does not send a password request message to this ONU. Instead, the OLT directly configures a GEM port for the ONU for carrying OMCI messages, and allows the ONU to go online. The GEM port can be automatically configured by the OLT so that the OMCI-carrying GEM port has the same ID as the ONU ID. In addition, the OLT reports an ONU online alarm to the CLI or NMS.
l SN+password authentication
In SN+password authentication, the OLT matches both the ONU SN and password. Figure 1-16 shows the process of SN+password authentication.
Module
Figure 1-16 SN+password authentication
OLT DS Frame with valid Psync
Upstream_Overhead PLOAM SN _Request(BWMap) Serial_Number_ONU PLOAM
O1: Initial state O2: Standby state
O3: Serial number state
Assign ONU_ID
Ranging request Ranging response
Ranging time
O4: Ranging state ONU
Normal-state OLT
O5: Operation state Request password Password Normal-state ONU SN is matched. Password is matched.
– After receiving the SN response message from the ONU, the OLT checks whether an ONU with the same SN is already online. If yes, the OLT reports an SN conflict alarm to the CLI or NMS. If no, the OLT directly assigns the user-defined ONU ID to the ONU.
– After the ONU enters the operation state, the OLT sends a password request message to the ONU, and compares the password reported by the ONU with the password configured on the OLT. If the passwords are the same, the OLT checks whether an ONU Module
authenticated by the same SN+password is already online. If yes, the OLT reports a password conflict alarm to the CLI or NMS. If no, the OLT directly configures a GEM port for the ONU for carrying OMCI messages, and allows the ONU to go online. In addition, the OLT reports an ONU online alarm to the CLI or NMS. If the passwords are different, the OLT does not report an ONU automatic discovery message even if the ONU automatic discovery function is enabled on the PON port to which this ONU is connected. Instead, the OLT sends a Deactivate_ONU-ID PLOAM message to deregister the ONU.
l Password authentication
Password authentication includes two modes: always-on and once-on. An ONU that uses password authentication is added to a PON port on an OLT in advance, and then this ONU is connected to the PON port.
– In once-on mode, the aging-time is configurable, ranging from 1 hour to 168 hours. After the aging-time is set, the ONU must register with the OLT and go online within the preset aging time. Otherwise, the ONU is not allowed to register with the OLT or go online. Once the ONU is authenticated, its SN cannot be modified. In once-on mode, only the initial authentication of an ONU is by password, as shown in Figure 1-17. In subsequent authentications, the ONU is authenticated by SN or SN+password according to the CLI configuration, as shown in Figure 1-15 or Figure 1-16. Once-on mode is applied in the following scenario: The carrier allocates a password to the user, and the user must go online within the specified time. After going online, the user cannot change the ONU. To change the ONU, the user must notify the carrier of this requirement. Module
Figure 1-17 Initial ONU authentication in once-on mode
OLT DS Frame with valid Psync
Upstream_Overhead PLOAM SN _Request(BWMap) Serial_Number_ONU PLOAM
O1: Initial state O2: Standby state
O3: Serial number state
Assign ONU_ID Ranging request Ranging response
Ranging time
O4: Ranging state ONU
Normal-state OLT
O5: Operation state Request password
Password
Normal-state ONU
For the ONU that goes online for the first time, the OLT records the ONU SN.
Password is matched.
– In always-on mode, there is no restriction on the time when the user goes online. An ONU is authenticated by password when it goes online for the first time. After the ONU passes the password authentication and goes online successfully, the OLT generates an SN+password entry according to the SN and password of the ONU. If it is not the first time that an ONU goes online, and if the SN and password of the ONU are the same as the SN and password of the ONU that successfully goes online for the first time, the ONU is authenticated by SN+password. If the user needs to replace the ONU with an ONU that has the same password but a different SN, the ONU after the replacement will be authenticated by password. After this ONU passes authentication and goes online Module
successfully, the original SN+password entry is updated. Therefore, in the always-on mode, the ONU can go online at any time if its password is correct. Figure 1-18 shows the process of ONU authentication in always-on mode. The always-on mode is applied in the following scenario: The carrier allocates a password to the user, and the user can use different ONUs with different SNs, as long as the user uses the same password. As such, the user can change the ONU without informing the carrier.
Figure 1-18 ONU authentication in always-on mode
OLT DS Frame with valid Psync
Upstream_Overhead PLOAM SN _Request(BWMap) Serial_Number_ONU PLOAM
O1: Initial state O2: Standby state
O3: Serial number state Assign ONU_ID
Ranging request Ranging response
Ranging time
O4: Ranging state ONU
Normal-state OLT
O5: Operation state Request password Password Normal-state ONU Password is matched.
– In password authentication, if finding that the SN or password of the ONU to be authenticated conflicts with that of an online ONU, the OLT deregisters the ONU to be authenticated. This does not affect the online ONU.
– In once-on mode, before the registration of the ONU times out or before the ONU successfully registers with the OLT for the first time, the ONU discovery status is Module
ON (only the ONU whose discovery status is ON is allowed to register with the OLT
and go online). After the registration of the ONU times out or after the ONU successfully registers with the OLT for the first time, the OLT sets the discovery status of the ONU to OFF. The ONU whose registration times out is not allowed to register with the OLT or go online. In this case, the registration timeout flag of the ONU needs to be reset at the central office (CO), and then the ONU can go online. An ONU that successfully registers for the first time is allowed to register and go online again.
l LOID+CC authentication
LOID+CC authentication is defined by the CTC2.1 standard of China Telecom. In this authentication mode, LOID has 24 bytes, and CC has 12 bytes and is optional. Based on this authentication mode, China Telecom defines a new GPON OMCI entity for GPON LOID+CC authentication.
Figure 1-19 shows the process of GPON LOID+CC authentication.
Figure 1-19 GPON LOID+CC authentication
LOID (24) CC (12) LOID (24) CC (12) LOID (24) CC (12) OSS NMS OLT PW (10) LOID(24) CC(12)
OMCI: last 10 bytes
of the LOID OMCI: (LOID,CC)
GPON ONT
(Password authentication)
GPON ONT
(LOID authentication)
In GPON LOID+CC authentication:
1. The OLT obtains LOID+CC (configured on the ONT web page) of an ONT and matches the information against related information on the OLT. If the information is matched, the ONT passes the authentication.
2. If the information is not matched, the OLT obtains the password of the ONT and compares it with the last 10 bytes of the LOID. If the information is matched, the ONT passes the authentication.
Module