8.1.2 RRC reconfiguration

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.1.2.1 Radio bearer establishment / reconfiguration / release

8.1.2.1.1 RRC reconfiguration / DRB / SRB / Establishment / Modification / Release / Success

8.1.2.1.1.1 Test Purpose (TP)

(1)

with { UE having completed the RRC connection establishment procedure}

ensure that {

when { SS sends in sequence a SecurityModeCommand and an RRCReconfiguration message to establish a DRB and SRB2}

then { UE establishes the initial security configuration in accordance with the received securityConfigSMC included in SecurityModeCommand and successfully establish the data and signalling radio bearers }

}

(2)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCReconfiguration message to reconfigure the current UE configuration of SRB and DRB }

then { UE reconfigures the data and signalling radio bearers and sends an RRCReconfigurationComplete message }

}

(3)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCReconfiguration message including a drb-ToReleaseList }

then { for each drb-Identity release the PDCP entity and RLC entity and logical channel and indicate release of the DRB(s) to upper layers }

}

8.1.2.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.3.4.3, 5.3.5.6.3, 5.3.5.6.4, and 5.3.5.6.5. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.4.3]

The UE shall:

1> derive the K_gNB key, as specified in TS 33.501 [11];

1> derive the K_RRCint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.501 [11];

1> request lower layers to verify the integrity protection of the SecurityModeCommand message, using the algorithm indicated by the integrityProtAlgorithm as included in the SecurityModeCommand message and the K_RRCint key;

1> if the SecurityModeCommand message passes the integrity protection check:

2> derive the K_RRCenc key and the K_UPenc key associated with the cipheringAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.501 [11];

2> derive the K_UPint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.501 [11];

2> configure lower layers to apply SRB integrity protection using the indicated algorithm and the K_RRCint key immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE, including the SecurityModeComplete message;

[TS 38.331, clause 5.3.5.6.3]

The UE shall:

1> for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment or reconfiguration from E-UTRA PDCP to NR PDCP):

2> establish a PDCP entity;

2> if AS security has been activated:

3> if target RAT of handover is E-UTRA/5GC, or;

3> if the UE is only connected to E-UTRA/5GC:

4> configure the PDCP entity with the security algorithms and keys (K_RRCenc and K_RRCint) configured/derived as specified in TS 36.331 [10];

3> else:

4> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (K_RRCenc and K_RRCint) associated with the master key (K_eNB/ K_gNB) or secondary key (S-K_gNB) as indicated in keyToUse, if applicable;

2> if the current UE configuration as configured by E-UTRA in TS 36.331 [10] includes an SRB identified with the same srb-Identity value:

3> associate the E-UTRA RLC entity and DCCH of this SRB with the NR PDCP entity;

3> release the E-UTRA PDCP entity of this SRB;

2> if the pdcp-Config is included:

3> configure the PDCP entity in accordance with the received pdcp-Config;

2> else:

3> configure the PDCP entity in accordance with the default configuration defined in 9.2.1 for the corresponding SRB;

1> for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration:

2> if the reestablishPDCP is set:

3> if target RAT of handover is E-UTRA/5GC, or;

3> if the UE is only connected to E-UTRA/5GC:

4> configure the PDCP entity to apply the integrity protection algorithm and K_RRCint key configured/derived as specified in TS 36.331 [10], i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

4> configure the PDCP entity to apply the ciphering algorithm and K_RRCenc key configured/derived as specified in TS 36.331 [10], i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

3> else:

4> configure the PDCP entity to apply the integrity protection algorithm and K_RRCint key associated with the master key (K_eNB/K_gNB) or secondary key (S-K_gNB), as indicated in keyToUse , i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

4> configure the PDCP entity to apply the ciphering algorithm and K_RRCenc key associated with the master key (K_eNB/K_gNB) or secondary key (S-K_gNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

4> re-establish the PDCP entity of this SRB as specified in TS 38.323 [5];

2> else, if the discardOnPDCP is set:

3> trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5];

2> if the pdcp-Config is included:

3> reconfigure the PDCP entity in accordance with the received pdcp-Config.

