Page 1042 - 5G Basics - Core Network Aspects

2 Transport aspects

X.7.1.1 Handshake – FTU-O

See clause 12.3.2.1.
X.7.1.1.1 CL messages

See clause 12.3.2.1.1. For operation with Annex X, the FTU-O shall include the following fields in the CL
message of ITU-T G.994.1:

Table X.5 – FTU-O CL message NPar(2) bit definitions for Annex X operation

ITU-T G.994.1 NPar(2) bit Definition of NPar(2) bit
Annex X operation If set to ZERO, indicates that FTU-O does not support operation according to Annex X. If
set to ONE, indicates that the FTU-O supports operation according to Annex X.

Table X.6 – FTU-O CL message SPar(2) bit definitions

ITU-T G.994.1 SPar(2) bit Definition of Spar(2) bit
DTA_min_DRMCds2us Always set to ZERO.

Table X.7 – FTU-O CL message Npar(3) bit definitions

G.994.1 SPar(2) Bit Definition of Npar(3) bits
Profiles Each valid profile is represented by one bit in a field of 6 bits. The valid profiles are:
106a, 106b, 106c, 212a and 212c. Profiles 106c and 212c shall only be indicated if the
NPar(2) bit "Annex X operation" is set to ONE. Each profile supported by the FTU-O is
indicated by setting its corresponding bit to ONE.

X.7.1.1.2 MS messages
See clause 12.3.2.1.2. For operation with Annex X, the FTU-O shall include the following fields in the MS
message of ITU-T G.994.1:

Table X.8 – FTU-O MS message NPar(2) bit definitions

ITU-T G.994.1 NPar(2) bit Definition of NPar(2) bit
Annex X operation Set to ONE if and only if this bit is set to ONE in both the last previous capabilities list
request (CLR) message and the last previous CL message. If set to ONE, both the FTU-O
and the FTU-R shall enable Annex X operation.

Table X.9 – FTU-O MS message SPar(2) bit definitions

ITU-T G.994.1 SPar(2) bit Definition of SPar(2) bit
DTA_min_DRMCds2us Always set to ZERO.

1032