Page 962 - 5G Basics - Core Network Aspects

2 Transport aspects

Field 1 "Message descriptor" is a unique one-byte code (8916) that identifies the message. See Table 12-7
for a complete list of codes.

Field 2 "Bit-loading table for data symbol" contains the bi values for every subcarrier in MEDLEYds. The bi
shall indicate the number of bits to be mapped by the FTU-O to subcarrier i.

The bi shall only be defined for subcarriers from the MEDLEYds set (as indicated in O-PRM message), and
shall be sent in ascending order of subcarrier index i.

Each bi value shall be represented as an unsigned 4-bit integer with valid range from 0 to 12. Pairs of bis
shall be packed into bytes in the same way as in the bit-loading table field of O-PMD message
(see Table 12-52).

Field 3 "Number of RMC DS subcarriers (NSCRds)" indicates the number of subcarriers assigned for
downstream RMC symbol represented as an unsigned integer. The valid range is from 1 to 512.

Field 4 "Downstream RMC tone set (RTSds)" indicates the indices of the subcarriers used to encode the
RMC in the downstream direction. Each subcarrier index shall be represented as a 12-bit value. Pairs of
subcarrier indices shall be mapped to a field of three bytes. For example, if the value of the nth field is
40020016, rsc2n−1 = 20016 = 512 and rsc2n = 40016 = 1 024. If the number of subcarriers in the RTSus set is odd,
the last 12 bits of the field shall be set to ZERO (and ignored by the receiver). The first encoded value shall
correspond to the lowest subcarrier used to encode the RMC. The remaining indices shall be sent in
increasing frequency order. The subcarriers for RTSds shall be selected from the MEDLEYds set.
Field 5 "Bit-loading table for RMC DS subcarriers" contains the bi values for every subcarrier in the
downstream RMC subcarrier set presented in field 4 of the R-PMD message. The bi shall indicate the
number of bits to be mapped by the FTU-O to the subcarrier i. The bi values shall be sent in ascending order
of subcarrier indices i. Each bi value shall be represented as an unsigned 4-bit integer with valid values of
0 and from 2 to 6.
Field 6 "Tone ordering table" contains the tone ordering table t for the downstream direction. The tone
ordering table contains the order in which the subcarriers shall be assigned bits in the downstream
direction. The table shall include all subcarriers of the MEDLEYds set and only these subcarriers. Each
subcarrier index shall be represented as a 12-bit value. Pairs of subcarrier indices shall be mapped to a field
of three bytes. For example, if the value of the nth field is 40020016, t2n−1 = 20016 = 512 and t2n = 40016 =
1 024. If the number of subcarriers in the MEDLEYds set is odd, the last 12 bits of the field shall be set to
ZERO (and ignored by the receiver). The value of the first index sent shall be equal to the index of the first
entry in the tone ordering table (t1, see clause 10.2.1.2). The remaining indices shall be sent in increasing
order of the tone ordering table t entries (t2, t3, ... tNSCds).
Field 7 "Showtime pilot tones" indicates the selection of pilot tones that the FTU-R intends to use during
the showtime. The field shall be formatted as a tone descriptor, as shown in Table 12-34.
The FTU-R shall only select a tone as a pilot tone if the bit loading for that tone, as given in the bit-loading
table (field 2), is equal to zero. The showtime pilot tones shall be modulated as specified in clause 10.2.2.3.
The total number of showtime pilot tones shall not exceed 16.

Field 8 "Initialization status":
If, within the constraints of the channel initialization policies defined in clause 12.3.7, the receiver is unable
to select a set of configuration parameters, the "Initialization success/failure code" indicates the
initialization failure cause. If, within the constraints of the channel initialization policies defined in clause
12.3.7, the receiver is able to select a set of configuration parameters, the "Initialization success/failure
code" indicates the initialization success. Valid “Initialization success/failure codes” are as follows:
8016: Initialization success;
8116: Configuration error;

8216: Configuration not feasible on line;
0016: Feature not supported.

952