TECHNICAL REPORT
© The Broadband Forum. All rights rerved. TR-167
GPON-fed TR-101 Ethernet Access Node
Issue: 1
Issue Date: February 2010
粤语发音
Notice
The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Broadband Forum Technical Report has been approved by members of the Forum. This Broadband Forum Technical Report is not binding on the Broadband Foru
m, any of its members, or any developer or rvice provider. This Broadband Forum Technical Report is subject to change, but only with approval of members of the Forum. This Technical Report is copyrighted by the Broadband Forum, and all rights are rerved. Portions of this Technical Report may be copyrighted by Broadband Forum members. This Broadband Forum Technical Report is provided AS IS, WITH ALL FAULTS. ANY PERSON HOLDING A COPYRIGHT IN THIS BROADBAND FORUM TECHNICAL REPORT, OR ANY PORTION THEREOF, DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW ANY REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY:
(A)OF ACCURACY, COMPLETENESS, MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE;
(B)THAT THE CONTENTS OF THIS BROADBAND FORUM TECHNICAL REPORT
ARE SUITABLE FOR ANY PURPOSE, EVEN IF THAT PURPOSE IS KNOWN TO
THE COPYRIGHT HOLDER;
(C)THAT THE IMPLEMENTATION OF THE CONTENTS OF THE TECHNICALbusy
REPORT WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
TRADEMARKS OR OTHER RIGHTS.
By using this Broadband Forum Technical Report, urs acknowledge that implementation may require licens to patents. The Broadband Forum encourages but does not require its members to identify such patents. For a list of declarations made by Broadband Forum member companies, plea e www.broadband-forum. No assurance is given that licens to patents necessary to implement this Technical Report will be available for licen at all or on reasonable and non-discriminatory terms.
ANY PERSON HOLDING A COPYRIGHT IN THIS BROADBAND FORUM TECHNICAL REPORT, OR ANY PORTION THEREOF, DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW (A) ANY LIABILITY (INCLUDING DIRECT, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES UNDER ANY LEGAL THEORY) ARISING FROM OR RELATED TO THE USE OF OR RELIANCE UPON THIS TECHNICAL REPORT; AND (B) ANY OBLIGATION TO UPDATE OR CORRECT THIS TECHNICAL REPORT. Broadband Forum Technical Reports may be copied, downloaded, stored on a rver or otherwi re-distributed in their entirety only, and may not be modified without the advance written permission of the Broadband Forum.
The text of this notice must be included in all copies of this Broadband Forum Technical Report.
Issue History
windirIssue Number Issue Date Issue Editor Changes
Original
1 February 2010 Michael Shaffer, Huawei
Technologies Co.,Ltd.
Dave Hood, Ericsson
cjis
北京爱迪国际学校Comments or questions about this Broadband Forum Technical Report should be directed to info@broadband-forum.
Editors: Michael Shaffer Huawei
Dave Hood Ericsson
A&T WG Chairs David Allan Ericsson
BT
Thorne
empire stateDavid
Table of Contents
1PURPOSE AND SCOPE (7)
1.1 P URPOSE (7)
1.2 S COPE (7)
1.3 O UT OF S COPE (8)
2REFERENCES AND TERMINOLOGY (9)
murano2.1 C ONVENTIONS (9)
2.2 R EFERENCES (9)
2.3 D EFINITIONS (10)
2.4 A BBREVIATIONS (11)
3TECHNICAL REPORT IMPACT (13)
3.1 E NERGY EFFICIENCY (13)
3.2 IP V6 (13)
三月 英文3.3 S ECURITY (13)
4FUNDAMENTAL ARCHITECTURAL AND TOPOLOGICAL ASPECTS (14)
4.1 V REFERENCE POINT (15)
4.2 A GGREGATION NETWORK (16)
5VLANS AND QOS (17)
5.1 GPON-FED E THERNET A CCESS NODE VLAN S COPE AND Q O S (17)
5.2 ONU ENTITY VLAN AND Q O S (18)
5.2.1Upstream frame handling (18)
5.2.2Downstream frame mapping (18)
5.3 VLAN AND Q O S REQUIREMENTS (18)
6MULTICAST (22)
6.1 A CCESS NODE MULTICAST (22)
6.2 GPON ONU ENTITY MULTICAST (22)
vitamin6.3 OLT MULTICAST (22)
6.4 M ULTICAST REQUIREMENTS (22)
7FORWARDING INFORMATION AND LOOP DETECTION (SPANNING TREE)24 7.1 GPON FORWARDING INFORMATION AND LOOP AVOIDANCE/REMOVAL (24)
7.2 F ORWARDING I NFORMATION AND L OOP D ETECTION R EQUIREMENTS (24)
8OAM (26)
8.1 A CCESS N ODE OAM (26)
8.2 GPON ONU ENTITY OAM REQUIREMENTS (27)
8.2.1Intra-carrier maintenance level (27)
8.2.2Short intra-carrier maintenance level (wholesale model) (28)
8.2.3Short carrier maintenance level (wholesale model) (29)
苦肉计
9CONFIGURATION MANAGEMENT (30)
9.1 C ONFIGURATION MANAGEMENT REQUIREMENTS (30)
List of Figures
Figure 1 – Network architecture for Ethernet-bad GPON aggregation (14)
Figure 2 – Separation of functions at the V reference point : Upstream (15)
Figure 3 – Separation of Functions at the V Reference Point : Downstream (16)
Figure 4 – GPON-fed Ethernet access node VLAN and QoS management (17)
Figure 5 – Frame mapping for GPON-fed Ethernet access node (18)
Figure 6 – Ethernet OAM model (26)
Figure 7 – Ethernet OAM model - Wholesale (27)
Figure 8 – Configuration Management for GPON-fed Ethernet Access Node (30)
