Page 1022 - 5G Basics - Core Network Aspects

2 Transport aspects

Table S.14 – Commit image message

Field Byte 7 6 5 4 3 2 1 0 Comments

Message contents 6-7 Length of message contents field in
length bytes = 0 (Note).

NOTE – 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].

S.5.12 Commit image response

Table S.15 – Commit image response 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 0 1 1 0 1 1 1 AR = 0, AK = 1, MT = 23
Action = commit image response.

Managed software 5 Software image instance
image instance 0 first instance

1 second instance
2..254 vendor-specific use
Message contents 6-7 Length of message contents field in bytes
length = 1 (Note).
Message contents 8 0 0 0 0 x x x x Result, reason
0000 command processed successfully
0001 command processing error
0010 command not supported
0011 parameter error
0100 reserved by ITU-T
0101 unknown managed software
image instance
0110 device busy
NOTE – 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].

S.6 Software upgrade (informative)
S.6.1 Overview

The software image management is specified in clause S.4. The NT creates two software image instances, 0
and 1. Each image has three Boolean attributes: committed, active and valid. An image is valid if the
contents have been verified to be an executable code image. An image is committed if it will be loaded and
executed upon reboot of the NT. An image is active if it is currently loaded and executing in the NT. At any
given time, at most one image may be active and at most one image may be committed.
An NT goes through a series of states to download and activate a software image as shown in Figure S.3.
Each state is determined by the status of both software images. For example, S3 is the state where both
images are valid but only image 0 is committed and active. State S0 is a conceptual initialization state.

1012