8.2.2 Radio Bearer Addition, Modification and Release

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

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

8.2.2.1 Radio Bearer Addition, Modification and Release / SRB

8.2.2.1.1 SRB3 Establishment, Reconfiguration and Release / NR addition, modification and release / EN-DC

8.2.2.1.1.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to add SRB3 }

then { UE establishes SRB3 and sends an RRCConnectionReconfigurationComplete message on SRB1 }

}

(2)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG and SRB3 configured }

ensure that {

when { UE receives an RRCReconfiguration message on SRB3 including secondaryCellGroup to reconfigure NR MAC }

then { UE sends RRCReconfigurationComplete message on SRB3 }

}

(3)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG and SRB3 configured }

ensure that {

when { UE receives an RRCReconfiguration message on SRB3 including radioBearerConfig to reconfigure NR PDCP }

then { UE sends RRCReconfigurationComplete message on SRB3 }

}

(4)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to release SRB3 }

then {UE releases SRB3 and sends an RRCConnectionReconfigurationComplete message on SRB1 }

}

8.2.2.1.1.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 36.331, clause 5.3.5.3, TS 38.331, clauses 5.3.5.1, 5.3.5.3, 5.3.5.5.1, 5.3.5.5.3, 5.3.5.5.4, 5.3.5.5.8, 5.3.5.5.9, 5.3.5.6.1, 5.3.5.6.2 and 5.3.5.6.3. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, 5.3.5.3]

1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or

1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd:

2> perform ENDC release as specified in TS38.331 [82], clause 5.3.5.10;

…

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

…

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 38.331, 5.3.5.1]

In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, to (re-)configure MAC, RLC, physical layer and RLF timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S-K_gNB or SRB3, and to reconfigure SDAP for DRBs associated with S-K_gNB in (NG)EN-DC and NR-DC, provided that the (re-)configuration does not require any MN involvement. In EN-DC, only measConfig, radioBearerConfig and/or secondaryCellGroup are included in RRCReconfiguration received via SRB3.

[TS 38.331, 5.3.5.3]

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

1> if the RRCReconfiguration includes the secondaryCellGroup:

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

…

1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):

2> if RRCReconfiguration was received via SRB1:

3> construct RRCReconfigurationComplete message and submit it via the EUTRA MCG embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10];

…

2> else (RRCReconfiguration was received via SRB3):

3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;

NOTE: In the case of SRB1, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case of SRB3, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.

[TS 38.331, 5.3.5.5.1]

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

…

1> if the CellGroupConfig contains the rlc-BearerToReleaseList:

2> perform RLC bearer release as specified in 5.3.5.5.3;

1> if the CellGroupConfig contains the rlc-BearerToAddModList:

2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4;

1> if the CellGroupConfig contains the mac-CellGroupConfig:

2> configure the MAC entity of this cell group as specified in 5.3.5.5.5;

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, 5.3.5.5.3]

1> for each logicalChannelIdentity value included in the rlc-BearerToReleaseList that is part of the current UE configuration (LCH release); or

1> for each logicalChannelIdentity value that is to be released as the result of an SCG release according to 5.3.5.4:

2> release the RLC entity or entities as specified in TS 38.322 [4, clause 5.1.3];

2> release the corresponding logical channel.

[TS 38.331, 5.3.5.5.4]

For each RLC-Bearer-Config received in the rlc-BearerToAddModList IE the UE shall:

1> if the UE’s current configuration contains a RLC bearer with the received logicalChannelIdentity:

…

2> reconfigure the RLC entity or entities in accordance with the received rlc-Config;

[TS 38.331, 5.3.5.5.8]

The UE shall:

1> if the release is triggered by reception of the sCellToReleaseList:

2> for each sCellIndex value included in the sCellToReleaseList:

3> if the current UE configuration includes an SCell with value sCellIndex:

4> release the SCell.

[TS 38.331, 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.

[TS 38.331, 5.3.5.6.1]

The UE shall perform the following actions based on a received RadioBearerConfig IE:

1> if the RadioBearerConfig includes the srb3-ToRelease and set to true:

2> perform the SRB release as specified in 5.3.5.6.2;

1> if the RadioBearerConfig includes the srb-ToAddModList:

2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3;

[TS 38.331, 5.3.5.6.2]

The UE shall:

1> release the PDCP entity of the SRB3.

[TS 38.331, 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 and configure it 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 pdcp-Config is included:

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

8.2.2.1.1.3 Test description

8.2.2.1.1.3.1 Pre-test conditions

System Simulator:

– E-UTRA Cell 1 is the PCell and NR Cell 1 is the PSCell

– System Information combination as defined in TS 38.508-1 [4] clause 4.4.3.1.1 is used in E-UTRA Cell 1 and NR Cell 1.

UE:

– None.

Preamble:

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

8.2.2.1.1.3.2 Test procedure sequence

Table 8.2.2.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message containing NR RRCReconfiguration message to add SRB3 sent on SRB1/E-UTRA Cell 1.	<–	RRCConnectionReconfiguration (RRCReconfiguration)	–	–
2	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message containing NR RRCReconfigurationComplete message on SRB1/E-UTRA Cell 1?	–>	RRCConnectionReconfigurationComplete (RRCReconfigurationComplete)	1	P
3	The SS transmits an RRCReconfiguration message to reconfigure NR MAC sent on SRB3/NR Cell 1.	<–	RRCReconfiguration	–	–
4	Check: Does the UE transmit an RRCReconfigurationComplete message on SRB3/NR Cell 1?	–>	RRCReconfigurationComplete	2	P
5	The SS transmits an RRCReconfiguration message to reconfigure NR PDCP sent on SRB3/NR Cell 1.	<–	RRCReconfiguration	–	–
6	Check: Does the UE transmit an RRCReconfigurationComplete message on SRB3/NR Cell 1?	–>	RRCReconfigurationComplete	3	P
7	The SS transmits an RRCConnectionReconfiguration message to release SRB3 sent on SRB1/E-UTRA Cell 1.	<–	RRCConnectionReconfiguration	–	–
8	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on SRB1/E-UTRA Cell 1?	–>	RRCConnectionReconfigurationComplete	4	P
9	The SS releases the RRC connection.	–	–	–	–

8.2.2.1.1.3.3 Specific message contents

Table 8.2.2.1.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.1.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_EmbedNR_RRCRecon and EN-DC_Embed_RBConfig
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15	OCTET STRING including the RRCReconfiguration message according to table 8.2.2.1.1.3.3-1A.
nr-RadioBearerConfig1-r15	RadioBearerConfig according to 38.508-1 [4] Table 4.6.3-132 with condition SRB3
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.1.1.3.3-1A: RRCReconfiguration (Table 8.2.2.1.1.3.3-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 {
secondaryCellGroup	OCTET STRING containing CellGroupConfig according to Table 8.2.2.1.1.3.3-1B.
}
}
}

Table 8.2.2.1.1.3.3-1B: CellGroupConfig (Table 8.2.2.1.1.3.3-1A)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	1
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig {	1 entry
RLC-Bearer-Config[1] SEQUENCE {		entry 1
logicalChannelIdentity	3
servedRadioBearer CHOICE {
srb-Identity	3
}
}
mac-CellGroupConfig	Not Present
physicalCellGroupConfig	Not Present
spCellConfig	Not Present
}

Table 8.2.2.1.1.3.3-2: RRCReconfiguration (step 3, Table 8.2.2.1.1.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 {
secondaryCellGroup	OCTET STRING containing CellGroupConfig according to Table 8.2.2.1.1.3.3-3.
}
}
}

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

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	Not present
mac-CellGroupConfig	MAC-CellGroupConfig according to table 8.2.2.1.1.3.3-3a
physicalCellGroupConfig	Not present
spCellConfig	Not present
}

Table 8.2.2.1.1.3.3-3a: MAC-CellGroupConfig (Table 8.2.2.1.1.3.3-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-68
Information Element	Value/remark	Comment	Condition
MAC-CellGroupConfig ::= SEQUENCE {
drx-config	Not present.
schedulingRequestConfig	Not present.
bsr-Config SEQUENCE {
periodicBSR-Timer	sf5
retxBSR-Timer	sf40
}
tag-Config	Not present.
phr-Config	Not present.
skipUplinkTxDynamic	Not present.
}

Table 8.2.2.1.1.3.3-4: RRCReconfiguration (step 5, Table 8.2.2.1.1.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 {
radioBearerConfig	RadioBearerConfig	Table 8.2.2.1.1.3.3-4B
}
}
}

Table 8.2.2.1.1.3.3-4A: PDCP-Config (Table 8.2.2.1.1.3.3-4B)

Derivation Path: TS 38.508-1 [4], Table: 4.6.3-99 with condition SRB
Information Element	Value/remark	Comment	Condition
PDCP-Config ::= SEQUENCE {
t-Reordering	ms20
}

Table 8.2.2.1.1.3.3-4B: RadioBearerConfig (Table 8.2.2.1.1.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132 with condition SRB3
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod {	1 entry
SRB-ToAddMod[1] SEQUENCE {
pdcp-Config SEQUENCE {	PDCP-Config
}
}
securityConfig	Not present
}

Table 8.2.2.1.1.3.3-5: Void

Table 8.2.2.1.1.3.3-6: RRCConnectionReconfiguration (step 7, Table 8.2.2.1.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition EN-DC_EmbedNR_RRCRecon and EN-DC_Embed_RBConfig
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15 CHOICE {}	OCTET STRING including the RRCReconfiguration message according to table 8.2.2.1.1.3.3-8.
nr-RadioBearerConfig1-r15	RadioBearerConfig according to Table 8.2.2.1.1.3.3-7
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.1.1.3.3-7: RadioBearerConfig (Table 8.2.2.1.1.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb3-ToRelease	true
securityConfig	Not present
}

Table 8.2.2.1.1.3.3-8: RRCReconfiguration (Table 8.2.2.1.1.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	OCTET STRING containing CellGroupConfig according to Table 8.2.2.1.1.3.3-9.
}
}
}

Table 8.2.2.1.1.3.3-9: CellGroupConfig (Table 8.2.2.1.1.3.3-8)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition EN-DC
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]	3	entry 1
}
mac-CellGroupConfig SEQUENCE {	Not Present
tag-Config	Not Present
phr-Config	Not Present
}
physicalCellGroupConfig	Not Present
rlf-TimersAndConstants	Not Present
}

8.2.2.1.2 SRB3 Establishment, Reconfiguration and Release / NR addition, modification and release / NR-DC

8.2.2.1.2.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state with NR-DC }

ensure that {

when { UE receives an RRCReconfiguration message to establish SRB3 }

then { UE establishes SRB3 and sends an RRCReconfigurationComplete message on SRB1 }

}

(2)

with { UE in NR RRC_CONNECTED state with NR-DC and SRB3 configured }

ensure that {

when { UE receives an RRCReconfiguration message on SRB3 to reconfigure NR MAC of the SCG }

then { UE reconfigures NR MAC and sends RRCReconfigurationComplete message on SRB3 }

}

(3)

with { UE in NR RRC_CONNECTED state with NR-DC and SRB3 configured }

ensure that {

when { UE receives an RRCReconfiguration message on SRB3 to reestablish NR PDCP of the SCG }

then { UE reestablishes NR PDCP and sends RRCReconfigurationComplete message on SRB3 }

}

(4)

with { UE in NR RRC_CONNECTED state with NR-DC and SRB3 configured }

ensure that {

when { UE receives an RRCReconfiguration message to release SRB3 }

then { UE releases SRB3 and sends an RRCReconfigurationComplete message on SRB1 }

}

8.2.2.1.2.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 38.331, clauses 5.3.5.3, 5.3.5.5.1, 5.3.5.5.3, 5.3.5.5.4, 5.3.5.5.8, 5.3.5.5.9, 5.3.5.6.1, 5.3.5.6.2 and 5.3.5.6.3. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, 5.3.5.3]

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

…

1> if the RRCReconfiguration includes the secondaryCellGroup:

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

1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:

2> if the mrdc-SecondaryCellGroupConfig is set to setup:

3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:

4> perform MR-DC release as specified in clause 5.3.5.10;

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

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

…

1> if the RRCReconfiguration message includes the radioBearerConfig:

2> perform the radio bearer configuration according to 5.3.5.6;

…

1> set the content of the RRCReconfigurationComplete message as follows:

…

2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:

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

…

1> else if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration via SRB1):

2> if reconfigurationWithSync was included in spCellConfig in nr-SCG:

3> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];

2> else

3> the procedure ends;

NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.

1> else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):

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

1> else (RRCReconfiguration was received via SRB1):

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

…

1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a Random Access procedure triggered above;

2> stop timer T304 for that cell group;

2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;

…

[TS 38.331, 5.3.5.1]

[TS 38.331, 5.3.5.5.1]

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

…

1> if the CellGroupConfig contains the rlc-BearerToReleaseList:

2> perform RLC bearer release as specified in 5.3.5.5.3;

1> if the CellGroupConfig contains the rlc-BearerToAddModList:

2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4;

1> if the CellGroupConfig contains the mac-CellGroupConfig:

2> configure the MAC entity of this cell group as specified in 5.3.5.5.5;

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, 5.3.5.5.3]

1> for each logicalChannelIdentity value included in the rlc-BearerToReleaseList that is part of the current UE configuration (LCH release); or

1> for each logicalChannelIdentity value that is to be released as the result of an SCG release according to 5.3.5.4:

2> release the RLC entity or entities as specified in TS 38.322 [4, clause 5.1.3];

2> release the corresponding logical channel.

[TS 38.331, 5.3.5.5.4]

For each RLC-Bearer-Config received in the rlc-BearerToAddModList IE the UE shall:

1> if the UE’s current configuration contains a RLC bearer with the received logicalChannelIdentity:

…

2> reconfigure the RLC entity or entities in accordance with the received rlc-Config;

[TS 38.331, 5.3.5.5.8]

The UE shall:

1> if the release is triggered by reception of the sCellToReleaseList:

2> for each sCellIndex value included in the sCellToReleaseList:

3> if the current UE configuration includes an SCell with value sCellIndex:

