9.2.2 Detach procedure

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

9.2.2.1 UE initiated detach procedure

9.2.2.1.1 UE initiated detach / UE switched off

9.2.2.1.1.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state }

ensure that {

when { the UE is switched off }

then { the UE establishes the RRC connection with the RRC establishmentCause set to ‘mo-Signalling’ and sends DETACH REQUEST message, keeps the native security context, and deactivates the EPS bearer context(s) locally }

}

9.2.2.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.3.1.1, 5.5.2.2.1, 5.5.2.2.2 and Annex D and TS 36.331 clause 5.3.3.3.

[TS 24.301 clause 5.3.1.1]

When the UE is in EMM-IDLE mode and needs to transmit an initial NAS message, the UE shall request the lower layer to establish a NAS signalling connection. In this request to the lower layer the NAS shall provide to the lower layer the RRC establishment cause and the call type as specified in annex D of this specification.

[TS 24.301 clause 5.5.2.2.1]

The detach procedure is initiated by the UE by sending a DETACH REQUEST message. The Detach type IE included in the message indicates whether detach is due to a "switch off" or not. The Detach type IE also indicates whether the detach is for EPS services only, for non-EPS services only, or for both. If the UE has a mapped EPS security context as the current EPS security context, the UE shall set the type of security context flag to "mapped security context". Otherwise, the UE shall set the type of security context flag to "native security context".

If the UE is to be switched off, the UE shall try for a period of 5 seconds to send the DETACH REQUEST message. During this period, the UE may be switched off as soon as the DETACH REQUEST message has been sent.

After the last DETACH REQUEST message is sent, the UE shall proceed as follows:

– if the current EPS security context is a native EPS security context, then the UE shall store the current EPS security context as specified in annex C and mark it as valid;

– else if the current EPS security context is a mapped EPS security context and a non-current full native EPS security context exists, then the UE shall store the non-current EPS security context as specified in annex C and mark it as valid, and finally the UE shall delete any mapped EPS security context or partial native EPS security context.

[TS 24.301 clause 5.5.2.2.2]

When the DETACH REQUEST message is received by the network, the network shall send a DETACH ACCEPT message to the UE and store the current EPS security context, if the Detach type IE does not indicate "switch off". Otherwise, the procedure is completed when the network receives the DETACH REQUEST message. On reception of a DETACH REQUEST message indicating "switch off", the MME shall delete the current EPS security context, if it is a mapped EPS security context.

The network and the UE shall deactivate the EPS bearer context(s) for this UE locally without peer-to-peer signalling between the UE and the MME.

The UE, when receiving the DETACH ACCEPT message, shall stop timer T3421.

The UE is marked as inactive in the network for EPS services. State EMM-DEREGISTERED is entered in the network.

The UE in PS mode of operation shall enter the EMM-DEREGISTERED state.

The UE in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, disable E‑UTRAN and select GERAN or UTRAN access technology and enter the EMM-NULL state.

[TS 24.301, Annex D]

Table D.1.1: Mapping of NAS procedure to establishment cause and call type

NAS procedure

RRC establishment cause (according 3GPP TS 36.331 [22])

Call type

Detach

MO signalling (See Note 1)

"originating signalling"

Note 1: For these NAS procedures initiated by UEs of access class 12, 13 or 14 in their home country, the RRC establishment cause will be set to "High priority access AC 11 – 15". For this purpose the home country is defined as the country of the MCC part of the IMSI, see 3GPP TS 22.011 [1A].
For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN or EHPLMN, the RRC establishment cause will be set to "High priority access AC 11 – 15".

[TS 36.331, clause 5.3.3.3]

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

1> set the ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else

3> draw a random value and set the ue-Identity to this value;

NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> Set the establishmentCause in accordance with the information received from upper layers;

9.2.2.1.1.3 Test description

9.2.2.1.1.3.1 Pre-test conditions

System Simulator:

– cell A (HPLMN).

UE:

none.

Preamble:

– the UE is in state Registered, Idle mode (State 2) according to TS 36.508 [18].

9.2.2.1.1.3.2 Test procedure sequence

Table 9.2.2.1.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause switch off

1A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

2

Check: Does the UE transmit an RRCConnectionRequest message with establishmentCause set to ‘mo-Signalling’ followed by a DETACH REQUEST with the Detach Type IE indicating "switch off"?

–>

DETACH REQUEST

1

P

2A

The SS releases the RRC connection.

3-7

Void

8

The UE is switched on

9

Check: Does the UE transmit ATTACH REQUEST message using KSIASME of the previously allocated EPS native security context?

–>

ATTACH REQUEST

1

P

10-23b1

The attach procedure is completed by executing steps 5 to 18b1 of the UE registration procedure in TS 36.508 sub clause 4.5.2.3.

At the end of this test procedure sequence, the UE is in end state E-UTRA idle (E1) according to TS 36.508.

9.2.2.1.1.3.3 Specific message contents

Table 9.2.2.1.1.3.3-1: Message RRCConnectionRequest (step 2, Table 9.2.2.1.1.3.2-1)

Derivation path: 36.508 table 4.6.1-16

Information Element

Value/Remark

Comment

Condition

RRCConnectionRequest ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r8 SEQUENCE {

establishmentCause

mo-Signalling

}

}

}

Table 9.2.2.1.1.3.3-2: Message ATTACH REQUEST (step 9, Table 9.2.2.1.1.3.2-1)

Derivation path: 36.508 table 4.7.2-4 (Security protected NAS message)

Information Element

Value/Remark

Comment

Condition

NAS key set identifier

TSC

native security context (for KSIASME)

9.2.2.1.2 UE initiated detach / USIM removed from the UE

9.2.2.1.2.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED }

ensure that {

when { the USIM is removed from the UE }

then { the UE sends DETACH REQUEST message and indicates that the detach is for both EPS services and non-EPS services or for EPS services depending on the EPS attach type used }

}

9.2.2.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.5.2.2.1 and 5.5.2.2.3.

[TS 24.301 clause 5.5.2.2.1]

The detach procedure is initiated by the UE by sending a DETACH REQUEST message. The Detach type IE included in the message indicates whether detach is due to a "switch off" or not. The Detach type IE also indicates whether the detach is for EPS services only, for non-EPS services only, or for both. If the UE has a mapped EPS security context as the current EPS security context, the UE shall set the type of security context flag to "mapped security context". Otherwise, the UE shall set the type of security context flag to "native security context".

If the UE has a valid GUTI, the UE shall populate the GUTI or IMSI IE with the valid GUTI. If the UE does not have a valid GUTI, the UE populates the GUTI or IMSI IE with its IMSI.

If the detach is not due to switch off and the UE is in the state EMM-REGISTERED or EMM-REGISTERED-INITIATED, timer T3421 shall be started in the UE after the DETACH REQUEST message has been sent. If the detach type indicates that the detach is for non-EPS services only the UE shall enter the state EMM-REGISTERED.IMSI-DETACH-INITIATED, otherwise the UE shall enter the state EMM-DEREGISTERED-INITIATED. If the detach type indicates that the detach is for non-EPS services or both EPS and non-EPS services, the UE shall enter the state MM IMSI DETACH PENDING.

[TS 24.301 clause 5.5.2.2.3]

When the DETACH REQUEST message is received by the network, a DETACH ACCEPT message shall be sent to the UE, if the Detach type IE value indicates that the detach request has not been sent due to switching off. Depending on the value of the Detach type IE the following applies:

– combined EPS/IMSI detach:

The UE is marked as inactive in the network for EPS and for non-EPS services. The states EMM-DEREGISTERED and MM-NULL are entered in both the UE and the network.

9.2.2.1.2.3 Test description

9.2.2.1.2.3.1 Pre-test conditions

System Simulator:

– cell A (HPLMN).

UE:

none.

Preamble:

– the UE is in state Registered, Idle mode (State 2) according to TS 36.508 [18]

9.2.2.1.2.3.2 Test procedure sequence

Table 9.2.2.1.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause removal of USIM from the UE without powering down

1A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

2

Check: Does the UE transmit a DETACH REQUEST with the Detach Type IE indicating "normal detach" or “power off” detach and "combined EPS/IMSI detach" or "EPS detach" depending on the UE configuration?

–>

DETACH REQUEST

1

P

EXCEPTION: Step 2a describe behaviour that depends on the UE implementation

2a

If in step 2 normal detach is performed SS responds with DETACH ACCEPT message

<–

