8.2.7

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

8.2.7.1

8.2.7.2 RRC Resume

8.2.7.2.1 RRC Resume / NR-DC

8.2.7.2.1.1 Test Purpose (TP)

(1)

with { UE in NR RRC_INACTIVE state and sends RRCResumeRequest message to resume RRC Connection }

ensure that {

when { UE receives a RRCResume message including mrdc-SecondaryCellGroup set to nr-SCG }

then { UE successfully transmits RRCResumeComplete message }

}

8.2.7.2.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.2.2.2.2, 5.3.13.2, 5.3.13.3 and 5.3.13.4. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.2.2.2.2]

A modification period is used, i.e. updated SI message (other than SI message for ETWS, CMAS and positioning assistance data) is broadcasted in the modification period following the one where SI change indication is transmitted. The modification period boundaries are defined by SFN values for which SFN mod m = 0, where m is the number of radio frames comprising the modification period. The modification period is configured by system information. The UE receives indications about SI modifications and/or PWS notifications using Short Message transmitted with P-RNTI over DCI (see clause 6.5). Repetitions of SI change indication may occur within preceding modification period. SI change indication is not applicable for SI messages containing posSIBs.

UEs in RRC_IDLE or in RRC_INACTIVE shall monitor for SI change indication in its own paging occasion every DRX cycle. UEs in RRC_CONNECTED shall monitor for SI change indication in any paging occasion at least once per modification period if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation, on the active BWP to monitor paging, as specified in TS 38.213 [13], clause 13.

