2016/11/01

GPON - EPON Comparison–轉載

引言

本文轉載自CommScope的GPON - EPON Comparison白皮書;未附插圖,詳參原文。



內文


Passive Optical Networking (PON) technology has been available since the mid 1990s. Significant development activities occurred during the early 2000s to develop Gigabit rate solutions designed to deliver Ethernet and IP services. Two very different solutions were developed by the IEEE and ITU-T, EPON and GPON respectively. While the general concepts (PON operation, ODN framework, wavelength plan, and application) are the same for both EPON and GPON, their operation is very different, as are the features and services supported by each. EPON is a native Ethernet solution that leverages the features, compatibility and performance of the Ethernet protocol, while GPON leveraged the techniques of SONET/SDH and GFP (Generic Framing Protocol) to transport Ethernet.

Introduction

PON standardization activities have been ongoing for the last fifteen years within the ITU-T and IEEE standards bodies. EPON and 10G-EPON are the latest ratified IEEE standards and GPON the latest ratified ITU-T standard. Figure 1 shows some of the key historical milestones:
Initial PON offerings in the early and mid 1990s were based on ATM framing (APON, BPON). With the explosion of Internet and Intranet based traffic in the years following, ATM-based BPON systems proved to be very inefficient, as the vast majority of traffic through the access network consisted of variable length IP traffic. This became the catalyst for the development of a pure-Ethernet based PON (EPON), taking advantage of emerging QOS-aware Gigabit Ethernet (GbE) switch silicon, evolving Ethernet standards (VLANs, prioritization, OAM) and cost-effective integration with other Ethernet equipment.
Development of the Gigabit-capable Passive Optical Network (GPON) standard started after proposals by FSAN members (Quantum Bridge et. al) for a dual Gigabit speed ATM/Ethernet PON solution were not able to gain support within the IEEE 802.3ah work groups and decided to continue this work within the ITU.
EPON and GPON both draw heavily from G.983, the BPON standard for their general concepts (PON operation, ODN framework, wavelength plan, and application). Also, both were designed to better accommodate variable length IP frames at Gigabit line rates. There are, however, significant differences in the approaches used by each.

Protocol Fundamentals

EPON is based upon IEEE 802.3 Ethernet that was modified to support Point-to-Multipoint (P2MP) connectivity. Ethernet traffic is transported natively and all Ethernet Features are fully supported. GPON on the other hand is fundamentally a transport protocol, wherein Ethernet services are adapted at the OLT and ONT Ethernet interfaces and carried over an agnostic synchronous framing structure from end to end.

Framing /Service Adaption

The GPON Transmission Convergence (GTC) layer is responsible for mapping service specific interfaces (e.g. Ethernet) into a common, service-agnostic framework.
Ethernet frames are encapsulated into GTC Encapsulation Method (GEM) frames, which have a GFP-like format (derived from Generic Frame Procedure ITU G.7401). GEM frames are in turn encapsulated into a SONET/SDH like GTC frame (in both upstream as downstream direction) that is transported synchronously every 125 μsec over the PON.
In contrast, EPON carries Ethernet frames natively on the PON with no changes or modifications. There is no need for extra adaption and encapsulation.

Basic Operation

As shown above, EPON is an IEEE Ethernet architecture. Its downstream media access control (MAC) works in the same manner as a standard GbE MAC, where all Ethernet traffic is broadcast. Optical splitters are used to passively divide the same downstream signal among each of the ONT end points.
Upstream the Ethernet MAC has been modified by the IEEE to support time division multiple access (TDMA) scheduling. The upstream Ethernet bandwidth (before 8B/10B coding) is scheduled for use by each of the ONT end points using a TDMA algorithm controlled by the OLT. The full bandwidth is available to each endpoint for the duration of its scheduled time. Dynamic Bandwidth Allocation (DBA) algorithms are implemented by vendors to dynamically change the allocation for each ONU based on the amount of traffic it has queued to send.
As shown in Figure 7, GPON is a synchronous transport network architecture. It’s downstream media access control (MAC) is derived from GFP-framed SONET, whereby it operates on a fixed time base of 125 μsecs and time division multiplexing (TDM) is used to divide the bandwidth to the 32 ONTs. Because it is synchronous in nature, idle characters are inserted whenever no asynchronous Ethernet traffic is available. Optical splitters passively split the same downstream signal to each of the 32 ONU end points.
Upstream, time division multiple access (TDMA) scheduling is used and incoming Ethernet traffic is again encapsulated and mapped into a 1.2 Gbps synchronous framed signal in a similar manner to the downstream.

Service Hierarchy

Since PON is P2MP in nature, the OLT must be able to uniquely identify and communicate with each ONT. EPON uses a Logical Link ID (LLID) to uniquely address an ONT. In addition, VLAN_IDs are used for further addressing in order to deliver VLAN based services. In the downstream direction, the OLT attaches the LLID to the preamble of the frame to identify the destination ONT.
In GPON, one or more Traffic Containers (T-CONT) is created between the OLT and an ONT. This T-CONT allows for the emulation of a point-to-point virtual connection between the OLT and ONT and the subsequent TDM multiplexing of the downstream bandwidth between T-CONTs. Within each T-CONT there can exist multiple Port IDs to identify individual ONT ports within a single ONT.