DETACH ACCEPT

3

Check: Does the test result of generic procedure in TS 36.508 subclause 6.4.2.5 indicate that the UE does not respond to paging when paged with S-TMSI included in GUTI-1 and with CN domain indicator set to "PS"?

1

9.2.2.1.2.3.3 Specific message contents

Table 9.2.2.1.2.3.3-1: DETACH REQUEST (step 2, Table 9.2.2.1.2.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

001

EPS detach

EPSOnlyAttach

011

combined EPS/IMSI detach

CombinedAttach

Switch off

Not checked

GUTI or IMSI

GUTI-1

9.2.2.1.3 UE initiated detach / EPS capability of the UE is disabled

9.2.2.1.3.1 Test Purpose (TP)

(1)

with { CS/PS mode 1 UE or CS/PS mode 2 UE in EMM-REGISTERED state }

ensure that {

when { EPS capability of the UE is disabled by disabling it’s EPS services }

then { UE sends the DETACH REQUEST message on the cell registered and indicates that the detach is for EPS services }

}

(2)

with { CS/PS mode 1 UE or CS/PS mode 2 UE }

ensure that {

when { EPS capability of the UE is disabled by disabling it’s EPS services and the UE detaches from EPS services }

then { UE selects GERAN or UTRAN radio access technology indicating E-UTRA not supported in order to enable the UE to continue to obtain CS services }

}

9.2.2.1.3.2 Conformance requirements

References: The conformance requirement covered in the present TC is specified in: 3GPP TS 24.301 clauses 5.5.2.1, 5.5.2.2.1, 5.5.2.2.2, 3.1 and 4.5, Unless otherwise stated these are Rel-8 requirements.

[TS 24.301, clause 5.5.2.1]

The detach procedure with appropriate detach type shall be invoked by the UE if the UE is switched off, the USIM card is removed from the UE or the UE has disabled EPS services or the UE wishes to detach for non-EPS services.

If the detach procedure for EPS services is performed, the EPS bearer context(s) for this particular UE are deactivated locally without peer-to-peer signalling between the UE and the MME.

Upon successful completion of the detach procedure, if the UE and the MME enter the EMM-DEREGISTERED state, the UE and the MME shall delete any mapped EPS security context or partial native EPS security context.

If the UE supports A/Gb mode or Iu mode, the UE shall store the TIN in the non-volatile memory in the ME, as described in annex C, for a subsequent attach procedure.

[TS 24.301, clause 5.5.2.2.1]

The detach procedure is initiated by the UE by sending a DETACH REQUEST message. The Detach type IE included in the message indicates whether detach is due to a "switch off" or not. The Detach type IE also indicates whether the detach is for EPS services only, for non-EPS services only, or for both. If the UE has a mapped EPS security context as the current EPS security context, the UE shall set the type of security context flag to "mapped security context". Otherwise, the UE shall set the type of security context flag to "native security context".

If the UE has a valid GUTI, the UE shall populate the GUTI or IMSI IE with the valid GUTI. If the UE does not have a valid GUTI, the UE populates the GUTI or IMSI IE with its IMSI.

If the detach is not due to switch off and the UE is in the state EMM-REGISTERED or EMM-REGISTERED-INITIATED, timer T3421 shall be started in the UE after the DETACH REQUEST message has been sent. If the detach type indicates that the detach is for non-EPS services only the UE shall enter the state EMM-REGISTERED.IMSI-DETACH-INITIATED, otherwise the UE shall enter the state EMM-DEREGISTERED-INITIATED. If the detach type indicates that the detach is for non-EPS services or both EPS and non-EPS services, the UE shall enter the state MM IMSI DETACH PENDING.

[TS 24.301, clause 5.5.2.2.2]

The network and the UE shall deactivate the EPS bearer context(s) for this UE locally without peer-to-peer signalling between the UE and the MME.

The UE, when receiving the DETACH ACCEPT message, shall stop timer T3421.

The UE is marked as inactive in the network for EPS services. State EMM-DEREGISTERED is entered in the network.

The UE in PS mode of operation shall enter the EMM-DEREGISTERED state.

The UE in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, disable E‑UTRAN and select GERAN or UTRAN access technology and enter the EMM-NULL state.

[TS 24.301, clause 3.1]

EPS services: Within the context of this specification, EPS services is used as a synonym for GPRS services in 3GPP TS 24.008 [13].

[TS 24.301, clause 4.5]

When the UE supporting the A/Gb and/or Iu mode together with the S1 mode needs to stay in A/Gb or Iu mode, in order to prevent unwanted handover or cell reselection from UTRAN/GERAN to E-UTRAN, the UE shall disable the E-UTRA capability.

– The UE shall not set the E-UTRA support bits of the MS Radio Access capability IE (see 3GPP TS 24.008 [13], subclause 10.5.5.12a), the E-UTRA support bits of Mobile Station Classmark 3 IE (see 3GPP TS 24.008 [13], subclause 10.5.1.7) and the ISR support bit of the MS network capability IE (see 3GPP TS 24.008 [13], subclause 10.5.5.12) in the ATTACH REQUEST message and the ROUTING AREA UPDATE REQUEST message after it selects GERAN or UTRAN; and

– the UE NAS layer shall indicate the access stratum layer(s) of disabling of the E-UTRA capability.

NOTE: The UE can only disable the E-UTRAN capabilities when in EMM-IDLE mode.

9.2.2.1.3.3 Test description

9.2.2.1.3.3.1 Pre-test conditions

System Simulator:

– Cell A.

– if pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA, cell 5 (home PLMN, RAI-1, NMO 1) is set to "Suitable cell";

– if pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN, cell 24 (home PLMN, RAI-1, NMO 1) is set to "Suitable cell";

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

NOTE: Setting px_RATComb_Tested = EUTRA_Only is not allowed.

UE:

– the UE is configured to initiate combined EPS/IMSI attach.

Preamble:

– the UE is in state Registered, Idle mode (state 2) on cell A according to TS 36.508 [18].

9.2.2.1.3.3.2 Test procedure sequence

Table 9.2.2.1.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause UE to disable the EPS services.

2

Check: Does the UE transmit a DETACH REQUEST message with the Detach type IE indicating “EPS detach” and “normal detach”.

–>

DETACH REQUEST

1

P

3

The SS transmits a DETACH ACCEPT message.

<–

DETACH ACCEPT

3A

The SS releases the RRC connection.

4

Void

EXCEPTION: Steps 5a1 to 5b5A describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.

5a1

IF pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA THEN

The following messages are to be observed on Cell 5 unless explicitly stated otherwise.

5a2

Check: Does the UE send RRC CONNECTION REQUEST indicating that it does not support E-UTRA?

–>

2

P

5a3

The SS sends RRC CONNECTION SETUP

<–

5a4

Check: Does the UE send RRC CONNECTION SETUP COMPLETE message indicating that it does not support E-UTRA?

–>

2

P

5a5

Check: Does the UE transmit a LOCATION UPDATING REQUEST on Cell 5?

–>

LOCATION UPDATING REQUEST

2

P

5a6

The SS transmits an AUTHENTICATION AND CIPHERING REQUEST message.

<–

AUTHENTICATION AND CIPHERING REQUEST

5a7

The UE transmits an AUTHENTICATION AND CIPHERING RESPONSE message.

–>

AUTHENTICATION AND CIPHERING RESPONSE

5a8

The SS transmits a LOCATION UPDATING ACCEPT message on Cell 5.

<–

LOCATION UPDATING ACCEPT

5a9

The UE transmits an TMSI REALLOCATION COMPLETE message

–>

TMSI REALLOCATION COMPLETE

5b1

ELSE IF pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN THEN

The following messages are to be observed on Cell 24 unless explicitly stated otherwise.

5b2

Check: Does the UE transmit a LOCATION UPDATING REQUEST?

–>

LOCATION UPDATING REQUEST

2

P

EXCEPTION: Steps 5b2AAa1 to 5b2AAb1 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.

5b2AAa1

IF pc_Dynamic_GERAN_Rel_downgrade=FALSE THEN

Check: Does the UE transmit a Classmark Change message indicating that it does not support E-UTRA?

–>

CLASSMARK CHANGE

2

P

5b2AAb1

IF pc_Dynamic_GERAN_Rel_downgrade=TRUE THEN the UE transmit a Classmark Change message.

–>

CLASSMARK CHANGE

5b2A

Void

EXCEPTION: Step 5b2B describes behaviour that depends on UE capability.

5b2B

IF pc_UTRA THEN the UE transmits a Utran Classmark Change message.

–>

UTRAN CLASSMARK CHANGE.

5b3

The SS transmits an AUTHENTICATION REQUEST message.

<–

AUTHENTICATION REQUEST

5b4

The UE transmits an AUTHENTICATION RESPONSE message.

–>

AUTHENTICATION RESPONSE

5b5

The SS transmits a LOCATION UPDATING ACCEPT message.

<–

LOCATION UPDATING ACCEPT

5b5A

The UE transmits an TMSI REALLOCATION COMPLETE message.

–>

TMSI REALLOCATION COMPLETE

5b6

Void

Table: 9.2.2.1.3.3.2-2: Void

9.2.2.1.3.3.3 Specific message contents

Table 9.2.2.1.3.3.3-1: DETACH REQUEST (steps 2 in Table 9.2.2.1.3.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

001

EPS detach only

Switch off

0

normal detach

GUTI or IMSI

GUTI-1

Table 9.2.2.1.3.3.3-2: Message RRC Connection Request (step 5a2 in Table 9.2.2.1.3.3.2-1)

Derivation path: 34.108 sub-clause 9.1.1

Information Element

Value/Remark

Comment

Condition

Pre-redirection info

Optional IE, but if transmitted it should have the below values

> Support of E-UTRA FDD

False

E-UTRA FDD not supported

> Support of E-UTRA TDD

False

E-UTRA TDD not supported

Table 9.2.2.1.3.3.3-3: Message RRC Connection Setup Complete (step 5a4 in Table 9.2.2.1.3.3.2-1)

Derivation path: 34.108 sub-clause 9.1.1

Information Element

Value/Remark

Comment

Condition

UE radio access capability

The UE shall not indicate support for E-UTRAN

>UE multi-mode/multi-RAT capability

>> Multi-RAT capability

>>> Support of Inter-RAT PS Handover to E-UTRA FDD

Not present

>>> Support of E-UTRA TDD

Not present

>>> Support of Inter-RAT PS Handover to E-UTRA TDD

Not present

>>> EUTRA Feature Group Indicators

Not checked

Table 9.2.2.1.3.3.3-4: CLASSMARK CHANGE (step 5b2A in Table 9.2.2.1.3.3.2-1)

Derivation path: 44.018 sub-clause 9.1.11

Information Element

Value/Remark

Comment

Condition

Mobile Station Classmark

CM3 bit is set to 1

Additional Mobile Station Classmark Information

Mobile Station Classmark 3

Table 9.2.2.1.3.3.3-5: Mobile Station Classmark 3 (Table 9.2.2.1.3.3.3-4)

Derivation path: 24.008 sub-clause 10.5.1.7

Information Element

Value/Remark

Comment

Condition

Only the following values should be checked (Note 1)

E-UTRA FDD support

‘0’B

Not supported

pc_Dynamic_GERAN_Rel_downgrade=FALSE

Not present

pc_Dynamic_GERAN_Rel_downgrade=TRUE

E-UTRA TDD support

‘0’B

Not supported

pc_Dynamic_GERAN_Rel_downgrade=FALSE

Not present

pc_Dynamic_GERAN_Rel_downgrade=TRUE

Note 1: When EPS capability is disabled, a UE may dynamically switch its GERAN Release to a lower release than GERAN Rel-8, and hence any Classmark 3 structures relevant for Rel-8 and above (inc. E-UTRA FDD support and E-UTRA FDD support) may not be present.

9.2.2.1.4 UE initiated detach / detach for non-EPS services

9.2.2.1.4.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state }

ensure that {

when { UE is detached for non-EPS services }

then { UE sends the DETACH REQUEST message on the cell registered and indicates a IMSI detach }

}

9.2.2.1.4.2 Conformance requirements

References: The conformance requirement covered in the present TC is specified in: 3GPP TS 24.301 clauses 5.5.2.1, 5.5.2.2.1 and 5.5.2.2.3.

[TS 24.301, clause 5.5.2.1]

The detach procedure with appropriate detach type shall be invoked by the UE if the UE is switched off, the USIM card is removed from the UE or the UE has disabled EPS services or the UE wishes to detach for non-EPS services.

[TS 24.301, clause 5.5.2.2.1]

The detach procedure is initiated by the UE by sending a DETACH REQUEST message (see example in figure 5.5.2.2.1.1). The Detach type IE included in the message indicates whether detach is due to a "switch off" or not. The Detach type IE also indicates whether the detach is for EPS services only, for non-EPS services only, or for both. If the UE has a mapped EPS security context as the current EPS security context, the UE shall set the type of security context flag to "mapped security context". Otherwise, the UE shall set the type of security context flag to "native security context".

If the UE has a valid GUTI, the UE shall populate the GUTI or IMSI IE with the valid GUTI. If the UE does not have a valid GUTI, the UE populates the GUTI or IMSI IE with its IMSI.

If the detach is not due to switch off and the UE is in the state EMM-REGISTERED or EMM-REGISTERED-INITIATED, timer T3421 shall be started in the UE after the DETACH REQUEST message has been sent. If the detach type indicates that the detach is for non-EPS services only the UE shall enter the state EMM-REGISTERED.IMSI-DETACH-INITIATED, otherwise the UE shall enter the state EMM-DEREGISTERED-INITIATED. If the detach type indicates that the detach is for non-EPS services or both EPS and non-EPS services, the UE shall enter the state MM IMSI DETACH PENDING.

[TS 24.301, clause 5.5.2.2.3]

When the DETACH REQUEST message is received by the network, a DETACH ACCEPT message shall be sent to the UE, if the Detach type IE value indicates that the detach request has not been sent due to switching off. Depending on the value of the Detach type IE the following applies:

– combined EPS/IMSI detach:

The UE is marked as inactive in the network for EPS and for non-EPS services. The states EMM-DEREGISTERED and MM-NULL are entered in both the UE and the network.

– IMSI detach:

The UE is marked as inactive in the network for non-EPS services. The states MM-NULL and EMM-REGISTERED are entered in both the UE and the network.

9.2.2.1.4.3 Test description

9.2.2.1.4.3.1 Pre-test conditions

System Simulator:

– Cell A is set to ”Serving cell”;

– Cell B is set to ”Non-Suitable cell’

UE:

– the UE is configured to initiate combined EPS/IMSI attach.

Preamble:

– the UE is in state Registered, Idle mode (state 2) on cell A according to TS 36.508 [18].

9.2.2.1.4.3.2 Test procedure sequence

Table 9.2.2.1.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause UE to initiate detach for non-EPS services.

2

Check: Does the UE transmit a DETACH REQUEST message with the Detach type IE indicating “IMSI detach” and “normal detach”.

–>

DETACH REQUEST

1

P

3

The SS responds with DETACH ACCEPT message.

DETACH ACCEPT

3A

The SS releases the RRC Connection.

4

Set the cell type of cell A to the "Non-Suitable cell ".

Set the cell type of cell B to the " Serving cell"

5

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

–>

TRACKING AREA UPDATE REQUEST

1

P

6

The SS transmits a TRACKING AREA UPDATE ACCEPT message.

<–

TRACKING AREA UPDATE ACCEPT

7

The UE transmits a TRACKING AREA UPDATE COMPLETE message?

–>

TRACKING AREA UPDATE COMPLETE

At the end of this test procedure sequence, the UE is in end state E-UTRA connected (E2_T3440) according to TS 36.508.

9.2.2.1.4.3.3 Specific message contents

Table 9.2.2.1.4.3.3-1: DETACH REQUEST (step 2 in Table 9.2.2.1.4.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

010

IMSI detach

Switch off

0

normal detach

Table 9.2.2.1.4.3.3-2: TRACKING AREA UPDATE REQUEST (step 5 in Table 9.2.2.1.4.3.2-1)

Derivation Path: 36.508, Table 4.7.2-27

Information Element

Value/remark

Comment

Condition

EPS update type

EPS update type value

‘000’B

TA updating

9.2.2.1.5 Void
9.2.2.1.6 UE initiated detach / Abnormal case / Local detach after 5 attempts due to no network response

9.2.2.1.6.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state }

ensure that {

when { the UE receives no response to the UE initiated DETACH REQUEST }

then { the UE re-transmits the DETACH REQUEST up to 4 times on the expiry of timer T3421 }

}

(2)

with { UE in EMM-REGISTERED state }

ensure that {

when { the UE receives no response to the UE initiated DETACH REQUEST }

then { the UE aborts the detach procedure and perform local detach on the 5th expiry of timer T3421 }

}

9.2.2.1.6.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.2.2.

[TS 24.301, clause 5.5.2.2.1]

The detach procedure is initiated by the UE by sending a DETACH REQUEST message. The Detach type IE included in the message indicates whether detach is due to a "switch off" or not. The Detach type IE also indicates whether the detach is for EPS services only, for non-EPS services only, or for both. If the UE has a mapped EPS security context as the current EPS security context, the UE shall set the type of security context flag to "mapped security context". Otherwise, the UE shall set the type of security context flag to "native security context".

If the UE has a valid GUTI, the UE shall populate the GUTI or IMSI IE with the valid GUTI. If the UE does not have a valid GUTI, the UE populates the GUTI or IMSI IE with its IMSI.

If the detach is not due to switch off and the UE is in the state EMM-REGISTERED or EMM-REGISTERED-INITIATED, timer T3421 shall be started in the UE after the DETACH REQUEST message has been sent. If the detach type indicates that the detach is for non-EPS services only the UE shall enter the state EMM-REGISTERED.IMSI-DETACH-INITIATED, otherwise the UE shall enter the state EMM-DEREGISTERED-INITIATED. If the detach type indicates that the detach is for non-EPS services or both EPS and non-EPS services, the UE shall enter the state MM IMSI DETACH PENDING.

[TS 24.301, clause 5.5.2.2.4 c)]

