User equipment (UE) in edge data network (EDN) and methods thereof

Abstract

The present disclosure relates to a user equipment (UE) in an edge data network (EDN) and a method thereof. The method comprises: selecting, by an edge Enabler Client (EEC), an EAS for use by an Application Client (AC) of the UE from at least one discovered edge Application Server (EAS); sending, by the EEC, a first message indicating an application context relocation (ACR) information subscription request to an edge enabled server (EES), wherein the first message includes an identifier (ID) of the selected EAS; and receiving, by the EEC from the EES, a second message indicating an ACR information subscription response in response to the first message.

Description

[0001] This application is a divisional application of an invention patent application with an application date of October 5, 2021, application number 202180006743.8, and invention name “Method and device for providing services to edge application servers (EAS) in edge data networks (EDN)”. Technical Field

[0002] The present disclosure relates to edge computing, and more particularly, to a method and apparatus for providing services to an edge application server (EAS) in an edge data network (EDN). Background Art

[0003] In order to meet the increased demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-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 (millimeter wave) bands (e.g., 60GHz bands) in order 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 are discussed in 5G communication systems. In addition, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoints (CoMP), receiving-end interference elimination, etc. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coded modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0004] The Internet, as a human-centered connected network in which humans generate and consume information, is now developing toward the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. Through connection with cloud servers, the Internet of Everything (IoE) has emerged as a combination of IoT technology and big data processing technology. Because the implementation of IoT requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology", sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently. Such an 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 convergence 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, healthcare, smart appliances, and advanced medical services.

[0005] 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. Cloud radio access networks (RANs) as an application of the above-mentioned big data processing technologies can also be considered as an example of the fusion between 5G technologies and IoT technologies.

[0006] Generally, edge computing systems provide an environment in which application(s) can be hosted close to the application(s) consumers to provide the benefits of high availability and low latency. Figure 1 The detailed architecture explained in the existing 3GPP technical specification (TS) 23.558 is shown. In the 3GPP edge, (multiple) applications are hosted in the edge data network (EDN) (10), and (multiple) applications are called (multiple) edge application servers (EAS) (11). EAS (11) is assisted by (multiple) edge enabler servers (EES) (12) co-located with EAS (11) in EDN (10). The assistance provided by EES (12) includes monitoring user equipment (UE) (20), providing EAS (11) with the self and capabilities exposed by the core network (30), assisting application context relocation, etc.

[0007] The application consumers (multiple) of the EAS (11) are referred to as application clients (multiple) (ACs) (21), which reside on the UE (20) and are assisted by an edge enabler client (EEC) (22) on the UE (20). Multiple EASs (11) for the same application may be accessible on various EDNs at any one time, ready to provide services to the UE (20). The edge configuration server (ECS) (13) and the EES (12) assist the UE (20) in finding these EASs (11). With the help of the AC (21), the EEC (22) then selects one of the available EASs (e.g., selects EAS (11a) among the EASs (11)) and facilitates the establishment of communications between the AC (21) and the selected EAS (11a).

[0008] Currently, there is no mechanism for the EES (12) to determine which EAS is selected by the EEC (22). This makes it difficult for the EES (12) to provide services to their EAS (11). Because the EES (12) does not know whether the EEC (22) has selected an EAS (11) registered with the EES (12), the EES (12) cannot decide whether the EES (12) needs to reserve resources and make appropriate arrangements (such as subscribing to 3GPP core network capabilities or monitoring UE application context relocation (ACR) support) to provide support to the EAS (11). Therefore, it is desirable to provide a useful alternative to inform the EES (12) about the use of the EAS (11). Summary of the invention

[0009] Technical issues

[0010] The main purpose of the embodiments herein is to receive edge application server (EAS) usage indications from edge enabler clients (EEC) and / or edge application servers (EAS) of user equipment (UE) by edge enabler servers (EES) of edge data network (EDN). The EES then reserves resources and makes appropriate arrangements (e.g., subscribing to CN capabilities or monitoring the ACR of the UE) to provide support to the EAS based on the EAS usage indications. As a result, resources are optimally utilized in the edge data network (EDN).

[0011] Another object of the embodiments of the present invention is to store multiple parameters associated with the EAS usage indication in the EES (e.g., an identifier of the EEC (EECID), security credentials of the EEC, an identifier of the UE (UE ID), a source Internet Protocol (IP) address of the UE, etc.) when the credentials of the EEC and / or EAS and / or the source EES are valid.

[0012] Technical Solution

[0013] Accordingly, one aspect of the present disclosure is to provide a method for a user equipment UE including an edge enabler client EEC in an edge data network EDN, the method comprising: the EEC selecting an EAS used by the UE's application client AC from at least one discovered edge application server EAS; the EEC sending a first message indicating an application context relocation ACR information subscription request to the edge enabling server EES, wherein the first message includes an identifier ID of the selected EAS; and the EEC receiving a second message indicating an ACR information subscription response in response to the first message from the EES.

