Selection of edge application server

Abstract

The present disclosure relates to selection of edge application servers. Methods and apparatus are disclosed for selecting an edge application server (EAS) to serve a user equipment (UE). An example method includes determining that a current protocol data unit (PDU) session for an application being executed by a UE is being served by a first EAS, determining that the first EAS is no longer suitable to serve the application, selecting a second EAS to serve the application, and instructing the UE to use the second EAS for future PDU sessions of the application.

Description

Background Technology

[0001] Edge computing refers to performing computation and data processing at the network where the data is generated. This allows for performance optimization and minimized latency. Edge computing is a distributed approach where data processing is localized. In an edge computing infrastructure, edge application servers (EAS) can be deployed near the application site.

[0002] User equipment (UE) can connect to the first EAS based on, for example, the applications running on the UE and the UE's location. However, at a later time, there may be situations where the UE should no longer be able to connect to the first EAS. These situations may include, but are not limited to, EAS congestion, EAS being out of service, changes to the UE's Data Network Access Identifier (DNAI), changes to the UE's currently running applications, the UE moving from one location to another, and so on.

[0003] When these situations occur, it is necessary to determine whether the UE should switch from the first EAS to a different EAS and which different EAS the UE should switch to. Summary of the Invention

[0004] According to some exemplary embodiments, a method is performed by a first network component. The method includes: determining that an application being executed by a user equipment (UE) is being served by a first edge application server (EAS), determining that the first EAS is no longer suitable for serving the application, and selecting a second EAS to serve the application.

[0005] Another exemplary implementation includes a method performed at a cellular network. The method includes: determining that a current Protocol Data Unit (PDU) session of an application being executed by a User Equipment (UE) is being served by a first Edge Application Server (EAS); determining that the first EAS is no longer suitable to serve the application; selecting a second EAS to serve the application; and instructing the UE to use the second EAS for future PDU sessions of the application.

[0006] Other exemplary embodiments include a cellular network having multiple network components. A first network component is configured to determine that a current Protocol Data Unit (PDU) session of an application being executed by a User Equipment (UE) is being served by a first Edge Application Server (EAS), determine that the first EAS is no longer suitable for serving the application, and select a second EAS to serve the application. A second network component is configured to instruct the UE to use the second EAS for future PDU sessions of the application.

[0007] In another exemplary embodiment, the method is performed by a user equipment (UE). The method includes: receiving rules related to an access edge application server (EAS) from a network to which the UE is connected, wherein the rules include a minimum link quality for the connection between the UE and the EAS, monitoring the link quality of the connection between the UE and the EAS, and sending a message to the network to initiate an EAS relocation procedure when the link quality is lower than the minimum link quality defined in the rules. Attached Figure Description

[0008] Figure 1 Exemplary network arrangements according to various exemplary embodiments described herein are shown.

[0009] Figure 2A A first exemplary arrangement of an edge computing architecture according to various exemplary embodiments described herein is shown, the first exemplary arrangement including access to the edge application server (EAS) via an uplink (UL) classifier (CL) and a branch point (BP).

[0010] Figure 2B A second exemplary arrangement of an edge computing architecture according to various exemplary embodiments described herein is shown, which does not include access to EAS via UL CL / BP.

[0011] Figure 3 An exemplary signaling diagram is shown according to various exemplary implementations, illustrating an EAS relocation initiated by an application function (AF).

[0012] Figure 4 An exemplary signaling diagram is shown according to various exemplary implementations, illustrating an EAS relocation initiated based on UE input.

[0013] Figure 5 An exemplary signaling diagram is shown according to various exemplary implementations, illustrating the updating of UE routing policy (URSP) rules for active PDU sessions during EAS relocation.

[0014] Figure 6 An exemplary signaling diagram is shown according to various exemplary embodiments, illustrating EAS relocation assisted by application function (AF).

[0015] Figure 7 An exemplary signaling diagram according to various exemplary embodiments is shown, illustrating the ability of AF to determine EAS-assisted EAS relocation.

[0016] Figure 8 Exemplary user equipment (UE) according to various exemplary embodiments are shown. Detailed Implementation

[0017] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. The exemplary embodiments describe various exemplary implementations for determining whether an Edge Application Server (EAS) relocation should be performed and, if so, selecting a new EAS.

[0018] The exemplary embodiments are described with respect to the UE. However, reference to the UE is provided for illustrative purposes only. The exemplary embodiments can be used with any electronic component capable of establishing a connection to a network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any electronic component.

[0019] Furthermore, exemplary embodiments are described with reference to 5G New Radio (NR) cellular networks. However, the reference to 5G NR networks is provided for illustrative purposes only. Exemplary embodiments can be used with any network that implements the functionality for edge computing described herein. Therefore, a 5G NR network as described herein can represent any network that includes functionality associated with edge computing.

