13.4.3 Inter-system mobility voice

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

13.4.3.0 General

Unless stated otherwise in a test case, for all test cases in this clause, the UE shall contain either ISIM and USIM applications or only a USIM application on UICC.

13.4.3.1 Inter-system mobility / E-UTRA voice to UTRA CS voice / SRVCC

13.4.3.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and an IMS voice call is ongoing and an UTRA Speech RAB combination is configured for an UTRA cell}

then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the utra cell}

}

13.4.3.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3, TS 23.216, clause 6.2.2.1 and clause 6.2.2.1A.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover‘:

2> if the targetRAT-Type is set to ‘utra‘ or ‘geran‘:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 23.216, clause 6.2.2.1]

Depicted in figure 6.2.2.1-1 is a call flow for SRVCC from E-UTRAN to GERAN without DTM support. The flow requires that eNB can determine that the target is GERAN without DTM support or that the UE is without DTM support.

Figure 6.2.2.1-1: SRVCC from E-UTRAN to GERAN without DTM support

1. UE sends measurement reports to E-UTRAN.

2. Based on UE measurement reports the source E‑UTRAN decides to trigger an SRVCC handover to GERAN.

3. Source E‑UTRAN sends Handover Required (Target ID, generic Source to Target Transparent Container, SRVCC HO Indication) message to the source MME. The E‑UTRAN places the "old BSS to new BSS information IE" for the CS domain in the generic Source to Target Transparent Container. The SRVCC HO indication indicates to the MME that target is only CS capable, hence this is a SRVCC handover operation only towards the CS domain. The message includes an indication that the UE is not available for the PS service in the target cell.

4. Based on the QCI associated with the voice bearer (QCI 1) and the SRVCC HO indication, the source MME splits the voice bearer from the non voice bearers and initiates the PS-CS handover procedure for the voice bearer only towards MSC Server.

5. The MME sends a SRVCC PS to CS Request (IMSI, Target ID, STN-SR, C‑MSISDN, generic Source to Target Transparent Container, MM Context, Emergency Indication) message to the MSC Server. The Emergency Indication and the equipment identifier are is included if the ongoing session is emergency session. Authenticated IMSI and C‑MSISDN shall also be included, if available. The MME received STN-SR and C‑MSISDN from the HSS as part of the subscription profile downloaded during the E‑UTRAN attach procedure. The MM Context contains security related information. CS security key is derived by the MME from the E‑UTRAN/EPS domain key as defined in TS 33.401 [22]. The CS Security key is sent in the MM Context.

6. The MSC Server interworks the PS-CS handover request with a CS inter‑MSC handover request by sending a Prepare Handover Request message to the target MSC. The MSC Server assigns a default SAI as Source ID on the interface to the target BSS and uses BSSMAP encapsulated for the Prepare Handover Request.

NOTE 1: The value of the default SAI is configured in the MSC and allows a release 8 and later BSC to identify that the source for the SRVCC Handover is E-UTRAN. To ensure correct statistics in the target BSS the default SAI should be different from the SAIs used in UTRAN.

7. Target MSC performs resource allocation with the target BSS by exchanging Handover Request/ Acknowledge messages.

8. Target MSC sends a Prepare Handover Response message to the MSC Server.

9. Establishment of circuit connection between the target MSC and the MGW associated with the MSC Server e.g. using ISUP IAM and ACM messages.

10. For non-emergency session, the MSC Server initiates the Session Transfer by using the STN-SR e.g. by sending an ISUP IAM (STN-SR) message towards the IMS. For emergency session, the MSC Server initiates the Session Transfer by using the locally configured E-STN-SR and by including the equipment identifier. Standard IMS Service Continuity or Emergency IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.237 [14].

NOTE 2: This step can be started after step 8.

NOTE 3: If the MSC Server is using an ISUP interface, then the initiation of the session transfer for non-emergency session may fail if the subscriber profile including CAMEL triggers is not available prior handover (see clause 7.3.2.1.3 in TS 23.292 [13]).

11. During the execution of the Session Transfer procedure the remote end is updated with the SDP of the CS access leg. The downlink flow of VoIP packets is switched towards the CS access leg at this point.

12. Source IMS access leg is released as per TS 23.237 [14].

NOTE 4: Steps 11 and 12 are independent of step 13.

13. MSC Server sends a SRVCC PS to CS Response (Target to Source Transparent Container) message to the source MME.

14. Source MME sends a Handover Command (Target to Source Transparent Container) message to the source E-UTRAN. The message includes information about the voice component only.

15. Source E-UTRAN sends a Handover from E-UTRAN Command message to the UE.

16. UE tunes to GERAN.

17. Handover Detection at the target BSS occurs. The UE sends a Handover Complete message via the target BSS to the target MSC. If the target MSC is not the MSC Server, then the Target MSC sends an SES (Handover Complete) message to the MSC Server.

18. The UE starts the Suspend procedure specified in TS 23.060 [10], clause 16.2.1.1.2. The TLLI and RAI pair are derived from the GUTI as described in TS 23.003 [27]. This triggers the Target SGSN to send a Suspend Notification message to the Source MME. The MME returns a Suspend Acknowledge to the Target SGSN.

NOTE 5: The MME might not be able to derive the GUTI from the received P-TMSI and RAI pair and therefore it might not be able to identify which UE context is associated with the Suspend Notification message. Also in this case the bearers are deactivated and/or suspended as in step 22a.

19. Target BSS sends a Handover Complete message to the target MSC.

20. Target MSC sends an SES (Handover Complete) message to the MSC Server. The speech circuit is through connected in the MSC Server/MGW according to TS 23.009 [18].

21. Completion of the establishment procedure with ISUP Answer message to the MSC Server according to TS 23.009 [18].

22. MSC Server sends a SRVCC PS to CS Complete Notification message to the source MME, informing it that the UE has arrived on the target side. Source MME acknowledges the information by sending a SRVCC PS to CS Complete Acknowledge message to the MSC Server.

22a. The MME deactivates bearers used for voice and other GBR bearers. All GBR bearers are deactivated towards S-GW and P-GW by initiating MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401 [2]. The MME does not send deactivation request toward the eNodeB on receiving PS-to-CS Complete Notification in step 22. PS-to-CS handover indicator is notified to P-GW for voice bearer during the bearer deactivation procedure. For GTP-based S5/S8, the S-GW requests the P-GW to delete all GBR bearer contexts by sending a Delete Bearer Command message. If dynamic PCC is deployed, the P‑GW may interact with PCRF as defined in TS 23.203 [31]. For PMIP-based S5/S8, S-GW interacts with the PCRF which in turn updates PCC rules for GBR traffic in the P-GW.

The MME starts preservation and suspension of non-GBR bearers by sending Suspend Notification message towards S-GW. For these non-GBR bearers, the S-GW releases S1-U bearers for the UE and sends Suspend Notification message to the P-GW(s). The MME stores in the UE context that UE is in suspended status. All the preserved non-GBR bearers are marked as suspended status in the S-GW and P-GW. The P-GW should discard packets if received for the suspended UE.

23a. If the HLR is to be updated, i.e. if the IMSI is authenticated but unknown in the VLR, the MSC Server performs a TMSI reallocation towards the UE using its own non-broadcast LAI and, if the MSC Server and other MSC/VLRs serve the same (target) LAI, with its own Network Resource Identifier (NRI).

NOTE 5: The TMSI reallocation is performed by the MSC Server towards the UE via target MSC.

23b. If the MSC Server performed a TMSI reallocation in step 23a, and if this TMSI reallocation was completed successfully, the MSC Server performs a MAP Update Location to the HSS/HLR.

NOTE 6: This Update Location is not initiated by the UE.

24. For an emergency services session after handover is complete, the source MME or the MSC Server may send a Subscriber Location Report carrying the identity of the MSC Server to a GMLC associated with the source or target side, respectively, as defined in TS 23.271 [29] to support location continuity.

NOTE 7: Any configuration of the choice between a source MME versus MSC Server update to a GMLC needs to ensure that a single update occurs from one of these entities when the control plane location solution is used on the source and/or target sides.

After the CS voice call is terminated and if the UE is still in GERAN (or for any other reason specified in TS 24.008), then the UE shall resume PS services as specified in TS 23.060 [10]. A Gn SGSN will follow TS 23.060 [10] to resume the PDP Context(s). An S4 SGSN will follow TS 23.060 [10] to resume the bearers, and will in addition inform S-GW and P-GW(s) to resume the suspended bearers. If the UE has returned to E-UTRAN after the CS voice call was terminated, then the UE shall resume PS service by sending TAU to MME. The MME will in addition inform S-GW and P-GW(s) to resume the suspended bearers. Resuming the suspended bearers in the S-GW and in the P-GW should be done by implicit resume using the Modify Bearer request message if it is triggered by the procedure in operation, e.g. RAU, TAU or Service Request. The S-GW is aware of the suspend state of the bearers and will forward the Modify Bearer request to the P-GW. Explicit resume using the Resume Notification message should be used in cases when Modify Bearer Request is not triggered by the procedure in operation.

[TS 23.216, clause 6.2.2.1A]

The call flow for this scenario is similar to the call flow depicted in figure 6.2.2.1‑1, with the exceptions that the Suspend procedure (step 18 and step 22a in figure 6.2.2.1-1) is not performed and that the MME only deactivates bearers used for voice (step 22a in figure 6.2.2.1-1) and sets the PS-to-CS handover indicator. The scenario requires that eNB can determine that the target is either GERAN with DTM but without DTM HO support and that the UE is supporting DTM or that the target is UTRAN (HSPA) without PS HO support. The message in step 3 in figure 6.2.2.1-1 includes an indication to the MME that the UE is available for PS service in the target cell. Furthermore, if the target is GERAN, the E‑UTRAN places in the generic Source to Target Transparent Container the "old BSS to new BSS information IE", while if the target is UTRAN, the generic Source to Target Transparent container is encoded according to the Source RNC to Target RNC Transparent Container IE definition. At the end of the procedure described in figure 6.2.2.1‑1, the remaining PS resources are re-established when the UE performs the Routeing Area update procedure. Triggers for performing Routeing Area update procedure are described in TS 23.060 [10]. The target SGSN may deactivate the PDP contexts that cannot be established as described in TS 23.060 [10].

13.4.3.1.3 Test description

13.4.3.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 5.

– 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 Registered, Idle mode (state 2) on Cell 1 according to [18].

13.4.3.1.3.2 Test procedure sequence

Table 13.4.3.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 after preamble, 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.4.3.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 5

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

The power level values are such that entering conditions for event B2 are not satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-88

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-88

T1

Cell-specific RS EPRE

dBm/15kHz

-84

The power level values are such that entering conditions for event B2 are satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

T2

Cell-specific RS EPRE

dBm/15kHz

Non-suitable “Off”

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

Table 13.4.3.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures UTRA cell 5 to reference configuration according 36.508 table 4.8.3-1, condition UTRA Speech.

2-25

Steps 1 to 24 of the generic test procedure for IMS MT speech call (TS 36.508 4.5A.7.3-1).

26-27

Void

28

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter RAT measurement and reporting for event B2.

<–

RRCConnectionReconfiguration

29

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

30

The SS changes the power level for Cell 1 and Cell 5 according to the row "T1" in table 13.4.3.1.3.2-1

31

The UE transmits a MeasurementReport message on Cell 1 to report event B2 for Cell 5.

–>

MeasurementReport

31A

The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for E-UTRA and UTRA.

<–

UECapabilityEnquiry

31B

The UE transmits a UECapabilityInformation message on Cell 1.

NOTE: The start-CS values received, should be used to configure ciphering on cell 5.

–>

UECapabilityInformation

32

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

33

Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message on cell 5?

–>

HANDOVER TO UTRAN COMPLETE

1

P

EXCEPTION: In parallel to the events described in step 34 to 39 the steps specified in table 13.4.3.1.3.2-5 takes place.

34

The SS transmits a SECURITY MODE COMMAND message for the CS domain.

<–

SECURITY MODE COMMAND

35

The UE transmits a SECURITY MODE COMPLETE message.

–>

SECURITY MODE COMPLETE

36

The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.

<–

UTRAN MOBILITY INFORMATION

37

The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.

–>

UTRAN MOBILITY INFORMATION CONFIRM

38

The SS transmits a TMSI REALLOCATION COMMAND message.

<–

TMSI REALLOCATION COMMAND

39

The UE transmits a TMSI REALLOCATION COMPLETE message.

–>

TMSI REALLOCATION COMPLETE

40

SS adjusts cell levels according to row T2 of table 13.4.3.1.3.2-1.

The UE is in end state UTRA CS call (U5).

Table 13.4.3.1.3.2-3: Void

Table 13.4.3.1.3.2-4: Void

Table 13.4.3.1.3.2-5: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE transmit a ROUTING AREA UPDATE REQUEST message?

–>

ROUTING AREA UPDATE REQUEST

P

1A

The SS transmits a SECURITY MODE COMMAND message for the PS domain.

<–

SECURITY MODE COMMAND

1B

The UE transmits a SECURITY MODE COMPLETE message.

–>

SECURITY MODE COMPLETE

2

The SS transmits a ROUTING AREA UPDATE ACCEPT message.

<–

ROUTING AREA UPDATE ACCEPT

3

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

13.4.3.1.3.3 Specific message contents

Table 13.4.3.1.3.3-0: Conditions for specific message contents
in Table 13.4.3.1.3.3-3

Condition

Explanation

Band > 64

If band > 64 is selected

Table 13.4.3.1.3.3-1: ATTACH REQUEST (preamble)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/remark

Comment

Condition

MS network capability

SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported

Mobile station classmark 2

Any allowed value

Supported Codecs

Any allowed value

Table 13.4.3.1.3.3-2: RRCConnectionReconfiguration (step 28, Table 13.4.3.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 13.4.3.1.3.3-3: MeasConfig (step 28, Table 13.4.3.1.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition UTRAN

Information Element

Value/Remark

Comment

Condition

measurementConfiguration ::= SEQUENCE {

measObjectToAddModifyList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f8

measObject[1]

MeasObjectUTRA-GENERIC(f8)

measObjectId[2]

IdMeasObject-f1

measObject[2]

MeasObjectEUTRA-GENERIC(f1)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModifyList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfigInterRAT-B2-UTRA

reportConfig[1]

ReportConfigInterRAT-B2-UTRA (-72, -76)

}

measIdToAddModifyList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f8

reportConfigId[1]

IdReportConfigInterRAT-B2-UTRA

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

    measObjectEUTRA-v9e0[1] SEQUENCE {}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Table 13.4.3.1.3.3-4: MeasurementReport (step 31, Table 13.4.3.1.3.2-2)

Derivation Path: 36.508, table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 5

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

utra-RSCP

(-5..91)

}

}

}

}

}

}

}

}

Table 13.4.3.1.3.3-5: MobilityFromEUTRACommand (step 32, Table 13.4.3.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

cs-FallbackIndicator

False

purpose CHOICE{

handover SEQUENCE {

targetRAT-Type

Utra

targetRAT-MessageContainer

HANDOVER TO UTRAN COMMAND(UTRA RRC message)

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

}

}

}

}

Table 13.4.3.1.3.3-6: HANDOVER TO UTRAN COMMAND (step 32, Table 13.4.3.1.3.3-5)

