8.2.5 Reconfiguration Failure / Radio link failure

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

8.2.5.1 Radio link failure / PSCell addition failure

8.2.5.1.1 Radio link failure / Random access problem / EN-DC

8.2.5.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 IP Packet to loopback on SCG DRB and the SS does not respond to the Scheduling Requests from UE }

then { UE encounters random access problem and initiates the NR SCG failure information procedure to report SCGFailureInformationNR with failure type randomAccessProblem }

}

8.2.5.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.6.13a.3, TS 38.331, clauses 5.3.10.3, 5.7.3.2, 5.7.3.3. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, clause 5.6.13a.3]

The UE shall set the contents of the SCGFailureInformationNR message as follows:

1> include failureType within failureReportSCG-NR and set it to indicate the SCG failure in accordance with TS 38.331 [82], clause 5.7.3.3;

…

The UE shall submit the SCGFailureInformationNR message to lower layers for transmission.

[TS 38.331, clause 5.3.10.3]

The UE shall:

…

1> upon random access problem indication from SCG MAC; or

…

3> consider radio link failure to be detected for the SCG i.e. SCG-RLF;

3> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure.

[TS 38.331, clause 5.7.3.2]

A UE initiates the procedure to report SCG failures when SCG transmission is not suspended and when one of the following conditions is met:

…

1> upon SCG configuration failure, in accordance with subclause 5.3.5.8.2;

…

Upon initiating the procedure, the UE shall:

1> suspend SCG transmission for all SRBs and DRBs;

1> reset SCG-MAC;

1> stop T304, if running;

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

2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10], clause 5.6.13a.

[TS 38.331, clause 5.7.3.3]

The UE shall set the SCG failure type as follows:

…

1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide random access problem indication from SCG MAC:

2> set the failureType as randomAccessProblem;

8.2.5.1.1.3 Test description

8.2.5.1.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) and Bearers (MCG(s) and SCG) established and Test Loop Function (On) with UE test loop mode B according to TS 38.508-1 [4], clause 4.5.4.

8.2.5.1.1.3.2 Test procedure sequence

Table 8.2.5.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS shall not respond to the Scheduling Requests for the IP Packet transmitted at next step (Note)	–	–	–	–
2	The SS transmits one IP Packet on SCG DRB	–	–	–	–
3	The SS shall not respond to the PRACH Preambles thereby simulating a random access problem.	–	–	–	–
4	Check: Does the UE transmit in the next 5 sec (arbitrary value) a SCGFailureInformationNR message with failureType set to ‘randomAccessProblem’?	–>	SCGFailureInformationNR	1	P
Note: The UE initiates random access procedure once SR number of attempts reach sr-transMax.

Table 8.2.5.1.1.3.2-2: Void

Table 8.2.5.1.1.3.2-3: Void

8.2.5.1.1.3.3 Specific message contents

Table 8.2.5.1.1.3.3-1: Void

Table 8.2.5.1.1.3.3-2: Void

Table 8.2.5.1.1.3.3-3: Void

Table 8.2.5.1.1.3.3-4: Void

Table 8.2.5.1.1.3.3-5: SCGFailureInformationNR (step 4, Table 8.2.5.1.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-18AA
Information Element	Value/remark	Comment	Condition
SCGFailureInformationNR-r15 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
scgFailureInformationNR-r15 SEQUENCE {
failureReportSCG-NR-r15 SEQUENCE {
failureType-r15	randomAccessProblem
measResultFreqListNR-r15	Not checked
measResultSCG-r15	Not checked
}
nonCriticalExtension SEQUENCE {}
}
}
}
}

8.2.5.1.2 Radio link failure / Random access problem / NR-DC

8.2.5.1.2.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE receives an IP Packet to loopback on SCG DRB and the SS stops transmitting Timing Advance Command and does not respond to the Scheduling Requests from UE }

then { UE encounters random access problem and initiates the SCG failure information procedure to report SCGFailureInformation with failure type randomAccessProblem }

}

8.2.5.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.7.3.2, 5.3.10.3, 5.7.3.3 and 5.7.3.5. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clauses 5.7.3.2]

A UE initiates the procedure to report SCG failures when neither MCG nor SCG transmission is suspended and when one of the following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with subclause 5.3.10.3;

…

Upon initiating the procedure, the UE shall:

1> suspend SCG transmission for all SRBs and DRBs;

1> reset SCG MAC;

1> stop T304 for the SCG, if running;

1> stop conditional reconfiguration evaluation for CPC, if configured;

1> if the UE is in (NG)EN-DC:

2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10], clause 5.6.13a.

1> else:

2> initiate transmission of the SCGFailureInformation message in accordance with 5.7.3.5.

[TS 38.331, clause 5.3.10.3]

The UE shall:

…

1> upon consistent uplink LBT failure indication from SCG MAC:

…

3> consider radio link failure to be detected for the SCG, i.e. SCG RLF;

3> if MCG transmission is not suspended:

4> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure.

[TS 38.331, clause 5.7.3.3]

The UE shall set the SCG failure type as follows:

1…

1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide random access problem indication from SCG MAC:

2> if the random access procedure was initiated for beam failure recovery:

3> set the failureType as other and set the failureType-v1610 as beamFailureRecoveryFailure;

2> else:

3> set the failureType as randomAccessProblem;

[TS 38.331, clause 5.7.3.5]

The UE shall set the contents of the SCGFailureInformation message as follows:

…

1> else if the UE initiates transmission of the SCGFailureInformation message to provide random access problem indication from SCG MAC:

2> if the random access procedure was initiated for beam failure recovery:

3> set the failureType as other and set the failureType-v1610 as beamFailureRecoveryFailure;

2> else:

3> set the failureType as randomAccessProblem;

8.2.5.1.2.3 Test description

8.2.5.1.2.3.1 Pre-test conditions

