Page 902 - 5G Basics - Core Network Aspects

2 Transport aspects

Table 12-7 – Message codes for the SOC messages

SOC message Message code The rest of the payload
O/R-REPEAT_REQUEST 5516 (Note)

O/R-ACK-SEG 0F16 (Note)
FTU-O messages
O-SIGNATURE 0016 see clause 12.3.3.2.1
O-TG-UPDATE 0116 see clause 12.3.3.2.2
O-UPDATE 0216 see clause 12.3.3.2.4
O-VECTOR-FEEDBACK 0316 see clause 12.3.3.2.6
O-SNR 0416 see clause 12.3.3.2.9

O-PRM 0516 see clause 12.3.3.2.11
O-MSG 1 0716 see clause 12.3.4.2.1
O-TPS 0816 see clause 12.3.4.2.3
O-PMS 0916 see clause 12.3.4.2.5
O-PMD 0A16 see clause 12.3.4.2.7
O-ACK (Note) 0B16 See clause 12.3.4.2.9
FTU-R messages

R-MSG 1 8016 see clause 12.3.3.2.3
R-UPDATE 8116 see clause 12.3.3.2.5
R-ACK (Note) 8216 see clause 12.3.3.2.7
R-VECTOR-FEEDBACK 8316 see clause 12.3.3.2.8
R-SNR 8416 see clause 12.3.3.2.10
R-PRM 8516 see clause 12.3.3.2.12
R-MSG 2 8616 see clause 12.3.4.2.2
R-ACK 1 (Note) 8716 See clause 12.3.4.2.4
R-PMS 8816 see clause 12.3.4.2.6
R-PMD 8916 see clause 12.3.4.2.8

NOTE – This is a one-byte message.
12.2.4.2 O/R-REPEAT_REQUEST

This message shall be used in RQ mode to request the remote side to resend the last unacknowledged
message (segment), as described in clause 12.2.2.2. The format of the message shall be as specified in
clause 12.2.1, and the payload shall be as specified in Table 12-7.

In AR and NR modes, O/R-REPEAT_REQUEST messages shall be ignored.
12.2.4.3 O/R-ACK-SEG

This message shall be used in RQ mode to acknowledge the reception of intermediate segments of a
segmented message, as described in clause 12.2.2.2. The format of the message shall be as specified in
clause 12.2.1 and the payload shall be as specified in Table 12-7.
In AR and NR modes, and when no segmentation is used in RQ mode, any O/R-ACK-SEG messages shall be
ignored.

892