Method and apparatus for selecting a target edge application server in an edge computing environment

Abstract

The present disclosure relates to a communication technology and system thereof for supporting the integration of a fifth generation (5G) communication system with a higher data rate than a fourth generation (4G) system and an Internet of Things (IoT) technology. The present disclosure can be applied to intelligent services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, security and safety services. A method for selecting a target edge application server for a user equipment (UE) in an edge computing system, which is performed by a source edge enabler server, is provided. The method includes: receiving a selection criterion for selecting a target edge application server from an edge enabler client in a UE; determining a need for an application context transfer by an application client in the UE; selecting a target edge application server for application context transfer based on the selection criterion received from the edge enabler client; and sending a notification about the selected target edge application server to the edge enabler client.

Description

Technical Field

[0001] The present disclosure relates to edge computing, and more particularly, to a method and user equipment (UE) for selecting a target edge application server (EAS) for service continuity in an edge computing environment. Background Art

[0002] In order to meet the increasing demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (mmWave) bands such as the 60GHz band to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology in 5G communication systems are discussed. In addition, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), and receiving-end interference elimination. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet is a human-centered connectivity network where humans generate and consume information, and is now evolving into the Internet of Things (IoT), where distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) is the Internet where IoT technology is combined with big data processing technology through connection with a cloud server. In order to realize the IoT, technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology" are required, and sensor networks, machine-to-machine (M2M) communication, machine-type communication (MTC), etc. have been studied recently. This IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances, and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs) as the above-mentioned big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology.

[0005] In an edge computing environment, if the UE is moving, eventually the server that provides the best service to the UE will no longer be the best. This may be due to the change in the location of the UE causing the distance between the server and the UE to increase. In another case, the server may be overloaded or crashed, so that the server cannot meet the performance requirements of the application client in the UE. In this case, it is expected that the UE will switch from the current server, called the source server, to a new optimal server, called the target server. Summary of the invention

[0006] [Technical issues]

[0007] In densely deployed areas where multiple edge server options are available, multiple target servers that may be the optimal target server are available. Ideally, it would be the responsibility of the edge enabler client (EEC) in the UE to select the target server from the potential target servers, because it understands the preferences of the user and application clients in the UE that communicate with the target server. But there may be many entities for the edge enabling layer somewhere, including entities in the network or edge that can detect service continuity requirements. In this case, it is not obvious how to select the target server while taking into account the preferences of the user and application and the performance requirements (key performance indicators, KPIs).

[0008] [Technical solution]

[0009] Therefore, an embodiment of the present invention includes a method for selecting a target edge application server (EAS) for a user equipment (UE) in an edge computing system, the method comprising: sending, by an edge enabler client (EEC) in the UE, selection criteria for an application client in the UE to a source edge enabler server (EES) for selecting the target EAS; determining, by the source edge enabler server, a need for application context transfer by the application client in the UE; selecting, by the source edge enabler server (EES), a target edge application server for application context transfer based on the selection criteria received from the edge enabler client; and sending, by the source edge enabler server (EES), a notification to the edge enabler client regarding the selected target edge application server and a target edge enabler server associated with the target edge application server.

[0010] In some embodiments, determining, by a source edge enabler server (EES), a need for an edge enabler client for an application context transfer includes one of the following: monitoring, by the source edge enabler server (EES), a location change of the UE; receiving, by the source edge enabler server (EES), a request for a UE application context transfer from an edge application server (EAS); receiving, by the source edge enabler server (EES), a request for a UE application context transfer from an edge enabler client; and monitoring, by the source edge enabler server (EES), an overload condition in the source edge application server.

[0011] In another embodiment, the selection criteria are shared by the edge enabler client as part of the initial registration request to the source edge enabler server. In another embodiment, the selection criteria are shared by the edge enabler client as part of the edge application server discovery request to the edge enabler server.

[0012] In another embodiment, the selection criteria include one of an application client expected KPI and an application client minimum KPI. The expected KPI represents the expected performance of the application client receiving currently required services from the EAS; the minimum KPI represents the minimum performance that enables the client to receive meaningful services from the EAS.

[0013] In yet another embodiment, the selection criteria is related to a specific application or one of a plurality of applications at the UE.

[0014] In some embodiments, the method further includes: the edge enabler client sending a confirmation message to the source edge enabler server to trigger the application context transfer process; and the source edge enabler server initiating the application context transfer from the edge enabler client to the selected edge application server.

[0015] In some embodiments, the source edge enabler server selects a target edge application server for application context transfer based on a selection criterion, including: the source edge enabler server sends a request to an edge configuration server to determine a potential target edge application server that serves an edge application server required by an edge enabler client based on the selection criterion; in response to the request, the source edge enabler server receives a list of potential target edge application servers from the edge configuration server; the source edge enabler server (252a) sends a request to one of the received edge enabler servers (252) to determine a potential target edge application server (254) required by the edge enabler client (220) based on the selection criterion; in response to the request, the source edge enabler server (252) receives a list of potential target edge application servers (254) from at least one of the potential edge enabler servers (252); and the source edge enabler server selects a target edge application server for application context transfer from the received potential target edge application servers based on the selection criterion.