[0020] Figure 1 A network arrangement 100 according to an exemplary embodiment is illustrated. Network arrangement 100 includes a UE 110. Those skilled in the art will understand that the UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet, smartphone, phablet, embedded device, wearable device, Cat-M device, Cat-M1 device, MTC device, eMTC device, other types of Internet of Things (IoT) devices, etc. A practical network arrangement may include any number of UEs used by any number of users. Therefore, the example of a single UE 110 is provided merely for illustrative purposes.

[0021] UE 110 can communicate with one or more networks. In the example of network configuration 100, the networks with which UE 110 can wirelessly communicate are 5G New Radio (NR) Radio Access Network (5G NR-RAN) 120, LTE Radio Access Network (LTE-RAN) 122, and Wireless Local Area Network (WLAN) 124. However, UE 110 can also communicate with other types of networks, and UE 110 can also communicate with networks via wired connections. Therefore, UE 110 may include a 5G NR chipset communicating with 5G NR-RAN 120, an LTE chipset communicating with LTE-RAN 122, and an ISM chipset communicating with WLAN 124.

[0022] 5G NR-RAN 120 and LTE-RAN 122 can be parts of cellular networks that can be deployed by cellular providers (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). These networks 120, 122 can include, for example, base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 can include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.). Further details of 5G NR-RAN 120 are provided below.

[0023] The base station (e.g., gNB 120A, eNB 122A) may include one or more communication interfaces to exchange data and / or information with the pre-occupied UE, the corresponding RAN, the cellular core network 130, the Internet 140, etc. Those skilled in the art will understand that any association procedure can be performed for UE 110 to connect to the 5G NR-RAN 120. For example, as described above, the 5G NR-RAN 120 can be associated with a specific cellular service provider, where UE 110 and / or its user have protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, UE 110 may transmit the corresponding credential information to associate with the 5G NR-RAN 120. More specifically, UE 110 may be associated with a specific cell (e.g., gNB 120A of the 5G NR-RAN 120). As described above, the use of the 5G NR-RAN 120 is for illustrative purposes and any type of network can be used.

[0024] In addition to networks 120, 122, and 124, network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 can be viewed as an interconnected set of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network services backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 can generally be described as a set of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0025] Figure 2A A first exemplary architectural arrangement 200 of an edge computing architecture according to various exemplary embodiments described herein is illustrated. This first exemplary architectural arrangement includes access to an edge application server (EAS) via an uplink (UL) classifier (CL) and a branch point (BP). A general overview of the various components of the exemplary architectural arrangement 200 will be provided below. However, in describing the exemplary embodiments, specific operations performed by the components with respect to the exemplary embodiments will be described in more detail below. It should also be understood that the components of the exemplary architectural arrangement 200 may reside as described above with respect to the exemplary embodiments. Figure 1 The various physical and / or virtual locations mentioned above. These locations may include within the access network (e.g., within 5G NR-RAN 120), within the core network 130, and as per [the context of] [other locations]. Figure 1 Individual components other than those mentioned above.

[0026] In addition, Figure 2A In this document, various components are shown connected via connections labeled Nx (e.g., N1, N2, N3, N6, N9, etc.). Those skilled in the art will understand that each of these connections (or interfaces) is defined in the 3GPP specification. Exemplary architecture 200 uses these connections in the manner defined in the 3GPP specification. Furthermore, while these interfaces are referred to as connections throughout the specification, it should be understood that these interfaces do not need to be direct wired or wireless connections; that is, these interfaces can communicate via intermediate hardware and / or software components. For example, UE 110 exchanges communication with gNB 120A. However, in architecture 200, UE 110 is shown having a connection to Access and Mobility Management Function (AMF) 230 within core network 130. This connection or interface is not a direct communication link between UE 110 and AMF 230, but rather a connection facilitated by intermediate hardware and software components. Therefore, throughout the specification, the terms “connection” and “interface” are used interchangeably to describe the Nx interfaces between various components.

[0027] Architecture 200 includes a UE 110 and an access network (AN) 120 (e.g., 5G NR-RAN 120). AN 120 is connected to a first User Plane Function (UPF) 205. UPF 205 performs various functions within the core network 130, including packet routing and forwarding. In this example, UPF 205 includes UL CL / BP functions. Generally, UL CL functions may refer to providing destination-based multihoming for load balancing, while BP may refer to forwarding UL traffic to different PDU Session Anchors (PSAs). The first UPF 205 is also connected to a second UPF 210 and a third UPF 215. The second UPF 210 and the third UPF 215 include PSA functions. The third UPF 215 is connected to a data network (DN) 220.

