Page 1018 - 5G Basics - Core Network Aspects

2 Transport aspects

S.5.7 End software download

The format of this command is similar to that of the start software download message.

Table S.10 – End software download message

Field Byte 7 6 5 4 3 2 1 0 Comments
Datagram protocol 1 0 0 0 0 0 0 0 1 NT software management = 0116
identifier
Transaction correlation 2-3
identifier
Message type 4 0 1 0 1 0 1 0 1 AR = 1, AK = 0, MT = 21
Action = end software download.

Managed software 5 Software image instance
image instance 0 instance 0

1 instance 1
2..254 vendor-specific use
255 reserved by ITU-T
Message contents 6-7 Length of message contents field in bytes
length = 8 (Note 1).
Message contents 8-11 CRC-32, computed over all bytes of the
software image, as specified in
[ITU-T I.363.5].

12-15 Image size in bytes (Note 2).
NOTE 1 – This field shall be coded as an unsigned integer on 16 bits [b 15 … b 0], where b 0 is the LSB. Byte 6 shall represent [b 15 …
b 8] and byte 7 shall represent [b 7 … b 0].
NOTE 2 – This value shall be coded as an unsigned integer on 32 bits [b 31 … b 0], where b 0 is the LSB. Byte 12 shall represent [b 31
… b 24] and byte 15 shall represent [b 7 … b 0].

S.5.8 End software download response

The response message informs the DPU whether the download command was successful. Byte 8 reports
the result of the process, and indicates device busy as long as the instances is busy writing the image to a
non-volatile store. Once the NT has stored all images successfully, it responds to continued end software
download commands with a 0 in byte 8.

1008