UE Configuration Update — Updating a Registered UE¶
Why — Some information can be updated without registering again¶
The AMF can update access and mobility management configuration for a registered UE. Unlike UE-initiated Mobility Registration Update, this is a network-initiated Generic UE configuration update (TS 23.502 Clause 4.2.4.2; TS 24.501 Clause 5.4.4).
Possible updates include 5G-GUTI, TAI List and NSSAI information. Rather than covering every field, this chapter uses an update of 5G-GUTI and TAI List with an acknowledgement requested.
Procedure — UE Configuration Update¶
The UE is registered and CM-CONNECTED. The diagram isolates the N1 exchange over 3GPP access and shows a case without a re-registration request. Updating 5G-GUTI or TAI List requires the AMF to request an acknowledgement from the UE (TS 23.502 Clause 4.2.4.2).
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
Note over AMF: Decide to update 5G-GUTI / TAI List
AMF->>RAN: NGAP Downlink NAS Transport<br/>NAS: Configuration Update Command (5G-GUTI, TAI List, ACK requested)
RAN->>UE: RRC DLInformationTransfer<br/>NAS: Configuration Update Command
Note over UE: Validate NAS message and<br/>apply accepted configuration
UE->>RAN: RRC ULInformationTransfer<br/>NAS: Configuration Update Complete
RAN->>AMF: NGAP Uplink NAS Transport<br/>NAS: Configuration Update Complete
Note over AMF: Receive UE acknowledgement
Note over UE,AMF: No new Registration in this exampleStep-by-step explanation¶
- The AMF decides to update: Changes to subscription data, policy or network configuration can trigger an update. Specific operational triggers and configuration methods are implementation-dependent.
- Send information and instructions in the Command: Updating information, requesting an acknowledgement and requesting re-registration are distinct aspects. The actual NAS message name is
Configuration Update Command(TS 24.501 Clause 5.4.4.2). - The UE applies the configuration: It accepts a valid message and updates the specified information. IEs other than 5G-GUTI/TAI List have their own processing conditions (TS 24.501 Clause 5.4.4.3).
- Return the requested ACK: Here the UE returns
Configuration Update Complete. Not every Command requests a Complete (TS 24.501 Clause 5.4.4.3 / Clause 5.4.4.4).
On an established connection NAS is relayed in NGAP Downlink/Uplink NAS Transport and RRC DLInformationTransfer/ULInformationTransfer (TS 38.413 Clause 8.6.2–Clause 8.6.3, TS 38.331 Clause 5.7.1–Clause 5.7.2).
Omitted updates to NG-RAN and UE lower layers
When 5G-GUTI is updated over 3GPP access, the AMF notifies NG-RAN of the new UE Identity Index Value after receiving the UE's ACK, and the UE passes the new 5G-GUTI to the lower layers of 3GPP access. These are not optional implementation details merely because they are absent from the diagram. Conditional rules also apply to multiple accesses (TS 23.502 Clause 4.2.4.2 steps 2c–2d).
First reach the UE if it is CM-IDLE
The AMF can wait until the UE becomes CM-CONNECTED or initiate a Network Triggered Service Request. The choice depends on the network implementation (TS 23.502 Clause 4.2.4.2 step 0). This preceding stage is omitted from the diagram.
Acknowledgement and re-registration are different instructions
When re-registration is requested, the updated information determines whether it occurs in CM-CONNECTED or starts in CM-IDLE after AN Release. Emergency sessions introduce additional conditions. It is therefore incorrect to always draw Complete → Release → Registration (TS 23.502 Clause 4.2.4.2 steps 3–4).
What — Distinguish similarly named procedures¶
- UE Configuration Update: The AMF updates the UE over N1/NAS (TS 24.501 Clause 5.4.4).
- AMF Configuration Update: A separate procedure updates NG-RAN configuration over N2/NGAP (TS 38.413 Clause 8.7.3).
- UE Policy delivery: Transparent UE Policy delivery has its own procedure. Do not confuse it with the access and mobility configuration update shown here (TS 23.502 Clause 4.2.4.3).
Packet Analysis¶
In NAS, inspect the Command's Configuration Update Indication and configuration IEs, then follow Complete according to whether acknowledgement was requested. If Registration follows, check the registration instruction and UE state. Display names and the ability to analyze encrypted NAS depend on the implementation and analysis environment.
Knowledge check¶
- Is a Command without a Complete always a failure? → Check whether acknowledgement was requested.
- Is this the same as AMF Configuration Update? → No. The peer and protocol differ.
3GPP Specification¶
- TS 23.502 V18.14.0 Clause 4.2.4.2 / Clause 4.2.4.3
- TS 24.501 V18.14.0 Clause 5.4.4.2–Clause 5.4.4.4
- TS 38.413 V18.10.0 Clause 8.7.3
Next Step¶
Mobility Registration Update / Service Request / GUAMI / Callflow