4> release the SCell.

[TS 38.331, 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.

[TS 38.331, 5.3.5.6.1]

The UE shall perform the following actions based on a received RadioBearerConfig IE:

1> if the RadioBearerConfig includes the srb3-ToRelease and set to true:

2> perform the SRB release as specified in 5.3.5.6.2;

1> if the RadioBearerConfig includes the srb-ToAddModList:

2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3;

[TS 38.331, 5.3.5.6.2]

The UE shall:

1> release the PDCP entity of the SRB3.

[TS 38.331, 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> if the pdcp-Config is included:

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

8.2.2.1.2.3 Test description

8.2.2.1.2.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell and NR Cell 10 is the PSCell

– System information combination NR-4 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 RRC_CONNECTED using generic procedure parameter Connectivity (NR-DC) and NR-DC bearers (MCG(s) and SCG) according to TS 38.508-1 [4], Table 4.5.1-1.

8.2.2.1.2.3.2 Test procedure sequence

Table 8.2.2.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCReconfiguration message via SRB1 to establish SRB3.	<–	NR RRC: RRCReconfiguration	–	–
2	Check: Does the UE transmit an RRCReconfigurationComplete message via SRB1?	–>	NR RRC: RRCReconfigurationComplete	1	P
3	The SS transmits an RRCReconfiguration message via SRB3 to reconfigure NR MAC.	<–	NR RRC: RRCReconfiguration	–	–
4	Check: Does the UE transmit an RRCReconfigurationComplete message via SRB3?	–>	NR RRC: RRCReconfigurationComplete	2	P
5	The SS transmits an RRCReconfiguration message via SRB3 to reconfigure PDCP.	<–	NR RRC: RRCReconfiguration	–	–
6	Check: Does the UE transmit an RRCReconfigurationComplete message via SRB3?	–>	NR RRC: RRCReconfigurationComplete	3	P
7	The SS transmits an RRCReconfiguration message via SRB1 to release SRB3.	<–	NR RRC: RRCReconfiguration	–	–
8	Check: Does the UE transmit an RRCReconfigurationComplete message via SRB1?	–>	NR RRC: RRCConnectionReconfigurationComplete	4	P

8.2.2.1.2.3.3 Specific message contents

Table 8.2.2.1.2.3.3-1: RRCReconfiguration (step 1, Table 8.2.2.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	Not present
nonCriticalExtension SEQUENCE {
masterCellGroup	Not present
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-SecondaryCellGroup CHOICE {
nr-SCG	RRCReconfiguration-SCG	Table 8.2.2.1.2.3.3-2
}
}
}
radioBearerConfig2	RadioBearerConfig as per TS 38.508-1[4] Table 4.6.3-132 with condition SRB3
}
}
}
}
}
}

Table 8.2.2.1.2.3.3-2: RRCReconfiguration-SCG (Table 8.2.2.1.2.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	Not present
secondaryCellGroup	CellGroupConfig	Table 8.2.2.1.2.3.3-3
}
}
}

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

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	CellGroupId as per TS 38.508-1[4] Table 4.6.3-20 with condition NR-DC_SCG
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF BearerConfig {	1 entry
RLC-Bearer-Config[1]	RLC-BearerConfig as per TS 38.508-1[4] Table 4.6.3-148 with condition SRB3	entry 1
}
mac-CellGroupConfig	Not Present
physicalCellGroupConfig	Not Present
spCellConfig	Not Present
}

Table 8.2.2.1.2.3.3-3A: RRCReconfigurationComplete (Steps 2/8, Table 4.5.4.2-5)

Derivation Path: TS 38.508-1, table 4.6.1-14 with condition NR-SCG

Table 8.2.2.1.2.3.3-4: RRCReconfiguration (step 3, Table 8.2.2.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	CellGroupConfig	Table 8.2.2.1.2.3.3-5
}
}
}

Table 8.2.2.1.2.3.3-5: CellGroupConfig (Table 8.2.2.1.2.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	CellGroupId as per TS 38.508-1[4] Table 4.6.3-20 with condition NR-DC_SCG
rlc-BearerToAddModList	Not present
rlc-BearerToReleaseList	Not present
mac-CellGroupConfig	MAC-CellGroupConfig as per TS 38.508-1[4] Table 4.6.3-68 with condition DRX
physicalCellGroupConfig	Not present
spCellConfig	Not present
}

Table 8.2.2.1.2.3.3-6: RRCReconfiguration (step 5, Table 8.2.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 {
radioBearerConfig	RadioBearerConfig	Table 8.2.2.1.2.3.3-7
}
}
}

Table 8.2.2.1.2.3.3-7: RadioBearerConfig (Table 8.2.2.1.2.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132 with condition SRB3
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod {	1 entry
SRB-ToAddMod[1] SEQUENCE {
reestablishPDCP	true
}
}
securityConfig	Not present
}

Table 8.2.2.1.2.3.3-8: Void

Table 8.2.2.1.2.3.3-9: RRCReconfiguration (step 7, Table 8.2.2.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	Not present
nonCriticalExtension SEQUENCE {
masterCellGroup	Not present
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-ReleaseAndAdd	true
mrdc-SecondaryCellGroup CHOICE {
nr-SCG	RRCReconfiguration-SCG	Table 8.2.2.1.2.3.3-10
}
}
}
radioBearerConfig2	RadioBearerConfig	Table 8.2.2.1.2.3.3-11
}
}
}
}
}
}

Table 8.2.2.1.2.3.3-10: RRCReconfiguration-SCG (Table 8.2.2.1.2.3.3-9)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	Not present
secondaryCellGroup	CellGroupConfig	Table 8.2.2.1.2.3.3-12
}
}
}

Table 8.2.2.1.2.3.3-11: RadioBearerConfig (Table 8.2.2.1.2.3.3-10)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb3-ToRelease	true
securityConfig	Not present
}

Table 8.2.2.1.2.3.3-12: CellGroupConfig (Table 8.2.2.1.2.3.3-10)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToAddModList	Not Present
rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity {	1 entry
logicalChannelIdentity[1]	LogicalChannelIdentity as per TS 38.508-1[4] Table 4.6.3-67 with condition SRB3	entry 1
}
}

8.2.2.2 Split SRB Establishment and Release

8.2.2.2.1 Split SRB Establishment and Release / EN-DC

8.2.2.2.1.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG }

ensure that {

when { UE receives an RRCConnectionReconfiguration message on SRB1 to configure split SRB1 and split SRB2 with PDCP duplication activated }

then { UE configures the split SRBs and sends an RRCConnectionReconfigurationComplete message on split SRB1 with the PDCP PDU duplicated on the MCG and SCG path }

}

(2)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG and split SRB configured }

ensure that {

when { UE receives an RRCConnectionReconfiguration message on split SRB1 over the SCG path to release split SRB1 and split SRB2 }

then { UE releases split SRB1 and split SRB2 and sends an RRCConnectionReconfigurationComplete message on SRB1 over the MCG path}

}

(3)

with { UE in RRC_CONNECTED state in EN-DC mode with split SRB1 and split SRB2 configured with PDCP duplication }

ensure that {

when { UE receives a CounterCheck on split SRB1 over the SCG path }

then { UE replies with CounterCheckResponse on split SRB1 duplicated on the MCG and SCG path}

}

(4)

with { UE in RRC_CONNECTED state in EN-DC mode with split SRB1 and split SRB2 configured with PDCP duplication }

ensure that {

when { UE receives a IDENTITY REQUEST on split SRB2 over the SCG path }

then { UE replies with IDENTITY RESPONSE on split SRB2 duplicated on the MCG and SCG path}

8.2.2.2.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.5.3 and TS 38.331: clauses 5.3.5.3, 5.3.5.5.3, 5.3.5.6.1 and 5.3.5.6.3. Unless and otherwise stated these are Rel-15 requirements

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

…

1> set the content of RRCConnectionReconfigurationComplete message as follows:

…

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[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 secondaryCellGroup:

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

1> if the RRCReconfiguration message contains the radioBearerConfig:

2> perform the radio bearer configuration according to 5.3.5.6;

…

1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):

2> if RRCReconfiguration was received via SRB1:

3> submit the RRCReconfigurationComplete via the E-UTRA MCG embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10];

[TS 38.331, clause 5.3.5.5.3]

The UE shall:

1> for each logicalChannelIdentity value included in the rlc-BearerToReleaseList that is part of the current UE configuration (LCH release); or

1> for each logicalChannelIdentity value that is to be released as the result of an SCG release according to 5.3.5.4:

2> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3;

2> release the corresponding logical channel

[TS 38.331, clause 5.3.5.6.1]

The UE shall perform the following actions based on a received RadioBearerConfig IE:

…

1> if the RadioBearerConfig includes the srb-ToAddModList:

2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3;

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

8.2.2.2.1.3 Test description

8.2.2.2.1.3.1 Pre-test conditions

System Simulator:

– E-UTRA Cell 1 is the PCell and NR Cell 1 is the PSCell.

UE:

– None.

Preamble:

– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (EN-DC), Bearers (MCG(s) and SCG) established according to TS 38.508-1 [4], clause 4.5.4.

8.2.2.2.1.3.2 Test procedure sequence

Table 8.2.2.2.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS is configured not to send RLC ACK on split SRB1.	–	–	–	–
1	SS transmits RRCConnectionReconfiguration message containing NR RRCReconfiguration message to configure split SRB1 and split SRB2.	<–	RRCConnectionReconfiguration (RRCReconfiguration)	–	–
–	EXCEPTION: In parallel to the event described in step 2 the steps specified in Table 8.2.2.2.1.3.2-2 is taking place.	–	–	–	–
2	Check: Does the UE send a RRCConnectionReconfigurationComplete message containing NR RRCReconfigurationComplete message on split SRB1 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	RRCConnectionReconfigurationComplete (RRCReconfigurationComplete)	1	P
2A	After steps in table 8.2.2.2.1.3.2-2 are completed the SS is configured to send RLC ACK on split SRB1 and the last message received in step 2 is acknowledged.	–	–	–	–
2B	The SS is configured not to send RLC ACK on split SRB1.	–	–	–	–
3	SS transmits CounterCheck message for NR capabilities on split SRB1 over the SCG path.	<–	CounterCheck	–	–
–	EXCEPTION: In parallel to the event described in step 4 the steps specified in Table 8.2.2.2.1.3.2-3 is taking place.	–	–	–	–
4	Check: Does the UE send CounterCheckResponse message including UE radio access capability information for NR on split SRB1 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	CounterCheckResponse	3	P
4A	After steps in table 8.2.2.2.1.3.2-3 are completed the SS is configured to send RLC ACK on split SRB1 and the last message received in step 4 is acknowledged.	–	–	–	–
4B	The SS is configured not to send RLC ACK on split SRB2.	–	–	–	–
4C	The SS sends DLInformationTransfer message (carrying IDENTITY REQUEST message) on split SRB2 over the SCG path.	<–	DLInformationTransfer (IDENTITY REQUEST)	–	–
–	EXCEPTION: In parallel to the event described in step 4B the steps specified in Table 8.2.2.2.1.3.2-4 is taking place.	–	–	–	–
4D	Check: Does the UE send the ULInformationTransfer message (carrying IDENTITY RESPONSE message) on split SRB2 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	ULInformationTransfer (IDENTITY RESPONSE)	4	P
4E	After steps in table 8.2.2.2.1.3.2-4 are completed the SS is configured to send RLC ACK on split SRB2 and the last message received in step 4D is acknowledged.	–	–	–	–
5	SS transmits RRCConnectionReconfiguration message containing NR RRCReconfiguration message on split SRB1 to release split SRB1 and split SRB2 over the SCG path.	<–	RRCConnectionReconfiguration (RRCReconfiguration)	–	–
6	Check: Does the UE send RRCConnectionReconfigurationComplete containing NR RRCReconfigurationComplete message on SRB1 over the MCG path? Note: The SS makes sure that the UE does not send any message on the SCG path. The SS sends the RLC ACK for this message.	–>	RRCConnectionReconfigurationComplete (RRCReconfigurationComplete)	2	P

Table 8.2.2.2.1.3.2-2: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an RRCConnectionReconfigurationComplete message on SRB1 over the MCG path/E-UTRA Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

RRCConnectionReconfigurationComplete (RRCReconfigurationComplete)

–

Table 8.2.2.2.1.3.2-3: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an CounterCheckResponse message on SRB1 over the MCG path/E-UTRA Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

CounterCheckResponse

–

Table 8.2.2.2.1.3.2-4: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an DLInformationTransfer

(IDENTITY RESPONSE) message on SRB2 over the MCG path/E-UTRA Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

DLInformationTransfer

(IDENTITY RESPONSE)

–

8.2.2.2.1.3.3 Specific message contents

Table 8.2.2.2.1.3.3-1: RRCConnectionReconfiguration (step 1 Table 8.2.2.2.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition MCG_and_SCG and condition HO
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInfo	MobilityControlInfo-HO-SameCell	As per Table 8.2.2.2.1.3.3-1a
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15 CHOICE {
setup SEQUENCE {
nr-SecondaryCellGroupConfig-r15	OCTET STRING containing RRCReconfiguration-SplitSRB	As per Table 8.2.2.2.1.3.3-1
}
}
nr-RadioBearerConfig1-r15	OCTET STRING containing RadioBearerConfig-SplitSRB	As per Table 8.2.2.2.1.3.3-4
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.2.1.3.3-1a: MobilityControlInfo-HO-SameCell (Table 8.2.2.2.1.3.3-1)

Derivation Path: TS 36.508 [7], Table 4.6.5-1
Information Element	Value/remark	Comment	Condition
MobilityControlInfo-HO ::= SEQUENCE {
targetPhysCellId	PhysicalCellIdentity of E-UTRA Cell 1
carrierFreq	Not present
}

Table 8.2.2.2.1.3.3-2: RRCReconfiguration-SplitSRB (Table 8.2.2.2.1.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition EN-DC_HO
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	CellGroupConfig-SplitSRB
}
}
}