[TS 38.331, clause 5.3.5.6.4]

The UE shall:

1> for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration; or

1> for each drb-Identity value that is to be released as the result of full configuration according to 5.3.5.11:

2> release the PDCP entity and the drb-Identity;

2> if SDAP entity associated with this DRB is configured:

3> indicate the release of the DRB to SDAP entity associated with this DRB (TS 37.324 [24], clause 5.3.3);

2> if the UE is operating in EN-DC:

3> if a new bearer is not added either with NR or E-UTRA with same eps-BearerIdentity:

4> indicate the release of the DRB and the eps-BearerIdentity of the released DRB to upper layers.

NOTE 1: The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity value that is not part of the current UE configuration.

NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig.

[TS 38.331, clause 5.3.5.6.5]

The UE shall:

1> for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment including the case when full configuration option is used):

2> establish a PDCP entity and configure it in accordance with the received pdcp-Config;

2> if the PDCP entity of this DRB is not configured with cipheringDisabled:

3> if target RAT of handover is E-UTRA/5GC, or;

3> if the UE is only connected to E-UTRA/5GC:

4> configure the PDCP entity with the ciphering algorithm and K_UPenc key configured/derived as specified in TS 36.331 [10];

3> else:

4> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the K_UPenc key associated with the master key (K_eNB/K_gNB) or the secondary key (S-K_gNB) as indicated in keyToUse;

2> if the PDCP entity of this DRB is configured with integrityProtection:

3> configure the PDCP entity with the integrity algorithms according to securityConfig and apply the K_UPint key associated with the master (K_eNB/K_gNB) or the secondary key (S-K_gNB) as indicated in keyToUse;

2> if an sdap-Config is included:

3> if an SDAP entity with the received pdu-Session does not exist:

4> establish an SDAP entity as specified in TS 37.324 [24] clause 5.1.1;

4> If an SDAP entity with the received pdu-Session did not exist prior to receiving this reconfiguration:

5> indicate the establishment of the user plane resources for the pdu-Session to upper layers;

3> configure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324 [24] and associate the DRB with the SDAP entity;

2> if the UE is operating in EN-DC:

3> if the DRB was configured with the same eps-BearerIdentity either by NR or E-UTRA prior to receiving this reconfiguration:

4> associate the established DRB with the corresponding eps-BearerIdentity;

3> else:

4> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

8.1.2.1.1.3 Test description

8.1.2.1.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1

UE:

– None

Preamble:

– If pc_IP_Ping is set to TRUE then the UE is in 5GS state 1N-A, PDU SESSION ACTIVE according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1

– Else, the UE is in 5GS state 1N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.

8.1.2.1.1.3.2 Test procedure sequence

