Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.7.1

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

9.11.2.10  Service-level-AA container |R17|Word‑p. 708

The purpose of the Service-level-AA container information element is to transfer upper layer information for authentication and authorization between the UE and the network.
The Service-level-AA container information element is coded as shown in Figure 9.11.2.10.1, Figure 9.11.2.10.2, Figure 9.11.2.10.3, Figure 9.11.2.10.4 and Table 9.11.2.10.1.
The Service-level-AA container information element is a type 6 information element with a minimum length of 6 octets and a maximum length of 65538 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.10.1: Service-level-AA container information element
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.10.2: Service-level-AA container contents
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.10.3: Service-level-AA parameter (when the type of service-level-AA parameter field contains an IEI of a type 4 information element as specified in TS 24.007 [11])
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.10.4: Service-level-AA parameter (when the type of service-level-AA parameter field contains an IEI of a type 6 information element as specified in TS 24.007 [11])
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.10.5: Service-level-AA parameter (when Service-level-AA payload type and its associated Service-level-AA payload are included in the Service-level-AA container contents)
Up
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.10.6: Service-level-AA parameter (when the type of service-level-AA parameter field contains an IEI of a type 1 information element as specified in 3GPP TS 24.007 [11])
Up
Service-level-AA container contents (octet 4 to octet n); max value of 65535 octets
The error handlings for service-level-AA parameters specified in subclauses 7.6.1, 7.6.3 and 7.7.1 shall apply to the service-level-AA parameters included in the service-level-AA container contents.
Service-level-AA parameters
Type of service-level-AA parameter (octet xi +1)
This field contains the IEI of the service-level-AA parameter.
Length of service-level-AA parameter
This field indicates binary coded length of the value of the service-level-AA parameter.
Value of service-level-AA parameter
This field contains the value of the service-level-AA parameter with the value part of the referred information element based on following service-level-AA parameter reference.
The receiving entity shall ignore service-level-AA parameter with type of service-level-AA parameter field containing an unknown IEI.
IEI (hexa­decimal)Service-level-AA parameter nameService-level-AA parameter reference
10Service-level device IDService-level device ID (see subclause 9.11.2.11)
20Service-level-AA server addressService-level-AA server address (see subclause 9.11.2.12)
30Service-level-AA responseService-level-AA response (see subclause 9.11.2.14)
40Service-level-AA payload typeService-level-AA payload type (see subclause 9.11.2.15) (NOTE)
70Service-level-AA payloadService-level-AA payload (see subclause 9.11.2.13)
A-Service-level-AA pending indicationService-level-AA pending indication (see subclause 9.11.2.17)
NOTE:
A service-level-AA payload type is always followed by the associated service-level-AA payload as shown in Figure 9.11.2.10.5.
Up

9.11.2.11  Service-level device ID |R17|Word‑p. 711

The purpose of the Service-level device ID information element is to carry the necessary identity for authentication and authorization by the external DN.
The Service-level device ID information element is coded as shown in Figure 9.11.2.11.1 and Table 9.11.2.11.1.
The Service-level device ID information element is a type 4 information element with minimum length of 3 octets and maximum length of 257 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.11.1: Service-level device ID information element
Up
Service-level device ID (octet 3 to octet y)
A service-level device ID encoded as UTF-8 string.
Up

9.11.2.12  Service-level-AA server address |R17|Word‑p. 711

The purpose of the Service-level-AA server address information element is to carry the address of the service level authentication and authorization server.
The Service-level-AA server address information element is coded as shown in Figure 9.11.2.12.1 and Table 9.11.2.12.1.
The Service-level-AA server address information element is a type 4 information element with minimum length of 4 octets and maximum length of 258 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.12.1: Service-level-AA server address information element
Up
Service-level-AA server address type (octet 3):
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1IPv4
0 0 0 0 0 0 1 0IPv6
0 0 0 0 0 0 1 1IPv4v6
0 0 0 0 0 1 0 0FQDN
All other values are spare.
If the service-level-AA server address type indicates IPv4, then the service-level-AA server address field contains an IPv4 address in octet 4 to octet 7.
If the service-level-AA server address type indicates IPv6, then the service-level-AA server address field contains an IPv6 address in octet 4 to octet 19.
If the service-level-AA server address type indicates IPv4v6, then the service-level-AA server address field contains two IP addresses. The first IP address is an IPv4 address in octet 4 to octet 7. The second IP address is an IPv6 address in octet 8 to octet 23.
If the service-level-AA server address type indicates FQDN, octet 4 to octet z is encoded as defined in subclause 28.3.2.2.2 in TS 23.003.
Up