Derivation Path: 36.508, Table 4.7B.1-1, condition UTRA Speech

Table 13.4.3.1.3.3-7: UECapabilityEnquiry (step 31A, Table 13.4.3.1.3.2-2)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

2 entry

RAT-Type[1]

eutra

RAT-Type[2]

utra

}

}

}

}

}

Table 13.4.3.1.3.3-8: SECURITY MODE COMMAND (step 34, Table 13.4.3.1.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-n

Information Element

Condition

Value/remark

Ciphering mode info

Not Present

Table 13.4.3.1.3.3-9: Void

Table 13.4.3.1.3.3-10: QuantityConfig-DEFAULT-RSCP (Table 13.4.3.1.3.3-3)

Derivation Path: 36.508, Table 4.6.6-3A

Information Element

Value/remark

Comment

Condition

quantityConfigUTRA SEQUENCE {

measQuantityUTRA-FDD

cpich-RSCP

measQuantityUTRA-TDD

pccpch-RSCP

filterCoefficient

Not present

DEFAULT fc4

}

Table 13.4.3.1.3.3-11: ROUTING AREA UPDATE ACCEPT (step 2, Table 13.4.3.1.3.2-5)

Derivation path: 36.508, Table 4.7B.2-2

Information Element

Value/Remark

Comment

Condition

PDP context status

0

NSAPI(0) – NSAPI(15) is set to 0, which means that the SM state of all PDP contexts is PDP-INACTIVE

Table 13.4.3.1.3.3-12: SECURITY MODE COMMAND (step 1A, Table 13.4.3.1.3.2-5)

Derivation Path: 36.508, Table 4.7B.1-n

Information Element

Condition

Value/remark

Ciphering mode info

StartRestart

Integrity protection mode info

modify

CN Domain Identity

ps-domain

13.4.3.2 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / SRVCC

13.4.3.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and an IMS voice call is ongoing and an UTRA PS RB + Speech combination is configured for an UTRA cell}

then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the utra cell}

}

13.4.3.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3 and TS 23.216, clause 6.2.2.2.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover‘:

2> if the targetRAT-Type is set to ‘utra‘ or ‘geran‘:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 23.216, clause 6.2.2.2]

Depicted in figure 6.2.2.2-1 is a call flow for SRVCC from E‑UTRAN to UTRAN or GERAN with DTM HO support, including the handling of the non‑voice component. The flow requires that eNB can determine that either the target is UTRAN with PS HO or the target is GERAN with DTM support and the UE is supporting DTM.

Figure 6.2.2.2-1: SRVCC from E-UTRAN to UTRAN with PS HO or GERAN with DTM HO support

1. UE sends measurement reports to E-UTRAN.

2. Based on UE measurement reports the source E‑UTRAN decides to trigger an SRVCC handover to UTRAN/GERAN.

3. If target is UTRAN, the source E‑UTRAN sends a Handover Required (Target ID, generic Source to Target Transparent Container, SRVCC HO indication) message to the source MME. SRVCC HO indication indicates to MME that this is for CS+PS HO.

NOTE 1: When the source E-UTRAN indicates using SRVCC HO Indication that target is both CS and PS capable and this is a CS+PS HO request, the source MME sends the single received transparent container to both the target CS domain and the target PS domain.

If target is GERAN, the source E UTRAN sends a Handover Required (Target ID, generic Source to Target Transparent Container, additional Source to Target Transparent Container, SRVCC HO Indication) message to the source MME. The E‑UTRAN places the "old BSS to new BSS information IE" for the CS domain in the additional Source to Target Transparent Container. The differentiation between CS and PS containers is described in TS 36.413 [30]. In this case, the MME identifies from SRVCC HO Indication that this is a request for a CS+PS handover.

4. Based on the QCI associated with the voice bearer (QCI 1) and the SRVCC HO Indication, the source MME splits the voice bearer from all other PS bearers and initiates their relocation towards MSC Server and SGSN, respectively.

5a) Source MME initiates the PS-CS handover procedure for the voice bearer by sending a SRVCC PS to CS Request (IMSI, Target ID, STN-SR, C‑MSISDN, Source to Target Transparent Container, MM Context, Emergency Indication) message to the MSC Server. The Emergency Indication and the equipment identifier are included if the ongoing session is emergency session. Authenticated IMSI and C‑MSISDN shall also be included if available. The message includes information relevant to the CS domain only. MME received STN-SR and C‑MSISDN from the HSS as part of the subscription profile downloaded during the E‑UTRAN attach procedure. MM Context contains security related information. CS security key is derived by the MME from the E‑UTRAN/EPS domain key as defined in TS 33.401 [22]. The CS Security key is sent in the MM Context.

5b) MSC Server interworks the PS-CS handover request with a CS inter‑MSC handover request by sending a Prepare Handover Request message to the target MSC. If the target system is GERAN, the MSC Server assigns a default SAI as Source ID on the interface to the target BSS and uses BSSMAP encapsulated for the Prepare Handover Request. If the target system is UTRAN, the MSC Server uses RANAP encapsulated for the Prepare Handover Request.

NOTE 2: The value of the default SAI is configured in the MSC and allows a release 8 and later BSC to identify that the source for the SRVCC Handover is E-UTRAN. To ensure correct statistics in the target BSS the default SAI should be different from the SAIs used in UTRAN.

5c) Target MSC requests resource allocation for the CS relocation by sending the Relocation Request/Handover Request message to the target RNS/BSS. If the target RAT is UTRAN, Relocation Request/Handover Request message contains the generic Source to Target Transparent Container. If the target RAT is GERAN, Relocation Request/Handover Request message contains the additional Source to Target Transparent Container.

6. In parallel to the previous step the source MME initiates relocation of the PS bearers. The following steps are performed (for details see TS 23.401 [2] clauses 5.5.2.1 and 5.5.2.3):

a) Source MME sends a Forward Relocation Request (generic Source to Target Transparent Container, MM Context, PDN Connections IE) message to the target SGSN. If the target SGSN uses S4 based interaction with S-GW and P-GW, the PDN Connections IE includes bearer information for all bearers except the voice bearer. The handling of security keys for PS handover of the remaining non-voice PS bearers is specified in TS 33.401 [22].

NOTE 3: If the target SGSN uses Gn/Gp based interaction with GGSN the Forward Relocation Request will contain PDP Contexts, instead of PDN Connections IE, including bearer information for all bearers except the voice bearer.

b) Target SGSN requests resource allocation for the PS relocation by sending the Relocation Request/Handover Request (Source to Target Transparent Container) message to the target RNS/BSS.

7. After the target RNS/BSS receives both the CS relocation/handover request with the PS relocation/handover request, it assigns the appropriate CS and PS resources. The following steps are performed:

a) Target RNS/BSS acknowledges the prepared PS relocation/handover by sending the Relocation Request Acknowledge/Handover Request Acknowledge (Target to Source Transparent Container) message to the target SGSN.

b) Target SGSN sends a Forward Relocation Response (Target to Source Transparent Container) message to the source MME.

8. In parallel to the previous step the following steps are performed:

a) Target RNS/BSS acknowledges the prepared CS relocation/handover by sending the Relocation Request Acknowledge/Handover Request Acknowledge (Target to Source Transparent Container) message to the target MSC.

b) Target MSC sends a Prepare Handover Response (Target to Source Transparent Container) message to the MSC Server.

c) Establishment of circuit connection between the target MSC and the MGW associated with the MSC Server e.g. using ISUP IAM and ACM messages.

NOTE 4: The Target to Source Transparent Container sent to the target SGSN is step 7a and the Target to Source Transparent Container sent to the target MSC in step 8a, include the same allocation of CS and PS resources (e.g. the target BSS includes the same DTM Handover Command in both containers).

9. For non-emergency session, the MSC Server initiates the Session Transfer by using the STN-SR e.g. by sending an ISUP IAM (STN-SR) message towards the IMS. For emergency session, the MSC Server initiates the Session Transfer by using the locally configured E-STN-SR and by including the equipment identifier. Standard IMS Service Continuity or Emergency IMS Service Continuity procedures are applied for execution of the Session Transfer, TS 23.237 [14].

NOTE 5: This step can be started after step 8b.

NOTE 6: If the MSC Server is using an ISUP interface, then the initiation of the session transfer for non-emergency sessions may fail if the subscriber profile including CAMEL triggers is not available prior handover (see clause 7.3.2.1.3 of TS 23.292 [13]).

10. During the execution of the Session Transfer procedure the remote end is updated with the SDP of the CS access leg according to TS 23.237 [14]. The downlink flow of VoIP packets is switched towards the CS access leg at this point.

11. The source IMS access leg is released according to TS 23.237 [14].

NOTE 7: Steps 10 and 11 are independent of step 12.

12. The MSC Server sends a SRVCC PS to CS Response (Target to Source Transparent Container) message to the source MME.

13. Source MME synchronises the two prepared relocations and sends a Handover Command (Target to Source Transparent Container) message to the source E‑UTRAN.

NOTE 8: When the target cell is GERAN, the MME may receive different Target to Source Transparent Containers from the MSC Server and from the SGSN, i.e. a "New BSS to Old BSS Information" (see TS 48.008 [23]) may be received from the MSC Server and a "Target BSS to Source BSS Transparent Container" (see TS 48.018 [24]) may be received from the SGSN.

14. E‑UTRAN sends a Handover from E‑UTRAN Command message to the UE.

15. UE tunes to the target UTRAN/GERAN cell.

16. Handover Detection at the target RNS/BSS occurs. The UE sends a Handover Complete message via the target RNS/BSS to the target MSC. If the target MSC is not the MSC Server, then the Target MSC sends an SES (Handover Complete) message to the MSC Server. At this stage, the UE re-establishes the connection with the network and can send/receive voice data.

17. The CS relocation/handover is complete. The following steps are performed:

a) Target RNS/BSS sends Relocation Complete/Handover Complete message to the target MSC.

b) Target MSC sends an SES (Handover Complete) message to the MSC Server. The speech circuit is through connected in the MSC Server/MGW according to TS 23.009 [18].

c) Completion of the establishment procedure with ISUP Answer message to the MSC Server according to TS 23.009 [18].

d) MSC Server sends a SRVCC PS to CS Complete Notification message to the source MME. Source MME acknowledges the information by sending a SRVCC PS to CS Complete Acknowledge message to the MSC Server.

e) The source MME deactivates the voice bearer towards S-GW/P-GW and sets the PS-to-CS handover indicator to Delete Bearer Command message. This triggers MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401 [2]. The MME does not send deactivation request toward the eNodeB on receiving PS-to-CS Complete Notification in step 17d. If dynamic PCC is deployed, the PGW may interact with PCRF as defined in TS 23.203 [31].

f) If the HLR is to be updated, i.e. if the IMSI is authenticated but unknown in the VLR, the MSC Server performs a TMSI reallocation towards the UE using its own non-broadcast LAI and, if the MSC Server and other MSC/VLRs serve the same (target) LAI, with its own Network Resource Identifier (NRI).

NOTE 9: The TMSI reallocation is performed by the MSC Server towards the UE via target MSC.

g) If the MSC Server performed a TMSI reallocation in step 17f, and if this TMSI reallocation was completed successfully, the MSC Server performs a MAP Update Location to the HSS/HLR.

NOTE 10: This Update Location is not initiated by the UE.

18. In parallel to the previous step, the PS relocation/handover is completed. The following steps are performed:

a) Target RNS/BSS sends Relocation Complete/Handover Complete message to target SGSN.

b) Target SGSN sends a Forward Relocation Complete message to the source MME. After having completed step 17e, the source MME acknowledges the information by sending a Forward Relocation Complete Acknowledge message to the target SGSN.

c) Target SGSN updates the bearer with S‑GW/P‑GW/GGSN as specified in TS 23.401 [2].

d) The MME sends Delete Session Request to the SGW as defined in TS 23.401 [2].

e) The source MME sends a Release Resources message to the Source eNodeB as defined in TS 23.401 [2]. The Source eNodeB releases its resources related to the UE.

NOTE 11: Routing Area Update procedures by the UE are done in accordance with TS 23.401 [2].

19. For an emergency services session after handover is complete, the source MME or the MSC Server may send a Subscriber Location Report carrying the identity of the MSC Server to a GMLC associated with the source or target side, respectively, as defined in TS 23.271 [29] to support location continuity.

NOTE 12: Any configuration of the choice between a source MME versus MSC Server update to a GMLC needs to ensure that a single update occurs from one of these entities when the control plane location solution is used on the source and/or target sides.

In case the MME determines that only the relocation of the voice bearer but not the relocation of one or more PS bearers succeeds, then the MME proceeds with step 13 after receiving SRVCC PS to CS Response from the MSC Server in step 12 and both UE and MME continue the procedure as described in clause 6.2.2.1A.

[24.237 Rel-12 , Clause 12.2.3]

After successful PS to CS SRVCC procedures (as described in 3GPP TS 24.008 [8]) have been completed, if the SC UE is not using ICS capabilities and the SC UE does not apply the MSC Server assisted mid-call feature as specified in subclause 12.2.3A, the SC UE shall replace the ongoing session with active speech media component which was made active most recently with the newly established CS voice call.

NOTE 1: In the case when ICS is not supported or used and the SC UE does not apply the MSC Server assisted mid-call feature, only the ongoing session with active speech media component which was made active most recently is transferred from PS to CS audio.

If the Gm reference point is:

1) retained upon successful PS handover completion;

NOTE 2: The SC UE knows that the Gm reference point is retained upon PS handover if, following handover, the SC UE has a dedicated PDP context for SIP signalling or has a general-purpose PDP context to carry the IM CN subsystem-related signalling, as described in 3GPP TS 24.229 [2] annex B.2.2.1.

a) and there are one or more remaining non-speech media component(s) in the IMS session other than the speech media component which were transferred to the CS Target Access Leg; the SC UE shall:

– send a SIP re-INVITE request to the SCC AS as specified for media removal in subclause 13.2.1; and

– indicate in the SDP offer the speech media component as removed.

b) and there are no more non-speech media component(s) remaining in the IMS session other than the speech media component which was transferred to the CS Target Access Leg; the SC UE shall either:

– send a SIP re-INVITE request to the SCC AS as specified for media removal in subclause 13.2.1 indicating in the SDP offer the speech media component as removed;

– wait for a period of time for a SIP BYE request to be received before clearing the SIP dialog state internally; or

– clear the SIP dialog state internally; or

2) not retained upon successful PS handover completion the SC UE shall clear the SIP dialog state internally.

NOTE 3: If a SIP BYE request is received after the UE has cleared the SIP dialog state internally the UE will send a SIP 481 Call/Transaction Does Not Exist response according to RFC 3261 [19].

13.4.3.2.3 Test description

13.4.3.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 5.

– 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 Registered, Idle mode (state 2) on Cell 1 according to [18].

13.4.3.2.3.2 Test procedure sequence

Table 13.4.3.2.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 after preamble, 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.4.3.2.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 5

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

The power level values are such that entering conditions for event B2 are not satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-88

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-88

T1

Cell-specific RS EPRE

dBm/15kHz

-84

The power level values are such that entering conditions for event B2 are satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

T2

Cell-specific RS EPRE

dBm/15kHz

Non-suitable “Off”

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

Table 13.4.3.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures UTRA cell 5 to reference configuration according TS 36.508 Table 4.8.3-1, condition UTRA PS RB + Speech.