[0014] Another aspect of the present disclosure is to provide a user equipment UE in an edge data network EDN, the UE comprising: an application client AC; and an edge enabler client EEC, wherein the EEC is configured to: select an EAS used by the AC from at least one discovered edge application server EAS; send a first message indicating an application context relocation ACR information subscription request to an edge enabler server EES, wherein the first message includes an identifier ID of the selected EAS; and receive a second message indicating an ACR information subscription response in response to the first message from the EES

[0015] Another aspect of the present disclosure is to provide a method for providing at least one service to an edge application server (EAS) in an edge data network (EDN), the method comprising: receiving, by an edge enabler server (EES), an EAS usage indication from an edge enabler client (EEC) of a user equipment (UE), wherein the EAS usage indication comprises at least one parameter; identifying, by the EES, the at least one parameter; and providing, by the EES, at least one service to the EAS based on the at least one parameter.

[0016] Another aspect of the present disclosure is to provide an edge enabler server (EES) that provides at least one service to an edge application server (EAS) in an edge data network (EDN), the EES comprising: a memory; a processor; and a controller, which is operably connected to the memory and the processor and is configured to: receive an EAS usage indication from an edge enabler client (EEC) of a user equipment (UE), wherein the EAS usage indication includes at least one parameter; identify the at least one parameter; and provide at least one service to the EAS based on the at least one parameter.

[0017] Accordingly, an embodiment of the present invention discloses a method for providing (multiple) services to an edge application server (EAS) in an edge data network (EDN). The method includes receiving, by an edge enabler server (EES), an EAS usage indication from an edge enabler client (EEC) of a user equipment (UE), wherein the EAS usage indication includes multiple parameters. In addition, the method includes determining, by the EES, whether the credentials of the EEC are valid. In addition, the method includes: in response to determining that the credentials of the EEC are valid, storing multiple parameters by the EES. In addition, the method includes providing (multiple) services to the EAS based on the stored multiple parameters by the EES.

[0018] In an example embodiment, the plurality of parameters include an identifier of the EEC (EECID), security credentials of the EEC, an identifier of the UE (UE ID), or a list of EAS identifiers (EASIDs) being used by an application client (AC) of the UE.

[0019] In an example embodiment, the method includes determining, by the EEC, a plurality of EASs in the EDN using an edge configuration server (ECS) and an EES. In addition, the method includes selecting, by the EEC, an EAS from the plurality of EASs to send an EAS usage indication of the selected EAS, wherein the AC establishes a connection with the selected EAS for (multiple) application services. The selection of the EAS by the EEC is performed with the help of an application client (AC) of the UE.

[0020] In an example embodiment, the method further includes sending, by the EES, an EAS usage indication confirmation to the EEC, wherein the EAS usage indication confirmation includes a success response, an identifier of the EES (EESID), and security credentials of the EES when the EES has successfully processed the received indication; or the EAS usage indication confirmation includes a failure response or a failure reason when the EES has failed to process the received indication.

[0021] In an example embodiment, the EEC sends the EAS usage indication as part of another message sent from the EEC to the EES, such as an Application Context Relocation (ACR) Information Subscription message, an EEC Registration Update message, or an EEC Context message.

[0022] In an example embodiment, in response to selecting an EAS for an application layer service, an ACR information subscription message or an EEC registration update message is sent by the EEC to the EES of the selected EAS.

[0023] In an example embodiment, when an EEC moves from a source EES to a target EES, the source EES sends / uses an EEC context message, and wherein the EEC context message includes information received from the EEC or the EAS.

[0024] In an example embodiment, the method includes receiving, by the EAS, a request for application layer services from the AC of the UE, and the request includes the source Internet Protocol (IP) address of the UE, the EECID, and the UE ID. In addition, the method includes receiving, by the EES, an EAS usage indication from the EAS, wherein the EAS usage indication includes the source IP address of the UE, the EECID, and the UE ID. In addition, the method includes determining, by the EES, whether the credentials of the EAS are valid. In addition, the method includes: in response to determining that the credentials of the EAS are valid, storing, by the EES, the source IP address, the EECID, and the UE ID of the UE. In addition, the method includes identifying, by the EES, the UE based on the received EAS usage indication. In addition, the method includes reserving, by the EES, (multiple) resources to provide services to the EAS associated with the identified UE. In addition, the method includes sending, by the EES, an EAS usage indication confirmation to the EAS.

[0025] In an example embodiment, providing (multiple) services by the EES to the EAS based on the stored multiple parameters includes, for example, performing at least one of the following: reserving resources such as computing resources or storage resources for the EAS, monitoring the location of the UE to provide assistance to the EAS for ACR, or subscribing to information related to the UE and exposing an application programming interface (API) utilizing 3GPP core network capabilities, etc.

[0026] Accordingly, embodiments of the present invention disclose an EES for providing (multiple) services to an EAS in an EDN. The EES includes a resource controller coupled to a processor and a memory. The resource controller is configured to receive an EAS usage indication from an edge EEC of a UE, wherein the EAS usage indication includes multiple parameters. In addition, the resource controller is configured to determine whether the credentials of the EEC are valid. In addition, the resource controller is configured to store multiple parameters in response to determining that the credentials of the EEC are valid. In addition, the resource controller is configured to provide at least one service to the EAS based on the stored multiple parameters.