The following abnormal cases can be identified:

c) T3421 timeout

On the first four expiries of the timer, the UE shall retransmit the DETACH REQUEST message and shall reset and restart timer T3421. On the fifth expiry of timer T3421, the detach procedure shall be aborted and the UE shall change to state:

– EMM-REGISTERED.NORMAL-SERVICE and MM-NULL if "IMSI detach" was requested;

– EMM-DEREGISTERED if "EPS detach" was requested;

– EMM-DEREGISTERED and MM-NULL if "combined EPS/IMSI detach" was requested.

[TS 24.301, clause 5.1.3.2.2.2]

In the state EMM-DEREGISTERED, no EMM context has been established and the UE location is unknown to an MME and hence it is unreachable by an MME. In order to establish an EMM context, the UE shall start the attach or combined attach procedure (see subclause 5.5.1).

9.2.2.1.6.3 Test description

9.2.2.1.6.3.1 Pre-test conditions

System Simulator:

– cell A (HPLMN).

UE:

none.

Preamble:

– the UE is in state Registered, Idle Mode (State 2) according to TS 36.508 [18].

9.2.2.1.6.3.2 Test procedure sequence

Table 9.2.2.1.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause UE to initiate detach.

1A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

2

The UE transmits a DETACH REQUEST message? The UE starts timer T3421.