[0028] In this exemplary embodiment, the second UPF 210 is connected to the local EAS 225. Those skilled in the art will understand that EAS 225 may include one or more EASs, as will be described in more detail below. Furthermore, those skilled in the art will understand that the network may include one or more additional UPFs (not shown), each connected to one or more additional EASs (not shown).

[0029] In addition to the connections described above, UE 110 and AN 120 can also connect to AMF 230. AMF 230 is typically responsible for mobility management in 5G NR-RAN 120. For example, AMF 230 can manage handover between gNBs. UPF 205-215 may also include a connection to Session Management Function (SMF) 235. SMF 2325 is typically responsible for creating, updating, and removing Protocol Data Unit (PDU) sessions for the UE.

[0030] The exemplary architecture 200 also includes a Network Exposure Function (NEF) 240. NEF 240 is typically responsible for securely exposing the services and capabilities provided by the 5G NR-RAN 120 network functions. The exemplary architecture 200 also includes a Location Computation Function (PCF) 245. PCF 245 is typically responsible for determining the location of UE 110. The exemplary architecture 200 also includes an Application Function (AF) 250. AF 250 can be considered as a logical element that provides session-related information.

[0031] Figure 2B A second exemplary architectural arrangement 260 of an edge computing architecture according to various exemplary embodiments described herein is shown, which does not include access to EAS via UL CL / BP. Therefore, in this exemplary architectural arrangement 260, there is no UPF (e.g., including UL CL / BP functionality). Figure 2A(UPF 205). In exemplary architecture arrangement 260, AN 120 is connected to UPF 270, which includes PSA functionality. UPF 270 is connected to DN 275, which includes EAS 280. Similar to architecture arrangement 200, those skilled in the art will understand that DN 275 may include one or more EAS 280s, and the network may include one or more additional UPFs (not shown), each UPF connected to one or more additional DNs having one or more EASs (not shown). The remaining components are the same as described with respect to architecture arrangement 200 and will not be described further.

[0032] Refer to each Figure 2A and Figure 2B The arrangements 200 and 260 shown and described are intended to provide two exemplary arrangements in which an edge computing architecture for implementing exemplary embodiments can be achieved. However, it should be understood that other edge computing architectures may exist that can be implemented with the exemplary embodiments. Furthermore, as described above, with... Figure 2A and Figure 2B The related descriptions are intended only to provide a general overview of the components in various arrangements. Exemplary operations performed by the components in implementing exemplary embodiments will be provided below.

[0033] Figure 3 An exemplary signaling diagram 300 is shown according to various exemplary embodiments, illustrating an EAS relocation initiated by an application function (AF). Reference will be made separately to... Figure 1 Network layout 100 and Figure 2A and Figure 2B The architecture layout is described using 200 and 260. Figure 3 In this exemplary implementation, the AF initiates a process to change the UE's EAS.

[0034] In discussion Figure 3 Before the signaling, the specific components that perform the signaling will be described. Starting from the left, a general description of UE 110, AMF 230, SMF 235, PCF 245, and AF 250 has been provided above, and these components are substantially the same in terms of architecture arrangements 200 and 260. In this exemplary embodiment, the UPF is labeled as UPF 210 connected to architecture arrangement 200 of EAS 225. However, the UPF could also be UPF 270 connected to architecture arrangement 260, which includes DN 275 of EAS. That is, with respect to this exemplary embodiment, the operations and signaling described with respect to signaling figure 300 can be performed within architecture arrangement 200, architecture arrangement 260, or any other edge computing architecture that can implement the exemplary embodiment.

[0035] In this example, there are two EASs, namely EAS 225a and EAS 225b. EAS 225a can be considered the EAS currently connected to UE 110, and EAS 225b is the target EAS. Again, for consistency with the example at the beginning above, the EASs are labeled with the reference numerals associated with architecture arrangement 200. However, as mentioned above, the exemplary implementation also applies to architecture arrangement 260, and may have been labeled with the reference numerals for that architecture.

[0036] Furthermore, throughout the description of signaling diagram 300 and the other signaling diagrams described herein, messages transmitted between various components can be labeled with specific message names / types. For example, in signaling diagram 300, the message name / type Namf_Communication_N1N2 is used to transmit UE configuration update commands. The information carried by these messages and their functions are described in the description. Therefore, although references to specific message names / types are made, it should be understood that any message name / type can be used to convey the information and functions described herein.

