H.2 General structure

24.3023GPPAccess to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networksRelease 18Stage 3TS

H.2.1 Structure

The general structure of the generic container is shown in figure H.2.1-1.

7

6

5

4

3

2

1

0

GUD

octet 1

UDHL

octet 2

IEI 1

octet 3

octet 4

octet i

Length of contents of IE 1

Contents of IE 1

IEI 2

octet i+1*

octet i+2

octet l

Length of contents of IE 2

Contents of IE 2

………

octet l+1*

octet m

IEI q

octet m+1*

octet m+2

octet n

Length of contents of IE q

Contents of IE q

Figure H.2.1-1 – Structure of IEEE Std 802.11 Generic Container

H.2.2 Generic container User Data (GUD)

Indicates the protocol version of the generic container

00000000 Version 1

00000001

To

11111111 Reserved

H.2.3 User Data Header Length (UDHL)

Indicates the number of octets in the generic container after the UDHL. This indication is encoded in binary format.

H.2.4 Information Elements

H.2.4.1 Information Element Identity (IEI)

Indicates the information element identity. The following values for IEI are defined in this version of the specification:

00000000 PLMN List

00000001 PLMN List with S2a connectivity

00000010 PLMN List with trusted 5G connectivity

00000011 PLMN List with trusted 5G connectivity-without-NAS

00000100 PLMN List with AAA connectivity to 5GC

00000101

To

00011111 Reserved

00100000 SNPN List with trusted 5G connectivity

00100001

To

11111111 Reserved

H.2.4.2 PLMN List IE

The PLMN List information element is used by a WLAN to indicate the PLMNs, for which the WLAN supports AAA connectivity to EPC, see clause 6.3.12.1 in 3GPP TS 23.501 [6A]. The format of the PLMN List information element coded according to 3GPP TS 24.007 [48] clause 11.2.2.1 is shown in figure H.2.4.2-1.

7

6

5

4

3

2

1

0

PLMN List IEI

octet 1

Length of PLMN List value contents

octet 2

Number of PLMNs

octet 3

PLMN information, PLMN 1

octet 4

octet 5

octet 6

PLMN information, PLMN N

octet 3N+1

octet 3N+2

octet 3N+3

Figure H.2.4.2-1: PLMN List information element

The "Number of PLMNs" (octet 3) contains the number of PLMN information items in the list. Bit 7 of octet 3 is the most significant bit and bit 0 of octet 3 the least significant bit.

The format of the PLMN information item according to 3GPP TS 24.007 [48] clause 11.2.2.1 is shown in figure H.2.4.2-2:

7

6

5

4

3

2

1

0

MCC digit 2

MCC digit 1

octet X

MNC digit 3

MCC digit 3

octet X+1

MNC digit 2

MNC digit 1

octet X+2

Figure H.2.4.2-2: PLMN information item of the PLMN List IE

Table H.2.4.2-1 shows the coding of the MCC and MNC in the PLMN information item.

Table H.2.4.2-1: PLMN information item of PLMN List IE

MCC, Mobile country code (octet X, octet X+1 bits 1 to 4)

The MCC field is coded as in ITU-T Rec. E212 [63], Annex A.

MNC, Mobile network code (octet X+2, octet X+1 bits 5 to 8).

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. For PCS 1900 for North America, Federal Regulation mandates that a 3-digit MNC shall be used. However a network operator may decide to use only two digits in the MNC over the radio interface. In this case, bits 5 to 8 of octet X+1 shall be coded as "1111". Mobile equipment shall accept MNC coded in such a way.

H.2.4.3 PLMN List with S2a Connectivity IE

The PLMN List with S2a connectivity information element is used by the WLAN to indicate the PLMNs to which the WLAN provides S2a connectivity.

The format of the PLMN List with S2a Connectivity information element is identical to the format of the PLMN List information element defined in clause H.2.4.2.

H.2.4.4 PLMN List with trusted 5G Connectivity IE

The PLMN List with trusted 5G connectivity information element is used by the WLAN to indicate the PLMNs for which the WLAN provides connectivity to a 5GCN, using trusted non-3GPP access.

The format of the PLMN List with trusted 5G connectivity information element is identical to the format of the PLMN List information element defined in clause H.2.4.2.

H.2.4.5 PLMN List with trusted 5G Connectivity-without-NAS IE