System Simulator:

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

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

UE:

– None.

Preamble:

– The UE is in state NR RRC_CONNECTED using generic procedure parameter Connectivity (NR-DC) according to TS 38.508-1 [4], Table 4.5.1-1, and with UE test loop mode B activated, as defined in TS 38.508-1 [4], subclause 4.4A.

8.2.5.1.2.3.2 Test procedure sequence

Table 8.2.5.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS shall not respond to the Scheduling Requests for the IP Packet transmitted at next step (Note)	–	–	–	–
2	The SS transmits one IP Packet on SCG DRB	–	–	–	–
3	The SS shall not respond to the PRACH Preambles thereby simulating a random access problem.	–	–	–	–
4	Check: Does the UE transmit in the next 5 sec (arbitrary value) a SCGFailureInformation message with failureType set to ‘randomAccessProblem’?	–>	SCGFailureInformation	1	P
Note: The UE initiates random access procedure once SR number of attempts reach sr-transMax.

8.2.5.1.2.3.3 Specific message contents

Table 8.2.5.1.2.3.3-1: SCGFailureInformation (step 4, Table 8.2.5.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-24A
Information Element		Value/remark	Comment	Condition
SCGFailureInformation ::= SEQUENCE {
criticalExtensions CHOICE {
scgFailureInformation SEQUENCE {
failureReportSCG		FailureReportSCG	Table 8.2.5.1.2.3.3-2
nonCriticalExtension		Not checked
}
}
}

Table 8.2.5.1.2.3.3-2: FailureReportSCG (Table 8.2.5.1.2.3.3-1)

Derivation Path: TS 38.331[4], clause 6.2.2
Information Element		Value/remark	Comment	Condition
FailureReportSCG ::= SEQUENCE {
failureType		randomAccessProblem
measResultFreqList		Not checked
measResultSCG-Failure		Not checked
}

8.2.5.2 Radio link failure / PSCell out of sync indication

8.2.5.2.1 Radio link failure / PSCell out of sync indication / EN-DC

8.2.5.2.1.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE receives N310 consecutive "out-of-sync" indications for the SpCell from lower layers due to radio link failure }

then { UE starts timer T310 for the corresponding SpCell, and, upon timer expiry initiates the NR SCG failure information procedure to report SCGFailureInformationNR with failure type set to ‘t310-Expiry’ }

}

8.2.5.2.1.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 36.331, clause 5.6.13a.3, TS 38.331, clauses 5.3.10.1, 5.3.10.3, 5.7.3.2, 5.7.3.3. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, clause 5.6.13a.3]

The UE shall set the contents of the SCGFailureInformationNR message as follows:

1> include failureType within failureReportSCG-NR and set it to indicate the SCG failure in accordance with TS 38.331 [82, 5.7.3.3];

…

The UE shall submit the SCGFailureInformationNR message to lower layers for transmission.

[TS 38.331, clause 5.3.10.1]

The UE shall:

1> upon receiving N310 consecutive "out-of-sync" indications for the SpCell from lower layers while T311 is not running:

2> start timer T310 for the corresponding SpCell.

[TS 38.331, clause 5.3.10.3]

The UE shall:

1> upon T310 expiry in PSCell; or

…

2> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure.

[TS 38.331, clause 5.7.3.2]

A UE initiates the procedure to report SCG failures when SCG transmission is not suspended and when one of the following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with subclause 5.3.10.3;

…

Upon initiating the procedure, the UE shall:

1> suspend SCG transmission for all SRBs and DRBs;

1> reset SCG-MAC;

1> stop T304, if running;

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

2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10, 5.6.13a].

[TS 38.331, clause 5.7.3.3]

The UE shall set the SCG failure type as follows:

1> if the UE initiates transmission of the SCGFailureInformationNR message due to T310 expiry:

2> set the failureType as t310-Expiry;

8.2.5.2.1.3 Test description

8.2.5.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) and DC Bearers (MCG(s) and SCG) on E-UTRA Cell 1 according to TS 38.508-1 [4], clause 4.5.4.

8.2.5.2.1.3.2 Test procedure sequence

Table 8.2.5.2.1.3.3-0A: RRCReconfiguration (Preamble)

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	OCTET STRING
}
}
}

Table 8.2.5.2.1.3.3-0B: CellGroupConfig (Table 8.2.5.2.1.3.3-0A: RRCReconfiguration)

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

Table 8.2.5.2.1.3.3-0E: RadioLinkMonitoringConfig (Table 8.2.5.2.1.3.3-0D: BWP-DownlinkDedicated)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-133
Information Element	Value/remark	Comment	Condition
RadioLinkMonitoringConfig ::= SEQUENCE {
failureDetectionResourcesToAddModList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS {	1 entry
RadioLinkMonitoringRS[1] SEQUENCE {		entry 1
radioLinkMonitoringRS-Id	0
purpose	rlf
detectionResource CHOICE {
ssb-Index	1
}
}
}
failureDetectionResourcesToReleaseList	Not present
beamFailureInstanceMaxCount	Not present
beamFailureDetectionTimer	Not present
}

Table 8.2.5.2.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes NR Cell 1 parameter to non-suitable “Off” in order to simulate radio link failure.	–	–	–	–
2	Void.	–	–	–	–
3	Check: Does the UE transmit in the next 5 sec (NOTE 1) a SCGFailureInformationNR message with failureType set to ‘t310-Expiry’?	–>	SCGFailureInformationNR	1	P
NOTE 1: The time of 5 sec is chosen arbitrary. When the UE will send the Failure report depends on (1) the values pre-set for N310 and T310 (see TS 38.508-1 [4], RLF-TimersAndConstants – set at the moment to ‘n1’ and ‘ms1000’ respectively), and, (2) the time it will take for the SS to complete step 1 and the UE to notice the change and perform internally all relevant to it actions. Because of the uncertainties associated with (2), and, the lower values used in typical network setting for (1), testing if the UE obeys the exact values of (1) is unreliable.

