How UPF selection process works
Summary
This process explains how UPF selection process works.
Workflow
These are the stages involved in the process of unified UPF selection.
- PFCP Association process: In the Sx Association Setup Request, We publish the GTPU IP address in the Userplane IP address Information IE. During the PFCP Association process, the UPF sends the IE “Userplane IP address Information” in the Sx Association Setup Request message. This IE contains PGW-U IP and SGW-U IP (IPv4 or IPv6) addresses associated with the UPF. These addresses are sourced from the gtpu-service where the interface type is 'upf-ingress' or 'sgw-egress', regardless of the peer node type. The sgw-egress is mapped to SGW-U IPs, and upf-ingress is mapped to PGW-U IPs.
- Population of IP addresses: The SMF and EPC GW store stores the advertised S5-U bind addresses. The mapping associates each UPF with its PGW-U and SGW-U address information. The result is a local lookup source for later handover selection.
-
MSUP selection: For a converged call, the initial attach or 5G to 4G handover within MSG, same MSUP selection is preferred.
- Initial attach: For a subscriber in 4G RAT connecting to SMF via SGW, it should select the same MSUP. During the initial attach at SGW, an MSUP is selected. The SGW sends Create Session Request to SMF. The SMF receives Create Session Request with SGW GTPU IP in SGW F-TEID. SMF extacts this SGW GTPU IP. The SMF gets the MSUP from the mapping table based on this SGW GTPU IP and selects the same MSUP that SGW selects.
- 5G to 4G handover: For a subscriber anchored on SMF moving to 4G RAT, SGW should select the same MSUP selected by SMF. During 5G to 4G handover, PGW GTPU IP received in "S5/S8-U PGW FTEID" is extracted. SGW gets the MSUP from mapping table based on this PGW GTPU IP and selects the same MSUP selected by SMF.
Feedback