3GPP 24.501 v20.0.0 — the document's own text
9.11.3.4 5GS mobile identity
Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).
The purpose of the 5GS mobile identity information element is to provide either the SUCI, the 5G-GUTI, the IMEI, the IMEISV, the 5G-S-TMSI, the MAC address or the EUI-64.
The 5GS mobile identity information element is coded as shown in figures 9.11.3.4.1, 9.11.3.4.2, 9.11.3.4.3, 9.11.3.4.4, 9.11.3.4.5, 9.11.3.4.6, 9.11.3.4.8 and 9.11.3.4.7, and table 9.11.3.4.1.
The 5GS mobile identity is a type 6 information element with a minimum length of 4.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GS mobile identity IEI | octet 1 | |||||||
| Length of 5GS mobile identity contents | octet 2octet 3 | |||||||
| 1 | 1 | 1 | 1 | 0spare | Type of identity | octet 4 | ||
| MCC digit 2 | MCC digit 1 | octet 5 | ||||||
| MNC digit 3 | MCC digit 3 | octet 6 | ||||||
| MNC digit 2 | MNC digit 1 | octet 7 | ||||||
| AMF Region ID | octet 8 | |||||||
| AMF Set ID | octet 9 | |||||||
| AMF Set ID (continued) | AMF Pointer | octet 10 | ||||||
| 5G-TMSI | octet 11 | |||||||
| 5G-TMSI (continued) | octet 12 | |||||||
| 5G-TMSI (continued) | octet 13 | |||||||
| 5G-TMSI (continued) | octet 14 |
Figure 9.11.3.4.1: 5GS mobile identity information element for type of identity "5G-GUTI"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GS mobile identity IEI | octet 1 | |||||||
| Length of 5GS mobile identity contents | octet 2octet 3 | |||||||
| Identity digit 1 | Odd/even indication | Type of identity | octet 4 | |||||
| Identity digit p+1 | Identity digit p | octet 5* |
Figure 9.11.3.4.2: 5GS mobile identity information element for type of identity "IMEI" or "IMEISV"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GS mobile identity IEI | octet 1 | |||||||
| Length of 5GS mobile identity contents | octet 2octet 3 | |||||||
| 0spare | SUPI format | 0spare | Type of identity | octet 4 | ||||
| MCC digit 2 | MCC digit 1 | octet 5 | ||||||
| MNC digit 3 | MCC digit 3 | octet 6 | ||||||
| MNC digit 2 | MNC digit 1 | octet 7 | ||||||
| Routing indicator digit 2 | Routing indicator digit 1 | octet 8 | ||||||
| Routing indicator digit 4 | Routing indicator digit 3 | octet 9 | ||||||
| 0Spare | 0Spare | 0Spare | 0Spare | Protection scheme Id | octet 10 | |||
| Home network public key identifier | octet 11 | |||||||
| Scheme output | octet 12 - x |
Figure 9.11.3.4.3: 5GS mobile identity information element for type of identity "SUCI" and SUPI format "IMSI"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| MSIN digit 2 | MSIN digit 1 | octet 12 | ||||||
| … | ||||||||
| MSIN digit n+1 | MSIN digit n | octet x |
Figure 9.11.3.4.3a: Scheme output for type of identity "SUCI", SUPI format "IMSI" and Protection scheme Id "Null scheme"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GS mobile identity IEI | octet 1 | |||||||
| Length of 5GS mobile identity contents | octet 2octet 3 | |||||||
| 0Spare | SUPI format | 0Spare | Type of identity | octet 4 | ||||
| SUCI NAI | octet 5 - y |
Figure 9.11.3.4.4: 5GS mobile identity information element for type of identity "SUCI" and SUPI format "Network specific identifier", "GCI" or "GLI"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GS mobile identity IEI | octet 1 | |||||||
| Length of 5GS mobile identity contents | octet 2octet 3 | |||||||
| 1 | 1 | 1 | 1 | 0spare | Type of identity | octet 4 | ||
| AMF Set ID | octet 5 | |||||||
| AMF Set ID (continued) | AMF Pointer | octet 6 | ||||||
| 5G-TMSI | octet 7 | |||||||
| 5G-TMSI (continued) | octet 8 | |||||||
| 5G-TMSI (continued) | octet 9 | |||||||
| 5G-TMSI (continued) | octet 10 |
Figure 9.11.3.4.5: 5GS mobile identity information element for type of identity "5G-S-TMSI"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GS mobile identity IEI | octet 1 | |||||||
| Length of 5GS mobile identity contents | octet 2octet 3 | |||||||
| 0 | 0 | 0 | 0 | 0 | Type of identity | octet 4 | ||
| spare |
Figure 9.11.3.4.6: 5GS mobile identity information element for type of identity "No identity"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GS mobile identity IEI | octet 1 | |||||||
| Length of 5GS mobile identity contents | octet 2octet 3 | |||||||
| 0spare | 0spare | 0spare | 0spare | MAURI | Type of identity | octet 4 | ||
| MAC address | octet 5octet 10 |
Figure 9.11.3.4.7: 5GS mobile identity information element for type of identity "MAC address"
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| 5GS mobile identity IEI | octet 1 | |||||||
| Length of 5GS mobile identity contents | octet 2octet 3 | |||||||
| 0spare | 0spare | 0spare | 0spare | 0spare | Type of identity | octet 4 | ||
| EUI-64 | octet 5octet 12 |
Figure 9.11.3.4.8: 5GS mobile identity information element for type of identity "EUI-64"
Table 9.11.3.4.1: 5GS mobile identity information element
| Type of identity (octet 4 bits 1 to 3)Bits | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| 3 | 2 | 1 | |||||||
| 0 | 0 | 0 | No identity (see NOTE 1) | ||||||
| 0 | 0 | 1 | SUCI | ||||||
| 0 | 1 | 0 | 5G-GUTI | ||||||
| 0 | 1 | 1 | IMEI | ||||||
| 1 | 0 | 0 | 5G-S-TMSI | ||||||
| 1 | 0 | 1 | IMEISV | ||||||
| 1 | 1 | 0 | MAC address | ||||||
| 1 | 1 | 1 | EUI-64 | ||||||
| Odd/even indication (octet 4 bit 4)Bit | |||||||||
| 4 | |||||||||
| 0 | even number of identity digits | ||||||||
| 1 | odd number of identity digits | ||||||||
| For the 5G-GUTI, then bits 5 to 8 of octet 4 are coded as "1111", octet 5 through 7 contain the MCC and MNC values as specified below, octet 8 through 10 contain the AMF Region ID, the AMF Set ID and the AMF Pointer values and octet 11 through 14 contain the 5G-TMSI as defined in 3GPP TS 23.003 [4]. | |||||||||
| MCC, Mobile country code (octet 5, octet 6 bits 1 to 4)The MCC field is coded as in ITU-T Recommendation E.212 [42], annex A. | |||||||||
| MNC, Mobile network code (octet 6 bits 5 to 8, octet 7)The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. If a network operator decides to use only two digits in the MNC, bits 5 to 8 of octet 6 shall be coded as "1111".The MCC and MNC digits are coded as octets 6 to 8 of the Temporary mobile group identity IE in figure 10.5.154 of 3GPP TS 24.008 [12]. | |||||||||
| AMF Region ID (octet 8)This field contains the binary encoding of the AMF Region ID. Bit 8 of octet 7 is the most significant bit and bit 1 of octet 7 is the least significant bit.AMF Set ID (octet 9, octet 10 bits 7 to 8)This field contains the binary encoding of the AMF Set ID. Bit 8 of octet 9 is the most significant bit and bit 7 of octet 10 is the least significant bit.AMF Pointer (octet 10 bits 1 to 6)This field contains the binary encoding of the AMF Pointer. Bit 6 of octet 9 is the most significant bit and bit 1 of octet 9 is the least significant bit.5G-TMSI (octet 11 to 14)Bit 8 of octet 11 is the most significant bit and bit 1 of octet 14 is the least significant bit. | |||||||||
| Identity digit (octet 4 bits 5 to 8, octet 5 etc.) | |||||||||
| For the IMEI, Identity digit field is coded using BCD coding. If the number of identity digits is even then bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". The format of the IMEI is described in 3GPP TS 23.003 [4]. | |||||||||
| For the IMEISV, Identity digit field is coded using BCD coding. Bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". The format of the IMEISV is described in 3GPP TS 23.003 [4]. | |||||||||
| For the SUCI, bit 8 of octet 4 is spare and shall be coded as zero. Bits 5-7 of octet 4 contain the SUPI format and are coded as shown below. | |||||||||
| SUPI format (octet 4, bits 5-7)Bits | |||||||||
| 7 | 6 | 5 | |||||||
| 0 | 0 | 0 | IMSI | ||||||
| 0 | 0 | 1 | Network specific identifier | ||||||
| 0 | 1 | 0 | GCI | ||||||
| 0 | 1 | 1 | GLI | ||||||
| All other values are interpreted as IMSI by this version of the protocol. | |||||||||
| For the SUCI with SUPI format "IMSI", octets 5 through 7 contain the MCC and MNC values as specified below. For subsequent fields, bit 8 of octet 8 is the most significant bit and bit 1 of the last octet the least significant bit. The required fields for the SUCI are as defined in 3GPP TS 23.003 [4]. | |||||||||
| MCC, Mobile country code (octet 5, octet 6 bits 1 to 4)The MCC field is coded as in ITU-T Recommendation E.212 [42], annex A. | |||||||||
| MNC, Mobile network code (octet 6 bits 5 to 8, octet 7)The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. If a network operator decides to use only two digits in the MNC, bits 5 to 8 of octet 6 shall be coded as "1111".The MCC and MNC digits are coded as octets 6 to 8 of the Temporary mobile group identity IE in figure 10.5.154 of 3GPP TS 24.008 [12]. | |||||||||
| Routing indicator (octets 8-9)Routing Indicator shall consist of 1 to 4 digits. The coding of this field is the responsibility of home network operator but BCD coding shall be used. If a network operator decides to assign less than 4 digits to Routing Indicator, the remaining digits shall be coded as "1111" to fill the 4 digits coding of Routing Indicator (see NOTE 2). If no Routing Indicator is configured in the USIM or the ME, the UE shall code bits 1 to 4 of octet 8 of the Routing Indicator as "0000" and the remaining digits as "1111". | |||||||||
| Protection scheme identifier (octet 10 bits 1 to 4) | |||||||||
| Bits | |||||||||
| 4 | 3 | 2 | 1 | ||||||
| 0 | 0 | 0 | 0 | Null scheme | |||||
| 0 | 0 | 0 | 1 | ECIES scheme profile A | |||||
| 0 | 0 | 1 | 0 | ECIES scheme profile B | |||||
| 0 | 0 | 1 | 1 | ||||||
| to | Reserved | ||||||||
| 1 | 0 | 1 | 1 | ||||||
| 1 | 1 | 0 | 0 | ||||||
| to | Operator-specific protection scheme | ||||||||
| 1 | 1 | 1 | 1 | ||||||
| Bits 5-8 of octet 10 are spare and shall be coded as zero. | |||||||||
| Home network public key identifier (octet 11) | |||||||||
| The Home network public key identifier (PKI) field is coded as defined in 3GPP TS 23.003 [4]. Home network public key identifier shall be coded as "00000000" when Protection scheme identifier is set to "0000" (i.e. Null scheme). | |||||||||
| Bits | |||||||||
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Home network PKI value 0 | |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | ||
| to | Home network PKI value (1-254) | ||||||||
| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | ||
| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Reserved | |
| Scheme output (octets 12 to x)The Scheme output field consists of a string of characters with a variable length or hexadecimal digits as specified in 3GPP TS 23.003 [4]. If Protection scheme identifier is set to "0000" (i.e. Null scheme), then the Scheme output consists of the MSIN and is coded using BCD coding with each digit of the MSIN coded over 4 bits. If the MSIN includes an odd number of digits, bits 5 to 8 of octet x shall be coded as "1111". If Protection scheme identifier is not "0000" (i.e. ECIES scheme profile A, ECIES scheme profile B or Operator-specific protection scheme), then Scheme output is coded as hexadecimal digits. | |||||||||
| For the SUCI with SUPI format set to "Network specific identifier", the SUCI NAI field contains an NAI constructed as specified in clause 28.7.3 of 3GPP TS 23.003 [4] and encoded as UTF-8 string. | |||||||||
| For the SUCI with SUPI format set to "GCI", the SUCI NAI field contains an NAI constructed as specified in clause 28.15.5 of 3GPP TS 23.003 [4] and encoded as UTF-8 string. | |||||||||
| For the SUCI with SUPI format set to "GLI", the SUCI NAI field contains an NAI constructed as specified in clause 28.16.5 of 3GPP TS 23.003 [4] and encoded as UTF-8 string. | |||||||||
| For the 5G-S-TMSI, bits 5 to 8 of octet 4 are coded as "1111". The coding of the 5G-S-TMSI is left open for each administration. | |||||||||
| AMF Set ID (octet 5, octet 6 bits 7 to 8)This field contains the binary encoding of the AMF Set ID. Bit 8 of octet 5 is the most significant bit and bit 7 of octet 6 is the least significant bit.AMF Pointer (octet 6 bits 1 to 6)This field contains the binary encoding of the AMF Pointer. Bit 6 of octet 6 is the most significant bit and bit 1 of octet 6 is the least significant bit.5G-TMSI (octet 7 to 10)Bit 8 of octet 7 is the most significant bit and bit 1 of octet 10 is the least significant bit. | |||||||||
| For Type of identity "No identity", the length of mobile identity contents parameter shall be set to 1 and the bits 4-8 of octet 4 are spare and shall be coded as zero. | |||||||||
| MAC address usage restriction indication (MAURI) (octet 4 bit 4) | |||||||||
| Bit | |||||||||
| 4 | |||||||||
| 0 | No restrictions | ||||||||
| 1 | MAC address is not usable as an equipment identifier | ||||||||
| MAC address (octets 5 to 10)This field contains the MAC address as defined in clause 8 of IEEE Std 802 [43].Bit 8 of octet 5 is the most significant bit and bit 1 of octet 10 is the least significant bit. | |||||||||
| EUI-64 (octets 5 to 12)This field contains an EUI-64 as defined in [48].Bit 8 of octet 5 is the most significant bit and bit 1 of octet 12 is the least significant bit. | |||||||||
| NOTE 1: This can be used when the requested identity is not available at the UE during the identification procedure.NOTE 2: For a 3-digit Routing Indicator, e.g "567", bits 1 to 4 of octet 8 are coded as "0101", bits 5 to 8 of octet 8 are coded as "0110", bits 1 to 4 of octet 9 are coded as "0111", bits 5 to 8 of octet 9 are coded as "1111". |