Page 821 - 5G Basics - Core Network Aspects

Transport aspects 2

not exceed 510 bytes. The clear eoc command is shown in Table 11-7 and may be initiated by either FTU;
the peer FTU shall then respond. The clear eoc responses shall be as shown in Table 11-8. The first byte of
either the command or a response shall be the assigned value for the clear eoc command type shown in
Table 11-5. The subsequent bytes of the command shall be as shown in Table 11-7. The subsequent bytes
of the responses shall be as shown in Table 11-8. The bytes shall be sent using the format described in
clause 11.2.2.1.

Table 11-7 – Clear eoc commands sent by the initiating FTU

Name Length (bytes) Byte Content
Request Variable 2 0116 (Note)
3 Segment code (SC)
4 + The information payload of the clear eoc message to
be delivered to the far end.
NOTE – All other values for byte 2 are reserved by ITU-T.

Table 11-8 – Clear eoc responses sent by the responding FTU

Name Length (bytes) Byte Content
ACK 2 2 8016 (Note)
NACK 3 2 8116 (Note)
3 0416 – Not supported (Note)

NOTE – All other values for bytes 2 and 3 are reserved by ITU-T
Upon reception of a clear eoc information payload (up to 510 bytes in length) over the γ_MGMT reference
point from the near-end ME, the FTU shall initiate a clear eoc command (up to 513 bytes in length) based
on its priority defined in Table 11-5. The clear eoc command may be segmented. Upon reception of a clear
eoc command, the FTU shall respond with an acknowledgement (ACK) and deliver the information payload
(up to 510 bytes in length) of the received clear eoc command over the γ_MGMT reference point to the
near-end ME transparently, with the original formatting used by the far-end ME of the initiating FTU. The
FTU may instead respond with a negative acknowledgment (NACK) including the not supported (value 0416)
reason code, indicating that the received information payload of the clear eoc command cannot be
delivered to the near-end ME (e.g., because the near-end ME may not support clear eoc messages). Other
reason codes are for further study.

11.2.2.4.2 Datagram eoc command
The datagram eoc command is used to transfer management data between the ME-O and ME-R of the
FTU-O and FTU-R, respectively. The datagram eoc command carries the management data as an
information payload. This information payload is generated by the upper-layer ME and passed to the FME
over the γ_MGMT reference point (see clause 11.1). The size of the information payload shall not exceed
1018 bytes. The datagram eoc command is shown in Table 11-8.1 and may be initiated by either FTU. No
response to the datagram eoc command shall be sent by the peer FTU. The first byte of the command shall
be the assigned value for the datagram eoc command type shown in Table 11-6. The subsequent bytes of
the command shall be as shown in Table 11-8.1. The bytes shall be sent using the format described in
clause 11.2.2.1.

811