9.1.6 De-registration

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

9.1.6.1 UE-initiated de-registration

9.1.6.1.1 UE-initiated de-registration / Switch off / Abnormal / De-registration and 5GMM common procedure collision

9.1.6.1.1.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED state }

ensure that {

when { the UE is switched off }

then { the UE shall send DEREGISTRATION REQUEST message with De-registration type IE indicated to "Switch off" }

}

(2)

with { the UE in 5GMM-DEREGISTERED-INITIATED state }

ensure that {

when { the UE receives a DEREGISTRATION REQUEST message before the UE-initiated de-registration procedure has been completed }

then { the UE ignores the message and shall continue de-registration procedure }

}

(3)

with { the UE in 5GMM-DEREGISTERED-INITIATED state }

ensure that {

when { the UE receives a 5GMM common procedure before the UE-initiated de-registration procedure has been completed }

then { the UE ignores the message and shall continue de-registration procedure }

}

(4)

with { the UE supports remove USIM without power down and in 5GMM-REGISTERED state }

ensure that {

when { the USIM is removed from the UE }

then { the UE shall send DEREGISTRATION REQUEST message with De-registration type IE indicated to "Switch off" }

}

9.1.6.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 5.5.2.1, 5.5.2.2.1 and 5.5.2.2.6. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.2.1]

The de-registration procedure is used:

a) by the UE to de-register for 5GS services over 3GPP access when the UE is registered over 3GPP access;;

b) by the UE to de-register for 5GS services over 3GPP access, non-3GPP access, or both when the UE is registered in the same PLMN over both accesses;

c) by the network to inform the UE that it is deregistered for 5GS services over 3GPP access when the UE is registered over 3GPP access;

d) by the network to inform the UE that it is deregistered for 5GS services over 3GPP access, non-3GPP access, or both when the UE is registered in the same PLMN over both accesses; and

e) by the network to inform the UE to re-register to the network.

The de-registration procedure with appropriate de-registration type shall be invoked by the UE:

a) if the UE is switched off; and

b) as part of the eCall inactivity procedure defined in subclause 5.5.3.

The de-registration procedure with appropriate de-registration type shall be invoked by the network:

a) if the network informs whether the UE should re-register to the network.

The de-registration procedure with appropriate access type shall be invoked by the UE:

a) if the UE wants to de-register for 5GS services over 3GPP access when the UE is registered over 3GPP access; or

b) the UE wants to de-register for 5GS services over 3GPP access, non-3GPP access, or both when the UE is registered in the same PLMN over both accesses.

If the de-registration procedure is triggered due to USIM removal, the UE shall indicate "switch off" in the de-registration type IE.

If the de-registration procedure is requested by the UDM for a UE that has an emergency PDU session, the AMF shall not send a DEREGISTRATION REQUEST message to the UE.

If the de-registration procedure for 5GS services is performed, the PDU sessions, if any, for this particular UE are released locally without peer-to-peer signalling between the UE and the network.

The UE is allowed to initiate the de-registration procedure even if the timer T3346 is running.

NOTE: When the UE has no PDU sessions over non-3GPP access, or the UE moves all the PDU sessions over a non-3GPP access to a 3GPP access, the UE and the AMF need not initiate de-registration over the non-3GPP access.

The AMF shall provide the UE with a non-3GPP de-registration timer.

[TS 24.501, clause 5.5.2.2.1]

The de-registration procedure is initiated by the UE by sending a DEREGISTRATION REQUEST message (see example in figure 5.5.2.2.1). The De-registration type IE included in the message indicates whether the de-registration procedure is due to a "switch off" or not. The access type included in the message indicates whether the de-registration procedure is:

a) for 5GS services over 3GPP access when the UE is registered over 3GPP access only;

b) for 5GS services over non-3GPP access when the UE is registered over non-3GPP access only; or

c) for 5GS services over 3GPP access, non-3GPP access or both 3GPP access and non-3GPP access when the UE is registered in the same PLMN over both accesses.