2-25

Steps 1 to 24 of the generic test procedure for IMS MT speech call (TS 36.508, 4.5A.7.3-1).

26-27

Void

28

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter RAT measurement and reporting for event B2.

<–

RRCConnectionReconfiguration

29

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

30

The SS changes the power level for Cell 1 and Cell 5 according to the row "T1" in table 13.4.3.2.3.2-1

31

The UE transmits a MeasurementReport message on Cell 1 to report event B2 for Cell 5.

–>

MeasurementReport

32

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

32A

The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for E-UTRA and UTRA.

<–

UECapabilityEnquiry

32B

The UE transmits a UECapabilityInformation message on Cell 1.

NOTE: The start-CS values received, should be used to configure ciphering on Cell 5.

–>

UECapabilityInformation

33

Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message on Cell 5?

–>

HANDOVER TO UTRAN COMPLETE

1

P

EXCEPTION: In parallel to the events described in step 34 to 39 the steps specified in Table 13.4.3.2.3.2-5 take place.

34

The SS transmits a SECURITY MODE COMMAND message for the CS domain.

<–

SECURITY MODE COMMAND

35

The UE transmits a SECURITY MODE COMPLETE message.

–>

SECURITY MODE COMPLETE

36

The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.

<–

UTRAN MOBILITY INFORMATION

37

The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.

–>

UTRAN MOBILITY INFORMATION CONFIRM

38

The SS transmits a TMSI REALLOCATION COMMAND message.

<–

TMSI REALLOCATION COMMAND

39

The UE transmits a TMSI REALLOCATION COMPLETE message.

–>

TMSI REALLOCATION COMPLETE

40

SS adjusts cell levels according to row T2 of Table 13.4.3.2.3.2-1.

The UE is in end state UTRA CS call (U5).

Table 13.4.3.2.3.2-3: Void

Table 13.4.3.2.3.2-4: Void

Table 13.4.3.2.3.2-5: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: In parallel to the events described in Step 1 to 3 the steps specified in Table 13.4.3.2.3.2-6 take place.

1

Check: Does the UE transmit a ROUTING AREA UPDATE REQUEST message?

–>

ROUTING AREA UPDATE REQUEST

P

1A

The SS transmits a SECURITY MODE COMMAND message for the PS domain.

<–

SECURITY MODE COMMAND

1B

The UE transmits a SECURITY MODE COMPLETE message.

–>

SECURITY MODE COMPLETE

2

The SS transmits a ROUTING AREA UPDATE ACCEPT message.

<–

ROUTING AREA UPDATE ACCEPT

3

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

EXCEPTION: Step 4a1-4a2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a certain action.

4a1

The UE transmits DEACTIVATE PDP CONTEXT REQUEST message

–>

DEACTIVATE PDP CONTEXT REQUEST

4a2

The SS transmits DEACTIVATE PDP CONTEXT ACCEPT message

<–

DEACTIVATE PDP CONTEXT ACCEPT

Table 13.4.3.2.3.2-6: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: Steps 7a1 – 7b1 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a certain action.

EXCEPTION: Step 7a1a1 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a certain action.

1-6

Void

6a

Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP re-registration defined in Annex C.46 of TS 34.229-1 can take place

7a1a1

IF the UE wants to remove SRVCC media in the next 10 sec THEN the generic procedure defined in Annex C.24 of TS 34.229-1 [35] take place.

7a2

Generic procedure defined in Annex C.36 of TS 34.229-1 [35]. IMS session release.

7a3

Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 [35] take place.

7b1

Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 [35] take place.

13.4.3.2.3.3 Specific message contents

Table 13.4.3.2.3.3-0: Conditions for specific message contents
in Table 13.4.3.2.3.3-3

Condition

Explanation

Band > 64

If band > 64 is selected

Table 13.4.3.2.3.3-1: ATTACH REQUEST (preamble)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/remark

Comment

Condition

MS network capability

SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported

Mobile station classmark 2

Any allowed value

Supported Codecs

Any allowed value

Table 13.4.3.2.3.3-2: RRCConnectionReconfiguration (step 28, Table 13.4.3.2.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 13.4.3.2.3.3-3: MeasConfig (step 28, Table 13.4.3.2.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition UTRAN

Information Element

Value/Remark

Comment

Condition

measurementConfiguration ::= SEQUENCE {

measObjectToAddModifyList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f8

measObject[1]

MeasObjectUTRA-GENERIC(f8)

measObjectId[2]

IdMeasObject-f1

measObject[2]

MeasObjectEUTRA-GENERIC(f1)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModifyList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfigInterRAT-B2-UTRA

reportConfig[1]

ReportConfigInterRAT-B2-UTRA (-72, -76)

}

measIdToAddModifyList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f8

reportConfigId[1]

IdReportConfigInterRAT-B2-UTRA

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Table 13.4.3.2.3.3-4: MeasurementReport (step 31, Table 13.4.3.2.3.2-2)

Derivation Path: 36.508, table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 5

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

utra-RSCP

(-5..91)

}

}

}

}

}

}

}

}

Table 13.4.3.2.3.3-5: MobilityFromEUTRACommand (step 32, Table 13.4.3.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

cs-FallbackIndicator

False

purpose CHOICE{

handover SEQUENCE {

targetRAT-Type

Utra

targetRAT-MessageContainer

HANDOVER TO UTRAN COMMAND(UTRA RRC message)

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

}

}

}

}

Table 13.4.3.2.3.3-6: HANDOVER TO UTRAN COMMAND (step 32, Table 13.4.3.2.3.3-5)

Derivation Path: 36.508, Table 4.7B.1-1, condition UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DCH

Table 13.4.3.2.3.3-7: UECapabilityEnquiry (step 32A, Table 13.4.3.2.3.2-2)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

2 entry

RAT-Type[1]

eutra

RAT-Type[2]

utra

}

}

}

}

}

Table 13.4.3.2.3.3-8: SECURITY MODE COMMAND (step 34, Table 13.4.3.2.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-n

Information Element

Condition

Value/remark

Ciphering mode info

Not Present

Table 13.4.3.2.3.3-9: Void

Table 13.4.3.2.3.3-10: Void

Table 13.4.3.2.3.3-11: ROUTING AREA UPDATE ACCEPT (step 2, Table 13.4.3.2.3.2-5)

Derivation path: 36.508, Table 4.7B.2-2

Information Element

Value/Remark

Comment

Condition

Update result

0 ‘ follow-on proceed’

PDP context status

‘0010000000000000’B

NSAPI 5

13.4.3.3 Inter-system mobility / E-UTRA voice to GSM CS voice / SRVCC

13.4.3.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and an IMS voice call is ongoing and an GERAN Speech RAB combination is configured for an GERAN cell}

then { UE transmits a HANDOVER COMPLETE message on the geran cell}

}

13.4.3.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3 and TS 23.216, clause 6.2.2.1.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover‘:

2> if the targetRAT-Type is set to ‘utra‘ or ‘geran‘:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 23.216, clause 6.2.2.1]

Depicted in figure 6.2.2.1-1 is a call flow for SRVCC from E-UTRAN to GERAN without DTM support. The flow requires that eNB can determine that the target is GERAN without DTM support or that the UE is without DTM support.

Figure 6.2.2.1-1: SRVCC from E-UTRAN to GERAN without DTM support

1. UE sends measurement reports to E-UTRAN.

2. Based on UE measurement reports the source E‑UTRAN decides to trigger an SRVCC handover to GERAN.

3. Source E‑UTRAN sends Handover Required (Target ID, generic Source to Target Transparent Container, SRVCC HO Indication) message to the source MME. The E‑UTRAN places the "old BSS to new BSS information IE" for the CS domain in the generic Source to Target Transparent Container. The SRVCC HO indication indicates to the MME that target is only CS capable, hence this is a SRVCC handover operation only towards the CS domain. The message includes an indication that the UE is not available for the PS service in the target cell.

4. Based on the QCI associated with the voice bearer (QCI 1) and the SRVCC HO indication, the source MME splits the voice bearer from the non voice bearers and initiates the PS-CS handover procedure for the voice bearer only towards MSC Server.

5. The MME sends a SRVCC PS to CS Request (IMSI, Target ID, STN-SR, C‑MSISDN, generic Source to Target Transparent Container, MM Context, Emergency Indication) message to the MSC Server. The Emergency Indication and the equipment identifier are is included if the ongoing session is emergency session. Authenticated IMSI and C‑MSISDN shall also be included, if available. The MME received STN-SR and C‑MSISDN from the HSS as part of the subscription profile downloaded during the E‑UTRAN attach procedure. The MM Context contains security related information. CS security key is derived by the MME from the E‑UTRAN/EPS domain key as defined in TS 33.401 [22]. The CS Security key is sent in the MM Context.

6. The MSC Server interworks the PS-CS handover request with a CS inter‑MSC handover request by sending a Prepare Handover Request message to the target MSC. The MSC Server assigns a default SAI as Source ID on the interface to the target BSS and uses BSSMAP encapsulated for the Prepare Handover Request.

NOTE 1: The value of the default SAI is configured in the MSC and allows a release 8 and later BSC to identify that the source for the SRVCC Handover is E-UTRAN. To ensure correct statistics in the target BSS the default SAI should be different from the SAIs used in UTRAN.

7. Target MSC performs resource allocation with the target BSS by exchanging Handover Request/ Acknowledge messages.

8. Target MSC sends a Prepare Handover Response message to the MSC Server.

9. Establishment of circuit connection between the target MSC and the MGW associated with the MSC Server e.g. using ISUP IAM and ACM messages.

10. For non-emergency session, the MSC Server initiates the Session Transfer by using the STN-SR e.g. by sending an ISUP IAM (STN-SR) message towards the IMS. For emergency session, the MSC Server initiates the Session Transfer by using the locally configured E-STN-SR and by including the equipment identifier. Standard IMS Service Continuity or Emergency IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.237 [14].

NOTE 2: This step can be started after step 8.

NOTE 3: If the MSC Server is using an ISUP interface, then the initiation of the session transfer for non-emergency session may fail if the subscriber profile including CAMEL triggers is not available prior handover (see clause 7.3.2.1.3 in TS 23.292 [13]).

11. During the execution of the Session Transfer procedure the remote end is updated with the SDP of the CS access leg. The downlink flow of VoIP packets is switched towards the CS access leg at this point.

12. Source IMS access leg is released as per TS 23.237 [14].

NOTE 4: Steps 11 and 12 are independent of step 13.

13. MSC Server sends a SRVCC PS to CS Response (Target to Source Transparent Container) message to the source MME.

14. Source MME sends a Handover Command (Target to Source Transparent Container) message to the source E-UTRAN. The message includes information about the voice component only.

15. Source E-UTRAN sends a Handover from E-UTRAN Command message to the UE.

16. UE tunes to GERAN.

17. Handover Detection at the target BSS occurs. The UE sends a Handover Complete message via the target BSS to the target MSC. If the target MSC is not the MSC Server, then the Target MSC sends an SES (Handover Complete) message to the MSC Server.

18. The UE starts the Suspend procedure specified in TS 23.060 [10], clause 16.2.1.1.2. The TLLI and RAI pair are derived from the GUTI as described in TS 23.003 [27]. This triggers the Target SGSN to send a Suspend Notification message to the Source MME. The MME returns a Suspend Acknowledge to the Target SGSN.

NOTE 5: The MME might not be able to derive the GUTI from the received P-TMSI and RAI pair and therefore it might not be able to identify which UE context is associated with the Suspend Notification message. Also in this case the bearers are deactivated and/or suspended as in step 22a.

19. Target BSS sends a Handover Complete message to the target MSC.

20. Target MSC sends an SES (Handover Complete) message to the MSC Server. The speech circuit is through connected in the MSC Server/MGW according to TS 23.009 [18].

21. Completion of the establishment procedure with ISUP Answer message to the MSC Server according to TS 23.009 [18].

22. MSC Server sends a SRVCC PS to CS Complete Notification message to the source MME, informing it that the UE has arrived on the target side. Source MME acknowledges the information by sending a SRVCC PS to CS Complete Acknowledge message to the MSC Server.

22a. The MME deactivates bearers used for voice and other GBR bearers. All GBR bearers are deactivated towards S-GW and P-GW by initiating MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401 [2]. The MME does not send deactivation request toward the eNodeB on receiving PS-to-CS Complete Notification in step 22. PS-to-CS handover indicator is notified to P-GW for voice bearer during the bearer deactivation procedure. For GTP-based S5/S8, the S-GW requests the P-GW to delete all GBR bearer contexts by sending a Delete Bearer Command message. If dynamic PCC is deployed, the P‑GW may interact with PCRF as defined in TS 23.203 [31]. For PMIP-based S5/S8, S-GW interacts with the PCRF which in turn updates PCC rules for GBR traffic in the P-GW.

The MME starts preservation and suspension of non-GBR bearers by sending Suspend Notification message towards S-GW. For these non-GBR bearers, the S-GW releases S1-U bearers for the UE and sends Suspend Notification message to the P-GW(s). The MME stores in the UE context that UE is in suspended status. All the preserved non-GBR bearers are marked as suspended status in the S-GW and P-GW. The P-GW should discard packets if received for the suspended UE.

23a. If the HLR is to be updated, i.e. if the IMSI is authenticated but unknown in the VLR, the MSC Server performs a TMSI reallocation towards the UE using its own non-broadcast LAI and, if the MSC Server and other MSC/VLRs serve the same (target) LAI, with its own Network Resource Identifier (NRI).

NOTE 5: The TMSI reallocation is performed by the MSC Server towards the UE via target MSC.

23b. If the MSC Server performed a TMSI reallocation in step 23a, and if this TMSI reallocation was completed successfully, the MSC Server performs a MAP Update Location to the HSS/HLR.

NOTE 6: This Update Location is not initiated by the UE.

24. For an emergency services session after handover is complete, the source MME or the MSC Server may send a Subscriber Location Report carrying the identity of the MSC Server to a GMLC associated with the source or target side, respectively, as defined in TS 23.271 [29] to support location continuity.

NOTE 7: Any configuration of the choice between a source MME versus MSC Server update to a GMLC needs to ensure that a single update occurs from one of these entities when the control plane location solution is used on the source and/or target sides.

13.4.3.3.3 Test description

13.4.3.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 24.

– 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 Registered, Idle mode (state 2) on Cell 1 according to [18].

13.4.3.3.3.2 Test procedure sequence

Table 13.4.3.3.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 after preamble, 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.4.3.3.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 24

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

The power level values are such that entering conditions for event B2 are not satisfied.

RSSI

dBm

-85

T1

Cell-specific RS EPRE

dBm/15kHz

-85

The power level values are such that entering conditions for event B2 are satisfied.

RSSI

dBm

-65

T2

Cell-specific RS EPRE

dBm/15kHz

Non-suitable “Off”

RSSI

dBm

-65

Table 13.4.3.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-26

Steps 1 to 26 of the generic test procedure for IMS MT speech call (TS 36.508 4.5A.7.3-1).

27

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter RAT measurement and reporting for event B2.

<–

RRCConnectionReconfiguration

28

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

29

The SS changes the power level for Cell 1 and Cell 5 according to the row "T1" in table 13.4.3.3.3.2-1

30