[0027] When considered in conjunction with the following description and the accompanying drawings, these and other aspects of the embodiments herein will be better understood and appreciated. However, it should be understood that although the following description indicates preferred embodiments and many specific details therein, these descriptions are given by way of illustration and not limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the scope of this invention, and the embodiments herein include all such modifications.

[0028] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives mean inclusion without limitation; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean include, be included, interconnected with, contain, be contained within, connect to or with, couple to or with, communicate with, cooperate with, interleave, juxtapose, be proximate, be combined with or with, have, have the property of, etc.; and the term "controller" means any device, system, or part thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0029] 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 embodied 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, instances, related data or parts thereof adapted to be implemented 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-transient" computer-readable media do not include wired, wireless, optical or other communication links that transmit instantaneous electrical signals or other signals. Non-transient computer-readable media include media that can permanently store data and media that can store data and overwrite it later, such as rewritable optical discs or erasable memory devices.

[0030] Definitions for certain words and phrases are provided in this patent document, those of ordinary skill 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.

[0031] Advantageous Effects of the Invention

[0032] According to various embodiments of the present disclosure, resources can be optimally utilized in an EDN. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The method and system are illustrated in the accompanying drawings, in which the same reference numerals indicate corresponding parts in the different drawings. With reference to the accompanying drawings, the embodiments of the present invention will be better understood from the following description, in which:

[0034] Figure 1 The architecture of an edge computing system for enabling edge applications in a 3rd Generation Partnership Project (3GPP) network according to the prior art disclosed herein is shown;

[0035] Figure 2A A system block diagram for notifying edge enabler server(s) (EES) about the use of edge application server(s) (EAS) in an edge data network (EDN) according to embodiments disclosed herein is shown;

[0036] Figure 2B A block diagram of an EES for providing service(s) to an EAS based on an EAS usage indication received from an edge enabler client (EEC) of a user equipment (UE) and / or an EAS in an EDN according to embodiments disclosed herein is shown;

[0037] Figure 3 is a flow chart illustrating a method for providing service(s) to an EAS in an EDN according to embodiments disclosed herein;

[0038] Figure 4 is a sequence diagram illustrating a method in which an EAS provides an EAS usage indication to an EES according to an embodiment disclosed herein;

[0039] Figure 5 is a sequence diagram illustrating a method in which an EEC provides an EAS usage indication to an EES according to an embodiment disclosed herein;

[0040] Figure 6 is a sequence diagram illustrating a method in which an EEC provides an EAS usage indication to an EES as part of another message (such as an ACR information subscription request) according to embodiments disclosed herein; and

[0041] Figure 7is a sequence diagram illustrating a method in which a source EES provides an EAS usage indication as part of an EEC context to a target EES according to embodiments disclosed herein.

[0042] Figure 8 is a block diagram of a first electronic device according to an embodiment of the present disclosure.

[0043] Fig. 9 is a block diagram of a second electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0044] Discussed below Figures 1 to 9 The various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary 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 suitably arranged system or device.

[0045] The embodiments of the present invention and their various features and advantageous details are explained more comprehensively with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. The description of known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments of the present invention. In addition, the various embodiments described herein are not necessarily mutually exclusive, because some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise indicated, the term "or" used herein refers to 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. Accordingly, these examples should not be interpreted as limiting the scope of the embodiments of the present invention.

[0046] According to the tradition of this field, embodiments can be described and illustrated according to the frame of performing one or more functions described.These frames (which may be referred to as units or modules, etc. in this article) are physically implemented by analog or digital circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and can be optionally driven by firmware.For example, the circuit can be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards, etc. The circuit constituting the frame can be implemented by dedicated hardware, or by a processor (for example, one or more programmed microprocessors and related circuits), or by a combination of dedicated hardware for executing some functions of the frame and a processor for executing other functions of the frame.Without departing from the scope of the present disclosure, each frame of the embodiment can be physically divided into two or more interacting and discrete frames.Similarly, without departing from the scope of the present disclosure, the frame of the embodiment can be physically combined into more complex frames.

[0047] The accompanying drawings are used to help easily understand various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. Therefore, the present disclosure should be interpreted as extending to any changes, equivalents and substitutes other than those specifically described in the accompanying drawings.

[0048] Accordingly, an embodiment of the present invention discloses a method for providing (multiple) services to an edge application server (EAS) in an edge data network (EDN). The method includes receiving, by an edge enabler server (EES), an EAS usage indication from an edge enabler client (EEC) of a user equipment (UE), wherein the EAS usage indication includes multiple parameters. In addition, the method includes determining, by the EES, whether the credentials of the EEC are valid. In addition, the method includes: in response to determining that the credentials of the EEC are valid, storing multiple parameters by the EES. In addition, the method includes providing (multiple) services to the EAS based on the stored multiple parameters by the EES.