If the UE has a valid 5G-GUTI, the UE shall populate the 5GS mobile identity IE with the valid 5G-GUTI. If the UE does not have a valid 5G-GUTI, the UE shall populate the 5GS mobile identity IE with its SUCI.

If the UE does not have a valid 5G-GUTI and it does not have a valid SUCI, then the UE shall populate the5GSmobile identity IE with its PEI.

If the de-registration request is not due to switch off and the UE is in the state 5GMM-REGISTERED or 5GMM-REGISTERED-INITIATED, timer T3521 shall be started in the UE after the DEREGISTRATION REQUEST message has been sent. The UE shall enter the state 5GMM-DEREGISTERED-INITIATED.

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

[TS 24.501, clause 5.5.2.2.6]

…

d) De-registration procedure collision.

De-registration containing de-registration type "switch off":

– If the UE receives a DEREGISTRATION REQUEST message before the UE-initiated de-registration procedure has been completed, this message shall be ignored and the UE-initiated de-registration procedure shall continue.

Otherwise:

– If the UE receives a DEREGISTRATION REQUEST message before the UE-initiated de-registration procedure has been completed, it shall treat the message as specified in subclause 5.5.2.3.2 with the following modification:

– If the DEREGISTRATION REQUEST message received by the UE contains de-registration type "re-registration required", and the UE-initiated de-registration procedure is with de-registration type "normal de-registration", the UE need not initiate the registration procedure for initial registration.

e) De-registration and 5GMM common procedure collision.

De-registration containing de-registration type "switch off":

– If the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed, this message shall be ignored and the de-registration procedure shall continue.

Otherwise:

– If the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed, both the 5GMM common procedure and the de-registration procedure shall continue.

9.1.6.1.1.3 Test description

9.1.6.1.1.3.1 Pre-test conditions

System Simulator:

– NGC Cell A.

UE:

– None.

Preamble:

– The UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].

9.1.6.1.1.3.2 Test procedure sequence

Table 9.1.6.1.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

SS stops sending RLC acknowledgments.

–

–

–

–

1

Cause switch off

–

–

–

–

2

Check: Does the UE transmit a DEREGISTRATION REQUEST with the De-registration type IE indicating "switch off"?

–>

DEREGISTRATION REQUEST

1

P

3

The SS transmits a DEREGISTRATION REQUEST message.

<–

DEREGISTRATION REQUEST

–

–

3A

SS resumes sending RLC acknowledgments

–

–

–

–

4

Check: Does the UE transmit a DEREGISTRATION ACCEPT message within 6 seconds (T3522)?

–>

DEREGISTRATION ACCEPT

2

F

5

The SS releases the RRC connection.

–

–

–

–

6

Switch on the UE

–

–

–

–

7

The UE performs Registration procedure as specified in TS 38.508-1 [4] subclause 4.5.2 with ‘connected without release’.

–

–

–

–

7A

SS stops sending RLC acknowledgments.

–

–

–

–

8

Cause switch off.

–

–

–

–

9

The UE transmits a DEREGISTRATION REQUEST with the De-registration type IE indicating "switch off".

–>

DEREGISTRATION REQUEST

–

–

10

The SS transmits an IDENTITY REQUEST message.

<–

IDENTITY REQUEST

–

–

10A

SS resumes sending RLC acknowledgments

11

Check: Does the UE transmit an IDENTITY RESPONSE message within 6 seconds (T3570)?

–>

IDENTITY RESPONSE

3

F

12

The SS releases the RRC connection.

–

–

–

–

–

EXCEPTION: Steps 13a1 to 13a4 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if the UE supports remove USIM without power down: pc_USIM_Removal = TRUE [29]

–

–

–

–

13a1

Switch on the UE

–

–

–

–

13a2

The UE performs Registration procedure as specified in TS 38.508-1 [4] subclause 4.5.2 with ‘connected without release’.

–

–

–

–

13a3

Cause removal of USIM from the UE without powering down.

–

–

–

–

13a4

Check: Does the UE transmit a DEREGISTRATION REQUEST with the De-registration type IE indicating "switch off"?

–>

DEREGISTRATION REQUEST

