9.1.4 Generic UE configuration update
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
9.1.4.1 Generic UE configuration update / New 5G-GUTI, NITZ, registration requested, network slicing indication, new allowed NSSAI / Acknowledgement from the UE
9.1.4.1.1 Test Purpose (TP)
(1)
with { UE in 5GMM-REGISTERED state }
ensure that {
when { UE receives a new 5G-GUTI in the CONFIGURATION UPDATE COMMAND message and acknowledgement from the UE is requested }
then { UE sends a CONFIGURATION UPDATE COMPLETE message and UE shall consider new 5G-GUTI as valid }
}
(2)
with { UE in 5GMM-REGISTERED state }
ensure that {
when { UE receives a NITZ information in the CONFIGURATION UPDATE COMMAND message and acknowledgement from the UE is not requested }
then { UE updates NITZ information }
}
(3)
with { UE in 5GMM-REGISTERED state }
ensure that {
when { UE receives CONFIGURATION UPDATE COMMAND message indicating “registration requested” and contains no other parameters }
then { UE deletes any stored allowed NSSAI for this PLMN and then release the existing N1 NAS signalling connection, starts a mobility registration procedure }
}
(4)
with { UE in 5GMM-REGISTERED state }
ensure that {
when { UE receives a new allowed NSSAI in the CONFIGURATION UPDATE COMMAND message and registration is not requested }
then { UE replaces any stored allowed NSSAI for this PLMN with new allowed NSSAI }
}
(5)
with { UE in 5GMM-REGISTERED state }
ensure that {
when { UE receives a Network Slicing subscription change indication set to "Network slicing subscription changed" in the CONFIGURATION UPDATE COMMAND message and registration is not requested }
then { UE deletes the network slicing information for each and every PLMN except for the current PLMN and default configured NSSAI }
}
9.1.4.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 4.6.2.2, 5.4.4.1, 5.4.4.2, 5.4.4.3, 5.5.1.2.2 and 5.5.1.3.2. Unless otherwise stated these are Rel-15 requirements.
[TS 24.501 clause 4.6.2.2]
If available, the configured NSSAI(s) shall be stored in a non-volatile memory in the ME as specified in annex C.
…
If the UE receives the CONFIGURATION UPDATE COMMAND message indicating "registration requested" and contains no other parameters (see subclauses 5.4.4.2 and 5.4.4.3), the UE shall delete any stored allowed NSSAI for this PLMN, and delete any stored mapping of each S-NSSAI of the allowed NSSAI to the S-NSSAI(s) of the HPLMN, if available;
…
d) When the UE receives the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed" in the REGISTRATION ACCEPT message or in the CONFIGURATION UPDATE COMMAND message, the UE shall delete the network slicing information for each of the PLMNs that the UE has slicing information stored for (excluding the current PLMN). The UE shall not delete the default configured NSSAI. Additionally, the UE shall update the network slicing information for the current PLMN (if received) as specified above in bullets a), b) and c):
[TS 24.501 clause 5.4.4.1]
The purpose of this procedure is to:
a) allow the AMF to update the UE configuration for access and mobility management-related parameters decided and provided by the AMF by providing new parameter information within the command; or
b) request the UE to perform a registration procedure for mobility and periodic registration update towards the network to update access and mobility management-related parameters decided and provided by the AMF (see subclause 5.5.1.3).
This procedure is initiated by the network and can only be used when the UE has an established 5GMM context, and the UE is in 5GMM-CONNECTED mode. When the UE is in 5GMM-IDLE mode, the AMF may use the paging or notification procedure to initiate the generic UE configuration update procedure. The AMF can request a confirmation response in order to ensure that the parameter has been updated by the UE.
This procedure shall be initiated by the network to assign a new 5G-GUTI to the UE after a successful service request procedure invoked as a response to a paging request from the network and before the release of the N1 NAS signalling connection. If the service request procedure was triggered due to 5GSM downlink signalling pending, the procedure for assigning a new 5G-GUTI can be initiated by the network after the transport of the 5GSM downlink signalling.
The following parameters are supported by the generic UE configuration update procedure without the need to request the UE to perform the registration procedure for mobility and periodic registration update:
a) 5G-GUTI;
b) TAI list;
c) Service area list;
d) Network identity and time zone information (Full name for network, short name for network, local time zone, universal time and local time zone, network daylight saving time);
e) LADN information;
f) Rejected NSSAI;
g) Network slicing indication;
h) Operator-defined access category definitions; and
i) SMS indication.
The following parameters can be sent to the UE with or without a request to perform the registration procedure for mobility and periodic registration update:
a) Allowed NSSAI; or
b) Configured NSSAI.
The following parameter is sent to the UE with a request to perform the registration procedure for mobility and periodic registration update:
a) MICO indication.
The following parameters are sent over 3GPP access only:
a) LADN information;
b) MICO indication;
c) TAI list; and
d) Service area list.
The following parameters are managed and sent per access type i.e., independently over 3GPP access or non 3GPP access:
a) Allowed NSSAI; and
b) Rejected NSSAI (when the NSSAI is rejected for the current registration area).
The following parameters are managed commonly and sent over 3GPP access or non 3GPP access:
a) 5G-GUTI;
b) Network identity and time zone information;
c) Rejected NSSAI (when the NSSAI is rejected for the current PLMN);
d) Configured NSSAI; and
e) SMS indication.
Figure 5.4.4.1.1: Generic UE configuration update procedure
[TS 24.501 clause 5.4.4.2]
The AMF shall initiate the generic UE configuration update procedure by sending the CONFIGURATION UPDATE COMMAND message to the UE.
The AMF shall in the CONFIGURATION UPDATE COMMAND message either:
a) include one or more of the following parameters: 5G-GUTI, TAI list, allowed NSSAI that may include the mapped S-NSSAI(s), LADN information, service area list, MICO indication NITZ information, configured NSSAI that may include the mapped S-NSSAI(s), rejected NSSAI, network slicing indication, operator-defined access category definitions or SMS indication;
b) include the Configuration update indication IE with the Registration requested bit set to "registration requested"; or
c) include a combination of both a) and b).
If an acknowledgement from the UE is requested, the AMF shall indicate "acknowledgement requested" in the Acknowledgement bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message and shall start timer T3555. Acknowledgement shall be requested for all parameters except when only NITZ is included.
To initiate parameter re-negotiation between the UE and network, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message.
If a new allowed NSSAI information or AMF re-configuration of supported S-NSSAIs requires an AMF relocation, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE and include the Allowed NSSAI IE in the CONFIGURATION UPDATE COMMAND message.
If the AMF includes a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and the new configured NSSAI requires an AMF relocation as specified in 3GPP TS 23.501 [8], the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE in the message.
If the AMF indicates "registration requested" in the Registration requested bit of the Configuration update indication IE, acknowledgement shall be requested.
If changes to the allowed NSSAI require the UE to initiate a registration procedure, but the AMF is unable to determine an allowed NSSAI for the UE as specified in 3GPP TS 23.501 [8], the CONFIGURATION UPDATE COMMAND message shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE, and shall not contain any other parameters.
If the AMF needs to update the LADN information, the AMF shall include the LADN information in the LADN information IE of the CONFIGURATION UPDATE COMMAND message.
During an established 5GMM context, the network may send none, one, or more CONFIGURATION UPDATE COMMAND messages to the UE. If more than one CONFIGURATION UPDATE COMMAND message is sent, the messages need not have the same content.
[TS 24.501 clause 5.4.4.3]
Upon receiving the CONFIGURATION UPDATE COMMAND message, the UE shall stop timer T3346 if running and use the contents to update appropriate information stored within the UE.
If "acknowledgement requested" is indicated in the Acknowledgement bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message, the UE shall send a CONFIGURATION UPDATE COMPLETE message.
If the UE receives a new 5G-GUTI in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new 5G-GUTI as valid, the old 5G-GUTI as invalid, stop timer T3519 if running, and delete any stored SUCI; otherwise, the UE shall consider the old 5G-GUTI as valid. The UE shall provide the 5G-GUTI to the lower layer of 3GPP access if the CONFIGURATION UPDATE COMMAND message is sent over the non-3GPP access, and the UE is in 5GMM-REGISTERED in both 3GPP access and non-3GPP access in the same PLMN.
If the UE receives a new TAI list in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new TAI list as valid and the old TAI list as invalid; otherwise, the UE shall consider the old TAI list as valid.
If the UE receives a new service area list in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new service area list as valid and the old service area list as invalid; otherwise, the UE shall consider the old service area list, if any, as valid.
If the UE receives new NITZ information in the CONFIGURATION UPDATE COMMAND message, the UE considers the new NITZ information as valid and the old NITZ information as invalid; otherwise, the UE shall consider the old NITZ information as valid.
If the UE receives a LADN information IE in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the old LADN information as invalid and the new LADN information as valid, if any; otherwise, the UE shall consider the old LADN information as valid.
If the UE receives a new allowed NSSAI for the associated access type in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new allowed NSSAI as valid for the associated access type, store the allowed NSSAI for the associated access type as specified in subclause 4.6.2.2 and consider the old allowed NSSAI for the associated access type as invalid; otherwise, the UE shall consider the old Allowed NSSAI as valid for the associated access type.
If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new configured NSSAI for the registered PLMN as valid and the old configured NSSAI for the registered PLMN as invalid; otherwise, the UE shall consider the old configured NSSAI for the registered PLMN as valid The UE shall store the new configured NSSAI as specified in subclause 4.6.2.2.
If the UE receives the Network slicing indication IE in the CONFIGURATION UPDATE COMMAND message with the Network slicing subscription change indication set to "Network slicing subscription changed", the UE shall delete the network slicing information for each and every PLMN except for the current PLMN as specified in subclause 4.6.2.2.
If the UE receives Operator-defined access category definitions IE in the CONFIGURATION UPDATE COMMAND message and the Operator-defined access category definitions IE contains one or more operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN and shall store the received operator-defined access category definitions for the RPLMN. If the UE receives the Operator-defined access category definitions IE in the CONFIGURATION UPDATE COMMAND message and the Operator-defined access category definitions IE contains no operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN. If the CONFIGURATION UPDATE COMMAND message does not contain the Operator-defined access category definitions IE, the UE shall not delete the operator-defined access category definitions stored for the RPLMN.
If the UE receives the SMS indication IE in the CONFIGURATION UPDATE COMMAND message with the SMS availability indication set to:
a) "SMS over NAS not available", the UE shall consider that SMS over NAS transport is not allowed by the network; and
b) "SMS over NAS available", the UE may request the use of SMS over NAS transport by performing a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3, after the completion of the generic UE configuration update procedure.
If the CONFIGURATION UPDATE COMMAND message indicates "registration requested" in the Registration requested bit of the Configuration update indication IE and:
a) contains no other parameters or contains at least one of the following parameters: a new allowed NSSAI, a new configured NSSAI or the Network slicing subscription change indication, and:
1) an emergency PDU session exists, the UE shall, after the completion of the generic UE configuration update procedure and the release of the emergency PDU session, release the existing N1 NAS signalling connection, and start a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3; or
2) no emergency PDU Session exists, the UE shall, after the completion of the generic UE configuration update procedure and the release of the existing N1 NAS signalling connection, start a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3; or
b) an MICO indication is included without a new allowed NSSAI or a new configured NSSAI, the UE shall, after the completion of the generic UE configuration update procedure, start a registration procedure for mobility and registration update as specified in subclause 5.5.1.3 to re-negotiate MICO mode with the network.
The UE receiving the rejected NSSAI in the CONFIGURATION UPDATE COMMAND message takes the following actions based on the rejection cause in the rejected NSSAI:
"S-NSSAI not available in the current PLMN"
The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN as specified in subclause 4.6.2.2 and not attempt to use this S-NSSAI in the current PLMN until switching off the UE or the UICC containing the USIM is removed.
"S-NSSAI not available in the current registration area"
The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as specified in subclause 4.6.2.2 and not attempt to use this S-NSSAI in the current registration area until switching off the UE, the UE moving out of the current registration area or the UICC containing the USIM is removed.
[TS 24.501 clause 5.5.1.2.2]
The subset of allowed NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the allowed NSSAI for the current PLMN.
NOTE 3: How the UE selects the subset of configured NSSAI or allowed NSSAI to be provided in the requested NSSAI is implementation specific. The UE can take preferences indicated by the upper layers (e.g. policies, applications) into account.
NOTE 4: The number of S-NSSAI(s) included in the requested NSSAI cannot exceed eight.
If the UE initiates an initial registration for emergency services or needs to prolong the established NAS signalling connection after the completion of the initial registration procedure (e.g. due to uplink signalling pending), the UE shall set the Follow-on request indicator to 1.
[TS 24.501 clause 5.5.1.3.2]
For a REGISTRATION REQUEST message with a 5GS registration type IE indicating "mobility registration updating", UE shall include the requested NSSAI containing the S-NSSAI(s) corresponding to the slices to which the UE intends to register with and shall include the mapped S-NSSAI(s) for the requested NSSAI, if available, in the REGISTRATION REQUEST message. If the UE has allowed NSSAI or configured NSSAI for the current PLMN, the requested NSSAI shall be either:
a) the configured NSSAI for the current PLMN, or a subset thereof as described below, if the UE has no allowed NSSAI for the current PLMN;
b) the allowed NSSAI for the current PLMN, or a subset thereof as described below, if the UE has an allowed NSSAI for the current PLMN; or
c) the allowed NSSAI for the current PLMN, or a subset thereof as described below, plus one or more S-NSSAIs from the configured NSSAI for which no corresponding S-NSSAI is present in the allowed NSSAI and those are neither in the rejected NSSAI for the current PLMN nor in the rejected NSSAI for the current registration area.
If the UE has neither allowed NSSAI for the current PLMN nor configured NSSAI for the current PLMN and has a default configured NSSAI, the UE shall:
a) include the S-NSSAI(s) in the Requested NSSAI IE of the REGISTRATION REQUEST message using the default configured NSSAI; and
b) include the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI" in the REGISTRATION REQUEST message.
If the UE has no allowed NSSAI for the current PLMN, no configured NSSAI for the current PLMN, and no default configured NSSAI, the UE shall not include a requested NSSAI in the REGISTRATION REQUEST message.
The subset of configured NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAI applicable to this PLMN, if the S-NSSAI is neither in the rejected NSSAIs for the current PLMN nor in the rejected NSSAI for the current registration area.
The subset of allowed NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the allowed NSSAI for this PLMN.
NOTE 3: How the UE selects the subset of configured NSSAI or allowed NSSAI to be provided in the requested NSSAI is implementation specific. The UE can take preferences indicated by the upper layers (e.g. policies, applications) into account.
NOTE 4: The number of S-NSSAI(s) included in the requested NSSAI cannot exceed eight.
9.1.4.1.3 Test description
9.1.4.1.3.1 Pre-test conditions
System Simulator:
– NGC Cell A configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] belongs to Home PLMN and set as serving cell;
– NGC Cell G configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] and set as Non-Suitable “Off” cell.
– System information combination NR-4 as defined in TS 38.508[4] clause 4.4.3.1.2 is used.
UE:
– UE is configured with NSSAI associated with HPLMN and with 5G-GUTI assigned.
– The UE is equipped with a USIM configuration as defined in TS 38.508-1 [4] Table 6.4.1-22.
Preamble:
– The UE is in state 3N-A on NGC cell A according to TS 38.508-1 [4].
9.1.4.1.3.2 Test procedure sequence
Table 9.1.4.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
||
|
U – S |
Message |
|||||
|
1 |
The SS transmits a CONFIGURATION UPDATE COMMAND message including a new 5G-GUTI. |
<– |
CONFIGURATION UPDATE COMMAND |
– |
– |
|
|
2 |
Check: Does UE transmit a CONFIGURATION UPDATE COMPLETE message? |
–> |
CONFIGURATION UPDATE COMPLETE |
1 |
P |
|
|
3 |
The SS transmits an RRCRelease message. |
– |
– |
– |
– |
|
|
4 |
The SS transmits a Paging message with the new 5G-GUTI. |
– |
– |
– |
– |
|
|
5-11 |
Steps 2 to 8 of the generic procedure for NR_RRC_CONNECTED specified in TS 38.508-1 [4] subclause 4.5.4.2-3 are performed. |
– |
– |
1 |
P |
|
|
12 |
The SS transmits a CONFIGURATION UPDATE COMMAND message including NITZ information. |
<– |
CONFIGURATION UPDATE COMMAND |
– |
– |
|
|
13 |
Check: Does the UE transmit a CONFIGURATION UPDATE COMPLETE message within the expiry of T3555? |
–> |
CONFIGURATION UPDATE COMPLETE |
2 |
F |
|
|
14 |
Check: Using MMI/AT command verify the NITZ update on the UE. |
– |
– |
2 |
P |
|
|
15 |
Switch off procedure in RRC_Connected specified in TS 38.508-1 [4] subclause 4.9.6.3 is performed. |
– |
– |
– |
– |
|
|
16 |
The UE is switched On. |
– |
– |
– |
– |
|
|
17-30 |
Steps 1 to13 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 [4] subclause 4.5.2 are performed. |
– |
– |
– |
– |
|
|
31 |
The SS transmits a REGISTRATION ACCEPT message including Configured NSSAI. |
<– |
REGISTRATION ACCEPT |
– |
– |
|
|
31A – 31E |
Steps 15 to 19a1 of the generic procedure for NR RRC IDLE as specified in TS 38.508-1 [4] subclause 4.5.2.2-2 with ‘connected without release’ are performed. |
– |
– |
– |
– |
|
|
32 |
The SS transmits a CONFIGURATION UPDATE COMMAND message including registration requested IE. |
<– |
CONFIGURATION UPDATE COMMAND |
– |
– |
|
|
32A |
The UE transmits a CONFIGURATION UPDATE COMPLETE message. |
–> |
CONFIGURATION UPDATE COMPLETE |
– |
– |
|
|
32B |
SS releases the RRC connection. |
– |
– |
– |
– |
|
|
33 |
Check: Does UE transmit a REGISTRATION REQUEST message with registration type value set to “Mobility” and including the Requested NSSAI? |
–> |
REGISTRATION REQUEST |
3 |
P |
|
|
34-42 |
Void. |
– |
– |
– |
– |
|
|
43 |
The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI. |
<– |
REGISTRATION ACCEPT |
– |
– |
|
|
44 |
The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message. |
–> |
REGISTRATION COMPLETE |
– |
– |
|
|
44A |
The SS transmits an RRCRelease message. |
– |
– |
– |
– |
|
|
45 |
Check: Using MMI/AT command (+C5GNSSAIRDP) verify the update of allowed NSSAI. |
– |
– |
3 |
P |
|
|
45A – 45H |
Steps 1 to 8 of the generic procedure for NR RRC_CONNECTED specified in TS 38.508-1 [4] subclause 4.5.4.2-3 are performed. |
– |
– |
– |
– |
|
|
46 |
The SS transmits a CONFIGURATION UPDATE COMMAND message including a new allowed NSSAI list. |
<– |
CONFIGURATION UPDATE COMMAND |
– |
– |
|
|
47 |
The UE transmits a CONFIGURATION UPDATE COMPLETE message. |
–> |
CONFIGURATION UPDATE COMPLETE |
– |
– |
|
|
48 |
Check: Using MMI/AT command (+C5GNSSAIRDP) verify the update of allowed NSSAI. |
– |
– |
4 |
P |
|
|
48A |
SS releases the RRC connection. |
– |
– |
– |
– |
|
|
49 |
The SS configures NGC Cell A as the "Non-suitable “Off” cell" and NGC Cell G as the "Serving cell". |
– |
– |
– |
– |
|
|
50-52 |
Steps 2-4 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed. |
– |
– |
– |
– |
|
|
– |
EXCEPTION: Steps 53A1 to 53A9 are performed if 5GS registration type is set as Initial Registration in step 52 |
– |
– |
– |
– |
|
|
53A1-53A9 |
Steps 5 to 13 of the generic test procedure in TS 38.508-1 [4] Table 4.5.2.2-2 are performed on NGC Cell G. |
– |
– |
– |
– |
|
|
53a1 -63 |
Void |
– |
– |
– |
– |
|
|
64 |
The SS transmits a REGISTRATION ACCEPT message including Allowed and Configured NSSAIs. |
<– |
REGISTRATION ACCEPT |
– |
– |
|
|
– |
EXCEPTION: Steps 65a1 to 65b describe behaviour that depends on events happening prior to their execution; the "lower case letter" identifies a step sequence that take place if a specific prior event takes place. |
– |
– |
– |
– |
|
|
65a1-65a5a1 |
IF 5GS registration type is set as Initial Registration in step 52, THEN Steps 15 to 19a1 of the generic test procedure in TS 38.508-1 [4] Table 4.5.2.2-2 are performed on NGC Cell G. |
– |
– |
– |
– |
|
|
65b |
IF 5GS registration type is set as Mobility Registration in step 52, THEN UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message on NGC Cell G. |
–> |
REGISTRATION COMPLETE |
– |
– |
|
|
65 |
Void. |
– |
– |
– |
– |
|
|
66 |
The SS transmits a CONFIGURATION UPDATE COMMAND message with Network slicing subscription changed. |
<– |
CONFIGURATION UPDATE COMMAND |
– |
– |
|
|
67 |
The UE transmits a CONFIGURATION UPDATE COMPLETE message. |
–> |
CONFIGURATION UPDATE COMPLETE |
– |
– |
|
|
67A |
Void |
– |
– |
– |
– |
|
|
67B |
SS releases the RRC connection. |
– |
– |
– |
– |
|
|
68 |
Check: Using MMI/AT command (+C5GNSSAIRDP) verify the update of allowed NSSAI. |
– |
– |
5 |
P |
|
|
68A- 68H |
Steps 1 to 8 of the NR RRC_CONNECTED procedure in TS 38.508-1 [4] Table 4.5.4.2-3 are executed. |
– |
– |
– |
– |
|
|
69 |
The SS transmits NSSAI DELETE REQUEST message to delete the Default Configured NSSAI list. |
<– |
NSSAI DELETE REQUEST |
– |
– |
|
|
70 |
UE transmits NSSAI DELETE RESPONSE message. |
–> |
NSSAI DELETE RESPONSE |
– |
– |
|
|
71 |
The SS transmits an RRCRelease message. |
<– |
– |
– |
– |
|
9.1.4.1.3.3 Specific message contents
Table 9.1.4.1.3.3-1: CONFIGURATION UPDATE COMMAND (step 1, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Configuration update indication |
0001 |
Acknowledgement (ACK) requested |
||
|
5G-GUTI |
Other than the default value |
|||
Table 9.1.4.1.3.3-2: CONFIGURATION UPDATE COMMAND (step 12, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Full name for network |
"C63A9BED0CB7CB31D98C56B3DD70" O |
"FullName12345678", Note 1 |
||
|
Short name for network |
"5367B85D8EC966" O |
"SName123", Note 1 |
||
|
Local time zone |
"40" O |
"GMT+1", Note 1, Note 2 |
||
|
Universal time and local time zone |
"xx211331832540" O |
"<Current Year> 31 December 13:38:52 GMT+1", Note 1, Note 2, Note 3 |
||
|
Network daylight saving time |
"01" O |
"+1 hour adjustment for Daylight Saving Time", Note 1 |
||
|
Note 1: Hard coded values have been chosen to allow for consistent/comparable SS behaviour. Note 2: Daylight Saving Time is included in the Local Time Zone. Note 3: Current Year is derived by the SS. |
||||
Table 9.1.4.1.3.3-3: REGISTRATION ACCEPT (step 31, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
5GS registration result value |
‘001’B |
3GPP access |
||
|
Configured NSSAI |
||||
|
S-NSSAI IEI |
S-NSSAI value 2 |
|||
|
Length of S-NSSAI contents |
‘00000010’B |
SST |
||
|
SST |
‘00000001’B |
2 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
|
S-NSSAI IEI |
S-NSSAI value 3 |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000011’B |
3 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
Table 9.1.4.1.3.3-4: CONFIGURATION UPDATE COMMAND (step 32, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Configuration update indication |
001 |
Registration and Acknowledgement (ACK) requested |
||
Table 9.1.4.1.3.3-5: REGISTRATION REQUEST (step 33, Table 9.1.4.1.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 |
||
|
Requested NSSAI |
||||
|
S-NSSAI IEI |
S-NSSAI value 2 (Note 1) |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000010’B |
2 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
|
S-NSSAI IEI |
S-NSSAI value 3 (Note 1) |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000011’B |
3 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
|
Note 1: the Requested NSSAI IE may include either S-NSSAI value 2, or S-NSSAI value 3, or S-NSSAI value 2 and S-NSSAI value 3. |
||||
Table 9.1.4.1.3.3-6: REGISTRATION ACCEPT (step 43, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
5GS registration result value |
‘001’B |
3GPP access |
||
|
Allowed NSSAI |
||||
|
S-NSSAI IEI |
S-NSSAI value 1 |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000001’B |
1 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
|
S-NSSAI IEI |
S-NSSAI value 2 |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000010’B |
2 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
|
S-NSSAI IEI |
S-NSSAI value 3 |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000011’B |
3 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
Table 9.1.4.1.3.3-7: CONFIGURATION UPDATE COMMAND (step 46, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Configuration update indication |
0001 |
Acknowledgement (ACK) requested |
||
|
Allowed NSSAI |
||||
|
S-NSSAI IEI |
S-NSSAI value 1 |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000001’B |
1 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
|
S-NSSAI IEI |
S-NSSAI value 2 |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000010’B |
2 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
Table 9.1.4.1.3.3-8: REGISTRATION ACCEPT (step 64, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
5GS registration result value |
‘001’B |
3GPP access |
||
|
Configured NSSAI |
||||
|
S-NSSAI IEI |
S-NSSAI value 2 |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000010’B |
2 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
|
S-NSSAI IEI |
S-NSSAI value 3 |
|||
|
Length of S-NSSAI contents |
‘00000001’B |
SST |
||
|
SST |
‘00000011’B |
3 |
||
|
SD |
Not Present |
|||
|
Mapped configured SST |
Not Present |
|||
|
Mapped configured SD |
Not Present |
|||
Table 9.1.4.1.3.3-9: CONFIGURATION UPDATE COMMAND (step 66, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Configuration update indication |
0001 |
Acknowledgement (ACK) requested |
||
|
Network slicing indication |
0001 |
Network slicing subscription changed |
||
Table 9.1.4.1.3.3-10: NSSAI DELETE REQUEST (step 69, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.509 Table 6.7.1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Protocol discriminator |
1111 |
|||
|
Skip indicator |
0000 |
|||
|
Message type |
‘10100110’B |
|||
|
Delete NSSAI type |
‘00000001’B |
Delete Configured NSSAI |
||
|
Configured NSSAI |
00000000 |
|||
Table 9.1.4.1.3.3-11: NSSAI DELETE RESPONSE (step 70, Table 9.1.4.1.3.2-1)
|
Derivation path: TS 38.509 Table 6.7.1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Protocol discriminator |
1111 |
|||
|
Skip indicator |
0000 |
|||
|
Message type |
‘10100111’B |
|||