[0016] In yet another embodiment, the target edge application server is selected by an edge enabler client at the UE.

[0017] These and other aspects of the embodiments herein will be better understood and appreciated when the following description and drawings are considered in conjunction. However, it should be understood that the following description, although illustrating exemplary embodiments and many specific details thereof, is provided in an illustrative manner and is not restrictive. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit of the present disclosure, and the embodiments herein include all such modifications.

[0018] [Beneficial Effects]

[0019] According to the embodiments of the present disclosure, a target edge application server (EAS) may be effectively selected and service continuity may be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a sequence diagram illustrating an example of an edge enabler client (EEC) detecting a need for an application context transfer (ACT) and providing a target edge application server (EAS) to a source edge enabler server (EES) according to various embodiments of the present disclosure.

[0021] Figure 2 An example of a UE in an edge computing system according to certain embodiments disclosed herein is shown in a block diagram format, and wherein the UE provides selection criteria for searching for an optimal target server based on an ACT request.

[0022] Figure 3is a sequence diagram illustrating an example of a source edge enabler server requesting an edge enabler client to provide detailed information of a target edge application server according to some embodiments disclosed herein.

[0023] Figure 4 is a sequence diagram illustrating an example of a source edge enabler server providing a potential target list to an edge enabler client to select a target edge application server according to some embodiments disclosed herein.

[0024] Figure 5 is a sequence diagram illustrating an example in which an edge enabler server triggers an edge configuration server to send a service provision notification to an edge enabler client and then requests the edge enabler client to select a target edge application server according to some embodiments described herein.

[0025] Figure 6 is a sequence diagram illustrating an example of an edge enabler client configuring a target edge application server selection criterion in a source edge enabler server according to some embodiments disclosed herein.

[0026] Figure 7 is a signaling diagram illustrating an example of a source edge enabler server selecting a target edge application server based on selection criteria received from an edge enabler client according to some embodiments disclosed herein.

[0027] Figure 8 is a flow chart illustrating an exemplary method of selecting an optimal target edge application server based on selection criteria stored at an edge enabler server according to certain embodiments disclosed herein.

[0028] Fig. 9 is a block diagram illustrating a source edge enabler server according to certain embodiments of the present disclosure. DETAILED DESCRIPTION

[0029] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout the patent document: The terms "include" and "comprise" and their derivatives are intended to include without limitation. The term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean include, included within, interconnected with, include, included within, connected to or connected with, connected to or connected with, communicate with, cooperate with, interweave, juxtapose, be in proximity to, be bound to or bound with, have, have the characteristics of, etc.; and the term "controller" means any device, system, or part thereof that controls at least one operation; such a controller may be implemented in hardware, firmware, or software, or a combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether local or remote.

[0030] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and implemented in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, examples, related data or parts thereof that are suitable for implementation with suitable computer-readable program codes. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable medium excludes wired, wireless, optical or other communication links that transmit instantaneous electrical signals or other instantaneous signals. Non-transitory computer-readable media include media that can permanently store data, and media that can store data and then rewrite data, such as rewritable optical discs or erasable storage devices.

[0031] Definitions for certain words and phrases are provided throughout this patent document, those skilled in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0032] Discussed below Figures 1 to 9 The various embodiments used to describe the principles of the present disclosure in this patent document are merely illustrative and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0033] The embodiments of the present invention and their various features and advantageous details are more fully explained with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following specification. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily confuse the embodiments of the present invention. In addition, the various embodiments described herein are not necessarily mutually exclusive, and some embodiments may be combined with one or more other embodiments to form new embodiments. Unless otherwise specified, the term "or" used herein means a non-exclusive or. The examples used herein are intended only to facilitate understanding of the manner in which the embodiments of the present invention can be practiced, and further enable those skilled in the art to practice the embodiments of the present invention. Therefore, these examples should not be interpreted as limiting the scope of the embodiments of the present invention.

[0034] In the present disclosure, embodiments may be described and illustrated in terms of blocks that perform one or more functions described. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, storage circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware. For example, the circuit may be implemented in one or more semiconductor chips, or on a substrate support such as a printed circuit board. The circuits that constitute the blocks may be implemented by dedicated hardware or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware that performs some functions of the blocks and a processor that performs other functions of the blocks. Without departing from the scope of the present disclosure, each block of the embodiments may be physically divided into two or more interactively discrete blocks. Similarly, without departing from the scope of the present disclosure, the blocks of the embodiments may be physically combined into more complex blocks.

[0035] The accompanying drawings are used to help easily understand each technical feature, and it should be understood that the present disclosure is not limited by the accompanying drawings. Therefore, the present disclosure should be interpreted as extending to any changes, equivalent forms and alternative forms other than those specifically described in the accompanying drawings. Although the terms "first", "second" and the like may be used to describe various elements in this article, these elements should not be limited by these terms. These terms are usually only used to distinguish one element from another element.