The UE transmits a MeasurementReport message on Cell 1 to report event B2 for Cell 24.

–>

MeasurementReport

31

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

32

Check: Does the UE transmit a HANDOVER COMPLETE message on Cell 24?

–>

HANDOVER COMPLETE

1

P

33

The UE transmits a GPRS SUSPENSION REQUEST message

–>

GPRS SUSPENSION REQUEST

34

The SS transmits a TMSI REALLOCATION COMMAND message.

<–

TMSI REALLOCATION COMMAND

35

The UE transmits a TMSI REALLOCATION COMPLETE message.

–>

TMSI REALLOCATION COMPLETE

35A

SS adjusts cell levels according to row T2 of table 13.4.3.3.3.2-1.

36-50

Steps 20 to 34 of the generic test procedure described in TS36.508 subclause 6.4.3.8.1 are performed on Cell 24.

Table 13.4.3.3.3.2-4: Void

13.4.3.3.3.3 Specific message contents

Table 13.4.3.3.3.3-1: ATTACH REQUEST (preamble)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/remark

Comment

Condition

MS network capability

SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported

Mobile station classmark 2

Any allowed value

Supported Codecs

Any allowed value

Table 13.4.3.3.3.3-2: RRCConnectionReconfiguration (step 27, Table 13.4.3.3.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 13.4.3.3.3.3-3: MeasConfig (step 27, Table 13.4.3.3.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition GERAN

Information Element

Value/Remark

Comment

Condition

measurementConfiguration ::= SEQUENCE {

measObjectToAddModifyList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f11

measObject[1]

MeasObjectGERAN-GENERIC(f11)

measObjectId[2]

IdMeasObject-f1

measObject[2]

MeasObjectEUTRA-GENERIC(f1)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModifyList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfigInterRAT-B2-GERAN

reportConfig[1]

ReportConfigInterRAT-B2-GERAN (-69, -75)

}

measIdToAddModifyList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f11

reportConfigId[1]

IdReportConfigInterRAT-B2-GERAN

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] ::= SEQUENCE {}

measObjectEUTRA-v9e0[1] ::= SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 13.4.3.3.3.3-4: MeasurementReport (step 30, Table 13.4.3.3.3.2-2)

Derivation Path: 36.508, table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListGERAN SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId

PhysicalCellIdentity of Cell 24

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rssi

The value of rssi is present but contents not checked

}

}

}

}

}

}

}

}

Table 13.4.3.3.3.3-5: MobilityFromEUTRACommand (step 31, Table 13.4.3.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

cs-FallbackIndicator

False

purpose CHOICE{

handover SEQUENCE {

targetRAT-Type

geran

targetRAT-MessageContainer

HANDOVER COMMAND(GERAN RRC message), see Table 13.4.3.3.3.3-6

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension

Not present

nonCriticalExtension SEQUENCE {

bandIndicator

Set according to the band used for Cell 24

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

Table 13.4.3.3.3.3-6: HANDOVER COMMAND (step 31, Table 13.4.3.3.3.2-2)

Derivation Path: 51.010, Table 40.2.4.33

Information Element

Value/remark

Comment

Condition

Cell Description

Network Colour Code

1

Base Station Colour Code

5

BCCH Carrier Number

The BCCH Carrier ARFCN as per table in clause 40.1.1 of 51.010-1.

Description of the First Channel, after time

Channel Description

Channel Type and TDMA offset

TCH/F + ACCH’s

Timeslot Number

Chosen arbitrarily, but not Zero.

Training Sequence Code

Same as the BCCH

Hopping channel

Single RF channel

ARFCN

The first ARFCN in the cell allocation as per table in clause 40.2.1.1.1 of 51.010-1

Cipher Mode Setting

1001xxxy

See TS 44.018 §9.1.15.10

xxx – px_GSM_CipherAlg

y – px_GSM_CipheringOnOff

Table 13.4.3.3.3.3-7: ROUTING AREA UPDATE ACCEPT (step 48, Table 13.4.3.3.3.2-2)

Derivation path: 36.508, Table 4.7B.2-2

Information Element

Value/Remark

Comment

Condition

PDP context status

0

NSAPI(0) – NSAPI(15) is set to 0, which means that the SM state of all PDP contexts is PDP-INACTIVE

13.4.3.4 Inter-system mobility / E-UTRA voice to UTRA CS voice / Unsuccessful case / Retry on old cell / SRVCC

13.4.3.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and an IMS voice call is ongoing and the UE does not succeed in establishing the connection to the target radio access technology }

then { UE initiates the connection re-establishment procedure }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE successfully completes the RRC Connection re-establishment procedure }

then { UE is in E-UTRA RRC_CONNECTED state }

}

4.3.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3, 5.4.3.5, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.5, TS 23.216, clause 6.2.2.1 and 6.2.2.1A.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover‘:

2> if the targetRAT-Type is set to ‘utra‘ or ‘geran‘:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 36.331, clause 5.4.3.5]

The UE shall:

1> if T304 expires (mobility from E-UTRA failure); or

1> if the UE does not succeed in establishing the connection to the target radio access technology; or

1> if the UE is unable to comply with (part of) the configuration included in the MobilityFromEUTRACommand message; or

1> if there is a protocol error in the inter RAT information included in the MobilityFromEUTRACommand message, causing the UE to fail the procedure according to the specifications applicable for the target RAT:

2> stop T304, if running;

2> if the cs-FallbackIndicator in the MobilityFromEUTRACommand message was set to ‘TRUE‘:

3> indicate to upper layers that the CS Fallback procedure has failed;

2> revert back to the configuration used in the source cell, excluding the configuration configured by the physicalConfigDedicated, mac-MainConfig and sps-Config;

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

[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 mobility from E-UTRA failure, in accordance with 5.4.3.5; or

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;

1> 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 a suitable E-UTRA cell, the UE shall:

1> stop timer T311;

1> start timer T301;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> initiate transmission of the RRCConnectionReestablishmentRequest message in accordance with 5.3.7.4;

[TS 36.331, clause 5.3.7.4]

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

1> set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases); and

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

1> set the reestablishmentCause as follows:

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure‘;

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

[TS 36.331, clause 5.3.7.5]

The UE shall:

1> stop timer T301;

1> re-establish PDCP for SRB1;

1> re-establish RLC for SRB1;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> resume SRB1;

1> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the procedure ends;

[TS 23.216, clause 6.2.2.1]

Depicted in figure 6.2.2.1-1 is a call flow for SRVCC from E-UTRAN to GERAN without DTM support. The flow requires that eNB can determine that the target is GERAN without DTM support or that the UE is without DTM support.

Figure 6.2.2.1-1: SRVCC from E-UTRAN to GERAN without DTM support

1. UE sends measurement reports to E-UTRAN.

2. Based on UE measurement reports the source E‑UTRAN decides to trigger an SRVCC handover to GERAN.

3. Source E‑UTRAN sends Handover Required (Target ID, generic Source to Target Transparent Container, SRVCC HO Indication) message to the source MME. The E‑UTRAN places the "old BSS to new BSS information IE" for the CS domain in the generic Source to Target Transparent Container. The SRVCC HO indication indicates to the MME that target is only CS capable, hence this is a SRVCC handover operation only towards the CS domain. The message includes an indication that the UE is not available for the PS service in the target cell.

4. Based on the QCI associated with the voice bearer (QCI 1) and the SRVCC HO indication, the source MME splits the voice bearer from the non voice bearers and initiates the PS-CS handover procedure for the voice bearer only towards MSC Server.

5. The MME sends a SRVCC PS to CS Request (IMSI, Target ID, STN-SR, C‑MSISDN, generic Source to Target Transparent Container, MM Context, Emergency Indication) message to the MSC Server. The Emergency Indication and the equipment identifier are is included if the ongoing session is emergency session. Authenticated IMSI and C‑MSISDN shall also be included, if available. The MME received STN-SR and C‑MSISDN from the HSS as part of the subscription profile downloaded during the E‑UTRAN attach procedure. The MM Context contains security related information. CS security key is derived by the MME from the E‑UTRAN/EPS domain key as defined in TS 33.401 [22]. The CS Security key is sent in the MM Context.

6. The MSC Server interworks the PS-CS handover request with a CS inter‑MSC handover request by sending a Prepare Handover Request message to the target MSC. The MSC Server assigns a default SAI as Source ID on the interface to the target BSS and uses BSSMAP encapsulated for the Prepare Handover Request.

NOTE 1: The value of the default SAI is configured in the MSC and allows a release 8 and later BSC to identify that the source for the SRVCC Handover is E-UTRAN. To ensure correct statistics in the target BSS the default SAI should be different from the SAIs used in UTRAN.

7. Target MSC performs resource allocation with the target BSS by exchanging Handover Request/ Acknowledge messages.

8. Target MSC sends a Prepare Handover Response message to the MSC Server.

9. Establishment of circuit connection between the target MSC and the MGW associated with the MSC Server e.g. using ISUP IAM and ACM messages.

10. For non-emergency session, the MSC Server initiates the Session Transfer by using the STN-SR e.g. by sending an ISUP IAM (STN-SR) message towards the IMS. For emergency session, the MSC Server initiates the Session Transfer by using the locally configured E-STN-SR and by including the equipment identifier. Standard IMS Service Continuity or Emergency IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.237 [14].

NOTE 2: This step can be started after step 8.

NOTE 3: If the MSC Server is using an ISUP interface, then the initiation of the session transfer for non-emergency session may fail if the subscriber profile including CAMEL triggers is not available prior handover (see clause 7.3.2.1.3 in TS 23.292 [13]).

11. During the execution of the Session Transfer procedure the remote end is updated with the SDP of the CS access leg. The downlink flow of VoIP packets is switched towards the CS access leg at this point.

12. Source IMS access leg is released as per TS 23.237 [14].

NOTE 4: Steps 11 and 12 are independent of step 13.

13. MSC Server sends a SRVCC PS to CS Response (Target to Source Transparent Container) message to the source MME.

14. Source MME sends a Handover Command (Target to Source Transparent Container) message to the source E-UTRAN. The message includes information about the voice component only.

15. Source E-UTRAN sends a Handover from E-UTRAN Command message to the UE.

16. UE tunes to GERAN.

17. Handover Detection at the target BSS occurs. The UE sends a Handover Complete message via the target BSS to the target MSC. If the target MSC is not the MSC Server, then the Target MSC sends an SES (Handover Complete) message to the MSC Server.

18. The UE starts the Suspend procedure specified in TS 23.060 [10], clause 16.2.1.1.2. The TLLI and RAI pair are derived from the GUTI as described in TS 23.003 [27]. This triggers the Target SGSN to send a Suspend Notification message to the Source MME. The MME returns a Suspend Acknowledge to the Target SGSN.

NOTE 5: The MME might not be able to derive the GUTI from the received P-TMSI and RAI pair and therefore it might not be able to identify which UE context is associated with the Suspend Notification message. Also in this case the bearers are deactivated and/or suspended as in step 22a.

19. Target BSS sends a Handover Complete message to the target MSC.

20. Target MSC sends an SES (Handover Complete) message to the MSC Server. The speech circuit is through connected in the MSC Server/MGW according to TS 23.009 [18].

21. Completion of the establishment procedure with ISUP Answer message to the MSC Server according to TS 23.009 [18].

22. MSC Server sends a SRVCC PS to CS Complete Notification message to the source MME, informing it that the UE has arrived on the target side. Source MME acknowledges the information by sending a SRVCC PS to CS Complete Acknowledge message to the MSC Server.

22a. The MME deactivates bearers used for voice and other GBR bearers. All GBR bearers are deactivated towards S-GW and P-GW by initiating MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401 [2]. The MME does not send deactivation request toward the eNodeB on receiving PS-to-CS Complete Notification in step 22. PS-to-CS handover indicator is notified to P-GW for voice bearer during the bearer deactivation procedure. For GTP-based S5/S8, the S-GW requests the P-GW to delete all GBR bearer contexts by sending a Delete Bearer Command message. If dynamic PCC is deployed, the P‑GW may interact with PCRF as defined in TS 23.203 [31]. For PMIP-based S5/S8, S-GW interacts with the PCRF which in turn updates PCC rules for GBR traffic in the P-GW.

The MME starts preservation and suspension of non-GBR bearers by sending Suspend Notification message towards S-GW. For these non-GBR bearers, the S-GW releases S1-U bearers for the UE and sends Suspend Notification message to the P-GW(s). The MME stores in the UE context that UE is in suspended status. All the preserved non-GBR bearers are marked as suspended status in the S-GW and P-GW. The P-GW should discard packets if received for the suspended UE.

23a. If the HLR is to be updated, i.e. if the IMSI is authenticated but unknown in the VLR, the MSC Server performs a TMSI reallocation towards the UE using its own non-broadcast LAI and, if the MSC Server and other MSC/VLRs serve the same (target) LAI, with its own Network Resource Identifier (NRI).

NOTE 5: The TMSI reallocation is performed by the MSC Server towards the UE via target MSC.

23b. If the MSC Server performed a TMSI reallocation in step 23a, and if this TMSI reallocation was completed successfully, the MSC Server performs a MAP Update Location to the HSS/HLR.

NOTE 6: This Update Location is not initiated by the UE.

24. For an emergency services session after handover is complete, the source MME or the MSC Server may send a Subscriber Location Report carrying the identity of the MSC Server to a GMLC associated with the source or target side, respectively, as defined in TS 23.271 [29] to support location continuity.

NOTE 7: Any configuration of the choice between a source MME versus MSC Server update to a GMLC needs to ensure that a single update occurs from one of these entities when the control plane location solution is used on the source and/or target sides.

After the CS voice call is terminated and if the UE is still in GERAN (or for any other reason specified in TS 24.008), then the UE shall resume PS services as specified in TS 23.060 [10]. A Gn SGSN will follow TS 23.060 [10] to resume the PDP Context(s). An S4 SGSN will follow TS 23.060 [10] to resume the bearers, and will in addition inform S-GW and P-GW(s) to resume the suspended bearers. If the UE has returned to E-UTRAN after the CS voice call was terminated, then the UE shall resume PS service by sending TAU to MME. The MME will in addition inform S-GW and P-GW(s) to resume the suspended bearers. Resuming the suspended bearers in the S-GW and in the P-GW should be done by implicit resume using the Modify Bearer request message if it is triggered by the procedure in operation, e.g. RAU, TAU or Service Request. The S-GW is aware of the suspend state of the bearers and will forward the Modify Bearer request to the P-GW. Explicit resume using the Resume Notification message should be used in cases when Modify Bearer Request is not triggered by the procedure in operation.

[TS 23.216, clause 6.2.2.1A]

The call flow for this scenario is similar to the call flow depicted in figure 6.2.2.1‑1, with the exceptions that the Suspend procedure (step 18 and step 22a in figure 6.2.2.1-1) is not performed and that the MME only deactivates bearers used for voice (step 22a in figure 6.2.2.1-1) and sets the PS-to-CS handover indicator. The scenario requires that eNB can determine that the target is either GERAN with DTM but without DTM HO support and that the UE is supporting DTM or that the target is UTRAN (HSPA) without PS HO support. The message in step 3 in figure 6.2.2.1-1 includes an indication to the MME that the UE is available for PS service in the target cell. Furthermore, if the target is GERAN, the E‑UTRAN places in the generic Source to Target Transparent Container the "old BSS to new BSS information IE", while if the target is UTRAN, the generic Source to Target Transparent container is encoded according to the Source RNC to Target RNC Transparent Container IE definition. At the end of the procedure described in figure 6.2.2.1‑1, the remaining PS resources are re-established when the UE performs the Routeing Area update procedure. Triggers for performing Routeing Area update procedure are described in TS 23.060 [10]. The target SGSN may deactivate the PDP contexts that cannot be established as described in TS 23.060 [10].