Table 8.2.5.2.1.3.3-3: ServingCellConfig (Table 8.2.5.2.1.3.3-0B: CellGroupConfig)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-167
Information Element	Value/remark	Comment	Condition
ServingCellConfig ::= SEQUENCE {
initialDownlinkBWP	BWP-DownlinkDedicated
}

Table 8.2.5.2.1.3.3-4: BWP-DownlinkDedicated (Table 8.2.5.2.1.3.3-0C: ServingCellConfig)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-11
Information Element	Value/remark	Comment	Condition
BWP-DownlinkDedicated ::= SEQUENCE {
radioLinkMonitoringConfig	RadioLinkMonitoringConfig
}

8.2.5.2.1.3.3 Specific message contents

Table 8.2.5.2.1.3.3-1: SCGFailureInformationNR (step 3, Table 8.2.5.2.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-18AA
Information Element	Value/remark	Comment	Condition
SCGFailureInformationNR-r15 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
scgFailureInformationNR-r15 SEQUENCE {
failureReportSCG-NR-r15 SEQUENCE {
failureType-r15	t310-Expiry
measResultFreqListNR-r15	Not checked
measResultSCG-r15	Not present
}
nonCriticalExtension SEQUENCE {}
}
}
}
}

8.2.5.2.2 Radio link failure / PSCell out of sync indication / NR-DC

8.2.5.2.2.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE detects out of sync on PSCell }

then { UE initiates the NR SCG failure information procedure to report SCGFailureInformation with failure type t310-Expiry }

}

8.2.5.2.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.3.10.3, 5.7.3.2, 5.7.3.4 and 5.7.3.5. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, 5.3.10.3]

The UE shall:

1> upon T310 expiry in PSCell; or

…

2> else:

3> consider radio link failure to be detected for the SCG, i.e. SCG RLF;

3> if MCG transmission is not suspended:

4> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure.

3> else:

4> if the UE is in NR-DC:

5> initiate the connection re-establishment procedure as specified in 5.3.7;

4> else (the UE is in (NG)EN-DC):

5> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7;

[TS 38.331, clause 5.7.3.2]

A UE initiates the procedure to report SCG failures when neither MCG nor SCG transmission is suspended and when one of the following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with subclause 5.3.10.3;

…

Upon initiating the procedure, the UE shall:

…

1> if the UE is in (NG)EN-DC:

2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10], clause 5.6.13a.

1> else:

2> initiate transmission of the SCGFailureInformation message in accordance with 5.7.3.5.

[TS 38.331, clause 5.7.3.4]

The UE shall set the contents of the MeasResultSCG-Failure as follows:

1> for each MeasObjectNR configured on NR SCG for which a measId is configured and measurement results are available:

2> include an entry in measResultPerMOList;

2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb:

3> set ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR;

2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs:

3> set refFreqCSI-RS to the value indicated by refFreqCSI-RS as included in the associated measurement object;

2> if a serving cell is associated with the MeasObjectNR:

3> set measResultServingCell to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14];

2> set the measResultNeighCellList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows;

3> ordering the cells with sorting as follows:

4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS;

4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR;

3> for each neighbour cell included:

4> include the optional fields that are available.

NOTE: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Blacklisted cells are not required to be reported.

2> if available, set the locationInfo as in 5.3.3.7.:

[TS 38.331, clause 5.7.3.5]

The UE shall set the contents of the SCGFailureInformation message as follows:

1> if the UE initiates transmission of the SCGFailureInformation message due to T310 expiry:

2> set the failureType as t310-Expiry;

…

1> include and set MeasResultSCG-Failure in accordance with 5.7.3.4;

8.2.5.2.2.3 Test description

8.2.5.2.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:

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

8.2.5.2.2.3.2 Test procedure sequence

Table 8.2.5.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes NR Cell 10 power level to non-suitable " Off" in order to simulate radio link failure.	–	–	–	–
2	Check: Does the UE transmit in the next 5 sec (NOTE 1) a SCGFailureInformation message with failureType set to "t310-Expiry"?	–>	SCGFailureInformation	1	P
NOTE 1: The time of 5 sec is chosen arbitrary. When the UE will send the Failure report depends on (1) the values pre-set for N310 and T310 (see TS 38.508-1 [4], RLF-TimersAndConstants – set at the moment to ‘n1’ and ‘ms1000’ respectively), and, (2) the time it will take for the SS to complete step 1 and the UE to notice the change and perform internally all relevant to it actions. Because of the uncertainties associated with (2), and, the lower values used in typical network setting for (1), testing if the UE obeys the exact values of (1) is unreliable.

8.2.5.2.2.3.3 Specific message contents

Table 8.2.5.2.2.3.3-1: RRCSetup(Preamble)

Derivation Path: TS 38.508-1 [4] table 4.6.1-21
Information Element	Value/remark	Comment	Condition
RRCSetup ::= SEQUENCE {
criticalExtensions CHOICE {
rrcSetup SEQUENCE {
masterCellGroup	CellGroupConfig with condition SRB1	OCTET STRING (CONTAINING CellGroupConfig)
}
}
}

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

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
rlf-TimersAndConstants SEQUENCE {
t311	ms10000
}
spCellConfigDedicated	ServingCellConfig
}

Table 8.2.5.2.2.3.3-3: ServingCellConfig (Table 8.2.5.2.2.3.3-2: CellGroupConfig)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-167
Information Element	Value/remark	Comment	Condition
ServingCellConfig ::= SEQUENCE {
initialDownlinkBWP	BWP-DownlinkDedicated
}