Table 8.1.2.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordList.	<–	NR RRC: Paging	–	–
2	UE transmits an RRCSetupRequest message.	–>	NR RRC: RRCSetupRequest	–	–
3	SS transmits an RRCSetup message	<–	NR RRC: RRCSetup	–	–
4	The UE transmits an RRCSetupComplete to confirm the successful completion of the connection establishment.	–>	NR RRC: RRCSetupComplete	–	–
5	SS transmits a SecurityModeCommand message to activate AS security.	<–	NR RRC: SecurityModeCommand	–	–
6	Using the same slot as the SecurityModeCommand message in step 5, the SS transmits an RRCReconfiguration message to establish a data radio bearer, DRB1 and signalling radio bearer, SRB2.	<–	NR RRC: RRCReconfiguration	–	–
7	Check: Does the UE transmit a SecurityModeComplete message?	–>	NR RRC: SecurityModeComplete	1	P
8	Check: Does the UE transmit an RRCReconfigurationComplete message to confirm the establishment of data radio bearer, DRB1 and signalling radio bearer, SRB2?	–>	NR RRC: RRCReconfigurationComplete	1	P
9	Void			–	–
10	Void			–	–
11	The SS transmits an RRCReconfiguration message to modify SRB and DRB configuration.	<–	NR RRC: RRCReconfiguration	–	–
12	Check: Does the UE transmit an RRCReconfigurationComplete message?	–>	NR RRC: RRCReconfigurationComplete	2	P
12A	Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB#1 established in Step 11?	–	–	2	–
12A1	The SS transmits an OPEN UE TEST LOOP Message.	<–	OPEN UE TEST LOOP	–	–
12A2	The UE transmits an OPEN UE TEST LOOP COMPLETE Message.	–>	OPEN UE TEST LOOP COMPLETE	–	–
12A3	The SS transmits DEACTIVATE TEST MODE message.	<–	DEACTIVATE TEST MODE	–	–
12A4	The UE transmits DEACTIVATE TEST MODE COMPLETE message.	–>	DEACTIVATE TEST MODE COMPLETE	–	–
12B	Cause the UE to request establishment of PDU session.(Note 1)	–	–	–	–
12C	The PDU session establishment procedure as specified in TS 38.508-1 [4] subclause 4.5A.2 takes place.	–	–	–	–
13	The SS transmits an RRCReconfiguration message with a drb-ToReleaseList and PDU SESSION RELEASE COMMAND to release the PDU session to which the released DRB is associated	<–	NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMMAND	–	–
14	Check: Does the UE transmit an RRCReconfigurationComplete message?	–>	NR RRC: RRCReconfigurationComplete	3	P
16	The UE transmits an ULInformationTransfer message and a UL NAS TRASPORT containing PDU SESSION RELEASE COMPLETE.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMPLETE	–	–
NOTE 1: The request to establish a PDU session may be performed by MMI or AT Command.

8.1.2.1.1.3.3 Specific message contents

Table 8.1.2.1.1.3.3-1: RRCReconfiguration (Step 6, Table 8.1.2.1.1.3.2-1)

Derivation Path: TS 38.508-1, table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	RadioBearerConfig with conditions SRB2 and DRB1
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig	OCTET STRING (CONTAINING CellGroupConfig)
}
}
}

Table 8.1.2.1.1.3.3-1A: CellGroupConfig (Table 8.1.2.1.1.3.3-1)

Derivation Path: TS 38.508-1, table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig {	2 entries
RLC-Bearer-Config[1] SEQUENCE {		entry 1
logicalChannelIdentity	LogicalChannelIdentity
servedRadioBearer CHOICE {
drb-Identity	DRB-Identity with condition DRB1
}
reestablishRLC	Not present
RLC-Config	RLC-Config with condition AM according to 38.508-1 [4], table 4.6.3-149
mac-LogicalChannelConfig	LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66
}
RLC-Bearer-Config[2] SEQUENCE {		entry 2
logicalChannelIdentity	LogicalChannelIdentity
servedRadioBearer CHOICE {
srb-Identity	SRB-Identity with condition SRB2
}
reestablishRLC	Not present
RLC-Config	Not present
mac-LogicalChannelConfig	LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66
}
}
mac-CellGroupConfig	Not present
physicalCellGroupConfig	Not present
spCellConfig SEQUENCE	Not present
}

Table 8.1.2.1.1.3.3-2: Void

Table 8.1.2.1.1.3.3-2A: Void

Table 8.1.2.1.1.3.3-3: RRCReconfiguration (Step 11, Table 8.1.2.1.1.3.2-1)

Derivation Path: TS 38.508-1, table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig	OCTET STRING (CONTAINING CellGroupConfig)
}
}
}
}

Table 8.1.2.1.1.3.3-4: CellGroupConfig (Table 8.1.2.1.1.3.3-3)

Derivation Path: TS 38.508-1, table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig {	2 entries
RLC-Bearer-Config[1] SEQUENCE {		entry 1
logicalChannelIdentity	LogicalChannelIdentity
servedRadioBearer CHOICE {
srb-Identity	SRB-Identity with condition SRB2
}
reestablishRLC	true
RLC-Config	RLC-Config with condition AM according to 38.508-1 [4], table 4.6.3-149
mac-LogicalChannelConfig	LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66
}
RLC-Bearer-Config[2] SEQUENCE {		entry 2
logicalChannelIdentity	LogicalChannelIdentity
servedRadioBearer CHOICE {
drb-Identity	DRB-Identity with condition DRB1
}
reestablishRLC	true
RLC-Config	Not present
mac-LogicalChannelConfig	LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66
}
}
mac-CellGroupConfig	Not present
physicalCellGroupConfig	Not present
spCellConfig SEQUENCE	Not present
}