4

P

9.1.6.1.1.3.3 Specific message contents

Table 9.1.6.1.1.3.3-1: DEREGISTRATION REQUEST (Steps 2, 9 and 13a4, Table 9.1.6.1.1.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-12

Information Element

Value/Remark

Comment

Condition

De-registration type

Switch off

‘1’B
9.1.6.1.2 UE-initiated de-registration / Normal de-registration / Abnormal / Transmission failure without TAI change from lower layers, de-registration and 5GMM common procedure collision, T3521 timeout

9.1.6.1.2.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED state }

ensure that {

when { the UE initiates "normal de-registration" type deregistration from 5GS services over 3GPP access }

then { the UE sends DEREGISTRATION REQUEST message with De-registration type IE indicated to "Normal de-registration" and starts timer T3521 }

}

(2)

with { the UE in 5GMM-DEREGISTERED-INTIATED state }

ensure that {

when { Transmission failure of DEREGISTRATION REQUEST message indication without TAI change from lower layers }

then { the UE restarts the de-registration procedure }

}

(3)

with { the UE in 5GMM-DEREGISTERED-INTIATED state }

ensure that {

when { the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed }

then { both the 5GMM common procedure and the de-registration procedure shall continue }

}

(4)

with { the UE in 5GMM-DEREGISTERED-INTIATED state }

ensure that {

when { the first four expiries of the timer T3521 }

then { the UE shall retransmit the DEREGISTRATION REQUEST message and shall reset and restart timer T3521 }

}

(5)

with { the UE in 5GMM-DEREGISTERED-INTIATED state }

ensure that {

when { On the fifth expiry of timer T3521 }

then { the detach procedure shall be aborted and the UE performs local detach }

}

9.1.6.1.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501 clause 5.5.2.2.6 and TS 38.331 clause 5.7.2.4. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.2.2.6]

c) T3521 timeout.

On the first four expiries of the timer, the UE shall retransmit the DEREGISTRATION REQUEST message and shall reset and restart timer T3521. On the fifth expiry of timer T3521, the de-registration procedure shall be aborted and the UE proceeds as follows:

1) if the de-registration procedure was performed due to disabling of 5GS services, the UE shall enter the 5GMM-NULL state; or

2) if the de-registration type "normal de-registration" was requested for reasons other than disabling of 5GS services, the UE shall enter the 5GMM-DEREGISTERED state.

…

e) De-registration and 5GMM common procedure collision.

De-registration containing de-registration type "switch off":

– If the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed, this message shall be ignored and the de-registration procedure shall continue.

Otherwise:

– If the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed, both the 5GMM common procedure and the de-registration procedure shall continue.

h) Transmission failure of DEREGISTRATION REQUEST message indication without TAI change from lower layers.

The UE shall restart the de-registration procedure.

[TS 38.331, clause 5.7.2.4]

The UE shall:

1> if AS security is not started and radio link failure occurs before the successful delivery of ULInformationTransfer messages has been confirmed by lower layers; or

1> if mobility (i.e. handover, RRC connection re-establishment) occurs before the successful delivery of ULInformationTransfer messages has been confirmed by lower layers:

2> inform upper layers about the possible failure to deliver the information contained in the concerned ULInformationTransfer messages.

9.1.6.1.2.3 Test description

9.1.6.1.2.3.1 Pre-test conditions

System Simulator:

– NGC Cell A and NGC Cell B

– Both cells are configured as per table 6.3.2.2-1 TS 38.508-1 [4] with the below exceptions

Table 9.1.6.1.2.3.1–1: Cell configuration

NGC Cell

TAC

TAI

B

1

TAI-1

UE:

– None.

Preamble:

– the UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].

9.1.6.1.2.3.2 Test procedure sequence

Table 9.1.6.1.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

The SS configures:

– NGC Cell B as "Suitable neighbour cell".

0A

SS transmits NR RRCReconfigurationmessage to configure specific maxRetxThreshold for NGC Cell A.

<–

NR RRC: RRCReconfiguration

–

–

0B

