13.3 Connection re-establishment

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

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

13.3.1 Intra-system connection re-establishment

13.3.1.1 Intra-system connection re-establishment / Radio link recovery while T310 is running

13.3.1.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and has data to transmit}

ensure that {

when { UE detects radio link recovery while T310 is running}

then { UE resumes the RRC connection without explicit signalling and continues data transfer}

}

13.3.1.1.2 Conformance requirements

Refer to TS 36.523-1 clause 8.5.1.5.2.

13.3.1.1.3 Test description

13.3.1.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The condition SRB2-DRB(1,0) is used for step 8 in 4.5.3A.3 according to [18].

– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.

13.3.1.1.3.2 Test procedure sequence

Table 13.3.1.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 13.3.1.1.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Remark
T0	RS EPRE	dBm/15kHz	P_default	Power level from 36.508 clause 6.2.2.1. P_defaultas serving cell.
T1	RS EPRE	dBm/15kHz	P_off	P_off as non-suitable “Off” cell.
T2	RS EPRE	dBm/15kHz	P_default	P_defaultas serving cell.

Table 13.3.1.1.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message	–	–
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
2	100 ms after step 1 the SS reduce DL RS TX power level of Cell 1 from “T0” to “T1” in table 13.3.1.1.3.2-1. Note: 100 ms delay after step 1 is to ensure that UE has time to transmit STATUS PDU for data received in step 1	–	–	–	–
3	The SS waits for 1.5s. T310 is 2s.	–	–	–	–
4	The SS recovers DL RS TX power level of Cell 1 from “T1” to “T2” in table 13.3.1.1.3.2-1.	–	–	–	–
5	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 1?( Note 1)	–>	IP packet	1	P
Note 1: Triggered when timer T_delay_modeB (IP PDU delay time) expires and pending uplink data exist in buffered PDCP SDUs according to [25] clause 5.4.4.3.

13.3.1.1.3.3 Specific message contents

Table 13.3.1.1.3.3-1: ACTIVATE TEST MODE (preamble, Table 13.3.1.1.3.2-2)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE B

Table 13.3.1.1.3.3-2: CLOSE UE TEST LOOP (preamble, Table 13.3.1.1.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	0 0 0 0 0 1 0 1	5 seconds

Table 13.3.1.1.3.3-3: SystemInformationBlockType2 (preamble and all steps, Table 13.3.1.1.3.2-2)

Derivation path: 36.508 table 4.4.3.3-1
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ue-TimersAndConstants {
t310	ms2000
}
}

Table 13.3.1.1.3.3-4: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1 [18], step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

13.3.1.2 Intra-system connection re-establishment / Re-establishment of a new connection when further data is to be transferred

13.3.1.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detects radio link failure on expiry of timer T310 }

then { UE starts timer T311 and UE initiates the RRC Connection re-establishment procedure }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detects radio link failure and successfully completes the RRC Connection re-establishment procedure and has data available for transmission }

then { UE use the DRB configured by network side and resume the data transfer }

}

13.3.1.2.2 Conformance requirements

Refer to TS 36.523-1 clause 8.5.1.1.2.

13.3.1.2.3 Test description

13.3.1.2.3.1 Pre-test conditions

System Simulator:

– 2 cells on same E-UTRA frequency:

– Cell 1 (default parameters) serving cell

– Cell 2 intra-frequency cell

UE:

None.

Preamble:

– The condition SRB2-DRB(1,0) is used for step 8 in 4.5.3A.3 according to [18].

– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.

13.3.1.2.3.2 Test procedure sequence