Table 8.1.2.1.1.3.3-5: RRCReconfiguration (Step 13, Table 8.1.2.1.1.3.2-1)

Derivation Path: TS 38.508-1, table 4.6.1-3
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	RadioBearerConfig
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig	OCTET STRING (CONTAINING CellGroupConfig)
}
}
}

Table 8.1.2.1.1.3.3-6: RadioBearerConfig (Table 8.1.2.1.1.3.3-5)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToReleaseList	1	DRB1
}

Table 8.1.2.1.1.3.3-7: CellGroupConfig (Table 8.1.2.1.1.3.3-5)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	1
rlc-BearerToAddModList	Not Present
rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity {	1 entry
logicalChannelIdentity[1]	LogicalChannelIdentity	entry 1
}
mac-CellGroupConfig	Not Present
tag-Config	Not Present
phr-Config	Not Present
physicalCellGroupConfig	Not Present
rlf-TimersAndConstants	Not Present
}

8.1.2.1.2 RRC reconfiguration / RRC bearer establishment / uplinkTxDirectCurrentList

8.1.2.1.2.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives a RRCReconfiguration message containing reportUplinkTxDirectCurrent }

then { UE will include the uplinkTxDirectCurrentList in RRCReconfigurationComplete message. }

}

8.1.2.1.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.3. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.5.3]

The UE shall perform the following actions upon reception of the RRCReconfiguration:

…

1> set the content of RRCReconfigurationComplete message as follows:

2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent, or;

2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent:

3> include the uplinkTxDirectCurrentList;

8.1.2.1.2.3 Test description

8.1.2.1.2.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 is used in NR cell.

UE:

– None.

Preamble:

– The UE is in state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.

8.1.2.1.2.3.2 Test procedure sequence

Table 8.1.2.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a RRCReconfiguration message containing uplinkBWP-ToAddModList IE to add BWP#1 and including reportUplinkTxDirectCurrent IE.	<–	NR RRC: RRCReconfiguration	–	–
2	Check: Does the UE transmit the RRCReconfigurationComplete message including the uplinkTxDirectCurrentList?	–>	NR RRC: RRCReconfigurationComplete	1	P

8.1.2.1.2.3.3 Specific message contents

Table 8.1.2.1.2.3.3-1: RRCReconfiguration (step 1, Table 8.1.2.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig
}
}
}
}

Table 8.1.2.1.2.3.3-2: CellGroupConfig (Table 8.1.2.1.2.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
spCellConfig SEQUENCE {
spCellConfigDedicated	ServingCellConfig
}
reportUplinkTxDirectCurrent-v1530	true
}

Table 8.1.2.1.2.3.3-3: ServingCellConfig (Table 8.1.2.1.2.3.3-2)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-167
Information Element	Value/remark	Comment	Condition
ServingCellConfigCommon ::= SEQUENCE {
uplinkConfig SEQUENCE {
uplinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Uplink {	1 entry
BWP-Uplink[1]	BWP-Uplink	entry 1 TS 38.508-1 [4], Table 4.6.3-13 to add BWP#1
}
}
}

Table 8.1.2.1.2.3.3-4: RRCReconfigurationComplete (step 2, Table 8.1.2.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-14
Information Element	Value/remark	Comment	Condition
RRCReconfigurationComplete ::= SEQUENCE {
rrc-TransactionIdentifier	Not checked
criticalExtensions CHOICE {
rrcReconfigurationComplete SEQUENCE {
lateNonCriticalExtension	Not checked
nonCriticalExtension SEQUENCE {
UplinkTxDirectCurrentList SEQUENCE (SIZE (1..maxNrofServingCells)) OF UplinkTxDirectCurrentCell {	1 entry
UplinkTxDirectCurrentCell[1] SEQUENCE {		entry 1
servCellIndex	0
UplinkTxDirectCurrentBWP SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP {	2 entries
UplinkTxDirectCurrentBWP[1] SEQUENCE {		entry 1
bwp-Id	0
shift7dot5kHz	Not checked
txDirectCurrentLocation	Any value between 0 and 3299
}
UplinkTxDirectCurrentBWP[2] SEQUENCE {		entry 2
bwp-Id	1
shift7dot5kHz	Not checked
txDirectCurrentLocation	Any value between 0 and 3299
}
}
}
}
nonCriticalExtension	Not checked
}
}
}
}

8.1.2.1.3 Void

8.1.2.1.4 RRC reconfiguration / Dedicated RLF timer

8.1.2.1.4.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state configured with timers according rlf-TimersAndConstants }