Table 8.2.5.2.2.3.3-4: BWP-DownlinkDedicated (Table 8.2.5.2.2.3.3-3: ServingCellConfig)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-11
Information Element	Value/remark	Comment	Condition
BWP-DownlinkDedicated ::= SEQUENCE {
radioLinkMonitoringConfig	RadioLinkMonitoringConfig
}

Table 8.2.5.2.2.3.3-5: RadioLinkMonitoringConfig (Table 8.2.5.2.2.3.3-4: BWP-DownlinkDedicated)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-133
Information Element	Value/remark	Comment	Condition
RadioLinkMonitoringConfig ::= SEQUENCE {
failureDetectionResourcesToAddModList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS {	1 entry
RadioLinkMonitoringRS[1] SEQUENCE {		entry 1
radioLinkMonitoringRS-Id	0
purpose	rlf
detectionResource CHOICE {
ssb-Index	SSB Index#n	SSB Index of NR Cell 10
}
}
}
failureDetectionResourcesToReleaseList	Not present
beamFailureInstanceMaxCount	Not present
beamFailureDetectionTimer	Not present
}

Table 8.2.5.2.2.3.3-6: SCGFailureInformation (step 2, Table 8.2.5.2.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-24A
Information Element		Value/remark	Comment	Condition
SCGFailureInformation ::= SEQUENCE {
criticalExtensions CHOICE {
scgFailureInformation SEQUENCE {
FailureReportSCG SEQUENCE {
failureType		t310-Expiry
measResultFreqList		Not checked
measResultSCG-Failure		Not present
}
nonCriticalExtension		Not checked
}
}
}

8.2.5.3 Radio link failure / rlc-MaxNumRetx failure

8.2.5.3.1 Radio link failure / rlc-MaxNumRetx failure / EN-DC

8.2.5.3.1.1 Test Purpose (TP)

(1)

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

ensure that {

when { the transmitting side of the UE’s AM RLC entity for the SCG DRB has retransmitted an RLC SDU until RETX_COUNT = maxRetxThreshold }

then { the UE shall transmit a SCGFailureInformationNR message with failureType set to ‘rlc-MaxNumRetx’ }

}

8.2.5.3.1.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 38.322, clause 5.3.2, TS 36.331, clause 5.6.13a.3, TS 38.331, clauses 5.3.10.3, 5.7.3.2, 5.7.3.3. Unless otherwise stated these are Rel-15 requirements.

[TS 38.322, clause 5.3.2]

When an RLC SDU or an RLC SDU segment is considered for retransmission, the transmitting side of the AM RLC entity shall:

– if the RLC SDU or RLC SDU segment is considered for retransmission for the first time:

– set the RETX_COUNT associated with the RLC SDU to zero.

– else, if it (the RLC SDU or the RLC SDU segment that is considered for retransmission) is not pending for retransmission already and the RETX_COUNT associated with the RLC SDU has not been incremented due to another negative acknowledgment in the same STATUS PDU:

– increment the RETX_COUNT.

– if RETX_COUNT = maxRetxThreshold:

– indicate to upper layers that max retransmission has been reached.

…

[TS 36.331, clause 5.6.13a.3]

The UE shall set the contents of the SCGFailureInformationNR message as follows:

1> include failureType within failureReportSCG-NR and set it to indicate the SCG failure in accordance with TS 38.331 []82clause , 5.7.3.3;

…

The UE shall submit the SCGFailureInformationNR message to lower layers for transmission.

[TS 38.331, clause 5.3.10.3]

The UE shall:

…

1> upon indication from SCG RLC that the maximum number of retransmissions has been reached:

2> if CA duplication is configured and activated; and for the corresponding logical channel allowedServingCells only includes SCell(s):

3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.

2> else:

3> consider radio link failure to be detected for the SCG i.e. SCG-RLF;

3> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure.

…

else3> consider radio link failure to be detected for the SCG i.e. SCG-RLF;

[TS 38.331, clause 5.7.3.2]

A UE initiates the procedure to report SCG failures when SCG transmission is not suspended and when one of the following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with subclause 5.3.10.3;

1> upon reconfiguration with sync failure of the SCG, in accordance with subclause 5.3.5.8.3;

1> upon SCG configuration failure, in accordance with subclause 5.3.5.8.2;

1> upon integrity check failure indication from SCG lower layers concerning SRB3.

Upon initiating the procedure, the UE shall:

1> suspend SCG transmission for all SRBs and DRBs;

1> reset SCG MAC;

1> stop T304 for the SCG, if running;

1> if the UE is in (NG)EN-DC:

2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10], clause 5.6.13a.

1> else:

2> initiate transmission of the SCGFailureInformation message in accordance with 5.7.3.5.

[TS 38.331, clause 5.7.3.3]

The UE shall set the SCG failure type as follows:

1> if the UE initiates transmission of the SCGFailureInformationNR message due to T310 expiry:

2> set the failureType as t310-Expiry;

1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide reconfiguration with sync failure information for an SCG:

2> set the failureType as synchReconfigFailure-SCG;

1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide random access problem indication from SCG MAC:

2> set the failureType as randomAccessProblem;1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide indication from SCG RLC that the maximum number of retransmissions has been reached:

2> set the failureType as rlc-MaxNumRetx;

1> else if the UE initiates transmission of the SCGFailureInformationNR message due to SRB3 integrity check failure:

2> set the failureType as srb3-IntegrityFailure;

1> else if the UE initiates transmission of the SCGFailureInformationNR message due to Reconfiguration failure of NR RRC reconfiguration message:

2> set the failureType as scg-reconfigFailure.

8.2.5.3.1.3 Test description

8.2.5.3.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 and Test Loop Function (On) with UE test loop mode A (message condition UE TEST LOOP MODE A to return one UL PDCP SDU per DL PDCP SDU) according to TS 38.508-1 [4] the exception that ciphering algorithm ‘nea0 (NULL)’ is configured.

– The RLC Acknowledged Mode is enabled

