3GPP 24.501 v20.0.0 — the document's own text
9.11.3.38 Operator-defined access category definitions
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 Operator-defined access category definitions information element is to provide the UE with the operator-defined access category definitions or to delete the operator-defined access category definitions at the UE.
The Operator-defined access category definitions information element is coded as shown in figure 9.11.3.38.1, figure 9.11.3.38.2 and table 9.11.3.38.1.
The Operator-defined access category definitions is a type 6 information element with a minimum length of 3 octets, and maximum length of 8323 octets.
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Operator-defined access category definitions IEI | octet 1 | |||||||
| Length of operator-defined access category definitions contents | octet 2octet 3 | |||||||
| Operator-defined access category definition 1 | octet 4*octet a* | |||||||
| Operator-defined access category definition 2 | octet a+1*octet b* | |||||||
| … | octet b+1*octet g* | |||||||
| Operator-defined access category definition n | octet g+1*octet h* |
Figure 9.11.3.38.1: Operator-defined access category definitions information element
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
|---|---|---|---|---|---|---|---|---|
| Length of operator-defined access category definition contents | octet 4 | |||||||
| Precedence value | octet 5 | |||||||
| PSAC | 0Spare | 0Spare | Operator-defined access category number | octet 6 | ||||
| Length of criteria | octet 7 | |||||||
| Criteria | octet 8octet a-1 | |||||||
| 0Spare | 0Spare | 0Spare | Standardized access category | octet a* |
Figure 9.11.3.38.2: Operator-defined access category definition
Table 9.11.3.38.1: Operator-defined access category definitions information element
| Value part of the Operator-defined access category definitions information element (octet 4 to h)The value part of the Operator-defined access category definitions information element consists of zero or no more than 32 operator-defined access category definition fields. Each operator-defined access category definition field is coded as described in figure 9.11.3.38.2. The length of each operator-defined access category definition field is determined by the length of operator-defined access category definition contents field. | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Operator-defined access category definition (octet 4 to octet a): | |||||||||
| Length of operator-defined access category definition contents (octet 4)Length of operator-defined access category definition contents indicates binary coded length of the operator-defined access category definition value field (octet 5 to octet a).Precedence value (octet 5) | |||||||||
| Bits | |||||||||
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Precedence value 0 | |
| to | |||||||||
| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Precedence value 255 | |
| Operator-defined access category number (bits 5 to 1 of octet 6) | |||||||||
| Bits | |||||||||
| 5 | 4 | 3 | 2 | 1 | |||||
| 0 | 0 | 0 | 0 | 0 | Access category number 32 | ||||
| to | |||||||||
| 1 | 1 | 1 | 1 | 1 | Access category number 63 | ||||
| Presence of standardized access category (PSAC) (bit 8 of octet 6) | |||||||||
| PSAC field indicates whether the standardized access category field is present or absent. | |||||||||
| Bit | |||||||||
| 8 | |||||||||
| 0 | Standardized access category field is not included | ||||||||
| 1 | Standardized access category field is included | ||||||||
| Length of criteria (octet 7) | |||||||||
| Length of criteria field indicates binary coded length of the criteria field. | |||||||||
| Criteria (octets 8 to octet a-1) | |||||||||
| The criteria field contains one or more criteria components fields. Each criteria component field shall be encoded as a sequence of a one octet criteria type field and zero or more octets criteria value field. The criteria type field shall be transmitted first. | |||||||||
| Criteria type | |||||||||
| Bits | |||||||||
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DNN type | |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | OS id + OS App Id type | |
| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | S-NSSAI type | |
| All other values are reserved. | |||||||||
| For "DNN type", the criteria value field shall be encoded as a sequence of one octet DNN length-value pair count field and one or more DNN length-value pair fields. The DNN length-value pair count field indicates the number of included DNN length-value pair fields. Each DNN length-value pair field is coded as a sequence of one octet DNN value length field and a DNN value field. The DNN value length field indicates the length in octets of the DNN value field. The DNN value field contains an APN as specified in 3GPP TS 23.003 [4]. | |||||||||
| For "OS Id + OS App Id type", the criteria value field shall be encoded as a sequence of one octet app id value count field and one or more app id value fields. The app id value count field indicates the number of included app id value fields. Each app id value field is coded as a sequence of a sixteen octet OS id value field, one octet OS app id value length field and an OS app id value field. The OS app id value length field indicates the length in octets of the OS app id value field. The OS id value field contains a Universally Unique IDentifier (UUID) as specified in IETF RFC 9562 [35A]. The OS app id value field contains an OS specific application identifier. Coding of the OS app id value field is outside the scope of the present document. | |||||||||
| For "S-NSSAI type", the criteria value field shall be encoded as a sequence of one octet S-NSSAI length-value pair count field and one or more S-NSSAI length-value value fields. The S-NSSAI length-value pair count field indicates the number of included S-NSSAI length-value pair fields. Each S-NSSAI length-value pair field is coded as a sequence of one octet S-NSSAI value length field and an S-NSSAI value field. The S-NSSAI value length field indicates the length in octets of the S-NSSAI value field. The S-NSSAI value field contains one octet SST field optionally followed by three octets SD field. The SST field contains a SST. The SD field contains an SD. SST and SD are specified in 3GPP TS 23.003 [4]. | |||||||||
| Standardized access category (bits 5 to 1 of octet a) | |||||||||
| Standardized access category field indicates the access category number of the standardized access category that is used in combination with the access identities to determine the establishment cause. | |||||||||
| Bits | |||||||||
| 5 | 4 | 3 | 2 | 1 | |||||
| 0 | 0 | 0 | 0 | 0 | Access category number 0 | ||||
| to | |||||||||
| 0 | 0 | 1 | 1 | 1 | Access category number 7 | ||||
| 0 | 1 | 0 | 0 | 1 | Access category number 9 | ||||
| 0 | 1 | 0 | 1 | 0 | Access category number 10 | ||||
| All other values are reserved. |