Reference
Documents under this category include information about the attributes, APIs, interfaces, and the full set of CLI commands supported by the MAG-c.
- CLI Reference Guide
  This guide describes all CLI commands and their supported values and parameters.
- PFCP Interface Description Guide
  - Getting started
    Find general information about this guide.
  - Introduction to PFCP and CUPS concepts
    The interfaces between the MAG-c and the BNG-UP 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.
  - Forwarding between MAG-c and BNG-UP
    The forwarding of control plane messages is in-band and sent using an IBCP tunnel.
  - Session handling
    A PFCP session is set up to control the creation, modification, and deletion of a bundle of PDRs. There is a single PFCP session per connected device.
  - PFCP protocol
    The core of session management is the PFCP protocol as defined in 3GPP TS 29.244, with BNG-specific extensions defined in BBF TR-459.
  - PFCP messages
    Get a description of the PFCP messages that are applicable for the MAG-c.
  - Nokia-specific information elements
    Get a description of the new and modified vendor-specific information elements required for the MAG-c.
  - Appendix: References
  - PFCP Interface Description Guide PDF
- RADIUS Attributes and IU Triggers
  A searchable HTML list of all supported RADIUS attributes and RADIUS Interim Update (IU) triggers for the MAG-C.
- TPSDA Python 3 API
  Python developers can use these APIs for a model-driven management interface to integrate with supported Nokia routers running the SR OS.

PFCP node-related messages

PFCP association messages

PFCP Association Setup Request

The PFCP Association Setup Request message can be initiated either from the MAG-c or from the BNG-UP.

Table 1. IEs in a PFCP Association Setup Request
Information elements	P	Description
Node ID	M	This IE contains the unique identifier of the sending node.
Recovery Time Stamp	M	This IE contains the time stamp when the node was started. This IE is ignored on the SCi interface.
UP Function Features	C	This IE is present if the BNG-UP sends the message and supports at least one UP feature defined in this IE. When present, this IE indicates the features that the BNG-UP supports.
CP Function Features	C	This IE is present if the MAG-c sends the message and supports at least one CP feature defined in this IE. When present, this IE indicates the features that the MAG-c supports.
(BBF) BBF UP Function Features	C	This IE is present if the BNG-UP sends the message and supports at least one BBF UP feature defined in this IE. When present, this IE indicates the BBF features that the BNG-UP supports.
Nokia UP Function Features See Nokia UP Function Features IE	C	This IE is present if the BNG-UP sends the message and supports at least one Nokia UP feature defined in this IE. When present, this IE indicates the Nokia-specific features that the BNG-UP supports.
Nokia NAT ISA members See Nokia NAT ISA Members IE	C	This IE is present if the BNG-UP sends the message and the Nokia UP Function Features IE indicates NAT support. When present, this IE includes the number of ISA members on the NAT group. When not present, the number of ISA members on the NAT group is assumed to be 1.

PFCP Association Setup Response

Table 2. IEs in a PFCP Association Setup Response
Information elements	P	Description
Node ID	M	This IE contains the unique identifier of the sending node.
Cause	M	This IE indicates the acceptance or the rejection of the corresponding request message.
Recovery Time Stamp	M	This IE contains the time stamp when the node was started. This IE is ignored on the SCi interface.
UP Function Features	C	This IE is present if the BNG-UP sends the message and supports at least one UP feature defined in this IE. When present, this IE indicates the features that the BNG-UP supports.
CP Function Features	C	This IE is present if the MAG-c sends the message and supports at least one CP feature defined in this IE. When present, this IE indicates the features that the MAG-c supports.
(BBF) BBF UP Function Features	C	This IE is present if the BNG-UP sends the message and supports at least one BBF UP feature defined in this IE. When present, this IE indicates the BBF features that the BNG-UP supports.
Nokia UP Function Features See Nokia UP Function Features IE	C	This IE is present if the BNG-UP sends the message and supports at least one Nokia UP feature defined in this IE. When present, this IE indicates the Nokia-specific features that the BNG-UP supports.
Nokia NAT ISA members See Nokia NAT ISA Members IE	C	This IE is present if the BNG-UP sends the message and the Nokia UP Function Features IE indicates NAT support. When present, this IE includes the number of ISA members on the NAT group. When not present, the number of ISA members on the NAT group is assumed to be 1.

