11.3.3 UAC / Access Identity 0 / AC8 / RRC_INACTIVE / RNA update / RRC resume

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

11.3.3.1 Test Purpose (TP)

(1)

with { UE not configured for special AIs (1,2,11-15) having received SIB1 indicating UAC info containing 0% accessibility for Access category 8 in NR RRC_INACTIVE state }

ensure that {

when { RRC connection is to be resumed due to an RNA update with no emergency services ongoing }

then { UE resume attempt is barred and UE does not attempt the connection }

}

(2)

with { SIB1 indicating UAC info containing 100% accessibility for Access category 8 in NR RRC_INACTIVE state }

ensure that {

when { Access Barring is alleviated for Access Category 8 & upper layers do not request resumption of an RRC connection & variable pendingRnaUpdate is set to true }

then { UE initiates RRC connection resume procedure with resumeCause value set to rna-Update }

}

11.3.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.3.13.2, 5.3.13.8, 5.3.14.2, 5.3.14.4 and 5.3.14.5. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.13.2]

The UE initiates the procedure when upper layers or AS (when responding to RAN paging or upon triggering RNA updates while the UE is in RRC_INACTIVE) requests the resume of a suspended RRC connection.

The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure.

Upon initiation of the procedure, the UE shall:

…

1> else if the resumption of the RRC connection is triggered due to an RNA update as specified in 5.3.13.8:

2> if an emergency service is ongoing:

NOTE: How the RRC layer in the UE is aware of an ongoing emergency service is up to UE implementation.

3> select ‘2’ as the Access Category;

3> set the resumeCause to emergency;

2> else:

3> select ‘8’ as the Access Category;

2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and one or more Access Identities to be applied as specified in TS 24.501 [23];

3> if the access attempt is barred:

4> set the variable pendingRnaUpdate to true;

4> the procedure ends;

[TS 38.331, clause 5.3.13.8]

In RRC_INACTIVE state, the UE shall:

1> if T380 expires; or

1> if RNA Update is triggered at reception of SIB1, as specified in 5.2.2.4.2:

2> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause set to rna-Update;

1> if barring is alleviated for Access Category ‘8’, as specified in 5.3.14.4:

2> if upper layers do not request RRC the resumption of an RRC connection, and

2> if the variable pendingRnaUpdate is set to true:

3> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause value set to rna-Update.

[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> 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;

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

2> if barring is alleviated for Access Category ‘8’:

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> 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.3.3 Test description

11.3.3.3.1 Pre-test conditions

System Simulator:

– NR Cell 1

– System information combination NR-1 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 2N-A on NR cell 1 according to TS 38.508-1 [4] Table 4.4A.2-2.

11.3.3.3.2 Test procedure sequence

Table 11.3.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Wait for 5 minute to make the timer T380 expire and trigger the RNA update procedure in UE.
2	Check: Does the UE transmit an RRCResumeRequest message with resumeCause value set to rna-Update on NR Cell 1 within 60s?	–>	NR RRC: RRCResumeRequest	1	F
3	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	–	–
4	Check: Does the UE transmit an RRCResumeRequest message with resumeCause value set to rna-Update on NR Cell 1?	–>	NR RRC: RRCResumeRequest	2	P
5	The SS transmits an RRCResume message.	<–	NR RRC: RRCResume	–	–
6	The UE transmits an RRCResumeComplete message.	–>	NR RRC: RRCResumeComplete	–	–

11.3.3.3.3 Specific message contents

Table 11.3.3.3.3-1: SIB1 for NR Cell 1 (preamble, Table 11.3.3.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 entry
UAC-BarringPerCat[1] SEQUENCE {		entry 1
accessCategory	8
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
uac-BarringTime	s64
uac-BarringForAccessIdentity	‘0000000’B
}
}
uac-AccessCategory1-SelectionAssistanceInfo	Not Present
}
}

Table 11.3.3.3.3-2: RRCRelease (preamble, Table 11.3.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
suspendConfig SEQUENCE {			NR_RRC_INACTIVE
t380	min5	5 minutes
}
}
}
}

Table 11.3.3.3.3-3: RRCResumeRequest (step 2 and step 5, Table 11.3.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-19
Information Element	Value/remark	Comment	Condition
RRCResumeRequest ::= SEQUENCE {
rrcResumeRequest SEQUENCE {
resumeCause	rna-Update
}
}