[0037] In 305, UE 110 is shown registering with 5G NR-RAN 120. As part of this registration, details of the EAS (e.g., EAS 225a) to which UE 110 should connect may be shared with UE 110 via UE Routing Policy (URSP) rules. URSP rules typically inform UE 110 about information related to services and / or applications. This information may include rules that can be used to determine the identity of the EAS to which UE 110 should use. For example, UE 110 may be executing an application, and the URSP rules may indicate the EAS that UE 110 should connect to while executing the application. Those skilled in the art will understand that multiple factors / rules may exist to be evaluated to determine the EAS to which UE 110 will connect. For example, in addition to the application, the USRP rules may also include rules regarding the location of UE 110 when selecting an EAS. In another exemplary embodiment, the EAS to which UE 110 should connect may be shared via Domain Name System (DNS) resolution. For example, when UE 110 connects to a specific domain, that domain may indicate that UE 110 should connect to the EAS that interacts with that domain. In any case, at 305, UE 110 can be considered to be currently connected to EAS 225a.

[0038] In 310, AF 250 can determine that the EAS of UE 110 should be changed from EAS 225a to EAS 225b. Figure 3In the example, UE 110 indicates that the change is due to the application changing the EAS server provider from EAS 225a to EAS 225b. However, other reasons may exist to initiate an EAS change. For example, EAS 225a may experience congestion or outages, or it may undergo periodic maintenance. In one exemplary implementation, UE 110 may provide feedback to AF 250 indicating that it is currently receiving service from EAS 225a. AF 250 can use this feedback to determine whether the EAS is experiencing any conditions that warrant a change in EAS. In another exemplary implementation, EAS 225a may provide AF 250 with periodic feedback (e.g., every 3-5 minutes) regarding the status of EAS 225a (e.g., congestion). Therefore, it should be understood that AF 250 may initiate an EAS change for any reason defined as a reason for changing the EAS.

[0039] In 315, AF 250 may send a notification to PCF 245 that the server credentials for the application should change (e.g., from EAS 225a to EAS 225b). The EAS change may involve a single UE (e.g., UE 110) or a group of UEs (e.g., UEs currently executing the considered application). In 320, PCF 245 may forward the new URSP rule to AMF 230. In this example, the new USRP rule may be forwarded via the Namf_Communication_N1N2 message transmission. However, the exemplary implementation is not limited to this type of message.

[0040] In step 325, AMF 230 may send a UE configuration update command to UE 110. The update command will include new USRP rules and may also include the IP address of the new EAS (e.g., EAS 225b). In step 330, UE 110 may send a UE configuration update complete message to AMF 230, indicating that UE 110 is now configured with updated URSP rules regarding the new EAS. In step 335, AMF 230 may notify PCF 245 that UE 110 has updated using the new URSP rules regarding the changes to the EAS. In this example, the notification may be provided via Namf_N1MessageNotify. However, the exemplary implementation is not limited to this type of message.

[0041] Therefore, in Figure 3 In the exemplary signaling diagram 300, AF 250 is the component that initiates a change to the EAS of UE 110. The operation of signaling diagram 300 can be used to initiate changes to the EAS for future PDU sessions (e.g., PDU sessions established after an EAS relocation has occurred). The following will discuss... Figure 5Provide more detailed examples of operations related to the current PDU session.

[0042] Figure 4 An exemplary signaling diagram 400 is shown according to various exemplary embodiments, illustrating an EAS relocation initiated based on UE input. Reference will be made separately to… Figure 1 Network layout 100 and Figure 2A and Figure 2B The architecture layout is described using 200 and 260. Figure 4 In this exemplary implementation, EAS relocation is initiated based on input received from UE 110.

[0043] The components shown in signaling diagram 400 are the same as those shown in signaling diagram 300, including UE110, AMF 230, SMF 235, PCF 245, UPF 210, current EAS 225a, target EAS 225b, and AF 250, starting from the left. A general description of these components has been provided above, and they will not be described again except for exemplary operations performed by these components in signaling diagram 400. Similarly, although some components are labeled with reference numerals related to architecture arrangement 200, exemplary embodiments can also be implemented in architecture arrangement 260.

[0044] In 405, it is shown that UE 110 registers with 5G NR-RAN 120, and it can be assumed that UE 110 is currently connected to EAS 225a based on the URSP rules currently configured for UE 110. The operation of 405 is similar to the operation of 305 in signaling diagram 300, and will not be described again.

[0045] In 410, UE 110 may send periodic measurement information to AF 250. This measurement information relates to the connection between UE 110 and the current EAS 225a. In one exemplary embodiment, the measurement information includes the average, minimum, and maximum round-trip time (RTT) of packets to be received from EAS 225a within a specific time window. However, UE 110 may send other types of measurement information to AF 250 regarding the connection between UE 110 and EAS 225a.

