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 messages

Get a description of the PFCP messages that are applicable for the MAG-c.

Message types defines which PFCP messages are applicable for the MAG-c.

The applicability of the messages and the applicability of the information elements that are defined in 3GPP TS 29.244 remain as specified in 3GPP TS 29.244.

Information elements that are added and defined by BBF in TR-459 are prefixed with (BBF) in the tables of this chapter. However, their name does not include the (BBF) prefix.

Vendor-specific information elements are prefixed with Nokia. Their name includes the Nokia prefix.

For the applicable messages, only the IEs used by the MAG-c are listed in the tables. .

Note: The abbreviations listed in the P (Presence) column in the tables in this section represent the following:

M = Mandatory
C = Conditional
O = Optional

August 29, 2024