Table 8.2.2.2.1.3.3-3: CellGroupConfig-SplitSRB (Table 8.2.2.2.1.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	1
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig {	2 entries
RLC-BearerConfig[1] SEQUENCE {		entry 1
logicalChannelIdentity	1
servedRadioBearer CHOICE {
srb-Identity	1
}
reestablishRLC	Not present
RLC-Config	Not present.
mac-LogicalChannelConfig	Not present
}
RLC-BearerConfig[2] SEQUENCE {		entry 2
logicalChannelIdentity	2
servedRadioBearer CHOICE {
srb-Identity	2
}
reestablishRLC	Not present
RLC-Config	Not present
mac-LogicalChannelConfig	Not present
}
}
}

Table 8.2.2.2.1.3.3-4: RadioBearerConfig-SplitSRB (step 1, Table 8.2.2.2.1.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod {	2 entries
SRB-ToAddMod[1] SEQUENCE {		entry 1
srb-Identity	1
pdcp-Config	PDCP-Config-SRB with condition SRB1
}
SRB-ToAddMod[2] SEQUENCE {		entry 2
srb-Identity	2
pdcp-Config	PDCP-Config-SRB with condition SRB2
}
}
}

Table 8.2.2.2.1.3.3-5: PDCP-Config-SRB (Table 8.2.2.2.1.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-99 with condition Split_SRB
Information Element	Value/remark	Comment	Condition
PDCP-Config ::= SEQUENCE {
moreThanOneRLC SEQUENCE {
primaryPath SEQUENCE {
logicalChannel	1		SRB1
logicalChannel	2		SRB2
}
pdcp-Duplication	TRUE
}
}

Table 8.2.2.2.1.3.3-6: Void

Table 8.2.2.2.1.3.3-7: RRCConnectionReconfigurationComplete (steps 2, 6, Table 8.2.2.2.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-9
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfigurationComplete ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionReconfigurationComplete-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
scg-ConfigResponseNR-r15	Present
}
}
}
}
}
}
}
}
}

Table 8.2.2.2.1.3.3-8: CounterCheck (step 3, Table 8.2.2.2.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-0a
Information Element	Value/remark	Comment	Condition
CounterCheck ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
countercheck-r8 SEQUENCE {
drb-CountMSB-InfoList SEQUENCE (SIZE (1..maxDRB)) OF DRB-CountMSB-Info {	2 entries
DRB-CountMSB-Info[1] SEQUENCE {		entry 1
drb-Identity	DRBn	MCG DRB identity
countMSB-Uplink	0
countMSB-Downlink	0
}
DRB-CountMSB-Info[2] SEQUENCE {		entry 2
drb-Identity	DRB2	SCG DRB identity
countMSB-Uplink	0
countMSB-Downlink	0
}
}
}
}
}
}

Table 8.2.2.2.1.3.3-9: CounterCheckResponse (step 4, Table 8.2.2.2.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-0b
Information Element	Value/remark	Comment	Condition
CounterCheckResponse ::= SEQUENCE {
criticalExtensions CHOICE {
counterCheckResponse-r8 SEQUENCE {
drb-CountInfoList SEQUENCE (SIZE (0..maxDRB)) OF DRB-CountInfo {	2 entries
DRB-CountInfo[1] SEQUENCE {		entry 1
drb-Identity	DRB-Identity with Condition DRBn	MCG DRB identity as sent in Step 3
count-Uplink	Not checked
count-Downlink	Not checked
}
DRB-CountInfo[2] SEQUENCE {		entry 2
drb-Identity	DRB-Identity with Condition DRB2	SCG DRB
count-Uplink	Not checked
count-Downlink	Not checked
}
}
}
}
}

Table 8.2.2.2.1.3.3-10: RRCConnectionReconfiguration (step 5, Table 8.2.2.2.1.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.6.1-8 condition MCG_and_split
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15 CHOICE {
setup SEQUENCE {
nr-SecondaryCellGroupConfig-r15	RRCReconfiguration-SplitSRBRelease
}
}
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.2.1.3.3-11: RRCReconfiguration–SplitSRBRelease (Table 8.2.2.2.1.3.3-10)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	Not present
secondaryCellGroup	CellGroupConfig-SplitSRB-Release
measConfig	Not Present
}
}
}
}

Table 8.2.2.2.1.3.3-12: CellGroupConfig-SplitSRB-Release (Table 8.2.2.2.1.3.3-11)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-8
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	1
rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity {	2 entries
logicalChannelIdentity[1]	1	entry 1
logicalChannelIdentity[2]	2	entry 2
}
}

8.2.2.2.2 Split SRB Establishment and Release / NR-DC

8.2.2.2.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with NR-DC }

ensure that {

when { UE receives an RRCReconfiguration message on SRB1 to configure split SRB1 and split SRB2 with PDCP duplication activated }

then { UE configures the split SRBs and sends an RRCConnectionReconfigurationComplete message on split SRB1 with the PDCP PDU duplicated on the MCG and SCG path }

}

(2)

with { UE in RRC_CONNECTED state with NR-DC and split SRB configured }

ensure that {

when { UE receives an RRCReconfiguration message on split SRB1 over the SCG path to release split SRB1 and split SRB2 }

then { UE releases split SRB1 and split SRB2 and sends an RRCConnectionReconfigurationComplete message on SRB1 over the MCG path}

}

(3)

with { UE in RRC_CONNECTED state in NR-DC mode with split SRB1 and split SRB2 configured with PDCP duplication }

ensure that {

when { UE receives a CounterCheck on split SRB1 over the SCG path }

then { UE replies with CounterCheckResponse on split SRB1 duplicated on the MCG and SCG path}

}

(4)

with { UE in RRC_CONNECTED state in NR-DC mode with split SRB1 and split SRB2 configured with PDCP duplication }

ensure that {

when { UE receives a IDENTITY REQUEST on split SRB2 over the SCG path }

then { UE replies with IDENTITY RESPONSE on split SRB2 duplicated on the MCG and SCG path}

8.2.2.2.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 clauses 5.3.5.3, 5.3.5.5.3, 5.3.5.6.1 and 5.3.5.6.3. Unless and 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, or upon execution of the conditional reconfiguration (CHO, CPA or CPC):

…

1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:

2> if the mrdc-SecondaryCellGroupConfig is set to setup:

3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:

4> perform MR-DC release as specified in clause 5.3.5.10;

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

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

3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG:

4> perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG;

2> else (mrdc-SecondaryCellGroupConfig is set to release):

3> perform MR-DC release as specified in clause 5.3.5.10;

…

1> else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration or RRCResume via SRB1):

2> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SCG within mrdc-SecondaryCellGroup:

3> submit the RRCReconfigurationComplete message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3.

2> if the scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message:

3> if reconfigurationWithSync was included in spCellConfig in nr-SCG; or

3> if the SCG was deactivated before the reception of the NR RRC message containing the RRCReconfiguration message and lower layers consider that a Random Access procedure is needed for SCG activation:

4> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];

3> else:

4> the procedure ends;

2> else

3> the procedure ends;

NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.

1> else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):

2> if the RRCReconfiguration message was received within DLInformationTransferMRDC:

3> if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (NR SCG RRC Reconfiguration):

4> if reconfigurationWithSync was included in spCellConfig in nr-SCG:

5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];

4> else:

5> the procedure ends;

3> else:

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

2> else:

3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;

1> else (RRCReconfiguration was received via SRB1):

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

2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure:

3> resume SRB2, SRB4, and DRBs, multicast MRB, and BH RLC channels for IAB-MT, that are suspended;

…

[TS 38.331, clause 5.3.5.5.3]

The UE shall:

1> for each logicalChannelIdentity value included in the rlc-BearerToReleaseList that is part of the current UE configuration (LCH release); or

1> for each logicalChannelIdentity value that is to be released as the result of an SCG release according to 5.3.5.4:

2> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3;

2> release the corresponding logical channel

[TS 38.331, clause 5.3.5.6.1]

The UE shall perform the following actions based on a received RadioBearerConfig IE:

…

1> if the RadioBearerConfig includes the srb-ToAddModList:

2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3;

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

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;

8.2.2.2.2.3 Test description

8.2.2.2.2.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell and NR Cell 2 is the PSCell.

UE:

– None.

Preamble:

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

8.2.2.2.2.3.2 Test procedure sequence

Table 8.2.2.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS is configured not to send RLC ACK on split SRB1.	–	–	–	–
2	SS transmits RRCReconfiguration message with mrdc-SecondaryCellGroup is set to nr-SCG to configure split SRB1 and split SRB2.	<–	RRCReconfiguration	–	–
–	EXCEPTION: In parallel to the event described in step 3 the steps specified in Table 8.2.2.2.2.3.2-2 is taking place.	–	–	–	–
3	Check: Does the UE send a RRCReconfigurationComplete message on split SRB1 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	RRCReconfigurationComplete	1	P
4	After steps in table 8.2.2.2.2.3.2-2 are completed the SS is configured to send RLC ACK on split SRB1 and the last message received in step 3 is acknowledged.	–	–	–	–
5	The SS is configured not to send RLC ACK on split SRB1.	–	–	–	–
6	SS transmits CounterCheck message for capabilities on split SRB1 over the SCG path.	<–	CounterCheck	–	–
–	EXCEPTION: In parallel to the event described in step 7 the steps specified in Table 8.2.2.2.2.3.2-3 is taking place.	–	–	–	–
7	Check: Does the UE send CounterCheckResponse message including UE radio access capability information on split SRB1 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	CounterCheckResponse	3	P
8	After steps in table 8.2.2.2.2.3.2-3 are completed the SS is configured to send RLC ACK on split SRB1 and the last message received in step 7 is acknowledged.	–	–	–	–
–	EXCEPTION: In parallel to the event described in step 9 the steps specified in Table 8.2.2.2.2.3.2-4 is taking place.	–	–	–	–
9	The SS is configured not to send RLC ACK on split SRB2.	–	–	–	–
10	The SS sends DLInformationTransfer message (carrying IDENTITY REQUEST message) on split SRB2 over the SCG path.	<–	DLInformationTransfer (IDENTITY REQUEST)	–	–
11	Check: Does the UE send the ULInformationTransfer message (carrying IDENTITY RESPONSE message) on split SRB2 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	ULInformationTransfer (IDENTITY RESPONSE)	4	P
12	After steps in table 8.2.2.2.2.3.2-4 are completed the SS is configured to send RLC ACK on split SRB2 and the last message received in step 10 is acknowledged.	–	–	–	–
13	SS transmits RRCReconfiguration message message on split SRB1 to release split SRB1 and split SRB2 over the SCG path.	<–	RRCReconfiguration	–	–
14	Check: Does the UE send RRCReconfigurationComplete message on SRB1 over the MCG path? Note: The SS makes sure that the UE does not send any message on the SCG path. The SS sends the RLC ACK for this message.	–>	RRCReconfigurationComplete	2	P

Table 8.2.2.2.2.3.2-2: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an RRCReconfigurationComplete message on SRB1 over the MCG path/Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

RRCReconfigurationComplete

–

Table 8.2.2.2.2.3.2-3: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an CounterCheckResponse message on SRB1 over the MCG path/ Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

CounterCheckResponse

–

Table 8.2.2.2.2.3.2-4: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an DLInformationTransfer

(IDENTITY RESPONSE) message on SRB2 over the MCG path/ Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

DLInformationTransfer

(IDENTITY RESPONSE)

–

8.2.2.2.2.3.3 Specific message contents

Table 8.2.2.2.2.3.3-1: RRCReconfiguration (Table 8.2.2.2.2.3.2-1, Step 2 and Step 13)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	RadioBearerConfig	Table 8.2.2.2.2.3.3-2
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-SecondaryCellGroup CHOICE {
nr-SCG	RRCReconfiguration-SCG	Table 8.2.2.2.2.3.3-5

}
}
}
radioBearerConfig2	Not present
}
}
}
}
}
}

Table 8.2.2.2.2.3.3-2: RadioBearerConfig (Table 8.2.2.2.2.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132 with condition SRB1
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod {	2 entries
SRB-ToAddMod[1] SEQUENCE {		entry 1
SRB-Identity	SRB-Identity with condition SRB1
pdcp-Config	PDCP-Config-SRB1	Table 8.2.2.2.2.3.3-3
}
SRB-ToAddMod[2] SEQUENCE {		entry 2
SRB-Identity	SRB-Identity with condition SRB2
reestablishPDCP	Not present
discardOnPDCP	Not present
pdcp-Config	PDCP-Config-SRB2	Table 8.2.2.2.2.3.3-4
}
}
}

Table 8.2.2.2.2.3.3-3: PDCP-Config-SRB1 (Table 8.2.2.2.2.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-99 with condition Split_SRB
Information Element	Value/remark	Comment	Condition
PDCP-Config ::= SEQUENCE {
moreThanOneRLC	Not present		Step 13
moreThanOneRLC SEQUENCE {			Step 2
primaryPath SEQUENCE {
logicalChannel	1
}
pdcp-Duplication	true
}
}

Table 8.2.2.2.2.3.3-4: PDCP-Config-SRB2 (Table 8.2.2.2.2.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-99 with condition Split_SRB
Information Element	Value/remark	Comment	Condition
PDCP-Config ::= SEQUENCE {
moreThanOneRLC	Not present		Step 13
moreThanOneRLC SEQUENCE {			Step 2
primaryPath SEQUENCE {
logicalChannel	2
}
pdcp-Duplication	true
}
}

Table 8.2.2.2.2.3.3-5: RRCReconfiguration-SCG (Table 8.2.2.2.2.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	CellGroupConfig-SCG	Table 8.2.2.2.2.3.3-6
}
}
}

Table 8.2.2.2.2.3.3-6: CellGroupConfig-SCG (Table 8.2.2.2.2.3.3-5)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToAddModList	Not present		Step 13
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig {	2 entries		Step 2
RLC-BearerConfig[1]	RLC-BearerConfig with condition SRB1 and AM	entry 1
RLC-BearerConfig[2]	RLC-BearerConfig with condition SRB2 and AM	entry 2
}
rlc-BearerToReleaseList	Not present		Step 2
rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity {	2 entries		Step 13
LogicalChannelIdentity[1]	1
LogicalChannelIdentity[2]	2
}
mac-CellGroupConfig	Not present
physicalCellGroupConfig	Not present
spCellConfig	Not present
}

