Page 830 - 5G Basics - Core Network Aspects

2 Transport aspects

Table 11-20 – Reason codes for FTU responses

Byte Applicable to Applicable to Applicable to Applicable to Applicable to
Reason value reject OLR reject OLR reject OLR reject OLR reject OLR
(Note 1) request type 1 request type 2 request type 3 request type 4 request type 5
Busy 0116 Yes Yes No No No
Invalid 0216 Yes Yes Yes Yes Yes
parameters
Missing 0316 Yes Yes Yes Yes N/A
segments
Wait 0416 Yes Yes No No No
(Note 2)
NOTE 1 – All other reason codes are reserved by ITU-T.
NOTE 2 – With this reason code, the FTU shall wait at least 1 second before initiating a new eoc-based OLR procedure.

11.2.2.6 Diagnostic commands and responses

The diagnostic commands shall be used to control the FTU diagnostic capabilities defined in this clause. The
diagnostic commands shown in Table 11-21 may be initiated only by the FTU-O. The diagnostic commands
shown in Table 11-22 may be initiated only by the FTU-R. The responses are shown in Table 11-23. All
diagnostic commands and responses shall consist of two or three bytes. The first byte shall be the assigned
value for the diagnostic command type, as shown in Table 11-5. For commands, the second byte shall be as
shown in Table 11-21. For responses, the second and third bytes shall be as shown in Table 11-23. The
bytes shall be sent using the format described in clause 11.2.2.1.

Table 11-21 – Diagnostic commands sent by the FTU-O

Name Length (bytes) Byte Content
Perform self-test 2 2 0116 (Note)
Update test parameters 2 2 0216 (Note)
Start RTX_TESTMODE 2 2 0316 (Note)
End RTX_TESTMODE 2 2 0416 (Note)

Start TPS_TESTMODE 2 2 0516 (Note)
End TPS_TESTMODE 2 2 0616 (Note)
NOTE – All other values for byte 2 are reserved by ITU-T.

Table 11-22 – Diagnostic commands sent by the FTU-R

Name Length (bytes) Byte Content
Update test parameters 2 2 0216 (Note)
NOTE – All other values for byte 2 are reserved by ITU-T.

820