Table 13.3.1.2.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message	–	–
0	Void	–	–	–	–
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
2	100 ms after step 1 the SS changes the power level of cell 1 to non-suitable “Off” and changes the power level of cell 2 to suitable according to TS 36.508 subclause 6.2.2.1 in order that the radio link quality of Cell 1 is degraded. Note: 100 ms delay after step 1 is to ensure that UE has time to transmit STATUS PDU for data received in step 1	–	–	–	–
3	Check: Does the UE initiate an RRC connection re-establishment procedure and transmit an RRCConnectionReestablishmentRequest message on Cell 2?	–>	RRCConnectionReestablishmentRequest	1	P
4	The SS transmits RRCConnectionReestablishment message	<–	RRCConnectionReestablishment	–	–
5	UE transmits an RRCConnectionReestablishmentComplete message	–>	RRCConnectionReestablishmentComplete	–	–
6	The SS transmits RRCConnectionReconfiguration message	<–	RRCConnectionReconfiguration	–	–
–	EXCEPTION : the steps 7 and 8 can happen in any order	–	–	–	–
7	UE transmits an RRCConnectionConfigurationComplete message	–>	RRCConnectionReconfigurationComplete	–	–
8	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 2?	–>	IP packet	2	P

13.3.1.2.3.3 Specific message contents

Table 13.3.1.2.3.3-0: ACTIVATE TEST MODE (preamble, Table 13.3.1.2.3.2-2)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE B

Table 13.3.1.2.3.3-0A: CLOSE UE TEST LOOP (preamble, Table 13.3.1.2.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	00000101	5 seconds

Table 13.3.1.2.3.3-1: SchedulingRequest-Configuration (RRCConnectionReconfiguration, preamble : Table 4.5.3.3-1 [18], step 8)

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration ::= CHOICE {
setup SEQUENCE {
dsr-TransMax	n64	Max value allowed
}
}

Table 13.3.1.2.3.3-2: RRCConnectionReestablishmentRequest (step 3, Table 13.3.1.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCConnectionReestablishmentRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionReestablishmentRequest-r8 SEQUENCE {
ue-Identity SEQUENCE {
c-RNTI	the value of the C-RNTI of the UE
physCellId	PhysicalCellIdentity of Cell 1
shortMAC-I	The same value as the 16 least significant bits of the XMAC-I value calculated by SS
}
reestablishmentCause	otherFailure
}
}
}

Table 13.3.1.2.3.3-3: RRCConnectionReconfiguration (step 6, Table 13.3.1.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated	RadioResourceConfigDedicated-HO
}
}
}
}

13.3.1.3 RRC connection reconfiguration / Full configuration / DRB establishment

13.3.1.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and has data to transmit }

ensure that {
when { UE detects radio link failure and successfully completed the RRC Connection re-establishment procedure and receives an RRCConnectionReconfiguration message including fullConfig-r9 }

then { UE release and re-setup DRB and resume data transfer }

}

13.3.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.3 and 5.3.5.8.

[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 this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

2> re-establish PDCP for SRB2 and for all DRBs that are established, if any;

2> re-establish RLC for SRB2 and for all DRBs that are established, if any;

2> if the RRCConnectionReconfiguration message includes the fullConfig:

3> perform the radio configuration procedure as specified in section 5.3.5.8;

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

2> resume SRB2 and all DRBs that are suspended, if any;

NOTE 1: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> else:

…

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

[TS 36.331, clause 5.3.5.8]

The UE shall:

1> release/ clear all current dedicated radio configurations except the C-RNTI, the security configuration and the PDCP, RLC and logical channel configurations for the RBs;

NOTE 2: Radio configuration is not just the resource configuration but includes other configurations like MeasConfig and OtherConfig.

1> if the RRCConnectionReconfiguration message includes the mobilityControlInfo:

2> release/ clear all current common radio configurations;

2> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;

1> else:

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

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration):

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

2> apply the corresponding default RLC configuration for the SRB specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for SRB2;

2> apply the corresponding default logical channel configuration for the SRB as specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for SRB2;

NOTE 3: This is to get the SRBs (SRB1 and SRB2 for handover and SRB2 for reconfiguration after reestablishment) to a known state from which the reconfiguration message can do further configuration.

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

2> release the PDCP entity;

2> release the RLC entity or entities;

2> release the DTCH logical channel;

2> release the drb-identity;

NOTE 4: This will retain the eps-bearerIdentity but remove the DRBs including drb-identity of these bearers from the current UE configuration and trigger the setup of the DRBs within the AS in Section 5.3.10.3 using the new configuration. The eps-bearerIdentity acts as the anchor for associating the released and re-setup DRB.

