Documente Academic
Documente Profesional
Documente Cultură
Outline
PON benefits PON architecture Fiber optic basics PON physical layer PON user plane PON control plane
PON benefits
Why fiber ?
todays high data rate networks are all based on optical fiber the reason is simple (examples for demonstration sake) twisted copper pair(s)
8 Mbps @ 3 km, 1.5 Mbps @ 5.5 km (ADSL) 1 Gb @ 100 meters (802.3ab)
microwave
70 Mbps @ 30 km (WiMax)
coax
10 Mbps @ 3.6 km (10BROAD36) 30 Mbps @ 30 km (cable modem)
optical fiber
10 Mbps @ 2 km (10BASE-FL) 100 Mbps @ 400m (100BASE-FX) 1 Gbps @ 2km (1000BASE-LX) 10 Gbps @ 40 (80) km (10GBASE-E(Z)R) 40 Gbps @ 700 km [Nortel] or 3000 km [Verizon]
so fiber beats coax by about 2 orders of magnitude noise ingress and cross-talk copper couples to all nearby conductors no similar ingress mechanism for fiber
e.g. 10 dB/km for thin coax at 50MHz, 0.15 dB/km l =1550nm fiber
ground-potential, galvanic isolation, lightning protection copper can be hard to handle and dangerous no concerns for fiber
access
core
core
feeder fiber
N end users
core
N end users
access network
An obvious solution
deploy intermediate switches (active) switch located at curb or in basement saves space at central office need 2 N + 2 optical transceivers
core
feeder fiber
N end users
core
feeder fiber
PON advantages
shared infrastructure translates to lower cost per customer minimal number of optical transceivers feeder fiber and transceiver costs divided by N customers greenfield per-customer cost similar to UTP passive splitters translate to lower cost can be installed anywhere no power needed essentially unlimited MTBF fiber data-rates can be upgraded as technology improves initially 155 Mbps then 622 Mbps now 1.25 Gbps soon 2.5 Gbps and higher
PON architecture
Terminology
like every other field, PON technology has its own terminology the CO head-end is called an OLT ONUs are the CPE devices (sometimes called ONTs in ITU) the entire fiber tree (incl. feeder, splitters, distribution fibers) is an ODN all trees emanating from the same OLT form an OAN downstream is from OLT to ONU (upstream is the opposite direction) downstream upstream
NNI
core
PON types
many types of PONs have been defined APON ATM PON BPON Broadband PON GPON Gigabit PON EPON Ethernet PON GEPON Gigabit Ethernet PON CPON CDMA PON WPON WDM PON
Bibliography
BPON is explained in ITU-T G.983.x GPON is explained in ITU-T G.984.x EPON is explained in IEEE 802.3-2005 clauses 64 and 65
(but other 802.3 clauses are also needed)
Warning
do not believe white papers from vendors
especially not with respect to GPON/EPON comparisons
GPON
BPON
EPON
PON principles
(almost) all PON types obey the same basic principles OLT and ONU consist of Layer 2 (Ethernet MAC, ATM adapter, etc.) optical transceiver using different ls for transmit and receive
optionally: Wavelength Division Multiplexer
downstream transmission OLT broadcasts data downstream to all ONUs in ODN ONU captures data destined for its address, discards all other data encryption needed to ensure privacy upstream transmission ONUs share bandwidth using Time Division Multiple Access OLT manages the ONU timeslots ranging is performed to determine ONU-OLT propagation time additional functionality Physical Layer OAM Autodiscovery Dynamic Bandwidth Allocation
PON has a unique architecture (broadcast) point-to-multipoint in DS direction (multiple access) multipoint-to-point in US direction
contrast that with, for example Ethernet - multipoint-to-multipoint ATM - point-to-point This means that existing protocols
do not provide all the needed functionality e.g. receive filtering, ranging, security, BW allocation
downstream upstream
(multi)point - to - (multi)point
PON encapsulation
The majority of PON traffic is Ethernet So EPON enthusiasts say
use EPON - it's just Ethernet
That's true by definition anything in 802.3 is Ethernet and EPON is defined in clauses 64 and 65 of 802.3-2005
But don't be fooled - all PON methods encapsulate MAC frames EPON and GPON differ in the contents of the header
EPON hides the new header inside the GbE preamble GPON can also carry non-Ethernet payloads
PON header
DA
SA
data
FCS
GPON history
= sin 1(n2/n1)
V =c/n
t = Ln/c
Single-mode Fiber
Sources of Dispersion
Total Dispersion
Multimode Dispersion Chromatic Dispersion
Material Dispersion
Multimode Dispersion
1 1
Graded-index Dispersion
1 1
1 0 1
Single-Mode Dispersion
1 1
Tc = Dmat * l * L
For Laser 1550nm Fabry Perot
Spectral Characteristics
LASER/laser diode: Light Amplification by Stimulated Emission of Radiation. Done of the wide range of devices that generates light by that principle. Laser light is directional, covers a narrow range of wavelengths, and is more coherent than ordinary light. Semiconductor diode lasers are the standard light sources in fiber optic systems. Lasers emit light by stimulated emission.
Laser
Light Detectors
PIN DIODES (PD) - Operation simular to LEDs, but in reverse, photon are converted to electrons
AVALANCHE PHOTODIODES (APD) - Use more complex design and higher operating voltage than PIN diodes to produce amplification effect - Significantly more sensitive than PIN diodes - More complex design increases cost - Used for long-haul/higher bit rate systems
Wavelength-Division Multiplexing
WDM Duplexing
OLT = Optical Line Termination ONU = Optical Network Unit BMCDR = Burst Mode Clock Data Recovery
Burst-Mode CDR
Sampling
Hysteresis
Optical Splitters
Budget Calculations
LB
= PS - PO
Assume:
l allocations - G.983.1
Upstream and downstream directions need about the same bandwidth US serves N customers, so it needs N times the BW of each customer
but each customer can only transmit 1/N of the time
In APON and early BPON work it was decided that 100 nm was needed Where should these bands be placed for best results? In the second and third windows ! Upstream 1260 - 1360 nm (1310 50) second window
DS
1500 nm 1600 nm
l allocations - G.983.3
Afterwards it became clear that there was a need for additional DS bands Pressing needs were broadcast video and data Where could these new DS bands be placed ?
1270
1490
1630
US
1200 nm 1300 nm 1400 nm
DS
1500 nm
l allocations - final
US
1200 nm 1300 nm 1400 nm
DS
1500 nm 1600 nm
GPON
EPON 10GEPON
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
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
However, 1000 Mbps is expanded to 1250 Mbps 10GbE uses a different linecode - 64B/66B
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)
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
US timing diagram
grant
inter-ONU guard
grant
data
laser turn-off laser turn-on lock laser turn-off
data
laser turn-on lock
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
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
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
ONU
VP
T-CONT
VP Port Port
PON
ONU
T-CONT
VC VC VC VC
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
GTC frame
PCBd payload PCBd
scrambled
125 msec
PCBd payload
payload
PSync (4B)
Ident (4B)
PLOAMd (13B)
BIP (1B)
ATM partition
GEM partition
US BW map (N*8B)
GPON payloads
GTC payload potentially has 2 sections:
ATM partition (Alen * 53 bytes in length) GEM partition (now preferred method)
PCBd ATM cell ATM cell
ATM cell
GEM frame
GEM frame
GEM frame
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
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)
PTI (3b)
HEC (13b)
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.
GEM fragmentation
GEM can fragment its payload For example
unfragmented Ethernet frame PLI PLI PLI ID ID ID PTI=001 HEC DA PTI=000 HEC DA PTI=001 HEC SA SA data2 T T data1 FCS data FCS fragmented Ethernet frame
GEM frag 1
PCBd
ATM partition
GEM frag 2
GEM frame
large frag 1
PCBd
ATM partition
urgent frame
large frag 2
PCBd
We saw that the PCBd is
PSync (4B) Ident (4B)
B6AB31E0
PLOAMd
(13B)
BIP
(1B)
PLend
(4B)
PLend
(4B)
US BW map
(N*8B)
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)
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)
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)
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
US allocation example
DS frame PCBd payload
BWmap
US frame
preamble + delimiter
guard time
scrambled
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)
Security
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
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
QoS
Principles
GPON uses PLOAMd and PLOAMu as control channel PLOAM are incorporated in regular (data-carrying) frames Standard ITU control mechanism
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
guard times left between timeslots each ONU transmits with the proper delay to avoid overlap delay computed during a ranging process
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)
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
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)
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
GPON autodiscovery
Failure recovery
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
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
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