Table 8.2.2.2.2.3.3-7: RRCReconfigurationComplete (Table 8.2.2.2.2.3.2-1, step 3 and 14, Table 8.2.2.2.2.3.2-2, step 1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-14 with condition NR-DC

Table 8.2.2.2.2.3.3-8: CounterCheck (Table 8.2.2.2.2.3.2-1, Step 6)

Derivation Path: TS 38.508-1[4] Table 4.6.1-1
Information Element	Value/remark	Comment	Condition
CounterCheck ::= SEQUENCE {
criticalExtensions CHOICE {
counterCheck SEQUENCE {
drb-CountMSB-InfoList SEQUENCE (SIZE (1..maxDRB)) OF DRB-CountMSB-Info {	2 entries
DRB-CountMSB-Info[1] SEQUENCE {		entry 1
drb-Identity	DRB-Identity of DRBn	DRBn is the MCG DRB established in preamble
countMSB-Uplink	0
countMSB-Downlink	0
}
DRB-CountMSB-Info[2] SEQUENCE {		entry 2
drb-Identity	DRB-Identity of DRBj	DRBj is the SCG DRB established in preamble
countMSB-Uplink	0
countMSB-Downlink	0
}
}
}
}
}

Table 8.2.2.2.2.3.3-9: CounterCheckResponse (Table 8.2.2.2.2.3.2-1, Step 7, Table 8.2.2.2.2.3.2-3, Step 1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-2
Information Element	Value/remark	Comment	Condition
CounterCheckResponse ::= SEQUENCE {
criticalExtensions CHOICE {
counterCheckResponse SEQUENCE {
drb-CountInfoList SEQUENCE (SIZE (0..maxDRB)) OF DRB-CountInfo {	2 entries
DRB-CountInfo[1] SEQUENCE {		entry 1
drb-Identity	DRB-Identity of DRBn	DRBn is the MCG DRB established in preamble
count-Uplink	Not checked
count-Downlink	Not checked
}
DRB-CountInfo[2] SEQUENCE {		entry 1
drb-Identity	DRB-Identity of DRBj	DRBj is the SCG DRB established in preamble
count-Uplink	Not checked
count-Downlink	Not checked
}
}
}
}
}

8.2.2.2.3 Split SRB Establishment and Release / NE-DC

8.2.2.2.3.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with NE-DC }

ensure that {

when { UE receives an RRCReconfiguration message on SRB1 to configure split SRB1 and split SRB2 with PDCP duplication activated }

then { UE configures the split SRBs and sends an RRCConnectionReconfigurationComplete message on split SRB1 with the PDCP PDU duplicated on the MCG and SCG path }

}

(2)

with { UE in RRC_CONNECTED state with NE-DC and split SRB configured }

ensure that {

when { UE receives an RRCReconfiguration message on split SRB1 over the SCG path to release split SRB1 and split SRB2 }

then { UE releases split SRB1 and split SRB2 and sends an RRCConnectionReconfigurationComplete message on SRB1 over the MCG path}

}

(3)

with { UE in RRC_CONNECTED state in NE-DC mode with split SRB1 and split SRB2 configured with PDCP duplication }

ensure that {

when { UE receives a CounterCheck on split SRB1 over the SCG path }

then { UE replies with CounterCheckResponse on split SRB1 duplicated on the MCG and SCG path}

}

(4)

with { UE in RRC_CONNECTED state in NE-DC mode with split SRB1 and split SRB2 configured with PDCP duplication }

ensure that {

when { UE receives a IDENTITY REQUEST on split SRB2 over the SCG path }

then { UE replies with IDENTITY RESPONSE on split SRB2 duplicated on the MCG and SCG path}

8.2.2.2.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.3.5.3 and TS 36.331: clauses 5.3.5.3, 5.3.10.1a and 5.3.10.17. Unless and 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, or upon execution of the conditional reconfiguration (CHO, CPA or CPC):

…

1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:

2> if the mrdc-SecondaryCellGroupConfig is set to setup:

3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:

4> perform MR-DC release as specified in clause 5.3.5.10;

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

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

3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG:

4> perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG;

2> else (mrdc-SecondaryCellGroupConfig is set to release):

3> perform MR-DC release as specified in clause 5.3.5.10;

…

1> set the content of the RRCReconfigurationComplete message as follows:…

2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG:

3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331 [10] clause 5.3.5.3;

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the UE is configured with NE-DC:

2> if the received RRCConnectionReconfiguration message was included in an NR RRCResume message:

3> transfer the RRCConnectionReconfigurationComplete message via SRB1 embedded in NR RRC message RRCResumeComplete as specified in TS 38.331 [82], clause 5.3.13.4;

2> else:

3> transfer the RRCConnectionReconfigurationComplete message via SRB1 embedded in NR RRC message RRCReconfigurationComplete as specified in TS 38.331 [82], clause 5.3.5.3;

1> else:

2> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 38.331, clause 5.3.10.1a]

The UE shall:

1> for each srb-Identity value included in the srb-ToAddModListSCG that is not part of the current UE E-UTRA SCG configuration (i.e. SCG RLC bearer establishment):

2> apply the specified configuration defined in 9.1.2 for the corresponding SRB;

2> establish an (SCG) RLC entity in accordance with the received rlc-Config;

2> establish a (SCG) DCCH logical channel in accordance with the received logicalChannelConfig and with the logical channel identity set in accordance with 9.1.2;

2> if the UE is configured with DC:

3> associate the established SCG RLC bearer and DCCH logical channel with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

3> configure the E-UTRA PDCP entity to activate duplication with t-Reordering set to infinity;

2> else (i.e. the UE is configured with NE-DC):

3> associate the SCG RLC bearer and DCCH logical channel with the NR PDCP entity, i.e. as configured by NR see TS 38.331 [82], identified with the same srb-Identity within the current UE configuration;

1> for each srb-Identity value included in the srb-ToAddModListSCG that is part of the current UE SCG configuration (SCG RLC bearer reconfiguration):

2> re-establish the SCG RLC entity, if reestablishRLC is included;

2> reconfigure the RLC entity in accordance with the received rlc-Config;

2> reconfigure the DCCH logical channel in accordance with the received logicalChannelConfig;

[TS 36.331, clause 5.3.10.17]

The UE shall:

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

2> if the SRB configuration does not include an E-UTRA PDCP entity (release the SCG RLC bearer configuration):

3> re-establish the RLC entity as specified in TS 36.322 [7] for this SRB;

3> configure the E-UTRA PDCP entity to deactivate duplication;

2> release the RLC entity or entities;

2> release the DCCH logical channel;

2> if srb-Identity value is set to 4, release the PDCP entity;

8.2.2.2.3.3 Test description

8.2.2.2.3.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell and E-UTRA Cell 1 is the PSCell.

UE:

– None.

Preamble:

– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (NE-DC), Bearers (MCG(s) and SCG) established according to TS 38.508-1 [4], clause 4.5.4.

8.2.2.2.3.3.2 Test procedure sequence

Table 8.2.2.2.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS is configured not to send RLC ACK on split SRB1.	–	–	–	–
1	SS transmits RRCReconfiguration message containing Eutra RRCConnectionReconfiguration message to configure split SRB1 and split SRB2.	<–	RRCReconfiguration (RRCConnectionReconfiguration)	–	–
–	EXCEPTION: In parallel to the event described in step 2 the steps specified in Table 8.2.2.2.3.3.2-2 is taking place.	–	–	–	–
2	Check: Does the UE send a RRCReconfigurationComplete message containing Eutra RRCConnectionReconfigurationComplete message on split SRB1 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	RRCReconfigurationComplete (RRCConnectionReconfigurationComplete)	1	P
2A	After steps in table 8.2.2.2.3.3.2-2 are completed the SS is configured to send RLC ACK on split SRB1 and the last message received in step 2 is acknowledged.	–	–	–	–
2B	The SS is configured not to send RLC ACK on split SRB1.	–	–	–	–
3	SS transmits CounterCheck message for E-UTRA capabilities on split SRB1 over the SCG path.	<–	CounterCheck	–	–
–	EXCEPTION: In parallel to the event described in step 4 the steps specified in Table 8.2.2.2.3.3.2-3 is taking place.	–	–	–	–
4	Check: Does the UE send CounterCheckResponse message including UE radio access capability information for E-UTRA on split SRB1 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	CounterCheckResponse	3	P
4A	After steps in table 8.2.2.2.3.3.2-3 are completed the SS is configured to send RLC ACK on split SRB1 and the last message received in step 4 is acknowledged.	–	–	–	–
4B	The SS is configured not to send RLC ACK on split SRB2.	–	–	–	–
4C	The SS sends DLInformationTransfer message (carrying IDENTITY REQUEST message) on split SRB2 over the SCG path.	<–	DLInformationTransfer (IDENTITY REQUEST)	–	–
–	EXCEPTION: In parallel to the event described in step 4B the steps specified in Table 8.2.2.2.3.3.2-4 is taking place.	–	–	–	–
4D	Check: Does the UE send the ULInformationTransfer message (carrying IDENTITY RESPONSE message) on split SRB2 duplicated over the SCG path? Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.	–>	ULInformationTransfer (IDENTITY RESPONSE)	4	P
4E	After steps in table 8.2.2.2.3.3.2-4 are completed the SS is configured to send RLC ACK on split SRB2 and the last message received in step 4D is acknowledged.	–	–	–	–
5	SS transmits RRCReconfiguration message containing Eutra RRCConnectionReconfiguration message on split SRB1 to release split SRB1 and split SRB2 over the SCG path.	<–	RRCReconfiguration (RRCConnectionReconfiguration)	–	–
6	Check: Does the UE send RRCReconfigurationComplete message containing Eutra RRCConnectionReconfigurationComplete message on SRB1 over the MCG path? Note: The SS makes sure that the UE does not send any message on the SCG path. The SS sends the RLC ACK for this message.	–>	RRCReconfigurationComplete (RRCConnectionReconfigurationComplete)	2	P

Table 8.2.2.2.3.3.2-2: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an RRCReconfigurationComplete message on SRB1 over the MCG path/NR Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

RRCReconfigurationComplete (RRCConnectionReconfigurationComplete)

–

Table 8.2.2.2.3.3.2-3: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an CounterCheckResponse message on SRB1 over the MCG path/NR Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

CounterCheckResponse

–

Table 8.2.2.2.3.3.2-4: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE transmits an DLInformationTransfer

(IDENTITY RESPONSE) message on SRB2 over the MCG path/NR Cell 1

Note: The UE RLC might re-transmit this message several times (no more than maxRetxThreshold) until RLC ACK is sent by the SS.

–>

DLInformationTransfer

(IDENTITY RESPONSE)

–

8.2.2.2.3.3.3 Specific message contents

FFS

8.2.2.3 Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB

8.2.2.3.1 Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB with one UL path / EN-DC

8.2.2.3.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state in EN-DC mode with SRB3 and split SRB1 configured with no PDCP duplication}

ensure that {

when { UE receives RRCReconfiguration message on SRB3 to modify SCG DRB }

then { UE sends RRCReconfigurationComplete message on SRB3 over the SCG path }

}

(2)

with { UE in RRC_CONNECTED state in EN-DC mode with SRB3 and split SRB1 configured with no PDCP duplication }

ensure that {

when { UE receives an RRCConnectionReconfiguration message on split SRB1 on the SCG path to release SRB3 }

then { UE releases SRB3 and sends an RRCConnectionReconfigurationComplete message on split SRB1 over the MCG path }

}

(3)

with { UE in RRC_CONNECTED state in EN-DC mode with split SRB1 configured with no PDCP duplication}

ensure that {

when { UE receives an RRCConnectionReconfiguration message to release split SRB1 on SCG path }

then { UE releases split SRB1 and sends an RRCConnectionReconfigurationComplete message on SRB1 over the MCG path }

}

8.2.2.3.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 37.340, clause 7.6, TS 36.331, clauses 5.3.5.3 and TS 38.331:5.3.5.3, 5.3.5.5, 5.3.5.5.3, 5.3.5.6, 5.3.5.6.2 and 5.3.5.6.3. Unless and otherwise stated these are Rel-15 requirements.

[TS 37.340, clause 7.6]

Split SRB is supported for both SRB1 and SRB2 (split SRB is not supported for SRB0 and SRB3) in all MR-DC cases. RRC PDUs on split SRB are ciphered and integrity protected using NR PDCP.

Split SRB can be configured by the MN in Secondary Node Addition and/or Modification procedure, with SN configuration part provided by the SN. A UE can be configured with both split SRB and SRB3 simultaneously. SRB3 and the SCG leg of split SRB can be independently configured.

For the split SRB, the selection of transmission path in downlink depends on network implementation. For uplink, the UE is configured via MN RRC signalling whether to use MCG path or duplicate the transmission on both MCG and SCG.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

…

1> set the content of RRCConnectionReconfigurationComplete message as follows:

…

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[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 secondaryCellGroup:

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

1> if the RRCReconfiguration message contains the radioBearerConfig:

2> perform the radio bearer configuration according to 5.3.5.6;

…

1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):

2> if RRCReconfiguration was received via SRB1:

3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10].

[TS 38.331, clause 5.3.5.5.3]

The UE shall:

1> for each logicalChannelIdentity value included in the rlc-BearerToReleaseList that is part of the current UE configuration (LCH release); or

1> for each logicalChannelIdentity value that is to be released as the result of an SCG release according to 5.3.5.4:

2> release the RLC entity or entities as specified in TS 38.322 [4] clause 5.1.3;

2> release the corresponding logical channel.