[0036] Therefore, the embodiments of this document provide a different method and UE that considers user and application preferences and application client KPIs to select a target server in different scenarios. The KPI indicates the performance capacity of the server, such as the storage space available at the server. In some embodiments, the KPI can be CPU / GPU, available memory, maximum round-trip time, the request rate that the server can handle, etc.

[0037] When the UE is responsible for determining the need for service continuity, the edge enabler client (EEC) discovers available target servers when determining that an application context transfer is required, and selects the optimal target server based on the preferences of the user and / or application client. In order to discover the available target servers, the EEC performs a service provisioning and enabler application server (EAS) discovery process to select a preferred target server from the discovered EAS list. In addition, the method includes providing detailed information of the target server to the edge enabler server (EES) to initiate a continuity process with the selected server.

[0038] However, in some cases, it may be advantageous for a server (i.e., an edge enabler server or an edge application server) to be responsible for determining the need for service continuity. In some embodiments, a method according to the present disclosure provides that the edge enabler server considers the preferences of the edge enabler client (EEC) and the application client served by the EES in order to select an appropriate target server to maintain service continuity by satisfying the preferences of the application client as well as the KPI requirements.

[0039] For clarity and better understanding of the present specification, the scope of certain terms used in the present disclosure should be interpreted as including, but not limited to, the description provided below.

[0040] Application client: An application that resides in the UE and performs client functions.

[0041] Edge Enabler Client (EEC): An enabling layer entity in the UE that assists the application client in implementing edge-related functions.

[0042] Edge Enabler Server (EES): An enabling layer entity in the edge that assists the Edge Enabler Client (EEC) in implementing edge-related functions.

[0043] Edge Configuration Server (ECS): An enabling layer entity in a wireless network used to assist edge enabler clients (EECs) in discovering and connecting to edge enabler servers.

[0044] Edge Application Server (EAS): An application server that resides at the edge.

[0045] Source Edge Enabler Server (EES): The edge enabler server currently serving the edge enabler client.

[0046] Source Edge Application Server (EAS): The edge application server currently serving the application client.

[0047] Target edge enabler server: The edge enabler server that will serve the edge enabler client after service continuity / application context transfer.

[0048] Target edge application server: The edge application server that will serve the application client after service continuity / application context transfer.

[0049] Target server: The optimal target edge application server when service continuity needs to be maintained between two edge application servers, or the cloud server when service continuity needs to be maintained between an edge application server and a cloud application server.

[0050] In this disclosure, the terms "service continuity" and "application context transfer (ACT)" may be used interchangeably to refer to the process of moving or transferring a user's application context from a server to a new server to maintain service continuity when the application connects to the new server.

[0051] In this disclosure, the terms "application context transfer (ACT)" and "application context relocation (ACR)" may also be used interchangeably. ACT refers to the actual transfer of application context between application servers. ACT refers to a part of the process called ACR for continuing services across application servers.

[0052] In certain embodiments, Figures 3 to 8 The edge enabler client in can be replaced with the source edge application server to help select the target edge application server.

[0053] Referring now to the drawings and more particularly to Figures 1 to 8 , a preferred embodiment is shown, wherein like reference numerals consistently denote corresponding features throughout the drawings.

[0054] Figure 1 is a sequence diagram illustrating an example of an edge enabler client (EEC) (102) detecting a need for an application context transfer (ACT) and providing a target edge application server (EAS) (106) to a source edge enabler server (EES) (104) according to certain known embodiments.

[0055] refer to Figure 1 When determining that an ACT is required, the EEC (102) discovers and selects a target EAS (106). In addition, the EEC (102) provides the source edge enabler server (104) with information of the determined target EAS (106) to initiate an application context transfer with the target EAS (106).

[0056] Thus, as can be seen, the prior art does not disclose taking into account the preferences of the user and the application client in the UE when the source EES detects the need for an ACT.

[0057] It would therefore be desirable to address the above-mentioned disadvantages or others, or at least provide a useful alternative.

[0058] Certain embodiments described herein address the above problems by providing a method and UE that provide selection criteria to a source EES for selecting an optimal target server for service continuity based on preferences of users and application clients in the UE.

[0059] Various embodiments described herein provide a method and apparatus for selecting an optimal target server for service continuity based on preferences of users and application clients in UEs using EEC.

[0060] Various embodiments described herein send target EAS selection criteria to the source EES through the EEC so that the source EES is aware of the preferences (such as KPI requirements) of the user and application clients in the UE even before detecting that an ACT is needed.

[0061] Figure 2 An example of a UE (210) in an edge computing environment (230) according to certain embodiments disclosed herein is shown in a block diagram format, and wherein the UE (210) is responsible for providing selection criteria for searching for an optimal target server based on an ACT request.

[0062] refer to Figure 2 In an illustrative example, an edge computing system (200) includes a UE (210) that communicates with a wireless network (240) via an edge (250).