[0046] In step 415, AF 250 evaluates the measurement data received from UE 110 to determine whether the EAS of UE 110 should be switched. In an exemplary implementation where the measurement data includes RTT data, AF 250 may determine whether the RTT data indicates that the Quality of Service (QoS) guaranteed for UE 110 can be met. If the measurement data indicates that the QoS cannot be met, AF 250 may then initiate a change to the EAS of UE 110 (e.g., from EAS 225a to EAS 225b).

[0047] If a change is initiated, in step 420, AF 250 may send a notification to PCF 245 that UE 110's server credentials should be changed (e.g., from EAS 225a to EAS 225b). In step 425, PCF 245 may forward the new URSP rules to AMF 230. In step 430, AMF 230 may send a UE configuration update command to UE 110. The UE configuration update command will include the new USRP rules and may also include the IP address of the new EAS (e.g., EAS 225b). In step 435, UE 110 may send a UE configuration update complete message to AMF 230, indicating that UE 110 is now configured with updated URSP rules regarding the new EAS. In step 440, AMF 230 may notify PCF 245 that UE 110 has updated using the new URSP rules regarding the change to the EAS. A brief description of the operations associated with signaling 420-440 is provided, as these operations are generally similar to those associated with... Figure 3 The corresponding operations associated with signaling 315-335.

[0048] Therefore, in Figure 3 In the exemplary signaling diagram 400, regarding the connection between UE 110 and the current EAS 225a, UE 110 provides feedback to AF 250 in the form of measurement data. AF 250 then determines whether to initiate a change to UE 110's EAS based on this measurement data. Similar to the operation of signaling diagram 300, the operation of signaling diagram 400 can be used to initiate changes to the EAS for future PDU sessions (e.g., PDU sessions established after EAS relocation has occurred). The following will discuss... Figure 5 Provide more detailed examples of operations related to the current PDU session.

[0049] Figure 5 An exemplary signaling diagram 500 is shown according to various exemplary embodiments, illustrating the updating of UE routing policy (URSP) rules for active PDU sessions during EAS relocation. Reference will be made separately to... Figure 1 Network layout 100 and Figure 2A and Figure 2B The architecture layout is described using 200 and 260. Figure 5As described above, signaling diagrams 300 and 400 relate to operations that may be more suitable for future PDU sessions regarding EAS relocation. Signaling diagram 500 describes the operations and signaling that may be related to the currently active PDU session during EAS relocation. In this exemplary embodiment, URSP rules related to the active PDU session may be updated during EAS relocation. Similarly, although some components are labeled with reference numerals related to architecture layout 200, the exemplary embodiment can also be implemented in architecture layout 260.

[0050] The components shown in signaling diagram 500 are the same as those shown in signaling diagrams 300 and 400, including UE 110, AMF 230, SMF 235, PCF 245, UPF 210, current EAS 225a, target EAS 225b, and AF 250, starting from the left. A general description of these components has been provided above, and they will not be described further except for exemplary operations performed by these components in signaling diagram 500.

[0051] The operations and signaling associated with 505-535 are generally the same as those associated with 305-335 in signaling diagram 300 and will not be repeated. However, it should be understood that these operations and signaling 505-535 will generally have the same results as described above for 305-335, for example, future PDU sessions of UE 110 will be served by the new EAS 225b.

[0052] However, in addition to considering future PDU sessions, signaling diagram 500 also considers the current PDU session. When PCF 245 receives the updated URSP rules in 515, PCF 245 can also use EAS 225a to determine whether UE 110 has a currently active PDU session. If a currently active PDU session exists, then in 540, PCF 245 can send the updated URSP rules to SMF 235. In 545, SMF 235 can send the updated URSP rules to UE 110 via a PDU session modification command that includes the IP address of the new EAS (e.g., EAS 225b).

[0053] In step 550, the currently active PDU session is pushed from the current EAS 225a to the new EAS 225b. When the modification is complete, for example, when the current PDU session has moved from EAS 225a to EAS 225b, in step 555, UE 110 can send a message to SMF 235 to indicate that the session modification is complete. In step 560, SMF 235 can then report to PCF 245 that UE 110's session modification is complete.

[0054] In this exemplary implementation, because SMF 235 has sent a PDU session modification command, the current PDU session can be modified to switch the current PDU session from EAS 225a to EAS 225b. Therefore, when signaling diagram 500 is completed, UE 110 has switched the current PDU session and any future PDU sessions to the new EAS 225b.