The UE transmits NR RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

–

1

The SS is configured not send RLC ACK for the message sent in step 2.

–

–

–

–

1A

AT or MMI command to cause UE to initiate de-registration.

–

–

–

–

–

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

–

–

–

–

2

Does the UE transmit a DEREGISTRATION REQUEST message with De-registration type IE indicating "Normal de-registration"? The UE starts timer T3521.

–>

5GMM: DEREGISTRATION REQUEST

1

P

3

Void

–

–

–

–

3A

The SS transmits an RRCReconfiguration message including reconfigurationWithSync with rach-ConfigDedicated to order the UE to perform intra-frequency handover to NGC Cell B.

<–

NR RRC: RRCReconfiguration

–

–

–

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

–

–

–

–

3B

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

–

4

Check: Does the UE restart the de-registration procedure by sending DEREGISTRATION REQUEST message? Timer T3521 is started.

–>

5GMM: DEREGISTRATION REQUEST

2

P

4A

The SS configures:

– NGC Cell A as "Non-suitable "Off" cell".

–

–

–

–

5

With T3521 still running the SS shall send AUTHENTICATION REQUEST.

<–

5GMM: AUTHENTICATION REQUEST

–

–

6

Check: Does the UE transmit an AUTHENTICATION RESPONSE message?

–>

5GMM: AUTHENTICATION RESPONSE

3

P

7

SS responds with DEREGISTRATION ACCEPT message.

<–

5GMM: DEREGISTRATION ACCEPT

–

–

8

The SS releases the RRC connection.

–

–

–

–

9

AT or MMI command to cause UE to initiate registration.

–

–

–

–

10-24a4

Steps 2-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed to complete the registration.

–

–

–

–

25

Cause UE to initiate de-registration.

–

–

–

–

26

Check: Does the UE transmit a DEREGISTRATION REQUEST message with De-registration type IE indicating "Normal de-registration"? The UE starts timer T3521.

–>

5GMM: DEREGISTRATION REQUEST

1

P

27

SS does not respond to the DEREGISTRATION REQUEST message.

–

–

–

–

28

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

–>

5GMM: DEREGISTRATION REQUEST

4

P

29

The SS does not respond to the DEREGISTRATION REQUEST message.

–

–

–

–

30

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

–>

5GMM: DEREGISTRATION REQUEST

4

P

31

The SS does not respond to the DEREGISTRATION REQUEST message.

–

–

–

–

32

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

–>

5GMM: DEREGISTRATION REQUEST

4

P

33

The SS does not respond to the DEREGISTRATION REQUEST message.

–

–

–

–

34

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

–>

5GMM: DEREGISTRATION REQUEST

4

P

35

The SS does not respond to the DEREGISTRATION REQUEST message.

–

–

–

–

36

Check: When the timer T3521 expires does the UE re-transmit DEREGISTRATION REQUEST message in 10s?

The UE shall abort the de-registration procedure and enter the 5GMM-DEREGISTERED (5th expiry).

–>

5GMM: DEREGISTRATION REQUEST

5

F

Note: T3521 value is specified as 15s in TS 24.501 [22].

9.1.6.1.2.3.3 Specific message contents

Table 9.1.6.1.2.3.3-0A: RRCReconfiguration (step 0A Table 9.1.6.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13

Information Element

Value/remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfiguration SEQUENCE {

nonCriticalExtension SEQUENCE {

masterCellGroup

CellGroupConfig with condition SRB2_DRB1 configured in the preamble

OCTET STRING (CONTAINING CellGroupConfig)

}

}

}

}

Table 9.1.6.1.2.3.3-0B: CellGroupConfig (Table 9.1.6.1.2.3.3-0A)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-19

Information Element

Value/remark

Comment

Condition

CellGroupConfig ::= SEQUENCE {

rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig {

1 entry

SRB2_DRB1

RLC-Bearer-Config[1]

RLC-BearerConfig with condition SRB2

}

}

Table 9.1.6.1.2.3.3-0C: RLC-BearerConfig (Table 9.1.6.1.2.3.3-0B)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-148