[0049] Accordingly, embodiments of the present invention disclose an EES for providing (multiple) services to an EAS in an EDN. The EES includes a resource controller coupled to a processor and a memory. The resource controller is configured to receive an EAS usage indication from an edge EEC of a UE, wherein the EAS usage indication includes multiple parameters. In addition, the resource controller is configured to determine whether the credentials of the EEC are valid. In addition, the resource controller is configured to store multiple parameters in response to determining that the credentials of the EEC are valid. In addition, the resource controller is configured to provide at least one service to the EAS based on the stored multiple parameters.

[0050] In an alternative embodiment, the EAS usage indication is provided by the EAS to the EES. In another embodiment, when the EEC moves from the source EES to the target EES, the EAS usage indication is provided by the source EES to the target EES as part of the EEC context.

[0051] Figure 1 An existing general architecture for enabling edge applications in a 3rd Generation Partnership Project (3GPP) network is shown, as described in 3GPP Technical Specification (TS) 23.558. The ECS (13) is responsible for providing relevant configurations to the EEC (22) in the UE (20) so that the EEC (22) determines the availability of edge computing services and connects to available edge enabler servers. This process is called service provisioning. In addition, the EES (12) is responsible for providing relevant configurations to the EEC (22) in the UE (20) so that the EEC (22) can determine the availability of (multiple) EAS (11) and enable the AC (21) to connect to (multiple) EAS (11). This process is called EAS discovery.

[0052] During service provisioning, the EEC (22) may obtain the configuration of multiple EES (12) and further perform EAS discovery on all or some of those EES (12), thereby receiving details of multiple EAS (11). The EEC (22) selects a specific EAS (or set of EAS) for the application service in a post-EAS discovery operation. The EEC (22) may make the selection with the help of the AC (21). Once the EAS(s) are selected, the AC (21) establishes a connection with the EAS(s) (11) and utilizes the application service(s).

[0053] During this process, the EES (12) is not informed whether the EEC (22) has selected an EAS to register with the EES (12). This creates a problem for the EES (12) to determine whether it needs to provide any services to the EAS (11) in response to the most recent EAS discovery request. The EES (12) may need to reserve some resources or may need to subscribe to capabilities of the core network (i.e., the 3GPP core network (30)). For example, a subscription may be required to monitor and detect the need for application context relocation (ACR).

[0054] Unlike existing methods and systems, the provided method allows the EES to receive EAS usage indications from the EEC and / or EAS of the UE. The EES then reserves resources and makes appropriate arrangements (e.g., subscribing to CN capabilities or monitoring the ACR of the UE) to provide support to the EAS based on the EAS usage indications. As a result, resources are optimally utilized in the edge data network (EDN).

[0055] Unlike existing methods and systems, the provided method allows the EES to store multiple parameters associated with the EAS usage indication in the EES (e.g., an identifier of the EEC (EECID), security credentials of the EEC, an identifier of the UE (UE ID), a source Internet Protocol (IP) address of the UE, etc.) when the credentials of the EEC and / or EAS and / or the source EES are valid.

[0056] Referring now to the drawings, and more particularly to the Figures 2A to 7 , showing a preferred embodiment.

[0057] Figure 2A A block diagram of a system (1000) for notifying edge enabler servers (EES) (120) of usage of edge application servers (EAS) (110) in an edge data network (EDN) (100) is shown according to embodiments disclosed herein.

[0058] The system (1000) includes a user equipment (200), a 3GPP core network (300), an EDN (100), and an edge configuration server (ECS) (130). The UE (200) can be, for example but not limited to, a smart phone, a smart watch, a tablet, an Internet of Things (IoT) device, and a robot device. The UE (200) includes (multiple) application clients (AC) (210) and an edge enabler client (EEC) (220). The EDN (100) includes an EAS (110) and an EES (120).

[0059] The EEC (220) determines the availability of multiple EASs in the EDN (100) by using the ECS (130) and the EES (120). In addition, the EEC (220) selects (multiple) EASs (110) from the multiple EASs by using the AC (210) of the UE (200). Once selected, the EEC (220) sends an EAS use indication to the EES (120) in which the selected EAS (110) is registered. The AC (210) establishes a connection with the selected EAS for (multiple) application services.

[0060] The EES (120) receives an EAS usage indication from an EEC (220) of a UE (200), wherein the EAS usage indication includes a plurality of parameters. The plurality of parameters include an identifier (EECID) of the EEC (220), security credentials of the EEC (220), an identifier (UEID) of the UE (200), or a list of EAS identifiers (EASIDs) being used by the AC (210) of the UE (200). The EEC (220) sends the EAS usage indication to the EES (120) using a dedicated message or as part of another message, such as an application context relocation (ACR) information subscription message and / or an EEC registration update message and / or an EEC context message.

[0061] The source EES (120a) sends / uses an EEC context message to the target EES (120b), wherein the EEC context message includes information received from the EEC (220) or the EAS (110).

[0062] In addition, the EES (120) determines whether the credentials of the EEC are valid. In addition, in response to determining that the credentials of the EEC are valid, the EES (120) stores multiple parameters. In addition, the EES (120) provides (multiple) services to the EAS based on the stored multiple parameters. In addition, the EES (120) sends an EAS usage indication confirmation and / or an ACR information subscription response and / or an EEC registration response back to the EEC (220), wherein when the EES (120) has successfully processed the EAS usage indication, the message includes at least one of a success response, an identifier of the EES (EESID) and a security credential of the EES (120), otherwise, the message includes a failure response and / or a failure reason.