[0055] Figure 6 An exemplary signaling diagram 600 is shown according to various exemplary embodiments, illustrating application function (AF)-assisted EAS relocation. Reference will be made separately to… Figure 1 Network layout 100 and Figure 2A and Figure 2B The architecture layout is described using 200 and 260. Figure 6 In this exemplary implementation, AF facilitates the process of changing the UE's EAS.

[0056] In discussion Figure 6 Before the signaling diagram, the specific components performing the signaling will be listed. Starting from the left, general descriptions of UE 110, AF250, NEF 240, and SMF 235 have been provided above and will not be repeated. Unlike the previous examples, this signaling diagram is labeled with reference numerals related to architecture arrangement 260 to illustrate that the exemplary implementation described herein can be implemented in any architecture arrangement of the edge computing network. When describing architecture arrangement 260 above, it is described that UPF 270 can be one or more UPFs, where each UPF is connected to a DN with one or more EASs. Therefore, in this exemplary implementation, it can be assumed that there are two UPFs, namely UPF / PSA1 270a and UPF / PSA2 270a, each of which is connected to a separate DN with an EAS, namely DN1 / EAS1 280a and DN2 / EAS2 280b. It can be considered that UE 110 is initially connected to UPF / PSA1 270a and the corresponding DN1 / EAS1 280a. UPF / PSA2 270b and the corresponding DN2 / EAS2 280b can be considered as targets. Therefore, in this exemplary embodiment, the current EAS can be considered part of a first data network, and the target EAS can be considered part of a second data network. However, this is not mandatory. The current EAS and the target EAS can be part of the same data network.

[0057] In step 605, UE 110 may register with 5G NR-RAN 120 and is currently connected to DN1 / EAS1 280a based on the URSP rules currently configured for UE 110. The operation of step 605 is similar to that of step 305 in signaling diagram 300 and will not be described further. It is also possible that the latency requirements for packets between UE 110 and DN1 / EAS1 280a are currently met. In step 610, periodic latency measurements or RTTs are performed between UE 110, UPF / PSA1 270a, and DN1 / EAS1 280a for the currently executing application. In one exemplary implementation, periodic latency measurements are performed on the N6 connection between UPF / PSA1 270a and DN1 / EAS1 280a. However, other latency measurements may also be performed. These latency measurements may be reported to the current UPF / PSA1270a.

[0058] At point 615, a link problem can be considered to exist in DN1 / EAS1 280a, as identified by delay measurements reported to UPF / PSA1 270a. As mentioned above, many types of problems exist that can be characterized as link problems, such as congestion, overload, quality monitoring, maintenance, etc. Again, the exact problem with DN1 / EAS1 280a is not relevant; the only relevant factor is that UPF / PSA1270a has identified a problem with the current link. At point 620, UPF / PSA1 270a will notify SMF 235 of the abnormal condition of the DN1 / EAS1280a link.

[0059] In step 625, SMF 235 sends a monitoring request to NEF 240, and then in step 630, an event exposure request related to the monitoring request is sent to AF 250. As mentioned above, NEF 240 is typically responsible for securely exposing services and capabilities. Therefore, event exposure is one of the functions provided by NEF 240. The monitoring request is another available EAS for determining whether there is a UE 110 available for currently running applications.

[0060] Therefore, in 635, in response to a monitoring request exposed by NEF 240, AF 250 will monitor the service link from UPF to EAS via NEF 240 and SMF 235. In the example of signaling diagram 600, this monitoring is shown as monitoring the available service link 640 between UPF / PSA2 270b and the corresponding DN2 / EAS2 280b. However, those skilled in the art will understand that monitoring can include any number of UPF to EAS service links to identify acceptable candidates for EAS relocation. Monitoring can include the same type of latency measurement described for the current UPF / PSA1 270a to DN1 / EAS1 280a service link. In some exemplary embodiments, monitoring can be processed via Nnef / Nsmf / N4 data requests, for example, latency measurements can be performed based on data requests. In 645, the link state report of the service link from UPF / PSA2270b to DN2 / EAS2 280b is reported to AF 250 via SMF 235 and NEF240.

[0061] It can be assumed that the service link from UPF / PSA2 270b to DN2 / EAS2 280b is acceptable for the currently executing application of UE 110. Therefore, in 650, a data notification buffer request is exchanged between SMF 235 and the target UPF / PSA2 270b. The purpose of the buffer request is to store the application state between the current UPF / PSA1 270a and DN1 / EAS1 280a for the service continuity of the executing application, as shown in 655.

[0062] In step 660, AF 250 sends a request to SMF 235 for EAS relocation from the current DN1 / EAS1 280a to the target DN2 / EAS2 280b. As described above, because link monitoring exists in this exemplary embodiment, this request may include the movement of data traffic and continuous monitoring of the service link from the target UPF / PSA2270b to DN2 / EAS2 280b. In step 665, SMF 235 sends a message to AF 250 accepting the relocation request, and in step 670, SMF 235 notifies NEF 240 of traffic updates.

