01-07 Key GPON Techniques
01-07 Key GPON Techniques
Ranging Principles
Ranging process is as follows:
l The OLT starts ranging for an ONU when the ONU registers with the OLT for the first
time and obtains the round trip delay (RTD) of the ONU. Based on the RTD, the OLT
calculates the physical reach of this ONU.
l The OLT specifies a proper equalization delay (EqD) for the ONU based on the physical
reach.
NOTE
The OLT requires a quiet zone during ranging to pause the upstream transmission channel of the ONUs
connected to it. The quiet zone is implemented by emptying BWmap so that no timeslot is allocated for data
transmission.
Ranging Results
RTD and EqD synchronize data frames sent by all ONUs, preventing data conflict on optical
splitters. In this way, all ONUs locate at the same logic reach and they send data at specified
timeslots, thereby preventing upstream cell conflict.
Ranging can be implemented to prevent cells transmitted by different ONUs from conflicting
with each other on the OLT. However, the ranging accuracy is ± 1 bit and the cells transmitted
by different ONUs have a protection time of several bits (not a multiple of 1 bit). If the ONU
optical modules do not support the burst receive and transmit function, the transmitted signals
overlap and distortion occurs.
NOTE
In the GPON system, all data is broadcast downstream to ONUs. The transmission requires OLT optical
modules to transmit optical signals continuously and ONU optical modules to receive optical signals
continuously. Therefore, in GPON downstream direction, the OLT optical modules are not required to
support the burst transmit function, the ONU optical modules are not required to support the burst
receive function.
l The distance from each ONU to the OLT varies and therefore the optical signal
attenuation varies for each ONU. As a result, the power and level of packets received by
an OLT at different timeslots various.
l If the OLT optical modules do not support the burst receive and transmit function, an
error occurs when the optical signals sent by the ONU with a long transmission distance
and large optical attenuation are recovered on the OLT because the optical power level is
less than the threshold (only the signals with the optical power level greater than the
threshold can be recovered). Dynamic threshold adjustment enables the OLT to
dynamically adjust the threshold for optical power levels based on the strengths of
signals received by the OLT. This ensures that all ONU signals can be recovered.
A mechanism for upstream GPON traffic management has been a primary focus in
standardization of GPON traffic management. To resolve the problem, ITU-T
Recommendation G.984.3 is developed, which defines the DBA protocol for managing
upstream PON traffic.
DBA enables the OLT to monitor congestion on the PON network in real time. Then, the OLT
can dynamically adjust bandwidths based on congestion, bandwidth usages, and
configurations. DBA supports the following functions:
l Improves upstream bandwidth usages on a PON port.
l Supports more users on a PON port.
l Provides higher bandwidths for users, especially the services with significant bandwidth
bursts.
l The embedded DBA module of an OLT continuously collects DBA reports, performs
calculation, and uses the BWMap field in the downstream frame to notify the ONU of
the DBA calculation result.
l According to the BWMap information, the ONUs send data upstream in the timeslots
allocated to them, and occupy the upstream bandwidth. Therefore, each ONU
dynamically adjusts its upstream bandwidth according to its actually transmitted data
traffic, improving upstream bandwidth usage.
Bandwidth can also be allocated in static mode, or fixed mode. In this mode, an OLT
periodically allocates a fixed bandwidth to each ONU based on the ONU's service level
agreement (SLA), bandwidth, and delay indicators.
l In fixed mode, an OLT uses a polling mechanism. The bandwidths allocated to ONUs
may vary but the bandwidth allocated to each ONU is the same in each polling period.
The bandwidth guarantee depends on an ONU's SLA but not on its upstream service
traffic. An ONU is allocated a fixed bandwidth even carrying no upstream services.
l The allocation mode is simple and applies to services, such as TDM, that have a fixed
traffic, but does not apply to IP services that have burst requirements on bandwidth. If
the mode applies to the IP services, the upstream bandwidth usage is low because the
upstream bandwidth cannot be adjusted dynamically based on the upstream service
traffic.
To resolve the preceding issue, an error correction technology is required. Among the error
correction technologies, the effective ones achieve transmission reliability by reducing
bandwidth usages, which also increases telecom device complexity. The error correction
technologies are used for controlling errors. The codes involved in these technologies are
classified as error detection codes and error correction codes based on usage scenarios.
l Error detection codes, such as parity check codes, are used for detecting error codes.
l Error correction codes, such as BCH codes, Reed-Solomon (RS) codes, and Hamming
codes, are used for automatically correcting errors.
The only difference between the error detection codes and error correction codes lies in
performance parameters applied in different usage scenarios. FEC uses error correction codes.
FEC is a data coding technology, which enables the RX end to check error bits in transmission
based on the coding data. FEC is unidirectional, not supporting error information feedback.
Redundant codes are added to signals on the TX end. Then, the RX end checks the signals for
errors based on error-correcting code (ECC) and corrects errors is there is any. Common FEC
codes include Hamming codes, RS codes, and convolutional codes. Figure 7-6 shows FEC
principles.
In the GPON FEC algorithm, the most common RS code RS (255,239) is used, where the
code word is 255 bytes long, consisting of 239 data bytes followed by 16 overhead redundant
bytes. RS code RS (255,239) complies with ITU-T Recommendation G.984.3. The FEC
algorithm drops the bit error rate (BER) of 10-3 to 10-12 for GPON lines. However, due to
the overhead caused by multi-frame tail fragments, the bandwidth throughput of the GPON
system with FEC enabled is about 90% of that with FEC disabled.
FEC status can be configured in GPON systems based on GPON ports in the downstream
direction (by running the port fec command) and based on ONUs in the upstream direction.
To configure the FEC status in the upstream direction based on ONUs, run either of the
following commands:
l In profile mode, run the fec-upstream command.
l In discrete mode, run the ont fec-upstream command.
Line encryption is used to eliminate these security risks. The GPON system uses the
Advanced Encryption Standard 128 (AES128) algorithm to encrypt the data packets
transmitted in plaintext mode so that the packets are transmitted in ciphertext mode,
improving system security. Enable line encryption if the usage scenarios promote high
security requirements.
l The line encryption algorithms used in GPON systems neither increase overhead nor
decrease bandwidth usages.
l The line encryption algorithms will not prolong transmission delays.
l Due to length limitation on PLOAM messages, the ONU sends the key to the OLT in two pieces and
sends both parts of the key three times for extra redundancy. If the OLT is unsuccessful in receiving either
part of the key all three times it is transmitted, the OLT initiates a key exchange request to the ONU again
until the OLT receives the same key for three times.
l The OLT issues a command three times to the ONU to notify the ONU of using the frame number of the
new key. The ONU switches the verification key on data frames after receiving the command only once.
Configuration Method
l In GPON systems, run either of the following commands to configure line encryption
status based on GEM ports (excluding multicast and broadcast GEM ports).
– In profile mode, run the gem add command.
Overview
The OLT supports the pre-configuration of the service flow creation policy on the PON port.
When the ONU that meets conditions goes online, registration and service flow creation are
automatically implemented based on the pre-configured policy. This function simplifies the
configuration process and improves the installation and deployment efficiency.
NOTE
The ONU ID is configured during the pre-configuration of the service flow creation policy. When the
ONU starts to register with the OLT, the ONU ID and vendor identity are verified. Only the ONU
meeting conditions can implement automatic registration.
O&M for these automatically created service flows is the same as that for commonly created
service flows.
NOTE
Automatic registration and service flow creation are supported in the PON profile mode only. They are
not supported in the distributed mode.
Figure 7-8 Process of automatic service flow creation (no ONU is manually added)
Figure 7-9 Process of automatic service flow creation (the ONU is manually added)
When auto-confirm is set to enable, you do not need to run the ont confirm command on the
GPON port to confirm the ONU. When auto-confirm is set to disable, you need to run the ont
confirm command on the GPON port.
2. Configure the automatic service flow creation policy.
Run the auto-service-port
command to configure the automatic service flow creation policy.
For details about how to configure automatic service flow creation, see "Configuring
Automatic Service Flow Creation (GPON)."
Automatic Migration
When the ONU automatic migration function is enabled, if a PON port or fiber is faulty, the
ONU connected to this faulty PON port is migrated to another PON port. If the ONU
automatic adding policy is met, the ONU is automatically removed from the original PON
port, and then added to the new PON port. In this process, the OLT does not report the SN
authentication conflict alarm. The ONU connected to the original PON port must meet the
following conditions:
l The ONU is offline.
l The ONU supports OMCI management.
l The ONU is not a member of the type C protection group.
l The ONU supports SN authentication.
NOTE
Automatic migration and aging are supported in the PON profile mode only. They are not supported in
the disperse mode.
Automatic Aging
When an offline ONU is aged and meets automatic adding policy, the OLT automatically
deletes the aged ONU to save resources. The ONU automatic aging period can be configured.
The value range is 1–365. The default value is no-aging, which indicates no aging. For an
aged ONU that meets the automatic adding policy, it will be automatically registered after
being powered on.