Skip to content

NG Reset — Resetting UE-associated N2 Contexts

Why — This is not another NG Setup

NG Reset initializes or reinitializes UE-associated NGAP contexts when a failure has caused transaction or UE-related information to be lost. It does not change the application-level configuration exchanged during NG Setup (TS 38.413 Clause 8.7.4.1).

This companion chapter distinguishes Reset from NG Setup, per-UE UE Context Release and NAS Deregistration.

What — Initiator and scope are independent

  • Either the AMF or NG-RAN can initiate Reset.
  • Reset Type specifies Reset All for the entire NG interface or Part of NG interface.
  • For a partial Reset, the UE-associated Logical NG-connection List identifies targets using AMF UE NGAP ID and/or RAN UE NGAP ID.

References: TS 38.413 Clause 8.7.4.2 / Clause 9.2.6.11 / Clause 9.2.6.12. The examples below show AMF-initiated full Reset and NG-RAN-initiated partial Reset, but the initiator does not determine the scope.

Procedure — AMF-initiated NG Reset

The AMF resets UE-associated information on the NG interface in this example. NG Reset uses non-UE-associated signalling (TS 38.413 Clause 8.7.4.1 / Clause 8.7.4.2.1).

sequenceDiagram
    participant AMF
    participant RAN as NG-RAN
    Note over AMF: UE-related transaction information is lost
    AMF->>RAN: NG RESET<br/>(Cause, Reset Type = Reset All)
    Note over RAN: Release target UEs' NG / Uu resources<br/>Delete UE contexts and NGAP IDs
    RAN-->>AMF: NG RESET ACKNOWLEDGE
    Note over AMF,RAN: Configuration exchanged during NG Setup is unchanged

Step-by-step explanation

  1. The AMF specifies the scope: Cause and Reset Type state why and what to reset.
  2. NG-RAN processes the targets: It releases the specified UE-associated NG/Uu resources and contexts.
  3. Return the ACK: It is sent after releasing NG resources and UE NGAP IDs. There is no need to wait for radio-resource release to finish (TS 38.413 Clause 8.7.4.2.1).
  4. Keep the meaning bounded: The ACK acknowledges Reset processing. It does not confirm that all UEs have reconnected or re-registered.

Procedure — NG-RAN-initiated Partial Reset

This example resets a subset of UE-associated connections following a failure on the NG-RAN side (TS 38.413 Clause 8.7.4.2.2).

sequenceDiagram
    participant RAN as NG-RAN
    participant AMF
    Note over RAN: Transaction information is lost for some UEs
    RAN->>AMF: NG RESET<br/>(Cause, Part of NG interface, UE connection list)
    Note over AMF: Release listed UEs' NG resources and NGAP IDs
    AMF-->>RAN: NG RESET ACKNOWLEDGE<br/>(UE-associated Logical NG-connection List)
    Note over RAN,AMF: UEs outside the target list are not all reset

Step-by-step explanation

  1. List the target UEs: A partial Reset sends the target AMF UE NGAP IDs and/or RAN UE NGAP IDs.
  2. The AMF releases the relevant resources: It processes the specified UE-associated NG resources and NGAP IDs. Do not reinterpret Reset as unconditional deletion of AMF subscriber data or every PDU Session.
  3. Include the corresponding list in the ACK: The specification requires the targets to be returned in the received order, including unknown UE-associated connections. Empty received Items may be omitted under the specified conditions (TS 38.413 Clause 8.7.4.2.2).
  4. Check cancellation of concurrent procedures: Ongoing procedures for the target UE on the same NG interface are aborted, except another NG Reset. Check subsequent signalling to establish whether communication recovers after Reset (TS 38.413 Clause 8.7.4.2.2).

Packet Analysis

Use ngap to follow NG RESET and its ACK, Cause, Reset Type and the target ID list. Observe NGAP Reset separately even when SCTP remains connected. If several UEs are affected simultaneously, first distinguishing Reset All from partial Reset helps narrow the affected scope.

Knowledge check

  • Does NG Reset update information such as Supported TA List? → No. It does not change configuration exchanged through procedures such as NG Setup.
  • Does an AMF-originated Reset always mean Reset All? → No. Initiator and scope are separate dimensions.

3GPP Specification

Next Step

NG Setup / CM State / UE Context Release / Deregistration / N2 / Callflow