GTPC Protocol Endpoint with UDP Proxy Bypass
With the UDP proxy mode, all message exchanges for the GTPv2 protocol occur through the UDP proxy. The UDP proxy is responsible for connecting or receiving connections on the S11 and S5e, S2b, and S5/S8 interface. The service or the GTP peer initiates the session-related or node-related messages, and the responses pass through the UDP proxy. The UDP proxy handles all node-related messages and forwards the messages to the protocol node.
With the inbound and outbound UDP proxy bypass mode, the service-initiated session-related messages are sent directly to the GTP peer through the GTPC-EP pod, with the UDP proxy bypassed. For node-related messages, the GTPC-EP starts a GTP endpoint for peers to connect with it on the S11, S5e, S2b, and S5/S8 interfaces. The GTPC-EP pod also establishes a connection with the GTP peer as and when the app service initiates a GTPv2 message toward the GTP peer.
The following features are integrated from UDP proxy:
-
Transaction SLA
-
DSCP marking for GTP packets
-
Adding BGP routes for roamer subscribers on the fly
-
Supporting Dispatcher feature and incoming retransmission
-
SGW cache integration for DDN
-
MBR cache integration
The following features are integrated from GTPC-EP:
-
Retransmissions based on n3t3 configuration for outbound requests
-
Monitor protocol and monitor subscriber
-
Echo message handling
All existing features supporting the UDP proxy mode are supported with and without the UDP proxy bypass mode.