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 (NOTE 3) | UE for which a disaster condition applies |
4-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:
NOTE 2:
Access identity 2 is used by UEs configured for MCS and is valid when:
NOTE 3:
Access identities 11 and 15 are valid in HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the EHPLMN list is present). Access Identities 12, 13 and 14 are only valid in HPLMN and visited PLMNs of home country only.
NOTE 4:
Access Identity 3 is valid when the UE is registering or registered for disaster roaming services (see TS 23.122).
|
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 ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access; or Access attempt upon receipt of "call-pull-initiated" indication from the upper layers (see TS 24.174). | Access attempt is for MT access, or handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access; or Access attempt is made upon receipt of "call-pull-initiated" (TS 24.174) | 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 current PLMN as specified in subclause 4.5.3, and access attempt is matching criteria of an operator-defined access category definition | 32-63 (= based on operator classification) |
3.1 | Access attempt for MO exception data | UE is in NB-N1 mode and allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in TS 24.368 or the USIM file EFNASCONFIG in TS 31.102), and access attempt is for MO data or for MO signalling initiated upon receiving a request from upper layers to transmit user data related to an exceptional event. | 10 (= MO exception data) |
4 | Access attempt for delay tolerant service |
| 1 (= delay tolerant) |
5 | MO MMTel voice call; or MT MMTel voice call | Access attempt is for MO MMTel voice call or MT MMTel voice call
or 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; or
MT MMTel video call | Access attempt is for MO MMTel video call or MT MMTel video call or for NAS signalling connection recovery during ongoing MO MMTel video call or ongoing MT SMS over SMSoIP (NOTE 2) | 5 (= MO MMTel video) |
7 | MO SMS over NAS or MO SMSoIP; or
MT SMSoIP | Access attempt is for MO SMS over NAS (NOTE 4) or MO SMS over SMSoIP transfer or MT SMS over SMSoIP or for NAS signalling connection recovery during ongoing MO SMS or SMSoIP transfer or ongoing MT MMTel video call (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 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:
This includes 5GMM specific procedures while the service is ongoing and 5GMM connection management procedures required to establish a PDU session with request type = "initial emergency request" or "existing emergency PDU session", or to re-establish user-plane resources for such a PDU session. This further includes the service request procedure initiated with a SERVICE REQUEST message with the Service type IE set to "emergency services fallback".
NOTE 2:
Access for the purpose of NAS signalling connection recovery during an ongoing service as defined in subclause 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 subclause 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 procedure for MO IMS registration related signalling as defined in subclause 4.5.5, or for the purpose of NAS signalling connection establishment following fallback indication from lower layers during an ongoing procedure for MO IMS registration related signalling as defined in subclause 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 PLMN, then the selected PLMN is used to check the membership; otherwise the UE uses the RPLMNor a PLMN equivalent to the RPLMN.
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. If a UE supporting both S1 mode and N1 mode is configured for NAS signalling low priority in S1 mode as specified in TS 24.368 or TS 31.102, the UE shall ignore the configuration for NAS signalling low priority when in N1 mode.
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:
"EAB override" does not apply, if the UE is not configured to allow overriding EAB (see the "Override_ExtendedAccessBarring" leaf of NAS configuration MO in TS 24.368 or TS 31.102), or if NAS has not received an indication from the upper layers to override EAB and the UE does not have a PDU session that was established with EAB override.
NOTE 8:
For the definition of categories a, b and c associated with access category 1, see TS 22.261. The categories associated with access category 1 are distinct from the categories a, b and c associated with EAB (see TS 22.011).
NOTE 9:
This includes:
NOTE 10:
This includes:
|
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:
NOTE 2:
Access identity 2 is used by UEs configured for MCS and is valid when:
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 TS 23.122), if an entry of "list of subscriber data" is selected, or in the USIM (see TS 31.102), 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 TS 23.122), if an entry of "list of subscriber data" is selected, or in the USIM (see TS 31.102), 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.
|
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 TS 24.174) | Access attempt is for MT access, handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access; or Access attempt is made upon receipt of "call-pull-initiated" indication (TS 24.174) | 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 subclause 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 |
| 1 (= delay tolerant) |
5 | MO MMTel voice call; or
MT MMTel voice call | Access attempt is for MO MMTel voice call or MT MMTel voice call or 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; or
MT MMTel video call | Access attempt is for MO MMTel video call or MT MMTel video call or 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; or
MT SMSoIP | Access attempt is for MO SMS over NAS (NOTE 4) or MO SMS over SMSoIP transfer or MT SMS over SMSoIP or for NAS signalling connection recovery during ongoing MO SMS or SMSoIP transfer or MT SMS over SMSoIP (NOTE 2) | 6 (= MO SMS and SMSoIP) |
5 | MO MMTel voice call | Access attempt is for MO MMTel voice call or for NAS signalling connection recovery during ongoing MO MMTel voice call (NOTE 2) | 4 (= MO MMTel voice) |
6 | MO MMTel video call | Access attempt is for MO MMTel video call or for NAS signalling connection recovery during ongoing MO MMTel video call (NOTE 2) | 5 (= MO MMTel video) |
7 | MO SMS over NAS or MO SMSoIP | Access attempt is for MO SMS over NAS (NOTE 4) or MO SMS over SMSoIP transfer or for NAS signalling connection recovery during ongoing MO SMS or SMSoIP transfer (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 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 subclause 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 subclause 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 subclause 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 subclause 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 TS 22.261. The categories associated with access category 1 are distinct from the categories a, b and c associated with EAB (see TS 22.011).
NOTE 9:
This includes:
NOTE 10:
This includes:
|