8.4.1 Inter-RAT handover E-UTRA to UTRA

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

8.4.1.1 Void

8.4.1.2 Inter-RAT handover / From E-UTRA to UTRA PS / Data

8.4.1.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and a DPCH PS RAB combination is configured for an UTRA cell}

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

}

8.4.1.2.2 Conformance requirements

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

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

8.4.1.2.3 Test description

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

– The UE is previously registered on cell 5.

Preamble:

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

8.4.1.2.3.2 Test procedure sequence

Table 8.4.1.2.3.2-1: 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.

–

–

–

–

1A

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

<–

UECapabilityEnquiry

–

–

1B

The UE transmit a UECapabilityInformation message on Cell 1.

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

–>

UECapabilityInformation

–

–

2

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

–

–

3

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

–>

HANDOVER TO UTRAN COMPLETE

1

P

–

EXCEPTION: Step 3Aa1 depend on UE implementation

–

–

–

–

3Aa1

The UE sends a ROUTING AREA UPDATE REQUEST message within [2] seconds.

–>

ROUTING AREA UPDATE REQUEST

–

–

4

The SS transmits a SECURITY MODE COMMAND message on Cell 5 in order to activate integrity protection.

<–

SECURITY MODE COMMAND

–

–

5

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

–>

SECURITY MODE COMPLETE

–

–

–

EXCEPTION: Steps 5Aa1 to 5Aa2 depend on UE implementation; the second "lower case letter" identifies a step sequence that takes place if the UE sent a ROUTING AREA UPDATE REQUEST message at step 3a

–

–

–

–

5Aa1

The SS transmits a ROUTING AREA UPDATE ACCEPT message.

<–

ROUTING AREA UPDATE ACCEPT

–

–

5Aa2

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

–

–

6

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

<–

UTRAN MOBILITY INFORMATION

–

–

7

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

–>

UTRAN MOBILITY INFORMATION CONFIRM

–

–

–

EXCEPTION: In parallel to the events described in steps 7A to 9 and depending on the UE implementation the steps defined in Table 8.4.1.2.3.2-2 may take place.

–

–

–

–

7A

IF pc_IMS = TRUE THEN SS starts 6s timer

–

EXCEPTION: Steps 8a1 to 8a3 depend on UE implementation; the second "lower case letter" identifies a step sequence that takes place if the UE did not send a ROUTING AREA UPDATE REQUEST message at step 3a

–

–

–

–

8a1

The UE sends a ROUTING AREA UPDATE REQUEST message.

–>

ROUTING AREA UPDATE REQUEST

–

–

8a2

The SS transmits a ROUTING AREA UPDATE ACCEPT message.

<–

ROUTING AREA UPDATE ACCEPT

–

–

8a3

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

–

–

9

IF pc_IMS = TRUE THEN SS waits until the 6s timer expires

–

Note : At the end of the test procedure sequence, the UE is in end state UTRA connected (U2) according to 36.508

–

–

–

–

Table 8.4.1.2.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 [35] takes place.

–

–

–

–

8.4.1.2.3.3 Specific message contents

Table 8.4.1.2.3.3-1: MobilityFromEUTRACommand (step 2, Table 8.4.1.2.3.2-1)

Derivation Path: 36.508 table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

purpose CHOICE {

handover SEQUENCE {

targetRAT-Type

utra

targetRAT-MessageContainer

HANDOVER TO UTRAN COMMAND

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

}

}

}

}

Table 8.4.1.2.3.3-2: HANDOVER TO UTRAN COMMAND (Table 8.4.1.2.3.3-1)

Derivation Path: 36.508 table 4.7B.1-1, condition UTRA PS RB

Table 8.4.1.2.3.3-3: SECURITY MODE COMMAND (step 4, Table 8.4.1.2.3.2-1)

Derivation Path: 34.108 clause 9.1.1 (SECURITY MODE COMMAND message)

Information Element

Condition

Value/remark

Ciphering mode info

Not Present

Table 8.4.1.2.3.3-4: UTRAN MOBILITY INFORMATION (step 6, Table 8.4.1.2.3.2-1)

Derivation Path: 34.108 clause 9.1.1 (UTRAN MOBILITY INFORMATION message)

Information Element

Value/remark

CN information info

– PLMN identity

– MCC

001

– MNC

01

– CN common GSM-MAP NAS system information

00 01H

– CN domain information list full

– CN domain identity

PS

– CN domain specific NAS system information

01 00H

– DRX cycle length coefficient

7

– CN domain identity

CS

– CN domain specific NAS system information

1E 01H

– DRX cycle length coefficient

7

Table 8.4.1.2.3.3-5: UECapabilityEnquiry (step 1A, Table 8.4.1.2.3.2-1)

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 8.4.1.2.3.3-6: ROUTING AREA UPDATE ACCEPT (step 5Aa1, step 8a2 Table 8.4.1.2.3.2-2)

Derivation Path: 36.508 Table 4.7B.2-2

Information Element

Value/remark

Comment

Condition

Update result

0 ‘Follow-on proceed’

8.4.1.3 Void