[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> if the resumption of the RRC connection is triggered by response to NG-RAN paging:

2> select ‘0’ 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 provided by upper layers;

3> if the access attempt is barred, the procedure ends;

1> else if the resumption of the RRC connection is triggered by upper layers:

2> if the upper layers provide an Access Category and one or more Access Identities:

3> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers;

4> if the access attempt is barred, the procedure ends;

2> if the resumption occurs after release with redirect with mpsPriorityIndication:

3> set the resumeCause to mps-PriorityAccess;

2> else:

3> set the resumeCause in accordance with the information received from upper layers;

1> initiate transmission of the RRCResumeRequest message or RRCResumeRequest1 in accordance with 5.3.13.3.

[38.331, clause 5.3.13.3]

The UE shall set the contents of RRCResumeRequest or RRCResumeRequest1 message as follows:

1> if field useFullResumeID is signalled in SIB1:

2> select RRCResumeRequest1 as the message to use;

2> set the resumeIdentity to the stored fullI-RNTI value;

1> else:

2> select RRCResumeRequest as the message to use;

2> set the resumeIdentity to the stored shortI-RNTI value;

1> restore the RRC configuration, RoHC state, the stored QoS flow to DRB mapping rules and the KgNB and KRRCint keys from the stored UE Inactive AS context except for the following:

– masterCellGroup;

– mrdc-SecondaryCellGroup, if stored; and

– pdcp-Config;

1> set the resumeMAC-I to the 16 least significant bits of the MAC-I calculated:

2> over the ASN.1 encoded as per clause 8 (i.e., a multiple of 8 bits) VarResumeMAC-Input;

2> with the KRRCint key in the UE Inactive AS Context and the previously configured integrity protection algorithm; and

2> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> derive the KgNB key based on the current KgNB key or the NH, using the stored nextHopChainingCount value, as specified in TS 33.501 [11];

1> derive the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key;

1> configure lower layers to apply integrity protection for all radio bearers except SRB0 using the configured algorithm and the KRRCint key and KUPint key derived in this subclause immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE;

NOTE 1: Only DRBs with previously configured UP integrity protection shall resume integrity protection.

1> configure lower layers to apply ciphering for all radio bearers except SRB0 and to apply the configured ciphering algorithm, the KRRCenc key and the KUPenc key derived in this subclause, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE;

1> re-establish PDCP entities for SRB1;

1> resume SRB1;

1> submit the selected message RRCResumeRequest or RRCResumeRequest1 for transmission to lower layers.

NOTE 2: Only DRBs with previously configured UP ciphering shall resume ciphering.

If lower layers indicate an integrity check failure while T319 is running, perform actions specified in 5.3.13.5.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.13.6.

[38.331, clause 5.3.13.4]

The UE shall:

1> if the RRCResume includes the mrdc-SecondaryCellGroup:

2> if the received mrdc-SecondaryCellGroup is set to nr-SCG:

3> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG;

1> enter RRC_CONNECTED;

1> indicate to upper layers that the suspended RRC connection has been resumed;

  1. stop the cell re-selection procedure;

1> consider the current cell to be the PCell;

  1. set the content of the of RRCResumeComplete message as follows:

2> if the RRCResume message includes mrdc-SecondaryCellGroup set to nr-SCG:

3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message;

1> submit the RRCResumeComplete message to lower layers for transmission;

1> the procedure ends.

8.2.7.2.1.3 Test description

8.2.7.2.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell, NR Cell 10 is the PSCell.

– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cell.

UE:

– None.

Preamble:

– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (NR-DC) and Bearers (MCG and SCG) established according to TS 38.508-1 [4] Table 4.5.1-1.

8.2.7.2.1.3.2 Test procedure sequence

Table 8.2.7.2.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCRelease message with suspendConfig.

<–

NR RRC: RRCRelease

2

The SS waits for 5 sec and transmits a Paging message including a matched identity (correct fullI-RNTI).

<–

NR RRC: Paging

3

UE transmits an RRCResumeRequest message by setting resumeIdentity to the stored shortI-RNTI value.

–>

NR RRC: RRCResumeRequest

4

The SS transmits an RRCResume message.

<–

NR RRC: RRCResume

5

The UE transmits an RRCResumeComplete message.

–>

NR RRC: RRCResumeComplete

1

P

8.2.7.2.1.3.3 Specific message contents

Table 8.2.7.2.1.3.3-1: RRCRelease (step 1, Table 8.2.7.2.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-16 with condition NR_RRC_INACTIVE

Table 8.2.7.2.1.3.3-2: Paging (step 2, Table 8.2.7.2.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-9 with condition NR_RRC_RESUME

Table 8.2.7.2.1.3.3-3: RRCResume (step 4, Table 8.2.7.2.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-17

Information Element

Value/remark

Comment

Condition

RRCResume ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier

criticalExtensions CHOICE {

rrcResume SEQUENCE {

nonCriticalExtension SEQUENCE {

radioBearerConfig2

RadioBearerConfig according to Table 8.2.7.2.1.3.3-5

sk-Counter

0

nonCriticalExtension SEQUENCE {

idleModeMeasurementReq-r16

Not Present

restoreMCG-SCells-r16

Not Present

restoreSCG-r16

True

mrdc-SecondaryCellGroup-r16 CHOICE {

nr-SCG-r16

According to TS 38.508-1[4], Table 4.6.1-13 with condition NR-DC_SCG

}

}

needForGapsConfigNR-r16

Not Present

}

}

}

}

Table 8.2.7.2.1.3.3-4: RRCResumeComplete (step 5, Table 8.2.7.2.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-18

Information Element

Value/remark

Comment

Condition

RRCResumeComplete ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier

criticalExtensions CHOICE {

rrcResumeComplete SEQUENCE {

nonCriticalExtension SEQUENCE {

idleMeasAvailable-r16

Not Present

measResultIdleEUTRA-r16

Not Present

measResultIdleNR-r16

Not Present

scg-Response-r16 CHOICE{

nr-SCG-Response

RRCReconfigurationComplete defined as per TS 38.508-1[4] Table 4.6.1-14 with condition NR-DC

eutra-SCG-Response

Not Present

}

ue-MeasurementsAvailable-r16

Not Present

mobilityHistoryAvail-r16

Not Present

mobilityState-r16

Not Present

needForGapsInfoNR-r16

Not Present

nonCriticalExtension

Not Present

}

}

}

}

Table 8.2.7.2.1.3.3-5: RadioBearerConfig (Table 8.2.7.2.1.3.2-3)

Derivation Path: TS 38.508 [4], Table 4.6.3-132 with condition DRBn and SecondaryKeys

Information Element

Value/remark

Comment

Condition

RadioBearerConfig ::= SEQUENCE {

drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod {

1 entry

DRB-ToAddMod SEQUENCE {

cnAssociation

Not present

drb-Identity

DRB-Identity using condition DRBn

n set to the SCG DRB identity

reestablishPDCP

True

recoverPDCP

Not present

pdcp-Config

Not present

daps-Config-r16

Not present

}

}

}