–>

DETACH REQUEST

3

The SS does not respond to the DETACH REQUEST message.

4

Check: When the timer T3421 expires does the UE re-transmit DETACH REQUEST message. Timer T3421 is re-started (1st expiry).

–>

DETACH REQUEST

1

P

5

The SS does not respond to the DETACH REQUEST message.

6

Check: When the timer T3421 expires does the UE re-transmit DETACH REQUEST message. Timer T3421 is re-started (2nd expiry).

–>

DETACH REQUEST

1

P

7

The SS does not respond to the DETACH REQUEST message.

8

Check: When the timer T3421 expires does the UE re-transmit DETACH REQUEST message. Timer T3421 is re-started (3rd expiry).

–>

DETACH REQUEST

1

P

9

The SS does not respond to the DETACH REQUEST message.

10

Check: When the timer T3421 expires does the UE re-transmit DETACH REQUEST message. Timer T3421 is re-started (4th expiry).

–>

DETACH REQUEST

1

P

11

The SS does not respond to the DETACH REQUEST message.

12

When the timer T3421 expires the UE aborts the detach procedure and performs a local detach (5th expiry).

2

P

13

The SS starts the EPS bearer context modification procedure using the previously allocated EPS bearer identity

<–

MODIFY EPS BEARER CONTEXT REQUEST

14

Check: Does the UE transmit a MODIFY EPS BEARER CONTEXT ACCEPT message within the next 10s?

–>

MODIFY EPS BEARER CONTEXT ACCEPT

2

F

15

Void

16a1

Void

Note: T3421 value is specified as 15s in TS 24.301. If the UE supports CE mode B and UEs usage setting is not voice centric, T3421 takes a value of 45s (see TS 24.301 Table 10.2.1)

9.2.2.1.6.3.3 Specific message contents

Table 9.2.2.1.6.3.3-1: DETACH REQUEST (steps 2, 4, 6, 8 and 10 Table 9.2.2.1.6.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

001 or 011

EPS detach or combined EPS/IMSI detach

Switch off

0

normal detach

GUTI or IMSI

GUTI-1

Table 9.2.2.1.6.3.3-2: Void

9.2.2.1.7 UE initiated detach / Abnormal case / Detach procedure collision

9.2.2.1.7.1 Test Purpose (TP)

(1)

with { UE in EMM-DEREGISTERED-INITIATED state }

ensure that {

when { the UE receives the DETACH REQUEST message from the network }

then { the UE aborts the UE initiated detach procedure and completes the network initiated detach procedure }

}

(2)

with { UE in EMM-DEREGISTERED state }

ensure that {

when { the UE has completed the network initiated detach procedure with re-attach required and the UE supports re-attach after DETACH collision }

then { the UE initiates the attach procedure }

}

(3)

with { UE in EMM-DEREGISTERED state }

ensure that {

when { the UE has completed the network initiated detach procedure with re-attach required and the UE does not support re-attach after DETACH collision }

then { the UE does not initiate the attach procedure }

}

9.2.2.1.7.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.2.2.4 and 5.5.2.3.2.

[TS 24.301, clause 5.5.2.2.4]

The following abnormal cases can be identified:

d) Detach procedure collision

If the UE receives a DETACH REQUEST message before the UE initiated detach procedure has been completed, it shall treat the message as specified in subclause 5.5.2.3.2 with the following modification: if the DETACH REQUEST message received by the UE contains detach type "re-attach required", and the UE initiated detach procedure is with detach type "EPS detach" or "combined EPS/IMSI detach", the UE need not initiate the attach or combined attach procedure.

[TS 24.301, clause 5.5.2.3.2]

When receiving the DETACH REQUEST message and the detach type indicates "re-attach required", the UE shall deactivate the EPS bearer context(s) including the default EPS bearer context locally without peer-to-peer signalling between the UE and the MME. The UE shall then send a DETACH ACCEPT message to the network and enter state EMM-DEREGISTERED. Furthermore, the UE shall, after the completion of the detach procedure, and the existing NAS signalling connection has been released, initiate an attach or combined attach procedure.

NOTE 1: When detach type indicates "re-attach required", user interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically.

9.2.2.1.7.3 Test description

9.2.2.1.7.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Registered, Idle mode (State 2) according to TS 36.508 [18].

9.2.2.1.7.3.2 Test procedure sequence

Table 9.2.2.1.7.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause UE to initiate detach.

1A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

2

The UE transmits a DETACH REQUEST message. The UE starts timer T3421.

–>

DETACH REQUEST

3

The SS does not respond to the DETACH REQUEST message.

4

With T3421 still running the SS shall send DETACH REQUEST message with the Detach type IE indicating "re-attach required".

<–

DETACH REQUEST

5

Check: Does the UE transmit a DETACH ACCEPT message?

–>

DETACH ACCEPT

1

P

6

The SS releases the RRC connection.

EXCEPTION: Step 7a1-7b1 describe a behaviour which depends on the UE capability

7a1

Void

7a2

IF pc_Re_Attach_AfterDetachColl THEN

Check: Does the UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message?

–>

ATTACH REQUEST

2

P

7a3-7a14

The attach procedure is completed by executing steps 5 to 16 of the UE registration procedure in TS 36.508 sub clause 4.5.2.3.

7a15

Cause UE to initiate detach.

7a15A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

7a16

The UE transmits a DETACH REQUEST with the Detach Type IE indicating "normal detach" and "combined EPS/IMSI detach" or "EPS detach" depending on the UE configuration.

–>

DETACH REQUEST

7a17

The SS responds with DETACH ACCEPT message

<–

DETACH ACCEPT

7a18

