IP Library › Granted Patent US 12,349,006
Granted Patent B2
US 12,349,006 · App. 18/010,320 · Granted Jul 1, 2025

Coordination of edge application server reselection using edge client subnet

Inventors: Maria Luisa Mas Rosique (Tres Cantos, ES); Attila Mihály (Dunakeszi, HU); Jan Backman (Kärna, SE)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04W28/0858H04W40/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,349,006
App. No.
18/010,320
Granted
Jul 1, 2025
Kind
B2
Abstract

A Session Management Function, SMF, ( 650 ) determines that a first data path for a Packet Data Unit, PDU, session between an application client ( 611 ) and a first edge application server, EAS, ( 681 ) should be relocated from a first local PDU session anchor, PSA, ( 631 ) and a first uplink classifier and branching point, ULCL/BP, ( 621 ) to a second PSA ( 632 ) and a second ULCL/BP ( 622 ). Further, the SMF ( 650 ) determines an edge client subnet, ECS, associated with the second PSA ( 632 ). Further, the SMF ( 650 ) sends, to an application function, AF, ( 670 ) associated with the application client ( 611 ), a notification of the relocation. The notification includes an identifier of the ECS and a data network access identifier, DNAI, associated with the second PSA ( 632 ). From the AF ( 670 ), the SMF ( 650 ) receives a response that includes an identifier of a second EAS ( 682 ) and the DNAI associated with the second PSA ( 632 ). Based on the response, the SMF ( 650 ) establishes a second data path for the PDU session between the application client ( 611 ) and the second EAS ( 682 ) via the second PSA ( 632 ) and the second ULCL/BP ( 622 ).

Claims (52)

1. A method performed by a session management function (SMF) in a communication network, the method comprising:

determining that a first data path for a Packet Data Unit (PDU) session between an application client and a first edge application server (EAS) should be relocated from a first local PDU session anchor (PSA) and a first uplink classifier and branching point (ULCL/BP) to a second PSA and a second ULCL/BP;

determining an edge client subnet (ECS) associated with the second PSA;

sending, to an application function (AF) associated with the application client, a notification of the relocation, wherein the notification includes an identifier of the ECS and a data network access identifier (DNAI) associated with the second PSA;

receiving, from the AF, a response that includes an identifier of a second EAS and the DNAI associated with the second PSA; and

based on the response, establishing a second data path for the PDU session between the application client and the second EAS via the second PSA and the second ULCL/BP.

2. The method of claim 1 , wherein the DNAI has a value that indicates that the ECS is included in the notification and should be used by the AF to select the second EAS.

3. The method of claim 1 , further comprising sending, to the AF, an identifier of the second data path.

4. The method of claim 1 , further comprising:

initiating a timer upon establishing the second data path;

maintaining the first data path to the first EAS while the timer is running; and

removing the first data path to the first EAS upon expiration of the timer.

5. The method of claim 1 , wherein determining that the first data path should be relocated is based on a domain name service (DNS) query by the application client.

6. The method of claim 1 , wherein the first EAS and the second EAS are associated with respective first and second ranges of IP addresses, associated with an application server, that are managed together.

7. The method of claim 1 , wherein:

the notification is sent to the AF via a network exposure function (NEF) in the communication network; and

the response is received from the AF via the NEF.

8. A method performed by an application function (AF) in a communication network, the method comprising:

receiving, from a session management function (SMF) in the communication network, a notification of a relocation of a first data path, for a packet data Unit (PDU) session between an application client and a first edge application server (EAS) from a first local PDU session anchor (PSA) and a first uplink classifier and branching point (ULCL/BP) to a second PSA and a second ULCL/BP, wherein the notification includes:

an identifier of an edge client subnet (ECS) associated with the second PSA, and a data network access identifier (DNAI) associated with the second PSA;

determining a second EAS based on the ECS; and

sending, to the SMF, a response that includes an identifier of a second EAS and the DNAI associated with the second PSA.

9. The method of claim 8 , wherein the DNAI has a value that indicates that the ECS is included in the notification and should be used by the AF to select the second EAS.

10. The method of claim 8 , further comprising receiving, from the SMF, an identifier of the second data path.

11. The method of claim 8 , wherein:

determining the second EAS comprises sending a domain name service (DNS) query that includes the identifier of the ECS; and

the identifier of the second EAS includes an IP address of the second EAS received in response to the DNS query.

12. The method of claim 8 , wherein the first EAS and second EAS are associated with respective first and second ranges of IP addresses, associated with an application server, that are managed together.

13. The method claim 8 , wherein:

the notification is received from the SMF via a network exposure function (NEF) in the communication network; and

the response is sent to the SMF via the NEF.

14. A network node configured to operate as a session management function (SMF) in a communication network, the network node comprising:

interface circuitry configured to communicate with at least an application function (AF) associated with an application client; and

processing circuitry operably coupled to the interface circuitry, whereby the processing circuitry and the interface circuitry are configured to:

determine that a first data path for a Packet Data Unit (PDU) session between the application client and a first edge application server (EAS) should be relocated from a first local PDU session anchor (PSA) and a first uplink classifier and branching point (ULCL/BP) to a second PSA and a second ULCL/BP;

determine an edge client subnet (ECS) associated with the second PSA;

send, to the AF associated with the application client, a notification of the relocation, wherein the notification includes an identifier of the ECS and a data network access identifier (DNAI) associated with the second PSA;