[0063] The UE (210) may be, for example, a mobile device, a smart watch, a cellular phone, a smartphone, a personal digital assistant (PDA), a tablet computer, a laptop computer, an Internet of Things (IoT) device, an artificial intelligence (AI) device, etc.

[0064] In certain embodiments, the UE (210) includes a memory (212), a processor (214), a communicator (216), an application client (218), and an edge enabler client (220).

[0065] The wireless network (240) includes an edge configuration server (ECS) (242).

[0066] The edge (250) includes an edge enabler server (EES) (252) and a plurality of edge application servers (EAS) (254a to 254n). In some embodiments, the EES (252) serving the UE (210) is referred to as a source EES. In some embodiments, the EAS serving the UE (210) is referred to as a source EAS. In some embodiments, the edge (250) represents an edge data network as defined in the 3GPP TS23.558 technical standard.

[0067] In some embodiments, a memory (212) in the UE (210) stores instructions to be executed by the processor (214) for selecting an optimal target EAS from a plurality of target EASs (254a to 254n).

[0068] The memory (212) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (212) may be considered to be a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not included in the carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory (212) being non-removable. In some examples, the memory (212) may be configured to store a larger amount of information than the memory. In some instances, the non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache). The memory (212) may be an internal memory, or it may be an external storage unit of the UE (210), a cloud storage, or any other type of external memory.

[0069] In certain implementations, the processor (214) is in communication with the memory (212), the communicator (216), a plurality of application clients (218), and an edge enabler client (220).

[0070] The processor (214) is configured to execute instructions stored in the memory (212), including instructions for selecting an optimal target EAS from among a plurality of target EASs (254a through 254n).

[0071] The processor (214) may include one or more processors, which may be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), a graphics processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU) and / or an artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0072] In certain embodiments, the communicator (216) is configured for internal communication between internal hardware components, as well as communication with external devices via one or more networks. The communicator (216) includes electronic circuitry dedicated to supporting standards for wired or wireless communication.

[0073] The multiple application clients (218a to 218n) in the UE (210) are applications stored on the UE (210) or currently running on the UE (210). The multiple application clients (218a to 218n) may include, for example, streaming service applications, music applications, game applications, and social network applications.

[0074] Information about the application clients (218a-218n) is maintained by an edge enabler client (220) at the UE (210).

[0075] The EEC (220) at the UE (210) tracks information about the services required by different applications in the UE (210) and determines the need for an application context transfer (ACT) accordingly. The EEC (220) then sends the ACT information to a source EES (252) present in the edge (250).

[0076] In some embodiments, a user of a UE (210) may use one or more applications from multiple application clients (218a to 218n). For example, if a user is watching a video on a streaming application, a network service providing data to the UE (210) requires that the video stream with optimal quality be provided to the user uninterruptedly. However, the user of the UE (210) may move to different locations while watching the video. In this case, the EAS (254) to which the UE (210) is currently connected may no longer be the optimal EAS for the UE (210) at its new location. In order to achieve seamless video streaming, the UE (210) needs to connect to another optimal EAS.

[0077] In some embodiments, the source EES (252) present in the edge (250) sends a request to the EEC (220) to determine the target EAS (254) when an ACT is detected. The request from the source EES (252a) also serves as a notification or indication to the edge enabler client (220) to prepare the application client (218) for service continuity.

[0078] Upon receiving a request from a source edge enabler server (252), the edge enabler client (220) determines potential target edge application servers (254). Once the edge enabler client (220) has a list of potential targets, it uses the preferences of the user and application client (218) and the KPI requirements of the application client (218) to select the optimal target edge application server (254).

[0079] The edge enabler client (220) sends detailed information of the selected optimal target edge application server (254) with which the application context transfer should be initiated.

[0080] The source edge enabler server (252) considers the information received from the EEC (220) and initiates an application context transfer process with the selected target edge application server (EAS) (254).

[0081] In certain embodiments, selection of an optimal target EAS (254) is performed by a source EES (252) present in an edge (250) upon detection of an ACT received from an EEC (220), wherein a potential target EAS (254) is selected by the EES (252).

[0082] In various embodiments, upon determining that service continuity (i.e., ACT) is required, the edge enabler server (252) contacts the edge configuration server (242) to push a service provisioning update notification to the edge enabler client (220). The service provisioning update notification includes a list of potential target edge enabler servers. Additionally, the source edge enabler server (252) requests the edge enabler client (220) to provide the selected edge application server (254) for application context transfer.

[0083] In some embodiments, the edge enabler client (220) prepares selection criteria to select a target edge application server (254) in the event that service continuity may be required. The selection criteria may be for a specific application, or may apply to multiple applications. The edge enabler client (220) utilizes the preferences of the user and the application client (218), including the KPI requirements of the application client (218). Once prepared, the edge enabler client (220) shares the selection criteria with the edge enabler server (252). In some embodiments, the selection criteria may be shared by the edge enabler client (220) as part of a registration request to the edge enabler server (252). The edge enabler server (252) stores the received criteria and sends a response confirming receipt of the selection criteria. In addition, in the event that service continuity is required, the edge enabler server (252) uses the criteria to determine the target edge application server (254).