The SS releases the RRC connection

7b1

ELSE Check: Does the UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message in the next 30s?

–>

ATTACH REQUEST

3

F

At the end of this test procedure sequence, the UE is in end state E-UTRA deregistered (E4) according to TS 36.508.

9.2.2.1.7.3.3 Specific message contents

Table 9.2.2.1.7.3.3-1: DETACH REQUEST (steps 2 and 7a16 Table 9.2.2.1.7.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

001 or 011

EPS detach or combined EPS/IMSI detach

Switch off

0

normal detach

GUTI or IMSI

GUTI-1

Table 9.2.2.1.7.3.3-2: DETACH REQUEST (step 4 Table 9.2.2.1.7.3.2-1)

Derivation Path: 36.508, Table 4.7.2-12

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

001

re-attach required

Table 9.2.2.1.7.3.3-3: Message ATTACH REQUEST (step 7a2, Table 9.2.2.1.7.3.2-1)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/Remark

Comment

Condition

EPS attach type

0001 or 0010

EPS attach or combined EPS/IMSI attach

9.2.2.1.8 UE initiated detach / Abnormal case / Detach and EMM common procedure collision

9.2.2.1.8.1 Test Purpose (TP)

(1)

with { UE in EMM-DEREGISTERED-INITIATED state due to switch off }

ensure that {

when { the UE receives an EMM common procedure message from the network }

then { the UE ignores the message and continues the detach procedure }

}

(2)

with { UE in EMM-DEREGISTERED-INITIATED state due to normal detach }

ensure that {

when { the UE receives GUTI REALLOCATION COMMAND from the network }

then { the UE ignores the message and continues the detach procedure }

}

(3)

with { UE in EMM-DEREGISTERED-INITIATED state due to normal detach }

ensure that {

when { the UE receives AUTHENTICATION REQUEST, SECURITY MODE COMMAND or IDENTITY REQUEST message from the network }

then { the UE responds to the message and then continues the detach procedure }

}

9.2.2.1.8.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.2.2.4.

[TS 24.301, clause 5.5.2.2.4]

The following abnormal cases can be identified:

e) Detach and EMM common procedure collision

Detach containing cause "switch off":

– If the UE receives a message used in an EMM common procedure before the detach procedure has been completed, this message shall be ignored and the detach procedure shall continue

Detach containing other causes than "switch off":

– If the UE receives a GUTI REALLOCATION COMMAND, an EMM STATUS or an EMM INFORMATION message before the detach procedure is completed, this message shall be ignored and the detach procedure shall continue.

– If the UE receives an AUTHENTICATION REQUEST, SECURITY MODE COMMAND or IDENTITY REQUEST message before the detach procedure has been completed, the UE shall respond to it as described in subclause 5.4.2, 5.4.3 and 5.4.4 respectively and the detach procedure shall continue.

9.2.2.1.8.3 Test description

9.2.2.1.8.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Registered, Idle mode (State 2) according to TS 36.508[18].

9.2.2.1.8.3.2 Test procedure sequence

Table 9.2.2.1.8.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause switch off.

1A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

2

The UE transmits a DETACH REQUEST message with the Detach type IE indicating “switch off”.

–>

DETACH REQUEST

3

The SS transmits a GUTI REALLOCATION COMMAND message.

<–

GUTI REALLOCATION COMMAND

4

Check: Does the UE transmit an GUTI REALLOCATION COMPLETE message?

–>

GUTI REALLOCATION COMPLETE

1

F

5

Check: Does the test result of the generic procedure in TS 36.508 subclause 6.4.2.5 indicates that the UE responds to paging when paged with S-TMSI included in GUTI-1 and with CN domain indicator set to "PS"?

1

6

The UE is switched on and performs an ATTACH procedure.

7

Cause UE to initiate detach.

7A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

8

The UE transmits a DETACH REQUEST message? ((The UE starts timer T3421)

–>

DETACH REQUEST

2

P

9

The SS does not respond to the DETACH REQUEST message.

10

With T3421 still running the SS shall send GUTI REALLOCATION COMMAND.

<–

GUTI REALLOCATION COMMAND

11

Check: Does the UE transmit a GUTI REALLOCATION COMPLETE message?

–>

GUTI REALLOCATION COMPLETE

2

F

12

SS responds with DETACH ACCEPT message.

<–

DETACH ACCEPT

13

The SS releases the RRC connection.

14

Cause UE to initiate attach. The generic procedure in 36.508 clause 4.5.2.3-1 is executed so as to complete the attach procedure (Note).

15

Cause UE to initiate detach.

15A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

16

The UE transmits a DETACH REQUEST message? (The UE starts timer T3421. )

–>

DETACH REQUEST

17

The SS does not respond to the DETACH REQUEST message.

18

With T3421 still running the SS shall send AUTHENTICATION REQUEST.

<–

AUTHENTICATION REQUEST

19

Check: Does the UE transmit an AUTHENTICATION RESPONSE message?

–>

AUTHENTICATION RESPONSE

3

P

20

SS responds with DETACH ACCEPT message.

<–

DETACH ACCEPT

21

The SS releases the RRC connection.

22

Cause UE to initiate attach. The generic procedure in 36.508 clause 4.5.2.3-1 is executed so as to complete the attach procedure (Note).

23

Cause UE to initiate detach.

23A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

24

The UE transmits a DETACH REQUEST message? (The UE starts timer T3421. )

–>

DETACH REQUEST

25

The SS does not respond to the DETACH REQUEST message.

26

With T3421 still running the SS shall send SECURITY MODE COMMAND.

<–

SECURITY MODE COMMAND

27

Check: Does the UE transmit a SECURITY MODE COMPLETE message?

–>

SECURITY MODE COMPLETE

3

P

28

SS responds with DETACH ACCEPT message.

<–

DETACH ACCEPT

29

The SS releases the RRC connection.

30

Cause UE to initiate attach. The generic procedure in 36.508 clause 4.5.2.3-1 is executed so as to complete the attach procedure (Note).

31

Cause UE to initiate detach.

31A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

32

The UE transmits a DETACH REQUEST message? (The UE starts timer T3421)

–>

DETACH REQUEST

33

The SS does not respond to the DETACH REQUEST message.

34

With T3421 still running the SS shall send IDENTITY REQUEST.

<–

IDENTITY REQUEST

35

Check: Does the UE transmit an IDENTITY RESPONSE message?

–>

IDENTITY RESPONSE

3

P

36

SS responds with DETACH ACCEPT message.

<–

DETACH ACCEPT

37

The SS releases the RRC connection.

Note: The request is triggered by either of the following AT commands, depending on UE capability:
– IF pc_KeepEpsBearerParametersAfterNormalDetach THEN AT command AT+CGATT=1, or
– ELSE AT command AT+CGDCONT=1,”IP” followed by AT+CGACT=1

9.2.2.1.8.3.3 Specific message contents

Table 9.2.2.1.8.3.3-1: DETACH REQUEST (steps 8, 16, 24 and 32 Table 9.2.2.1.8.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

001 or 011

EPS detach or combined EPS/IMSI detach

Switch off

0

normal detach

Table 9.2.2.1.8.3.3-2: GUTI REALLOCATION COMMAND (step 3 Table 9.2.2.1.8.3.2-1)

Derivation Path: 36.508, Table 4.7.2-15

Information Element

Value/remark

Comment

Condition

GUTI

GUTI-2

TAI list

Not present

Table 9.2.2.1.8.3.3-3: GUTI REALLOCATION COMMAND (step 10 Table 9.2.2.1.8.3.2-1)

Derivation Path: 36.508, Table 4.7.2-15

Information Element

Value/remark

Comment

Condition

GUTI

GUTI-3

TAI list

Not present

Table 9.2.2.1.8.3.3-4: Message ATTACH REQUEST (steps 14, 22 and 30, Table 9.2.2.1.8.3.2-1)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/Remark

Comment

Condition

EPS attach type

0001 or 0010

EPS attach or combined EPS/IMSI attach

9.2.2.1.9 UE initiated detach / Abnormal case / Change of cell into a new tracking area

9.2.2.1.9.1 Test Purpose (TP)

(1)

with { UE in EMM-DEREGISTERED-INITIATED state }

ensure that {

when { the UE changes into a new tracking area that is not in the stored TAI list }

then { the UE aborts the detach procedure and initiates a Tracking Area Updating procedure }

}

(2)

with { UE in EMM-TRACKING-AREA-UPDATING-INITIATED state }

ensure that {

when { the UE receives TRACKING AREA UPDATE ACCEPT message }

then { the UE re-initiates the detach procedure after completing the Tracking Area Updating procedure }

}

9.2.2.1.9.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.2.2.4.

[TS 24.301, clause 5.5.2.2.4]

The following abnormal cases can be identified:

b) Lower layer failure or release of the NAS signalling connection before reception of DETACH ACCEPT message

The detach procedure shall be aborted, and the UE shall enter state:

– EMM-REGISTERED.NORMAL-SERVICE and MM-NULL if "IMSI detach" was requested;

– EMM-DEREGISTERED if "EPS detach" was requested;

– EMM-DEREGISTERED and MM-NULL if "combined EPS/IMSI detach" was requested.

f) Change of cell into a new tracking area