[0063] In addition, the EAS (110) receives a request for (multiple) application layer services from the AC (210) of the UE (200), and the request includes at least one of a source Internet Protocol (IP) address, an EECID, and a UE ID of the UE (200). In addition, the EES (120) receives an EAS usage indication from the EAS, wherein the EAS usage indication includes at least one of a source IP address, an EECID, and a UE ID of the UE. In addition, the EES (120) determines whether the credentials of the EAS (110) are valid. In addition, in response to determining that the credentials of the EAS (110) are valid, the EES (120) stores the source IP address, the EECID, and the UE ID of the UE (200). In addition, the EES (120) identifies the UE (200) based on the received EAS usage indication. In addition, the EES (120) reserves (multiple) resources for the EAS (110) associated with the identified UE (200). In addition, the EES (120) sends an EAS usage indication confirmation to the EAS (110).

[0064] In addition, the EES (120) performs at least one of the following: reserving at least one resource, wherein the at least one resource includes at least one of a computing resource for the EAS (110) and a storage resource for the EAS (110); monitoring the location of the UE (200) to provide assistance to the EAS (110) for ACR; subscribing to information related to the UE (200) and exposing an application programming interface (API) using a third generation partnership project (3GPP) core network (300) capability.

[0065] In an alternative embodiment, the source EES (120) sends the EAS usage indication to the target EES (120) as part of an EEC context message used by the source EES when the EEC (220) moves from the source EES to the target EES, and wherein the EEC context message includes information received from the EEC (220) or the EAS (110).

[0066] Figure 2BA block diagram of an EES (120) for providing service(s) to an EAS (110) based on EAS usage indications received from an EEC (220) of a UE (200) and / or an EAS (110) and / or a source EES (120) in an EDN (100) according to embodiments disclosed herein is shown.

[0067] In one embodiment, the EES (122) includes a memory (121), a processor (122), a communicator (123), and a resource controller (124).

[0068] In one embodiment, the memory (121) is configured to store a plurality of parameters. The memory (121) stores instructions to be executed by the processor (122). The memory (121) 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 a form of an electrically programmable memory (EPROM) or an electrically erasable programmable memory (EEPROM). In addition, in some examples, the memory (121) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagating signal. However, the term "non-transitory" should not be interpreted as the memory (121) being non-removable. In some examples, the memory (121) may be configured to store a greater amount of information than the memory. In some examples, 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 (121) may be an internal storage unit, or it may be an external storage unit of the EES (120), a cloud storage device, or any other type of external storage device.

[0069] The processor (122) communicates with the memory (121), the communicator (123) and the resource controller (124). The processor (122) is configured to execute instructions stored in the memory (121) and perform various processes. The processor (122) may include one or more processors, which may be general-purpose processors (such as central processing units (CPUs), application processors (APs), etc.), graphics processing units (such as graphics processing units (GPUs), visual processing units (VPUs)) and / or artificial intelligence (AI) dedicated processors (such as neural processing units (NPUs)).

[0070] The communicator (123) is configured to communicate internally between internal hardware components and with external devices (e.g., EAS (110), UE (200), ECS (130), etc.) via one or more networks (e.g., radio technologies). The communicator (123) includes electronic circuitry specific to a standard that enables wired or wireless communication.

[0071] The resource controller (124) is implemented by processing circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware. For example, the circuits may be embodied in one or more semiconductor chips, or on a substrate support such as a printed circuit board.

[0072] In an example embodiment, a resource controller (124) receives an EAS usage indication from an EEC (220) of a UE (200), wherein the EAS usage indication includes a plurality of parameters. In addition, the resource controller (124) determines whether the credentials of the EEC (220) are valid. In addition, in response to determining that the credentials of the EEC (220) are valid, the resource controller (124) stores the plurality of parameters. In addition, the resource controller (124) provides (a plurality of) services to the EAS (110) based on the stored plurality of parameters. In addition, the resource controller (124) sends an EAS usage indication confirmation to the EEC (220) and / or the EAS (110).

[0073] In an alternative example embodiment, a resource controller (124) receives an EAS usage indication from an EAS (110), wherein the EAS usage indication includes at least one of a source IP address, an EECID, and a UE ID of a UE (200). In addition, the resource controller (124) determines whether the credentials of the EAS (110) are valid. In addition, in response to determining that the credentials of the EAS (110) are valid, the resource controller (124) stores the source IP address, the EECID, and the UE ID of the UE (200). In addition, the resource controller (124) identifies the UE (200) based on the received EAS usage indication. In addition, the resource controller (124) reserves (multiple) resources for the EAS (110) associated with the identified UE (200).

[0074] In addition, the resource controller (124) reserves at least one resource, wherein the at least one resource includes at least one of a computing resource for the EAS (110) and a storage resource for the EAS (110). In addition, the resource controller (124) monitors the location of the UE (200) to provide assistance to the EAS (110) for ACR. In addition, the resource controller (124) subscribes to information related to the UE (200) and exposes an application programming interface (API) using a third generation partnership project (3GPP) core network (300) capability.

