11.3.4 UAC / Access Identity 0 / Registration procedure for mobility and periodic registration update / Barring per PLMN / Implicit AC barring list
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
11.3.4.1 Test Purpose (TP)
(1)
with { UE in NR RRC_IDLE not configured for special AIs (1,2,11-15) having received a SIB1 message including UAC set to 0% accessibility for Access Category 3 }
ensure that {
when { UE finds a new cell (AC 3) with SIB1 containing UAC Barring Info Per PLMN with Implicit AC Barring List }
then { UE does not access the new cell until access barring is alleviated }
}
11.3.4.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.1 and 5.5.1.3.7, TS 38.331 clause 5.3.14.2, 5.3.14.4 and 5.3.14.5. Unless otherwise stated these are Rel-15 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]). |
|
…
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 |
Access attempt is for MT 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 (= based on operator classification) |
|
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) |
|
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) |
|
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, or for the purpose of NAS signalling connection establishment following fallback indication from lower layers during an ongoing service, 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 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]). |
|||
[TS 24.501, clause 4.5.4.1]
When the UE is in 5GMM-IDLE mode, upon receiving a request from the upper layers for an access attempt, the NAS shall categorize the access attempt into access identities and an access category following subclause 4.5.2, table 4.5.2.1 and table 4.5.2.2, and subclause 4.5.3, and provide the applicable 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: The access barring check is performed by the lower layers.
NOTE 2: 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 lower layers indicate that the access attempt is allowed, the NAS shall initiate the procedure to send the initial NAS message for the access attempt.
If the lower layers indicate that the access attempt is barred, the NAS shall not initiate the procedure to send the initial NAS message for the access attempt. Additionally:
a) if the event which triggered the access attempt was an MO-MMTEL-voice-call-started indication or an MO-MMTEL-video-call-started indication:
1) if the UE is operating in the single-registration mode and the UE’s usage setting is "voice centric", the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, it then proceeds with the appropriate EMM specific procedures and, if necessary, ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.2 and 3GPP TS 24.301 [15];
2) 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];
3) 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 and may initiate the procedure to send the initial NAS message, if still needed; and
b) if the event which triggered the access attempt was an MO-SMSoIP-attempt-started indication:
1) if the UE is operating in the single-registration mode, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, it then proceeds with the appropriate EMM specific procedures and, if necessary, ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.2 and 3GPP TS 24.301 [15];
2) 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];
3) otherwise, the NAS layer 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 and may initiate the procedure to send the initial NAS message, if still needed.
NOTE 4: Barring timers, on a per access category basis, are run by the lower layers. At expiry of barring timers, the indication of alleviation of access barring is indicated to the NAS on a per access category basis.
[TS 24.501, clause 5.5.1.3.7]
b) The lower layers indicate that the access attempt is barred.
The UE shall not start the registration procedure for mobility and periodic registration update. The UE stays in the current serving cell and applies the normal cell reselection process.
The registration procedure for mobility and periodic registration update is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated.
ba) The lower layers indicate that access barring is applicable for all access categories except categories 0 and 2 and the access category with which the access attempt was associated is other than 0 and 2.
If the REGISTRATION REQUEST message has not been sent, the UE shall proceed as specified for case b. If the REGISTRATION REQUEST message has been sent, the UE shall proceed as specified for case e and, additionally, the registration procedure for mobility and periodic registration update is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated. For additional UE requirements for both cases see subclause 4.5.5.
[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:
2> if the Access Category is ‘0’:
3> consider the access attempt as allowed;
2> else:
3> if SIB1 includes uac-BarringPerPLMN-List and the uac-BarringPerPLMN-List contains an UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers (see TS 24.501 [23]):
4> select the UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers;
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 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> 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> 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.
[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> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;
2> if ‘rand‘ is lower than the value indicated by uac-BarringFactor included in "UAC barring parameter":
3> consider the access attempt as allowed;
2> else:
3> 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 "AC barring parameter":
T390 = (0.7+ 0.6 * rand) * uac-BarringTime.
11.3.4.3 Test description
11.3.4.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 and NR Cell 11 have different tracking areas according to TS 38.508-1 [4] Table 4.4.2-3.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR Cells.
UE:
– None.
Preamble:
– The UE is in state 1N-A on NR cell 1 according to TS 38.508-1 [4] Table 4.4A.2-1.
11.3.4.3.2 Test procedure sequence
Table 11.3.4.3.2-1/2 illustrate the downlink power levels and other changing parameters to be applied for the cell at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause. The configuration T0 indicates the initial conditions for preamble. Configurations marked "T1" is applied at the points indicated in the Main behaviour description in Table 11.3.4.3.2-3.
Table 11.3.4.3.2-1: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 11 |
Remark |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
Off |
|
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-80 |
The power level values are assigned to satisfy RNRCell 1 < RNRCell 11 |
Table 11.3.4.3.2-2: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 11 |
Remark |
|
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-91 |
Off |
|
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-91 |
-82 |
The power level values are assigned to satisfy RNRCell 1 < RNRCell 11 |
Table 11.3.4.3.2-3: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Void |
||||
|
2 |
The SS adjusts the SS/PBCH EPRE levels and according to row "T1" in table 11.3.4.3.2-1/2. |
– |
– |
– |
– |
|
3 |
Wait for 34s for FR1 or 130s for FR2 to allow UE to recognise the change.(Note 1) |
||||
|
3A |
Wait for 84s for T390 to expire (Note 2) |
– |
– |
– |
– |
|
4 |
Check: Does the UE transmit an RRCSetupRequest message on NR cell 11? |
–> |
NR RRC: RRCSetupRequest |
1 |
F |
|
5 |
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 |
– |
– |
|
6 |
Wait for one paging cycle. |
||||
|
7 |
Void |
||||
|
8 |
Check: Does UE transmit RRCSetupRequest message on NR cell 11? |
–> |
NR RRC: RRCSetupRequest |
1 |
P |
|
9-12 |
Steps 2 to 5 of the generic test procedure in TS 38.508-1 Table 4.9.5.2.2-1 with condition MOBILITY are performed on NR cell 11. NOTE: The UE performs a " REGISTRATION REQUEST procedure with type "mobility registration updating”. |
– |
– |
– |
– |
|
Note 1: The wait time for reselection to a newly detected intra frequency cell is selected to cover Tdetect,NR_Intra (25*1280ms=32s for FR1 and 25*4*1280ms=128s for FR2) + TSI-NR (11280ms= fo FR2 1.28s for FR1 and FR2) = 33.28s rounded up to 34s for FR1 and 129.28s rounded up to 130s for FR2. Note 2: T390 timer value is derived from 38.331 [12] T390 = (0.7 + 0.6*rand)*uac-BarringTime where the uac-BarringTime value of 64s is provided in 38.523 Table 11.3.4.3.3-1 and where the value of rand is chosen to be 1 as to arrive at the maximum value for T390 of 83.2s rounded up to 84s |
|||||
11.3.4.3.3 Specific message contents
Table 11.3.4.3.3-1: SIB1 for NR Cell 11 (Preamble, Table 11.3.4.3.3-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB1 ::= SEQUENCE { |
|||
|
cellAccessRelatedInfo SEQUENCE { |
|||
|
PLMN-IdentityInfoList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfo { |
1 entry |
||
|
PLMN-IdentityInfo[1] SEQUENCE { |
entry 1 |
||
|
plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity { |
1 entry |
||
|
plmn-Identity[1] |
entry 1 PLMN ID of NR Cell 11 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
uac-BarringInfo SEQUENCE { |
|||
|
uac-BarringForCommon |
Not present |
||
|
uac-BarringPerPLMN-List SEQUENCE (SIZE (1.. maxPLMN)) OF UAC-BarringPerPLMN { |
|||
|
UAC-BarringPerPLMN SEQUENCE { |
|||
|
plmn-IdentityIndex |
1 |
||
|
uac-ACBarringListType CHOICE { |
|||
|
uac-ImplicitACBarringList SEQUENCE (SIZE(maxAccessCat-1)) OF UAC-BarringInfoSetIndex { |
63 entries |
||
|
UAC-BarringInfoSetIndex[1] |
2 |
entry 1 |
|
|
UAC-BarringInfoSetIndex[2] |
2 |
entry 2 |
|
|
UAC-BarringInfoSetIndex[3] |
1 |
entry 3 |
|
|
UAC-BarringInfoSetIndex[4] |
2 |
entry 4 |
|
|
UAC-BarringInfoSetIndex[5] |
2 |
entry 5 |
|
|
UAC-BarringInfoSetIndex[6] |
2 |
entry 6 |
|
|
UAC-BarringInfoSetIndex[7] |
2 |
entry 7 |
|
|
UAC-BarringInfoSetIndex[8] |
2 |
entry 8 |
|
|
UAC-BarringInfoSetIndex[9] |
2 |
entry 9 |
|
|
UAC-BarringInfoSetIndex[10] |
2 |
entry 10 |
|
|
UAC-BarringInfoSetIndex[11] |
2 |
entry 11 |
|
|
UAC-BarringInfoSetIndex[12] |
2 |
entry 12 |
|
|
UAC-BarringInfoSetIndex[13] |
2 |
entry 13 |
|
|
UAC-BarringInfoSetIndex[14] |
2 |
entry 14 |
|
|
UAC-BarringInfoSetIndex[15] |
2 |
entry 15 |
|
|
UAC-BarringInfoSetIndex[16] |
2 |
entry 16 |
|
|
UAC-BarringInfoSetIndex[17] |
2 |
entry 17 |
|
|
UAC-BarringInfoSetIndex[18] |
2 |
entry 18 |
|
|
UAC-BarringInfoSetIndex[19] |
2 |
entry 19 |
|
|
UAC-BarringInfoSetIndex[20] |
2 |
entry 20 |
|
|
UAC-BarringInfoSetIndex[21] |
2 |
entry 21 |
|
|
UAC-BarringInfoSetIndex[22] |
2 |
entry 22 |
|
|
UAC-BarringInfoSetIndex[23] |
2 |
entry 23 |
|
|
UAC-BarringInfoSetIndex[24] |
2 |
entry 24 |
|
|
UAC-BarringInfoSetIndex[25] |
2 |
entry 25 |
|
|
UAC-BarringInfoSetIndex[26] |
2 |
entry 26 |
|
|
UAC-BarringInfoSetIndex[27] |
2 |
entry 27 |
|
|
UAC-BarringInfoSetIndex[28] |
2 |
entry 28 |
|
|
UAC-BarringInfoSetIndex[29] |
2 |
entry 29 |
|
|
UAC-BarringInfoSetIndex[30] |
2 |
entry 30 |
|
|
UAC-BarringInfoSetIndex[31] |
2 |
entry 31 |
|
|
UAC-BarringInfoSetIndex[32] |
2 |
entry 32 |
|
|
UAC-BarringInfoSetIndex[33] |
2 |
entry 33 |
|
|
UAC-BarringInfoSetIndex[34] |
2 |
entry 34 |
|
|
UAC-BarringInfoSetIndex[35] |
2 |
entry 35 |
|
|
UAC-BarringInfoSetIndex[36] |
2 |
entry 36 |
|
|
UAC-BarringInfoSetIndex[37] |
2 |
entry 37 |
|
|
UAC-BarringInfoSetIndex[38] |
2 |
entry 38 |
|
|
UAC-BarringInfoSetIndex[39] |
2 |
entry 39 |
|
|
UAC-BarringInfoSetIndex[40] |
2 |
entry 40 |
|
|
UAC-BarringInfoSetIndex[41] |
2 |
entry 41 |
|
|
UAC-BarringInfoSetIndex[42] |
2 |
entry 42 |
|
|
UAC-BarringInfoSetIndex[43] |
2 |
entry 43 |
|
|
UAC-BarringInfoSetIndex[44] |
2 |
entry 44 |
|
|
UAC-BarringInfoSetIndex[45] |
2 |
entry 45 |
|
|
UAC-BarringInfoSetIndex[46] |
2 |
entry 46 |
|
|
UAC-BarringInfoSetIndex[47] |
2 |
entry 47 |
|
|
UAC-BarringInfoSetIndex[48] |
2 |
entry 48 |
|
|
UAC-BarringInfoSetIndex[49] |
2 |
entry 49 |
|
|
UAC-BarringInfoSetIndex[50] |
2 |
entry 50 |
|
|
UAC-BarringInfoSetIndex[51] |
2 |
entry 51 |
|
|
UAC-BarringInfoSetIndex[52] |
2 |
entry 52 |
|
|
UAC-BarringInfoSetIndex[53] |
2 |
entry 53 |
|
|
UAC-BarringInfoSetIndex[54] |
2 |
entry 54 |
|
|
UAC-BarringInfoSetIndex[55] |
2 |
entry 55 |
|
|
UAC-BarringInfoSetIndex[56] |
2 |
entry 56 |
|
|
UAC-BarringInfoSetIndex[57] |
2 |
entry 57 |
|
|
UAC-BarringInfoSetIndex[58] |
2 |
entry 58 |
|
|
UAC-BarringInfoSetIndex[59] |
2 |
entry 59 |
|
|
UAC-BarringInfoSetIndex[60] |
2 |
entry 60 |
|
|
UAC-BarringInfoSetIndex[61] |
2 |
entry 61 |
|
|
UAC-BarringInfoSetIndex[62] |
2 |
entry 62 |
|
|
UAC-BarringInfoSetIndex[63] |
2 |
entry 63 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
uac-BarringInfoSetList SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet { |
1 entry |
||
|
UAC-BarringInfoSet[1] SEQUENCE { |
entry 1 |
||
|
uac-BarringFactor |
p00 |
||
|
uac-BarringTime |
s64 |
||
|
uac-BarringForAccessIdentity |
‘0000000’B |
||
|
} |
|||
|
uac-AccessCategory1-SelectionAssistanceInfo |
Not Present |
||
|
} |
|||
|
} |
|||
|
Note：UAC-BarringInfoSetIndex value 2 referring to an entry not included in uac-BarringInfoSetList indicates no barring for the Access Category. |
|||