8.2.5.3.1.3.2 Test procedure sequence

Table 8.2.5.3.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits AMD PDU#1 containing a complete RLC SDU#1 (on the SCG bearer).	<–	AMD PDU#1	–	–
1A	Void	–	–	–	–
1B	The UE transmits one AMD PDU#1 containing a complete RLC SDU#1 (on the SCG bearer).	–>	AMD PDU#1 (SN=0)	–	–
–	EXCEPTION: Steps 1C-3 are repeated maxRetxThreshold times NOTE: maxRetxThreshold is configured by RLC-Config.	–	–	–	–
1C	The SS transmits an RLC STATUS PDU. ACK_SN =1 and NACK_SN =0.	<–	STATUS PDU	–	–
2	Void	–	–	–	–
3	The UE transmits one AMD PDU#1 containing a complete RLC SDU#1 (on the SCG bearer).	–>	AMD PDU#1 (SN=0)	–	–
3A	The SS transmits an RLC STATUS PDU. ACK_SN =1 and NACK_SN =0.	<–	STATUS PDU	–	–
4	Check: Does the UE transmit in the next 5 sec (arbitrary value) a SCGFailureInformationNR message with failureType set to ‘rlc-MaxNumRetx’?	–>	SCGFailureInformationNR	1	P

8.2.5.3.1.3.3 Specific message contents

Table 8.2.5.3.1.3.3-1: SCGFailureInformationNR (step 4, Table 8.2.5.3.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-18AA
Information Element	Value/remark	Comment	Condition
SCGFailureInformationNR-r15 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
scgFailureInformationNR-r15 SEQUENCE {
failureReportSCG-NR-r15 SEQUENCE {
failureType-r15	rlc-MaxNumRetx
measResultFreqListNR-r15	Not checked
measResultSCG-r15	Not checked
}
nonCriticalExtension SEQUENCE {}
}
}
}
}

8.2.5.3.2 Radio link failure / rlc-MaxNumRetx failure / NR-DC

8.2.5.3.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with NR-DC }

ensure that {

when { the transmitting side of the UE’s AM RLC entity for the SCG DRB has retransmitted an RLC SDU until RETX_COUNT = maxRetxThreshold }

then { the UE shall transmit a SCGFailureInformation message with failureType set to ‘rlc-MaxNumRetx’ }

}

8.2.5.3.2.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 38.322, clause 5.3.2, TS 38.331, clauses 5.3.10.3, 5.7.3.2, 5.7.3.5. Unless otherwise stated these are Rel-15 requirements.

[TS 38.322, clause 5.3.2]

When an RLC SDU or an RLC SDU segment is considered for retransmission, the transmitting side of the AM RLC entity shall:

– if the RLC SDU or RLC SDU segment is considered for retransmission for the first time:

– set the RETX_COUNT associated with the RLC SDU to zero.

– else, if it (the RLC SDU or the RLC SDU segment that is considered for retransmission) is not pending for retransmission already and the RETX_COUNT associated with the RLC SDU has not been incremented due to another negative acknowledgment in the same STATUS PDU:

– increment the RETX_COUNT.

– if RETX_COUNT = maxRetxThreshold:

– indicate to upper layers that max retransmission has been reached.

…

[TS 38.331, clause 5.3.10.3]

The UE shall:

…

1> upon indication from SCG RLC that the maximum number of retransmissions has been reached; or

1> if connected as an IAB-node, upon BH RLF indication received on BAP entity from the SCG; or

1> upon consistent uplink LBT failure indication from SCG MAC:

2> if the indication is from SCG RLC and CA duplication is configured and activated for SCG, and for the corresponding logical channel allowedServingCells only includes SCell(s):

3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.

2> else:

3> consider radio link failure to be detected for the SCG, i.e. SCG RLF;

3> if MCG transmission is not suspended:

4> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure.

[TS 38.331, clause 5.7.3.2]

A UE initiates the procedure to report SCG failures when neither MCG nor SCG transmission is suspended and when one of the following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with subclause 5.3.10.3;

…

Upon initiating the procedure, the UE shall:

1> suspend SCG transmission for all SRBs, DRBs and, if any, BH RLC channels;

1> reset SCG MAC;

1> stop T304 for the SCG, if running;

1> stop conditional reconfiguration evaluation for CPC, if configured;

1> if the UE is in (NG)EN-DC:

2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10], clause 5.6.13a.

1> else:

2> initiate transmission of the SCGFailureInformation message in accordance with 5.7.3.5.

[TS 38.331, clause 5.7.3.5]

The UE shall set the contents of the SCGFailureInformation message as follows:

…

1> else if the UE initiates transmission of the SCGFailureInformation message to provide indication from SCG RLC that the maximum number of retransmissions has been reached:

2> set the failureType as rlc-MaxNumRetx;

…

The UE shall submit the SCGFailureInformation message to lower layers for transmission.

8.2.5.3.2.3 Test description

8.2.5.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-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cell 1.

UE:

– None.

Preamble:

– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (NR-DC) with DC bearer(MCG and SCG), and Test Loop Function (On) with UE test loop mode A according to TS 38.508-1 [4], Table 4.5.1-1 with the exception that ciphering algorithm ‘nea0 (NULL)’ is configured.

8.2.5.3.2.3.2 Test procedure sequence

Table 8.2.5.3.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits AMD PDU#1 on the DRB associated with SCG	<–	AMD PDU#1	–	–
2	The UE transmits one AMD PDU#1	–>	AMD PDU#1 (SN=0)	–	–
–	EXCEPTION: Steps 3-4 are repeated maxRetxThreshold times	–	–	–	–
3	The SS transmits an RLC STATUS PDU. ACK_SN =1 and NACK_SN =0.	<–	STATUS PDU	–	–
4	The UE transmits one AMD PDU#1	–>	AMD PDU#1 (SN=0)	–	–
5	The SS transmits an RLC STATUS PDU. ACK_SN =1 and NACK_SN =0.	<–	STATUS PDU	–	–
6	Check: Does the UE transmit in the next 5 sec (arbitrary value) a SCGFailureInformation message with failureType set to ‘rlc-MaxNumRetx’?	–>	SCGFailureInformation	1	P