1> for each eps-BearerIdentity value that is part of the current UE configuration but not part of the drb-ToAddModList:

2> perform DRB release as specified in 5.3.10.2;

13.3.1.3.3 Test description

13.3.1.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2.

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

– The condition SRB2-DRB(1, 0) is used for step 8 in 4.5.3A.3 on Cell 1 according to [18].

– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.

13.3.1.3.3.2 Test procedure sequence

Table 13.3.1.3.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 2
T1	Cell-specific RS EPRE	dBm/15kHz	“Off”	-85
Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 13.3.1.3.3.2-2: Main behaviour

St	Procedure		Message Sequence		TP	Verdict
			U – S	Message
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–		IP packet	–	–
2	The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 13.3.1.3.3.2-1 in order that the radio link quality of Cell 1 is degraded and Cell 2 is suitable for camping.	–		–	–	–
3	The UE send RRCConnectionReestablishmentRequest message on Cell 2.	–>		RRCConnectionReestablishmentRequest	–	–
4	The SS transmits RRCConnectionReestablishment message.	<–		RRCConnectionReestablishment	–	–
5	The UE transmits RRCConnectionReestablishmentComplete message.	–>		RRCConnectionReestablishmentComplete	–	–
6	The SS transmits an RRCConnectionReconfiguration message to perform full configuration option to Cell 2.		<–	RRCConnectionReconfiguration	–	–
7	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2?		–>	RRCConnectionReconfigurationComplete	–	–
8	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 2?		–>	IP packet	1	P

13.3.1.3.3.3 Specific message contents

Table 13.3.1.3.3.3-1: ACTIVATE TEST MODE (preamble, Table 13.3.1.3.3.2-2)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE B

Table 13.3.1.3.3.3-2: CLOSE UE TEST LOOP (preamble, Table 13.3.1.3.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	00000101	5 seconds

Table 13.3.1.3.3.3-3: RRCConnectionReestablishmentRequest (step 3, Table 13.3.1.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-13
Information Element	Value/remark	Comment	Condition
RRCConnectionReestablishmentRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionReestablishmentRequest-r8 SEQUENCE {
ue-Identity SEQUENCE {
c-RNTI	the value of the C-RNTI of the UE
physCellId	PhysicalCellIdentity of Cell 1
shortMAC-I	The same value as the 16 least significant bits of the XMAC-I value calculated by SS
}
reestablishmentCause	otherFailure
}
}
}

Table 13.3.1.3.3.3-4: RRCConnectionReconfiguration (step 6, Table 13.3.1.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated	RadioResourceConfigDedicated-RECONFIG
nonCriticalExtension SEQUENCE {
lateNonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {
otherConfig-r9	Not present
fullConfig-r9	true
nonCriticalExtension SEQUENCE {}	Not present
}
}
}
}
}
}

Table 13.3.1.3.3.3-5: RadioResourceConfigDedicated-RECONFIG (Table 13.3.1.3.3.3-4)

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated ::= SEQUENCE {
srb-ToAddModList	SRB-ToAddModList-DEFAULT	TS 36.508 Table 4.8.2.1.1-1
drb-ToAddModList	DRB-ToAddModList-DEFAULT (1) using condition AM	TS 36.508 Table 4.8.2.1.7-1
drb-ToReleaseList	Not present
mac-MainConfig CHOICE {
explicitValue	MAC-MainConfig-DEFAULT
}
sps-Config	Not present
physicalConfigDedicated	PhysicalConfigDedicated-DEFAULT		SRB1
	PhysicalConfigDedicated-epdcch-r11		(CEmodeA OR CEmodeB)
}

Table 13.3.1.3.3.3-6: MAC-MainConfig-DEFAULT (Table 13.3.1.3.3.3-5)

Derivation Path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfig ::= SEQUENCE {
ul-SCH-Config SEQUENCE {
periodicBSR-Timer	infinity
retxBSR-Timer	sf2560
}
drx-Config	Not present
phr-Config CHOICE {
release	NULL
}
sr-ProhibitTimer-r9	0
}

