Application triggered setup of distributed anchor for edge computing
Embodiments describing methods performed by a system comprising Network functions including at least a Session Management Function and a User Plane Function for performing a UPF re-anchoring for an application triggered at a User Equipment over an established Packet Data Unit (PDU) Session, where when the system receives the initial trigger for a service triggered by the application (e.g., a DNS request or an application level request), a determination is made by the system based on the information related to the application that re-anchoring of the UPF for that application into a local UPF closer to the UE is required. When re-anchoring of the UPF is successful, the initial trigger is discarded, and the UE is instructed to establish a new PDU session over the local UPF for that application.
1. A method performed by a one or more network functions in a network, the method comprising:
receiving a DNS request as a trigger for a service related to an application in a User Equipment (UE) over a first Packet Data Unit (PDU) session anchored at a first User Plane Function (UPF);
determining that UPF re-anchoring is required for the application based on the trigger;
In response to determining that UPF re-anchoring is required, establishing a second PDU session to a local UPF to be used between the application in the UE and an edge application server; and
In response to determining that UPF re-anchoring is not required, providing the service for the application as triggered via the first UPF.
2. The method of claim 1 wherein determining that UPF re-anchoring is required further comprises extracting a Fully Qualified Domain Name (FQDN) from the DNS query and verifying that at least one of a Service Level Agreement SLA and policies related to the FQDN indicate that the UPF re-anchoring for the application is required.
3. The method of claim 1 further comprises in response to determining that re-anchoring is successful, dropping the DNS query.
4. A server system hosting one or more network functions of the same or different type and comprising one or more processing circuitry and one or more memory, the memory containing instructions executable by the processing circuitry whereby the server system is configured to:
receive a DNS request as a trigger for a service related to an application in a User Equipment (UE) over a first Packet Data Unit (PDU) session anchored at a first User Plane Function (UPF);
determine that UPF re-anchoring is required for the application based on the trigger;
In response to determining that UPF re-anchoring is required, establish a second PDU session to a local UPF to be used between the application in the UE and an edge application server; and
In response to determining that UPF re-anchoring is not required, provide the service for the application as triggered via the first UPF.
5. A server system of claim 4 , where the one or more network functions comprises at least a Session Management Function and a User plane function.
6. A non-transitory computer readable medium containing a computer program or instructions, wherein when the computer program or instructions is executed by a compute server, causes it to perform the steps of:
receiving a DNS request as a trigger for a service related to an application in a User Equipment (UE) over a first Packet Data Unit (PDU) session anchored at a first User Plane Function (UPF);
determining that UPF re-anchoring is required for the application based on the trigger;
In response to determining that UPF re-anchoring is required, establishing a second PDU session to a local UPF to be used between the application in the UE and an edge application server; and
In response to determining that UPF re-anchoring is not required, providing the service for the application as triggered via the first UPF.
7. The server system of claim 4 wherein the server system configured to determine that UPF re-anchoring is required further comprises the server system configured to extract a Fully Qualified Domain Name (FQDN) from the DNS query and verifying that at least one of a Service Level Agreement SLA and policies related to the FQDN indicate that the UPF re-anchoring for the application is required.
8. The server system of claim 4 further configured to in response to determining that re-anchoring is successful, drop the DNS query.