[0075] In another alternative example embodiment, the resource controller (124) receives the EAS usage indication from the source EES (120) as part of the EEC context.

[0076] Although attached Figure 2BVarious hardware components of the EES (120) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the EES (120) may include fewer or greater numbers of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components may be combined to perform the same or substantially similar functions to provide (multiple) services to the EAS (110) in the EDN (100).

[0077] Figure 3 is a flow chart (300) illustrating a method for providing service(s) to an EAS (110) in an EDN (100) according to embodiments disclosed herein. Steps (302-310) are performed by an EES (120).

[0078] In step 302, the method includes receiving an EAS usage indication from an EEC (220) and / or an EAS (110) and / or a source EES (120) of a UE (200), wherein the EAS usage indication includes a plurality of parameters. In step 304, the method includes determining whether the credentials of a sender (i.e., the EEC (220) and / or the EAS (110) and / or the source EES (120)) are valid. In step 306, the method includes: in response to determining that the credentials of the sender (i.e., the EEC (220) and / or the EAS (110) and / or the source EES (120)) are valid, storing the plurality of parameters. In step 308, the method includes providing (a plurality of) services to the EAS (110) based on the stored plurality of parameters. In step 310, the method includes sending an EAS usage indication confirmation to the EEC (220) and / or the EAS (110) and / or the source EES.

[0079] In alternative embodiments, the EAS usage indication is included as part of another message (such as an ACR information subscription request or an EEC registration message) when sent by the EEC (220), or as an EEC context message when sent by the source EES (120a).

[0080] The various actions, actions, boxes, steps, etc. in the flowchart (300) can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, actions, boxes, steps, etc. can be omitted, added, modified, skipped, without departing from the scope of the present disclosure.

[0081] Figure 4 is a sequence diagram illustrating a method in which the EAS (110) provides an EAS usage indication to the EES (120) according to embodiments disclosed herein.

[0082] In step 401, the EAS (110) sends an EAS usage indication to the EES (120), wherein the EAS usage indication includes the source IP address of the UE (200) available in the AC (210) request to the EAS (110), thereby notifying the new AC (i.e., the UE (200)) that it has connected with the EAS (110). In such a scenario where the AC (210) provides the EAS (110) with an explicit identification of the UE (200) (e.g., UE ID) or an explicit identification of the EEC (220) (e.g., EEC ID), the explicit identification can be included as part of the EAS usage indication sent by the EAS (110) to the EES (120), eliminating the need to identify the UE (200) by converting its IP address into its identifier in step 402. In step 402, the EES (120) further uses the source IP address to identify the associated UE (200) and reserves resources to provide services to the EAS (110), such as location monitoring of the UE, monitoring of the user plane path, etc. In step 403, the EES (120) sends an EAS usage indication confirmation as an acknowledgement of receiving the indication from the EAS (110).

[0083] In an example embodiment, the EES (120) may also infer the use of the UE (200) upon receiving an explicit request for EES services from the EAS (110). For example, the UE monitors requests for service continuity, conversion of IP addresses to UE IDs, and the like.

[0084] In an example embodiment, the EAS (110) may also use the UE ID API to indicate to the EES (120) the use of the EAS (110) by the UE (200). This may also allow the EAS (110) to obtain user consent for the use of a generic public subscription identifier (GPSI).

[0085] In an example embodiment, once the AC (210) has used the services of the EAS (110) and is not interested in further use, the EEC (220) of the UE (200) notifies the EES (120), causing the EES (120) to release the reserved resources.

[0086] In an example embodiment, once service to the AC (210) has completed, the EAS (110) notifies the EES (120). After providing service to the AC (210), the EAS (110) indicates to the EES (120) that the EES (120) no longer needs to monitor the EAS-specific service(s) of the UE (200). This may be accomplished using an explicit API exposed by the EES (120) to the EAS (110).

[0087] Figure 5 is a sequence diagram illustrating a method in which an EEC (220) provides an EAS usage indication to an EES (120) according to an embodiment disclosed herein.

[0088] In an example embodiment, after selecting an EAS (110) from a list of discovered EASs, the EEC (220) sends an explicit indication of the use of the EAS to the EES (120), and the EEC (220) receives information of the selected EAS (110) from the EES (120). The EES (120) then stores the information and reserves resources to provide services to the EAS (110), such as location monitoring of the UE, monitoring of user plane paths, etc. The EES (120) may also subscribe to core network provided capabilities for the UE (200). The request from the EEC (220) to provide an explicit indication of the use of the EAS (110) may also include relevant details of a user of the UE (200) or the EAS (110). For example, the EEC (220) may include a UE identifier and the user's consent for the EAS (110) to use the UE identifier. The EES (120) stores the information to further provide the UE ID to the EAS (110) in consideration of the user's consent.

[0089] Prerequisite: The EEC (220) has discovered and selected the EAS (110) to be used by the AC (210).