The PLMN List with trusted 5G connectivity-without-NAS information element is used by the WLAN to indicate the PLMNs for which the WLAN provides connectivity to a 5GCN, for devices without NAS capability, using trusted non-3GPP access.

The format of the PLMN List with trusted 5G connectivity-without-NAS information element is identical to the format of the PLMN List information element defined in clause H.2.4.2.

H.2.4.6 PLMN List with AAA connectivity to 5GC IE

The PLMN List with AAA connectivity to 5GC information element is used by the WLAN to indicate the PLMNs, which support NSWO in 5GS as specified in annex S of 3GPP TS 33.501 [78], for a UE served by the WLAN.

The format of the PLMN List with AAA connectivity to 5GC information element is identical to the format of the PLMN List information element defined in clause H.2.4.2.

H.2.4.7 SNPN List with trusted 5G Connectivity IE

The SNPN List with trusted 5G Connectivity information element is used by the network to indicate the SNPNs that can be selected from the WLAN. The SNPN List with trusted 5G Connectivity information element optionally includes per SNPN access information, per SNPN supported GINs, and a GIN list. The format of the SNPN List with trusted 5G Connectivity information element coded according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-1.

7

6

5

4

3

2

1

0

SNPN List with trusted 5G Connectivity IE

octet 1

Length of SNPN List with trusted 5G Connectivity value contents

octet 2

SNPN information List

octet 3

octet d

GIN list

octet d+1*

octet Z*

Figure H.2.4.7-1: SNPN List with trusted 5G Connectivity information element

The format of the SNPN information list according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-2:

Length of SNPN information list

octet 3

SNPN information entry 1

octet 4

octet b

..

octet b+1*

octet c-1*

SNPN information entry N

octet c*

octet d*

Figure H.2.4.7-2: SNPN information List

The format of the SNPN information entry according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-3:

Length of SNPN information entry

octet 4

SNPN identity

octet 5

octet 13

SNPN access information

octet 14*

octet 15*

Supported GINs

octet 16*

octet b*

Figure H.2.4.7-3: SNPN information entry

The format of the SNPN identity according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-4:

7

6

5

4

3

2

1

0

MCC digit 2

MCC digit 1

octet 5

MNC digit 3

MCC digit 3

octet 6

MNC digit 2

MNC digit 1

octet 7

NID value digit 1

NID assignment mode

octet 8

NID value digit 3

NID value digit 2

octet 9

NID value digit 5

NID value digit 4

octet 10

NID value digit 7

NID value digit 6

octet 11

NID value digit 9

NID value digit 8

octet 12

Spare

NID value digit 10

octet 13

Figure H.2.4.7-4: SNPN identity

