NAS 5G AMF to UE 3GPP TS 24.501

5G NAS - Configuration Update Command

Configuration Update Command is the network-initiated NAS message used to update UE 5GMM context after registration.

Message Fact Sheet

Protocol	nas	Network	5g
Spec	3GPP TS 24.501	Spec Section	8.2.18
Direction	AMF to UE	Message Type	5GMM signaling

Full message name	5G NAS - Configuration Update Command
Protocol	NAS
Technology	5G
Direction	AMF to UE
Interface	N1
Signaling bearer / channel	NAS signaling / Dedicated NAS message, commonly via DL Information Transfer
Typical trigger	Sent when the network must update registration-related context such as 5G-GUTI, TAI list, allowed NSSAI, NITZ, or registration-request indications.
Main purpose	Lets the AMF push refreshed identity, tracking area, slice, timer, and related mobility-management context to the UE.
Main specification	3GPP TS 24.501, 8.2.18
Release added	Release 15
Procedures where used	Generic UE Configuration Update, Registered-state mobility-management update
Related timers	T3555
Related cause values	Configuration update indication

What is Configuration Update Command in simple terms?

Configuration Update Command is the network-initiated NAS message used to update UE 5GMM context after registration.

Lets the AMF push refreshed identity, tracking area, slice, timer, and related mobility-management context to the UE.

Why this message matters

Configuration Update Command is the network updating the UE's registered 5G context after registration is already active.

Where this message appears in the call flow

Generic UE Configuration Update

Call flow position: Network-initiated update of UE mobility-management context after registration.

Typical state: UE is already registered.

Preconditions:

The UE has an active 5GMM context.

Next likely message: Configuration Update Complete or a later registration trigger

Call flow position

Previous message(s): Registration Accept, Normal registered operation

Next message(s): Configuration Update Complete, Registration procedure if requested

Message direction and transport

Sender and receiver: AMF to UE

Interface: N1

Domain: Core-side mobility management update signaling

Signaling bearer: NAS signaling

Logical channel: Dedicated NAS message, commonly via DL Information Transfer

Transport / encapsulation: NAS 5GS message carried end-to-end between AMF and UE

Security context: Normally sent within an established NAS security context.

Message Structure Overview

Configuration Update Command is a flexible network-initiated update message. Engineers usually focus on which context elements changed and whether acknowledgement was requested.

Structure Syntax

This message is not typically analyzed as ASN.1 on the wire. Engineers usually inspect it as a NAS or protocol field decode rather than an ASN.1 tree.

Configuration Update Command is defined by NAS 24.501 rather than ASN.1.

Decoded Message Dump

Configuration Update Command
  Extended Protocol Discriminator: 5G Mobility Management
  Security Header Type: Integrity protected and ciphered
  Message Type: Configuration Update Command
  5G-GUTI: 02 F1 10 00 01 AB CD EF 56 78
  TAI List:
    PLMN: 001-01
    TAC: 0x2001
  Allowed NSSAI:
    S-NSSAI: SST 1, SD 0x112233
  Configuration Update Indication: Acknowledgement requested

How to read this dump

The key question is which context actually changed and whether the UE must acknowledge or re-register.

Important Information Elements

IE	Required	Description
`5G-GUTI`	Optional	Updated temporary identity that the UE should use after the command.
`TAI list`	Optional	Updated tracking-area scope that affects reachability and later mobility behavior.
`Allowed NSSAI`	Optional	Updated allowed slice context provided by the network.
`Configuration update indication`	Optional	Tells the UE whether acknowledgement or a later registration procedure is requested.
`NITZ information`	Optional	Optional network-provided time-zone and time information.

Detailed field explanation

`5G-GUTI`

Updated temporary identity that the UE should use after the command.

Presence: Optional

`TAI list`

Updated tracking-area scope that affects reachability and later mobility behavior.

Presence: Optional

`Allowed NSSAI`

Updated allowed slice context provided by the network.

Presence: Optional

`Configuration update indication`