13.4.3.4.3 Test description

13.4.3.4.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 5.

– 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 Registered, Idle mode (state 2) on Cell 1 according to [18].

13.4.3.4.3.2 Test procedure sequence

Table 13.4.3.5.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 after preamble, 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.4.3.4.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 5

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

The power level values are such that entering conditions for event B2 are not satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-88

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-88

T1

Cell-specific RS EPRE

dBm/15kHz

-84

The power level values are such that entering conditions for event B2 are satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

T2

Cell-specific RS EPRE

dBm/15kHz

-60

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

“Off”

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

“Off”

NOTE 1: Power level “Off” for Cell 5 is defined in TS 34.108 [5] Table 6.1.4

Table 13.4.3.4.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures UTRA cell 5 to reference configuration according 36.508 table 4.8.3-1, condition UTRA Speech.

2-25

Steps 1 to 24 of the generic test procedure for IMS MT speech call (TS 36.508 4.5A.7.3-1).

26-27

Void

28

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter RAT measurement and reporting for event B2.

<–

RRCConnectionReconfiguration

29

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

30

The SS changes the power level for Cell 1 and Cell 5 according to the row "T1" in table 13.4.3.4.3.2-1

31

The UE transmits a MeasurementReport message on Cell 1 to report event B2 for Cell 5.

–>

MeasurementReport

32

The SS changes the power level for Cell 1 and Cell 5 according to the row "T2" in table 13.4.3.4.3.2-1

33

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

EXCEPTION: In parallel to the events described in step 34 to 39 the steps specified in table 13.4.3.4.3.2-4 take place if requested by the UE. The SS shall wait up to 3s for the UE to trigger the generic test procedure for media re-establishment.

NOTE: The specified wait period of 3s is a working assumption to facilitate test case implementation.

34

The UE transmits an RRCConnectionReestablishmentRequest on Cell 1.

–>

RRCConnectionReestablishmentRequest

1

P

35

The SS transmits an RRCConnectionReestablishment message on Cell 1.

<–

RRCConnectionReestablishment

36

The UE transmits an RRCConnectionReestablishmentComplete on Cell 1

–>

RRCConnectionReestablishmentComplete

37

The SS transmits an RRCConnectionReconfiguration message to resume existing radio bearers.

<–

RRCConnectionReconfiguration

38

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationtComplete

39

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

2

P

40

Generic test procedure for MT release of IMS call as described in annex C.33 of TS 34.229-1 [35] takes place.

Table 13.4.3.4.3.2-3: Void

Table 13.4.3.4.3.2-4: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-4

Steps 1 to 4 of the generic test procedure for media re-establishment after unsuccessful SRVCC handover (TS 34.229-1 [35], C31).

13.4.3.4.3.3 Specific message contents

Table 13.4.3.4.3.3-0: Conditions for specific message contents
in Table 13.4.3.4.3.3-3

Condition

Explanation

Band > 64

If band > 64 is selected

Table 13.4.3.4.3.3-1: ATTACH REQUEST (preamble)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/remark

Comment

Condition

MS network capability

SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported

Mobile station classmark 2

Any allowed value

Supported Codecs

Any allowed value

Table 13.4.3.4.3.3-2: RRCConnectionReconfiguration (step28, Table 13.4.3.4.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 13.4.3.4.3.3-3: MeasConfig (step28, Table 13.4.3.4.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition UTRAN

Information Element

Value/Remark

Comment

Condition

measurementConfiguration ::= SEQUENCE {

measObjectToAddModifyList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f8

measObject[1]

MeasObjectUTRA-GENERIC(f8)

measObjectId[2]

IdMeasObject-f1

measObject[2]

MeasObjectEUTRA-GENERIC(f1)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModifyList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfigInterRAT-B2-UTRA

reportConfig[1]

ReportConfigInterRAT-B2-UTRA (-72, -76)

}

measIdToAddModifyList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f8

reportConfigId[1]

IdReportConfigInterRAT-B2-UTRA

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Table 13.4.3.4.3.3-4: MeasurementReport (step31, Table 13.4.3.4.3.2-2)

Derivation Path: 36.508, table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 5

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

utra-RSCP

(-5..91)

}

}

}

}

}

}

}

}

Table 13.4.3.4.3.3-5: MobilityFromEUTRACommand (step 33, Table 13.4.3.4.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

cs-FallbackIndicator

False

purpose CHOICE{

handover SEQUENCE {

targetRAT-Type

Utra

targetRAT-MessageContainer

HANDOVER TO UTRAN COMMAND(UTRA RRC message)

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

}

}

}

}

Table 13.4.3.4.3.3-6: HANDOVER TO UTRAN COMMAND (step33, Table 13.4.3.4.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-1, condition UTRA Speech

Table 13.4.3.4.3.3-7: RRCConnectionReestablishmentRequest (step34, Table 13.4.3.4.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

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

handoverFailure

spare

Present but contents not checked

}

}

}

Table 13.4.3.4.3.3-8: RRCConnectionReconfiguration (step 37, Table 13.4.3.4.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

}

}

}

}

Table 13.4.3.4.3.3-9: Void

Table 13.4.3.4.3.3-10: Void

13.4.3.5 Inter-system mobility / E-UTRA voice to GSM CS voice / Unsuccessful case / Retry on old cell / SRVCC

13.4.3.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and an IMS voice call is ongoing and the UE does not succeed in establishing the connection to the target radio access technology }

then { UE initiates the connection re-establishment procedure }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE successfully completes the RRC Connection re-establishment procedure }

then { UE is in E-UTRA RRC_CONNECTED state }

}

13.4.3.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3, 5.4.3.5, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.5 and TS 23.216, clause 6.2.2.1.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover‘:

2> if the targetRAT-Type is set to ‘utra‘ or ‘geran‘:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

  1. access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 36.331, clause 5.4.3.5]

The UE shall:

1> if T304 expires (mobility from E-UTRA failure); or

1> if the UE does not succeed in establishing the connection to the target radio access technology; or

1> if the UE is unable to comply with (part of) the configuration included in the MobilityFromEUTRACommand message; or

1> if there is a protocol error in the inter RAT information included in the MobilityFromEUTRACommand message, causing the UE to fail the procedure according to the specifications applicable for the target RAT:

2> stop T304, if running;

2> if the cs-FallbackIndicator in the MobilityFromEUTRACommand message was set to ‘TRUE‘:

3> indicate to upper layers that the CS Fallback procedure has failed;

2> revert back to the configuration used in the source cell, excluding the configuration configured by the physicalConfigDedicated, mac-MainConfig and sps-Config;

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

[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 mobility from E-UTRA failure, in accordance with 5.4.3.5; or

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;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> 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 a suitable E-UTRA cell, the UE shall:

1> stop timer T311;

1> start timer T301;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> initiate transmission of the RRCConnectionReestablishmentRequest message in accordance with 5.3.7.4;

NOTE: This procedure applies also if the UE returns to the source cell.

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.7.4]

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

1> set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases); and

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

1> set the reestablishmentCause as follows:

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure‘;

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

[TS 36.331, clause 5.3.7.5]

The UE shall:

1> stop timer T301;

1> re-establish PDCP for SRB1;

1> re-establish RLC for SRB1;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> resume SRB1;

1> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

  1. set the content of RRCConnectionReestablishmentComplete message as follows:

2> include the rlf-InfoAvailable and set it to true, if the UE has radio link failure information available that is related to the last occurrence of radio link failure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the procedure ends;

[TS 23.216, clause 6.2.2.1]

Depicted in figure 6.2.2.1-1 is a call flow for SRVCC from E-UTRAN to GERAN without DTM support. The flow requires that eNB can determine that the target is GERAN without DTM support or that the UE is without DTM support.

Figure 6.2.2.1-1: SRVCC from E-UTRAN to GERAN without DTM support

1. UE sends measurement reports to E-UTRAN.

2. Based on UE measurement reports the source E‑UTRAN decides to trigger an SRVCC handover to GERAN.

3. Source E‑UTRAN sends Handover Required (Target ID, generic Source to Target Transparent Container, SRVCC HO Indication) message to the source MME. The E‑UTRAN places the "old BSS to new BSS information IE" for the CS domain in the generic Source to Target Transparent Container. The SRVCC HO indication indicates to the MME that target is only CS capable, hence this is a SRVCC handover operation only towards the CS domain. The message includes an indication that the UE is not available for the PS service in the target cell.

4. Based on the QCI associated with the voice bearer (QCI 1) and the SRVCC HO indication, the source MME splits the voice bearer from the non voice bearers and initiates the PS-CS handover procedure for the voice bearer only towards MSC Server.

5. The MME sends a SRVCC PS to CS Request (IMSI, Target ID, STN-SR, C‑MSISDN, generic Source to Target Transparent Container, MM Context, Emergency Indication) message to the MSC Server. The Emergency Indication and the equipment identifier are is included if the ongoing session is emergency session. Authenticated IMSI and C‑MSISDN shall also be included, if available. The MME received STN-SR and C‑MSISDN from the HSS as part of the subscription profile downloaded during the E‑UTRAN attach procedure. The MM Context contains security related information. CS security key is derived by the MME from the E‑UTRAN/EPS domain key as defined in TS 33.401 [22]. The CS Security key is sent in the MM Context.

6. The MSC Server interworks the PS-CS handover request with a CS inter‑MSC handover request by sending a Prepare Handover Request message to the target MSC. The MSC Server assigns a default SAI as Source ID on the interface to the target BSS and uses BSSMAP encapsulated for the Prepare Handover Request.

NOTE 1: The value of the default SAI is configured in the MSC and allows a release 8 and later BSC to identify that the source for the SRVCC Handover is E-UTRAN. To ensure correct statistics in the target BSS the default SAI should be different from the SAIs used in UTRAN.

7. Target MSC performs resource allocation with the target BSS by exchanging Handover Request/ Acknowledge messages.

8. Target MSC sends a Prepare Handover Response message to the MSC Server.

9. Establishment of circuit connection between the target MSC and the MGW associated with the MSC Server e.g. using ISUP IAM and ACM messages.

10. For non-emergency session, the MSC Server initiates the Session Transfer by using the STN-SR e.g. by sending an ISUP IAM (STN-SR) message towards the IMS. For emergency session, the MSC Server initiates the Session Transfer by using the locally configured E-STN-SR and by including the equipment identifier. Standard IMS Service Continuity or Emergency IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.237 [14].

NOTE 2: This step can be started after step 8.

NOTE 3: If the MSC Server is using an ISUP interface, then the initiation of the session transfer for non-emergency session may fail if the subscriber profile including CAMEL triggers is not available prior handover (see clause 7.3.2.1.3 in TS 23.292 [13]).

11. During the execution of the Session Transfer procedure the remote end is updated with the SDP of the CS access leg. The downlink flow of VoIP packets is switched towards the CS access leg at this point.

12. Source IMS access leg is released as per TS 23.237 [14].

NOTE 4: Steps 11 and 12 are independent of step 13.

13. MSC Server sends a SRVCC PS to CS Response (Target to Source Transparent Container) message to the source MME.

14. Source MME sends a Handover Command (Target to Source Transparent Container) message to the source E-UTRAN. The message includes information about the voice component only.

15. Source E-UTRAN sends a Handover from E-UTRAN Command message to the UE.

16. UE tunes to GERAN.

17. Handover Detection at the target BSS occurs. The UE sends a Handover Complete message via the target BSS to the target MSC. If the target MSC is not the MSC Server, then the Target MSC sends an SES (Handover Complete) message to the MSC Server.

18. The UE starts the Suspend procedure specified in TS 23.060 [10], clause 16.2.1.1.2. The TLLI and RAI pair are derived from the GUTI as described in TS 23.003 [27]. This triggers the Target SGSN to send a Suspend Notification message to the Source MME. The MME returns a Suspend Acknowledge to the Target SGSN.

NOTE 5: The MME might not be able to derive the GUTI from the received P-TMSI and RAI pair and therefore it might not be able to identify which UE context is associated with the Suspend Notification message. Also in this case the bearers are deactivated and/or suspended as in step 22a.

19. Target BSS sends a Handover Complete message to the target MSC.

20. Target MSC sends an SES (Handover Complete) message to the MSC Server. The speech circuit is through connected in the MSC Server/MGW according to TS 23.009 [18].

21. Completion of the establishment procedure with ISUP Answer message to the MSC Server according to TS 23.009 [18].

22. MSC Server sends a SRVCC PS to CS Complete Notification message to the source MME, informing it that the UE has arrived on the target side. Source MME acknowledges the information by sending a SRVCC PS to CS Complete Acknowledge message to the MSC Server.

22a. The MME deactivates bearers used for voice and other GBR bearers. All GBR bearers are deactivated towards S-GW and P-GW by initiating MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401 [2]. The MME does not send deactivation request toward the eNodeB on receiving PS-to-CS Complete Notification in step 22. PS-to-CS handover indicator is notified to P-GW for voice bearer during the bearer deactivation procedure. For GTP-based S5/S8, the S-GW requests the P-GW to delete all GBR bearer contexts by sending a Delete Bearer Command message. If dynamic PCC is deployed, the P‑GW may interact with PCRF as defined in TS 23.203 [31]. For PMIP-based S5/S8, S-GW interacts with the PCRF which in turn updates PCC rules for GBR traffic in the P-GW.

The MME starts preservation and suspension of non-GBR bearers by sending Suspend Notification message towards S-GW. For these non-GBR bearers, the S-GW releases S1-U bearers for the UE and sends Suspend Notification message to the P-GW(s). The MME stores in the UE context that UE is in suspended status. All the preserved non-GBR bearers are marked as suspended status in the S-GW and P-GW. The P-GW should discard packets if received for the suspended UE.

23a. If the HLR is to be updated, i.e. if the IMSI is authenticated but unknown in the VLR, the MSC Server performs a TMSI reallocation towards the UE using its own non-broadcast LAI and, if the MSC Server and other MSC/VLRs serve the same (target) LAI, with its own Network Resource Identifier (NRI).

NOTE 5: The TMSI reallocation is performed by the MSC Server towards the UE via target MSC.

23b. If the MSC Server performed a TMSI reallocation in step 23a, and if this TMSI reallocation was completed successfully, the MSC Server performs a MAP Update Location to the HSS/HLR.

NOTE 6: This Update Location is not initiated by the UE.

24. For an emergency services session after handover is complete, the source MME or the MSC Server may send a Subscriber Location Report carrying the identity of the MSC Server to a GMLC associated with the source or target side, respectively, as defined in TS 23.271 [29] to support location continuity.

NOTE 7: Any configuration of the choice between a source MME versus MSC Server update to a GMLC needs to ensure that a single update occurs from one of these entities when the control plane location solution is used on the source and/or target sides.

13.4.3.5.3 Test description

13.4.3.5.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 24.