[0084] Therefore, as described above, the methods and apparatuses according to various embodiments disclosed herein take into account the preferences of users and applications.

[0085] although Figure 2A given set of hardware components of the UE (210) is shown, but it should be understood that other embodiments are possible and within the intended scope of the present disclosure. In some embodiments, the UE (210) may include more or fewer components than shown in the figure. In addition, the labels or names of the components are only for illustrative purposes and do not limit the scope of the present disclosure. One or more components can be combined together as part of the architecture to perform the function of selecting the optimal target EAS from multiple target EASs (254a to 254n).

[0086] Figure 3 is a sequence diagram showing an example of a source edge enabler server (252) requesting an edge enabler client (220) to provide detailed information of a target edge application server according to some embodiments disclosed herein.

[0087] refer to Figure 3 In an illustrative example, the source edge enabler server (252) requests the edge enabler client (220) to discover and select a target edge application server (254) to which the application context should be transferred when determining that service continuity is required. Upon receiving information of the selected target edge application server (254) from the edge enabler client (220) (which may also include information of the target edge enabler server), the source edge enabler server (252) performs an application context transfer process according to the operations described below.

[0088] At operation 302, the source edge enabler server (252a) detects a need for an application context transfer. In some embodiments, the need for an application context transfer can be a result of a change in the location of the UE (210) detected by the source edge enabler server (252) with or without the assistance of the wireless network (240). In some embodiments, the need for an application context transfer can be a result of a request from the source edge enabler server (252a) or a request from the edge enabler client (220) itself. In various embodiments, the need for an application context transfer is based on certain events monitored by the source edge enabler server (252a), such as an overload in the source edge application server (254). The above situations are just some examples of how the source edge enabler server (252a) detects the need for service continuity.

[0089] At operation 304, upon determining that an application context transfer is required, the source edge enabler server (252a) sends a request to the edge enabler client (220) to determine a target edge application server (254) for transferring the application context. The request also serves as a notification or instruction to the edge enabler client (220) to prepare the application client (218) for service continuity.

[0090] At operation 306, upon receiving the request from the source edge enabler server (252), the edge enabler client (220) uses the service provisioning process and the EAS discovery process as needed to determine potential target edge enabler servers (252b1 to 252bn) and potential target edge application servers (254) at operation 308. The provisioning process and the EAS discovery process are proposed in 3GPP TS23.558.

[0091] Once the edge enabler client (220) has a list of potential targets, the user and application client (218) preferences and the application client (218) KPI requirements are utilized to select the optimal target edge application server (254) and, if necessary, the target edge enabler server (252b1 to 252bn).

[0092] The edge enabler client (220) includes in its response to the source edge enabler server (252) details of the selected optimal target edge application server (254) or the target edge application server (254) that should initiate the application context transfer in operation 310.

[0093] At operation 312, the source edge enabler server (252) considers the information provided in step 310 and initiates an application context transfer process with the selected optimal target edge application server (254).

[0094] In some embodiments, Figure 3 As described in , the source edge enabler server (252a) is replaced with the target edge enabler server (252b1 to 252bn). In this embodiment, the need for the edge enabler client (220) to request service provision (operation 306, i.e., discovering the target edge enabler server) can be avoided. In addition, if necessary, the target edge enabler server (252b1 to 252bn) provides a list of potential target edge application servers (254) in its request to the edge enabler client (220). In this embodiment, the edge enabler client (220) may not need to perform discovery of potential target edge application servers according to operation 308.

[0095] Figure 4 is a sequence diagram showing an example of a source edge enabler server (252) providing a potential target list to an edge enabler client (220) to select a target edge application server (254) according to some embodiments disclosed herein

[0096] refer to Figure 4As a non-limiting example, in some embodiments, the source edge enabler server (252a) contacts the edge configuration server (242) to discover potential target edge application servers (254) when determining that service continuity is required. In addition, the source edge enabler server (252) discovers detailed information of the potential target edge application servers (254) from the potential target edge enabler servers (252b). Once the source edge enabler server (252a) has determined the list of potential target edge application servers (254), it sends the list to the edge enabler client (220) to select the target edge application server (254) from the provided list. Specifically, an example of providing a potential target list to select a target EAS includes the following operations:

[0097] At operation 402, the source edge enabler server (252a) detects a need for an application context transfer. As described above, in some embodiments, the need for an application context transfer can be a result of a change in the location of the UE (210) detected by the source edge enabler server (252) with or without the assistance of the wireless network (240). In some embodiments, the need for an application context transfer can be a result of a request from the source edge enabler server (252) or a request from the edge enabler client (220). In some embodiments, the need for an application context transfer is based on certain events monitored by the edge enabler server (252), such as an overload in the source edge application server (254). The above scenarios are a non-exhaustive set of examples of how the source edge enabler server (252) detects the need to provide service continuity.

