Page 968 - 5G Basics - Core Network Aspects

2 Transport aspects

Support of CIpolicy = 0 is mandatory.

The CIpolicy parameter values other than 0 are reserved for use by the ITU-T.

a) b)
NDR_max NDR

b)
ETR

a)
ETR_min_eoc

Achievable NDR
No connect 1) Maximize NDR 2) Maximize margin until MAXSNRM
Failed Init 3) Minimize excess-margin
a) Control parameters
b) Test parameters G.9701(14)-Cor.1(15)_F12-14

Figure 12-14 – Illustration of CIpolicy = 0

12.4 Loop diagnostics mode
For further study.

13 Online reconfiguration (OLR)

13.1 Overview

13.1.1 Types of online reconfiguration

Types of OLR include seamless rate adaptation (SRA), bit swapping, transmitter initiated gain adjustment
(TIGA), RMC parameter adjustment (RPA), fast rate adaptation (FRA), and L2 transmission schedule
adaptation (L2TSA).
Seamless rate adaptation (SRA) is used to reconfigure the NDR by modifying the bits and gains (bi, gi), the
data frame parameters (BDR, BD), and the DTU size (parameters KFEC, RFEC and Q). This SRA procedure is not
applicable to the RMC. SRA is a mandatory capability. The procedures for SRA are defined in clause 13.2.1.1
and shall be implemented using OLR request types 1 and 2 eoc commands defined in Table 11-9.

Bit swapping is used to reallocate the bits and transmit power among the allowed subcarriers without
changing the total number of data bytes loaded onto a data symbol, BD. Bit swapping reconfigures the bits
and gains (bi, gi) without changing any other PMD or PMS-TC control parameters. Bit swapping is a
mandatory capability. The procedure for bit swapping shall be implemented using OLR request types 1 and
2 eoc commands defined in Table 11-9. The bit swapping procedure is not applicable to the RMC tone set; a
similar feature for the RMC tone set is implemented by using RPA.

Transmitter-initiated gain adjustment (TIGA) provides the VCE means to address changes in the
downstream precoded direct channel gain (e.g., due to a change in the precoder). TIGA is a mandatory
capability. The procedure for TIGA is defined in clause 13.2.2.1 and shall be implemented using the OLR
request type 3 eoc command defined in Table 11-9.

958