9.11.2.13  Service-level-AA payload |R17|Word‑p. 712

The purpose of the Service-level-AA payload information element is to carry the upper layer payload for authentication and authorization between the UE and the service-level-AA server.
The Service-level-AA payload information element is coded as shown in Figure 9.11.2.13.1 and Table 9.11.2.13.1.
The Service-level-AA payload information element is a type 6 information element with minimum length of 4 octets and maximum length of 65535 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.13.1: Service-level-AA payload information element
Up
Service-level-AA payload (octet 4 to octet s)
A payload for authentication and authorization transparently transported and which is provided from/to the upper layers.
Up

9.11.2.14  Service-level-AA response |R17|Word‑p. 712

The purpose of the Service-level-AA response information element is to provide information regarding the service level authentication and authorization request, e.g. to indicate that the authentication and authorization request to the service level authentication server was successful.
The Service-level-AA response information element is coded as shown in Figure 9.11.2.14.1 and Table 9.11.2.14.1.
The Service-level-AA response information element is a type 4 information element with length of 3 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.14.1: Service-level-AA response information element
Up
Service-level-AA result field (SLAR) (octet 3, bits 1 and 2)
Bits
1 2
0 0No information
0 1Service level authentication and authorization was successful.
1 0Service level authentication and authorization was not successful or service level authorization is revoked.
1 1Reserved
C2 authorization result field (C2AR) (octet 3, bits 3 and 4)
Bits
3 4
0 0No information
0 1C2 authorization was successful.
1 0C2 authorization was not successful or C2 authorization is revoked.
1 1Reserved
Bits 5 to 8 of octet 3 are spare and shall be coded as zero.
Up

9.11.2.15  Service-level-AA payload type |R17|Word‑p. 713

The purpose of the Service-level-AA payload type information element is to indicates type of payload included in the Service-level-AA payload information element.
The Service-level-AA payload type information element is coded as shown in Figure 9.11.2.15.1 and Table 9.11.2.15.1.
The Service-level-AA payload type information element is a type 4 information element with length of 3 octets.
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.15.1: Service-level-AA payload type information element
Up
Service-level-AA payload type (octet 3):
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 1UUAA payload (see NOTE 1)
0 0 0 0 0 0 1 0C2 authorization payload (see NOTE 2)
All other values are spare.
NOTE 1:
If the service-level-AA payload type indicates UUAA payload, the field for the service-level-AA payload of the Service-level AA payload information element is an application layer payload for UUAA procedure between the UE supporting UAS services and the USS.
NOTE 2:
If the service-level-AA payload type indicates C2 authorization payload, the field for the service-level-AA payload of the Service-level-AA payload information element is an application layer payload for C2 authorization procedure between the UE supporting UAS services and the USS.
Up

9.11.2.16Void

9.11.2.17  Service-level-AA pending indication |R17|Word‑p. 714

The purpose of the Service-level-AA pending indication information element is to provide an indication that the service level authentication and authorization procedure is to be performed.
The Service-level-AA pending indication information element is coded as shown in Figure 9.11.2.17.1 and Table 9.11.2.17.1.
The Service-level-AA pending indication information element is a type 1 information element.
Reproduction of 3GPP TS 24.501, Fig. 9.11.2.17.1: Service-level-AA pending indication
Up
Service-level-AA pending indication (SLAPI) (octet 1, bit 1)
Bit
1
0reserved
1Service-level-AA procedure is to be performed
Up

Up   Top   ToC