[0098] At operation 404, upon determining that an application context transfer is required, the source edge enabler server (252a) sends a request to the edge configuration server (242) to determine potential target edge enabler servers (252b) that service the edge application server (254) required by the edge enabler client (220).

[0099] At operation 406, once the source edge enabler server (252a) has the list of potential target edge enabler servers (252b), the source edge enabler server (252a) contacts each of the potential target edge enabler servers (252a) to obtain the details of the edge application server (254) and creates a list of potential target edge application servers (254).

[0100] At operation 408, once the source edge enabler server (252a) has a list of potential target edge application servers (254), the source edge enabler server (252a) shares the list, including detailed information of the edge application servers (254), with the edge enabler client (220) to select a target edge application server (254). In various embodiments, the source edge enabler server (252a) skips operation 406 and shares the list of potential target edge enabler servers (252b) with the edge enabler client (220).

[0101] In some embodiments, if the list of potential target edge application servers (254) is shared by the source edge enabler server (252a), the edge enabler client (220) selects the target edge application server (254) at operation 410. Otherwise, if the list of potential target edge enabler servers (252b) is shared by the source edge enabler server (252a), the edge enabler client (220) performs an EAS discovery process with the potential target edge enabler server (252b) and also selects the target edge application server (254) at operation 410.

[0102] In operation 412, once the edge enabler client (220) selects the target edge application server (254), the edge enabler client (220) shares the details of the target edge application server (254) with the source edge enabler server (252a) taking into account the user and application client (218) preferences and KPI requirements. The source edge enabler server (252a) considers the information provided in operation 410 and initiates the application context transfer process with the selected target edge application server (254).

[0103] Figure 5 is a sequence diagram illustrating an example of a source edge enabler server (252a) triggering an edge configuration server (242) to send a service provisioning update with a potential target edge enabler server (252b) to an edge enabler client (220) according to embodiments disclosed herein.

[0104] refer to Figure 5In an illustrative example, the source edge enabler server (252a), upon determining that service continuity is required, contacts the edge configuration server (242) to push a service provision update notification to the edge enabler client (220). The service provision update notification will include a list of potential target edge enabler servers (252b). In addition, the source edge enabler server requests the edge enabler client (220) to provide the selected edge application server (254) for application context transfer. The request from the source edge enabler server (252a) triggers the edge enabler client (220) to discover the EAS of the potential target edge enabler server (252b). The edge enabler client (220) selects the target edge application server (254) from the available servers and provides the information to the source edge enabler server (252a) to initiate the application context transfer. An example of the exchange outlined above is presented with reference to the operations described below.

[0105] At operation 502, the source edge enabler server (252a) detects a need for an application context transfer. As described above, in some embodiments, the need for an application context transfer can be a result of a change in the location of the UE (210) detected by the source edge enabler server (252) with or without the assistance of the wireless network (240). In various embodiments, the need for an application context transfer can be a result of a request from the source edge enabler server (252) or a request from the edge enabler client (220). In some embodiments, the need for an application context transfer is based on certain events monitored by the edge enabler server (252), such as an overload at the source edge application server (254). The above situations are merely some examples of how the source edge enabler server (252) can detect the need for service continuity.

[0106] At operation 504, upon determining that an application context transfer is required, the source edge enabler server (252a) sends a request to the edge configuration server (242) to push a service provisioning notification to the edge enabler client (220). The request includes EAS information such as an EAS ID and may include the future location of the UE requiring the target edge application server (254).

[0107] At operation 506, the edge configuration server (242), upon receiving the request from the source edge enabler server (252a), determines and notifies the edge enabler client (220) of the provisioning information including a list of potential target edge enabler servers (252b). In an alternative embodiment, the edge configuration server (242) monitors the UE (210) and pushes updated service provisioning based on updated characteristics of the UE (210), such as the current location; there is no request from the source edge enabler server (252a).

[0108] At operation 508, once the edge enabler client (220) is notified, the edge configuration server (242) responds to the source edge enabler server (252a).

[0109] At operation 510, the source edge enabler server (252a) sends a request to the edge enabler client (220) to select a target edge application server (254).

[0110] At operation 512, upon receiving the request from the source edge enabler server (252a), the edge enabler client (220) uses the EAS discovery process to determine a list of potential target edge application servers (254). The edge enabler client (220) selects the target edge application server (254) taking into account the preferences of the user and application client (218) and the KPI requirements.

[0111] In operation 514, the edge enabler client (220) shares detailed information of the target edge application server (254) with the source edge enabler server (252a), the detailed information including detailed information of the edge enabler server (252b).

[0112] At operation 516, the source edge enabler server (252a) considers the information provided in operation 514 and initiates an application context transfer process with the selected target edge application server (254).