Information Element

Value/remark

Comment

Condition

RLC-BearerConfig ::= SEQUENCE {

rlc-Config

RLC-Config using condition AM

AM

}

Table 9.1.6.1.2.3.3-0D: RLC-Config (Table 9.1.6.1.2.3.3-0C)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-149

Information Element

Value/remark

Comment

Condition

RLC-Config ::= CHOICE {

am SEQUENCE {

AM

ul-AM-RLC SEQUENCE {

maxRetxThreshold

t32

}

}

}

Table 9.1.6.1.2.3.3-1: DEREGISTRATION REQUEST (steps 2, 4, 26, 28, 30, 32 and 34, Table 9.1.6.1.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-12

Information Element

Value/remark

Comment

Condition

De-registration type

Switch off

‘0’B

Normal de-registration

Access type

‘01’B

3GPP access

Table 9.1.6.1.2.3.3-2: RRCReconfiguration-HO (step 3A Table 9.1.6.1.2.3.2-1)

Derivation path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange
9.1.6.1.3 UE-initiated de-registration / Abnormal / Change of cell into a new tracking area

9.1.6.1.3.1 Test Purpose (TP)

(1)

with { UE in 5GMM-DEREGISTERED-INITIATED state and de-registration request is not due to switch off }

ensure that {

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

then { UE aborts the de-registration procedure and initiates a mobility registration procedure }

}

(2)

with { UE in 5GMM-REGISTERED-INITIATED state for a mobility registration procedure due to change of cell into a new tracking area list during UE-initiated de-registration procedure }

ensure that {

when { UE receives REGISTRATION ACCEPT message }

then { UE re-initiates the de-registration procedure after completing the mobility registration procedure }

}

(3)

Void

9.1.6.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 5.5.2.2.6. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501 clause 5.5.2.2.6]

The following abnormal cases can be identified:

…

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 de-registration procedure is completed, the de-registration procedure shall be aborted and re-initiated after successfully performing a registration procedure for mobility or periodic update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message). If the de-registration procedure was initiated due to removal of the USIM or the UE is to be switched off, the UE shall abort the de-registration procedure and enter the state 5GMM-DEREGISTERED.

9.1.6.1.3.3 Test description

9.1.6.1.3.3.1 Pre-test conditions

System Simulator:

– NGC Cell A belongs to Home PLMN and TAI-1 and set as serving cell;

– NGC Cell B belongs to Home PLMN and TAI-2 and set as Non-suitable “Off” cell.

UE:

– None;

Preamble:

– The UE is in state 3N-A on NGC cell A according to TS 38.508-1 [4].

9.1.6.1.3.3.2 Test procedure sequence

Table 9.1.6.1.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

–

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

–

–

–

–

1

Cause UE to de-register for non Switch off reason using MMI or AT commands.

–

–

–

–

2

The UE transmits DEREGISTRATION REQUEST message. (The UE starts timer T3521)

–>

DEREGISTRATION REQUEST

3

The SS does not respond to DEREGISTRATION REQUEST message.

–

–

–

–

4

The SS configures NGC Cell A as the " Suitable neighbour intra-frequency cell " and NGC Cell B as the "Serving cell".

Note: T3521 value is specified as 15s in TS 24.501 [22] and it is assumed that SS can

configure cells within this time.

–

–

–

–

5

The SS transmits an

RRCReconfiguration message on

NGC Cell A to order the UE to perform intra-frequency handover to NGC Cell B.

–

–

–

–

6

The UE transmits a

RRCReconfigurationComplete

message on NGC Cell B to confirm the successful completion of the intra frequency handover.

–

–

–

–

–

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

–

–

–

–

7

Check: Does the UE transmit a REGISTRATION REQUEST message with registration type value set to “mobility registration updating”

–>

REGISTRATION REQUEST

1

P

8 -9

Steps 4 to 5 of the generic procedure in TS 38.508-1 [4] subclause 4.9.5.2.2

–

–

–

–

10-22

Void

23

Check: Does the UE transmit DEREGISTRATION REQUEST message?