8.2.5.3.2.3.3 Specific message contents

Table 8.2.5.3.2.3.3-1: SCGFailureInformation (step 6, Table 8.2.5.3.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-24A
Information Element		Value/remark	Comment	Condition
SCGFailureInformation ::= SEQUENCE {
criticalExtensions CHOICE {
scgFailureInformation SEQUENCE {
FailureReportSCG SEQUENCE {
failureType		rlc-MaxNumRetx
measResultFreqList		Not checked
measResultSCG-Failure		Not present
}
nonCriticalExtension		Not checked
}
}
}

8.2.5.3.3 Radio link failure / rlc-MaxNumRetx failure / NE-DC

8.2.5.3.3.1 Test Purpose (TP)

(1)

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

ensure that {

when { the transmitting side of the UE’s AM RLC entity for the SCG DRB has retransmitted an RLC SDU until RETX_COUNT = maxRetxThreshold }

then { the UE shall transmit a SCGFailureInformationEUTRA message with failureType set to ‘rlc-MaxNumRetx’ }

}

8.2.5.3.3.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 36.331, clause 5.6.13.4, TS 38.331, clauses 5.7.3a. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.7.3a]

A UE initiates the procedure to report EUTRA SCG failures when neither NR MCG nor EUTRA SCG transmission is suspended and in accordance with TS 36.331 [10] clause 5.6.13.2. Actions the UE shall perform upon initiating the procedure, other than related to the transmission of the SCGFailureInformationEUTRA message are specified in TS 36.331 [10] clause 5.6.13.2

The UE shall set the contents of the SCGFailureInformationEUTRA message as follows:

1> include failureType within failureReportSCG-EUTRA and set it to indicate the SCG failure in accordance with TS 36.331 [10] clause 5.6.13.4;

…

The UE shall submit the SCGFailureInformationEUTRA message to lower layers for transmission.

[TS 36.331, clause 5.6.13.2]

A UE initiates the procedure to report SCG failures when neither MCG nor SCG transmission is suspended and when one of the following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with 5.3.11; or

1. upon SCG change failure, in accordance with 5.3.5.7a; or

…

In case of DC, upon initiating the procedure, the UE shall:

…

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

2> initiate transmission of the SCGFailureInformationEUTRA message via the NR MCG as specified in TS 38.331 [82], clause 5.7.3a;

…

[TS 36.331, clause 5.6.13.4]

The UE shall:

…

1> else if SCG failure is due to indication from SCG RLC that the maximum number of retransmissions was reached:

2> consider the failureType to be rlc-MaxNumRetx;

…

8.2.5.3.3.3 Test description

8.2.5.3.3.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell and E-URTRA Cell 1 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:

– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (NE-DC) with DC bearer(MCG and SCG), and Test Loop Function (On) with UE test loop mode A according to TS 38.508-1 [4], Table 4.5.1-1 with the exception that ciphering algorithm ‘nea0 (NULL)’ is configured.

8.2.5.3.3.3.2 Test procedure sequence

Table 8.2.5.3.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits AMD PDU#1 on the DRB associated with SCG	<–	AMD PDU#1	–	–
2	The UE transmits one AMD PDU#1	–>	AMD PDU#1 (SN=0)	–	–
–	EXCEPTION: Steps 3-4 are repeated maxRetxThreshold times	–	–	–	–
3	The SS transmits an RLC STATUS PDU. ACK_SN =1 and NACK_SN =0.	<–	STATUS PDU	–	–
4	The UE transmits one AMD PDU#1	–>	AMD PDU#1 (SN=0)	–	–
5	The SS transmits an RLC STATUS PDU. ACK_SN =1 and NACK_SN =0.	<–	STATUS PDU	–	–
6	Check: Does the UE transmit in the next 5 sec (arbitrary value) a SCGFailureInformationEUTRA message with failureType set to ‘rlc-MaxNumRetx’?	–>	SCGFailureInformationEUTRA	1	P

8.2.5.3.3.3.3 Specific message contents

Table 8.2.5.3.3.3.3-1: SCGFailureInformationEUTRA (step 6, Table 8.2.5.3.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-24B
Information Element		Value/remark	Comment	Condition
SCGFailureInformationEUTRA ::= SEQUENCE {
criticalExtensions CHOICE {
scgFailureInformationEUTRA SEQUENCE {
FailureReportSCG-EUTRA SEQUENCE {
failureType		rlc-MaxNumRetx
measResultFreqListMRDC		Not checked
measResultSCG-FailureMRDC		Not present
}
nonCriticalExtension		Not checked
}
}
}

8.2.5.4 Reconfiguration failure / SCG change failure

8.2.5.4.1 Reconfiguration failure / SCG change failure / EN-DC

8.2.5.4.1.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE receives an RRCConnectionReconfiguration message with nr-Config IE containing NR RRCReconfiguration message with reconfigurationWithSync for configured PSCell and if T304 of a secondary cell group expires }

then { UE initiates the NR SCG failure information procedure to report SCGFailureInformationNR with failure type set to ‘synchReconfigFailure-SCG’ }

}

8.2.5.4.1.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 36.331, clause 5.6.13a.3, TS 38.331, clauses 5.3.5.3, 5.3.5.5.1, 5.3.5.5.2, 5.3.5.8.3, 5.7.3.2 and 5.7.3.3. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, clause 5.6.13a.3]

The UE shall set the contents of the SCGFailureInformationNR message as follows:

1> include failureType within failureReportSCG-NR and set it to indicate the SCG failure in accordance with TS 38.331 [82, 5.7.3.3];