Table 13.3.1.3.3.3-7: PhysicalConfigDedicated-epdcch-r11 (Table 13.3.1.3.3.3-5)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with condition SRB1 AND (CE Mode A or CE Mode B)
Information Element		Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
pdsch-ConfigDedicated		PDSCH-ConfigDedicated-DEFAULT
pusch-ConfigDedicated		PUSCH-ConfigDedicated-DEFAULT
uplinkPowerControlDedicated		UplinkPowerControlDedicated-DEFAULT
epdcch-Config-r11	EPDCCH-Config-r11-DEFAULT
pucch-ConfigDedicated-r13	PUCCH-ConfigDedicated- r13-DEFAULT
ce-Mode-r13 CHOICE {
Setup	ce-ModeA			CEmodeA
Setup	ce-ModeB			CEmodeB
}
}

13.3.2 Inter-system connection re-establishment

13.3.2.1 Inter-system connection re-establishment / E-UTRAN to UTRAN / Further data are to be transferred

13.3.2.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detects radio link failure }

then { UE successfully selects the available strongest UTRAN cell and further data is transfered in the target cell}

}

13.3.2.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331 clause 5.3.7.2, TS 36.304, clause 4.1.

[TS 36.331 clause 5.3.7.2]

The UE shall only initiate the procedure when AS security has been activated. The UE initiates the procedure when one of the following conditions is met:

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

1> upon handover failure, in accordance with 5.3.5.6; or

1> upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or

1> upon integrity check failure indication from lower layers; or

1> upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5;

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> start timer T311;

1> suspend all RBs except SRB0;

1> reset MAC;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

perform cell selection in accordance with the cell selection process as specified in TS 36.304 [4];

[TS 36.331, clause 5.3.7.3]

Upon selecting an inter-RAT cell, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’;

[TS 36.331, clause 5.3.12]

Upon leaving RRC_CONNECTED, the UE shall:

1> reset MAC;

1> stop all timers that are running except T320 and T330;

1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established RBs;

1> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:

2> enter RRC_IDLE and perform procedures as specified in TS 36.304 [4, 5.2.7];

[TS 36.304, clause 4.1]

With the cell selection, the UE searches for a suitable cell of the selected PLMN and chooses that cell to provide available services, further the UE shall tune to its control channel. This choosing is known as "camping on the cell".

13.3.2.1.3 Test description

13.3.2.1.3.1 Pre-test conditions

System Simulator:

– 2 cells :

– Cell 1 (default parameters) E-UTRAN serving cell

– Cell 5 UTRAN cell

– System information combination 4 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B with T_delay_modeB timer set according to PIXIT parameter px_TestLoopModeB_Delay.

13.3.2.1.3.2 Test procedure sequence

Table 13.3.2.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
2	The SS changes the power level of cell 1 to non-suitable “Off” and changes the power level of cell 5 to suitable according to TS 36.508 subclause 6.2.2.1 in order that the radio link quality of Cell 1 is degraded.	–	–	–	–
3	Check: does the test result in generic test procedure in TS 36.508 subclause 6.4.2.8 indicate that the UE is camped on UTRAN Cell 5? NOTE: The UE performs a RAU procedure and the RRC connection is released.			1	P
4	The UE transmits a RRC CONNECTION REQUEST on Cell 5.	–>	RRC CONNECTION REQUEST	–	–
5	The SS transmits a RRC CONNECTION SETUP on Cell 5.	<–	RRC CONNECTION SETUP	–	–
6	The UE transmits a RRC CONNECTION SETUP COMPLETE message on Cell 5.	–>	RRC CONNECTION SETUP COMPLETE	–	–
7	The UE transmits a SERVICE REQUEST message on Cell 5.	–>	SERVICE REQUEST	–	–
8	void
9	void
10	The SS transmits a SECURITY MODE COMMAND message on Cell 5.	<–	SECURITY MODE COMMAND	–	–
11	The UE transmits a SECURITY MODE COMPLETE message on Cell 5.	–>	SECURITY MODE COMPLETE	–	–
12	void
13	The SS transmits a RADIO BEARER SETUP message on Cell 5.	<–	RADIO BEARER SETUP	–	–
14	The UE transmits a RADIO BEARER SETUP COMPLETE message on Cell 5.	–>	RADIO BEARER SETUP COMPLETE	–	–
15	Void
16	Void
17	Check: UE loops back the IP packet on Cell 5?	–>	IP packet	1	P