–>

DEREGISTRATION REQUEST

2

P

24

The SS transmits DEREGISTRATION ACCEPT message.

<–

DEREGISTRATION ACCEPT

–

–

25

The SS transmits an RRCRelease message.

–

–

–

–

26

Check: Does the test result of the generic procedure in TS 38.508-1 [4] subclause 4.9.13 indicates that the UE doesn’t responds to paging when paged with NG-5G-S-TMSI?

–

–

2

P

27-35

Void

–

–

–

–

9.1.6.1.3.3.3 Specific message contents

Table 9.1.6.1.3.3.3-1: DEREGISTRATION REQUEST (steps 2 and 23, Table 9.1.6.1.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-12

Information Element

Value/remark

Comment

Condition

De-registration type

Switch off

‘0’B

Normal de-registration

Re-registration required

‘0’B

Spare bit

Access type

‘01’B

3GPP access

5GS mobile identity

5G-GUTI

Same value as assigned in REGISTRATION ACCEPT

Table 9.1.6.1.3.3.3-2: RRCReconfiguration-HO (step 5, Table 9.1.6.1.3.3.2-1)

Derivation Path: TS 38.508-1 [4],Table 4.8.1-1A with condition RBConfig_KeyChange

Table 9.1.6.1.3.3.3-3: Void

Table 9.1.6.1.3.3.3-4: Void

Table 9.1.6.1.3.3.3-5: Void

Table 9.1.6.1.3.3.3-6: Void)

Table 9.1.6.1.3.3.3-7: REGISTRATION REQUEST (step 7, Table 9.1.6.1.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6

Information Element

Value/remark

Comment

Condition

5GS registration type value

‘010’B

Mobility

Table 9.1.6.1.3.3.3-8: Void

9.1.6.1.4 Void

9.1.6.2 Network-initiated de-registration

9.1.6.2.1 Network-initiated de-registration / De-registration for 3GPP access / Re-registration required

9.1.6.2.1.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED state }

ensure that {

when { the SS sends a DEREGISTRATION REQUEST message indicates "re-registration required" and the de-registration request is for 3GPP access }

then { the UE sends a DEREGISTRATION ACCEPT message to the network and releases the existing NAS signalling connection, then initiates an initial registration and also re-establishes any previously established PDU sessions. }

}

9.1.6.2.1.2 Conformance requirements

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

[TS 24.501 clause5.5.2.3.2]

NOTE 1: When the de-registration type indicates "re-registration required", user interaction is necessary in some cases when the UE cannot re-establish the PDU session (s), if any, automatically.

…

Upon sending a DEREGISTRATION ACCEPT message, the UE shall delete the rejected NSSAI as specified in subclause 4.6.2.2.

If the de-registration type indicates "re-registration required", then the UE shall ignore the 5GMM cause IE if received.

If the de-registration type indicates "re-registration not required", the UE shall take the actions depending on the received 5GMM cause value:

#3 (Illegal UE);

…

As an implementation option, the UE may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [5].

9.1.6.2.1.3 Test description

9.1.6.2.1.3.1 Pre-test conditions

System Simulator:

– NGC Cell A.

UE:

– None.

Preamble:

– the UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].

9.1.6.2.1.3.2 Test procedure sequence

Table 9.1.6.2.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

1

The SS transmits a DEREGISTRATION REQUEST with indicates "re-registration required".

<–

DEREGISTRATION REQUEST

–

–

2

Check: Does the UE transmits a DEREGISTRATION ACCEPT message?

–>

DEREGISTRATION ACCEPT

1

P

3

The SS releases RRC connection.

–

–

–

–

4

The UE transmits an RRCSetupRequest message.

–>

NR RRC: RRCSetupRequest

–

–

5

The SS transmits an RRCSetup message.

<–

NR RRC: RRCSetup

–

–

6

Check: Does the UE transmits an RRCSetupComplete message and REGISTRATION REQUEST message with registration type set to "initial registration".

–>

NR RRC: RRCSetupComplete

5GMM: REGISTRATION REQUEST