[0113] In various embodiments, reference Figures 3 to 5The described method may require real-time interaction between the source edge enabler server (252a) and the edge enabler client (220) in order to select the target edge application server (254). However, this real-time interaction may increase the delay in completing the entire service continuity process. To avoid this delay, in some embodiments, the edge enabler client (220) configures the target edge application server selection criteria in the source edge enabler server (252a) for all applications that may require service continuity in the future. When it is detected that an application context transfer is required, the source edge enabler server (252a) uses the target edge application server selection criteria to self-discover and select the target edge enabler server (252b) and the target edge application server (254). The criteria may include application client KPIs, preferred ECSPs, EAS availability conditions (e.g., available for at least 90 minutes), etc., and are provided to the source edge enabler server by the edge enabler client (220) in an explicit request, or as part of the EEC (220) registration details, or as part of the EAS discovery request.

[0114] If desired, the criteria may simply indicate that the source edge enabler server (252a) may select the target server on its own. This may be due to various usage scenarios, for example, the edge enabler client (220) is unaware of any preferences of the user or application client (218), including KPI requirements.

[0115] Figure 6 is a sequence diagram illustrating an example of an edge enabler client (220) configuring target edge application server selection criteria in an edge enabler server (252a) according to some embodiments disclosed herein.

[0116] Figure 6 A process is shown in which an edge enabler client (220) is providing selection criteria to a source edge enabler server (252a), wherein the process includes the operations described below.

[0117] The edge enabler client (220) prepares selection criteria to select a target edge application server (254) for an application that may require service continuity. The selection criteria may be for a specific application, or may apply to multiple applications in the UE (210). The edge enabler client (220) utilizes the preferences of the user and the application client (218), including the KPI requirements of the application client (218).

[0118] Once ready, the edge enabler client (220) shares the selection criteria with the source edge enabler server (252a) at operation 602. In an alternative embodiment, the selection criteria may be shared by the edge enabler client (220) as part of a registration request to the source edge enabler server (252a). In another embodiment, the selection criteria may be shared by the edge enabler client (220) as part of an EAS discovery request to the source edge enabler server (252a).

[0119] At operation 604, the source edge enabler server (252a) stores the received criteria.

[0120] The source edge enabler server (252a) sends a response confirming receipt of the selection criteria at operation 606. Additionally, in scenarios where service continuity is desired, the edge enabler server (252a) uses the criteria to determine the target edge application server (254).

[0121] Figure 7 is a signaling diagram illustrating an example of a source edge enabler server (252a) selecting a target edge application server (254) based on selection criteria received from an edge enabler client (220) according to certain embodiments disclosed herein.

[0122] Figure 7 A process is shown in which a source edge enabler server (252a) contacts an edge configuration server (242) to discover a potential target edge enabler server (252b) when determining that service continuity is required. The source edge enabler server (252a) discovers detailed information of a potential target edge application server (254) from the potential target edge enabler server (252b). Once the source edge enabler server (252a) has determined a list of potential target edge application servers (254), it also selects a target EAS (254) based on selection criteria received from an EEC (220), and notifies the EEC (220) of the detailed information of the selected target EAS (254) and the detailed information of the EEC on which the selected target EAS is registered (i.e., the target EEC). In some embodiments, the process includes the operations described below.

[0123] At operation 702, the source edge enabler server (252a) detects a need for an application context transfer. As described above, in some embodiments, the need for an application context transfer can be a result of a change in the location of the UE (210) detected by the source edge enabler server (252) with or without the assistance of the wireless network (240). In various embodiments, the need for an application context transfer can be a result of a request from the source edge enabler server (252) or a request from the edge enabler client (220). In some embodiments, the need for an application context transfer is based on certain events monitored by the edge enabler server (252), such as an overload in the source edge application server (254). The above situations are merely some examples of how the source edge enabler server (252) can detect the need for service continuity.

[0124] At operation 704, upon determining that an application context transfer is required, the source edge enabler server (252a) sends a request to the edge configuration server (242) to determine a potential target edge enabler server (252b) that serves the edge application server (254) required by the edge enabler client (220). If the edge enabler server (252a) already has detailed information of the potential target edge enabler server (252b), this operation can be skipped.

[0125] At operation 706, once the source edge enabler server (252a) has the list of potential target edge enabler servers (252b), it contacts each of the potential target edge enabler servers (252b) to obtain the details of the edge application server (254) that creates the list of potential target edge application servers (254). If the edge enabler server (252a) already has the details of the potential target edge application servers (254), this operation can be skipped.

[0126] At operation 708, once the edge enabler server (252a) has a list of potential target edge application servers (254), it selects the optimal target edge application server (254) taking into account user and application client (218) preferences and KPI requirements received from the EEC (220) as selection criteria.

[0127] In operation 710, the source edge enabler server (252a) sends information of the selected target edge application server (254) and the selected target EAS-registered EES (ie, target EES) to the edge enabler client (220).

[0128] At operation 712, the edge enabler client (220) provides a confirmation to the source edge enabler server (252a) that the application context transfer process may be triggered. In an alternative embodiment, the edge enabler server (252a) may trigger the application context transfer process without a confirmation from the edge enabler client (220).

[0129] At operation 714, the source edge enabler server (252a) initiates an application context transfer process with the selected target edge application server (254). In an alternative embodiment, this step may be performed without the participation of the edge enabler server (252a).