– 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 Registered, Idle mode (state 2) on Cell 1 according to [18].

13.4.3.5.3.2 Test procedure sequence

Table 13.4.3.5.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 after preamble, 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.4.3.5.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 24

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

The power level values are such that entering conditions for event B2 are not satisfied.

RSSI

dBm

-85

T1

Cell-specific RS EPRE

dBm/15kHz

-100

The power level values are such that entering conditions for event B2 are satisfied.

RSSI

dBm

-65

T2

Cell-specific RS EPRE

dBm/15kHz

-85

RSSI

dBm

“Off”

Table 13.4.3.5.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-24

Steps 1 to 24 of the generic test procedure for IMS MT speech call (TS 36.508 4.5A.7.3-1).

25-26

Void

27

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter RAT measurement and reporting for event B2.

<–

RRCConnectionReconfiguration

28

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

29

The SS changes the power level for Cell 1 and Cell 24 according to the row "T1" in table 13.4.3.5.3.2-1

30

The UE transmits a MeasurementReport message on Cell 1 to report event B2 for Cell 24.

–>

MeasurementReport

31

The SS changes the power level for Cell 1 and Cell 24 according to the row "T2" in table 13.4.3.5.3.2-1

32

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

EXCEPTION: In parallel to the events described in step 33 to 38 the steps specified in table 13.4.3.5.3.2-3 take place if requested by the UE. The SS shall wait up to 3s for the UE to trigger the generic test procedure for media re-establishment.

NOTE: The specified wait period of 3s is a working assumption to facilitate test case implementation.

33

The UE transmits an RRCConnectionReestablishmentRequest on Cell 1.

–>

RRCConnectionReestablishmentRequest

1

P

34

The SS transmits an RRCConnectionReestablishment message on Cell 1.

<–

RRCConnectionReestablishment

35

The UE transmits an RRCConnectionReestablishmentComplete on Cell 1

–>

RRCConnectionReestablishmentComplete

36

The SS transmits an RRCConnectionReconfiguration message to resume existing radio bearers.

<–

RRCConnectionReconfiguration

37

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationtComplete

38

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

2

P

39

Generic test procedure for MT release of IMS call as described in annex C.33 of TS 34.229-1 [35] takes place.

Table 13.4.3.5.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-4

Steps 1 to 4 of the generic test procedure for media re-establishment after unsuccessful SRVCC handover (TS 34.229-1 [35], C31).

13.4.3.5.3.3 Specific message contents

Table 13.4.3.5.3.3-1: ATTACH REQUEST (preamble)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/remark

Comment

Condition

MS network capability

SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported

Mobile station classmark 2

Any allowed value

Supported Codecs

Any allowed value

Table 13.4.3.5.3.3-2: RRCConnectionReconfiguration (step 27, Table 13.4.3.5.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 13.4.3.5.3.3-3: MeasConfig (step 27, Table 13.4.3.5.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition GERAN

Information Element

Value/Remark

Comment

Condition

measurementConfiguration ::= SEQUENCE {

measObjectToAddModifyList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f11

measObject[1]

MeasObjectGERAN-GENERIC(f11)

measObjectId[2]

IdMeasObject-f1

measObject[2]

MeasObjectEUTRA-GENERIC(f1)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModifyList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfigInterRAT-B2-GERAN

reportConfig[1]

ReportConfigInterRAT-B2-GERAN (-69, -94)

}

measIdToAddModifyList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f11

reportConfigId[1]

IdReportConfigInterRAT-B2-GERAN

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] ::= SEQUENCE {}

measObjectEUTRA-v9e0[1] ::= SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 13.4.3.5.3.3-4: MeasurementReport (step 30, Table 13.4.3.5.3.2-2)

Derivation Path: 36.508, table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListGERAN SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId

PhysicalCellIdentity of Cell 24

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rssi

The value of rssi is present but contents not checked

}

}

}

}

}

}

}

}

Table 13.4.3.5.3.3-5: MobilityFromEUTRACommand (step 32, Table 13.4.3.5.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

cs-FallbackIndicator

False

purpose CHOICE{

handover SEQUENCE {

targetRAT-Type

GERAN

targetRAT-MessageContainer

HANDOVER COMMAND(GERAN RRC message) , see Table 13.4.3.5.3.3-5a

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension

Not present

nonCriticalExtension SEQUENCE {

bandIndicator

Set according to the band used for Cell 24

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

Table 13.4.3.5.3.3-5a: HANDOVER COMMAND (step 32, Table 13.4.3.5.3.2-2)

Derivation Path: 51.01040.018, Table 40.2.4.339.1.15.1

Information Element

Value/remark

Comment

Condition

Cell Description

Network Colour Code

1

Base Station Colour Code

5

BCCH Carrier Number

The BCCH Carrier ARFCN as per table in clause 40.1.1 of 51.010-1.

Description of the First Channel, after time

Channel Description

Channel Type and TDMA offset

TCH/F + ACCH’s

Timeslot Number

Chosen arbitrarily, but not Zero.

Training Sequence Code

Same as the BCCH

Hopping channel

Single RF channel

ARFCN

The first ARFCN in the cell allocation as per table in clause 40.2.1.1.1 of 51.010-1

Cipher Mode Setting

1001xxxy

See TS 44.018 §9.1.15.10

xxx – px_GSM_CipherAlg

y – px_GSM_CipheringOnOff

Table 13.4.3.5.3.3-6: RRCConnectionReestablishmentRequest (step 33, Table 13.4.3.5.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

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

handoverFailure

spare

Present but contents not checked

}

}

}

Table 13.4.3.5.3.3-7: RRCConnectionReconfiguration (step 36, Table 13.4.3.5.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.4.3.6 Inter-system mobility / E-UTRA PS voice + PS Data / HO cancelled / Notification procedure / SRVCC

13.4.3.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a NOTIFICATION message and an IMS voice call is ongoing and an UTRA PS RB + Speech combination is configured for an UTRA cell}

then { UE transmits a SIP re-INVITE message on the e-utra cell}

}

13.4.3.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 23.216, clauses 8.1.3; TS 24.237, clause 12.2.4.1, 12.2.4.2; TS 24.301, clause 6.6.2.2; TS 24.301, clause 6.6.2.3

[TS 23.216, clause 8.1.3]

If the source E-UTRAN/UTRAN decides to terminate the handover procedure before its completion, the MME/SGSN shall return to its state before the handover procedure was triggered. The MME/SGSN attempts to trigger, at the MSC Server enhanced for SRVCC, handover cancellation procedures according to TS 23.009 [18]. The MSC Server enhanced for SRVCC shall take no SRVCC-specific action towards IMS.

The MME/SGSN shall also send a session reestablishment trigger notification to UE to start the recovery procedure if it receives notification from the MSC Server that the Session Transfer procedure is in progress. Figure 8.1.3-1 shows the overall procedure for SRVCC handover cancellation.

For vSRVCC the MME and MSC also behave the same way as in the case of SRVCC handover cancellation.

Figure 8.1.3-1: SRVCC Handover Cancellation Procedure

1. Network has started the SRVCC procedure. SGSN/MME has sent the SRVCC PS to CS request to MSC Server.

2. MSC Server is performing the CS HO procedure with target network, and has also started the Session Transfer procedure with IMS with STN-SR, see TS 23.237 [14].

3. Source UTRAN/E-UTRAN decides to cancel the SRVCC HO Procedure by sending a Cancel message to SGSN/MME.

4. Source SGSN/MME indicates SRVCC PS to CS Cancel Notification to MSC Server to start the HO cancellation procedure as according to TS 23.009 [18].

5. MSC Server acks the PS to CS Cancel Notification with an indication that Session Transfer procedure is in progress.

6. Due to the Session Transfer procedure in progress indication, the source SGSN/MME sends a Session Reestablishment trigger notification to UE to start the session re-establishment procedure

7. UE starts the re-establishment procedure, by attempting to return to E-UTRAN/UTRAN by sending a re-INVITE towards IMS for the related session. If the session is no longer active, then this session transfer request shall be rejected by the IMS.

[TS 24.237, clause 12.2.4.1]

If the SC UE engaged in one or more ongoing IMS sessions and:

– receives a SM NOTIFICATION message containing an "SRVCC handover cancelled, IMS session re-establishment required" as described in 3GPP TS 24.008 [8] or 3GPP TS 24.301 [52] depending on the access in use; or

– does not successfully retune to the 3GPP UTRAN or 3GPP GERAN after it receives the handover command from the eNodeB (as described in 3GPP TS 36.331 [62]) or from the NodeB (as described in 3GPP TS 25.331 [61]);

then the SC UE shall send a SIP re-INVITE request containing:

1) an SDP offer, including the media characteristics as used in the existing dialog; and

2) a Reason header field containing protocol "SIP" and reason parameter "cause" with value "487" as specified in IETF RFC 3326 [57] and with reason-text text set to either "handover cancelled" or "failure to transition to CS domain";

by following the rules of 3GPP TS 24.229 [2] in each transferred session.

[TS 24.237, clause 12.2.4.2]

If the SC UE is engaged in a session in early dialog state and:

– receives a SM NOTIFICATION message containing an "SRVCC handover cancelled, IMS session re-establishment required" as described in 3GPP TS 24.008 [8] or 3GPP TS 24.301 [52] depending on the access in use; or

– does not successfully retune to the 3GPP UTRAN or 3GPP GERAN after it receives the handover command from the eNodeB (as described in 3GPP TS 36.331 [62]) or from the NodeB (as described in 3GPP TS 25.331 [61]);

then the SC UE shall send a SIP UPDATE request containing:

1) an SDP offer, including the media characteristics as used in the existing dialog; and

2) a Reason header field containing protocol "SIP" and reason parameter "cause" with value "487" as specified in IETF RFC 3326 [57], and with reason-text set to either "handover cancelled" or "failure to transition to CS domain";

by following the rules of 3GPP TS 24.229 [2] in each transferred session.

[TS 24.301, clause 6.6.2.2]

The network initiates the notification procedure by sending a NOTIFICATION message to the UE (see example in figure 6.6.2.2.1).

Figure 6.6.2.2.1: Notification procedure

[TS 24.301, clause 6.6.2.3]

When the UE receives a NOTIFICATION message, the ESM protocol entity in the UE shall provide the notification indicator to the upper layer.

The notification indicator can have the following value:

#1: SRVCC handover cancelled, IMS session re-establishment required.

13.4.3.6.3 Test description

13.4.3.6.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 5.

– 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 Registered, Idle mode (state 2) on Cell 1 according to [18].

13.4.3.6.3.2 Test procedure sequence

Table 13.4.3.6.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 after preamble, while c

10AA

The SS transmits an DLInformationTransfer containing a tunnelled 1xRTT GCSNA encapsulated Registration Request order on Cell 2.

<–

DLInformationTransfer

olumns 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.4.3.6.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 5

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

The power level values are such that entering conditions for event B2 are not satisfied.

CPICH_Ec

(UTRA FDD)

dBm/3.84 MHz

-88

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-88

T1

Cell-specific RS EPRE

dBm/15kHz

-84

The power level values are such that entering conditions for event B2 are satisfied.

CPICH_Ec

(UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

Table 13.4.3.6.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures UTRA cell 5 to reference configuration according 36.508 table 4.8.3-1, condition UTRA PS RB + Speech.

2-27

Steps 1 to 26 of the generic test procedure for IMS MT speech call (TS 36.508 4.5A.7.3-1).

28

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter RAT measurement and reporting for event B2.

<–

RRCConnectionReconfiguration

29

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

30

The SS changes the power level for Cell 1 and Cell 5 according to the row "T1" in table 13.4.3.6.3.2-1

31

The UE transmits a MeasurementReport message on Cell 1 to report event B2 for Cell 5.

–>

MeasurementReport

32

The SS transmits a NOTIFICATION message on Cell 1.

<–

NOTIFICATION

33-36

Check: Does the UE perform steps 1 to 4 of the generic test procedure for media re-establishment after unsuccessful SRVCC handover (TS 34.229-1 [35], C31) and subsequently continues the call on EUTRA ?

(Note: Verdict assigned if SIP re-INVITE message is received in step 1 of TS 34.229-1, C.31).

1

P

37

Generic test procedure for MT release of IMS call as described in annex C.33 of TS 34.229-1 [35] takes place.

13.4.3.6.3.3 Specific message contents

Table 13.4.3.6.3.3-0: Conditions for specific message contents
in Table 13.4.3.6.3.3-3

Condition

Explanation

Band > 64

If band > 64 is selected

Table 13.4.3.6.3.3-1: ATTACH REQUEST (preamble)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/remark

Comment

Condition

MS network capability

SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported

Mobile station classmark 2

Any allowed value

Supported Codecs

Any allowed value

Table 13.4.3.6.3.3-2: RRCConnectionReconfiguration (step28, Table 13.4.3.6.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 13.4.3.6.3.3-3: MeasConfig (step28, Table 13.4.3.6.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition UTRAN

Information Element

Value/Remark

Comment

Condition

measurementConfiguration ::= SEQUENCE {

measObjectToAddModifyList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f8

measObject[1]

MeasObjectUTRA-GENERIC(f8)

measObjectId[2]

IdMeasObject-f1

measObject[2]

MeasObjectEUTRA-GENERIC(f1)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModifyList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfigInterRAT-B2-UTRA

reportConfig[1]

ReportConfigInterRAT-B2-UTRA(-72, -76)

}

measIdToAddModifyList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f8

reportConfigId[1]

IdReportConfigInterRAT-B2-UTRA

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Table 13.4.3.6.3.3-4: MeasurementReport (step31, Table 13.4.3.6.3.2-2)

Derivation Path: 36.508, table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 5

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

utra-RSCP

(-5..91)

}

}

}

}

}

}

}

}

Table 13.4.3.6.3.3-5: NOTIFICATION (step32, Table 13.4.3.6.3.2-2)

Notification Indicator

01 “SRVCC handover cancelled, IMS session re-establishment required”

Table 13.4.3.6.3.3-6: Void

13.4.3.7 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MO call

13.4.3.7.1 Test Purpose (TP)

(1)

with { UE is in E-UTRA RRC_CONNECTED state and an IMS MO speech call is in alerting phase }

ensure that {

when { UE receives a MobilityFromEUTRACommand message }

then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the UTRA cell }

}

(2)

with { UE is in UTRA CELL_DCH state and an SRVCC procedure for MO call in alerting phase is completed }

ensure that {

when { UE receives a CONNECT message }

then { UE transmits a CONNECT ACKNOWLEDGE message }

}

13.4.3.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3, TS 23.237, clause 6.3.2.1.4d, TS 23.216, clause 6.2.2.2, TS 24.237, clauses 12.1, 12.2.3B.1, 12.2.3B.2, 12.2.3B.3.2, and TS 24.008, clause 5.2.4.2.

[TS 36.331, clause 5.4.3.3]

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to handover:

2> if the targetRAT-Type is set to utra or geran:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 23.237, clause 6.3.2.1.4d]

Figure 6.3.2.1.4d-1 PS-CS: PS to CS – Single Radio, outgoing call in alerting phase, provides an information flow for Access Transfer of media of an IMS session in PS to CS direction for Access Transfers as specified in TS 23.216 [10].

