3GPP 24.501 v20.0.0 — the document's own text
4.5.2A Determination of the access identities and access category associated with a request for access for UEs operating in SNPN access operation mode over 3GPP access
When the UE needs to initiate an access attempt in one of the events listed in clause 4.5.1, the UE shall determine one or more access identities from the set of standardized access identities, and one access category from the set of standardized access categories and operator-defined access categories, to be associated with that access attempt.
The set of the access identities applicable for the request is determined by the UE in the following way:
- for each of the access identities 1, 2, 11, 12, 13, 14 and 15 in table 4.5.2A.1, the UE shall check whether the access identity is applicable in the selected SNPN, if a new SNPN is selected, or otherwise if it is applicable in the RSNPN or equivalent SNPN; and
- if none of the above access identities is applicable, then access identity 0 is applicable.
Table 4.5.2A.1: Access identities
| Access Identity number | UE configuration |
|---|---|
| 0 | UE is not configured with any parameters from this table |
| 1 (NOTE 1) | UE is configured for multimedia priority service (MPS). |
| 2 (NOTE 2) | UE is configured for mission critical service (MCS). |
| 3-10 | Reserved for future use |
| 11 (NOTE 3) | Access Class 11 is configured in the UE. |
| 12 (NOTE 3) | Access Class 12 is configured in the UE. |
| 13 (NOTE 3) | Access Class 13 is configured in the UE. |
| 14 (NOTE 3) | Access Class 14 is configured in the UE. |
| 15 (NOTE 3) | Access Class 15 is configured in the UE. |
| NOTE 1: Access identity 1 is valid when:- the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, indicates the UE is configured for access identity 1 in the selected SNPN, if a new SNPN is selected, or RSNPN, and the selected SNPN or the RSNPN is the subscribed SNPN, an SNPN equivalent to the subscribed SNPN, or an non-subscribed SNPN of the same country as the subscribed SNPN if the MCC of the SNPN identity of the subscribed SNPN is not the MCC of value 999; - the UE receives the 5GS network feature support IE with the MPS indicator bit set to "Access identity 1 valid" from the RSNPN as described in clause 5.5.1.2.4 and clause 5.5.1.3.4; or- the UE receives the Priority indicator IE with the MPS indicator bit set to "Access identity 1 valid" from the RSNPN as described in clause 5.4.4.3.NOTE 2: Access identity 2 is used by UEs configured for MCS and is valid when:- the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, indicates the UE is configured for access identity 2 in the selected SNPN, if a new SNPN is selected, or RSNPN, and the selected SNPN or the RSNPN is the subscribed SNPN, or an SNPN equivalent to the subscribed SNPN, or an non-subscribed SNPN of the same country as the subscribed SNPN if the MCC of the SNPN identity of the subscribed SNPN is not the MCC of value 999; or- the UE receives the 5GS network feature support IE with the MCS indicator bit set to "Access identity 2 valid" from the RSNPN as described in clause 5.5.1.2.4 and clause 5.5.1.3.4.NOTE 3: Access identities 11 and 15 are valid if indicated as configured for the UE in the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, in the selected SNPN, if a new SNPN is selected, or RSNPN, and the selected SNPN or the RSNPN is the subscribed SNPN. Access identities 12, 13 and 14 are valid if indicated as configured for the UE in the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, in the selected SNPN, if a new SNPN is selected, or RSNPN, and the selected SNPN or the RSNPN in the subscribed SNPN or an non-subscribed SNPN of the same country as the subscribed SNPN if the MCC of the SNPN identity of the subscribed SNPN is not the MCC of value 999. |
The contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, and the rules specified in table 4.5.2A.1 are used to determine the applicability of access identity 1 in the SNPN. When the contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, do not indicate the UE is configured for access identity 1 for the SNPN, the UE uses the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message and the MPS indicator bit of the Priority indicator IE in the CONFIGURATION UPDATE COMMAND message to determine if access identity 1 is valid.
The contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, and the rules specified in table 4.5.2A.1 are used to determine the applicability of access identity 2 in the SNPN. When the contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, do not indicate the UE is configured for access identity 2 for the SNPN, the UE uses the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 2 is valid.
The contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122 [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102 [22]), if the PLMN subscription is selected, and the rules specified in table 4.5.2A.1 are used to determine the applicability of access classes 11 to 15 in the SNPN.
In order to determine the access category applicable for the access attempt, the NAS shall check the rules in table 4.5.2A.2, and use the access category for which there is a match for barring check. If the access attempt matches more than one rule, the access category of the lowest rule number shall be selected. If the access attempt matches more than one operator-defined access category definition, the UE shall select the access category from the operator-defined access category definition with the lowest precedence value (see clause 4.5.3).
NOTE: The case when an access attempt matches more than one rule includes the case when multiple events trigger an access attempt at the same time. When multiple events trigger an access attempt at the same time, how the access attempt is checked for multiple events is up to UE implementation.
Table 4.5.2A.2: Mapping table for access categories
| Rule # | Type of access attempt | Requirements to be met | Access Category |
|---|---|---|---|
| 1 | Response to paging or NOTIFICATION over non-3GPP access ;5GMM connection management procedure initiated for the purpose of transporting an LPP or SLPP message without an ongoing 5GC-MO-LR or SL-MO-LR procedure;Access attempt to handover of MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access;Access attempt upon receipt of "call-pull-initiated" indication from the upper layers (see 3GPP TS 24.174 [13D]) | Access attempt is for MT access, handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access; orAccess attempt is made upon receipt of "call-pull-initiated" indication (3GPP TS 24.174 [13D]) | 0 (= MT_acc) |
| 2 | Emergency | UE is attempting access for an emergency session (NOTE 1, NOTE 2) | 2 (= emergency) |
| 3 | Access attempt for operator-defined access category | UE stores operator-defined access category definitions valid in the SNPN as specified in clause 4.5.3, and access attempt is matching criteria of an operator-defined access category definition | 32-63 (= based on operator classification) |
| 4 | Access attempt for delay tolerant service | (a) UE is configured for NAS signalling low priority, and(b) the UE received one of the categories a, b or c as part of the parameters for unified access control in the broadcast system information, and the UE is a member of the broadcasted category in the selected SNPN, RSNPN or equivalent SNPN(NOTE 3, NOTE 5, NOTE 6, NOTE 7, NOTE 8) | 1 (= delay tolerant) |
| 5 | MO MMTel voice call; orMT MMTel voice call | Access attempt is for MO MMTel voice call or MT MMTel voice callor for NAS signalling connection recovery during ongoing MO MMTel voice call or ongoing MT MMTel voice call (NOTE 2) | 4 (= MO MMTel voice) |
| 6 | MO MMTel video call; orMT MMTel video call | Access attempt is for MO MMTel video call or MT MMTel video callor for NAS signalling connection recovery during ongoing MO MMTel video call or ongoing MT MMTel video call (NOTE 2) | 5 (= MO MMTel video) |
| 7 | MO SMS over NAS or MO SMSoIP; orMT SMSoIP | Access attempt is for MO SMS over NAS (NOTE 4) or MO SMS over SMSoIP transfer or MT SMS over SMSoIPor for NAS signalling connection recovery during ongoing MO SMS or SMSoIP transfer or MT SMS over SMSoIP (NOTE 2) | 6 (= MO SMS and SMSoIP) |
| 7.1 | MO IMS registration related signalling | Access attempt is for MO IMS registration related signalling (e.g. IMS initial registration, re-registration, subscription refresh)or for PDU session establishment procedure for DNN = "IMS" or for the DNN used for SMSoIP, if the upper layers have indicated a DNN used for SMSoIP and the indicated DNN used for SMSoIP is different from "IMS", establishing a PDU session or transferring a PDU session from non-3GPP accessor service request procedure triggered by PDU session establishment procedure for DNN = "IMS" or for the DNN used for SMSoIP, if the upper layers have indicated a DNN used for SMSoIP and the indicated DNN used for SMSoIP is different from "IMS", establishing a PDU session or transferring a PDU session from non-3GPP accessor for NAS signalling connection recovery during ongoing procedure for MO IMS registration related signalling (NOTE 2a) | 9 (= MO IMS registration related signalling) |
| 8 | UE NAS initiated 5GMM specific procedures | Access attempt is for MO signalling | 3 (= MO_sig) |
| 8.1 | Mobile originated location request | Access attempt is for mobile originated location request (NOTE 9) | 3 (= MO_sig) |
| 8.2 | Mobile originated signalling transaction towards the PCF | Access attempt is for mobile originated signalling transaction towards the PCF (NOTE 10) | 3 (= MO_sig) |
| 8.3 | Access attempt for RAN timing synchronization | Access attempt is for mobile originated signalling for the reconnection to the network due to RAN timing synchronization status change | 3 (= MO_sig) |
| 9 | UE NAS initiated 5GMM connection management procedure or 5GMM NAS transport procedure | Access attempt is for MO data | 7 (= MO_data) |
| 10 | An uplink user data packet is to be sent for a PDU session with suspended user-plane resources | No further requirement is to be met | 7 (= MO_data) |
| NOTE 1: Void.NOTE 2: Access for the purpose of NAS signalling connection recovery during an ongoing service as defined in clause 4.5.5, or for the purpose of NAS signalling connection establishment following fallback indication from lower layers during an ongoing service as defined in clause 4.5.5, is mapped to the access category of the ongoing service in order to derive an RRC establishment cause, but barring checks will be skipped for this access attempt.NOTE 2a: Access for the purpose of NAS signalling connection recovery during an ongoing MO IMS registration related signalling as defined in clause 4.5.5, or for the purpose of NAS signalling connection establishment following fallback indication from lower layers during an ongoing MO IMS registration related signalling as defined in clause 4.5.5, is mapped to the access category of the MO IMS registration related signalling in order to derive an RRC establishment cause, but barring checks will be skipped for this access attempt.NOTE 3: If the UE selects a new SNPN, then the selected SNPN is used to check the membership; otherwise the UE uses the RSNPN or an SNPN equivalent to the RSNPN.NOTE 4: This includes the 5GMM connection management procedures triggered by the UE-initiated NAS transport procedure for transporting the MO SMS.NOTE 5: The UE configured for NAS signalling low priority is not supported in this release of specification.NOTE 6: If the access category applicable for the access attempt is 1, then the UE shall additionally determine a second access category from the range 3 to 7. If more than one access category matches, the access category of the lowest rule number shall be chosen. The UE shall use the second access category only to derive an RRC establishment cause for the access attempt.NOTE 7: Void.NOTE 8: For the definition of categories a, b and c associated with access category 1, see 3GPP TS 22.261 [3]. The categories associated with access category 1 are distinct from the categories a, b and c associated with EAB (see 3GPP TS 22.011 [1A]).NOTE 9: This includes:a) the UE-initiated NAS transport procedure for transporting a mobile originated location request;b) the 5GMM connection management procedure triggered by a) above; andc) NAS signalling connection recovery during an ongoing 5GC-MO-LR procedure.NOTE 10: This includes:a) the UE-initiated NAS transport procedure for transporting a mobile originated signalling transaction towards the PCF;b) the 5GMM connection management procedure triggered by a) above; andc) NAS signalling connection recovery during an ongoing UE-requested policy provisioning procedure for V2XP (see 3GPP TS 24.587 [19B]). |