| Additional information value (octet 3 to octet n) | |
| The coding of the additional information value is dependent on the LCS application. | |
| Access type value (octet 1, bit 1 to bit 2) | |
| Bits
2 1 | |
| 0 1 | 3GPP access |
| 1 0 | Non-3GPP access |
| All other values are reserved. | |
| EAP message (octet 4 to n) | |
| An EAP message as specified in RFC 3748. | |
| Message authentication code (octet 3 to 6) | |
| This field is coded as the Message authentication code information element (see subclause 9.8). | |
| Type of integrity protection algorithm (octet 7, bit 1 to 4) and
type of ciphering algorithm (octet 7, bit 5 to 8) | |
| These fields are coded as the type of integrity protection algorithm and type of ciphering algorithm in the NAS security algorithms information element (see subclause 9.11.3.34). | |
| K_AMF_change_flag (KACF) (octet 8, bit 5) | |
| Bit
5 | |
| 0 | a new KAMF has not been calculated by the network |
| 1 | a new KAMF has been calculated by the network |
| Key set identifier in 5G (octet 8, bit 1 to 3) and
Type of security context flag (TSC) (octet 8, bit 4) | |
| These fields are coded as the NAS key set identifier and type of security context flag in the NAS key set identifier information element (see subclause 9.11.3.32). | |
| Sequence number (octet 9) | |
| This field is coded as the Sequence number information element (see subclause 9.10) | |
| Sequence number (octet 2) | |
| This field is coded as the Sequence number information element (see subclause 9.10). | |
| Length of S-NSSAI contents (octet 2) | |
| This field indicates the length of the included S-NSSAI contents, and it can have the following values. Depending on the value of the length field the following S-NSSAI contents are included: | |
| Bits
8 7 6 5 4 3 2 1 | |
| 0 0 0 0 0 0 0 1 | SST |
| 0 0 0 0 0 0 1 0 | SST and mapped HPLMN SST |
| 0 0 0 0 0 1 0 0 | SST and SD |
| 0 0 0 0 0 1 0 1 | SST, SD and mapped HPLMN SST |
| 0 0 0 0 1 0 0 0 | SST, SD, mapped HPLMN SST and mapped HPLMN SD |
| All other values are reserved. | |
| Slice/service type (SST) (octet 3) | |
| This field contains the 8 bit SST value. The coding of the SST value part is defined in TS 23.003. If this IE is included during the network slice-specific authentication and authorization procedure, this field contains the 8 bit SST value of an S-NSSAI in the S-NSSAI(s) of the HPLMN or the RSNPN. | |
| Slice differentiator (SD) (octet 4 to octet 6) | |
| This field contains the 24 bit SD value. The coding of the SD value part is defined in TS 23.003. If this IE is included during the network slice-specific authentication and authorization procedure, this field contains the 24 bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN or the RSNPN. | |
| If the SST encoded in octet 3 is not associated with a valid SD value, and the sender needs to include a mapped HPLMN SST (octet 7) and a mapped HPLMN SD (octets 8 to 10), then the sender shall set the SD value (octets 4 to 6) to "no SD value associated with the SST". | |
| mapped HPLMN Slice/service type (SST) (octet 7) | |
| This field contains the 8 bit SST value of an S-NSSAI in the S-NSSAI(s) of the HPLMN to which the SST value is mapped. The coding of the SST value part is defined in TS 23.003. | |
| mapped HPLMN Slice differentiator (SD) (octet 8 to octet 10) | |
| This field contains the 24 bit SD value of an S-NSSAI in the S-NSSAI(s) of the HPLMN to which the SD value is mapped. The coding of the SD value part is defined in TS 23.003. | |
|
NOTE 1:
Octet 3 shall always be included.
NOTE 2:
If the octet 4 is included, then octet 5 and octet 6 shall be included.
NOTE 3:
If the octet 7 is included, then octets 8, 9, and 10 may be included.
NOTE 4:
If the octet 8 is included, then octet 9 and octet 10 shall be included.
NOTE 5:
If only HPLMN S-NSSAI or subscribed SNPN S-NSSAI is included, then octets 7 to 10 shall not be included.
|
|
| Message authentication code (octet 3 to 6) | |
| This field is coded as the Message authentication code information element (see subclause 9.8). | |
| Type of integrity protection algorithm (octet 7, bit 1 to 4) and
type of ciphering algorithm (octet 7, bit 5 to 8) | |
| These fields are coded as the type of integrity protection algorithm and type of ciphering algorithm in the NAS security algorithms information element (see subclause 9.11.3.34). | |
| NCC (octet 8, bits 5 to 7) | |
| This field contains the 3 bit Next hop chaining counter (see TS 33.501) | |
| Key set identifier in 5G (octet 8, bit 1 to 3) and
type of security context flag (TSC) (octet 8, bit 4) | |
| These fields are coded as the NAS key set identifier and type of security context flag in the NAS key set identifier information element (see subclause 9.11.3.32). | |
| Octets 9 and 10 are spare and shall be coded as zero. | |
|
NOTE:
In earlier versions of this protocol, octets 9 and 10 can have any value. In this version of the protocol, octets 9 and 10 can always be ignored by the UE.
|