[0063] In message 675, UPF / PSA2 270b notifies SMF 235 of the update policy related to the new UPF. Message 675 is similar to message 540 as described in reference signaling diagram 500. SMF 235 can then send PDU session modification 680 to UE 110 in message 680. PDU session modification 680 is similar to PDU session modification message 545 as described in reference signaling diagram 500. Therefore, similar to signaling diagram 500, signaling diagram 600 relates to changing the current PDU session of the application.

[0064] Because the application state is buffered in 655, when data communication resumes in 685, the application's data traffic can be recovered from its previous state within the application. In 690, the application synchronizes with the target DN2 / EAS2 280b, and monitoring of the service link from UPF / PSA2 270b to DN2 / EAS2 280b continues for the duration of the application's execution within the DN2 / EAS2 280b of the EAS.

[0065] Therefore, in Figure 6 In the exemplary signaling diagram 600, AF 250 assists in EAS relocation. This assistance is based on latency measurements between the UE, UPF, and EAS. When the latency measurement indicates a problem with the current EAS service link, the AF monitors other available service links and selects the appropriate link to serve the UE's currently executing application. In this exemplary implementation, EAS relocation can be performed for the current PDU session.

[0066] Figure 7 An exemplary signaling diagram 700 is shown according to various exemplary embodiments, illustrating the capability of AF 250 to determine EAS 225 assisted EAS relocation. Similarly, although components are labeled with reference numerals associated with architecture arrangement 200, exemplary embodiments may also be implemented in architecture arrangement 260.

[0067] In several examples provided above, AF 250 determines or assists in EAS relocation. Signaling diagram 700 can be used to assist AF 250 in determining whether an EAS is a candidate for EAS relocation. For example, not all EASs have the hardware and / or software capabilities to be used as an EAS for a specific application running on UE 110. Examples of application types that may require very high processing power and throughput could be virtual reality (VR) or augmented reality (AR) applications. Signaling diagram 700 allows AF 250 to poll EASs to determine whether a single EAS meets the hardware and / or software capabilities of the currently running application.

[0068] In step 705, AF 250 sends an EAS capability query to EAS 225. The EAS capability query 705 may include a general query for EAS 225 to provide all capabilities, or it may include a specific request for one or more capabilities related to the currently executing application. In step 710, EAS 225 responds with EAS capability information to AF 250. AF 250 can then determine whether EAS 225 is a candidate EAS for EAS relocation based on the capabilities required by the executing application. Those skilled in the art will understand that... Figure 7 Signaling can be performed between the AF 250 and any number of available EAS.

[0069] Tables 6.6.2.1-1, 6.6.2.1-2, and 6.6.2.1-3 in version 15.8.0 of 3GPP standard TS 23.503 describe the structure of URSP rules. Exemplary URSP rules that can be added to existing URSP rules are described below. The purpose of the exemplary rules is to guarantee the QoS of EAS. Guaranteeing QoS can be achieved by defining a minimum link quality metric for the routing validation standard. For example, if such a URSP rule is implemented, the UE can determine, based on RTT measurements, that the minimum link quality metric is not met. Therefore, due to the violation of the URSP rule, the UE can request the AF to initiate an EAS relocation. In another exemplary implementation, the UE can provide periodic link quality measurements to any network component (e.g., UPF, SMF, PCF, AF, etc.), and then, if necessary, the network component can initiate an EAS relocation based on the link quality measurements.

[0070] Figure 8 An exemplary user equipment (UE) 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1 The network layout 100 is used to describe UE 110. UE 110 can represent any electronic device and may include a processor 805, a memory layout 810, a display device 815, an input / output (I / O) device 820, a transceiver 825, and other components 830. Other components 830 may include, for example, a SIM card, an embedded SIM (eSIM), an audio input device, an audio output device, a battery providing a limited power source, a data acquisition device, ports for electrically connecting UE 110 to other electronic devices, etc.

[0071] Processor 805 can be configured to execute multiple engines for UE 110. For example, an engine may include a Link Quality Metric (LQM) engine 835. The LQM engine 835 can manage this when UE 110 requests EAS relocation from the network (e.g., 5G NR-RAN 120). As described above, the network can provide UE 110 with one or a set of rules (e.g., URSP rules) regarding EAS operation. One of these rules may include a minimum link quality for EAS connections. UE 110 can monitor the link quality, and when the link quality drops below the minimum link quality (e.g., a rule violation), UE 110 can send a request for EAS relocation to the network. This is the function of UE 110's LQM engine 835.

