Feature Description

UDP Proxy Functionality Merged into Protocol Microservices

UDP Proxy microservices provide UDP transport termination for protocols (PFCP, GTPC, and RADIUS) that require UDP protocol as the transport layer protocol. The UDP proxy provides user space packet forwarding and IPC communication to protocol microservices. It uses host networking for source IP address observability and operates in Active-Standby mode.

Multiple protocol microservices depend on UDP proxy for UDP transport. Therefore, UDP proxy is a scaling bottleneck. A surge of messages can lead to packet drop.

The incoming and outgoing messages use the UDP proxy pod for forwarding messages. With minimal packet processing, the UDP proxy forwards the messages to the GTPC-EP pod. This requires the IPC communication for message forwarding, along with marshal or unmarshal of the packet.

Merging the UDP proxy functionality into a respective protocol microservice helps in mitigating the scaling bottleneck. The protocol pod receive the messages directly, and avoids forwarding the messages and the IPC communication.

UDP proxy bypass improves the CPU usage by reducing one hop across microservices in the signaling path.

cnSGW-C supports UDP proxy bypass for the following protocols:

  • PFCP

  • GTPC

GTPC Endpoint with GR Split

To handle the scaled GTP traffic and to optimally use the CPU, multiple active instances of GTPC-EP are started, and a traffic split is performed based on GR instances.

Optimized GTPv2 Encoder and Decoder

Optimized GTPv2 encoder and decoder is provided for the following messages:

  • Bearer Resource Command

  • Change Notification Request / Response

  • Create Bearer Request / Response

  • Create IDFT Request / Response

  • Create Session Request / Response

  • Delete Bearer Command

  • Delete Bearer Failure Indication

  • Delete Bearer Request / Response

  • Delete IDFT Request / Response

  • Delete Session Request / Response

  • Downlink Data Notification Acknowledgment

  • Downlink Data Notification Failure Indication

  • Download Datalink Notification Request

  • Echo Request / Response

  • Modify Bearer Request / Response

  • Modify Bearer Command

  • Modify Bearer Failure Indication

  • Update Bearer Request / Response

For more information, refer to the Performance Optimization Support chapter.