Subscribers, QoS, and filters

The BNG CUPS automatically links sessions together into subscribers, based on the QoS Enforcement Rule (QER) Correlation ID it receives in the PFCP session. If the BNG CUPS UPF does not receive a QER Correlation ID, it assumes there is only one session per subscriber.

The usual subscriber-management processing applies, as described in the 7450 ESS, 7750 SR, and VSR Triple Play Service Delivery Architecture Guide, sections "QoS for subscribers and hosts" through "Configuring IP and IPv6 filter policies for subscriber hosts".

The PFCP may pass the following parameters:

• subscriber and SLA profile names; if these are not provided the name "default" is used

  Note: You must always configue the SLA and subscriber profiles for use with BNG CUPS; for example, configure subscriber-mgmt sla-profile control cups or configure subscriber-mgmt sub-profile control cups. This disables any feature that is not supported within BNG CUPS.
• direct QoS overrides of QoS objects such as aggregate-rate, schedulers, arbiters, queues, and policers

• SLA filter overrides, either by name or ID

• intermediate destination ID

PFCP can also signal GBR and MBR values directly in the QER, which is not linked directly to a specific QoS object. If the QER applies to the entire session, you can map the MBR and GBR to a direct QoS object PIR or CIR override using the configure subscriber-mgmt sla-profile name pfcp-mappings session-qer command. The BNG CUPS CPF signals the QER rate, for example, to install a session-AMBR (5G) or APN-AMBR (4G) for FWA sessions.