If a cell change into a new tracking area that is not in the stored TAI list occurs before the UE initiated detach procedure is completed, the detach procedure shall be aborted and re-initiated after successfully performing a tracking area updating procedure. If the detach procedure was initiated due to removal of the USIM, the UE shall abort the detach procedure and enter the state EMM-DEREGISTERED.

9.2.2.1.9.3 Test description

9.2.2.1.9.3.1 Pre-test conditions

System Simulator:

– cell A belongs to TAI-1 (home PLMN) is set to ”Serving cell”

– cell B belongs to TAI-2 (home PLMN) is set to ”Non-Suitable cell”.

– System information combination 3 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 Generic RB established (state 3) according to TS 36.508 [18].

9.2.2.1.9.3.2 Test procedure sequence

Table 9.2.2.1.9.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

The following messages are to be observed on Cell A unless explicitly stated otherwise.

1

Cause UE to initiate detach.

1A

UE may optionally perform IMS de-registration using the generic procedure defined in 34.229-1 [35] Annex C.30.

2

The UE transmits a DETACH REQUEST message. (The UE starts timer T3421)

–>

DETACH REQUEST

3

The SS does not respond to the DETACH REQUEST message.

4

Set the cell type of cell A to the ”Suitable neighbour cell”.

Set the cell type of cell B to the ”Serving cell”.

Note: T3421 value is specified as 15s in TS 24.301 and it is assumed that SS can configure cells within this time.

4A

The SS transmits an RRCConnectionReconfiguration message on Cell A to order the UE to perform intra frequency handover to Cell B.

<–

4B

The UE transmits an RRCConnectionReconfigurationComplete message on Cell B to confirm the successful completion of the intra frequency handover.

–>

The following messages are to be observed on Cell B unless explicitly stated otherwise.

5

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

–>

TRACKING AREA UPDATE REQUEST

1

P

6

The SS transmits a TRACKING AREA UPDATE ACCEPT message.

<–

TRACKING AREA UPDATE ACCEPT

7

Check: Does the UE transmit a TRACKING AREA UPDATE COMPLETE message?

–>

TRACKING AREA UPDATE COMPLETE

8

The UE transmits a DETACH REQUEST message.

–>

DETACH REQUEST

2

P

9

SS responds with DETACH ACCEPT message

<–

DETACH ACCEPT

10

Check: Does the test result of the generic procedure in TS 36.508 subclause 6.4.2.5 indicates that the UE responds to paging when paged with S-TMSI included in GUTI-2 and with CN domain indicator set to "PS"?

2

9.2.2.1.9.3.3 Specific message contents

Table 9.2.2.1.9.3.3-1: DETACH REQUEST (step 2, Table 9.2.2.1.9.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

001 or 011

EPS detach or combined EPS/IMSI detach

Switch off

0

normal detach

GUTI or IMSI

GUTI-1

Table 9.2.2.1.9.3.3-2: Message TRACKING AREA UPDATE ACCEPT (step 6, Table 9.2.2.1.9.3.2-1)

Derivation path: 36.508 table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

GUTI

GUTI-2

Table 9.2.2.1.9.3.3-3: RRCConnectionReconfiguration (step 4a, Table 9.2.2.1.9.3.2-1)

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

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo SEQUENCE {

MobilityControlInfo-HO

targetPhysCellId

PhysicalCellIdentity of Cell B (see 36.508 clause 4.6.5)

carrierFreq

Not present

}

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell B

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 9.2.2.1.9.3.3-4: Message TRACKING AREA UPDATE REQUEST (step 5, Table 9.2.2.1.9.3.2-1)

Derivation path: 36.508 table 4.7.2-27

Information Element

Value/Remark

Comment

Condition

EPS update type

Active Flag

Any allowed value

EPS bearer context status

Not present or (octet 3 = ‘00100000’B and octet 4 = ‘00000000’B) or (octet 3 = ‘00000000’B and octet 4 = ‘00000000’B)

Table 9.2.2.1.9.3.3-5: DETACH REQUEST (step 8, Table 9.2.2.1.9.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11

Information Element

Value/remark

Comment

Condition

Detach type

Type of detach

001 or 011

EPS detach or combined EPS/IMSI detach

Switch off

0

normal detach

GUTI or IMSI

GUTI-2

9.2.2.1.10 UE initiated detach / Mapped security context

9.2.2.1.10.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state }

ensure that {

when { the UE sent the last DETACH REQUEST }

then { the UE delete the mapped security context }

}

9.2.2.1.10.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.2.1 and 5.5.3.3.2. Unless otherwise stated these are rel-8 requirements.

[TS 24.301, clause 5.5.2.1]

Upon successful completion of the detach procedure, if the UE and the MME enter the EMM-DEREGISTERED state, the UE and the MME shall delete any mapped EPS security context or partial native EPS security context.

[Rel-12]

[TS 24.301, clause 5.5.3.3.2]

The UE operating in CS/PS mode 1 or CS/PS mode 2, in state EMM-REGISTERED, shall initiate the combined tracking area updating procedure:

d) when the UE performs an intersystem change from A/Gb or Iu mode to S1 mode, and the UE previously either performed a combined GPRS attach procedure, an IMSI attach procedure, a location area updating procedure or a combined routing area updating procedure, in A/Gb or Iu mode, or moved to A/Gb or Iu mode from S1 mode through an SRVCC handover or moved to Iu mode from S1 mode through an vSRVCC handover. In this case the EPS update type IE shall be set to "combined TA/LA updating with IMSI attach";

9.2.2.1.10.3 Test description

9.2.2.1.10.3.1 Pre-test conditions

System Simulator:

– Cell A 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 Switched OFF (state 1) according to TS 36.508 [18].

9.2.2.1.10.3.2 Test procedure sequence

Table 9.2.2.1.10.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U -S

Message

The SS configures:

– Cell 5 as a "Non-Suitable Off cell".

– Cell A as the "Serving cell".

1

The UE is switched on.

2

The UE transmits an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message.

–>

ATTACH REQUEST

2A-2D

Steps 5 to 8 from procedure 4.5.2.3 in TS 36.508.

3

The SS transmits an ATTACH REJECT message with EMM cause = "EPS services and non-EPS services not allowed" as specified.

<–

ATTACH REJECT

4

The SS releases the RRC connection.

5

If possible (see ICS) switch off is performed or the USIM is removed.

Otherwise the power is removed.

6

The SS configures:

– Cell A as a "Non-Suitable Off cell".

– Cell 5 as the "Serving cell".

7

The UE is brought back to operation or the USIM is inserted.

8

The UE transmits an ATTACH REQUEST message on Cell 5

–>

ATTACH REQUEST

9

The SS transmits an AUTHENTICATION AND CIPHERING REQUEST message.

<–

AUTHENTICATION AND CIPHERING REQUEST

10

The UE transmits an AUTHENTICATION AND CIPHERING RESPONSE message.

–>

AUTHENTICATION AND CIPHERING RESPONSE

11

SS responds with ATTACH ACCEPT message including P-TMSI-1 and RAI-1.

<–

ATTACH ACCEPT

12

The UE transmits an ATTACH COMPLETE message.

–>

ATTACH COMPLETE

12A

The SS releases the RRC connection.

12B

Generic test procedure in TS 36.508 subclause 4.5A.3A.2 is performed

13

The activation of a PDP context is triggered by MMI or AT command.

14

Generic test procedure in TS 34.108 subclause 7.2.4.2.3 is performed on Cell 5.

NOTE: The UE performs Radio Bearer Establishment in a UTRAN cell.

15

The SS releases the RRC connection.

16

The SS configures:

– Cell A as the "Serving cell".