Editor’s Note [WI: eNPN_Ph2, CR#0737]: The coding of SNPN identity may need to be updated in alignment with the coding of the NID in 3GPP TS 24.501 and 3GPP TS 24.502.

The format of the SNPN access information according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-4:

7

6

5

4

3

2

1

0

Length of SNPN access information

octet 14

Spare

Spare

Spare

Spare

Spare

OB

CHWC

CH

octet 15

Figure H.2.4.7-5: SNPN access information

The format of the Supported GINs according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-6:

7

6

5

4

3

2

1

0

Length of Supported GINs value

octet 16

G(8)

G(7)

G(6)

G(5)

G(4)

G(3)

G(2)

G(1)

octet 17*

..

octet 18*

octet b-1*

G(n)

G(n-1)

G(n-2)

G(n-3)

G(n-4)

G(n-5)

G(n-6)

G(n-7)

octet b*

Figure H.2.4.7-6: Supported GINs

The format of the GIN list according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7 7:

Length of GIN list

octet d+1

GIN information entry 1

octet d+2

octet e

..

octet e+1*

octet f-1*

GIN information entry N

octet f*

octet Z*

Figure H.2.4.7-7: GIN list

The format of the GIN information entry according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-8:

6

5

4

3

2

1

0

Length of GIN information entry

octet d+2

MCC digit 2

MCC digit 1

octet d+3

MNC digit 3

MCC digit 3

octet d+4

MNC digit 2

MNC digit 1

octet d+5

NID list

octet d+6

octet e

Figure H.2.4.7-8: GIN information entry

The format of the NID list according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-9:

Length of NID list

octet d+6

NID identity 1

octet d+7

octet d+12

..

octet d+13*

octet e-1*

NID identity N

octet e*

octet e+5*

Figure H.2.4.7-9: NID list

The format of the NID identity according to 3GPP TS 24.007 [48] subclause 11.2.2.1 is shown in figure H.2.4.7-10:

7

6

5

4

3

2

1

0

NID value digit 1

NID assignment mode

octet d+7

NID value digit 3

NID value digit 2

octet d+8

NID value digit 5

NID value digit 4

octet d+9

NID value digit 7

NID value digit 6

octet d+10

NID value digit 9

NID value digit 8

octet d+11

Spare

NID value digit 10

octet d+12

Figure H.2.4.7-10: NID identity

Editor’s Note [WI: eNPN_Ph2, CR#0737]: The coding of NID identity may need to be updated in alignment with the coding of the NID in 3GPP TS 24.501 and 3GPP TS 24.502.

Table H.2.4.7-1 shows the coding of SNPN List with trusted 5G Connectivity information element.

Table H.2.4.7-1: SNPN List with trusted 5G Connectivity information element

SNPN List with trusted 5G Connectivity information element (octets 1 to Z)

SNPN identity (octets 5 to 13)

MCC (octet 5, octet 6 bits 0 to 3) or (octet d+3, octet d+4 bits 0 to 3)

The MCC (Mobile country code) field is coded as in ITU-T Recommendation E.212 [63], Annex A

MNC (octet 7, octet 6 bits 4 to 7) or (octet d+5, octet d+4 bits 4 to 7).

The coding of the MNC (Mobile network code) 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 4 to 7 of octet 6 or octet d+4 shall be coded as "1111".

NID assignment mode (octet 8 bits 0 to 3) or (octet d+7 bits 0 to 3)

This field contains the binary encoding of the assignment mode of the NID as defined in 3GPP TS 23.003 [3].

NID value (octet 8 bits 4 to 7, octets 9 to 12, octet 13 bits 0 to 3) or (octet d+7 bits 4 to 7, octets d+8 to d+11, octet d+12 bits 0 to 3)

This field contains the binary encoding of each hexadecimal digit of the NID value as defined in 3GPP TS 23.003 [3]

Bits 4 to 7 of octet 13 or Bits 4 to 7 of octet d+12 are spare and shall be coded as zero.

SNPN access information (octets 14 to 15)

CH (octet 15 bit 0)

This bit indicates whether the SNPN supports access using credentials from a credentials holder.

0 access using credentials from a credentials holder supported.

1 access using credentials from a credentials holder not supported.

CHWC (octet 15 bit 1)

This bit indicates whether the SNPN allows registration attempts with credentials from a credentials holder from UEs that are not explicitly configured to select the SNPN.

0 registration attempts from UEs without configuration to select the SNPN not allowed.

1 registration attempts from UEs without configuration to select the SNPN allowed.

OB (octet 15 bit 2)

This bit indicates whether the SNPN allows onboarding.

0 onboarding is not allowed.

1 onboarding is allowed.

octet 15 bits 3 to 7 are spare.

Supported GINs value (octets 16 to b)

G(1) to G(n) is a bitmap indicating whether the SNPN identity in the SNPN information entry supports a corresponding GIN in the GIN list. G(1) bit corresponds to GIN index value one in the GIN list, G(2) corresponds to GIN index value two in the GIN list and so on. A bit set to 1 indicates that the GIN is supported by the SNPN and a bit set to 0 indicates that the GIN is not supported by the SNPN. The length of the Supported GINs value field in octets is the ceiling of the number of GINs in the GIN list divided by 8. The filling bits, if any, are set to 0.

GIN list (octets d+1 to Z)

The GIN list contains one or more GIN information entries. Each GIN information entry contains either one GIN, which is identified by a PLMN ID (MCC, MNC) and a single NID (NID list with a single NID entry), or multiple GINs that share the same PLMN ID with each GIN identified by the shared PLMN ID and a NID entry in the NID list. The GIN index m is defined as d1+d2+…+d(n-1)+i for the GIN included in the n-th entry of the GIN list and the i-th entry of its corresponding GIN information entry, where d(k) is the number of GIN index values used in the k-th GIN information entry.

Annex I (normative):
Definition of the Emergency Call Number field’s contents