[0090] In step 501, the EEC (220) sends an EAS usage indication to the EES (120) where the selected EAS (110) is registered. The EAS usage indication provides the EAS ID and EAS endpoint of the selected EAS and the EEC ID and its credentials. In addition, the EAS usage indication includes the UE ID of the UE and the consent of the relevant user, which the EES (120) can use to further provide services to the EAS (110). The EAS usage indication is shown in Table 1.

[0091]

Table 1

[0092]

[0093] Table 1: EAS usage instructions

[0094] In an example embodiment, the UE ID may be a list of "O" UE identifiers. Furthermore, each identifier may be associated with a specific usage (eg, location).

[0095] At step 502, upon receiving the EAS usage indication, the EES (120) verifies the credentials of the EEC (220). If the credentials of the EEC (220) are valid, the EES (120) stores the provided information (i.e., the EAS usage indication, Table 1), and uses the information to further provide services to the EAS (110), for example, the EES (120) begins monitoring the location of the UE or the user plane path to the EAS (110), thereby providing services (such as assistance in application context relocation).

[0096] At step 503, the EES (120) sends an EAS usage indication confirmation to the EEC (220) to confirm receipt of the EAS usage indication, the EAS usage indication confirmation being shown in Table 2.

[0097]

Table 2

[0098] Information Elements state describe Successful response O This indicates that the UE identifier request was successful. >EES ID M EES Identifier >Security Credentials M EES Security Credentials Failure Response O This indicates that the UE identifier request failed. >Cause O Indicates the reason why the UE identifier request failed

[0099] Table 2: EAS usage indication confirmation

[0100] In an example embodiment, once the AC (210) has consumed the services required by the EAS (110), the AC (210) indicates to the EEC (220), which the EEC (220) further discloses to the EES (120), that the reserved resources and monitoring of the UE (200) may be released because the services of the EAS (110) are no longer being used. The indication may be sent to the EES (120) in an explicit message from the EEC (220), similar to those described above. The EES (120) may release resources associated with the UE's use of the EAS (110) upon receiving the explicit indication.

[0101] Figure 6 1 is a sequence diagram illustrating a method in which an EEC (220) provides an EAS usage indication to an EES (120) as part of another message (such as an ACR information subscription request) according to an embodiment disclosed herein. The ACR information subscription allows the EES (120) to notify the EEC (220) about ACR-related events. The use of the ACR information subscription is merely an example, and any other message exchange between the EEC (220) and the EES (120), such as an EEC registration request / response, can be used for this purpose.

[0102] Prerequisite: The EEC (220) has discovered and selected the EAS (110) to be used by the AC (210).

[0103] In step 601, the EEC (220) sends a request to the EES (120), such as sending an ACR information subscription (i.e., ACR information subscription) or an EEC registration update message to the EES (120) where the selected EAS (110) is registered. The request from the EEC (220) provides the EAS ID and EAS endpoint of the selected EAS (110) and the EEC ID and credentials of the EEC (220). In addition, the request may include the UE ID of the UE and the consent of the relevant user, which the EES (120) can use to further provide services to the EAS (110).

[0104] At step 602, upon receiving the request, the EES (120) verifies the credentials of the EEC (220). If the credentials of the EEC (220) are valid, the EES (120) stores the provided information and uses it to further provide services to the EAS (110). For example, the EES (120) begins monitoring the location of the UE or the user plane path to the EAS (110) to provide services (such as assistance in application context relocation). At step 603, the EES (120) sends an ACR information subscription response to the EEC (220), thereby acknowledging receipt of the request.

[0105] In an example embodiment, the EEC (220) provides a similar indication of completion of use to the EES (120) as part of other messages, such as an EEC registration update, or, where applicable, as part of an EEC deregistration message. The EES (120) releases resources associated with the UE's use of the EAS (110) upon receipt of the indication as part of other messages between the EEC (220) and the EES (120).

[0106] Figure 7 is a sequence diagram illustrating a method in which a source EES (120a) provides an EAS usage indication to a target EES (120b) using an EEC context (ie, information related to an EEC (220) stored at the source EES (120a)) according to embodiments disclosed herein.

[0107] Prerequisite: The EEC (220) is or has moved from one EES (referred to as the source EES (120a)) to another EES (referred to as the target EES (120b)). The EEC (220) or EAS (110) has provided the source EES (120a) with an EAS usage indication.

[0108] When sharing EEC context information, the source EES (120a) includes that information (earlier received from the EEC (220) or EAS (110)) as part of the EEC context sent to the target EES (120b).

[0109] In step 701, the source EES (120a) sends an EEC context to the target EES (120b), which includes details of the EAS (110) being used by the UE (200) and registered at the source EES (120a). In addition, the request may include the UEID of the UE and the consent of the relevant user, which the target EES (120b) can use to further provide services to the EAS (110).

[0110] In step 702, upon receiving the EEC context, the target EES (120b) verifies the credentials of the source EES (120a). If the credentials of the source EES (120a) are valid, the target EES (120b) stores the provided information and further uses the information to provide services to the EAS (110). For example, the target EES (120b) begins monitoring the location of the UE or the user plane path to the EAS (110) to provide services (such as assistance in application context relocation). In step 703, the target EES (120b) sends an EEC context confirmation to the source EES (120a), thereby confirming the receipt of the EEC context.