1

P

7-23

Steps 5-20 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.

–

–

–

–

9.1.6.2.1.3.3 Specific message contents

Table 9.1.6.2.1.3.3-1: DEREGISTRATION REQUEST (step 1, Table 9.1.6.2.1.3.2-1)

Derivation path: TS 38.508-1 [4] Table 4.7.1-14

Information Element

Value/Remark

Comment

Condition

DEREGISTRATION type

Switch off

‘0’B

Normal de-registration

Re-registration required

‘1’B

re-registration required

Access type

‘01’B

3GPP access
9.1.6.2.2 Network-initiated de-registration / De-registration for 3GPP access / Re-registration not required

9.1.6.2.2.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED state }

ensure that {

when { the SS sends a DEREGISTRATION REQUEST message indicates no 5GMM cause IE, ""re-registration not required"" and the de-registration request is for 3GPP access) }

then { the UE deletes 5G-GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, ngKSI, sends a DEREGISTRATION ACCEPT message enter the state 5GMM-DEREGISTERED for 3GPP access }

}

9.1.6.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501 clauses 5.5.2.3.2 and 5.5.2.3.4. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.2.3.2]

Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration not required" and the de-registration request is for 3GPP access, the UE shall perform a local release of the PDU sessions over 3GPP access, if any. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for 3GPP access.

[TS 24.501, clause 5.5.2.3.4]

b) DEREGISTRATION REQUEST, other 5GMM cause values than those treated in subclause 5.5.2.3.2, cases of 5GMM cause value#11, #22 and #72 that are considered as abnormal cases according to subclause 5.5.2.3.2 or no 5GMM cause IE is included, and the De-registration type IE indicates "re-registration not required".

The UE shall delete 5G-GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, ngKSI, shall set the 5GS update status to 5U2 NOT UPDATED and shall start timer T3502.

A UE not supporting S1 mode may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [5]; otherwise the UE shall enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION.

9.1.6.2.2.3 Test description

9.1.6.2.2.3.1 Pre-test conditions

System Simulator:

– NGC Cell A.

UE:

– the UE is previously registered on 5GC, and when on 5GC, the UE is last authenticated and registered on NGC cell A using default message contents according to TS 38.508-1 [4];

Preamble:

– The UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].

– The T3502 in UE set to 2 minutes.

9.1.6.2.2.3.2 Test procedure sequence

Table 9.1.6.2.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS sends a DEREGISTRATION REQUEST message indicates no 5GMM cause IE, "re-registration not required" and the de-registration request is for 3GPP access

<–

5GMM: DEREGISTRATION REQUEST

–

–

2

Check: Does the UE transmit a DEREGISTRATION ACCEPT message?

Note: Now UE should start timer T3502.

–>

5GMM: DEREGISTRATION ACCEPT

1

P

3

The SS releases the RRC connection.

–

–

–

–

4

The SS waits 2 mins for T3502 to expire.

–

–

–

–

5-22a1

Does the UE performs Steps 2-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4]?

–

–

1

P

9.1.6.2.2.3.3 Specific message contents

Table 9.1.6.2.2.3.3-1: Message REGISTRATION ACCEPT (preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/remark

Comment

Condition

T3502 Value

2mins

Timer value

‘0 0010’B

The timer value is 2mins.

Unit

‘001’B

Table 9.1.6.2.2.3.3-2: Message DEREGISTRATION REQUEST (step 1, Table 9.1.6.2.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-12

Information Element

Value/remark

Comment

Condition

De-registration type

Switch off

‘0’B

Normal de-registration

Re-registration required

‘0’B

re-registration not required

Access type

‘01’B

3GPP access

5GMM cause

Not Present

Table 9.1.6.2.2.3.3-3: Message REGISTRATION REQUEST (step7, Table 9.1.6.2.2.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-6

Information Element

Value/Remark

Comment

Condition

ngKSI

NAS key set identifier

‘111’B

no key is available (UE to network)

TSC

Any allowed value

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

5GS mobile identity

The valid SUCI

Last visited registered TAI

Not present