[TS 38.331, clause 5.3.5.6.1

The UE shall perform the following actions based on a received RadioBearerConfig IE:

…

1> if the RadioBearerConfig includes the srb-ToAddModList:

2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3;

[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> if the current UE configuration as configured by E-UTRA in TS 36.331 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;

8.2.2.3.1.3 Test description

8.2.2.3.1.3.1 Pre-test conditions

System Simulator:

– E-UTRA Cell 1 is the PCell and NR Cell 1 is the PSCell.

– System Information combination as defined in TS 38.508-1 [4] clause 4.4.3.1.1 is used in E-UTRA Cell 1 and NR Cell 1.

UE:

– None.

Preamble:

– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (EN-DC), bearers (MCG(s) and SCG) established according to TS 38.508-1 [4], clause 4.5.4.

8.2.2.3.1.3.2 Test procedure sequence

Table 8.2.2.3.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits on SRB1 over MCG path/E-UTRA Cell 1 an RRCConnectionReconfiguration message to configure SRB3, to reconfigure SRB1 to split SRB1 without PDCP duplication and to reconfigure SRB2 to change the PDCP type from EUTRA PDCP to NR PDCP.	<–	RRCConnectionReconfiguration (RRCReconfiguration)	–	–
2	UE transmits an RRCConnectionReconfigurationComplete message on split SRB1 over the MCG path/EUTRA Cell 1.	–>	RRCConnectionReconfigurationComplete (RRCReconfigurationComplete)	–	–
3	The SS transmits on SRB3/SCG an NR RRCReconfiguration message to reconfigure SCG DRB.	<–	RRCReconfiguration	–	–
4	Check: Does the UE transmit an NR RRCReconfigurationComplete message on SRB3/NR Cell 1?	–>	RRCReconfigurationComplete	1	P
5	The SS transmits over split SRB1 SCG path/NR Cell 1 an RRCConnectionReconfiguration message to release SRB3.	<–	RRCConnectionReconfiguration (RRCReconfiguration)	–	–
–	Void	–	–	–	–
6	Check: Does the UE transmits an RRCConnectionReconfigurationComplete message on split SRB1 over the MCG path/EUTRA Cell 1?	–>	RRCConnectionReconfigurationComplete(RRCReconfigurationComplete)	2	P
7	The SS transmits an RRCConnectionReconfiguration message to release SRB1 over SCG path/NR Cell 1.	<–	RRCConnectionReconfiguration (RRCReconfiguration)	–	–
8	Check: Does the UE transmits an RRCConnectionReconfigurationComplete message on SRB1 over the MCG path/E-UTRA Cell 1?	–>	RRCConnectionReconfigurationComplete (RRCReconfigurationComplete)	3	P

Table 8.2.2.3.1.3.2-2: Void

8.2.2.3.1.3.3 Specific message contents

Table 8.2.2.3.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.3.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8
Information Element		Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInfo		MobilityControlInfo-HO-SameCell	As per Table 8.2.2.3.1.3.3-1E
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15 CHOICE {
setup SEQUENCE {
nr-SecondaryCellGroupConfig-r15		OCTET STRING including the RRCReconfiguration message and the IE secondaryCellGroup according table 8.2.2.3.1.3.3-1A
}
}
sk-Counter-r15	Increment the value by 1 from the previous value
nr-RadioBearerConfig1-r15		OCTET STRING including RadioBearerConfig according TS 38.508-1 [4], Table 4.6.3-132 with conditions EN-DC_DRB and Re-establish_PDCP and SRB3
nr-RadioBearerConfig2-r15		RadioBearerConfig according to Table 8.2.2.3.1.3.3-1C
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.3.1.3.3-1A: RRCReconfiguration (Table 8.2.2.3.1.3.3-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 {
secondaryCellGroup	OCTET STRING containing CellGroupConfig according to Table 8.2.2.3.1.3.3-1B.
}
}
}

Table 8.2.2.3.1.3.3-1B: CellGroupConfig (Table 8.2.2.3.1.3.3-1A)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition EN-DC and PSCell_change
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	1
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig {	3 entries
RLC-BearerConfig[1]	RLC-BearerConfig according to 38.508-1 [4], Table 4.6.3-148 with condition SRB1 and Re-establish_RLC	entry 1
RLC-BearerConfig[2]	RLC-BearerConfig according to 38.508-1 [4], Table 4.6.3-148 with condition SRB3	entry 2
RLC-BearerConfig[3]	RLC-BearerConfig according to 38.508-1 [4], Table 4.6.3-148 with conditions AM and DRB2 and Re-establish_RLC	entry 3
}
mac-LogicalChannelConfig	LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66
}

Table 8.2.2.3.1.3.3-1C: RadioBearerConfig (Table 8.2.2.3.1.3.3-1)

Derivation Path: TS 38.508-1[4] table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod {
SRB-ToAddMod[1] SEQUENCE {		entry 1
srb-Identity	LogicalChannelIdentity with condition SRB1
reestablishPDCP	true
discardOnPDCP	Not present
pdcp-Config	PDCP-Config according to table 8.2.2.3.1.3.3-1D
srb-Identity[2]	LogicalChannelIdentity with condition SRB2
reestablishPDCP[2]	true
discardOnPDCP[2]	Not present
pdcp-Config[2]	Not present
}
}
}

Table 8.2.2.3.1.3.3-1D: PDCP-Config (Table 8.2.2.3.1.3.3-1C)

Derivation Path: TS 38.508-1[4] table 4.6.3-99 with condition Split_SRB

Table 8.2.2.3.1.3.3-1E: MobilityControlInfo-HO-SameCell (Table 8.2.2.3.1.3.3-1)

Derivation Path: TS 36.508 [7], Table 4.6.5-1
Information Element	Value/remark	Comment	Condition
MobilityControlInfo-HO ::= SEQUENCE {
targetPhysCellId	PhysicalCellIdentity of E-UTRA Cell 1
carrierFreq	Not present
}

Table 8.2.2.3.1.3.3-2: Void

Table 8.2.2.3.1.3.3-3: Void

Table 8.2.2.3.1.3.3-4: RRCReconfiguration (step 3, Table 8.2.2.3.1.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 {
secondaryCellGroup	OCTET STRING containing CellGroupConfigaccording to table 8.2.2.3.1.3.3-5.
}
}
}

Table 8.2.2.3.1.3.3-5: CellGroupConfig (Table 8.2.2.3.1.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	1
mac-CellGroupConfig	MAC-CellGroupConfig according to table 8.2.2.3.1.3.3-5a
}

Table 8.2.2.3.1.3.3-5A: MAC-CellGroupConfig (Table 8.2.2.3.1.3.3-5)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-68
Information Element	Value/remark	Comment	Condition
MAC-CellGroupConfig ::= SEQUENCE {
bsr-Config SEQUENCE {
periodicBSR-Timer	sf5
retxBSR-Timer	sf40
}
}

Table 8.2.2.3.1.3.3-6: RRCConnectionReconfiguration (step 5, Table 8.2.2.3.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15 CHOICE {
setup SEQUENCE {
nr-SecondaryCellGroupConfig-r15	OCTET STRING containing RRCReconfiguration according to Table 8.2.2.3.1.3.3-8.
}
}
nr-RadioBearerConfig1-r15	RadioBearerConfig according to Table 8.2.2.3.1.3.3-7.
}
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.3.1.3.3-7: RadioBearerConfig (Table 8.2.2.3.1.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList	Not present
srb3-ToRelease	true
drb-ToAddModList	Not present
drb-ToReleaseList	Not present
securityConfig	Not present
}

Table 8.2.2.3.1.3.3-8: RRCReconfiguration (Table 8.2.2.3.1.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	OCTET STRING containing CellGroupConfig according to table 8.2.2.1.1.3.3-9.
}
}
}

Table 8.2.2.3.1.3.3-9: CellGroupConfig (Table 8.2.2.3.1.3.3-8)

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]	3		entry 1
}
mac-CellGroupConfig	Not present
physicalCellGroupConfig	Not present
sCellToAddModList	Not present
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex {	1 entry
SCellIndex[1]	SCellIndex	entry 1 NR Cell 1
}
}

Table 8.2.2.3.1.3.3-10: RRCConnectionReconfiguration (step 7, Table 8.2.2.3.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8 with condition HO-TO-EUTRA
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInfo		MobilityControlInfo-HO-SameCell	As per Table 8.2.2.3.1.3.3-1E
radioResourceConfigDedicated SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod {		1 entry
SRB-ToAddMod[1]		SRB-ToAddMod-DEFAULT using condition SRB1	entry 1 See TS 36.508 [7] subclause 4.8.2
}
}
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15 CHOICE {
setup SEQUENCE {
nr-SecondaryCellGroupConfig-r15	OCTET STRING containing RRCReconfigurationaccording to Table 8.2.2.3.1.3.3-11
}
}
nr-RadioBearerConfig1-r15	Not present
}
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.3.1.3.3-11: RRCReconfiguration (Table 8.2.2.3.1.3.2-10)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	OCTET STRING containing CellGroupConfig according to Table 8.2.2.3.1.3.3-12.
}
}
}

Table 8.2.2.3.1.3.3-12: CellGroupConfig (Table 8.2.2.3.1.3.3-11)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment		Condition
CellGroupConfig ::= SEQUENCE {
cellGroupId	1
rlc-BearerToReleaseList SEQUENCE (SIZE (1.. maxLC-ID)) OF LogicalChannelIdentity {	1 entry
LogicalChannelIdentity[1]	1		entry 1
}
}

8.2.2.3.2 Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB with one UL path / NR-DC

8.2.2.3.2.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state in NR-DC mode with SRB3 and split SRB1 configured with no PDCP duplication}

ensure that {

when { UE receives RRCReconfiguration message on SRB3 to modify SCG DRB }

then { UE sends RRCReconfigurationComplete message on SRB3 over the SCG path }

}

(2)

with { UE in RRC_CONNECTED state in NR-DC mode with SRB3 and split SRB1 configured with no PDCP duplication }

ensure that {

when { UE receives an RRCReconfiguration message on split SRB1 on the SCG path to release SRB3 }

then { UE releases SRB3 and sends an RRCReconfigurationComplete message on split SRB1 over the MCG path }

}

(3)

with { UE in RRC_CONNECTED state in NR-DC mode with split SRB1 configured with no PDCP duplication}

ensure that {

when { UE receives an RRCReconfiguration message to release split SRB1 on SCG path }

then { UE releases split SRB1 and sends an RRCReconfigurationComplete message on SRB1 over the MCG path }

}

8.2.2.3.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 37.340, clause 7.6 and TS 38.331, clause 5.3.5.3, 5.3.5.5.3, 5.3.5.5.4, 5.3.5.6.1, 5.3.5.6.3. Unless and otherwise stated these are Rel-15 requirements.

[TS 37.340, clause 7.6]

Split SRB is supported for both SRB1 and SRB2 (split SRB is not supported for SRB0 and SRB3) in all MR-DC cases. RRC PDUs on split SRB are ciphered and integrity protected using NR PDCP.

[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> if the RRCReconfiguration includes the masterKeyUpdate:

2> perform AS security key update procedure as specified in 5.3.5.7;

1> if the RRCReconfiguration includes the sk-Counter:

2> perform security key update procedure as specified in 5.3.5.7;

1> if the RRCReconfiguration includes the secondaryCellGroup:

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

1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:

2> if the mrdc-SecondaryCellGroupConfig is set to setup:

3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:

4> perform MR-DC release as specified in clause 5.3.5.10;

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

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

…

1> if the RRCReconfiguration message includes the radioBearerConfig:

2> perform the radio bearer configuration according to 5.3.5.6;

1> if the RRCReconfiguration message includes the radioBearerConfig2:

2> perform the radio bearer configuration according to 5.3.5.6;

…

1> set the content of the RRCReconfigurationComplete message as follows:

…

2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:

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

…

1> else if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration via SRB1):

2> if reconfigurationWithSync was included in spCellConfig in nr-SCG:

3> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];

2> else

3> the procedure ends;

NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.

1> else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):

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

1> else (RRCReconfiguration was received via SRB1):

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

2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure:

3> resume SRB2 and DRBs that are suspended;

[TS 38.331, clause 5.3.5.5.3]

The UE shall:

1> for each logicalChannelIdentity value included in the rlc-BearerToReleaseList that is part of the current UE configuration (LCH release); or

1> for each logicalChannelIdentity value that is to be released as the result of an SCG release according to 5.3.5.4:

2> release the RLC entity or entities as specified in TS 38.322 [4] clause 5.1.3;

2> release the corresponding logical channel.

[TS 38.331, clause 5.3.5.5.4]

For each RLC-BearerConfig received in the rlc-BearerToAddModList IE the UE shall:

1> if the UE’s current configuration contains an RLC bearer with the received logicalChannelIdentity within the same cell group:

2> if reestablishRLC is received:

3> re-establish the RLC entity as specified in TS 38.322 [4];

2> reconfigure the RLC entity or entities in accordance with the received rlc-Config;

2> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig;

NOTE: The network does not re-associate an already configured logical channel with another radio bearer. Hence servedRadioBearer is not present in this case.

…

