Skip to content

UPF Restart / Recovery — Restart Detection and Session Restoration

Why — A running process is not restored connectivity

A UPF restart does not by itself restore the previous forwarding rules. Check peer restart detection → Association re-establishment → restoration of the relevant PFCP Sessions separately (TS 23.527 Clause 4.2 / Clause 4.3).

This chapter assumes the SMF retains control information for the target sessions. An SMF restart or simultaneous failure is a separate procedure. Recovery from a PSA UPF failure without a restart is specified as implementation-dependent (TS 23.527 Clause 4.3.3 / Clause 4.4).

Procedure — PSA UPF Recovery

This example shows the SMF performing restoration. It does not guarantee restoration of every session. Restart detection uses the Recovery Time Stamp in Heartbeat, not the timestamp in Association Setup (TS 23.527 Clause 4.2 / Clause 4.3.2).

sequenceDiagram
    participant SMF
    participant PSA as PSA UPF
    Note over PSA: UPF restarts
    SMF->>PSA: PFCP Heartbeat Request
    PSA-->>SMF: PFCP Heartbeat Response (Recovery Time Stamp)
    Note over SMF: Detect peer restart
    SMF->>PSA: PFCP Association Setup Request
    PSA-->>SMF: PFCP Association Setup Response
    opt Association re-established and SMF performs session restoration
        SMF->>PSA: PFCP Session Establishment Request<br/>(original session information, restoration indication when applicable)
        alt Requested resources can be accepted
            PSA-->>SMF: PFCP Session Establishment Response (success)
            Note over SMF,PSA: Check restoration outcome for this PFCP Session
        else Requested addresses or other resources are unavailable
            PSA-->>SMF: PFCP Session Establishment Response<br/>(restoration failure cause)
            Note over SMF: Do not treat this as success#59; check subsequent processing
        end
    end

Step-by-step explanation

  1. Detect the restart: Compare the Heartbeat Recovery Time Stamp with known information. A response timeout alone does not prove a restart.
  2. Re-establish the Association: Restore the control relationship with the peer. A successful response alone does not confirm each session's PDRs/FARs and other rules.
  3. Restore sessions individually: Where the PSA UPF allocates F-TEIDs or UE IP addresses, the SMF includes a restoration indication identifying restoration of an existing session (TS 23.527 Clause 4.3.2).
  4. Check resource acceptance: The UPF accepts SMF-specified values when possible. If requested addresses or other resources are unavailable, it returns a restoration-failure cause. Preservation of the original IP address is not unconditional.
  5. Check the extent of success: Restoration priorities follow operator policy, while restoration load control is implementation-dependent. Check actual user-plane connectivity as well as control-plane success.

Post-restart resources and Error Indication

When the PSA UPF allocates F-TEIDs or UE IP addresses, it needs a mechanism to avoid immediately reusing pre-restart values. That mechanism is implementation-dependent. The specification also suppresses GTP-U Error Indications for G-PDUs that match no PDR during a configurable period. This chapter does not assume a fixed duration (TS 23.527 Clause 4.3.2).

Procedure — Intermediate UPF Recovery

This example covers an Intermediate UPF when the SMF supports reactive restoration. Rather than just renaming the node in the PSA diagram, it shows the path in which an unmatched packet triggers restoration (TS 23.527 Clause 4.3.4).

sequenceDiagram
    participant Peer as GTP-U peer (e.g. NG-RAN)
    participant IUPF as Intermediate UPF
    participant SMF
    Note over IUPF,SMF: Restart detected and Association already re-established
    SMF->>IUPF: PFCP Session Establishment Request<br/>(wildcarded PDR forwarding G-PDUs unmatched by other PDRs to SMF)
    IUPF-->>SMF: PFCP Session Establishment Response
    Peer->>IUPF: G-PDU
    IUPF->>SMF: G-PDU (unmatched packet over PFCP-u tunnel)
    Note over SMF: Check for a corresponding active session
    alt SMF has an active session
        SMF->>IUPF: PFCP Session Establishment Request<br/>(restore target session)
        IUPF-->>SMF: PFCP Session Establishment Response
    else No active session
        SMF->>IUPF: GTP-U Error Indication<br/>(addressed to the original G-PDU source)
        IUPF-->>Peer: GTP-U Error Indication (transparent forwarding)
    end
    Note over SMF: Discard the inspected G-PDU

Step-by-step explanation

  1. Check restoration-mode support: Proactive restoration is also possible. This diagram is limited to the reactive mode.
  2. Prepare forwarding for unmatched packets: The SMF configures a PFCP Session with a wildcarded PDR to forward G-PDUs unmatched by other PDRs to a unique F-TEID at the SMF.
  3. Look up the session when data arrives: The PFCP-u tunnel carries a user packet. Do not confuse it with a PFCP Heartbeat message.
  4. Restore if the session exists: If the SMF has an active session, it recreates that session's PFCP configuration. Otherwise, the path returns a GTP-U Error Indication to the original sender.
  5. Check the first packet's treatment: The SMF discards the G-PDU after the lookup. The diagram does not guarantee buffering and redelivery of that packet (TS 23.527 Clause 4.3.4).

Restoration conditions also apply to I-UPF

Where the I-UPF allocates F-TEIDs, a restoration indication is also required when requesting restoration of an existing PFCP Session. An operator-configurable period suppresses Error Indications for unmatched G-PDUs immediately after restart. Reactive restoration must account for the time needed for restart detection, Association establishment and wildcarded PDR configuration. Check the configuration rather than assuming a fixed duration (TS 23.527 Clause 4.3.4).

Packet Analysis

  • Compare Recovery Time Stamp values across Heartbeat exchanges.
  • Check Association success separately from Session Establishment restoration results.
  • Identify the PSA/I-UPF role, F-TEID/IP allocator, retained SMF context and restoration mode.
  • Do not assume universal values for restoration targets, priorities, rate control or operational actions after failure. Configuration and observation methods are implementation-dependent.

Knowledge check

  • Does a restored Association mean every session is restored? → No. Each session's result must be checked.
  • Is the first G-PDU always delivered during reactive I-UPF restoration? → No. In this procedure, the SMF discards it after inspection.

3GPP Specification

Next Step

Association / Heartbeat / PFCP Rules / PDR / PDI / Callflow