PFCP Association Update Request

The PFCP Association Update Request message can be initiated either from the MAG-c or from the BNG-UP.

Table 3. IEs in a PFCP Association Update Request
Information elements	P	Description
Node ID	M	This IE contains the unique identifier of the sending node.
UP Function Features	O	This IE may be present if the BNG-UP sends the message and supports at least one UP feature defined in this IE. When present, this IE indicates the features that the BNG-UP supports.
CP Function Features	O	This IE may be present if the MAG-c sends the message and supports at least one CP feature defined in this IE. When present, this IE indicates the features that the MAG-c supports.
PFCP Association Release Request	C	This IE is present if the BNG-UP requests the MAG-c to release the PFCP association.
Graceful Release Period	C	This IE is present if the BNG-UP requests a graceful release of the PFCP association.
(BBF) BBF UP Function Features	C	This IE is present if the BNG-UP sends the message and supports at least one BBF UP feature defined in this IE. When present, this IE indicates the BBF features that the BNG-UP supports.
Nokia UP Function Features See Nokia UP Function Features IE	C	This IE is present if the BNG-UP sends the message and supports at least one Nokia UP feature defined in this IE. When present, this IE indicates the Nokia-specific features that the BNG-UP supports.
Nokia NAT ISA members See Nokia NAT ISA Members IE	C	This IE is present if the BNG-UP sends the message and the Nokia UP Function Features IE indicates NAT support. When present, this IE includes the number of ISA members on the NAT group. When not present, the number of ISA members on the NAT group is assumed to be 1.

PFCP Association Update Response

Table 4. IEs in a PFCP Association Update Response
Information elements	P	Description
Node ID	M	This IE contains the unique identifier of the sending node.
Cause	M	This IE indicates the acceptance or the rejection of the corresponding request message.
UP Function Features	O	This IE may be present if the BNG-UP sends the message and supports at least one UP feature defined in this IE. When present, this IE indicates the features that the BNG-UP supports.
CP Function Features	O	This IE may be present if the MAG-c sends the message and supports at least one CP feature defined in this IE. When present, this IE indicates the features that the MAG-c supports.
(BBF) BBF UP Function Features	C	This IE is present if the BNG-UP sends the message and supports at least one BBF UP feature defined in this IE. When present, this IE indicates the BBF features that the BNG-UP supports.
Nokia UP Function Features See Nokia UP Function Features IE	C	This IE is present if the BNG-UP sends the message and supports at least one Nokia UP feature defined in this IE. When present, this IE indicates the Nokia-specific features that the BNG-UP supports.
Nokia NAT ISA members See Nokia NAT ISA Members IE	C	This IE is present if the BNG-UP sends the message and the Nokia UP Function Features IE indicates NAT support. When present, this IE includes the number of ISA members on the NAT group. When not present, the number of ISA members on the NAT group is assumed to be 1.

Heartbeat messages

PFCP Heartbeat Request

Table 5. IEs in a PFCP Heartbeat Request
Information elements	P	Description
Recovery Time Stamp	M	This IE contains the time stamp when the node was started.
Nokia PFCPHB-Flags See Nokia PFCPHB-Flags IE	C	The BNG-UP includes this IE to trigger an audit request. The MAG-c includes this IE to signal the start or the end of an audit.

PFCP Heartbeat Response

Table 6. IEs in a PFCP Heartbeat Response
Information elements	P	Description
Recovery Time Stamp	M	This IE contains the time stamp when the node was started.

August 29, 2024