Introduction to CUPS

CUPS is an architecture that gains popularity in the mobile core. The architecture was first adopted in the 4G Long Term Evolution (LTE) mobile core and later became the standard architecture for the 5G core. In 2019, BBF began a BNG CUPS project and subsequently standardized the BNG CUPS architecture in TR-459, TR-459.2, and TR-459.3. BBF continues to define new standardized features and solutions contributed by service providers and vendors.

BNG CUPS

Nokia offers the standard BNG CUPS features defined by BBF. The Nokia CUPS solution includes fixed wireless access (FWA) and resiliency solutions.

The following figure shows a high-level CUPS architecture as defined in TR-459.

The CUPS solution supports the following interfaces between the CP (Nokia MAG-c) and the UP (Nokia MAG-u ):
  • state control interface (SCi)
  • control packet redirect interface (CPRi)
  • management interface (Mi)
Figure 1. General CUPS architecture

BBF defines BNG CUPS as a disaggregated BNG (DBNG) where the CP of the DBNG is known as the DBNG-CP and the UP of the DBNG is known as the DBNG-UP. The following terms are used interchangeably in the industry:

  • DBNG and BNG CUPS
  • user plane (UP) and data plane (DP)

DBNG-CP overview

The DBNG-CP (referred to as the MAG-c in this document), provides subscriber management functions including authentication, authorization, and accounting (AAA), IP address management, and policy management. The MAG-c has northbound control interfaces (NCIs) to communicate with external systems, such as remote authentication dial in user service (RADIUS) servers and policy services. The MAG-c uses standard interfaces defined in TR-459 to interact with the DBNG-UP (referred to as the MAG-u in this document), such as programing data traffic forwarding rules.

Note: Subscriber routing, including the IGP or BGP routing control plane, is only located on the MAG-u, and CUPS is only applicable to the subscriber management function within the BNG.

DBNG-UP overview

The DBNG-UP (MAG-u) is responsible for subscriber data traffic forwarding. The MAG-u performs the following key functions:
  • traffic management, including NAT and multicast replication
  • policy enforcement
  • subscriber statistics collection
The MAG-u installs the subscriber forwarding rules communicated by the CP (MAG-c) through the SCi.
Note: For the DBNG architecture, the subscriber routing function, which includes the IGP and BGP routing control and packet forwarding, remains entirely on the MAG-u. The MAG-c is not involved in any subscriber routing process.

DBNG interfaces

State control interface

The state control interface (SCi) is responsible for programming subscriber data forwarding rules on the MAG-u. The CUPS solution uses the 3GPP packet forwarding control protocol (PFCP) protocol as specified in 3GPP TS 29.244. 3GPP designed the PFCP to be fully extensible. To accommodate the broadband wireline use case, BBF extended the PFCP information elements (IEs) and published the extension in TR-459. Nokia extended the PFCP IE set to offer additional feature sets.

For wireline access, the SCi programs at minimum the following two types of rules:

  • control packet redirection rules – bidirectional rules to redirect subscriber wireline control packets, via the MAG-u, from the residential gateway (RG) to the MAG-c and from the MAG-c to the RG
  • subscriber data forwarding rules – bidirectional rules to forward subscriber traffic between the access interface and the network interface
    Note: The terms "network interface" and "core interface" are used interchangeably in the industry.

See the MAG-c PFCP Interface Description Guide for more information about the SCi and the PFCP.

Control packet redirect interface

The purpose of the control packet redirect interface (CPRi) is to tunnel the control packets of the RG that are received on the MAG-u to the MAG-c and from the MAG-c to the MAG-u and back to the RG. The tunnel encapsulation is the GPRS tunneling protocol - user plane (GTP-U) as specified in 3GPP TS 29.244. GTP-U is extended with an optional network service header (NSH) as defined in RFC 8300, to carry MAG-u metadata such as the ingress port. There are two types of CPRi tunnels:
  • per-session CPRi tunnels
  • common CPRi tunnels
The SCi installs each CPRi tunnel on the MAG-u.
Note: The terms "CPRi" and "IBCP" (the Nokia in-band control plane) are used interchangeably; both indicate the same interface and function.

See the MAG-c PFCP Interface Description Guide for more information about the CPRi and GTP-U.

Management interface

The MAG-c uses the management interface (Mi) to program the MAG-u for everything that is not related to subscriber forwarding rules. BBF TR-459 has no specifications for this interface.