ensure that {

when { UE detecting radio link failure on expiring of timer T310 }

then { UE sends an RRCReestablishmentRequest message according rlf-TimersAndConstants }

}

(2)

with { UE in NR RRC_CONNECTED state with rlf-TimersAndConstants released}

ensure that {

when { UE detecting radio link failure on expiring of timer T310 }

then { UE sends an RRCReestablishmentRequest message according ue-TimersAndConstants }

}

8.1.2.1.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.3, 5.3.5.5, 5.3.5.5.6 and 5.3.5.5.7.

[TS 38.331 clause 5.3.5.3]

The UE shall perform the following actions upon reception of the RRCReconfiguration:

…

1> if the RRCReconfiguration includes the masterCellGroup:

2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;

…

1> else:

2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;

[TS 38.331 clause 5.3.5.5]

The UE performs the following actions based on a received CellGroupConfig IE:

…

1> if the CellGroupConfig contains the spCellConfig:

2> configure the SpCell as specified in 5.3.5.5.7;

[TS 38.331 clause 5.3.5.5.7]

The UE shall:

1> if the SpCellConfig contains the rlf-TimersAndConstants:

2> configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6;

[TS 38.331 clause 5.3.5.5.6]

The UE shall:

1> if the received rlf-TimersAndConstants is set to release:

2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;

1> else:

2> (re-)configure the value of timers and constants in accordance with received rlf-TimersAndConstants;

8.1.2.1.4.3 Test description

8.1.2.1.4.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 and NR Cell 2.

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

None.

Preamble:

– The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.

8.1.2.1.4.3.2 Test procedure sequence

Table 8.1.2.1.4.3.2-1: Time instances of cell power level and parameter changes for FR1

Parameter

Unit

Cell 1

Cell 2

SS/PBCH

SSS EPRE

dBm/SCS

“Off”

-88

SS/PBCH

SSS EPRE

dBm/SCS

“-88”

“Off”

Table 8.1.2.1.4.3.2-2: Time instances of cell power level and parameter changes for FR2

Parameter

Unit

Cell 1

Cell 2

SS/PBCH

SSS EPRE

dBm/SCS

“Off”

-82

SS/PBCH

SSS EPRE

dBm/SCS

“-82”

“Off”

Table 8.1.2.1.4.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes NR Cell 1 and NR Cell 2 parameters according to the row "T1" in table 8.1.2.1.4.3.2-1 or 8.1.2.1.4.3.2-2 in order that the radio link quality of NR Cell 1 is degraded, and NR Cell 2 is suitable for camping.	–	–	–	–
2	Check: Does the UE send RRCReestablishmentRequest message on NR Cell 2 after T310 expired (ms6000)?	–>	NR RRC: RRCReestablishmentRequest	1	P
3	The SS transmits an RRCReestablishment message.	<–	NR RRC: RRCReestablishment	–	–
4	The UE transmits an RRCReestablishmentComplete message.	–>	NR RRC: RRCReestablishmentComplete	–	–
5	The SS transmits an RRCReconfiguration message containing RLF-TimersAndConstants set to release.	<–	NR RRC: RRCReconfiguration	–	–
6	The UE transmits an RRCReconfigurationComplete message.	–>	NR RRC: RRCReconfigurationtComplete	–	–
7	The SS changes NR Cell 1 and NR Cell 2 parameters according to the row "T2" in table 8.1.2.1.4.3.2-1 or 8.1.2.1.4.3.2-2 in order that the radio link quality of NR Cell 2 is degraded, and NR Cell 1 is suitable for camping.	–	–	–	–
8	Check: Does the UE send RRCReestablishmentRequest message on NR Cell 1 after T310 expired (ms1000)?	–>	NR RRC: RRCReestablishmentRequest	2	P
9	The SS transmits RRCReestablishment message.	<–	NR RRC: RRCReestablishment	–	–
10	The UE transmits an RRCReestablishmentComplete message.	–>	NR RRC: RRCReestablishmentComplete	–	–
11	The SS transmits an RRCReconfiguration message to establish SRB2 and DRB.	<–	NR RRC: RRCReconfiguration	–	–
12	The UE transmits an RRCReconfigurationtComplete message.	–>	NR RRC: RRCReconfigurationtComplete	–	–