– Cell 5 as a "Non-Suitable cell".

17 – 24

Generic test procedure in TS 36.508 subclause 6.4.2.7A-1 is performed. (step 1 to 8)

Exception: Steps 24A to 24Aa5/24Ab1 describe optional behaviour that depend on the UE capability.

24A

If pc_IMS = TRUE SS starts 10s timer

24Aa1

The UE establishes an RRC connection and transmits a SERVICE REQUEST message

24Aa2

The SS establishes SRB2 and DRB

24Aa3

If MULTI-PDN = TRUE the UE executes the generic procedure for establishment of additional PDN connectivity defined in TS 36.508 4.5A.16.3.

24Aa4

The UE performs IMS registration using the generic procedure defined in 34.229-1 [35] Annex C.2 steps 4-11.

24Aa5

The SS releases the RRC connection

24Ab1

The 10s timer expires

25

If possible (see ICS) switch off is performed or the USIM is removed.

Otherwise the power is removed.

EXCEPTION: Step 25 describes behaviour that depends on the UE capability.

26

If pc_SwitchOnOff or pc_USIM_Removal then UE send DETACH REQUEST message.

–>

DETACH REQUEST

27

The SS configures:

– Cell A as the "Serving cell".

– Cell 5 as a "Non-Suitable Off cell".

28

The UE is brought back to operation or the USIM is inserted.

The following messages shall be received on cell A.

29

Cause UE to initiate attach

Check: Does the UE send ATTACH REQUEST message

–>

ATTACH REQUEST

1

P

30-43b1

The attach procedure is completed by executing steps 5 to 18b1 of the UE registration procedure in TS 36.508 sub clause 4.5.2.3.

At the end of this test procedure sequence, the UE is in end state E-UTRA idle (E1) according to TS 36.508.

9.2.2.1.10.3.3 Specific message contents

Table 9.2.1.1.10.3.3-1: Message ATTACH REJECT (step 3, Table 9.2.2.1.10.3.2-1)

Derivation path: 36.508 table 4.7.2-3

Information Element

Value/Remark

Comment

Condition

EMM cause

00001000

#8 "EPS services and non-EPS services not allowed"

ESM message container

Not present

Table 9.2.2.1.10.3.3-2: ATTACH REQUEST (step 29, Table 9.2.2.1.10.3.2-1)

Information Element

Value/remark

Comment

Condition

NAS key set identifier

‘111’

no key is available

9.2.2.2 Network initiated detach procedure

9.2.2.2.1 NW initiated detach / Re-attach required

9.2.2.2.1.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state }

ensure that {
when { SS sends DETACH REQUEST message with the Detach type IE "re-attach required" }

then { UE sends DETACH ACCEPT message and UE initiates an attach procedure with the current EPS security context}

}

9.2.2.2.1.2 Conformance requirements

References: The conformance requirement covered in the present TC is specified in: 3GPP TS 24.301 clauses 5.5.2.3.2.

[TS 24.301 clause5.5.2.3.2]

When receiving the DETACH REQUEST message and the detach type indicates "re-attach required", the UE shall deactivate the EPS bearer context(s) including the default EPS bearer context locally without peer-to-peer signalling between the UE and the MME. The UE shall then send a DETACH ACCEPT message to the network and enter state EMM-DEREGISTERED. Furthermore, the UE shall, after the completion of the detach procedure, and the existing NAS signalling connection has been released, initiate an attach or combined attach procedure.

NOTE 1: When detach type indicates "re-attach required", user interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically.

A UE which receives a DETACH REQUEST message with detach type indicating "re-attach required" or "re-attach not required" and no EMM cause IE, is detached only for EPS services.

…If the detach type indicates "IMSI detach" or "re-attach required" then the UE shall ignore the EMM cause IE if received.

9.2.2.2.1.3 Test description

9.2.2.2.1.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Generic RB established (state 3) on cell A according to TS 36.508 [18].

9.2.2.2.1.3.2 Test procedure sequence

Table 9.2.2.2.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

1

The SS initiates Detach procedure with the Detach Type IE "re-attach required"

<–

DETACH REQUEST

2

Check: Does the UE send DETACH ACCEPT message?

–>

DETACH ACCEPT

1

P

3

The SS releases RRC connection.

EXCEPTION: Step 3a describes a behaviour which depends on the UE capability

3a

IF NOT pc_Automatic_Re_Attach, the user initiates an attach by MMI or by AT command.

4

Check: Does the UE send ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message?

–>

ATTACH REQUEST

1

P

4Aa1-4Aa2

Void

4Ba1-4D

Steps 9a1-11 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.

5

The SS sends ATTACH ACCEPT to assign the new GUTI (GUTI-2). The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message

<–

ATTACH ACCEPT

EXCEPTION: In parallel to the event described in step 6 below, if initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

EXCEPTION: IF PDN1_IMS THEN in parallel to the event described in step 6 below the generic procedure for IMS signalling in the U-plane specified in TS 36.508 subclause 4.5A.3 takes place if requested by the UE

6

Check: Does the UE send ATTACH COMPLETE message including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?

–>

ATTACH COMPLETE

1

P

7a1 – 9b1

Steps 16a1-18b1 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.

9.2.2.2.1.3.3 Specific message contents

Table 9.2.2.2.1.3.3-1: Message DETACH REQUEST (step 1, Table 9.2.2.2.1.3.2-1)

Derivation path: 36.508 table 4.7.2-12

Information Element

Value/Remark

Comment

Condition

Detach type

‘001’B

"re-attach required"

Table 9.2.2.2.1.3.3-2: Message ATTACH REQUEST (step 4, Table 9.2.2.2.1.3.2-1)

Derivation path: 36.508 table 4.7.2-4

Information Element

Value/Remark

Comment

Condition

NAS key set identifier

TSC

‘0’B

native security context

NAS key set identifier

The value is a same value to be allocated by SS in Preamble.

Old GUTI or IMSI

GUTI-1

NOTE: This message is sent within the SECURITY NAS PROTECTED MESSAGE in Table 9.2.2.2.1.3.3-3.

Table 9.2.2.2.1.3.3-3: Message SECURITY PROTECTED NAS MESSAGE (step 4, Table 9.2.2.2.1.3.2-1)

Derivation Path: 36.508 Table 4.7.1-1

Information Element

Value/remark

Comment

Condition

Security header type

‘0001’B

Integrity protected

NAS message

‘01000001’B

”ATTACH REQUEST”

Table 9.2.2.2.1.3.3-4: Message ATTACH ACCEPT (step 5, Table 9.2.2.2.1.3.2-1)

Derivation path: 36.508 table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

TAI list

Length of tracking area identity list contents

‘00000110’B

6 octets

Number of elements

‘00000’B

1 element

Type of list

‘00’B

"list of TACs belonging to one PLMN, with non-consecutive TAC values"

Partial tracking area identity list

TAI-1

GUTI

GUTI-2

9.2.2.2.2 NW initiated detach / IMSI detach

9.2.2.2.2.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state }

ensure that {
when { UE receives DETACH REQUEST message with the Detach type IE = “IMSI detach” }

then { UE sends TRACKING AREA UPDATE REQUEST message with EPS update type IE = “Combined TA/LA updating with IMSI attach” }

}

(2)

with { UE in EMM-TRACKING-AREA-UPDATING-INITIATED state }

ensure that {
when { UE receives TRACKING AREA UPDATE ACCEPT message }

then { UE enters EMM-REGISTERED and enters MM IDLE and sends TRACKING AREA UPDATE COMPLETE message and re-attaches for non-EPS services }

}

9.2.2.2.2.2 Conformance requirements

References: The conformance requirement covered in the present TC is specified in: 3GPP TS 24.301 clauses 5.5.2.3.2. Unless otherwise stated these are Rel-8 requirements.

[TS 24.301 clause 5.5.2.3.2]

When receiving the DETACH REQUEST message and the Detach type IE indicates "IMSI detach", the UE shall not deactivate the EPS bearer context(s) including the default EPS bearer context. The UE shall set the MM update status to U2 NOT UPDATED. A UE may send a DETACH ACCEPT message to the network, and shall re-attach to non-EPS services by performing the combined tracking area updating procedure according to subclause 5.5.3.3, sending a TRACKING AREA UPDATE REQUEST message with EPS update type IE indicating "combined TA/LA updating with IMSI attach".

9.2.2.2.2.3 Test description

9.2.2.2.2.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

