11.3.10 UAC / Access Identity 0 / AC9 / 0% access probability / SIP Re-registration
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
11.3.10.1 Test Purpose (TP)
(1)
with { the UE is NR RRC_CONNECTED }
ensure that {
when { the UE receives SIB1 message not configured for special AIs (1,2,11-15) indicating UAC Info set to 0% accessibility for Access category 9}
then { UE is not able to send SIP REGISTER message successfully }
}
(2)
with { the UE is NR RRC_CONNECTED }
ensure that {
when { the UE receives SIB1 default message }
then { UE is able to perform reregistration successfully }
}
11.3.10.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in TS 24.501: clause 4.5.2, 4.5.4.2 and 4.5.6 and TS 38.331: clause 5.3.14.1, 5.3.14.2, 5.3.14.4 and 5.3.14.5. Unless otherwise stated these are Rel-16 requirements.
[TS 24.501, clause 4.5.2]
When the UE needs to initiate an access attempt in one of the events listed in subclause 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:
a) for each of the access identities 1, 2, 11, 12, 13, 14 and 15 in table 4.5.2.1, the UE shall check whether the access identity is applicable in the selected PLMN, if a new PLMN is selected, or otherwise if it is applicable in the RPLMN or equivalent PLMN; and
b) if none of the above access identities is applicable, then access identity 0 is applicable.
Table 4.5.2.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: 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 valid in HPLMN and visited PLMNs of home country only (see the definition of home country in 3GPP TS 24.301 [15]). |
|
The UE uses the MPS indicator bit of the 5GS network feature support IE to determine if access identity 1 is valid. Processing of the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4. The UE shall not consider access identity 1 to be valid when the UE is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present) prior to receiving the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message being set to "Access identity 1 valid".
When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFUAC_AIC as specified in 3GPP TS 31.102 [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access identity 1. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EFUAC_AIC does not indicate the UE is configured for access identity 1, the UE uses the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 1 is valid. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EFUAC_AIC indicates the UE is configured for access identity 1, the MPS indicator bit of the 5GS network feature support IE is not applicable. When the UE is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFUAC_AIC are not applicable.
The UE uses the MCS indicator bit of the 5GS network feature support IE to determine if access identity 2 is valid. Processing of the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4. The UE shall not consider access identity 2 to be valid when the UE is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present) prior to receiving the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message being set to "Access identity 2 valid".
When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFUAC_AIC as specified in 3GPP TS 31.102 [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access identity 2. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EFUAC_AIC does not indicate the UE is configured for access identity 2, 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. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EFUAC_AIC indicates the UE is configured for access identity 2, the MCS indicator bit of the 5GS network feature support IE is not applicable. When the UE is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFUAC_AIC are not applicable.
When the UE is in its HPLMN (if the EHPLMN list is not present or is empty) or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFACC as specified in 3GPP TS 31.102 [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access classes 11 and 15. When the UE is not in its HPLMN (if the EHPLMN list is not present or is empty) or in an EHPLMN (if the EHPLMN list is present), access classes 11 and 15 are not applicable.
When the UE is in the country of its HPLMN, the contents of the USIM file EFACC as specified in 3GPP TS 31.102 [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access classes 12 – 14. When the UE is not in the country of its HPLMN, access classes 12-14 are not applicable.
In order to determine the access category applicable for the access attempt, the NAS shall check the rules in table 4.5.2.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 subclause 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.
Table 4.5.2.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 message without an ongoing 5GC-MO-LR procedure; Access attempt to handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access |
Access attempt is for MT access, or handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access |
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 |
||||
|
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 3GPP TS 24.368 [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102 [22]), 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 |
(a) UE is configured for NAS signalling low priority or UE supporting S1 mode is configured for EAB (see the "ExtendedAccessBarring" leaf of NAS configuration MO in 3GPP TS 24.368 [17] or 3GPP TS 31.102 [22]) where "EAB override" does not apply, 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 PLMN or RPLMN/equivalent PLMN (NOTE 3, NOTE 5, NOTE 6, NOTE 7, NOTE 8) |
1 (= delay tolerant) |
||||
|
4.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) |
||||
|
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) |
||||
|
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) |
||||
|
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 RLPMN or 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 3GPP TS 24.368 [17] or 3GPP TS 31.102 [22], 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 3GPP TS 24.368 [17] or 3GPP TS 31.102 [22]), 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 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: NOTE 10: This includes: |
|||||||
[TS 24.501, clause 4.5.4.2]
When the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication, upon detecting one of events 1) through 8) listed in subclause 4.5.1, the NAS shall categorize the corresponding access attempt into access identities and an access category following:
a) subclause 4.5.2, table 4.5.2.1 and table 4.5.2.2, and subclause 4.5.2.3, if the UE is not operating in SNPN access mode; or
b) subclause 4.5.2A, table 4.5.2A.1 and table 4.5.2A.2, and subclause 4.5.3, if the UE is operating in SNPN access mode,
and provide the access identities and the access category to the lower layers for the purpose of access control checking. In this request to the lower layer the NAS can also provide to the lower layer the RRC establishment cause determined as specified in subclause 4.5.6 of this specification.
NOTE 1: As an implementation option, the NAS can provide the RRC establishment cause to the lower layers after being informed by the lower layers that the access attempt is allowed.
If the UE has uplink user data pending for one or more PDU sessions when it builds a REGISTRATION REQUEST or SERVICE REQUEST message for the access attempt, the UE shall indicate the respective PDU sessions in the Uplink data status IE as specified in subclause 5.5.1.3.2 and 5.6.1.2, regardless of the access category for which the access barring check is performed.
NOTE 2: The UE indicates pending user data for all the respective PDU sessions, even if barring timers are running for some of the corresponding access categories.
If the lower layers indicate that the access attempt is allowed, the NAS shall take the following action depending on the event which triggered the access attempt:
a) if the event which triggered the access attempt was an MO-MMTEL-voice-call-started indication, an MO-MMTEL-video-call-started indication, an MO-SMSoIP-attempt-started indication, or an MO-IMS-registration-related-signalling-started indication, the NAS shall notify the upper layers that the access attempt is allowed;
b) if the event which triggered the access attempt was a request from upper layers to send a mobile originated SMS over NAS, 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the SMS in an UL NAS TRANSPORT message;
c) if the event which triggered the access attempt was a request from upper layers to establish a new PDU session, 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the PDU SESSION ESTABLISHMENT REQUEST message;
d) if the event which triggered the access attempt was a request from upper layers to modify an existing PDU session, 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the PDU SESSION MODIFICATION REQUEST message;
e) if the event which triggered the access attempt was a request to re-establish the user-plane resources for an existing PDU session, 5GMM shall initiate the service request procedure as specified in subclause 5.6.1;
f) if the event which triggered the access attempt was an uplink user data packet to be sent for a PDU session with suspended user-plane resources, 5GMM shall consider that the uplink user data packet is allowed to be sent;
g) if the event which triggered the access attempt was a request from upper layers to send a mobile originated location request, 5GMM shall initiate the NAS transport procedure as specified in clause 5.4.5 to send an LCS message in an UL NAS TRANSPORT message; and
h) if the event which triggered the access attempt was a request from upper layers to send a mobile originated signalling transaction towards the PCF by sending an UL NAS TRANSPORT message including a UE policy container (see 3GPP TS 24.587 [19B]), 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the signalling transaction via an UL NAS TRANSPORT message.
If the lower layers indicate that the access attempt is barred, the NAS shall take the following action depending on the event which triggered the access attempt:
a) if the event which triggered the access attempt was an MO-MMTEL-voice-call-started indication, an MO-MMTEL-video-call-started indication or an MO-SMSoIP-attempt-started indication, or an MO-IMS-registration-related-signalling-started indication:
1) if the UE is operating in the dual-registration mode, the UE may proceed in S1 mode with the appropriate EMM specific procedures and ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.3 and 3GPP TS 24.301 [15];
2) otherwise, the NAS shall notify the upper layers that the access attempt is barred. In this case, upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall notify the upper layers that the barring is alleviated for the access category;
NOTE 3: In this case prohibiting the initiation of the MMTEL voice session, MMTEL video session or prohibiting sending of the SMS over IP or the IMS registration related signalling is performed by the upper layers.
b) if the event which triggered the access attempt was a request from upper layers to send a mobile originated SMS over NAS, 5GMM shall not initiate the NAS transport procedure as specified in subclause 5.4.5 to send the SMS in an UL NAS TRANSPORT message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, 5GMM may initiate the NAS transport procedure as specified in subclause 5.4.5 to send the SMS in an UL NAS TRANSPORT message, if still needed;
c) if the event which triggered the access attempt was a request from upper layers to establish a new PDU session, 5GMM shall not initiate the NAS transport procedure to send the PDU SESSION ESTABLISHMENT REQUEST message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS may initiate the NAS transport procedure as specified in subclause 5.4.5, if still needed;
d) if the event which triggered the access attempt was a request from upper layers to modify an existing PDU session modification, 5GMM shall not initiate the NAS transport procedure to send the PDU SESSION MODIFICATION REQUEST message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS may initiate the NAS transport procedure as specified in subclause 5.4.5, if still needed;
e) if the event which triggered the access attempt was a request to re-establish the user-plane resources for an existing PDU session, the NAS shall not initiate the service request procedure as specified in subclause 5.6.1. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS may initiate the service request procedure as specified in subclause 5.6.1, if still needed;
f) if the event which triggered the access attempt was an uplink user data packet to be sent for a PDU session with suspended user-plane resources, 5GMM shall consider that the uplink user data packet is not allowed to be sent. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall consider that the barring is alleviated for the access category;
g) if the event which triggered the access attempt was a request from upper layers to send a mobile originated location request, 5GMM shall not initiate the NAS transport procedure as specified in clause 5.4.5 to send an LCS message in an UL NAS TRANSPORT message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, 5GMM may initiate the NAS transport procedure as specified in clause 5.4.5 to send the LCS message in an UL NAS TRANSPORT message, if still needed; and
h) if the event which triggered the access attempt was a request from upper layers to send a mobile originated signalling transaction towards the PCF by sending an UL NAS TRANSPORT message including a UE policy container (see 3GPP TS 24.587 [19B]), 5GMM shall not initiate the NAS transport procedure as specified in subclause 5.4.5 to send the mobile originated signalling transaction via an UL NAS TRANSPORT message. Upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, 5GMM may initiate the NAS transport procedure as specified in subclause 5.4.5 to send the mobile originated signalling transaction via an UL NAS TRANSPORT message, if still needed.
[TS 24.501, clause 4.5.6]
When 5GMM requests the establishment of a NAS-signalling connection, the RRC establishment cause used by the UE shall be selected according to one or more access identities (see subclauses 4.5.2 and 4.5.2A) and the determined access category by checking the rules specified in table 4.5.6.1 and table 4.5.6.2. If the access attempt matches more than one rule, the RRC establishment cause of the lowest rule number shall be used. If the determined access category is an operator-defined access category, then the RRC establishment cause used by the UE shall be selected according to table 4.5.6.1 and table 4.5.6.2 based on one or more access identities (see subclauses 4.5.2 and 4.5.2A) and the standardized access category determined for the operator-defined access category as described in subclause 4.5.3.
Table 4.5.6.1: Mapping table for access identities/access categories and RRC establishment cause when establishing N1 NAS signalling connection via NR connected to 5GCN
|
Rule # |
Access identities |
Access categories |
RRC establishment cause is set to |
|
1 |
1 |
Any category |
mps-PriorityAccess |
|
2 |
2 |
Any category |
mcs-PriorityAccess |
|
3 |
11, 15 |
Any category |
highPriorityAccess |
|
4 |
12,13,14, |
Any category |
highPriorityAccess |
|
5 |
0 |
0 (= MT_acc) |
mt-Access |
|
1 (= delay tolerant) |
Not applicable (NOTE 1) |
||
|
2 (= emergency) |
emergency |
||
|
3 (= MO_sig) |
mo-Signalling |
||
|
4 (= MO MMTel voice) |
mo-VoiceCall |
||
|
5 (= MO MMTel video) |
mo-VideoCall |
||
|
6 (= MO SMS and SMSoIP) |
mo-SMS |
||
|
7 (= MO_data) |
mo-Data |
||
|
9 (= MO IMS registration related signalling) |
mo-Data |
||
|
NOTE 1: A UE using access category 1 for the access barring check will determine a second access category in the range 3 to 7 that is to be used for determination of the RRC establishment cause. See subclause 4.5.2, table 4.5.2.2, NOTE 6. NOTE 2: See subclause 4.5.2, table 4.5.2.1 for use of the access identities of 0, 1, 2, and 11-15. |
|||
Table 4.5.6.2: Mapping table for access identities/access categories and RRC establishment cause when establishing N1 NAS signalling connection via E-UTRA connected to 5GCN
|
Rule # |
Access identities |
Access categories |
RRC establishment cause is set to |
|
1 |
1 |
Any category |
highPriorityAccess |
|
2 |
2 |
Any category |
highPriorityAccess |
|
3 |
11, 15 |
Any category |
highPriorityAccess |
|
4 |
12,13,14, |
Any category |
highPriorityAccess |
|
5 |
0 |
0 (= MT_acc) |
mt-Access |
|
1 (= delay tolerant) |
Not applicable (NOTE 1) |
||
|
2 (= emergency) |
emergency |
||
|
3 (= MO_sig) |
mo-Signalling |
||
|
4 (= MO MMTel voice) |
mo-VoiceCall |
||
|
5 (= MO MMTel video) |
mo-VoiceCall |
||
|
6 (= MO SMS and SMSoIP) |
mo-Data |
||
|
7 (= MO_data) |
mo-Data |
||
|
9 (= MO IMS registration related signalling) |
mo-Data |
||
|
10 (= MO exception data) |
mo-ExceptionData (NOTE 3) |
||
|
NOTE 1: A UE using access category 1 for the access barring check will determine a second access category in the range 3 to 7 that is to be used for determination of the RRC establishment cause. See subclause 4.5.2, table 4.5.2.2, NOTE 6. NOTE 2: See subclause 4.5.2, table 4.5.2.1 for use of the access identities of 0, 1, 2, and 11-15. NOTE 3: This applies to the UE in NB-N1 mode. |
|||
[TS 38.331, clause 5.3.14.1]
The purpose of this procedure is to perform access barring check for an access attempt associated with a given Access Category and one or more Access Identities upon request from upper layers according to TS 24.501 [23] or the RRC layer. This procedure does not apply to IAB-MT.
After a PCell change in RRC_CONNECTED the UE shall defer access barring checks until it has obtained SIB1 (as specified in 5.2.2.2) from the target cell.
[TS 38.331, clause 5.3.14.2]
Upon initiation of the procedure, the UE shall:
1> if timer T390 is running for the Access Category:
2> consider the access attempt as barred;
1> else if timer T302 is running and the Access Category is neither ‘2’ nor ‘0’:
2> consider the access attempt as barred;
1> else:
2> if the Access Category is ‘0’:
3> consider the access attempt as allowed;
2> else:
3> if SIB1 includes uac-BarringPerPLMN-List that contains a UAC-BarringPerPLMN for the selected PLMN or SNPN:
4> if the procedure in 5.2.2.4.2 for a selected PLMN resulted in use of information in npn-IdentityInfoList and UAC-BarringPerPLMN has an entry with the plmn-IdentityIndex corresponding to used information in this list:
5> select the UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to used information in the npn-IdentityInfoList;
4> else:
5> select the UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the selected PLMN and the PLMN-IdentityInfo, if any, or the selected SNPN and the npn-IdentityInfoList;
3> if any UAC-BarringPerPLMN entry is selected:
4> in the remainder of this procedure, use the selected UAC-BarringPerPLMN entry (i.e. presence or absence of access barring parameters in this entry) irrespective of the uac-BarringForCommon included in SIB1;
3> else if SIB1 includes uac-BarringForCommon:
4> in the remainder of this procedure use the uac-BarringForCommon (i.e. presence or absence of these parameters) included in SIB1;
3> else:
4> consider the access attempt as allowed;
3> if uac-BarringForCommon is applicable or the uac-ACBarringListType indicates that uac-ExplicitACBarringList is used:
4> if the corresponding UAC-BarringPerCatList contains a UAC-BarringPerCat entry corresponding to the Access Category:
5> select the UAC-BarringPerCat entry;
5> if the uac-BarringInfoSetList contains a UAC-BarringInfoSet entry corresponding to the selected uac-barringInfoSetIndex in the UAC-BarringPerCat:
6> select the UAC-BarringInfoSet entry;
6> perform access barring check for the Access Category as specified in 5.3.14.5, using the selected UAC-BarringInfoSet as "UAC barring parameter";
5> else:
6> consider the access attempt as allowed;
4> else:
5> consider the access attempt as allowed;
3> else if the uac-ACBarringListType indicates that uac-ImplicitACBarringList is used:
4> select the uac-BarringInfoSetIndex corresponding to the Access Category in the uac-ImplicitACBarringList;
4> if the uac-BarringInfoSetList contains the UAC-BarringInfoSet entry corresponding to the selected uac-BarringInfoSetIndex:
5> select the UAC-BarringInfoSet entry;
5> perform access barring check for the Access Category as specified in 5.3.14.5, using the selected UAC-BarringInfoSet as "UAC barring parameter";
4> else:
5> consider the access attempt as allowed;
3> else:
4> consider the access attempt as allowed;
1> if the access barring check was requested by upper layers:
2> if the access attempt is considered as barred:
3> if timer T302 is running:
4> if timer T390 is running for Access Category ‘2’:
5> inform the upper layer that access barring is applicable for all access categories except categories ‘0’, upon which the procedure ends;
4> else
5> inform the upper layer that access barring is applicable for all access categories except categories ‘0’ and ‘2’, upon which the procedure ends;
3> else:
4> inform upper layers that the access attempt for the Access Category is barred, upon which the procedure ends;
2> else:
3> inform upper layers that the access attempt for the Access Category is allowed, upon which the procedure ends;
1> else:
2> the procedure ends.
[TS 38.331, clause 5.3.14.4]
The UE shall:
1> if timer T302 expires or is stopped:
2> for each Access Category for which T390 is not running:
3> consider the barring for this Access Category to be alleviated:
1> else if timer T390 corresponding to an Access Category other than ‘2’ expires or is stopped, and if timer T302 is not running:
2> consider the barring for this Access Category to be alleviated;
1> else if timer T390 corresponding to the Access Category ‘2’ expires or is stopped:
2> consider the barring for this Access Category to be alleviated;
1> when barring for an Access Category is considered being alleviated:
2> if the Access Category was informed to upper layers as barred:
3> inform upper layers about barring alleviation for the Access Category.
2> if barring is alleviated for Access Category ‘8’; or
2> if barring is alleviated for Access Category ‘2’:
3> perform actions specified in 5.3.13.8;
[TS 38.331, clause 5.3.14.5]
The UE shall:
1> if one or more Access Identities are indicated according to TS 24.501 [23], and
1> if for at least one of these Access Identities the corresponding bit in the uac-BarringForAccessIdentity contained in "UAC barring parameter" is set to zero:
2> consider the access attempt as allowed;
1> else:
2> if the establishment of the RRC connection is the result of release with redirect with mpsPriorityIndication (either in NR or E-UTRAN); and
2> if the bit corresponding to Access Identity 1 in the uac-BarringForAccessIdentity contained in the "UAC barring parameter" is set to zero:
3> consider the access attempt as allowed;
2> else:
3> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;
3> if ‘rand‘ is lower than the value indicated by uac-BarringFactor included in "UAC barring parameter":
4> consider the access attempt as allowed;
3> else:
4> consider the access attempt as barred;
1> if the access attempt is considered as barred:
2> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;
2> start timer T390 for the Access Category with the timer value calculated as follows, using the uac-BarringTime included in "UAC barring parameter":
T390 = (0.7+ 0.6 * rand) * uac-BarringTime.
11.3.10.3 Test description
11.3.10.3.1 Pre-test conditions
System Simulator:
– NR Cell 1.
– Cell power level is selected according to 38.508-1 [4] Table 6.2.2.1-3.
– System information combination NR-1 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1 is used in NR cell 1.
UE:
– None.
Preamble:
– The UE is switched on and brought to state 3N-A in accordance with the procedure described in TS 38.508-1 [4] and IMS PDU session establishment is completed on NR Cell 1.
11.3.10.3.2 Test procedure sequence
Table 11.3.10.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1-8 |
Steps 1-8 of initial IMS registration procedure as defined in Annex A.2 of TS 34.229-5 [41] take place, with SS giving 120 seconds expiration interval. |
||||
|
9 |
The SS changes the SIB1 according to 38.508-1[4] Table 11.3.10.3.3-2 and send Short Message on PDCCH using P-RNTI. |
<– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
9A |
Wait for 2.1* modification period to allow the new system information to take effect |
||||
|
10 |
Check: Does the UE performs SIP re-registration message in a time span between half of the expiration time and the full expiration time? (Note: in this test case, the re-registration time is set to an untypically short value of 120 seconds. As there are no requirements on the duration of a re-registration procedure it is only checked that the re-registration procedure starts between half of the expiration time and the full expiration time.) |
–> |
REGISTER: Re-Registration |
1 |
F |
|
11 |
The SS changes the SIB1 according to 38.508-1 [4] Table 4.6.1-28 and transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification |
<– |
PDCCH (DCI 1_0): Short Message |
||
|
11A |
Wait for 2.1* modification period to allow the new system information to take effect |
||||
|
12 |
Check: Does the UE performs SIP REGISTER message? |
–> |
REGISTER: Re-Registration |
2 |
P |
|
13 |
SS responds with 200 OK |
<– |
200 OK |
||
|
Note 1: T390 is a random value between (0.7 + 0.6 * 0) * uac-BarringTime(4s) = 2.8s and (0.7 + 0.6 * 1) * uac-BarringTime(4s) = 5.2s, |
|||||
11.3.10.3.3 Specific message contents
Table 11.3.10.3-1: 200 OK for REGISTER (step 4, Table 11.3.10.3.2-1)
|
Derivation path: TS 34.229-1 [2], Table in subclause A.1.3 |
||||
|---|---|---|---|---|
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|
Contact |
||||
|
expires |
120 |
|||
Table 11.3.10.3.3-2: SIB1 of NR Cell 1 (step9, Table 11.3.10.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB1 ::= SEQUENCE { |
|||
|
uac-BarringInfo SEQUENCE { |
|||
|
uac-BarringForCommon SEQUENCE (SIZE (1..maxAccessCat-1)) OF UAC-BarringPerCat { |
1 entries |
||
|
UAC-BarringPerCat[1] SEQUENCE { |
entry 1 |
||
|
accessCategory |
9 |
(= MO IMS registration related signalling) |
|
|
uac-barringInfoSetIndex |
1 |
||
|
} |
|||
|
} |
|||
|
uac-BarringPerPLMN-List |
Not present |
||
|
uac-BarringInfoSetList SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet { |
1 entry |
||
|
UAC-BarringInfoSet[1] SEQUENCE { |
entry 1 |
||
|
uac-BarringFactor |
p00 |
0 % access probability |
|
|
uac-BarringTime |
s4 |
4 s |
|
|
uac-BarringForAccessIdentity |
‘0000000’B |
||
|
} |
|||
|
} |
|||
|
uac-AccessCategory1-SelectionAssistanceInfo |
Not Present |
||
|
} |
|||
|
} |
|||