8.1.2.1.4.3.3 Specific message contents

Table 8.1.2.1.4.3.3-1: RLF-TimersAndConstants (preamble)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-150
Information Element	Value/remark	Comment	Condition
RLF-TimersAndConstants ::= SEQUENCE {
t310	ms6000
n310	n20
}

Table 8.1.2.1.4.3.3-2: RRCReconfiguration (step 5, Table 8.1.2.1.4.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition REEST
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig
}
}
}
}

Table 8.1.2.1.4.3.3-3: CellGroupConfig (Table 8.1.2.1.4.3.3-2)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-19 with condition REEST
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
spCellConfig SEQUENCE {
rlf-TimersAndConstants CHOICE {
release	NULL
}
}
}

Table 8.1.2.1.4.3.3-4: RRCReconfiguration (step 11 Table 8.1.2.1.4.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition REEST

8.1.2.1.5 NR CA / RRC reconfiguration / SCell addition / modification / release / Success

8.1.2.1.5.1 NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Intra-band Contiguous CA

8.1.2.1.5.1.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCReconfiguration message containing sCellToAddModList for SCell addition }

then { UE adds the new SCell and sends an RRCReconfigurationComplete message }

}

(2)

with { UE in NR RRC_CONNECTED state with SCell configured}

ensure that {

when { UE receives an RRCReconfiguration message containing sCellToAddModList for SCell modification }

then { UE modifies the SCell configuration and sends an RRCReconfigurationComplete message }

}

(3)

with { UE in NR RRC_CONNECTED state with SCell configured}

ensure that {

when { UE receives an RRCReconfiguration message containing sCellToReleaseList }

then { UE sends an RRCReconfigurationComplete message }

}

8.1.2.1.5.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.3, 5.3.5.5.1 and 5.3.5.5.9.

[TS 38.331 clause 5.3.5.3]

The UE shall perform the following actions upon reception of the RRCReconfiguration:

…

1> if the RRCReconfiguration includes the masterCellGroup:

2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;

…

1> else:

2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;

[TS 38.331 clause 5.3.5.5.1]

The UE performs the following actions based on a received CellGroupConfig IE:

…

1> if the CellGroupConfig contains the sCellToReleaseList:

2> perform SCell release as specified in 5.3.5.5.8;

…

1> if the CellGroupConfig contains the sCellToAddModList:

2> perform SCell addition/modification as specified in 5.3.5.5.9.

[TS 38.331 clause 5.3.5.5.9]

The UE shall:

1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;

2> configure lower layers to consider the SCell to be in deactivated state;

…

1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the sCellConfigDedicated.

8.1.2.1.5.1.3 Test description

8.1.2.1.5.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell, NR Cell 3 is the SCell.

None.

Preamble:

– The UE is in state 3N-A, and with UE test loop mode B active if pc_IP_Ping is set to FALSE, as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.

8.1.2.1.5.1.3.2 Test procedure sequence

