Feature Description
When the cnSGW service and SMF service selected for a subscriber are on the same cluster and same rack, the messages exchanged between the two services flow through the gtpc-ep pod.
If a collocated session is identified and enable-gtpc-bypass CLI command is configured under GTP endpoint, then the SMF and cnSGW-C directly communicate with each other without exchanging the messages through the gtpc-ep pod. This approach reduces the latency and the processing load on the gtpc-ep. For details on the command, see the Feature Configuration section.
The SMF service directly communicates with cnSGW service for processing the following requests:
-
Create Bearer Request
-
Update Bearer Request (UBR) (expect Modify Bearer Command (MBC) triggered UBR)
-
Delete Bearer Request (DBR) (expect Delete Bearer Command (DBC) triggered DBR)
The cnSGW service directly communicates with SMF service for processing the following requests:
-
Create Session Request
-
Modify Bearer Request
-
Delete Session Request
If the subscriber session is not collocated, the inbound and outbound messages from SMF or cnSGW-C continue to be exchanged through the gtpc-ep pod.
For this feature support on cnSGW, see the UCC 5G cnSGWc Configuration and Administration Guide.