The flow requires that the user is active in an outgoing IMS session and that the SIP session is in alerting state and there is no other ongoing session; procedures and capabilities specified in TS 23.216 [10], clause 6.2.1 are used for the switching of access networks at the transport layer. It further requires that the MSC Server supports I2 reference point.

Figure 6.3.2.1.4d-1: PS-CS: PS to CS – Single Radio, outgoing call in alerting phase

1-4. Standard procedures are used to initiate a SIP session from the UE towards the remote end. The remote end is alerting the user for the incoming voice session.

10. The MSC moves to the corresponding CS call state, e.g. Call Delivered in TS 24.008 [24].

10b. In parallel to step 10, the UE has received the HO command as described in TS 23.216 [10]. The UE determines the local call state in the SIP session, and creates the corresponding CS call state, e.g. Call Delivered in TS 24.008 [24]. The UE ensures that the same ring back tone is played to the end user.

14. The MSC uses the standard procedure to send the CS connect message to UE as e.g. described in TS 24.008 [24].

15. The MSC moves to Active state.

16. The UE moves to Active state.

[TS 23.216, clause 6.2.2.2]

Depicted in figure 6.2.2.2-1 is a call flow for SRVCC from E‑UTRAN to UTRAN or GERAN with DTM HO support, including the handling of the non‑voice component. The flow requires that eNB can determine that either the target is UTRAN with PS HO or the target is GERAN with DTM support and the UE is supporting DTM.

Figure 6.2.2.2-1: SRVCC from E-UTRAN to UTRAN with PS HO or GERAN with DTM HO support

1. UE sends measurement reports to E-UTRAN.

14. E‑UTRAN sends a Handover from E‑UTRAN Command message to the UE.

15. UE tunes to the target UTRAN/GERAN cell.

16. Handover Detection at the target RNS/BSS occurs. The UE sends a Handover Complete message via the target RNS/BSS to the target MSC. If the target MSC is not the MSC Server, then the Target MSC sends an SES (Handover Complete) message to the MSC Server. At this stage, the UE re-establishes the connection with the network and can send/receive voice data.

17. The CS relocation/handover is complete. The following steps are performed:

a) Target RNS/BSS sends Relocation Complete/Handover Complete message to the target MSC.

b) Target MSC sends an SES (Handover Complete) message to the MSC Server. The speech circuit is through connected in the MSC Server/MGW according to TS 23.009 [18].

c) Completion of the establishment procedure with ISUP Answer message to the MSC Server according to TS 23.009 [18].

d) MSC Server sends a SRVCC PS to CS Complete Notification message to the source MME. Source MME acknowledges the information by sending a SRVCC PS to CS Complete Acknowledge message to the MSC Server.

e) The source MME deactivates the voice bearer towards S-GW/P-GW and sets the PS-to-CS handover indicator to Delete Bearer Command message. This triggers MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401 [2]. The MME does not send deactivation request toward the eNodeB on receiving PS-to-CS Complete Notification in step 17d. If dynamic PCC is deployed, the PGW may interact with PCRF as defined in TS 23.203 [31].

f) If the HLR is to be updated, i.e. if the IMSI is authenticated but unknown in the VLR, the MSC Server performs a TMSI reallocation towards the UE using its own non-broadcast LAI and, if the MSC Server and other MSC/VLRs serve the same (target) LAI, with its own Network Resource Identifier (NRI).

NOTE 9: The TMSI reallocation is performed by the MSC Server towards the UE via target MSC.

g) If the MSC Server performed a TMSI reallocation in step 17f, and if this TMSI reallocation was completed successfully, the MSC Server performs a MAP Update Location to the HSS/HLR.

NOTE 10: This Update Location is not initiated by the UE.

[TS 24.237, clause 12.1]

In order to fulfil the requirements for PS-CS access transfer in SR-VCC for calls in alerting state, the SC UE needs to be engaged in a session with speech media component in early dialog state according to the following conditions before SR-VCC access transfer is performed:

– a SIP 180 (Ringing) response for the initial SIP INVITE request to establish this session has been sent or received; and

– a SIP final response for the initial SIP INVITE request to establish this session has not been sent or received.

[TS 24.237, clause 12.2.3B.1]

The SC UE shall apply the procedures in subclauses 12.2.3B.3 for access transfer for calls in alerting state if:

1) the SC UE supports single radio PS to CS access transfer for calls in alerting state; and

2) there are one or more early dialogs created by the same SIP INVITE request with at least one dialog that is an early dialog supporting a session with active speech media component where the SC UE:

– has sent a Contact header field in a SIP INVITE request or 180 (Ringing) response containing the g.3gpp.srvcc-alerting media feature tag (as described in annex C); and

– has received a Feature-Caps header field in a SIP INVITE request or 180 (Ringing) response containing the g.3gpp.srvcc-alerting feature capability indicator (as described in annex C).

[TS 24.237, clause 12.2.3B.2]

If the SC UE applies the procedures in subclause 12.2.3B.3 and the SC UE only has a single call in alerting state following access transfer, then the SC UE shall associate this session with transaction identifier value and TI flag as described in 3GPP TS 24.008 [8].

[TS 24.237, clause 12.2.3B.3.2]

If the SC UE has initiated an outgoing call which is in the early dialog state according to the conditions in subclauses 12.1 and 12.2.3B.1 and the SC UE successfully performs access transfer to the CS domain, then the UE continues in Ringing state in CS, i.e. UE moves to Call Delivered (U4) state as described in 3GPP TS 24.008 [8].

[TS 24.008, clause 5.2.4.2]

If the MS supports single radio PS to CS access transfer for calls in alerting state as specified in 3GPP TS 24.237 [136] subclause 12.2.3B, and the MS has a single voice media stream over the PS domain that is handed over to the CS domain via SRVCC, and the call control entity in "null" state receives an indication "MM connection establishment due to SRVCC handover", then:

– if the voice media stream is associated with a mobile originated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237 [136] subclause 12.2.3B.3.2, the call control entity of the MS shall enter the "call delivered" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call; and

If the MS has additional voice media streams carried over the PS domain that are handed over to the CS domain via SRVCC, the state for the transactions and the setting of the TI value and TI flag for these additional media streams is described in 3GPP TS 24.237 [136].

13.4.3.7.3 Test description

13.4.3.7.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 5.

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

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) on Cell 1 according to [18].

13.4.3.7.3.2 Test procedure sequence

Table 13.4.3.7.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 after preamble, 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.4.3.7.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 5

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

The power level values are such that entering conditions for event B2 are not satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-88

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-88

T1

Cell-specific RS EPRE

dBm/15kHz

-84

The power level values are such that entering conditions for event B2 are satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

T2

Cell-specific RS EPRE

dBm/15kHz

Non-suitable “Off”

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

Table 13.4.3.7.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures UTRA Cell 5 to reference configuration according 36.508 Table 4.8.3-1, condition UTRA Speech.

2-13

Steps 1 to 12 of the generic test procedure for IMS MO speech call (TS 36.508 4.5A.6.3-1).

EXCEPTION: In parallel to the events described in steps 14 to 15 the steps specified in Table 13.4.3.7.3.2-3 should take place.

14

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the establishment of the new data radio bearer, associated with the dedicated EPS bearer.

–>

RRCConnectionReconfigurationComplete

15

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message on Cell 1.

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

16

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter-RAT measurement and reporting for event B2.

<–

RRCConnectionReconfiguration

17

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

18

The SS changes the power level for Cell 1 and Cell 5 according to the row "T1" in Table 13.4.3.7.3.2-1.

19

The UE transmits a MeasurementReport message on Cell 1 to report event B2 for Cell 5.

–>

MeasurementReport

20

The SS transmits a UECapabilityEnquiry message on Cell 1 to request UE radio access capability information for E-UTRA and UTRA.

<–

UECapabilityEnquiry

21

The UE transmits a UECapabilityInformation message on Cell 1.

NOTE: The start-CS values received, should be used to configure ciphering on Cell 5.

–>

UECapabilityInformation

22

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

23

Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message on Cell 5?

–>

HANDOVER TO UTRAN COMPLETE

1

P

EXCEPTION: In parallel to the events described in step 24 to 29 the steps specified in Table 13.4.3.7.3.2-4 takes place.

24

The SS transmits a SECURITY MODE COMMAND message for the CS domain on Cell 5.

<–

SECURITY MODE COMMAND

25

The UE transmits a SECURITY MODE COMPLETE message on Cell 5.

–>

SECURITY MODE COMPLETE

26

The SS transmits an UTRAN MOBILITY INFORMATION message on Cell 5 to notify CN information.

<–

UTRAN MOBILITY INFORMATION

27

The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message on Cell 5.

–>

UTRAN MOBILITY INFORMATION CONFIRM

28

The SS transmits a TMSI REALLOCATION COMMAND message on Cell 5.

<–

TMSI REALLOCATION COMMAND

29

The UE transmits a TMSI REALLOCATION COMPLETE message on Cell 5.

–>

TMSI REALLOCATION COMPLETE

30

The SS transmits a CONNECT message on Cell 5.

<–

CONNECT

31

Check: Does the UE transmit a CONNECT ACKNOWLEDGE message on Cell 5?

–>

CONNECT ACKNOWLEDGE

2

P

40

SS adjusts cell levels according to row T2 of table 13.4.3.7.3.2-1.

The UE is in end state UTRA CS call (U5).

Table 13.4.3.7.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-7

Steps 5-11 expected sequence defined in annex C.21 of TS 34.229-1 [35].

NOTE: IMS MO speech call is in alerting phase.

Table 13.4.3.7.3.2-4: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a ROUTING AREA UPDATE REQUEST message on Cell 5.

–>

ROUTING AREA UPDATE REQUEST

2

The SS transmits a SECURITY MODE COMMAND message for the PS domain on Cell 5.

<–

SECURITY MODE COMMAND

3

The UE transmits a SECURITY MODE COMPLETE message on Cell 5.

–>

SECURITY MODE COMPLETE

4

The SS transmits a ROUTING AREA UPDATE ACCEPT message on Cell 5.

<–

ROUTING AREA UPDATE ACCEPT

5

The UE transmits a ROUTING AREA UPDATE COMPLETE message on Cell 5.

–>

ROUTING AREA UPDATE COMPLETE

13.4.3.7.3.3 Specific message contents

Table 13.4.3.7.3.3-0: Conditions for specific message contents
in Table 13.4.3.7.3.3-3

Condition

Explanation

Band > 64

If band > 64 is selected

Table 13.4.3.7.3.3-1: ATTACH REQUEST (preamble)

Derivation path: 36.508 Table 4.7.2-4

Information Element

Value/remark

Comment

Condition

MS network capability

SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported

Mobile station classmark 2

Any allowed value

Supported Codecs

Any allowed value

Table 13.4.3.7.3.3-2: RRCConnectionReconfiguration (step 16, Table 13.4.3.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 13.4.3.7.3.3-3: MeasConfig (Table 13.4.3.7.3.3-2)

Derivation Path: 36.508, Table 4.6.6-1, condition UTRAN

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f8

measObject[2]

MeasObjectUTRA-f8

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-B2-UTRA

reportConfig[1]

ReportConfigInterRAT-B2-UTRA (-72, -76)

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f8

reportConfigId[1]

IdReportConfig-B2-UTRA

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

    measObjectEUTRA-v9e0[2] SEQUENCE {}

}

}

Table 13.4.3.7.3.3-4: MeasObjectUTRA-f8 (Table 13.4.3.7.3.3-3)

Derivation Path: 36.508, Table 4.6.6-3

Information Element

Value/remark

Comment

Condition

MeasObjectUTRA ::= SEQUENCE {

carrierFreq

Same downlink ARFCN as used for Cell 5

cellsToAddModList CHOICE {

cellsToAddModListUTRA-FDD SEQUENCE (SIZE (1..maxCellMeas)) OF SEQUENCE {

1 entry

UTRA-FDD

cellIndex[1]

1

physCellId[1]

PhysicalCellIdentity of Cell 5

}

cellsToAddModListUTRA-TDD SEQUENCE (SIZE (1..maxCellMeas)) OF SEQUENCE {

UTRA-TDD

cellIndex[1]

1

physCellId[1]

PhysicalCellIdentity of Cell 5

}

}

csg-allowedReportingCells-v930

Not present

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 13.4.3.7.3.3-5: MeasurementReport (step 19, Table 13.4.3.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1] CHOICE {

fdd

PhysicalCellIdentity of Cell 5

UTRA-FDD

tdd

PhysicalCellIdentity of Cell 5

UTRA-TDD

}

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

utra-RSCP

(-5..91)

utra-EcN0

Not present

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10

Not present

}

}

}

}

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 13.4.3.7.3.3-6: UECapabilityEnquiry (step 20, Table 13.4.3.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-22

Information Element

Value/remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

2 entries

RAT-Type[1]

eutra

RAT-Type[2]

utra

}

}

}

}

}

Table 13.4.3.7.3.3-7: MobilityFromEUTRACommand (step 22, Table 13.4.3.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

mobilityFromEUTRACommand-r8 SEQUENCE {

cs-FallbackIndicator

False

purpose CHOICE {

handover SEQUENCE {

targetRAT-Type

utra

targetRAT-MessageContainer

HANDOVER TO UTRAN COMMAND(UTRA RRC message)

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

}

}

}

}

Table 13.4.3.7.3.3-8: HANDOVER TO UTRAN COMMAND (Table 13.4.3.7.3.3-7)

Derivation Path: 36.508, Table 4.7B.1-1, condition UTRA Speech

Table 13.4.3.7.3.3-9: SECURITY MODE COMMAND (step 24, Table 13.4.3.7.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-n

Information Element

Value/remark

Comment

Condition

Ciphering mode info

Not present

Table 13.4.3.7.3.3-10: CONNECT (step 30, Table 13.4.3.7.3.2-2)

Derivation Path: TS 24.008 Table 9.59

Information Element

Value/remark

Comment

Condition

Transaction identifier

TI flag

‘0’B

The message is sent from the side that originates the TI

TIO

‘000’B

TI value 0

Table 13.4.3.7.3.3-11: CONNECT ACKNOWLEDGE (step 31, Table 13.4.3.7.3.2-2)

Derivation Path: TS 24.008 Table 9.60

Information Element

Value/remark

Comment

Condition

Transaction identifier

TI flag

‘1’B

The message is sent to the side that originates the TI

TIO

‘000’B

TI value 0

Table 13.4.3.7.3.3-12: ROUTING AREA UPDATE ACCEPT (step 4, Table 13.4.3.7.3.2-4)

Derivation path: 36.508, Table 4.7B.2-2

Information Element

Value/Remark

Comment

Condition

PDP context status

0

NSAPI(0) – NSAPI(15) is set to 0, which means that the SM state of all PDP contexts is PDP-INACTIVE

13.4.3.8 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MO call / Forked responses

13.4.3.8.1 Test Purpose (TP)

(1)

with { UE is in E-UTRA RRC_CONNECTED state, an IMS MO speech call is in alerting phase and UE has received several SIP forked responses }

ensure that {
when { UE receives a MobilityFromEUTRACommand message }

then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the UTRA cell }

}

(2)

with { UE is in UTRA CELL_DCH state and an SRVCC procedure for MO call in alerting phase is completed }

ensure that {
when { UE receives a CONNECT message }

then { UE transmits a CONNECT ACKNOWLEDGE message }

}