– the UE is configured to initiate combined EPS/IMSI attach.

Preamble:

– the UE is in state Generic RB established (state 3) on cell A according to TS 36.508 [18].

9.2.2.2.2.3.2 Test procedure sequence

Table 9.2.2.2.2.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

1

The SS sends DETACH REQUEST with the Detach Type IE “IMSI detach”.

<–

DETACH REQUEST

EXCEPTION: Step 2a1 describes behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported..

2 a1

IF the UE supports indication that the detach procedure has been accepted THEN the UE sends DETACH ACCEPT message.

–>

DETACH ACCEPT

3

Check: Does the UE send TRACKING AREA UPDATE REQUEST message?

–>

TRACKING AREA UPDATE REQUEST

1

P

4-5

Void

6

The SS sends TRACKING AREA UPDATE ACCEPT message.

<–

TRACKING AREA UPDATE ACCEPT

7

Check: Does the UE send TRACKING AREA UPDATE COMPLETE message?

–>

TRACKING AREA UPDATE COMPLETE

2

P

8

The SS releases the RRC connection.

EXCEPTION: Step 9a1 to 9a6 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.

9 a1

IF pc_CS_fallback THEN SS pages the UE with S-TMSI2 for CS domain.

EXCEPTION: Step 9 a2a1 describes behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.

9 a2a1

IF the UE needs to request upper layer input before accepting the CS fallback (see ICS), THEN the incoming CS call is accepted at the UE through MMI or AT command.

9 a3

Check: Does the UE respond to paging by sending an EXTENDED SERVICE REQUEST message?

–>

EXTENDED SERVICE REQUEST

2

P

9 a4

The SS transmits SERVICE REJECT message.

<–

SERVICE REJECT

9 a5

The SS releases the RRC connection.

EXCEPTION: The behaviour in table 9.2.2.2.2.3.2-2 may occur in parallel with step 9 a6.

9 a6

The SS waits for 60 seconds (T3442 value provided in step 9a4.

Note: The value 60 sec is chosen to allow sufficient time if the parallel behaviour occurs to be handled before going to the next step.)

10

Check: Does the UE respond to paging with S-TMSI2 for PS domain?

Generic Procedure (TS 36.508 subclause 6.4.2.4)

2

Table 9.2.2.2.2.3.2-2: Parallel Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

1

The UE transmits a TRACKING AREA UPDATE REQUEST message.

–>

TRACKING AREA UPDATE REQUEST

2

The SS transmits a TRACKING AREA UPDATE ACCEPT message.

<–

TRACKING AREA UPDATE ACCEPT

3

The SS releases the RRC connection.

9.2.2.2.2.3.3 Specific message contents

Table 9.2.2.2.2.3.3-1: Message DETACH REQUEST (step 1, Table 9.2.2.2.2.3.2-1)

Derivation path: 36.508 table 4.7.2-12

Information Element

Value/Remark

Comment

Condition

Detach type

‘011’B

“IMSI detach”

EMM cause

Not present

Table 9.2.2.2.2.3.3-2: Message TRACKING AREA UPDATE REQUEST (step 3, Table 9.2.2.2.2.3.2-1)

Derivation path: 36.508 table 4.7.2-27

Information Element

Value/Remark

Comment

Condition

EPS update type

EPS update type value

‘010’B

“Combined TA/LA updating with IMSI attach”

Old GUTI

GUTI-1

Last visited registered TAI

TAI-1

Table 9.2.2.2.2.3.3-3: Message TRACKING AREA UPDATE ACCEPT (step 6, Table 9.2.2.2.2.3.2-1)

Derivation path: 36.508 table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

GUTI

GUTI-2

TAI list

Length of tracking area identity list contents

‘00000110’B

Partial tracking area identity list 1

1 element, TAI-1

Location area identification

LAI-1

MS identity

TMSI-1

Table 9.2.2.2.2.3.3-4: Message EXTENDED SERVICE REQUEST (step 9a3, Table 9.2.2.2.2.3.2-1)

Derivation Path: 36.508 table 4.7.2-14A

Information Element

Value/remark

Comment

Condition

M-TMSI

M-TMSI1

”M-TMSI1 is a part of GUTI-1”

Table 9.2.2.2.2.3.3-5: Message SERVICE REJECT (step 9a4, Table 9.2.2.2.2.3.2-1)

Derivation Path: 36.508 table 4.7.2-22

Information Element

Value/remark

Comment

Condition

EMM cause

‘0010 0111’B

#39 ‘CS domain temporarily not available’

T3442 value

‘0010 0001’B

60 sec

Table 9.2.2.2.2.3.3-6: Message TRACKING AREA UPDATE ACCEPT (step 2, Table 9.2.2.2.2.3.2-2)

Derivation path: 36.508 table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

GUTI

Not present

MS identity

Not present

9.2.2.2.3 Void
9.2.2.2.4 Void
9.2.2.2.5 Void
9.2.2.2.6 Void
9.2.2.2.7 Void
9.2.2.2.8 Void
9.2.2.2.9 Void
9.2.2.2.10 Void
9.2.2.2.11 Void
9.2.2.2.12 Void
9.2.2.2.13 Void
9.2.2.2.14 NW initiated detach / Abnormal case / EMM cause not included

9.2.2.2.14.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state }

ensure that {

when { UE receives a DETACH REQUEST message with the Detach type IE “re-attach not required” and with no EMM cause IE included }

then { UE delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, KSI, set the update status to EU2 NOT UPDATED and start timer T3402. when T3402 expired, the UE attempts to attach again }

}

9.2.2.2.14.2 Conformance requirements

References: The conformance requirement covered in the present TC is specified in: 3GPP TS 24.301 clauses 5.5.2.3.4.

[TS 24.301 clause5.5.2.3.4]

The following abnormal cases can be identified:

b) DETACH REQUEST, other EMM cause values than those treated in subclause 5.5.2.3.2 or no EMM cause IE is included, and the Detach type IE indicates "re-attach not required".

The UE shall delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, KSI, shall set the update status to EU2 NOT UPDATED and shall start timer T3402. The UE may enter the state EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [6]; otherwise the UE shall enter the state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH.

9.2.2.2.14.3 Test description

9.2.2.2.14.3.1 Pre-test conditions

System Simulator:

– cell I (VPLMN and set as a serving cell) configured according to table 6.3.2.2-3 in TS 36.508 [18].

UE:

None.

Preamble:

– the UE is in state Generic RB established (state 3) on cell I according to TS 36.508 [18];

– T3402 in the UE is set to 2 minutes.

9.2.2.2.14.3.2 Test procedure sequence

Table 9.2.2.2.14.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

1

SS initiates Detach procedure with the Detach Type IE “re-attach not required” and no EMM cause IE included

<–

DETACH REQUEST

2

The UE transmits a DETACH ACCEPT message on Cell I.

Note: Now UE should start timer T3402

–>

DETACH ACCEPT

3

The SS releases the RRC connection.

4

Check: When the timer T3402 expires does the UE transmit ATTACH REQUEST message on cell I?

–>

ATTACH REQUEST

1

P

5-18b1

The attach procedure is completed by executing steps 5 to 18b1 of the UE registration procedure in TS 36.508 sub clause 4.5.2.3.

At the end of this test procedure sequence, the UE is in end state E-UTRA connected (E2) according to TS 36.508.

9.2.2.2.14.3.3 Specific message contents

Table 9.2.2.2.14.3.3-1: Message DETACH REQUEST (step 1, Table 9.2.2.2.14.3.2-1)

Derivation path: 36.508 table 4.7.2-12

Information Element

Value/Remark

Comment

Condition

Detach type

‘010’B

“re-attach not required”

EMM cause

Not present

Table 9.2.2.2.14.3.3-2: Message ATTACH REQUEST (step 4, Table 9.2.2.2.14.3.2-1)

Derivation Path: TS 36.508 Table 4.7.2-4

Information Element

Value/remark

Comment

Condition

NAS key set identifier

NAS key set identifier

‘111’B

no key is available

TSC

Any allowed value

TSC does not apply for NAS key set identifier value "111".

Old GUTI or IMSI

IMSI1

Last visited registered TAI

Not present

Table 9.2.2.2.14.3.3-3: Message ATTACH ACCEPT (preamble, 9.2.2.2.14.3.1)

Derivation path: 36.508 table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

T3402 value

2 minute

The default value is 12 minutes, use 2 minute to shorten the whole TC execute time