[0130] In some implementations, operation 714 may be performed immediately after operation 708, depending on service requirements, in order to minimize service interruption during the continuity period.

[0131] In certain embodiments, Figure 4 and Figure 7 The methods shown can be used in combination. In this case, if the source edge enabler server (252a) has received the selection criteria (such as Figure 6 ), or requesting the edge enabler client (220) to select a target edge application server from a list of potential target edge application servers (such as Figure 3 ), the source edge enabler server (252a) selects a target edge application server (254).

[0132] Figure 8 is a flow chart illustrating an exemplary method of selecting an optimal target edge application server (254) based on selection criteria stored at an edge enabler server (252a) according to certain embodiments disclosed herein.

[0133] At operation 802, the edge enabler client (EEC) (220) sends selection criteria for selecting a target edge application server (254) to the source edge enabler server (252a). In addition, the source edge enabler server (252a) stores the selection criteria.

[0134] At operation 804, the source edge enabler server (252a) detects a need for application context transfer by the application client (218) in the UE (210).

[0135] At operation 806, the source edge enabler server (252a) selects a target EAS for application context transfer based on the selection criteria.

[0136] At operation 808, the source edge enabler server (252a) sends a notification to the edge enabler client (220) regarding the selected target EAS.

[0137] Fig. 9 is a block diagram illustrating an example of a source edge enabler server according to certain embodiments of the present disclosure.

[0138] refer to Fig. 9 , a source edge enabler server may include a transceiver (910), a controller (or processor) (920), and a memory (930).

[0139] The transceiver (910) is responsible for communicating with other network entities. The transceiver (910) may transmit information, signals or messages with other network entities (eg, an edge enabler client in a user equipment (UE)).

[0140] The controller (920) can control to: receive selection criteria for selecting a target edge application server from an edge enabler client in the UE via the transceiver (910), determine the need for application context transfer of the application client in the UE, select a target edge application server for application context transfer based on the selection criteria received from the edge enabler client, and send a notification about the selected target edge application server to the edge enabler client via the transceiver (910).

[0141] The memory (930) may store information, signals or messages received from other network entities. The memory (930) may also store information generated by the controller (920).

[0142] The various actions, actions, blocks, steps, etc. in the flowchart may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, actions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present disclosure.

[0143] Although the present disclosure has been described in conjunction with various embodiments, various changes and modifications may occur to those skilled in the art. The present disclosure is intended to cover such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by an edge enabler client in an edge computing system, the method comprising: Sending information on selection criteria for target edge application server selection to the source edge enabler server; as well as receiving, in an event that the source edge enabler server detects a need for application context relocation, a notification from the source edge enabler server regarding a target edge application server that meets the selection criteria for the application context relocation of the application client; The information related to the selection criteria includes: information indicating the need for service continuity, and at least one of an expected key performance indicator KPI of the application client or a minimum KPI of the application client.

2. The method according to claim 1, wherein: The need for relocating the application context is detected based on location information of a user equipment UE.

3. The method according to claim 1, wherein: The notification includes information about a target edge enabler server associated with the target edge application server.

4. The method according to claim 1, wherein: Information related to the selection criteria is shared to the source edge enabler server as part of an initial registration request, and wherein the information related to the selection criteria is associated with the application client.

5. The method according to claim 1, wherein: Information related to the selection criteria is shared to the source edge enabler server as part of an edge application server discovery request.

6. The method according to claim 1, wherein: The information related to the selection criteria is related to a specific application or one of a plurality of applications.

7. The method according to claim 1, wherein: The information related to the selection criteria also includes application client information related to the required service.

8. An edge enabler client in an edge computing system, the edge enabler client comprising: Transceiver; as well as The controller is configured as: sending, via the transceiver, information of selection criteria for target edge application server selection to the source edge enabler server, and receiving, in an event that the source edge enabler server detects a need for application context relocation, a notification from the source edge enabler server via the transceiver regarding a target edge application server that meets the selection criteria for the application context relocation of the application client, The information related to the selection criteria includes: information indicating the need for service continuity, and at least one of an expected key performance indicator KPI of the application client or a minimum KPI of the application client.

9. The edge enabler client according to claim 8, wherein: The need for the application context transfer is detected based on location information of a user equipment UE.

10. The edge enabler client according to claim 8, wherein: The notification includes information about a target edge enabler server associated with the target edge application server.

11. The edge enabler client according to claim 8, wherein: Information related to the selection criteria is shared to the source edge enabler server as part of an initial registration request, and wherein the information related to the selection criteria is associated with the application client.

12. The edge enabler client of claim 8, wherein: Information related to the selection criteria is shared to the source edge enabler server as part of an edge application server discovery request.

13. The edge enabler client of claim 8, wherein: The information related to the selection criteria is related to a specific application or one of a plurality of applications.

14. The edge enabler client of claim 8, wherein: The information related to the selection criteria also includes application client information related to the required service.

Images