8.4.1.4 Inter-RAT handover / From E-UTRA to UTRA HSDPA / Data

8.4.1.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and a DPCH and HS-PDSCH PS RAB combination is configured for an UTRA cell}

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

}

8.4.1.4.2 Conformance requirements

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

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

8.4.1.4.3 Test description

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

– The UE is previously registered on cell 5.

Preamble:

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

8.4.1.4.3.2 Test procedure sequence

Table 8.4.1.4.3.2-1: 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 HSDPA RB..

–

–

–

–

1A

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

<–

UECapabilityEnquiry

–

–

1B

The UE transmit a UECapabilityInformation message on Cell 1.

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

–>

UECapabilityInformation

–

–

2

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

–

–

3

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

–>

HANDOVER TO UTRAN COMPLETE

1

P

–

EXCEPTION: Step 3Aa1 depend on UE implementation

–

–

–

–

3Aa1

The UE sends a ROUTING AREA UPDATE REQUEST message within [2] seconds.

–>

ROUTING AREA UPDATE REQUEST

–

–

4

The SS transmits a SECURITY MODE COMMAND message on Cell 5 in order to activate integrity protection.

<–

SECURITY MODE COMMAND

–

–

5

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

–>

SECURITY MODE COMPLETE

–

–

–

EXCEPTION: Steps 5Aa1 to 5Aa2 depend on UE implementation; the second "lower case letter" identifies a step sequence that takes place if the UE sent a ROUTING AREA UPDATE REQUEST message at step 3a

–

–

–

–

5Aa1

The SS transmits a ROUTING AREA UPDATE ACCEPT message.

<–

ROUTING AREA UPDATE ACCEPT

–

–

5Aa2

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

–

–

6

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

<–

UTRAN MOBILITY INFORMATION

–

–

7

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

–>

UTRAN MOBILITY INFORMATION CONFIRM

–

–

–

EXCEPTION: In parallel to the events described in steps 7A to 9 and depending on the UE implementation the steps defined in Table 8.4.1.4.3.2-2 may take place.

–

–

–

–

7A

IF pc_IMS = TRUE THEN SS starts 6s timer

–

EXCEPTION: Steps 8a1 to 8a3 depend on UE implementation; the second "lower case letter" identifies a step sequence that takes place if the UE did not send a ROUTING AREA UPDATE REQUEST message at step 3a

–

–

–

–

8a1

The UE sends a ROUTING AREA UPDATE REQUEST message.

–>

ROUTING AREA UPDATE REQUEST

–

–

8a2

The SS transmits a ROUTING AREA UPDATE ACCEPT message.

<–

ROUTING AREA UPDATE ACCEPT

–

–

8a3

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

–

–

9

IF pc_IMS = TRUE THEN SS waits until the 6s timer expires

–

Note : At the end of the test procedure sequence, the UE is in end state UTRA connected (U2) according to 36.508

–

–

–

–

Table 8.4.1.4.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 [35] takes place.

–

–

–

–

8.4.1.4.3.3 Specific message contents

Table 8.4.1.4.3.3-1: MobilityFromEUTRACommand (step 2, Table 8.4.1.4.3.2-1)

Derivation Path: 36.508t able 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

purpose CHOICE {

handover SEQUENCE {

targetRAT-Type

utra

targetRAT-MessageContainer

HANDOVER TO UTRAN COMMAND

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

}

}

}

}

Table 8.4.1.4.3.3-2: HANDOVER TO UTRAN COMMAND (Table 8.4.1.4.3.3-1)

Derivation Path: 36.508 table 4.7B.1-1, condition UTRA HSDPA RB

Table 8.4.1.4.3.3-3: SECURITY MODE COMMAND (step 4, Table 8.4.1.4.3.2-1)

Derivation Path: 34.108 clause 9.1.1 (SECURITY MODE COMMAND message)

Information Element

Condition

Value/remark

Ciphering mode info

Not Present

Table 8.4.1.4.3.3-4: UTRAN MOBILITY INFORMATION (step 6, Table 8.4.1.4.3.2-1)

Derivation Path: 34.108 clause 9.1.1 (UTRAN MOBILITY INFORMATION message)

Information Element

Value/remark

CN information info

– PLMN identity

– MCC

001

– MNC

01

– CN common GSM-MAP NAS system information

00 01H

– CN domain information list full

– CN domain identity

PS

– CN domain specific NAS system information

01 00H

– DRX cycle length coefficient

7

– CN domain identity

CS

– CN domain specific NAS system information

1E 01H

– DRX cycle length coefficient

7

Table 8.4.1.4.3.3-5: UECapabilityEnquiry (step 1A, Table 8.4.1.4.3.2-1)

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 8.4.1.4.3.3-6: ROUTING AREA UPDATE ACCEPT (step 5Aa1, step 8a2 Table 8.4.1.4.3.2-2)

Derivation Path: 36.508 Table 4.7B.2-2

Information Element

Value/remark

Comment

Condition

Update result

0 ‘Follow-on proceed’

8.4.1.5 Inter-RAT Handover / from E-UTRA to UTRA(HSUPA/HSDPA) / Data