Table 8.1.2.1.5.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCReconfigurationmessage containing an sCellToAddModList with SCell NR Cell 3 addition,	<–	NR RRC: RRCReconfiguration	–	–
2	Check: Does the UE transmits an RRCReconfigurationComplete message?	–>	NR RRC: RRCReconfigurationtComplete	1	P
3	Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB1 and Cell 3?	–	–	1	P
4	The SS transmits an RRCReconfigurationmessage containing an sCellToAddModList with SCell NR Cell 3 modification.	<–	NR RRC: RRCReconfiguration	–	–
5	Check: Does the UE transmit an RRCReconfigurationComplete message?	–>	NR RRC: RRCReconfigurationtComplete	2	P
6	Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB1 and Cell 3?	–	–	2	P
7	The SS transmits an RRCReconfigurationmessage containing an sCellToReleaseList with SCell NR Cell 3.	<–	NR RRC: RRCReconfiguration	–	–
8	Check: Does the UE transmit an RRCReconfigurationComplete message?	–>	NR RRC: RRCReconfigurationtComplete	3	P

8.1.2.5.1.1.3.3 Specific message contents

Table 8.1.2.5.1.1.3.3-1: RRCReconfiguration (step 1, Table 8.1.2.1.5.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add

Table 8.1.2.5.1.1.3.3-2: RRCReconfiguration (step 4, Table 8.1.2.1.5.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig
}
}
}
}

Table 8.1.2.5.1.1.3.3-3: CellGroupConfig (Table 8.1.2.5.1.1.3.3-2)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-19 with condition SCell_add
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig {	1 entry
SCellConfig[1] SEQUENCE {		entry 1
sCellConfigCommon	Not present
sCellConfigDedicated	ServingCellConfig
}
}
}

Table 8.1.2.5.1.1.3.3-4: ServingCellConfig (Table 8.1.2.5.1.1.3.3-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-167
Information Element	Value/remark	Comment	Condition
ServingCellConfig ::= SEQUENCE {
firstActiveDownlinkBWP-Id	Not present
uplinkConfig SEQUENCE {
firstActiveUplinkBWP-Id	Not present
}
pdsch-ServingCellConfig CHOICE {
setup	PDSCH-ServingCellConfig
}
}

Table 8.1.2.5.1.1.3.3-5: PDSCH-ServingCellConfig (Table 8.1.2.5.1.1.3.3-4)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-102
Information Element	Value/remark	Comment	Condition
PDSCH-ServingCellConfig ::= SEQUENCE {
nrofHARQ-ProcessesForPDSCH	n16
}

Table 8.1.2.5.1.1.3.3-6: RRCReconfiguration (step 7, Table 8.1.2.1.5.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
nonCriticalExtension SEQUENCE{
masterCellGroup	CellGroupConfig
}
}
}
}

Table 8.1.2.5.1.1.3.3-7: CellGroupConfig (Table 8.1.2.5.1.1.3.3-6)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-19 with condition SCell_add
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
sCellToAddModList	Not present
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex {	1 entry
SCellIndex[1]	1	entry 1
}
}

8.1.2.1.5.2 NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Inter-band CA

8.1.2.1.5.2.1 Test Purpose (TP)

Same as TC 8.1.2.1.5.1 but applied to Inter-band CA.

8.1.2.1.5.2.2 Conformance requirements

Same as TC 8.1.2.1.5.1 but applied to Inter-band CA.

8.1.2.1.5.2.3 Test description

8.1.2.1.5.2.3.1 Pre-test conditions

Same as TC 8.1.2.1.5.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: NR Cell 10 replaces NR Cell 3

8.1.2.1.5.2.3.2 Test procedure sequence

Same as TC 8.1.2.1.5.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: NR Cell 10 replaces NR Cell 3

8.1.2.1.5.3 NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Intra-band non-contiguous CA

8.1.2.1.5.3.1 Test Purpose (TP)

Same as TC 8.1.2.1.5.1 but applied to Intra-band non-contiguous CA.

8.1.2.1.5.3.2 Conformance requirements

Same as TC 8.1.2.1.5.1 but applied to Intra-band non-contiguous CA.

8.1.2.1.5.3.3 Test description

8.1.2.1.5.3.3.1 Pre-test conditions

Same as TC 8.1.2.1.5.1 with the following differences:

– CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA

8.1.2.1.5.3.3.2 Test procedure sequence

Same as TC 8.1.2.1.5.1 with the following differences:

– CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA