Redirection rules and actions that are received over Gx are part of RAR and CCA-U messages in a dynamic rule. CUPS supports redirection rules and actions to be conveyed from C-Plane to U-Plane and applied to U-Plane. The following fields are translated and sent to U-Plane and U-Plane redirects accordingly:

[V] Redirect-Information
   [V] Redirect-Support
   [M] Redirect-Address-Type
   [M] Redirect-Server-Address

In C-Plane:

• FAR, associated with PDR, is populated to support "Redirect-Information" AVP in ADC dynamic rule over Gx.

• PDR and FAR are sent with the "Redirect Information" IE to U-Plane in:

  • Sx Session Establishment Request in case "Redirect-Information" AVP is received in an ADC dynamic rule over Gx in CCA-I from PCRF.

  • Sx Session Modification Request in case "Redirect-Information" AVP is received in an ADC dynamic rule over Gx in CCA-U from PCRF.

  • Sx Session Modification Request in case "Redirect-Information" AVP is received in an ADC dynamic rule over Gx in RAR from PCRF.

• Support is added for removal of ADC dynamic rule.

In U-Plane:

• ADC dynamic rule for the subscriber is installed.

• The packet is redirected if ADC dynamic rule is matched.

For more details, refer to the ADC Over Gx chapter in the Ultra Packet Core CUPS Conrol Plane Administration Guide or the Ultra Packet Core CUPS User Plane Administration Guide.

LTE-M (LTE-MTC low-power-wide area (LPWA)) is a cellular radio access technology that is specified by 3GPP that addresses low power-wide area connectivity solutions. It specifically refers to a category of LTE UEs that are suitable for IoT LTE-M, which supports IoT through lower device complexity and provides extended coverage, while allowing the reuse of the LTE installed base. The RAT Type Information Element (IE) is present in various call flows across many interfaces. When a Create Session Request is received with an unknown RAT Type, as the RAT Type is a mandatory IE in this message, S-GW or P-GW may reject a Create Session Request. With this feature, LTE-M RAT (Radio Access Technology) Type for CUPS is supported.

For more information, refer to the LTE-M RAT Type Support chapter in the Ultra Packet Core CUPS Control Plane Administration Guide or the Ultra Packet Core CUPS User Plane Administration Guide.

StarOS/CUPS supports signature file verification along with P2P binary file. This feature is enabled in both trusted and normal builds. Verification is mandatory in trusted builds and is optional in normal builds.

Use the following CLI configuration command to verify the P2P signing process:

patch plugin filepath binary_path  certificate  certificate_path  signature  signature_path   

When P2P binary file along with a signature file gets patched into the system, StarOS/CUPS verifies the signature and accepts or rejects the P2P binary file.

For more information, refer to the Application Detection and Control Configuration chapter in the ADC Administration Guide.

A simple traffic classification helps in simplifying the operation and configuration processes in Traffic Steering due to the huge number of the charging rules across multiple rulebases.

• Trigger condition in service scheme framework supports post processing ruledef name match.

• The L3/L4 ruledef which is configured as a post processing rule for traffic is traffic-steered.

• Trigger action supports trigger condition of post processing rule match for traffic steering.

• The post processing ruledef name in trigger condition is supported in PFD push and RCM.

For more information, refer to the NSH Traffic Steering chapter in the Ultra Packet Core CUPS Control Plane Administration Guide or the Ultra Packet Core CUPS User Plane Administration Guide.

Previous Behavior: The RCM BFD Manager runs only in host networking mode.

New Behavior: The RCM BFD Manager can run either in host networking mode (legacy) or non-host networking mode based on a CLI toggle.

Customer Impact: None.

The following two RCM Ops Center CLI commands are introduced:

1. k8 smf profile rcm-bfd-ep host-networking { true | false }

   The default value of this CLI command is true .

2. k8 smf profile rcm-bfd-ep node-port-enabled { true | false }

   The default value of this CLI command is false .

NOTES:

• The node-port-enabled must be set to true when host-networking is set to false .

• The host-networking to false must not be set in CNDP.