receive, from the AF, a response that includes an identifier of a second EAS and the DNAI associated with the second PSA; and

based on the response, establish a second data path for the PDU session between the application client and the second EAS via the second PSA and the second ULCL/BP.

15. The network node of claim 14 , wherein the DNAI has a value that indicates that the ECS is included in the notification and should be used by the AF to select the second EAS.

16. The network node of claim 14 , wherein the processing circuitry and the interface circuitry are further configured to:

initiate a timer upon establishing the second data path;

maintain the first data path to the first EAS while the timer is running; and

remove the first data path to the first EAS upon expiration of the timer.

17. The network node of claim 14 , wherein the processing circuitry and the interface circuitry are configured to determine that the first data path should be relocated based on a domain name service (DNS) query by the application client.

18. The network node of claim 14 , wherein one or more of the following applies:

the first EAS and the second EAS are associated with respective first and second ranges of IP addresses, associated with an application server, that are managed together; and

the notification is sent to the AF via a network exposure function (NEF) in the communication network and the response is received from the AF via the NEF.

19. A network node configured to operate as an application function (AF) in a communication network, the network node comprising:

interface circuitry configured to communicate with at least a session management function (SMF) in the communication network; and

processing circuitry operably coupled to the interface circuitry, whereby the processing circuitry and the interface circuitry are configured to perform operations corresponding to the method of claim 8 .

20. The network node of claim 19 , wherein the DNAI has a value that indicates that the ECS is included in the notification and should be used by the AF to select the second EAS.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 14, 2022
From: MAS ROSIQUE, MARIA LUISA; MIHÁLY, ATTILA; BACKMAN, JAN
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 062089/0802 →
Continuity (2)
Provisional Application 63064161 · Aug 11, 2020
Related Publication 20230337056A1 · Oct 19, 2023
References Cited (18)
US 20180192390A1 · Li et al. · 2018 [cited by applicant]
“3GPP TR 23.748 V0.4.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of support for Edge Computing in 5G Core network (5GC) (Release 17), Jun. 2020… [cited by applicant]
“3GPP TS 23.501 V16.5.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16), Jul. 2020, pp. 1-441. [cited by applicant]
“3GPP TS 23.503 V15.5.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and Charging Control Framework for the 5G System; Stage 2 (Release 15), Mar. 2019, pp. 1-41. [cited by applicant]
“Client Subnet in DNS Queries”, Internet Engineering Task Force (IETF), Request for Comments: 7871, Category: Informational, ISSN: 2070-1721, May 2016, pp. 1-30. [cited by applicant]
“Domain names—Concepts and Facilities”, Network Working Group, Request for Comments: 1034, Obsoletes: RFCs 882, 883, 973, Nov. 1987, pp. 1-55. [cited by applicant]
“Domain names—Implementation and Specification”, Network Working Group, Request for Comments: 1035, Obsoletes: RFCs 882, 883, 973, Nov. 1987, pp. 1-55. [cited by applicant]
“Extension Mechanisms for DNS (EDNS(0))”, Internet Engineering Task Force (IETF), Request for Comments: 6891, STD: 75, Obsoletes: 2671, 2673, Category: Standards Track, ISSN: 2070-1721, Apr. 2013, pp. 1-16. [cited by applicant]
“KI#2, New sol: Service Continuity at Edge Relocation with DNS triggered insertion of BP/ULCL and Edge PSA”, 3GPP TSG-SA/WG2 Meeting #140E,S2-2004954, Electronic meeting, Aug. 19-Sep. 2, 2020, pp. 1-7. [cited by applicant]
“KI#2, New Solution: UE Agnostic EAS P address replacement for traffic subject to edge computing”, SA WG2 Temporary Document, S2-2004416, (revision of S2-2004314), SA WG2 Meeting #139E, Jun. 1-12, 2020, pp. 1-10. [cited by applicant]
“Solution for KI#2: Eas change with reducing packet loss”, SA WG2 Temporary Document, S2-2004118, (revision of S2˜200xxxx), 3GPP TSG-WG SA2 Meeting #139E e-meeting, Elbonia, Jun. 1-12, 2020, pp. 1-6. [cited by applicant]
“Solution for KI#2: Edge relocation based on MPTCP”, SA WG2 Temporary Document, S2-2004424, (revision of S2-20xxxx), SA WG2 Meeting #139, Elbonia, Jun. 13-17, 2020, pp. 1-8. [cited by applicant]
“3GPP TS 38.401 V15.6.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15), Jul. 2019, pp. 1-46. [cited by applicant]
“3GPP TR 38.801 V14.0.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on new radio access technology: Radio access architecture and interfaces (Release 14), Mar. 2017, p… [cited by applicant]
“3GPP TS 33.401 V15.8.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture (Release 15), Jun. 2019, pp. 1-163. [cited by applicant]
“3GPP TS 23.502 V15.5.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15), Mar. 2019, pp. 1-355. [cited by applicant]
“3GPP TS 23.501 V15.5.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15), Mar. 2019, pp. 1-241. [cited by applicant]
“ETSI TS 123 502 V16.5.0”, 5G; Procedures for the 5G System (5GS) (3GPP TS 23.502 version 16.5.0 Release 16), Jul. 2020, pp. 1-597. [cited by applicant]