…

The UE shall submit the SCGFailureInformationNR message to lower layers for transmission.

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

…

[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). For EN-DC, the MCG 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 with reconfigurationWithSync:

2> perform Reconfiguration with sync according to 5.3.5.5.2;

[TS 38.331, clause 5.3.5.5.2]

The UE shall perform the following actions to execute a reconfiguration with sync.

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

1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;

[TS 38.331, clause 5.3.5.8.3]

The UE shall:

1> else if T304 of a secondary cell group expires:

2> release dedicated preambles provided in rach-ConfigDedicated, if configured;

2> initiate the SCG failure information procedure as specified in subclause 5.7.3 to report SCG reconfiguration with sync failure, upon which the RRC reconfiguration procedure ends.

[TS 38.331, clause 5.7.3.2]

A UE initiates the procedure to report SCG failures when SCG transmission is not suspended and when one of the following conditions is met:

…

1> upon reconfiguration with sync failure of the SCG, in accordance with subclause 5.3.5.8.3;

…

Upon initiating the procedure, the UE shall:

1> suspend SCG transmission for all SRBs and DRBs;

1> reset SCG-MAC;

1> stop T304, if running;

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

2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10], clause 5.6.13a.

[TS 38.331, clause 5.7.3.3]

The UE shall set the SCG failure type as follows:

…

1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide reconfiguration with sync failure information for an SCG:

2> set the failureType as synchReconfigFailure-SCG;

8.2.5.4.1.3 Test description

8.2.5.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:

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

8.2.5.4.1.3.2 Test procedure sequence

Table 8.2.5.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 perform SCG change with reconfigurationWithSync with the same PSCell.	<–	RRCConnectionReconfiguration (RRCReconfiguration)	–	–
–	EXCEPTION: In parallel to the event described in step 2 the event described in Table 8.2.5.4.1.3.2-2 takes place.	–	–	–	–
2	Wait for t304 ms to ensure that T304 expires (the value is defined in CellGroupConfig). NOTE: SS does not respond to the UE transmitted RACH preambles on NR Cell 1	–	–	–	–
3	Check: Does the UE transmit on PCell (E-UTRA Cell 1) in the next 5 sec (arbitrary value) a SCGFailureInformationNR message with failureType set to ‘synchReconfigFailure-SCG‘?	–>	SCGFailureInformationNR	1	P

Table 8.2.5.4.1.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits an RRCConnectionReconfigurationComplete message containing NR RRCReconfigurationComplete message on E-UTRA Cell 1.	–>	RRCConnectionReconfigurationComplete (RRCReconfigurationComplete)	–	–

8.2.5.4.1.3.3 Specific message contents

Table 8.2.5.4.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.5.4.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-8, with condition EN-DC_EmbedNR_RRCRecon

Table 8.2.5.4.1.3.3-1A: RRCReconfiguration (Table 8.2.5.4.1.3.3-1)

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

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

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition EN-DC
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
spCellConfig SEQUENCE {
reconfigurationWithSync SEQUENCE {
spCellConfigCommon	ServingCellConfigCommon
}
}
}

Table 8.2.5.4.1.3.3-1C: ServingCellConfigCommon (Table 8.2.5.4.1.3.3-1B)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-168
Information Element	Value/remark	Comment	Condition
ServingCellConfigCommon ::= SEQUENCE {
uplinkConfigCommon SEQUENCE {
initialUplinkBWP	BWP-UplinkCommon
}
}

Table 8.2.5.4.1.3.3-1D: BWP-UplinkCommon (Table 8.2.5.4.1.3.3-1C)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-14
Information Element	Value/remark	Comment	Condition
BWP-UplinkCommon ::= SEQUENCE {
rach-ConfigCommon CHOICE {
setup	RACH-ConfigCommon
}
}

Table 8.2.5.4.1.3.3-1E: RACH-ConfigCommon (Table 8.2.5.4.1.3.3-1D)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-128
Information Element	Value/remark	Comment	Condition
RACH-ConfigCommon::= SEQUENCE {
rach-ConfigGeneric	RACH-ConfigGeneric
}

Table 8.2.5.4.1.3.3-1F: RACH-ConfigGeneric (Table 8.2.5.4.1.3.3-1E)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-130
Information Element	Value/remark	Comment	Condition
RACH-ConfigGeneric ::= SEQUENCE {
preambleTransMax	n200
}

Table 8.2.5.4.1.3.3-2: SCGFailureInformationNR (step 3, Table 8.2.5.4.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-18AA
Information Element	Value/remark	Comment	Condition
SCGFailureInformationNR-r15 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
scgFailureInformationNR-r15 SEQUENCE {
failureReportSCG-NR-r15 SEQUENCE {
failureType-r15	synchReconfigFailure-SCG
measResultFreqListNR-r15	Not checked
measResultSCG-r15	Not checked
}
nonCriticalExtension SEQUENCE {}
}
}
}
}

8.2.5.4.2 Reconfiguration failure / SCG change failure / NR-DC

8.2.5.4.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with NR-DC }

ensure that {

when { UE receives an RRCReconfiguration message with reconfigurationWithSync for configured PSCell and if T304 of a secondary cell group expires }

then { UE initiates the SCG failure information procedure to report SCGFailureInformation with failure type set to ‘synchReconfigFailure-SCG’ }

}

8.2.5.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.5.1, 5.3.5.5.2, 5.3.5.8.3, 5.3.10.3, 5.7.3.2, 5.7.3.5. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.5.5.1]

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

1> if the CellGroupConfig contains the spCellConfig with reconfigurationWithSync:

2> perform Reconfiguration with sync according to 5.3.5.5.2;

[TS 38.331, clause 5.3.5.5.2]

The UE shall perform the following actions to execute a reconfiguration with sync.

…