Tells the UE whether acknowledgement or a later registration procedure is requested.

Presence: Optional

`NITZ information`

Optional network-provided time-zone and time information.

Presence: Optional

What to check in logs and traces

Check what context fields were updated.
Inspect whether acknowledgement was requested and whether T3555 started.
Correlate the command with the UE's Configuration Update Complete or later registration behavior.

Common Issues and Troubleshooting

The network updates UE context but later paging or mobility behavior looks inconsistent.

Likely cause: The UE may not have applied the updated identity, TAI list, or slice context correctly.

What to inspect: Check the exact IE set in Configuration Update Command and whether Configuration Update Complete followed.

Next step: Correlate the updated fields with later paging, mobility, and slice behavior.

Detailed explanation

5G NAS - Configuration Update Command Explained

Configuration Update Command is the network-initiated NAS message used when the AMF needs to update the UE’s stored 5GMM context after registration is already active. It is one of the most useful registered-state messages because it explains why the UE’s behavior can change without a fresh initial registration.

For beginners, the simple meaning is: the network is updating the UE’s stored 5G configuration.
For engineers, the message is valuable because it can change identity, reachability scope, allowed slices, and later mobility behavior.

What is Configuration Update Command in simple terms?

The UE is already registered. The network decides some of that stored context needs to be updated, so it sends Configuration Update Command.

Why Configuration Update Command matters

This message matters because it can silently change important operating context, including:

temporary identity
tracking-area scope
allowed slice information
whether the UE should acknowledge or start a new registration

If later behavior suddenly changes without a new registration, this is often the message to inspect.

Where Configuration Update Command appears in the call flow

UE                              gNB / AMF
|   UE already registered        |
|<-- Configuration Update Cmd ---|
|--- Configuration Update Cpl -->|
|   or later registration ------>|

Transport characteristics

Direction: AMF to UE
Interface: N1
Transport on access side: commonly via DL Information Transfer
Security expectation: normally protected because the UE is already in registered state

What Configuration Update Command means operationally

Operationally, this message means the network wants the UE to refresh one or more pieces of stored mobility-management context. The first practical task is to determine exactly which values changed.

The second key check is whether the network requested:

acknowledgement only
or a later registration procedure

Important Information Elements

IE	Why it matters
`5G-GUTI`	Can change later paging and identity correlation.
`TAI list`	Affects where the UE is considered reachable.
`Allowed NSSAI`	Explains later slice behavior and slice availability.
`Configuration update indication`	Tells the UE whether acknowledgement or later registration is required.
`NITZ information`	Can explain time-related behavior when present.

Example message dump

Configuration Update Command
  Extended Protocol Discriminator: 5G Mobility Management
  Security Header Type: Integrity protected and ciphered
  Message Type: Configuration Update Command
  5G-GUTI: 02 F1 10 00 01 AB CD EF 56 78
  TAI List:
    PLMN: 001-01
    TAC: 0x2001
  Allowed NSSAI:
    S-NSSAI: SST 1, SD 0x112233
  Configuration Update Indication: Acknowledgement requested

How to read this dump

First identify which IEs are present.
Then decide whether the message is only updating stored context or also requesting later registration action.
After that, check whether the UE sends Configuration Update Complete.

What to check in logs

inspect which identity, TAI, slice, or timer fields changed
verify whether T3555 is started because acknowledgement was requested
correlate the command with Configuration Update Complete
compare later mobility or paging behavior with the updated context

FAQ

What does Configuration Update Command do in 5G?

It lets the network update UE registration-related context such as identity, tracking-area, slice, and timer information.

Summary

Configuration Update Command is the network-initiated NAS message used to update UE 5GMM context after registration.

Advanced Engineer Notes

This message is especially important when later behavior changes without a fresh full registration, because the network may have updated the UE context here.

Related message pages

Related Procedures

Related Tools

Use This Reference in Practice

Decode this message with the 3GPP Decoder, inspect the related message database, or open the matching call flow to see where this signaling step fits in the full procedure.