Академический Документы
Профессиональный Документы
Культура Документы
work in progress
Amd 1
Amd 2
GPON
PONs Slide 58
Reach and splits
Reach and the number of ONUs supported are contradictory design goals
In addition to physical reach derived from optical budget
there is logical reach limited by protocol concerns (e.g. ranging protocol)
and differential reach (distance between nearest and farthest ONUs)
The number of ONUs supported depends not only on the number of splits
but also on the addressing scheme
BPON called for 20 km and 32-64 ONUs
GPON allows 64-128 splits and the reach is usually 20 km
but there is a low-cost 10 km mode (using Fabry-Perot laser diodes in ONUs)
and a long physical reach 60 km mode with 20 km differential reach
EPON allows 16-256 splits (originally designed for link budget of 24 dB, but now 30 dB)
and has 10 km and 20 km Physical Media Dependent sublayers
PONs Slide 59
Line codes
BPON and GPON use a simple NRZ linecode (high is 1 and low is 0)
An I.432-style scrambling operation is applied to payload (not to PON overhead)
Preferable to conventional scrambler because no error propagation
each standard and each direction use different LFSRs
LFSR initialized with all ones
LFSR sequence is XOR'ed with data before transmission
EPON uses the 802.3z (1000BASE-X) line code - 8B/10B
Every 8 data bits are converted into 10 bits before transmission
DC removal and timing recovery ensured by mapping
Special function codes (e.g. idle, start_of_packet, end_of_packet, etc)
However, 1000 Mbps is expanded to 1250 Mbps
10GbE uses a different linecode - 64B/66B
PONs Slide 60
FEC
G984.3 clause 13 and 802.3-2005 subclause 65.2.3
define an optional G.709-style Reed-Solomon code
Use (255,239,8) systematic RS code designed for submarine fiber (G.975)
to every 239 data bytes add 16 parity bytes to make 255 byte FEC block
Up to 8 byte errors can be corrected
Improves power budget by over 3 dB,
allowing increased reach or additional splits
Use of FEC is negotiated between OLT and ONU
Since code is systematic
can use in environment where some ONUs do not support FEC
In GPON FEC frames are aligned with PON frames
In EPON FEC frames are marked using K-codes
(and need 8B10B decode - FEC - 8B10B encode)
PONs Slide 61
More physical layer problems
Near-far problem
OLT needs to know signal strength to set decision threshold
If large distance between near/far ONUs, then very different attenuations
If radically different received signal strength can't use a single threshold
EPON: measure received power of ONU at beginning of burst
GPON: OLT feedback to ONUs to properly set transmit power
Burst laser problem
Spontaneous emission noise from nearby ONU lasers causes interference
Electrically shut ONU laser off when not transmitting
But lasers have long warm-up time
and ONU lasers must stabilize quickly after being turned on
PONs Slide 62
US timing diagram
How does the ONU US transmission appear to the OLT ?
grant grant
laser
turn-on
laser
turn-off
data
l
o
c
k
laser
turn-on
laser
turn-off
data
l
o
c
k
inter-ONU
guard
Notes:
GPON - ONU reports turn-on and turn-off times to OLT
ONU preamble length set by OLT
EPON - long lock time as need to Automatic Gain Control and Clock/Data Recovery
long inter-ONU guard due to AGC-reset
Ethernet preamble is part of data
PONs Slide 63
PON User plane
PONs Slide 64
How does it work?
ONU stores client data in large buffers (ingress queues)
ONU sends a high-speed burst upon receiving a grant/allocation
Ranging must be performed for ONU to transmit at the right time
DBA - OLT allocates BW according to ONU queue levels
OLT identifies ONU traffic by label
OLT extracts traffic units and passes to network
OLT receives traffic from network and encapsulates into PON frames
OLT prefixes with ONU label and broadcasts
ONU receives all packets and filters according to label
ONU extracts traffic units and passes to client
PONs Slide 65
Labels
In an ODN there is 1 OLT, but many ONUs
ONUs must somehow be labeled for
OLT to identify the destination ONU
ONU to identify itself as the source
EPON assigns a single label Logical Link ID to each ONU (15b)
GPON has several levels of labels
ONU_ID (1B) (1B)
Transmission-CONTainer (AKA Alloc_ID) (12b) (can be >1 T-CONT per ONU)
For ATM mode
VPI
VCI
For GEM mode
Port_ID (12b) (12b)
PON
ONU
ONU
T-CONT
T-CONT
Port
Port
VP
VP
VC
VC
VC
VC
PONs Slide 66
DS GPON format
GPON Transmission Convergence frames are always 125 msec long
19440 bytes / frame for 1244.16 rate
38880 bytes / frame for 2488.32 rate
Each GTC frame consists of Physical Control Block downstream + payload
PCBd contains sync, OAM, DBA info, etc.
payload may have ATM and GEM partitions (either one or both)
payload PCBd payload PCBd payload PCBd
GTC frame
PSync (4B) Ident (4B) PLOAMd (13B) BIP (1B)
PLend (4B) PLend (4B) US BW map (N*8B)
ATM
partition
GEM
partition
scrambled 125 msec
PONs Slide 67
GPON payloads
GTC payload potentially has 2 sections:
ATM partition (Alen * 53 bytes in length)
GEM partition (now preferred method)
ATM partition
Alen (12 bits) is specified in the PCBd
Alen specifies the number of 53B cells in the ATM partition
if Alen=0 then no ATM partition
if Alen=payload length / 53 then no GEM partition
ATM cells are aligned to GTC frame
ONUs accept ATM cells based on VPI in ATM header
GEM partition
Unlike ATM cells, GEM delineated frames may have any length
Any number of GEM frames may be contained in the GEM partition
ONUs accept GEM frames based on 12b Port-ID in GEM header
ATM cell PCBd
GEM frame GEM frame
GEM frame ATM cell ATM cell
PONs Slide 68
GPON Encapsulation Mode
A common complaint against BPON was inefficiency due to ATM cell tax
GEM is similar to ATM
constant-size HEC-protected header
but avoids large overhead by allowing variable length frames
GEM is generic any packet type (and even TDM) supported
GEM supports fragmentation and reassembly
GEM is based on GFP, and the header contains the following fields:
Payload Length Indicator - payload length in Bytes
Port ID - identifies the target ONU
Payload Type Indicator (GEM OAM, congestion/fragmentation indication)
Header Error Correction field (BCH(39,12,2) code+ 1b even parity)
The GEM header is XOR'ed with B6AB31E055 before transmission
Port ID
(12b)
PLI
(12b)
HEC
(13b)
PTI
(3b)
payload fragment
(L Bytes)
5 B
PONs Slide 69
Ethernet / TDM over GEM
When transporting Ethernet traffic over GEM:
only MAC frame is encapsulated (no preamble, SFD, EFD)
MAC frame may be fragmented (see next slide)
When transporting TDM traffic over GEM:
TDM input buffer polled every 125 msec.
PLI bytes of TDM are inserted into payload field
length of TDM fragment may vary by 1 Byte due to frequency offset
round-trip latency bounded by 3 msec.
DA SA T data FCS PLI
Ethernet over GEM
ID PTI HEC
PLI Bytes of TDM PLI
TDM over GEM
ID PTI HEC
PONs Slide 70
GEM fragmentation
GEM can fragment its payload
For example
GEM fragments payloads for either of two reasons:
GEM frame may not straddle GTC frame
GEM frame may be pre-empted for delay-sensitive data
DA SA T data FCS PLI
unfragmented Ethernet frame
ID PTI=001 HEC
DA SA T data
1
PLI
fragmented Ethernet frame
ID PTI=000 HEC
data
2
PLI ID PTI=001 HEC FCS
ATM partition PCBd GEM frame
GEM frag 1 ATM partition PCBd GEM frag 2
GEM frame
ATM partition PCBd urgent frame
large frag 1 ATM partition PCBd urgent frame
large frag 2
PONs Slide 71
PCBd
We saw that the PCBd is
PSync - fixed pattern used by ONU to located start of GTC frame
Ident - MSB indicates if FEC is used, 30 LSBs are superframe counter
PLOAMd - carries OAM, ranging, alerts, activation messages, etc.
BIP - SONET/SDH-style Bit Interleaved Parity of all bytes since last BIP
PLend (transmitted twice for robustness) -
Blen - 12 MSB are length of BW map in units of 8 Bytes
Alen - Next 12 bits are length of ATM partition in cells
CRC - final 8 bits are CRC over Blen and Alen
US BW map - array of Blen 8B structures granting BW to US flow
will discuss later (DBA)
PSync
(4B)
Ident
(4B)
PLOAMd
(13B)
BIP
(1B)
PLend
(4B)
PLend
(4B)
US BW map
(N*8B)
B6AB31E0
PONs Slide 72
GPON US considerations
GTC fames are still 125 msec long, but shared amongst ONUs
Each ONU transmits a burst of data
using timing acquired by locking onto OLT signal
according to time allocation sent by OLT in BWmap
there may be multiple allocations to single ONU
OLT computes DBA by monitoring traffic status (buffers)
of ONUs and knowing priorities
at power level requested by OLT (3 levels)
this enables OLT to use avalanche photodiodes which are
sensitive to high power bursts
leaving a guard time from previous ONU's transmission
prefixing a preamble to enable OLT to acquire power and phase
identifying itself (ONU-ID) in addition to traffic IDs (VPI, Port-ID)
scrambling data (but not preamble/delimiter)
PONs Slide 73
US GPON format
4 different US overhead types:
Physical Layer Overhead upstream
always sent by ONU when taking over from another ONU
contains preamble and delimiter (lengths set by OLT in PLOAMd)
BIP (1B), ONU-ID (1B), and Indication of real-time status (1B)
PLOAM upstream (13B) - messaging with PLOAMd
Power Levelling Sequence upstream (120B)
used during power-set and power-change to help set ONU
power so that OLT sees similar power from all ONUs
Dynamic Bandwidth Report upstream
sends traffic status to OLT in order to enable DBA computation
PLOu PLOAMd PLSu DBRu payload
if all OH types are present:
PONs Slide 74
US allocation example
BWmap sent by OLT to ONUs is a list of
ONU allocation IDs
flags (not shown above) tell if use FEC, which US OHs to use, etc.
start and stop times (16b fields, in Bytes from beginning of US frame)
payload PCBd
DS frame
Alloc-ID SStart SStop Alloc-ID SStart Sstop Alloc-ID SStart SStop BWmap
US frame
guard
time
preamble
+
delimiter
scrambled
PONs Slide 75
EPON format
EPON operation is based on the Ethernet MAC
and EPON frames are based on GbE frames
but extensions are needed
clause 64 - MultiPoint Control Protocol PDUs
this is the control protocol implementing the required logic
clause 65 - point-to-point emulation (reconciliation)
this makes the EPON look like a point-to-point link
and EPON MACs have some special constraints
instead of CSMA/CD they transmit when granted
time through MAC stack must be constant ( 16 bit durations)
accurate local time must be maintained
PONs Slide 76
EPON header
Standard Ethernet starts with an essentially content-free 8B preamble
7B of alternating ones and zeros 10101010
1B of SFD 10101011
In order to hide the new PON header
EPON overwrites some of the preamble bytes
LLID field contains
MODE (1b)
always 0 for ONU
0 for OLT unicast, 1 for OLT multicast/broadcast
actual Logical Link ID (15b)
Identifies registered ONUs
7FFF for broadcast
CRC protects from SLD (byte 3) through LLID (byte 7)
10101010 10101010 10101010 10101010 10101010 10101010 10101010 10101011
10101010 10101010 10101011 10101010 10101010 LLID LLID CRC
PONs Slide 77
MPC PDU format
MultiPoint Control Protocol frames are untagged MAC frames
with the same format as PAUSE frames
Ethertype = 8808
Opcodes (2B) - presently defined:
GATE/REPORT/REGISTER_REQ/REGISTER/REGISTER_ACK
Timestamp is 32b, 16 ns resolution
conveys the sender's time at time of MPCPDU transmission
Data field is needed for some messages
DA SA L/T Opcode timestamp data / RES / pad FCS
PONs Slide 78
Security
DS traffic is broadcast to all ONUs, so encryption is essential
easy for a malicious user to reprogram ONU to capture desired frames
US traffic not seen by other ONUs, so encryption is not needed
do not take fiber-tappers into account
EPON does not provide any standard encryption method
can supplement with IPsec or MACsec
many vendors have added proprietary AES-based mechanisms
in China special China Telecom encryption algorithm
BPON used a mechanism called churning
Churning was a low cost hardware solution (24b key)
with several security flaws
engine was linear - simple known-text attack
24b key turned out to be derivable in 512 tries
So G.983.3 added AES support - now used in GPON
PONs Slide 79
GPON encryption
OLT encrypts using AES-128 in counter mode
Only payload is encrypted (not ATM or GEM headers)
Encryption blocks aligned to GTC frame
Counter is shared by OLT and all ONUs
46b = 16b intra-frame + 30 bits inter-frame
intra-frame counter increments every 4 data bytes
reset to zero at beginning of DS GTC frame
OLT and each ONU must agree on a unique symmetric key
OLT asks ONU for a password (in PLOAMd)
ONU sends password US in the clear (in PLOAMu)
key sent 3 times for robustness
OLT informs ONU of precise time to start using new key
PONs Slide 80
QoS - EPON
Many PON applications require high QoS (e.g. IPTV)
EPON leaves QoS to higher layers
VLAN tags
P bits or DiffServ DSCP
In addition, there is a crucial difference between LLID and Port-ID
there is always 1 LLID per ONU
there is 1 Port-ID per input port - there may be many per ONU
this makes port-based QoS simple to implement at PON layer
RT BE EF
GPON
PONs Slide 81
QoS - GPON
GPON treats QoS explicitly
constant length frames facilitate QoS for time-sensitive applications
5 types of Transmission CONTainers
type 1 - fixed BW
type 2 - assured BW
type 3 - allocated BW + non-assured BW
type 4 - best effort
type 5 - superset of all of the above
GEM adds several PON-layer QoS features
fragmentation enables pre-emption of large low-priority frames
PLI - explicit packet length can be used by queuing algorithms
PTI bits carry congestion indications
PONs Slide 82
PON control plane
PONs Slide 83
Principles
GPON uses PLOAMd and PLOAMu as control channel
PLOAM are incorporated in regular (data-carrying) frames
Standard ITU control mechanism
EPON uses MPCP PDUs
Standard IEEE control mechanism
EPON control model - OLT is master, ONU is slave
OLT sends GATE PDUs DS to ONU
ONU sends REPORT PDUs US to OLT
PONs Slide 84
Ranging
Upstream traffic is TDMA
Were all ONUs equidistant, and were all to have a common clock
then each would simply transmit in its assigned timeslot
But otherwise the signals will overlap
To eliminate overlap
guard times left between timeslots
each ONU transmits with the proper delay to avoid overlap
delay computed during a ranging process
PONs Slide 85
Ranging background
In order for the ONU to transmit at the correct time
the delay between ONU transmission and OLT reception
needs to be known (explicitly or implicitly)
Need to assign an equalization-delay
The more accurately it is known
the smaller the guard time that needs to be left
and thus the higher the efficiency
Assumptions behind the ranging methods used:
can not assume US delay is equal to DS delay
delays are not constant
due to temperature changes and component aging
GPON: ONUs not time synchronized accurately enough
EPON: ONUs are accurately time synchronized (std contains jitter masks)
with time offset by OLT-ONU propagation time
PONs Slide 86
GPON ranging method
Two types of ranging
initial ranging
only performed at ONU boot-up or upon ONU discovery
must be performed before ONU transmits first time
continuous ranging
performed continuously to compensate for delay changes
OLT initiates coarse ranging by stopping allocations to all other ONUs
thus when new ONU transmits, it will be in the clear
OLT instructs the new ONU to transmit (via PLOAMd)
OLT measures phase of ONU burst in GTC frame
OLT sends equalization delay to ONU (in PLOAMd)
During normal operation OLT monitors ONU burst phase
If drift is detected OLT sends new equalization delay to ONU (in PLOAMd)
PONs Slide 87
EPON ranging method
All ONUs are synchronized to absolute time (wall-clock)
When an ONU receives an MPCPDU from OLT
it sets its clock according to the OLT's timestamp
When the OLT receives an MPCPDU in response to its MPCPDU
it computes a "round-trip time" RTT (without handling times)
it informs the ONU of RTT, which is used to compute transmit delay
RTT = (T2-T0) - (T1-T0) = T2-T1
OLT compensates all grants by RTT before sending
Either ONU or OLT can detect that timestamp drift exceeds threshold
time
OLT sends MPCPDU
Timestamp = T0
ONU receives MPCPDU
Sets clock to T0
ONU sends MPCPDU
Timestamp = T1
OLT receives MPCPDU
RTT = T2 - T1
T0 OLT time T2
T0 ONU time T1
PONs Slide 88
Autodiscovery
OLT needs to know with which ONUs it is communicating
This can be established via NMS
but even then need to setup physical layer parameters
PONs employ autodiscovery mechanism to automate
discovery of existence of ONU
acquisition of identity
allocation of identifier
acquisition of ONU capabilities
measure physical layer parameters
agree on parameters (e.g. watchdog timers)
Autodiscovery procedures are complex (and uninteresting)
so we will only mention highlights
PONs Slide 89
GPON autodiscovery
Every ONU has an 8B serial number (4B vendor code + 4B SN)
SN of ONUs in OAN may be configured by NMS, or
SN may be learnt from ONU in discovery phase
ONU activation may be triggered by
Operator command
Periodic polling by OLT
OLT searching for previously operational ONU
G.984.3 differentiates between three cases:
cold PON / cold ONU
warm PON / cold ONU
warm PON / warm ONU
Main steps in procedure:
ONU sets power based on DS message
OLT sends a Serial_Number request to all unregistered ONUs
ONU responds
OLT assigns 1B ONU-ID and sends to ONU
ranging is performed
ONU is operational
PONs Slide 90
EPON autodiscovery
OLT periodically transmits DISCOVERY GATE messages
ONU waits for DISCOVERY GATE to be broadcast by OLT
DISCOVERY GATE message defines discovery window
start time and duration
ONU transmits REGISTER_REQ PDU using random offset in window
OLT receives request
registers ONU
assigns LLID
bonds MAC to LLID
performs ranging computation
OLT sends REGISTER to ONU
OLT sends standard GATE to ONU
ONU responds with REGISTER_ACK
ONU goes into operational mode - waits for grants
PONs Slide 91
Failure recovery
PONs must be able to handle various failure states
GPON
if ONU detects LOS or LOF it goes into POPUP state
it stops sending traffic US
OLT detects LOS for ONU
if there is a pre-ranged backup fiber then switch-over
EPON
during normal operation ONU REPORTs reset OLT's watchdog timer
similarly, OLT must send GATES periodically (even if empty ones)
if OLT's watchdog timer for ONU times out
ONU is deregistered
PONs Slide 92
Dynamic Bandwidth Allocation
MANs and WANs have relatively stationary BW requirements
due to aggregation of large number of sources
But each ONU in a PON may serve only 1 or a small number of users
So BW required is highly variable
It would be inefficient to statically assign the same BW to each ONU
So PONs assign dynamically BW according to need
The need can be discovered
by passively observing the traffic from the ONU
by ONU sending reports as to state of its ingress queues
The goals of a Dynamic Bandwidth Allocation algorithm are
maximum fiber BW utilization
fairness and respect of priority
minimum delay introduced
PONs Slide 93
GPON DBA
DBA is at the T-CONT level, not port or VC/VP
GPON can use traffic monitoring (passive) or status reporting (active)
There are three different status reporting methods
status in PLOu - one bit for each T-CONT type
piggy-back reports in DBRu - 3 different formats:
quantity of data waiting in buffers,
separation of data with peak and sustained rate tokens
nonlinear coding of data according to T-CONT type and tokens
ONU report in DBA payload - select T-CONT states
OLT may use any DBA algorithm
OLT sends allocations in US BW map
PONs Slide 94
EPON DBA
OLT sends GATE messages to ONUs
flags include DISCOVERY and Force_Report
Force_Report tells the ONU to issue a report
Reports represent the length of each queue at time of report
OLT may use any algorithm to decide how to send the following grants
DA SA 8808 Opcode=0002 timestamp Ngrants/flags grants
DA SA 8808 Opcode=0003 timestamp Nqueue_sets Reports
GATE message
REPORT message