[0111] In an example embodiment, the source EES (120a) may also infer completion of use of the EAS (110) based on the participation of the EAS (110) in the application context relocation process. Once the application context relocation process is complete, the source EES (120a) releases resources associated with UE use of the EAS (110).

[0112] In an alternative embodiment, the target EES (120b) may also infer the use of the EAS (110) based on the participation of the EAS (110) in the application context relocation process. The target EES (120b) reserves resources required to provide services (such as monitoring the location of the UE, monitoring the user plane path, etc.) to the EAS (110) when participating in the ACR process.

[0113] Figure 8 is a block diagram of a first electronic device according to an embodiment of the present disclosure. Figure 1-Figure 7 As shown, the first electronic device may correspond to, for example, a UE, (multiple) ACs in a UE, or an EEC in a UE.

[0114] refer to Figure 8 , the first electronic device may include a transceiver 810, a controller 820, and a storage device 830. In the present disclosure, the controller 820 may include a circuit, an ASIC, or at least one processor.

[0115] The transceiver 810 may transmit and receive signals to and from another electronic device.

[0116] According to an embodiment, the controller 820 may control the overall operation of the first electronic device. For example, the controller 820 may control the signal flow to perform the above Figure 1-Figure 7 For example, the control unit 820 may perform at least one operation on the EAS usage indication.

[0117] The storage device 830 may store at least one of information exchanged through the transceiver 810 and information generated by the controller 830 .

[0118] Fig. 9 is a block diagram of a second electronic device according to an embodiment of the present disclosure. The second electronic device may correspond to, for example, Figure 1-Figure 7 (multiple) EAS, (multiple) EES or (multiple) ECS in.

[0119] refer to Fig. 9 , the second electronic device may include a transceiver 910, a controller 920, and a storage device 930. In the present disclosure, the controller 920 may include a circuit, an ASIC, or at least one processor.

[0120] The transceiver 910 may transmit and receive a signal to and from another electronic device.

[0121] According to an embodiment, the controller 920 may control the overall operation of the second electronic device. For example, the controller 920 may control the signal flow to perform the above Figure 1-Figure 7 For example, the control unit 920 may perform at least one operation on the EAS usage indication.

[0122] The storage device 930 may store at least one of information exchanged through the transceiver 910 and information generated by the controller 930 .

[0123] The embodiments disclosed herein may be implemented using at least one hardware device and executing a network management function control element.

[0124] The foregoing description of specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, easily modify and / or adapt such specific embodiments for various applications without departing from the general concepts, and therefore, such adjustments and modifications should and are intended to be understood within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the words or terms used herein are for descriptive and not limiting purposes. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the scope of the embodiments described herein.

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

Claims

1. A method for a user equipment UE including an edge enabler client EEC in an edge data network EDN, the method comprising: The EEC selects an EAS used by the application client AC of the UE from at least one discovered edge application server EAS; The EEC sends a first message indicating an application context relocation ACR information subscription request to the edge enabling server EES, wherein the first message includes an identifier ID of the selected EAS; and A second message indicating an ACR information subscription response in response to the first message is received by the EEC from the EES.

2. The method according to claim 1, wherein: The second message includes at least one of information indicating a successful response, information indicating an ID EESID of the EES, information indicating a security credential of the EES, information indicating a failed response, or information indicating a failure reason.

3. The method according to claim 1, wherein: The selected EAS having the ID of the selected EAS receives the service associated with the ACR from the EES.

4. The method according to claim 1, wherein: At least one parameter in the first message is stored by the EES based on the EEC determining that the credentials of the EEC are valid.

5. The method according to claim 1, wherein: The first message further includes at least one of information indicating an ID of the EEC, information indicating security credentials of the EEC, or information indicating an ID of the UE.

6. The method according to claim 1, wherein: The AC of the UE establishes a connection with the selected EAS for service.

7. A user equipment UE in an edge data network EDN, the UE comprising: Application client AC; as well as Edge Enabler Client EEC, wherein the EEC is configured to: Selecting an EAS to be used by the AC from at least one discovered edge application server EAS; Sending a first message indicating an application context relocation ACR information subscription request to an edge enabling server EES, wherein the first message includes an identifier ID of the selected EAS; and A second message indicating an ACR information subscription response in response to the first message is received from the EES.

8. The UE according to claim 7, wherein: The second message includes at least one of information indicating a successful response, information indicating an ID EESID of the EES, information indicating a security credential of the EES, information indicating a failed response, or information indicating a failure reason.

9. The UE according to claim 7, wherein: The selected EAS having the ID of the selected EAS receives the service associated with the ACR from the EES.

10. The UE according to claim 7, wherein: At least one parameter in the first message is stored by the EES based on the EEC determining that the credentials of the EEC are valid.

11. The UE according to claim 7, wherein: The first message further includes at least one of information indicating an ID of the EEC, information indicating security credentials of the EEC, or information indicating an ID of the UE.

12. The UE according to claim 7, wherein: The AC is configured to establish a connection with the selected EAS for service.

Images