Content for TS 38.331 Word version: 18.0.0

1… 4… 5… 5.2.2.4… 5.3… 5.3.3… 5.3.5… 5.3.5.5… 5.3.5.6… 5.3.5.7… 5.3.5.13… 5.3.5.17… 5.3.6… 5.3.8… 5.3.13… 5.3.14… 5.4… 5.5… 5.5.3… 5.5.4… 5.5.4.15… 5.5.4.23… 5.5.5… 5.5a… 5.7… 5.7.4… 5.7.8… 5.7.12… 5.8… 5.8.9… 5.8.9.2… 5.8.9.8… 5.8.10… 5.8.11… 5.9… 5.10… 6… 6.2.2… 6-2-2-23… 6-2-2-27… 6-2-2-43… 6-2-2-47… 6.3… 6.3.2… 6-3-2-27… 6-3-2-49… 6-3-2-73… 6-3-2-95… 6-3-2-108… 6-3-2-134… 6-3-2-162… 6-3-2-188… 6-3-2-213… 6-3-2-243… 6-3-2-271… 6-3-2-297… 6-3-2-341… 6.3.3… 6-3-3-25… 6-3-3-51… 6.3.4… 6.3.5… 6-3-5-25… 6.3.6… 6.4… 7… 9… 11… A… A.4… B…

5.3.14 Unified Access Control 5.3.14.1 General 5.3.14.2 Initiation 5.3.14.4 T302, T390 expiry or stop (Barring alleviation) 5.3.14.5 Access barring check 5.3.15 RRC connection reject 5.3.15.1 Initiation 5.3.15.2 Reception of the RRCReject by the UE
...

5.3.14 Unified Access Control p. 206

5.3.14.1 General p. 206

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 or the RRC layer. This procedure does not apply to IAB-MT and NCR-MT. This procedure does not apply to L2 U2N Relay UE initiating RRC connection establishment or RRC connection resume upon reception of any message from a L2 U2N remote UE via SL-RLC0 or SL-RLC1 in accordance to clause 5.3.3.1a or 5.3.13.1a.

After a PCell change in RRC_CONNECTED the UE shall defer access barring checks until it has obtained SIB1 (as specified in clause 5.2.2.2) from the target cell.

5.3.14.2 Initiation p. 206

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 clause 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 clause 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 clause 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.

5.3.14.3 Void

5.3.14.4 T302, T390 expiry or stop (Barring alleviation) p. 208

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 >

else if the Access Category is Access Category '0':

3 >

perform actions specified in clause 5.3.13.1d;

2 >

if barring is alleviated for Access Category '8'; or

2 >

if barring is alleviated for Access Category '2':

3 >

perform actions specified in clause 5.3.13.8;

5.3.14.5 Access barring check p. 208

The UE shall:

1 >

if one or more Access Identities equal to 1, 2, 11, 12, 13, 14, or 15 are indicated according to TS 24.501, 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 if Access Identity 3 is indicated:

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-BarringFactorForAI3 included in "UAC barring parameter":

4 >

consider the access attempt as allowed;

3 >

else:

4 >

consider the access attempt as barred;

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.

5.3.15 RRC connection reject p. 209

5.3.15.1 Initiation p. 209

The UE initiates the procedure upon the reception of RRCReject when the UE tries to establish or resume an RRC connection.

5.3.15.2 Reception of the RRCReject by the UE p. 209

The UE shall:

1 >

stop timer T300, if running;

1 >

stop timer T319, if running;

1 >

stop timer T319a, if running and consider SDT procedure is not ongoing;

1 >

stop timer T302, if running;

1 >

reset MAC and release the default MAC Cell Group configuration;

1 >

if waitTime is configured in the RRCReject:

2 >

start timer T302, with the timer value set to the waitTime;

1 >

if RRCReject is received in response to a request from upper layers:

2 >

inform the upper layer that access barring is applicable for all access categories except categories '0' and '2';

1 >

if RRCReject is received in response to an RRCSetupRequest:

2 >

inform upper layers about the failure to setup the RRC connection, upon which the procedure ends;

1 >

else if RRCReject is received in response to an RRCResumeRequest or an RRCResumeRequest1:

2 >

if resume is triggered by upper layers:

3 >

inform upper layers about the failure to resume the RRC connection;

2 >

if resume is triggered due to an RNA update; or

2 >

if resume is triggered for SDT and T380 has expired:

3 >

set the variable pendingRNA-Update to true;

2 >

discard the current KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key derived in accordance with clause 5.3.13.3;

2 >

if resume is triggered for SDT:

3 >

for SRB2, if it is resumed and for SRB1:

4 >

trigger the PDCP entity to perform SDU discard as specified in TS 38.323;

4 >

re-establish the RLC entity as specified in TS 38.322;

3 >

for each DRB that is not suspended:

4 >

indicate PDCP suspend to lower layers;

4 >

re-establish the RLC entity as specified in TS 38.322;

2 >

suspend SRB1 and the radio bearers configured for SDT, if any;

2 >

the procedure ends.

Upon L2 U2N Relay UE receives RRCReject, it either indicates to upper layers (to trigger PC5 unicast link release) or sends NotificationMessageSidelink message to the connected L2 U2N Remote UE(s) in accordance with clause 5.8.9.10.

The RRC_INACTIVE UE shall continue to monitor paging while the timer T302 is running.