13.3.2.1.3.3 Specific message contents

Table 13.3.2.1.3.3-1: ACTIVATE TEST MODE –>preamble)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	Set according to PIXIT parameter px_TestLoopModeB_Delay

13.3.2.2 Inter-system connection re-establishment / E-UTRAN to GPRS / Further data are to be transferred

13.3.2.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detects radio link failure }

then { UE successfully selects the available strongest GERAN cell and further data is transfered in the target cell}

}

13.3.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331 clause 5.3.7.2, TS 36.304, clause 4.1.

[TS 36.331 clause 5.3.7.2]

The UE shall only initiate the procedure when AS security has been activated. The UE initiates the procedure when one of the following conditions is met:

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

1> upon handover failure, in accordance with 5.3.5.6; or

1> upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or

1> upon integrity check failure indication from lower layers; or

1> upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5;

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> start timer T311;

1> suspend all RBs except SRB0;

1> reset MAC;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

perform cell selection in accordance with the cell selection process as specified in TS 36.304 [4];

[TS 36.331, clause 5.3.7.3]

Upon selecting an inter-RAT cell, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’;

[TS 36.331, clause 5.3.12]

Upon leaving RRC_CONNECTED, the UE shall:

1> reset MAC;

1> stop all timers that are running except T320 and T330;

1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established RBs;

1> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:

2> enter RRC_IDLE and perform procedures as specified in TS 36.304 [4, 5.2.7];

[TS 36.304, clause 4.1]

13.3.2.2.3 Test description

13.3.2.2.3.1 Pre-test conditions

System Simulator:

– 2 cells:

– Cell 1 (default parameters) E-UTRAN serving cell

– Cell 24 GERAN cell

– System information combination 5 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B with T_delay_modeB timer set according to PIXIT parameter px_TestLoopModeB_Delay.

13.3.2.2.3.2 Test procedure sequence

Table 13.3.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
2	The SS changes the power level of cell 1 to non-suitable “Off” and changes the power level of cell 24 to suitable according to TS 36.508 subclause 6.2.2.1	–	–	–	–
3	Check: does the test result in generic test procedure in TS 36.508 subclause 6.4.2.9 indicate that the UE is camped on GERAN Cell 24?	–	–	1	P
4-14	The UE performs RAU steps 1-11 according to TS36.508 subclause 6.4.2.9
15	Check: Does the UE loop back the IP packet on Cell 24?	–>	IP packet	1	P

13.3.2.2.3.3 Specific message contents

Table 13.3.2.2.3.3-1: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	Set according to PIXIT parameter px_TestLoopModeB_Delay

Table 13.3.2.2.3.3-2: ROUTING AREA UPDATE REQUEST (step 6, Table 13.3.2.2.3.2-1)

Derivation Path: Derivation path: 36.508 table 4.7B.2-1
Information Element	Value/remark	Comment	Condition
PDP context status	The SM state of the PDP context established on the NSAPI used in the E-UTRA data transfer shall be indicated as not PDP-INACTIVE	The UE indicates that the default bearer context is still active.

Table 13.3.2.2.3.3-3: ROUTING AREA UPDATE ACCEPT (step 12, Table 13.3.2.2.3.2-1)

Derivation Path: Derivation path: 36.508 table 4.7B.2-2
Information Element	Value/remark	Comment	Condition
PDP context status	The SM state of the PDP context established on the NSAPI used in the E-UTRA data transfer shall be indicated as not PDP-INACTIVE	The network confirms that the default bearer context is still active.