13.4.3.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3, TS 23.237, clause 6.3.2.1.4d, TS 23.216, clause 6.2.2.2, TS 24.237, clauses 12.1, 12.2.3B.1, 12.2.3B.2, 12.2.3B.3.2, A.17.6 and TS 24.008, clause 5.2.4.2.

[TS 36.331, clause 5.4.3.3]

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to handover:

2> if the targetRAT-Type is set to utra or geran:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 23.237, clause 6.3.2.1.4d]

Figure 6.3.2.1.4d-1 PS-CS: PS to CS – Single Radio, outgoing call in alerting phase, provides an information flow for Access Transfer of media of an IMS session in PS to CS direction for Access Transfers as specified in TS 23.216 [10].

The flow requires that the user is active in an outgoing IMS session and that the SIP session is in alerting state and there is no other ongoing session; procedures and capabilities specified in TS 23.216 [10], clause 6.2.1 are used for the switching of access networks at the transport layer. It further requires that the MSC Server supports I2 reference point.

Figure 6.3.2.1.4d-1: PS-CS: PS to CS – Single Radio, outgoing call in alerting phase

1-4. Standard procedures are used to initiate a SIP session from the UE towards the remote end. The remote end is alerting the user for the incoming voice session.

10. The MSC moves to the corresponding CS call state, e.g. Call Delivered in TS 24.008 [24].

10b. In parallel to step 10, the UE has received the HO command as described in TS 23.216 [10]. The UE determines the local call state in the SIP session, and creates the corresponding CS call state, e.g. Call Delivered in TS 24.008 [24]. The UE ensures that the same ring back tone is played to the end user.

14. The MSC uses the standard procedure to send the CS connect message to UE as e.g. described in TS 24.008 [24].

15. The MSC moves to Active state.

16. The UE moves to Active state.

[TS 23.216, clause 6.2.2.2]

Depicted in figure 6.2.2.2-1 is a call flow for SRVCC from E‑UTRAN to UTRAN or GERAN with DTM HO support, including the handling of the non‑voice component. The flow requires that eNB can determine that either the target is UTRAN with PS HO or the target is GERAN with DTM support and the UE is supporting DTM.

Figure 6.2.2.2-1: SRVCC from E-UTRAN to UTRAN with PS HO or GERAN with DTM HO support

1. UE sends measurement reports to E-UTRAN.

14. E‑UTRAN sends a Handover from E‑UTRAN Command message to the UE.

15. UE tunes to the target UTRAN/GERAN cell.

16. Handover Detection at the target RNS/BSS occurs. The UE sends a Handover Complete message via the target RNS/BSS to the target MSC. If the target MSC is not the MSC Server, then the Target MSC sends an SES (Handover Complete) message to the MSC Server. At this stage, the UE re-establishes the connection with the network and can send/receive voice data.

17. The CS relocation/handover is complete. The following steps are performed:

a) Target RNS/BSS sends Relocation Complete/Handover Complete message to the target MSC.

b) Target MSC sends an SES (Handover Complete) message to the MSC Server. The speech circuit is through connected in the MSC Server/MGW according to TS 23.009 [18].

c) Completion of the establishment procedure with ISUP Answer message to the MSC Server according to TS 23.009 [18].

d) MSC Server sends a SRVCC PS to CS Complete Notification message to the source MME. Source MME acknowledges the information by sending a SRVCC PS to CS Complete Acknowledge message to the MSC Server.

e) The source MME deactivates the voice bearer towards S-GW/P-GW and sets the PS-to-CS handover indicator to Delete Bearer Command message. This triggers MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401 [2]. The MME does not send deactivation request toward the eNodeB on receiving PS-to-CS Complete Notification in step 17d. If dynamic PCC is deployed, the PGW may interact with PCRF as defined in TS 23.203 [31].

f) If the HLR is to be updated, i.e. if the IMSI is authenticated but unknown in the VLR, the MSC Server performs a TMSI reallocation towards the UE using its own non-broadcast LAI and, if the MSC Server and other MSC/VLRs serve the same (target) LAI, with its own Network Resource Identifier (NRI).

NOTE 9: The TMSI reallocation is performed by the MSC Server towards the UE via target MSC.

g) If the MSC Server performed a TMSI reallocation in step 17f, and if this TMSI reallocation was completed successfully, the MSC Server performs a MAP Update Location to the HSS/HLR.

NOTE 10: This Update Location is not initiated by the UE.

[TS 24.237, clause 12.1]

In order to fulfil the requirements for PS-CS access transfer in SR-VCC for calls in alerting state, the SC UE needs to be engaged in a session with speech media component in early dialog state according to the following conditions before SR-VCC access transfer is performed:

– a SIP 180 (Ringing) response for the initial SIP INVITE request to establish this session has been sent or received; and

– a SIP final response for the initial SIP INVITE request to establish this session has not been sent or received.

[TS 24.237, clause 12.2.3B.1]

The SC UE shall apply the procedures in subclauses 12.2.3B.3 for access transfer for calls in alerting state if:

1) the SC UE supports single radio PS to CS access transfer for calls in alerting state; and

2) there are one or more early dialogs created by the same SIP INVITE request with at least one dialog that is an early dialog supporting a session with active speech media component where the SC UE:

– has sent a Contact header field in a SIP INVITE request or 180 (Ringing) response containing the g.3gpp.srvcc-alerting media feature tag (as described in annex C); and

– has received a Feature-Caps header field in a SIP INVITE request or 180 (Ringing) response containing the g.3gpp.srvcc-alerting feature capability indicator (as described in annex C).

[TS 24.237, clause 12.2.3B.2]

If the SC UE applies the procedures in subclause 12.2.3B.3 and the SC UE only has a single call in alerting state following access transfer, then the SC UE shall associate this session with transaction identifier value and TI flag as described in 3GPP TS 24.008 [8].

[TS 24.237, clause 12.2.3B.3.2]

If the SC UE has initiated an outgoing call which is in the early dialog state according to the conditions in subclauses 12.1 and 12.2.3B.1 and the SC UE successfully performs access transfer to the CS domain, then the UE continues in Ringing state in CS, i.e. UE moves to Call Delivered (U4) state as described in 3GPP TS 24.008 [8].

[TS 24.237, clause A.17.6]

In the example flow at the figure A.17.6-1, SC UE A initiates an originating session with speech media component which has received several forked responses. The call is anchored at SCC AS and in alerting phase. Based upon measurement reports sent from the UE to E-UTRAN, the source E-UTRAN decides to trigger a SRVCC handover to CS access.

Figure A.17.6-1: PS-CS SRVCC, incoming call in alerting phase with forked responses

[TS 24.008, clause 5.2.4.2]

If the MS supports single radio PS to CS access transfer for calls in alerting state as specified in 3GPP TS 24.237 [136] subclause 12.2.3B, and the MS has a single voice media stream over the PS domain that is handed over to the CS domain via SRVCC, and the call control entity in "null" state receives an indication "MM connection establishment due to SRVCC handover", then:

– if the voice media stream is associated with a mobile originated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237 [136] subclause 12.2.3B.3.2, the call control entity of the MS shall enter the "call delivered" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call; and

If the MS has additional voice media streams carried over the PS domain that are handed over to the CS domain via SRVCC, the state for the transactions and the setting of the TI value and TI flag for these additional media streams is described in 3GPP TS 24.237 [136].

13.4.3.8.3 Test description

13.4.3.8.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 5.

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

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) on Cell 1 according to [18].

13.4.3.8.3.2 Test procedure sequence

Table 13.4.3.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 after preamble, 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.4.3.8.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 5

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

The power level values are such that entering conditions for event B2 are not satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-88

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-88

T1

Cell-specific RS EPRE

dBm/15kHz

-84

The power level values are such that entering conditions for event B2 are satisfied.

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

T2

Cell-specific RS EPRE

dBm/15kHz

Non-suitable “Off”

CPICH_Ec (UTRA FDD)

dBm/3.84 MHz

-64

PCCPCH_Ec (UTRA LCR TDD)

dBm/1.28 MHz

-64

Table 13.4.3.8.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures UTRA Cell 5 to reference configuration according 36.508 Table 4.8.3-1, condition UTRA Speech.

2-13

Steps 1 to 12 of the generic test procedure for IMS MO speech call (TS 36.508 4.5A.6.3-1).

EXCEPTION: In parallel to the events described in steps 14 to 15 the steps specified in Table 13.4.3.8.3.2-3 should take place.

14

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the establishment of the new data radio bearer, associated with the dedicated EPS bearer.

–>

RRCConnectionReconfigurationComplete

15

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message on Cell 1.

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

16

Expected sequence defined in annex C.27 of TS 34.229-1 [35].

NOTE: The UE receives forked response.

17

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter-RAT measurement and reporting for event B2.

<–

RRCConnectionReconfiguration

18

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

19

The SS changes the power level for Cell 1 and Cell 5 according to the row "T1" in Table 13.4.3.8.3.2-1.

20

The UE transmits a MeasurementReport message on Cell 1 to report event B2 for Cell 5.

–>

MeasurementReport

21

The SS transmits a UECapabilityEnquiry message on Cell 1 to request UE radio access capability information for E-UTRA and UTRA.

<–

UECapabilityEnquiry

22

The UE transmits a UECapabilityInformation message on Cell 1.

NOTE: The start-CS values received, should be used to configure ciphering on Cell 5.

–>

UECapabilityInformation

23

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

24

Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message on Cell 5?

–>

HANDOVER TO UTRAN COMPLETE

1

P

EXCEPTION: In parallel to the events described in step 25 to 30 the steps specified in Table 13.4.3.8.3.2-4 takes place.

25

The SS transmits a SECURITY MODE COMMAND message for the CS domain on Cell 5.

<–

SECURITY MODE COMMAND

26

The UE transmits a SECURITY MODE COMPLETE message on Cell 5.

–>

SECURITY MODE COMPLETE

27

The SS transmits an UTRAN MOBILITY INFORMATION message on Cell 5 to notify CN information.

<–

UTRAN MOBILITY INFORMATION

28

The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message on Cell 5.

–>

UTRAN MOBILITY INFORMATION CONFIRM

29

The SS transmits a TMSI REALLOCATION COMMAND message on Cell 5.

<–

TMSI REALLOCATION COMMAND

30

The UE transmits a TMSI REALLOCATION COMPLETE message on Cell 5.

–>

TMSI REALLOCATION COMPLETE

31

The SS transmits a CONNECT message on Cell 5.

<–

CONNECT

32

Check: Does the UE transmit a CONNECT ACKNOWLEDGE message on Cell 5?

–>

CONNECT ACKNOWLEDGE

2

P

33

SS adjusts cell levels according to row T2 of table 13.4.3.8.3.2-1.

The UE is in end state UTRA CS call (U5).

Table 13.4.3.8.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-7

Steps 5-11 expected sequence defined in annex C.21 of TS 34.229-1 [35].

NOTE: IMS MO speech call is in alerting phase.

Table 13.4.3.8.3.2-4: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a ROUTING AREA UPDATE REQUEST message on Cell 5.

–>

ROUTING AREA UPDATE REQUEST

2

The SS transmits a SECURITY MODE COMMAND message for the PS domain on Cell 5.

<–

SECURITY MODE COMMAND

3

The UE transmits a SECURITY MODE COMPLETE message on Cell 5.

–>

SECURITY MODE COMPLETE

4

The SS transmits a ROUTING AREA UPDATE ACCEPT message on Cell 5.

<–

ROUTING AREA UPDATE ACCEPT

5

The UE transmits a ROUTING AREA UPDATE COMPLETE message on Cell 5.

–>

ROUTING AREA UPDATE COMPLETE

13.4.3.8.3.3 Specific message contents

Table 13.4.3.8.3.3-0: Conditions for specific message contents
in Table 13.4.3.8.3.3-3.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 13.4.3.8.3.3-1: ATTACH REQUEST (preamble)

Derivation path: 36.508 Table 4.7.2-4

Information Element

Value/remark

Comment

Condition

MS network capability

SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported

Mobile station classmark 2

Any allowed value

Supported Codecs

Any allowed value

Table 13.4.3.8.3.3-2: RRCConnectionReconfiguration (step 17, Table 13.4.3.8.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 13.4.3.8.3.3-3: MeasConfig (Table 13.4.3.8.3.3-2)

Derivation Path: 36.508, Table 4.6.6-1, condition UTRAN

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f8

measObject[2]

MeasObjectUTRA-f8

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-B2-UTRA

reportConfig[1]

ReportConfigInterRAT-B2-UTRA (-72, -76)

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f8

reportConfigId[1]

IdReportConfig-B2-UTRA

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {}

}

}

Table 13.4.3.8.3.3-4: MeasObjectUTRA-f8 (Table 13.4.3.8.3.3-3)

Derivation Path: 36.508, Table 4.6.6-3

Information Element

Value/remark

Comment

Condition

MeasObjectUTRA ::= SEQUENCE {

carrierFreq

Same downlink ARFCN as used for Cell 5

cellsToAddModList CHOICE {

cellsToAddModListUTRA-FDD SEQUENCE (SIZE (1..maxCellMeas)) OF SEQUENCE {

1 entry

UTRA-FDD

cellIndex[1]

1

physCellId[1]

PhysicalCellIdentity of Cell 5

}

cellsToAddModListUTRA-TDD SEQUENCE (SIZE (1..maxCellMeas)) OF SEQUENCE {

UTRA-TDD

cellIndex[1]

1

physCellId[1]

PhysicalCellIdentity of Cell 5

}

}

csg-allowedReportingCells-v930

Not present

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 13.4.3.8.3.3-5: MeasurementReport (step 20, Table 13.4.3.8.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1] CHOICE {

fdd

PhysicalCellIdentity of Cell 5

UTRA-FDD

tdd

PhysicalCellIdentity of Cell 5

UTRA-TDD

}

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

utra-RSCP

(-5..91)

utra-EcN0

Not present

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10

Not present

}

}

}

}

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 13.4.3.8.3.3-6: UECapabilityEnquiry (step 21, Table 13.4.3.8.3.2-2)

Derivation Path: 36.508, Table 4.6.1-22

Information Element

Value/remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

2 entries

RAT-Type[1]

eutra

RAT-Type[2]

utra

}

}

}

}

}

Table 13.4.3.8.3.3-7: MobilityFromEUTRACommand (step 23, Table 13.4.3.8.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

mobilityFromEUTRACommand-r8 SEQUENCE {

cs-FallbackIndicator

False

purpose CHOICE {

handover SEQUENCE {

targetRAT-Type

utra

targetRAT-MessageContainer

HANDOVER TO UTRAN COMMAND(UTRA RRC message)

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

}

}

}

}

Table 13.4.3.8.3.3-8: HANDOVER TO UTRAN COMMAND (Table 13.4.3.8.3.3-7)

Derivation Path: 36.508, Table 4.7B.1-1, condition UTRA Speech

Table 13.4.3.8.3.3-9: SECURITY MODE COMMAND (step 25 Table 13.4.3.8.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-n

Information Element

Value/remark

Comment

Condition

Ciphering mode info

Not present

Table 13.4.3.8.3.3-10: CONNECT (step 31, Table 13.4.3.8.3.2-2)

<

Derivation Path: TS 24.008 Table 9.59

Information Element

Value/remark

Comment

Condition

Transaction identifier