[TS 38.331, clause 5.3.5.6.1

The UE shall perform the following actions based on a received RadioBearerConfig IE:

…

1> if the RadioBearerConfig includes the srb-ToAddModList:

2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3;

…

[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 NR PDCP to NR PDCP):

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

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

3> release the NR 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;

8.2.2.3.2.3 Test description

8.2.2.3.2.3.1 Pre-test conditions

System Simulator:

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

– System information combination NR-4 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 RRC_CONNECTED using generic procedure parameter Connectivity (NR-DC), bearers (MCG(s) and SCG) established according to TS 38.508-1 [4], clause 4.5.4.

8.2.2.3.2.3.2 Test procedure sequence

Table 8.2.2.3.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits on SRB1 over MCG path/NR Cell 1 an RRCReconfiguration message to configure SRB3 and reconfigure SRB1 to split SRB without PDCP duplication.	<–	RRCReconfiguration	–	–
2	UE transmits an RRCReconfigurationComplete message on split SRB1 over the MCG path/NR Cell 1.	–>	RRCReconfigurationComplete	–	–
3	The SS transmits on SRB3/SCG an NR RRCReconfiguration message to reconfigure SCG DRB.	<–	RRCReconfiguration	–	–
4	Check: Does the UE transmit an NR RRCReconfigurationComplete message on SRB3/NR Cell 10?	–>	RRCReconfigurationComplete	1	P
5	The SS transmits over split SRB1 SCG path/NR Cell 10 an RRCReconfiguration message to release SRB3.	<–	RRCReconfiguration	–	–
6	Check: Does the UE transmits an RRCReconfigurationComplete message on split SRB1 over the MCG path/NR Cell 1?	–>	RRCReconfigurationComplete	2	P
7	The SS transmits an RRCReconfiguration message to release SRB1 over SCG path/NR Cell 10.	<–	RRCReconfiguration	–	–
8	Check: Does the UE transmits an RRCReconfigurationComplete message on SRB1 over the MCG path/NR Cell 1?	–>	RRCReconfigurationComplete	3	P

8.2.2.3.2.3.3 Specific message contents

Table 8.2.2.3.2.3.3-1: RRCReconfiguration (step 1, Table 8.2.2.3.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	OCTET STRING containing RadioBearerConfig given in Table 8.2.2.3.2.3.3-4
nonCriticalExtension SEQUENCE {
masterCellGroup	Not present
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-SecondaryCellGroup CHOICE {
nr-SCG	OCTET STRING containing the RRCReconfiguration given in Table 8.2.2.3.2.3.3-2
}
}
}
radioBearerConfig2	OCTET STRING containing the RadioBearerConfig specified in TS 38.508-1 [4], Table 4.6.3-132 with condition SRB3
sk-Counter	Increment the value by 1 from the previous value
}
}
}
}
}
}

Table 8.2.2.3.2.3.3-2: RRCReconfiguration (Table 8.2.2.3.2.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with Condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	OCTET STRING containing CellGroupConfig given in Table 8.2.2.3.2.3.3-3
}
}
}

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

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig {	2+n entries	n is the number of established SCG DRBs. Value of n depends on TTCN implementation
RLC-BearerConfig[1]	RLC-BearerConfig according to 38.508-1 [4], Table 4.6.3-148 with condition SRB1 and Re-establish_RLC	entry 1
RLC-BearerConfig[2]	RLC-BearerConfig according to 38.508-1 [4], Table 4.6.3-148 with condition SRB3	entry 2
RLC-BearerConfig[2+k: k=1..n]	RLC-BearerConfig according to 38.508-1 [4], Table 4.6.3-148 with conditions AM and DRBk and Re-establish_RLC	entry 2+k
}
mac-LogicalChannelConfig	LogicalChannelConfig according to 38.508-1 [4], table 4.6.3-66
}

Table 8.2.2.3.2.3.3-4: RadioBearerConfig (Table 8.2.2.3.2.3.3-1)

Derivation Path: TS 38.508-1[4] table 4.6.3-132 with condition SRB_NR_PDCP and Re-establish_PDCP
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod {	2 entries
SRB-ToAddMod[1] SEQUENCE {		entry 1 SRB1
pdcp-Config	PDCP-Config according to TS 38.508-1[4] table 4.6.3-99 with condition Split_SRB
}
}
}

Table 8.2.2.3.2.3.3-5: RRCReconfiguration (step 3, Table 8.2.2.3.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 {
secondaryCellGroup	OCTET STRING containing CellGroupConfig given in Table 8.2.2.3.2.3.3-6
}
}
}

Table 8.2.2.3.2.3.3-6: CellGroupConfig (Table 8.2.2.3.2.3.3-5)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
mac-CellGroupConfig	MAC-CellGroupConfig according to Table 8.2.2.3.2.3.3-7
}

Table 8.2.2.3.2.3.3-7: MAC-CellGroupConfig (Table 8.2.2.3.2.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-68
Information Element	Value/remark	Comment	Condition
MAC-CellGroupConfig ::= SEQUENCE {
bsr-Config SEQUENCE {
periodicBSR-Timer	sf5
retxBSR-Timer	sf40
}
}

Table 8.2.2.3.2.3.3-8: RRCReconfiguration (step 5, Table 8.2.2.3.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	Not present
nonCriticalExtension SEQUENCE {
masterCellGroup	Not present
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-SecondaryCellGroup CHOICE {
nr-SCG	OCTET STRING containing RRCReconfiguration according to Table 8.2.2.3.2.3.3-10
}
}
}
radioBearerConfig2	RadioBearerConfig according to Table 8.2.2.3.2.3.3-9
}
}
}
}
}
}

Table 8.2.2.3.2.3.3-9: RadioBearerConfig (Table 8.2.2.3.2.3.3-8)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList	Not present
srb3-ToRelease	true
drb-ToAddModList	Not present
drb-ToReleaseList	Not present
securityConfig	Not present
}

Table 8.2.2.3.2.3.3-10: RRCReconfiguration (Table 8.2.2.3.2.3.3-8)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	OCTET STRING containing CellGroupConfig according to Table 8.2.2.3.2.3.3-11
}
}
}

Table 8.2.2.3.2.3.3-11: CellGroupConfig (Table 8.2.2.3.2.3.3-10)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition NR-DC_SCG
Information Element	Value/remark	Comment		Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToAddModList	Not present
rlc-BearerToReleaseList SEQUENCE (SIZE (1.. maxLC-ID)) OF LogicalChannelIdentity {	1 entry
LogicalChannelIdentity[1]	3		entry 1
}
mac-CellGroupConfig	Not present
physicalCellGroupConfig	Not present
}

Table 8.2.2.3.2.3.3-12: RRCReconfiguration (step 7, Table 8.2.2.3.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	OCTET STRING containing RadioBearerConfig according Table 8.2.2.3.2.3.3-13
nonCriticalExtension SEQUENCE {
masterCellGroup	Not present
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-SecondaryCellGroup CHOICE {
nr-SCG	OCTET STRING containing RRCReconfiguration according to Table 8.2.2.3.2.3.3-14
}
}
}
radioBearerConfig2	Not present
}
}
}
}
}
}

Table 8.2.2.3.2.3.3-13: RadioBearerConfig (Table 8.2.2.3.2.3.3-12)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-132 with condition SRB1
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod {	1 entry
SRB-ToAddMod[1] SEQUENCE {		entry 1
reestablishPDCP	true
pdcp-Config	PDCP-Config with condition SRB
}
}
}

Table 8.2.2.3.2.3.3-14: RRCReconfiguration (Table 8.2.2.3.2.3.3-12)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC_SCG
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	OCTET STRING containing CellGroupConfig according to Table 8.2.2.3.2.3.3-15
}
}
}

Table 8.2.2.3.2.3.3-15: CellGroupConfig (Table 8.2.2.3.2.3.3-14)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition NR-DC_SCG
Information Element	Value/remark	Comment		Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToReleaseList SEQUENCE (SIZE (1.. maxLC-ID)) OF LogicalChannelIdentity {	1 entry
LogicalChannelIdentity[1]	1		entry 1
}
}

8.2.2.4 PSCell addition, modification and release / SCG DRB

8.2.2.4.1 PSCell addition, modification and release / SCG DRB / EN-DC

8.2.2.4.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to add PSCell with SCG DRB }

then { UE configures the PSCell with SCG DRB and sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to modify SCG DRB }

then {UE reconfigures the SCG DRB and sends an RRCConnectionReconfigurationComplete message }

}

(3)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to release PSCell with SCG DRB }

then { UE releases the PSCell and SCG DRB and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.4.1.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 36.331, clause 5.3.5.3, TS 38.331, clauses 5.3.5.3, 5.3.5.5.7, 5.3.5.6.4 and 5.3.5.6.5. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or

1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:

2> perform ENDC release as specified in TS38.331 [82], clause 5.3.5.10;

1> if the received RRCConnectionReconfiguration includes the sk-Counter:

2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.7;

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

…

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:

3> include perCC-GapIndicationList and numFreqEffective;

2> if the frequencies are configured for reduced measurement performance:

3> include numFreqEffectiveReduced;

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[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 secondaryCellGroup:

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

1> if the RRCReconfiguration message contains the radioBearerConfig:

2> perform the radio bearer configuration according to 5.3.5.6;

1> if the RRCReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

…

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;

1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):

2> if RRCReconfiguration was received via SRB1:

3> construct RRCReconfigurationComplete message and submit it via the EUTRA MCG embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10].

3> if reconfigurationWithSync was included in spCellConfig of an SCG:

4> initiate the random access procedure on the SpCell, as specified in TS 38.321 [3];

3> else:

4> the procedure ends;

NOTE: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.

2> else (RRCReconfiguration was received via SRB3):

3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration.

NOTE:For EN-DC, in the case RRCReconfiguration is received via SRB1, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.

1 > else:

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

2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure:

3> resume SRB2 and DRBs that are suspended;

1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a random access procedure triggered above;

2> stop timer T304 for that cell group;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;

2> if the reconfigurationWithSync was included in spCellConfig of an MCG::

3> if T390 is running:

4> stop timer T390 for all access categories;

4> perform the actions as specified in 5.3.14.4.

3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and

3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1:

4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;

4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2;

2> the procedure ends;

NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.

[TS 38.331, clause 5.3.5.5.7]

The UE shall:

…

1> if the SpCellConfig contains spCellConfigDedicated:

2> configure the SpCell in accordance with the spCellConfigDedicated;

2> consider the bandwidth part indicated in firstActiveUplinkBWP-Id if configured to be the active uplink bandwidth part;

2> consider the bandwidth part indicated in firstActiveDownlinkBWP-Id if configured to be the active downlink bandwidth part;

2> if the any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received spCellConfigDedicated:

3> stop timer T310 for the corresponding SpCell, if running;

3> reset the counters N310 and N311.

[TS 38.331, clause 5.3.5.6.4]

Editor’s Note: FFS / TODO: Add handling for the new QoS concept (mapping of flows; configuration of QFI-to-DRB mapping; reflective QoS…) but keep also EPS-Bearer handling for the EN-DC case

The UE shall:

1> for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuratio; orn:

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

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

2> if the reestablishPDCP is set:

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

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

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

5> configure the PDCP entity with the ciphering algorithm and K_UPenc key configured/derived as specified in TS 36.331 [10], clause 5.4.2.3, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;

3> else:

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

5> configure the PDCP entity with the ciphering algorithm and K_UPenc key associated with the master key (K_eNB/ K_gNB) or the secondary key (S-K_gNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;

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

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

3> re-establish the PDCP entity of this DRB as specified in 38.323 [5], clause 5.1.2;

2> else, if the recoverPDCP is set:

3> trigger the PDCP entity of this DRB to perform data recovery as specified in 38.323[5];

2> if the pdcp-Config is included:

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

…

NOTE 1: Void

NOTE 2: When determining whether a drb-Identity value is part of the current UE configuration, the UE does not distinguish which RadioBearerConfig and DRB-ToAddModList that DRB was originally configured in. To re-associate a DRB with a different key (KeNB to S-KeNB or vice versa), the network provides the drb-Identity value in the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list the drb-Identity in the (source) drb-ToReleaseList.

NOTE 3: When setting the reestablishPDCP flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity.

NOTE 4: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated.

NOTE 5: Ciphering and integrity protection can be enabled or disabled for a DRB. The enabling/disabling of cipheriong or integrity protection can be changed only by releasing and adding the DRB.

8.2.2.4.1.3 Test description

8.2.2.4.1.3.1 Pre-test conditions

System Simulator:

– E-UTRA Cell 1 is the PCell and NR Cell 1 is the PSCell.

UE:

– None.

Preamble:

– If pc_IP_Ping is set to TRUE then, the UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (E-UTRA/EPC) established according to TS 38.508-1 [4], clause 4.5.4.

– Else, the UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (E-UTRA/EPC) established and Test Mode (On) associated with UE test loop mode B configured on E-UTRA Cell 1 according to TS 38.508-1 [4], clause 4.5.4.

8.2.2.4.1.3.2 Test procedure sequence

Table 8.2.2.4.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message containing NR RRCReconfiguration message to add NR PSCell with SCG DRB. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.	<–	RRCConnectionReconfiguration (RRCReconfiguration)	–	–
2	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message containing NR RRCReconfigurationComplete message?	–>	RRCConnectionReconfigurationComplete (RRCReconfigurationComplete)	1	P
3	The UE transmits an ULInformationTransfer message containing the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	ULInformationTransfer	–	–
–	EXCEPTION: Steps 4a1 to 4a2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation.	–	–	–	–
4a1	IF pc_IP_Ping = FALSE, then, the SS transmits a CLOSE UE TEST LOOP message.	<–	CLOSE UE TEST LOOP	–	–
4a2	The UE transmits a CLOSE UE TEST LOOP COMPLETE message.	–>	CLOSE UE TEST LOOP COMPLETE	–	–
5	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 SCG DRB#2?	–	–	1	P
6	SS transmits RRCConnectionReconfiguration message containing NR RadioBearerConfig to modify PDCP discardTimer value of SCG DRB.	<–	RRCConnectionReconfiguration	–	–
7	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?	–>	RRCConnectionReconfigurationComplete	2	P
8	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 SCG DRB#2?	–	–	2	P
9	SS transmits RRCConnectionReconfiguration message containing nr-Config-r15 and NR RadioBearerConfig to release PSCell and SCG DRB. RRCConnectionReconfiguration message contains the DEACTIVATE EPS BEARER CONTEXT REQUEST message.	<–	RRCConnectionReconfiguration	–	–
10	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?	–>	RRCConnectionReconfigurationComplet	3	P
11	The UE transmits an ULInformationTransfer message containing the DEACTIVATE EPS BEARER CONTEXT ACCEPT message.	–>	ULInformationTransfer	–	–

8.2.2.4.1.3.3 Specific message contents

Table 8.2.2.4.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.4.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15 CHOICE {
setup SEQUENCE {
nr-SecondaryCellGroupConfig-r15	OCTET STRING including the RRCReconfiguration message and the IE secondaryCellGroup.
}
}
nr-RadioBearerConfig1-r15	OCTET STRING including RadioBearerConfig.
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.4.1.3.3-2: RRCReconfiguration (Table 8.2.2.4.1.3.3-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 {
secondaryCellGroup	CellGroupConfig
}
}
}

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

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig {	1 entry
RLC-BearerConfig[1] SEQUENCE {		entry 1
servedRadioBearer CHOICE {
drb-Identity	2	SCG DRB Id
}
}
}
}