[0072] The engines described above, each acting as an application (e.g., a program) executed by processor 805, are merely exemplary. The functionality associated with the engines may also be represented as a separate, integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Engines may also be embodied as a single application or multiple separate applications. Furthermore, in some UEs, the functionality described for processor 805 is distributed among two or more processors (such as a baseband processor and an application processor). Exemplary implementations can be implemented according to any of these or other configurations of the UE.

[0073] Memory arrangement 810 may be a hardware component configured to store data related to operations performed by UE 110. Display device 815 may be a hardware component configured to display data to a user, while I / O device 820 may be a hardware component enabling user input. Display device 815 and I / O device 820 may be separate components or may be integrated together (such as a touchscreen). Transceiver 825 may be a hardware component configured to establish connections with 5G NR-RAN 120, WLAN 122, etc. Therefore, transceiver 825 may operate on multiple different frequencies or channels (e.g., a set of consecutive frequencies).

[0074] Various exemplary implementations of the EAS relocation scenarios described above. As mentioned above, some of these scenarios include AF-assisted EAS relocation. Besides the examples provided above, other scenarios for AF-assisted EAS relocation may exist. In the first example, the AF may notify the currently running application that its EAS provider has changed. In the second example, the AF may notify the 5G NR-RAN, based on a geographic region, that the EAS of one or more UEs has changed, and the 5G NR-RAN can then notify the UE of the new EAS. Many other scenarios related to EAS relocation may exist, as these are only provided as examples.

[0075] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of an embodiment can be combined with features of other embodiments or features that are not functionally or logically inconsistent with the operation or function of the device of the disclosed embodiment of the invention in any manner not explicitly denied.

[0076] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. In other examples, exemplary embodiments of the methods described above may be embodied as programs comprising lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0077] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0078] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A method for communication, comprising: By applying function AF: It is determined that the application being executed by the user equipment (UE) is being served by the first edge application server (EAS). Determine that the first EAS is no longer suitable for serving the application, wherein the determination that the first EAS is no longer suitable for serving the application is based on receiving a notification from the Session Management Function (SMF); as well as A request is transmitted to the Position Calculation Function (PCF), wherein the request is configured to trigger an EAS relocation of the UE from the first EAS to the second EAS.

2. A method for communication, comprising: At the cellular network: The application function AF determines that the current Protocol Data Unit (PDU) session of the application being executed by the user equipment UE is being served by the First Edge Application Server (EAS). The AF determines that the first EAS is no longer suitable for serving the application, wherein the determination that the first EAS is no longer suitable for serving the application is based on receiving a notification from the Session Management Function (SMF). The AF transmits a request to the Positioning Calculation Function (PCF), wherein the request is configured to trigger the UE to relocate from the first EAS to the second EAS. as well as The UE is instructed to use the second EAS for future PDU sessions of the application.

3. The method according to claim 2, further comprising: The instruction to the UE to update the current PDU session to use the second EAS is based on at least two different messages sent to the UE.

4. The method of claim 2, wherein the indication is based on a message including one of: a rule for accessing EAS, or a message for updating the EAS IP address.

5. The method of claim 2, wherein determining that the first EAS is no longer suitable for serving the application includes monitoring a first service link of the first EAS in the cellular network.

6. The method of claim 5, wherein the selection of the second EAS is based at least on at least a second service link of the second EAS monitored in the cellular network.

7. The method according to claim 2, further comprising: The application state is buffered between the application and the first EAS.

8. The method according to claim 7, further comprising: The application's PDU session is served via the second EAS, wherein the switching from the first EAS to the second EAS is based at least on the buffered application state.

9. A cellular network system, comprising: An application function AF is configured to determine that the current Protocol Data Unit (PDU) session of an application being executed by a User Equipment (UE) is being served by a first Edge Application Server (EAS), determine that the first EAS is no longer suitable for serving the application, and transmit a request to a Location Computing Function (PCF), wherein the determination that the first EAS is no longer suitable for serving the application is based on receiving a notification from a Session Management Function (SMF), and wherein the request is configured to trigger an EAS relocation of the UE from the first EAS to a second EAS.

10. The cellular network system of claim 9, wherein the AF determines that the first EAS is no longer suitable to serve the application based on monitoring information received in relation to a first service link to the first EAS in the cellular network system.

11. The cellular network system of claim 9, wherein the AF selects the second EAS based at least on monitoring information related to a second service link to the second EAS in the cellular network system.

12. The cellular network system according to claim 9, further comprising: A buffer is provided for storing application state between the application and the first EAS, wherein the PDU session of the application served via the second EAS is based at least on the stored application state.

Images