Skip to content

PFCP Association / Heartbeat — Session-control Prerequisites and Liveness

Why — What to check before Session Establishment

PFCP Rules covers session-level rules such as PDRs and FARs. Before controlling sessions, the SMF and UPF establish a PFCP Association. Association is node-level, whereas a PFCP Session is session-level; they are not the same kind of "connection" (TS 29.244 Clause 6.2.6 / Clause 6.3).

This chapter covers N4 in the 5GC, separating initial SMF-initiated Association establishment from Heartbeat.

Procedure — PFCP Association Setup

This example precedes the SMF's first PFCP Session. Node ID and IP address are not synonymous; destination discovery or configuration is a separate prerequisite (TS 29.244 Clause 5.8.1 / Clause 6.2.6.2).

sequenceDiagram
    participant SMF
    participant UPF
    Note over SMF: Obtain UPF destination via configuration / DNS / NRF, etc.
    SMF->>UPF: PFCP Association Setup Request<br/>(Node ID, Recovery Time Stamp, CP Function Features, etc.)
    alt UPF accepts
        UPF-->>SMF: PFCP Association Setup Response<br/>(Cause=success, Node ID, Recovery Time Stamp, UP Function Features, etc.)
        Note over SMF,UPF: Association established
        opt Subsequent PDU Session processing
            SMF->>UPF: PFCP Session Establishment Request
            UPF-->>SMF: PFCP Session Establishment Response
        end
    else UPF rejects the request
        UPF-->>SMF: PFCP Association Setup Response (error cause)
        Note over SMF: Do not start session-related procedures without a successful response
    end

Step-by-step explanation

  1. Obtain the destination: Obtain the UPF address through configuration or discovery. NRF use is not mandatory in every case (TS 29.244 Clause 5.8.1).
  2. Request Association: The SMF sends Node ID and other applicable information. Recovery Time Stamp is a message IE; CP/UP Function Features are conditional IEs related to supported functionality (TS 29.244 Clause 7.4.4.1 / Clause 7.4.4.2).
  3. Check Cause: Session-related control starts after a successful response. The rejection branch shows a normal error cause; separate responses such as unsupported PFCP version handling are omitted (TS 29.244 Clause 6.2.6.2).
  4. Create sessions separately: Establishing an Association does not automatically create forwarding rules for individual PDU Sessions.

Re-association is not session restoration

Re-association for an existing Node ID includes handling of PFCP Session Retention Information and the retention outcome. Existing sessions are not always retained (TS 29.244 Clause 6.2.6.2.2). For 5GC restart detection, use Heartbeat rather than the Recovery Timestamp in Association Setup (TS 23.527 Clause 4.2).

Procedure — PFCP Heartbeat

This example is initiated by the SMF. Heartbeat can also be initiated in the opposite direction, and a PFCP entity receiving a Heartbeat Request responds (TS 29.244 Clause 6.2.2).

sequenceDiagram
    participant SMF
    participant UPF
    SMF->>UPF: PFCP Heartbeat Request<br/>(SMF Recovery Time Stamp)
    alt Response received
        UPF-->>SMF: PFCP Heartbeat Response<br/>(UPF Recovery Time Stamp)
        Note over SMF: Check response availability and known Recovery Time Stamp
        opt Restart detected
            Note over SMF,UPF: Check Association re-establishment and restoration conditions
        end
    else No response
        Note over SMF: Detect failure according to retransmission and monitoring conditions
        Note over SMF,UPF: No response alone does not prove a restart
    end

Step-by-step explanation

  1. Probe the peer PFCP entity: Heartbeat checks the PFCP entity's liveness, not connectivity for each UE.
  2. Read the response and Recovery Time Stamp: Receiving a response and confirming that the peer has not restarted are separate observations. Restart detection follows TS 23.527 Clause 4.2.
  3. Investigate missing responses: Examine packet loss, the N4 path and peer state. Operational monitoring intervals and retransmission settings are implementation-dependent; no fixed values are assumed here.
  4. Follow restoration separately: Heartbeat does not restore sessions. Continue with UPF Recovery.

A Heartbeat response does not establish an Association

The specification requires a PFCP entity to be prepared to respond to Heartbeat Requests from unknown peers as well. A Heartbeat Response alone is not evidence of successful Association Setup (TS 29.244 Clause 6.2.2.2).

Packet Analysis

In pfcp, inspect Node ID, Cause and supported features for Association, and Sequence Number and Recovery Time Stamp for Heartbeat. Do not confuse the SEID in session messages with the node-level Association (TS 29.244 Clause 7.2 / Clause 7.4.2 / Clause 7.4.4).

Knowledge check

  • Is a PDU Session restored once Heartbeat responds? → No. Check liveness, Association and Session separately.
  • Is the Recovery Time Stamp in Association Setup used for 5GC restart detection? → TS 23.527 Clause 4.2 specifies that it is ignored. Check Heartbeat instead.

3GPP Specification

Next Step

PFCP Rules / UPF Recovery / N4 / Callflow