UDP Proxy for SMF Call Flow
The following call flow describes the flow of messages for the SMF initiated messages (applicable to messages initiated by peer nodes as well).

Step | Description |
---|---|
1 | The peer nodes send the UDP messages to the VIP address. The active instance of “smf-udp-proxy” receives the UDP messages. |
2 | The UDP message’s IP and the UDP header is stripped and the UDP payload is sent to the selected smf-protocol, gtp-ep, or radius-ep POD. The meta-data contains the source IP and source port number. With the help of the internal GRPC based IPC, the message is forwarded to the smf-protocol, gtp-ep, or radius-ep POD. |
3 | Based on the protocol, the smf-protocol, gtp-ep, or radius-ep POD decodes the message and loads the contents in proto-encoded buffer. The smf-protocol, gtp-ep, or radius-ep POD forwards the message to the smf-service POD for further processing over GRPC. |
4 | The smf-service POD generates the response message and sends it back to the smf-protocol, gtp-ep, or radius-ep POD in proto-encoded buffer. |
5 | The smf-protocol, gtp-ep, or radius-ep POD encodes the message and creates the UDP payload. The UDP payload is sent to the active “smf-udp-proxy” in a GRPC message. |
6 | The active “smf-udp-proxy” sends the message to the peer nodes on the UDP socket. |