Bandwidth Allocation

The use of TDMA in the upstream direction requires the OLT to schedule each ONTs transmission to avoid collisions. Fundamentally each ONT receives a Grant telling it when to begin and end transmission. In GPON Grants are scheduled per T-CONT; in EPON per LLID. In the case of GPON, Grants are carried in the downstream frame header. A map field within the header specifies the specific T-CONT, Start and End {Alloc-ID+Start+End} for each granted upstream Window (timeslot).
In EPON, Grant messages are sent per-LLID, as separate MAC-Control client frames (GATEs), in-between regular Ethernet frames. Each Grant specifies the {LLID+Start+Length}.

Dynamic Bandwidth Allocation (DBA)

Optionally, both GPON and EPON support DBA. This is used for real-time variation of timeslot allocation to ONTs, which increases throughput as a function of upstream demand.

Control Messages

In GPON there are three different types of control messages: OMCI, OAM, and PLOAM. Their roles are shown in the table below.
In contrast EPON utilizes IEEE 802.3ah OAM messages for Provisioning, Fault Isolation and Performance Monitoring in conjunction with SNMP sets & gets through IETF MIBs. Additional control messages are MPCP GATEs/REPORTs for BW granting.

ONT Discovery & Activation

Both EPON and GPON support automatic ONT discovery and activation mechanisms. GPON uses the Serial Number (SN) for ONT authentication. There are two methods for activating ONTs.
• Method-A -- The SN of the ONT is registered in advance at the OLT by the Operator
• Method-B -- The SN of the ONT is not registered at the OLT by the Operator/EMS.
Method-B requires an automatic detection mechanism of the SN. In case a new ONT is detected, an ONT-ID is assigned and the ONT is activated.
Traditionally EPON does not authenticate via the SN, but instead uses the ONT MAC Address in order to assign an LLID. However, some vendor specific EPON implementations optionally utilize the ONT’s SN.

Encryption

Both EPON and GPON supports AES-128bit encryption. For GPON, Key management messages are exchanged via PLOAM cells. Upon request by the OLT, the ONT sends a new key three times. Once received, the OLT toggles a bit in the GTC header to initiate a key switch. For EPON, Key management messages are either via a management VLAN or via IEEE 802.3ah OAM messages depending on vendor implementation.

Bandwidth and Efficiency

Probably the most heralded claim of GPON vendors is the fact that it is 2.448 Gbps in the downstream direction and 1.24416 Gbps in the upstream direction, whereas EPON is symmetrical 1.25 Gbps (1.0 Gbps prior to 8B/10B coding). Efficiency has to be considered in both directions of a PON. Each PON protocol introduces its own overhead in either direction. Overall PON efficiency is a function of protocol encapsulation and scheduling efficiencies. In the downstream direction, protocol overhead should be negligible. In the upstream direction the total scheduling overhead within EPON is between 2.92% and 9.67%. In other words, EPON efficiency is 90.33% to 97.08% compared to a GbE point-to-point link. In the downstream direction, EPON efficiency reaches 97.13% to 98.92% of the efficiency of a point-to-point 1GbE link. While GPON in GEM mode can achieve ~ 95% efficiency of its usable bandwidth. It should be noted that, optionally, EPON can be operated in what is typically termed ‘turbo mode’. With turbo mode, the downstream EPON data rate is doubled to 2.5Gbps, thus enabling bandwidth throughput comparable to GPON.

Ethernet Service Support

Ethernet Features

Since EPON is an IEEE Ethernet standard and utilizes Ethernet switches within its silicon, it can natively support all of the 802.1 and 802.3 features of Ethernet including VLAN tags, prioritization, OAM … etc. All ethernet services can be natively delivered in a manner identical to what is done with switched Ethernet today.
Since GPON only defines the transport of Ethernet frames there is no native Ethernet functionality. Ethernet switches must be placed either in front of or within GPON OLTs and ONTs to provide any additional Ethernet capabilities. Capabilities are thus unique to each manufacturer’s implementation.

Bridging

Since the cross connect at the GPON OLT is not an Ethernet switch, GPON cannot support standard Ethernet Bridging. Thus, in order to support standard bridging, there would be the need for an Ethernet switch upstream of the OLT cross-connect, either in an aggregation point in the same chassis, or externally.

Transparent LAN Services (TLS)

TLS is achieved via VLAN tunneling on Ethernet switches. Without these in the GPON OLT chassis, one would need to use external Ethernet switches in order to achieve the same result. The GEM cross-connect cannot inspect VLANs in order to make the appropriate forwarding decisions.

Conclusion

Both EPON and GPON recognized the need to evolve PON to being a Gigabit capable solution for transporting Ethernet and IP traffic. Their implementations, while utilizing a common optical infrastructure, are very different in execution. EPON extended native Ethernet to support the PON P2MP architecture, while GPON looked to techniques similar to GFP framed SONET/SDH to create an efficient Ethernet Transport mechanism.

參考文獻

原文 http://www.commscope.com/catalog/doc/pdf/7438/GPON_EPON_Comparison_White_Paper.pdf

沒有留言:

張貼留言