8.4.1.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and a E-DCH and HS-DSCH PS RAB combination is configured for an UTRA cell}

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

}

8.4.1.5.2 Conformance requirements

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

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

8.4.1.5.3 Test description

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

– The UE is previously registered on cell 5.

Preamble:

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

8.4.1.5.3.2 Test procedure sequence

Table 8.4.1.5.3.2-1: 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 HSUPA/HSDPA RB.

–

–

–

–

1A

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

<–

UECapabilityEnquiry

–

–

1B

The UE transmit a UECapabilityInformation message on Cell 1.

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

–>

UECapabilityInformation

–

–

2

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

–

–

3

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

–>

HANDOVER TO UTRAN COMPLETE

1

P

–

EXCEPTION: Step 3Aa1 depend on UE implementation

–

–

–

–

3Aa1

The UE sends a ROUTING AREA UPDATE REQUEST message within [2] seconds.

–>

ROUTING AREA UPDATE REQUEST

–

–

4

The SS transmits a SECURITY MODE COMMAND message on Cell 5 in order to activate integrity protection.

<–

SECURITY MODE COMMAND

–

–

5

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

–>

SECURITY MODE COMPLETE

–

–

–

EXCEPTION: Steps 5Aa1 to 5Aa2 depend on UE implementation; the second "lower case letter" identifies a step sequence that takes place if the UE sent a ROUTING AREA UPDATE REQUEST message at step 3a

–

–

–

–

5Aa1

The SS transmits a ROUTING AREA UPDATE ACCEPT message.

<–

ROUTING AREA UPDATE ACCEPT

–

–

5Aa2

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

–

–

6

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

<–

UTRAN MOBILITY INFORMATION

–

–

7

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

–>

UTRAN MOBILITY INFORMATION CONFIRM

–

–

–

EXCEPTION: In parallel to the events described in steps 7A to 9 and depending on the UE implementation the steps defined in Table 8.4.1.5.3.2-2 may take place.

–

–

–

–

–

EXCEPTION: Steps 8a1 to 8a3 depend on UE implementation; the second "lower case letter" identifies a step sequence that takes place if the UE did not send a ROUTING AREA UPDATE REQUEST message at step 3a

–

–

–

–

7A

IF pc_IMS = TRUE THEN SS starts 6s timer

8a1

The UE sends a ROUTING AREA UPDATE REQUEST message.

–>

ROUTING AREA UPDATE REQUEST

–

–

8a2

The SS transmits a ROUTING AREA UPDATE ACCEPT message.

<–

ROUTING AREA UPDATE ACCEPT

–

–

8a3

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

–

–

9

IF pc_IMS = TRUE THEN SS waits until the 6s timer expires

–

Note : At the end of the test procedure sequence, the UE is in end state UTRA connected (U2) according to 36.508

–

–

–

–

Table 8.4.1.5.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 [35] takes place.

–

–

–

–

8.4.1.5.3.3 Specific message contents

Table 8.4.1.5.3.3-1: MobilityFromEUTRACommand (step 2, Table 8.4.1.5.3.2-1)

Derivation Path: 36.508t able 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

purpose CHOICE {

handover SEQUENCE {

targetRAT-Type

utra

targetRAT-MessageContainer

HANDOVER TO UTRAN COMMAND

nas-SecurityParamFromEUTRA

The 4 least significant bits of the NAS downlink COUNT value

systemInformation

Not present

}

}

}

}

}

}

Table 8.4.1.5.3.3-2: HANDOVER TO UTRAN COMMAND (Table 8.4.1.5.3.3-1)

Derivation Path: 36.508 table 4.7B.1-1, condition UTRA HSUPA/HSDPA RB

Table 8.4.1.5.3.3-3: SECURITY MODE COMMAND (step 4, Table 8.4.1.5.3.2-1)

Derivation Path: 34.108 clause 9.1.1 (SECURITY MODE COMMAND message)

Information Element

Condition

Value/remark

Ciphering mode info

Not Present

Table 8.4.1.5.3.3-4: UTRAN MOBILITY INFORMATION (step 6, Table 8.4.1.5.3.2-1)

Derivation Path: 34.108 clause 9.1.1 (UTRAN MOBILITY INFORMATION message)

Information Element

Value/remark

CN information info

– PLMN identity

– MCC

001

– MNC

01

– CN common GSM-MAP NAS system information

00 01H

– CN domain information list full

– CN domain identity

PS

– CN domain specific NAS system information

01 00H

– DRX cycle length coefficient

7

– CN domain identity

CS

– CN domain specific NAS system information

1E 01H

– DRX cycle length coefficient

7

Table 8.4.1.5.3.3-5: UECapabilityEnquiry (step 1A, Table 8.4.1.5.3.2-1)

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 8.4.1.5.3.3-6: ROUTING AREA UPDATE ACCEPT (step 5Aa1, step 8a2 8.4.1.5.3.2-2)

Derivation Path: 36.508 Table 4.7B.2-2

Information Element

Value/remark

Comment

Condition

Update result

0 ‘Follow-on proceed’