1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;

[TS 38.331, clause 5.3.5.8.3]

The UE shall:

…

1> else if T304 of a secondary cell group expires:

2> if MCG transmission is not suspended:

3> release dedicated preambles provided in rach-ConfigDedicated, if configured;

3> initiate the SCG failure information procedure as specified in subclause 5.7.3 to report SCG reconfiguration with sync failure, upon which the RRC reconfiguration procedure ends;

[TS 38.331, clause 5.7.3.2]

A UE initiates the procedure to report SCG failures when neither MCG nor SCG transmission is suspended and when one of the following conditions is met:

1> upon reconfiguration with sync failure of the SCG, in accordance with subclause 5.3.5.8.3;

…

Upon initiating the procedure, the UE shall:

1> suspend SCG transmission for all SRBs, DRBs and, if any, BH RLC channels;

1> reset SCG MAC;

1> stop T304 for the SCG, if running;

1> stop conditional reconfiguration evaluation for CPC, if configured;

1> if the UE is in (NG)EN-DC:

2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10], clause 5.6.13a.

1> else:

2> initiate transmission of the SCGFailureInformation message in accordance with 5.7.3.5.

[TS 38.331, clause 5.7.3.5]

The UE shall set the contents of the SCGFailureInformation message as follows:

…

1> else if the UE initiates transmission of the SCGFailureInformation message to provide reconfiguration with sync failure information for an SCG:

2> set the failureType as synchReconfigFailure-SCG;

…

The UE shall submit the SCGFailureInformation message to lower layers for transmission.

8.2.5.4.2.3 Test description

8.2.5.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:

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

8.2.5.4.2.3.2 Test procedure sequence

Table 8.2.5.4.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCReconfiguration message to perform SCG change with reconfigurationWithSync with the same PSCell.	<–	RRCReconfiguration	–	–
–	EXCEPTION: In parallel to the event described in step 2 the event described in Table 8.2.5.4.2.3.2-2 takes place.	–	–	–	–
2	Wait for t304 ms to ensure that T304 expires (the value is defined in CellGroupConfig). NOTE: SS does not respond to the UE transmitted RACH preambles on NR Cell 10	–	–	–	–
3	Check: Does the UE transmit on PCell (NR Cell 1) in the next 5 sec (arbitrary value) a SCGFailureInformation message with failureType set to ‘synchReconfigFailure-SCG‘?	–>	SCGFailureInformation	1	P

Table 8.2.5.4.2.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits an RRCReconfigurationComplete message on NR Cell 1.	–>	RRCReconfigurationComplete	–	–

8.2.5.4.2.3.3 Specific message contents

Table 8.2.5.4.2.3.3-1: RRCReconfiguration (Table 8.2.5.4.2.3.2-1, Step 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 {
nonCriticalExtension SEQUENCE {
masterCellGroup	Not present
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-SecondaryCellGroup CHOICE {
nr-SCG	OCTET STRING (CONTAINING RRCReconfiguration specified in Table 8.2.5.4.2.3.3-2)
}
}
}
}
}
}
}
}
}

Table 8.2.5.4.2.3.3-2: RRCReconfiguration (Table 8.2.5.4.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 {
rrc-TransactionIdentifier
criticalExtensions CHOICE {
rrcReconfiguration SEQUENCE {
secondaryCellGroup	CellGroupConfig
}
}
}

Table 8.2.5.4.2.3.3-3: CellGroupConfig (Table 8.2.5.4.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 {
spCellConfig SEQUENCE {
reconfigurationWithSync SEQUENCE {
spCellConfigCommon	ServingCellConfigCommon
newUE-Identity	RNTI-Value with condition NR-DC_SCG
t304	ms1000
rach-ConfigDedicated	Not present
}
}
}

Table 8.2.5.4.2.3.3-4: ServingCellConfigCommon (Table 8.2.5.4.2.3.3-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-168
Information Element	Value/remark	Comment	Condition
ServingCellConfigCommon ::= SEQUENCE {
uplinkConfigCommon SEQUENCE {
initialUplinkBWP	BWP-UplinkCommon
}
}

Table 8.2.5.4.2.3.3-5: BWP-UplinkCommon (Table 8.2.5.4.2.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-14
Information Element	Value/remark	Comment	Condition
BWP-UplinkCommon ::= SEQUENCE {
rach-ConfigCommon CHOICE {
setup	RACH-ConfigCommon
}
}

Table 8.2.5.4.2.3.3-6: RACH-ConfigCommon (Table 8.2.5.4.2.3.3-5)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-128
Information Element	Value/remark	Comment	Condition
RACH-ConfigCommon::= SEQUENCE {
rach-ConfigGeneric	RACH-ConfigGeneric
}

Table 8.2.5.4.2.3.3-7: RACH-ConfigGeneric (Table 8.2.5.4.2.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-130
Information Element	Value/remark	Comment	Condition
RACH-ConfigGeneric ::= SEQUENCE {
preambleTransMax	n200
}

Table 8.2.5.4.2.3.3-8: SCGFailureInformation (step 3, Table 8.2.5.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-24A
Information Element		Value/remark	Comment	Condition
SCGFailureInformation ::= SEQUENCE {
criticalExtensions CHOICE {
scgFailureInformation SEQUENCE {
FailureReportSCG SEQUENCE {
failureType		synchReconfigFailure-SCG
measResultFreqList		Not checked
measResultSCG-Failure		Not present
}
nonCriticalExtension		Not checked
}
}
}

8.2.5.5 Reconfiguration failure / SCG Reconfiguration failure / SRB3

Note: Core specs requirements cannot be simulated and verified as conformance test.

8.2.5.5.1 Void

8.2.5.6 Reconfiguration failure / SCG Reconfiguration failure / SRB1

Note: Core specs requirements cannot be simulated and verified as conformance test.

8.2.5.6.1 Void