Introduction to PFCP and CUPS concepts

The interfaces between the cMAG-c and the MAG-u that are related to PFCP are the SCi, CPRi, Sx, N4, Sx-u, and N4-u interfaces. Get a brief overview of those interfaces and of general CUPS and BNG concepts, including PFCP association and path, PFCP session, and PDR.

PFCP in the CUPS architecture

The interfaces between the cMAG-c and the MAG-u that are related to PFCP are the SCi, CPRi, Sx, N4, Sx-u, and N4-u interfaces.

The following lists the interfaces between the cMAG-c and the MAG-u.

  • SCi, Sx, N4

    The cMAG-c creates traffic forwarding rules and related states on the MAG-u via these interfaces. When the rules and states are created, the MAG-u forwards subscriber data traffic accordingly. The Sx interface is defined by 3GPP for 4G sessions, while the N4 interface is defined for 5G sessions. 3GPP defines these interfaces mainly in TS 29.244. The SCi interface is an extension added for pure BNG sessions as defined in TR-459 and is based on the Sx/N4 interface.

  • CPRi, Sx-u, N4-u

    The MAG-u and cMAG-c use these interfaces to forward and tunnel control packets; for example, DHCP discovery and PPPoE Active Discovery Initiation (PADI). All these interfaces use GTP-U as the tunnel transport layer and these tunnels are configured using the PFCP protocol. Sx-u and N4-u are the 3GPP terms defined in TS 29.244 in context of 4G and 5G sessions, while CPRi is the BBF term defined in TR-459, but all imply the same concept. Nokia uses the term in-band control plane (IBCP) to indicate any of these interfaces.

CUPS concepts

Get a brief overview of general CUPS and BNG concepts. See 3GPP TS 29.244 for more information about the CUPS concepts.

PFCP association and path

The PFCP association and path define the connectivity between the cMAG-c and MAG-u.

To send a session to a MAG-u, a PFCP association needs to be established. While establishing this association, the MAG-u and the cMAG-c exchange capabilities, functional features, and parameters; for example, a MAG-u sends functional features such as PPPoE support, IPoE support, and LCP keep-alive offload support.

  • PFCP association

    A PFCP association must be set up before sessions can be established between the MAG-u and the cMAG-c. Only one association per cMAG-c and MAG-u pair is allowed. The identifiers of the association are the cMAG-c and the MAG-u node IDs, which can be IP addresses or domain names (FQDNs). Nokia recommends using an FQDN as identifier because it is more stable.

  • PFCP path

    Multiple paths are possible per PFCP association. The identifier of a PFCP path is the pair of IP addresses to communicate between the cMAG-c and the MAG-u. Paths are not negotiated but are learned while using PFCP signaling. Each IP address is called a PFCP entity. Each pair of cMAG-c and MAG-u IP addresses is called a PFCP path.

Note: Both the cMAG-c and MAG-u use PFCP heartbeat messages to verify that all peering PFCP entities are alive. The heartbeat parameters are configured in the context of the PFCP profile.

PFCP session

A session is the basic operational object of the MAG, and represents the connectivity of a single device such as a residential gateway. The following are done in the scope of a single session:

  • address assignment
  • authentication
  • accounting
  • communication

A PFCP association is required to create a PFCP session.

Packet data rule

Packet data rules (PDRs) are the building blocks to create a correct forwarding state on the MAG-u.

The PFCP sessions are containers for PDRs. Each PDR defines a unidirectional traffic flow and the rules associated with that flow. The MAG-u adheres to the PDR rules when treating the traffic for the defined traffic flow.

A PDR consists of the following sub-objects and references.

  • PDI

    The packet detection information (PDI ) is a sub-object that specifies the match criteria for the packet. It contains detailed flow matching criteria and is usually set to "any flow". It also contains a reference to a traffic endpoint that contains the session matching criteria.

  • TE

    The traffic endpoint (TE) specifies the identifying criteria for the session, for example the Layer 2 access ID, VLANs, MAC address, and IP addresses. The PDR refers to one TE via the PDI. TEs can be shared between multiple PDRs within a session.

  • FAR ID

    The forwarding action rule (FAR) specifies the action (for example, drop, forward, mirror) for matching packets. The PDR refers to one FAR. FARs can be shared between multiple PDRs within a session.

  • QER ID

    The QoS enforcement rule (QER) specifies the QoS treatment for matching packets (for example, GBR, MBR). The PDR refers to one or multiple QERs. QERs can be shared between multiple PDRs within a session and between sessions.

    Multiple PDRs of one session share the same QER using the QER ID, while multiple PDRs of different sessions share the same QER using the QER correlation ID.

  • URR ID

    The usage reporting rule (URR) specifies the usage reporting and charging for matching packets. The PDR refers to one or multiple URRs. URRs can be shared between multiple PDRs within a session.