Table 8.2.2.4.1.3.3-4: RadioBearerConfig (Table 8.2.2.4.1.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod {	1 entry
DRB-ToAddMod[1] SEQUENCE {		entry 1
cnAssociation CHOICE {
eps-BearerIdentity	6	Dedicated EPS bearer Id of SCG DRB
}
drb-Identity	2	SCG DRB Id
}
}
securityConfig SEQUENCE {
keyToUse	secondary
}
}

Table 8.2.2.4.1.3.3-5: RRCConnectionReconfiguration (step 6, Table 8.2.2.4.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-RadioBearerConfig1-r15	OCTET STRING including RadioBearerConfig.
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.4.1.3.3-6: RadioBearerConfig (Table 8.2.2.4.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-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod {	1 entry
DRB-ToAddMod[1] SEQUENCE {		entry 1
cnAssociation CHOICE {
eps-BearerIdentity	6	Dedicated EPS bearer Id of SCG DRB
}
drb-Identity	2	SCG DRB Id
pdcp-Config	PDCP-Config
}
}
}

Table 8.2.2.4.1.3.3-7: PDCP-Config (Table 8.2.2.4.1.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-99
Information Element	Value/remark	Comment	Condition
PDCP-Config ::= SEQUENCE {
drb SEQUENCE {
discardTimer	ms500	Other than default value.
}
}

Table 8.2.2.4.1.3.3-8: RRCConnectionReconfiguration (step 9, Table 8.2.2.4.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nr-Config-r15 CHOICE {
release
}
nr-RadioBearerConfig1-r15	OCTET STRING including RadioBearerConfig.
}
}
}
}
}
}
}
}
}
}
}
}

Table 8.2.2.4.1.3.3-9: RadioBearerConfig (Table 8.2.2.4.1.3.3-8)

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

8.2.2.4.2 PSCell addition, modification and release / SCG DRB / NR-DC

8.2.2.4.2.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCReconfiguration message to add an NR PSCell with SCG DRB }

then { UE configures the PSCell with SCG DRB and sends an RRCReconfigurationComplete message }

}

(2)

with { UE in NR RRC_CONNECTED state with NR-DC }

ensure that {

when { UE receives an RRCReconfiguration message to modify SCG DRB }

then { UE reconfigures the SCG DRB and sends an RRCReconfigurationComplete message }

}

(3)

with { UE in NR RRC_CONNECTED state with NR-DC }

ensure that {

when { UE receives an RRCReconfiguration message to release PSCell with SCG DRB }

then { UE releases the PSCell and SCG DRB and sends an RRCReconfigurationComplete message }

}

8.2.2.4.2.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 38.331, clauses 5.3.5.3, 5.3.5.5.1, 5.3.5.5.7, 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.5.3]

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

…

1> if the RRCReconfiguration includes the secondaryCellGroup:

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

1> if the RRCReconfiguration message contains the radioBearerConfig:

2> perform the radio bearer configuration according to 5.3.5.6;

1> if the RRCReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

…

1> set the content of the RRCReconfigurationComplete message as follows:

2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:

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

2> if reconfigurationWithSync was included in spCellConfig in nr-SCG:

3> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];

2> else

3> the procedure ends;

NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.

[TS 38.331, clause 5.3.5.5.1]

…

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 spCellConfigDedicated:

2> configure the SpCell in accordance with the spCellConfigDedicated;

2> consider the bandwidth part indicated in firstActiveUplinkBWP-Id if configured to be the active uplink bandwidth part;

2> consider the bandwidth part indicated in firstActiveDownlinkBWP-Id if configured to be the active downlink bandwidth part;

2> if any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received spCellConfigDedicated:

3> stop timer T310 for the corresponding SpCell, if running;

3> stop timer T312 for the corresponding SpCell, if running;

3> reset the counters N310 and N311.

[TS 38.331, clause 5.3.5.6.4]

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 DRB is associated with an eps-BearerIdentity:

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 connected to E-UTRA/5GC:

4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC:

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

4> else (i.e., a UE capable of NGEN-DC):

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

…

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

3> configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the K_UPint key associated with the master (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;

…

1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and not configured with dapsConfig:

2> if the reestablishPDCP is set:

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

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

4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC:

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

6> configure the PDCP entity with the ciphering algorithm and K_UPenc key configured/derived as specified in TS 36.331 [10], clause 5.4.2.3, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;

4> else (i.e., a UE capable of NGEN-DC):

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

6> configure the PDCP entity with the ciphering algorithm and K_UPenc key associated with the master key (K_eNB) or the secondary key (S-K_gNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;

…

2> else, if the recoverPDCP is set:

3> trigger the PDCP entity of this DRB to perform data recovery 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.

2> if the sdap-Config is included:

3> reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS37.324 [24];

3> for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB;

NOTE 1: Void.

NOTE 2: When determining whether a drb-Identity value is part of the current UE configuration, the UE does not distinguish which RadioBearerConfig and DRB-ToAddModList that DRB was originally configured in. To re-associate a DRB with a different key (K_eNB to S-K_gNB,K_gNB to S-K_eNB, K_gNB to S-K_gNB, or vice versa), the network provides the drb-Identity value in the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list the drb-Identity in the (source) drb-ToReleaseList.

NOTE 4: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated.

NOTE 5: Ciphering and integrity protection can be enabled or disabled for a DRB. The enabling/disabling of ciphering or integrity protection can be changed only by releasing and adding the DRB.

8.2.2.4.2.3 Test description

8.2.2.4.2.3.1 Pre-test conditions

System Simulator:

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

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

UE:

– None.

Preamble:

– If pc_IP_Ping is set to TRUE then, the UE is in state NR RRC_CONNECTED using generic procedure parameter Connectivity (NR), according to TS 38.508-1 [4], clause 4.5.4.

– Else, the UE is in state NR RRC_CONNECTED using generic procedure parameter Connectivity (NR), Test Mode (On) associated with UE test loop mode B configured on NR Cell 1 according to TS 38.508-1 [4], clause 4.5.4.

8.2.2.4.2.3.2 Test procedure sequence

Table 8.2.2.4.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND to add NR PSCell with SCG DRB.	<–	NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMMAND	–	–
2	Check: Does the UE transmit an RRCReconfigurationComplete message including nr-SCG-Response?	–>	RRCReconfigurationComplete	1	P
2A	The UE transmits a ULInformationTransfer message and an PDU SESSION MODIFICATION COMPLETE message.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE	–	–
–	EXCEPTION: Steps 2Ba1 to 2Ba2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation.	–	–	–	–
2Ba1	IF pc_IP_Ping = FALSE, then, the SS transmits a CLOSE UE TEST LOOP message.	<–	CLOSE UE TEST LOOP	–	–
2Ba2	The UE transmits a CLOSE UE TEST LOOP COMPLETE message.	–>	CLOSE UE TEST LOOP COMPLETE	–	–
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 SCG DRB?	–	–	1	P
4	SS transmits RRCReconfiguration message containing NR RadioBearerConfig to modify PDCP discardTimer value of SCG DRB.	<–	RRCReconfiguration	–	–
5	Check: Does the UE transmit an RRCReconfigurationComplete message?	–>	RRCReconfigurationComplete	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 SCG DRB?	–	–	2	P
7	SS transmits RRCReconfiguration message to release NR PSCell and SCG DRB.	<–	RRCReconfiguration	–	–
8	Check: Does the UE transmit an RRCReconfigurationComplete message?	–>	RRCReconfigurationComplete	3	P

8.2.2.4.2.3.3 Specific message contents

Table 8.2.2.4.2.3.3-1: RRCReconfiguration (step 1, Table 8.2.2.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC

Table 8.2.2.4.2.3.3-1A: PDU SESSION MODIFICATION COMMAND (step 1, Table 8.2.2.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.2-9.
Information Element	Value/remark	Comment	Condition
PDU session ID	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST associated with the Internet PDU session if available or with the first PDU session
Authorized QoS rules	One entry
QoS rule [1]	Reference QoS rule #5 as defined in TS 38.508-1 [4], Table 4.8.2.1-5.	QFI=5
Authorized QoS flow descriptions	One entry
QoS flow [1]	Reference QoS flow #5 as defined in TS 38.508-1 [4], Table 4.8.2.3-5.	QFI=5

Table 8.2.2.4.2.3.3-2: Void

Table 8.2.2.4.2.3.3-3: RRCCReconfiguration (step 4, Table 8.2.2.4.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 {
nonCriticalExtension SEQUENCE {
radioBearerConfig2	OCTET STRING (CONTAINING RadioBearerConfig_SCG-Mod)
}
}
}
}
}

Table 8.2.2.4.2.3.3-4: RadioBearerConfig_SCG-Mod (Table 8.2.2.4.2.3.3-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod {	1 entry
DRB-ToAddMod[1] SEQUENCE {		entry 1
drb-Identity	DRBn	n set to the same DRB ID as in Table 8.2.2.4.2.3.3-1
pdcp-Config	PDCP-Config
}
}
}

Table 8.2.2.4.2.3.3-5: PDCP-Config (Table 8.2.2.4.2.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-99
Information Element	Value/remark	Comment	Condition
PDCP-Config ::= SEQUENCE {
drb SEQUENCE {
discardTimer	ms500	Other than default value.
}
}

Table 8.2.2.4.2.3.3-6: RRCReconfiguration (step 7, Table 8.2.2.4.2.3.2-1)

Derivation Path: TS 38.508 [4], Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-ReleaseAndAdd	true
}
}
radioBearerConfig2	OCTET STRING (CONTAINING RadioBearerConfig_SCG-Rel)
}
}
}
}
}

Table 8.2.2.4.2.3.3-7: RadioBearerConfig_SCG-Rel (Table 8.2.2.4.2.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToReleaseList	DRBn	n set to the same DRB ID as in Table 8.2.2.4.2.3.3-2
}

Table 8.2.2.4.2.3.3-8: RRCReconfigurationComplete (step 2, Table 8.2.2.4.2.3.2-1)

Derivation Path: TS 38.508 [4], Table 4.6.1-14 with condition NR-DC

8.2.2.4.3 PSCell addition, modification and release / SCG DRB / NE-DC

8.2.2.4.3.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCReconfiguration message to add an E-UTRA PSCell with SCG DRB }

then { UE configures the PSCell with SCG DRB and sends an RRCReconfigurationComplete message }

}

(2)

with { UE in NR RRC_CONNECTED state with NE-DC, and, MCG(s) (NR PDCP) and SCG }

ensure that {

when { UE receives an RRCReconfiguration message to modify SCG DRB }

then { UE reconfigures the SCG DRB and sends an RRCReconfigurationComplete message }

}

(3)

with { UE in NR RRC_CONNECTED state with NE-DC, and, MCG(s) (NR PDCP) and SCG }

ensure that {

when { UE receives an RRCReconfiguration message to release E-UTRA PSCell with SCG DRB }

then { UE releases the PSCell and SCG DRB and sends an RRCReconfigurationComplete message }

}

8.2.2.4.3.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 38.331, clauses 5.3.5.3, 5.3.5.5.1, 5.3.5.5.7, TS 36.331, clauses 5.3.5.3, 5.3.10.3d, 5.3.10.3e, 5.3.10.10. 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, or upon execution of the conditional reconfiguration (CHO or CPC):

…

1> if the RRCReconfiguration includes the secondaryCellGroup:

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

1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:

2> if the mrdc-SecondaryCellGroupConfig is set to setup:

3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:

4> perform MR-DC release as specified in clause 5.3.5.10;

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

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

3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG:

4> perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG;

2> else (mrdc-SecondaryCellGroupConfig is set to release):

3> perform MR-DC release as specified in clause 5.3.5.10;

1> if the RRCReconfiguration message includes the radioBearerConfig:

2> perform the radio bearer configuration according to 5.3.5.6;

1> if the RRCReconfiguration message includes the radioBearerConfig2:

2> perform the radio bearer configuration according to 5.3.5.6;

1> if the RRCReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

…

1> set the content of the RRCReconfigurationComplete message as follows:

…

2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG:

3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331 [10] clause 5.3.5.3;

…

[TS 38.331, clause 5.3.5.5.1]

The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331 [10], and for NE-DC, the SCG is configured as specified in TS 36.331 [10]. The network provides the configuration parameters for a cell group in the CellGroupConfig IE.

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 spCellConfigDedicated:

2> configure the SpCell in accordance with the spCellConfigDedicated;

2> consider the bandwidth part indicated in firstActiveUplinkBWP-Id if configured to be the active uplink bandwidth part;

2> consider the bandwidth part indicated in firstActiveDownlinkBWP-Id if configured to be the active downlink bandwidth part;

2> if any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received spCellConfigDedicated:

3> stop timer T310 for the corresponding SpCell, if running;

3> stop timer T312 for the corresponding SpCell, if running;

3> reset the counters N310 and N311.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the received RRCConnectionReconfiguration includes the sCellGroupToReleaseList:

2> perform SCell group release as specified in 5.3.10.3d;

1> if the received RRCConnectionReconfiguration includes the sCellGroupToAddModList:

2> perform SCell group addition or modification as specified in 5.3.10.3e;

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs configured with pdcp-Config and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

…

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:

3> include perCC-GapIndicationList and numFreqEffective;

2> if the frequencies are configured for reduced measurement performance:

3> include numFreqEffectiveReduced;

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

1> if the UE is configured with NE-DC:

2> if the received RRCConnectionReconfiguration message was included in an NR RRCResume message:

3> transfer the RRCConnectionReconfigurationComplete message via SRB1 embedded in NR RRC message RRCResumeComplete as specified in TS 38.331 [82], clause 5.3.13.4;

2> else:

3> transfer the RRCConnectionReconfigurationComplete message via SRB1 embedded in NR RRC message RRCReconfigurationComplete as specified in TS 38.331 [82], clause 5.3.5.3;

1> else:

2> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3d]

The UE shall:

1> if the release is triggered by reception of the sCellGroupToReleaseList:

2> for each sCellGroupIndex value included in the sCellGroupToReleaseList:

3> if the current UE configuration includes an SCell with value sCellGroupIndex:

4> consider the SCell not to be part of the SCell group indicated by sCellGroupIndex;

4> consider the sCellConfigCommon of the SCell group to be not applicable for the SCell;

3> release the SCell group;

1> if the release is triggered by RRC connection re-establishment:

2> release all SCell groups that are part of the current UE configuration;

[TS 36.331, clause 5.3.10.3e]

The UE shall:

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

2> for each sCellIndex value included in the sCellToReleaseList that is part of the SCell group indicated by sCellGroupIndex (SCell deletion from SCell group):

3> consider the sCellConfigCommon of the SCell group to be not applicable for the SCell;

3> consider the SCell not to be part of the SCell group indicated by sCellGroupIndex

2> for each sCellIndex value included in the sCellToAddModList that is not part of the SCell group indicated by sCellGroupIndex (SCell addition to SCell group):

3> consider the SCell to be part of the SCell group indicated by sCellGroupIndex;

3> apply the SCell configuration for parameters not already configured as part of the current SCell configuration in accordance with the sCellConfigCommon for the SCell group;

2> if sCellConfigCommon is included (modify the SCell group configuration):

3> for each SCell that is part of the current SCell group indicated by sCellGroupIndex:

4> apply the SCell configuration for parameters not already configured as part of the current SCell configuration in accordance with the sCellConfigCommon for the SCell group;

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

2> for each sCellIndex value included in the sCellToAddModList (SCell addition to the group):

3> consider the SCell to be part of the SCell group indicated by sCellGroupIndex

3> apply the SCell configuration for parameters not already configured as part of the current SCell configuration in accordance with the sCellConfigCommon for the SCell group;

[TS 36.331, clause 5.3.10.10]

The UE shall:

…

1> if scg-Configuration is received and is set to release or includes the mobilityControlInfoSCG (i.e. SCG release/ change):

2> if mobilityControlInfo is not received (i.e. SCG release/ change without HO):

3> reset SCG MAC, if configured;

3> if the UE is not configured with NE-DC:

4> for each drb-Identity value that is part of the current UE configuration:

5> if the DRB indicated by drb-Identity is an SCG DRB:

6> re-establish the PDCP entity and the SCG RLC entity or entities;

5> if the DRB indicated by drb-Identity is a split DRB:

6> perform PDCP data recovery and re-establish the SCG RLC entity;

5> if the DRB indicated by drb-Identity is an MCG DRB; and

5> drb-ToAddModListSCG is received and includes the drb-Identity value, while for this entry drb-Type is included and set to scg (i.e. MCG to SCG):

6> re-establish the PDCP entity and the MCG RLC entity or entities;

3> configure lower layers to consider the SCG SCell(s), except for the PSCell, to be in deactivated state;

1> if scg-Configuration is received and is set to release:

2> release the entire SCG configuration, except for the DRB configuration (i.e. as configured by drb-ToAddModListSCG);

2> if the current UE configuration includes one or more split or SCG DRBs and the received RRCConnectionReconfiguration message includes radioResourceConfigDedicated including drb-ToAddModList:

3> reconfigure the SCG or split DRB by drb-ToAddModList as specified in 5.3.10.12;

2> stop timer T313, if running;

2> stop timer T307, if running;

1> else:

2> if scg-ConfigPartMCG is received and includes the scg-Counter:

3> update the S-K_eNB key based on the K_eNB key and using the received scg-Counter value, as specified in TS 33.401 [32];

3> derive the K_UPenc key associated with the cipheringAlgorithmSCG included in mobilityControlInfoSCG within the received scg-ConfigPartSCG, as specified in TS 33.401 [32];

3> configure lower layers to apply the ciphering algorithm and the K_UPenc key;

2> if scg-ConfigPartSCG is received and includes the radioResourceConfigDedicatedSCG:

3> reconfigure the dedicated radio resource configuration for the SCG as specified in 5.3.10.11;

2> if the current UE configuration includes one or more split or SCG DRBs and the received RRCConnectionReconfiguration message includes radioResourceConfigDedicated including drb-ToAddModList:

3> reconfigure the SCG or split DRB by drb-ToAddModList as specified in 5.3.10.12;

2> if scg-ConfigPartSCG is received and includes measConfigSN:

3> for measConfigSN perform the actions as specified in 5.5.2 for measConfig unless explicitly stated otherwise;

2> if scg-ConfigPartSCG is received and includes the sCellToReleaseListSCG:

3> perform SCell release for the SCG as specified in 5.3.10.3a;

2> if scg-ConfigPartSCG is received and includes the pSCellToAddMod:

3> perform PSCell addition or modification as specified in 5.3.10.3c;

NOTE 0: This procedure is also used to release the PSCell e.g. PSCell change, SI change for the PSCell.

2> if scg-ConfigPartSCG is received and includes the sCellToAddModListSCG:

3> perform SCell addition or modification as specified in 5.3.10.3b;

2> configure lower layers in accordance with mobilityControlInfoSCG, if received;

2> if rach-SkipSCG is configured:

3> configure lower layers to apply the rach-SkipSCG for the target SCG, as specified in TS 36.213 [23] and TS 36.321 [6];

2> if scg-ConfigPartSCG is received and includes the mobilityControlInfoSCG (i.e. SCG change):

3> resume all SCG DRBs and resume SCG transmission for split DRBs, if suspended;

3> stop timer T313, if running;

3> start timer T307 with the timer value set to t307, as included in the mobilityControlInfoSCG, if makeBeforeBreakSCG is not configured;

3> start synchronising to the DL of the target PSCell;

3> initiate the random access procedure on the PSCell, as specified in TS 36.321 [6], if rach-SkipSCG is not configured:

NOTE 1: The UE is not required to determine the SFN of the target PSCell by acquiring system information from that cell before performing RACH access in the target PSCell.

3> the procedure ends, except that the following actions are performed when MAC successfully completes the random access procedure on the PSCell or when MAC indicates the successful reception of a PDCCH transmission addressed to C-RNTI and if rach-skipSCG is configured:

4> stop timer T307;

4> release rach-SkipSCG;

4> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PSCell, if any;

4> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PSCell (e.g. periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PSCell;

NOTE 2: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

8.2.2.4.3.3 Test description

8.2.2.4.3.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell and EUTRA Cell 1 is the PS Cell.

UE:

– None

Preamble:

– If pc_IP_Ping is set to TRUE then, the UE is in state NR RRC_CONNECTED using generic procedure parameter Connectivity (NR), according to TS 38.508-1 [4], clause 4.5.4.

8.2.2.4.3.3.2 Test procedure sequence

Table 8.2.2.4.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCReconfiguration message containing RRCConnectionReconfiguration message and a PDU SESSION MODIFICATION COMMAND to add E-UTRA PSCell with SCG DRB.	<–	NR RRC: RRCReconfiguration (RRCConnectionReconfiguration) 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMMAND	–	–
–	EXCEPTION: Depending upon UE implementation, steps 2 and 2A can occur in any order	–	–	–	–
2	Check: Does the UE transmit an RRCReconfigurationComplete message including eutra-SCG-Response?	–>	RRCReconfigurationComplete (RRCConnectionReconfigurationComplete)	1	P
2A	The UE transmits a ULInformationTransfer message and an PDU SESSION MODIFICATION COMPLETE message.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE	–	–
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 SCG DRB?	–	–	1	P
–	EXCEPTION: Steps 3Aa1 to 3Aa2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation.	–	–
3Aa1	IF pc_IP_Ping = FALSE, then, the SS transmits a CLOSE UE TEST LOOP message.	<–	CLOSE UE TEST LOOP
3Aa2	The UE transmits a CLOSE UE TEST LOOP COMPLETE message.	–>	CLOSE UE TEST LOOP COMPLETE
3B	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 SCG DRB?	–	–	1	P
4	SS transmits RRCReconfiguration message containing E-UTRA RadioBearerConfig to modify PDCP discardTimer value of SCG DRB.	<–	NR RRC: RRCReconfiguration	–	–
5	Check: Does the UE transmit an RRCReconfigurationComplete message?	–>	RRCReconfigurationComplete	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 SCG DRB?	–	–	2	P
7	SS transmits RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND to release E-UTRA PSCell and SCG DRB.	<–	NR RRC: RRCReconfiguration	–	–
–	EXCEPTION: Depending upon UE implementation, steps 8 and 9 can occur in any order	–	–	–	–
8	Check: Does the UE transmit an RRCReconfigurationComplete message?	–>	RRCReconfigurationComplete	3	P
9	The UE transmits a ULInformationTransfer message and an PDU SESSION MODIFICATION COMPLETE message.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE	–	–

8.2.2.4.3.3.3 Specific message contents

Table 8.2.2.4.3.3.3-1: RRCReconfiguration (step 1 , Table 8.2.2.4.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	Not present
secondaryCellGroup	Not present
measConfig	Not present
lateNonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {
masterCellGroup	Not present
fullConfig	Not present
dedicatedNAS-MessageList	Not present
masterKeyUpdate	Not present
dedicatedSIB1-Delivery	Not present
dedicatedSystemInformationDelivery	Not present
otherConfig	Not present
nonCriticalExtension SEQUENCE {
otherConfig-v1540	Not present
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-ReleaseAndAdd	Not present
mrdc-SecondaryCellGroup CHOICE {
eutra-SCG	RRCConnectionReconfiguration	OCTET STRING
}
}
}
radioBearerConfig2	RadioBearerConfig with condition DRBn and SecondaryKeys	OCTET STRING (CONTAINING RadioBearerConfig)
sk-Counter	SK-Counter
nonCriticalExtension	Not present
}
}
}
}
}
}

Table 8.2.2.4.3.3.3-2: RRCConnectionReconfiguration (Table 8.2.2.4.3.3.3-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
scg-Configuration-r12	SCG-Configuration-r12-NE-DC		Step 1
}
}
}
}
}
}
}
}
}

Table 8.2.2.4.3.3.3-3: SCG-Configuration-r12-NE-DC (Table 8.2.2.4.3.3.3-2)

Derivation Path: 36.508, Clause 4.6.3, Table 4.6.3-19G, condition NE-DC

Table 8.2.2.4.3.3.3-1A: PDU SESSION MODIFICATION COMMAND (step 1, Table 8.2.2.4.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.2-9.
Information Element	Value/remark	Comment	Condition
PDU session ID	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST associated with the Internet PDU session if available or with the first PDU session
Authorized QoS rules	One entry
QoS rule	Reference QoS rule #5 as defined in TS 38.508-1 [4], Table 4.8.2.1-5.	QFI=5
Authorized QoS flow descriptions	One entry
QoS flow	Reference QoS flow #5 as defined in TS 38.508-1 [4], Table 4.8.2.3-5.	QFI=5

Table 8.2.2.4.3.3.3-4: RRCReconfiguration (step4 , step7, Table 8.2.2.4.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
radioBearerConfig	Not Present
radioBearerConfig
secondaryCellGroup	Not present
measConfig	Not present
lateNonCriticalExtension	Not present
nonCriticalExtension	Not present		Step 4
nonCriticalExtension SEQUENCE {			Step 7
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
release			Step 7
}
radioBearerConfig2	OCTET STRING (CONTAINING RadioBearerConfig_SCG-Mod)	As specified in Table 8.2.2.4.3.3.3-5	Step 4
	OCTET STRING (CONTAINING RadioBearerConfig_SCG-Rel)	As specified in Table 8.2.2.4.3.3.3-6	Step 7
sk-Counter	Not present
nonCriticalExtension	Not present
}
}
}
}
}
}

Table 8.2.2.4.3.3.3-5: RadioBearerConfig_SCG-Mod (Table 8.2.2.4.3.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod {	1 entry
DRB-ToAddMod[1] SEQUENCE {		entry 1
drb-Identity	DRBn	n set to the same DRB ID as in Table 8.2.2.4.3.3.3-1
pdcp-Config SEQUENCE {
discardTimer	ms500	Other than default value.
}
}
}
}

Table 8.2.2.4.3.3.3-6: RadioBearerConfig_SCG-Rel (Table 8.2.2.4.3.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-132
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity {
DRB-Identity	DRBn	n set to the same DRB ID as in Table 8.2.2.4.3.3.3-1
}
}
}

Table 8.2.2.4.3.3.3-7: RRCReconfigurationComplete (step 3, Table 8.2.2.4.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-14 Condition with NE-DC

Table 8.2.2.4.3.3.3-8: PDU SESSION MODIFICATION COMMAND (step 7, Table 8.2.2.4.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.2-9.
Information Element	Value/remark	Comment	Condition
PDU session ID	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST associated with the Internet PDU session if available or with the first PDU session
Authorized QoS rules	One entry
QoS rule identifier	‘00000101’B	QFI=5
Rule operation code	‘010’B	Delete existing QoS rule
Authorized QoS flow descriptions
QoS flow descriptions
QFI	‘00000101’B	QFI=5
Operation code	‘010’B	Delete existing QoS flow

8.2.2.5 PSCell addition, modification and release / Split DRB

8.2.2.5.1 PSCell addition, modification and release / Split DRB / EN-DC

8.2.2.5.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to add PSCell with Split DRB }

then { UE configures the PSCell and sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and Split }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to modify Split DRB }

then { UE reconfigures the Split DRB and sends an RRCConnectionReconfigurationComplete message }

}

(3)

with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and Split }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to release PSCell with Split DRB }

then { UE releases the PSCell and Split DRB and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.5.1.2 Conformance requirements

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

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

…

1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or

1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:

2> perform EN-DC release as specified in TS 38.331 [82], clause 5.3.5.10;

1> if the received RRCConnectionReconfiguration includes the sk-Counter:

2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.7;

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

…

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:

3> include perCC-GapIndicationList and numFreqEffective;

2> if the frequencies are configured for reduced measurement performance:

3> include numFreqEffectiveReduced;

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82, 5.3.5.3];

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[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 fullConfig:

2> perform the radio configuration procedure as specified in 5.3.5.11;