Method and apparatus for generating and removing dynamic EAS using a UE APP and status

Abstract

A communication technology for combining a 5G communication system that supports higher data transfer rates than 4G systems with IoT technology is disclosed. The present disclosure relates to a wireless communication system, and more particularly, to an application layer network architecture that provides edge computing services in a cellular wireless communication system. According to an embodiment, a method of an EES includes receiving a first message from an EEC that includes information for determining a matching EAS, and triggering an EAS management system to instantiate the matching EAS in response to receiving the first message.

Description

Technical Field

[0001] The present disclosure relates to an apparatus and method for providing edge computing services, and more particularly, to an apparatus and method for providing edge computing services in a wireless communication system. Background Art

[0002] In order to meet the demand for wireless data services since the 4G communication system entered the market, efforts are being made to develop an enhanced 5G communication system or a pre-5G communication system. Therefore, the 5G communication system or the pre-5G communication system is referred to as a super 4G network communication system or a post-LTE system.

[0003] For higher data transmission rates, it is considered to implement the 5G communication system in the super high frequency band (mmWave) (such as, for example, 60 GHz). In order to mitigate the path loss in the super high frequency band and increase the reach of radio waves, the following technologies are considered for the 5G communication system: beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antennas.

[0004] Various technologies for the 5G communication system are also being developed to have an enhanced network, such as evolved or advanced small cells, cloud radio access network (cloud RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-point (CoMP), and interference cancellation. There are also various other solutions developed for the 5G system, including, for example, hybrid FSK and QAM modulation (FQAM) and sliding window superimposed coding (SWSC) as advanced coding modulation (ACM) schemes, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access schemes.

[0005] The Internet is evolving from a human-centered connected network where humans create and consume information to an Internet of Things (IoT) network that communicates, transfers, and processes information between things or other distributed components. Another emerging technology is the Internet of Everything (IoE) which is a combination of big data processing technology and IoT technology through connection with a cloud server. In order to implement the IoT, technical elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, object-to-object connection technologies such as sensor networks, machine-to-machine (M2M), or machine type communication (MTC) are being studied.

[0006] In the IoT environment, intelligent Internet technology (IT) services can be provided, which collect and analyze data generated by things connected to each other to create new value for human life. By transforming or integrating existing information technology (IT) technologies and various industries, IoT can have various applications, such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare or smart home appliance industries, or state-of-the-art medical services.

[0007] Therefore, various efforts are being made to apply the 5G communication system to the IoT network. For example, sensor networks, machine-to-machine (M2M), machine type communication (MTC), or other 5G technologies are implemented through schemes such as beamforming, multiple input multiple output (MIMO), and array antenna schemes. The above application of cloud radio access network (RAN) as a big data processing technology can be said to be an example of the integration of 5G and IoT technologies.

[0008] Meanwhile, the 3GPP, which is responsible for the standardization of cellular mobile communications, has named and standardized a new core network architecture as 5G Core (5GC) to facilitate the evolution from the traditional fourth-generation long-term evolution (4G LTE) system to the 5G system.

[0009] Compared with the evolved packet core (EPC), which is the core of the traditional network as 4G, 5GC can support the following different functions.

[0010] First of all, 5GC adopts the network slicing function. 5GC is needed to support various types of UEs and services. For example, such services can include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC).

[0011] These UEs / services have different requirements for the core network. For example, eMBB services may require high data rates, while URLLC services may require high stability and low latency. Network slicing is a technology provided to meet such various requirements.

[0012] Network slicing is a method for creating multiple logical networks by virtualizing a physical network, and network slice instances (NSIs) can have different characteristics. Therefore, by allowing each NSI to have network functions (NFs) suitable for the characteristics of each NSI, various service requirements can be met. Therefore, by allocating an NSI that meets the required service characteristics to each UE, various 5G services can be effectively supported.

[0013] Second, by separating the mobility management function and the session management function, the 5GC can seamlessly support the network virtualization paradigm. In traditional 4G LTE, all UEs can receive services on the network through signaling exchange with a single core device called the Mobility Management Entity (MME) responsible for registration, authentication, mobility management, and session management functions. Summary of the Invention

[0014] Technical Problem

[0015] However, in 5G, the number of UEs has increased explosively, and the mobility and service / session characteristics that need to be supported according to the type of UE have been segmented. As a result, if all functions are supported by a single device (such as the MME), the scalability of adding entities for each required function may decrease. Therefore, based on the structure of separating the mobility management function and the session management function, various functions are being developed to enhance the scalability of the core equipment responsible for the control plane and signaling load in terms of function / implementation complexity.

[0016] Solution to the Problem

[0017] According to an embodiment, a device and method for providing edge computing services in a wireless communication system are provided.

[0018] According to an embodiment, a method and device for dynamic EAS instantiation using the UE app state are provided.

[0019] According to an embodiment, a method and device that can instantiate an EAS associated with a UE's app when the UE uses the app are provided.

[0020] According to an embodiment, a method and device for reporting the AC state for instantiating an EAS associated with a UE's AC are provided.

[0021] According to an embodiment, a method of an EES includes: receiving a first message including information for determining a matching EAS from an EEC; and in response to receiving the first message, triggering an EAS management system to instantiate the matching EAS.

[0022] According to an embodiment, an EES includes: a transceiver; and a processor configured to control the transceiver to receive a first message including information for determining a matching Edge Application Server (EAS) from an Edge Enablement Client (EEC); and in response to receiving the first message, trigger an EAS management system to instantiate the matching EAS.

[0023] Before proceeding with the following detailed implementation, it may be advantageous to clarify the definitions of certain words and phrases used throughout this patent document: The terms "comprise" and "include" and their derivatives mean inclusion without limitation; the term "or" is inclusive and means and / or; the phrases "associated with" and "associated therewith" and their derivatives can mean include, be included within, be interconnected with, contain, be contained within, be connected or connected to, be coupled or coupled with, be communicable with, cooperate with, be intertwined, be juxtaposed, be adjacent, be combined or combined with, have, have the property of, etc.; and the term "controller" means any device, system, or part thereof that controls at least one operation, and such a device can be implemented in hardware, firmware, software, or some combination of at least two of them. It should be noted that the functions associated with any particular controller can be centralized or distributed, whether locally or remotely.

[0024] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by 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, sets of instructions, procedures, functions, objects, classes, instances, related data, or a part thereof that are suitable for implementation in appropriate computer-readable program code. 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 read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of memory. A "non-transitory" computer-readable medium does not include wired, wireless, optical, or other communication links that transmit transient electrical signals or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and then overwritten, such as rewritable optical discs or erasable memory devices.

[0025] Throughout this patent document, definitions of certain words and phrases are provided, and those of ordinary skill in the art should understand that in many instances, if not most instances, such definitions apply to the prior and future use of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] When considered in conjunction with the accompanying drawings, a more complete appreciation of the present disclosure and many of its attendant aspects will be readily obtained by reference to the following detailed description, in which:

[0027] Figure 1Shows an application network architecture and interface supporting edge computing according to an embodiment of the present disclosure;

[0028] Figure 2 Is a flowchart showing the subscription request process of the AC status and AC service status reports according to Embodiment 1 of the present disclosure;

[0029] Figure 3 Is a flowchart showing the process of detecting and reporting the AC status and AC service status according to Embodiment 2 of the present disclosure;

[0030] Figure 4A and Figure 4B Is a flowchart showing the process of the AC status and AC service status reports during the EEC registration process according to Embodiment 3-1 of the present disclosure;

[0031] Figure 5 Is a flowchart showing the process of dynamically instantiating the EAS by the EES according to Embodiment 3-2 of the present disclosure;

[0032] Figure 6 Is a flowchart showing the state transition of the UE app status according to the user's work according to Embodiment 4 of the present disclosure;

[0033] Figure 7 Is a flowchart showing the state transition of the UE app service status according to Embodiment 5 of the present disclosure;

[0034] Figure 8 Is a block diagram showing the configuration of the UE according to various embodiments of the present disclosure; and

[0035] Figure 9 Is a block diagram showing the configuration of the server according to various embodiments of the present disclosure. Detailed Description of the Embodiments

[0036] The following discussion Figures 1 to 9 And the various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be construed in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0037] Hereinafter, embodiments of the present disclosure are described in detail with reference to the accompanying drawings. When it is determined that the subject matter of the present disclosure is unclear, the detailed description of known technologies or functions may be skipped. The terms used herein are defined in consideration of the functions in the present disclosure and may be replaced with other terms according to the intention or practice of the user or operator. Therefore, these terms should be defined based on the entire present disclosure.

[0038] In the following, a base station may be an entity that allocates resources to a terminal, and may be at least one of an eNodeB, a Node B, a base station (BS), a radio access network (RAN), an access network (AN), a RAN node, a radio access unit, a base station controller, or a node on a network. A terminal may include a UE (user equipment), an MS (mobile station), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. According to the present disclosure, a downlink (DL) may refer to a wireless transmission path of a signal sent from a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal sent from a terminal to a base station.

[0039] Although the post-LTE system is described below in conjunction with embodiments of the present disclosure, as an example, embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel form. In addition, under the determination of those of ordinary skill in the art, embodiments of the present disclosure may be modified within such an interval without significantly departing from the scope of the present disclosure, and such modifications may be applicable to other communication systems (e.g., LTE or LTE-A systems).

[0040] Figure 1 An application network architecture 100 supporting edge computing according to an embodiment of the present disclosure is shown.

[0041] Reference Figure 1 , the UE 101 may include at least one application client (AC) 102 and an edge enabling client (EEC) 103. When providing edge computing services, the application client 102 may be an application-level client for providing to users.

[0042] In addition, the UE 101 may include a communication processor (CP) for communicating with another wireless communication network (e.g., at least one or more mobile communication networks) ( Figure 1 not shown in

[0043] The 3GPP network 104 is shown as a representative of a mobile communication network and may include, for example, an EPC and / or a 5GC. The 3GPP network 104 may include a base station that communicates directly with the UE 101 via Over-The-Air (OTA), and may include a higher-level core network configuration. When the 3GPP network includes a 5GC, it may include an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), and a user plane function (UPF).

[0044] In addition, when having an EPC as a core network (CN), it may include network nodes corresponding to the 5GC.

[0045] The edge data network can be implemented through network slicing technology, and all edge data networks can be configured in the same form. The configuration of an edge data network 105 is described as an example, which may include an edge hosting platform, and may include an Edge Enablement Server (EES) 107, one or more Edge Application Servers (EAS) 106, and an orchestrator for the edge hosting platform. The Edge Enablement Server 106 may include an edge enablement client manager, an edge enablement platform, and an edge enablement application programming interface (API) server.

[0046] Network functions can be defined as follows, some of which are shown in Figure 1 as follows.

[0047] The 3GPP network 104 may include a 3GPP Radio Access Network (RAN) and a core network.

[0048] One or more edge data networks 105 are data networks of the 5G core network or packet data networks of the EPC network, and may be data networks including functions for providing edge computing services (such as an edge hosting platform edge enablement server).

[0049] The Application Client (AC) 102 may be an application running on the mobile operating system of the UE 101, and may be identified by an application identifier on the 5G core network. In an environment providing a mobile operating system, the AC may be identified by an operating system (OS) identifier and a unique application identifier (OSAppID) for each OS.

[0050] One or more edge application servers 106 may be application server programs running on virtualized containers or virtual machine (VM) images operating in an edge hosting environment, and may be server programs executed when the VM image is instantiated, and may be referred to as edge applications.

[0051] The edge configuration server 108 may be a server that provides configuration information about the edge data network 105 to the UE 101, and may be an initial access server that can receive configuration information for the UE 101 to use Mobile Edge Computing (MEC) services.

[0052] The edge hosting platform may be platform software including a virtualization layer that can execute multiple edge applications. In the present disclosure, the terms "edge hosting platform" and "edge hosting environment" have the same concept and may be used interchangeably.

[0053] The orchestrator of the edge hosting platform can be a management system that manages the lifecycle of edge applications running on the edge hosting platform and manages the edge hosting platform. It can perform the functions of an orchestrator defined in the European Telecommunications Standards Institute Management and Network Operations (ETSI MANO).

[0054] The Edge-Enabled Server (EES) 107 can be a server for providing edge computing services, and can be a server that provides a list of applications available on the edge hosting platform (Edge-Enabled Client Manager) to the UE 101, manages configuration information regarding edge applications operating on the edge computing hosting platform, and provides an API for functions provided to edge applications from the 3GPP network.

[0055] The Edge-Enabled Client (EEC) 103 can be a software module of the UE 101, and can be a software agent having functions for providing edge computing services. It can perform an authentication function for the UE to access the edge computing server, and it can be a software agent through which the UE 101 receives information provided from the edge hosting platform when interacting with the Edge-Enabled Server 107, performs routing required for UE applications, and provides information to UE applications.

[0056] As Figure 1 shown, the application network architecture for supporting edge computing can be managed by an edge computing service provider separate from the mobile communication service provider, and there can be multiple separate edge computing service providers in one mobile communication service provider network. As Figure 1 shown, the application network architecture for supporting edge computing can support the configuration of service providers.

[0057] In Figure 1 the application network architecture shown can support multiple edge computing service providers in one mobile communication network. The application network architecture can deliver multiple edge computing service providers available in one mobile communication network and configuration information for accessing the edge computing network installed by the service provider to the UE.

[0058] In Figure 1 the application network architecture shown can deliver the edge network service provider selected by the mobile communication service provider among multiple edge computing service providers existing in one mobile communication network and configuration information for accessing the edge computing network installed by the selected edge network service provider to the UE.

[0059] Various embodiments of the present disclosure are described below. The present disclosure may relate to a method and apparatus for providing two scenarios for a service provider to install a flexible edge network and implement the network.

[0060] In an embodiment 1 of the present disclosure, due to the AC status from EAS, such as AC installation, startup, or user actions, it provides a service subscription process for app screen control change, app service detection, and app Domain Name System (DNS) request detection reports.

[0061] Figure 2 It is a flowchart showing the subscription request process 200 of the AC status and AC service status report according to Embodiment 1 of the present disclosure.

[0062] Refer to Figure 2 , EAS 201 transmits a request for AC status / status change report and / or AC service status / status change report to EES 202 (e.g., operation 211).

[0063] In this case, the status report request message can be a one-time report request, or it can be a report request for the status change of a specified AC for each EEC (or for each GPSI).

[0064] When EES 201 receives a request for AC status / status change and / or AC service status / status change, if the request is not a one-time request, EES 201 receives a list of target UEs or target EECs, the AC status / status change and / or AC service status / status change report, and expiration conditions, assigns a transaction identifier to the corresponding report, and records such information. When the corresponding event report is received in the future, the information that can identify the requester of the event report is retained together.

[0065] When the event subscription is successfully completed, EES 202 passes a response message to the report request to EAS201 (e.g., operation 213). When the report is not a one-time report and the event report conditions and expiration conditions are included in the request message, the transaction identifier information that can identify the subscription request assigned in operation 212 can be included and transmitted.

[0066] According to the embodiment, EES 202 that has received the status reports of multiple ACs from one or more EECs identifies the status of the ACs of one or more EECs requested from EAS 201 (e.g., operation 212). EES 202 reports the identified AC status of the EECs to EAS 201. In this case, EES 202 transmits an AC status report including information about the AC status and / or EEC that matches the conditions of the requested AC and AC status to EAS 201 together with the response message of operation 214.

[0067] When the EAS 201 that receives the AC status report including information about the AC status and / or EEC (and UE) is an orchestrator, the orchestrator can use the status information about the relevant AC when instantiating, load balancing, horizontally scaling, or horizontally scaling down the EAS.

[0068] The EES 202 that transmits the response message in operation 213 can perform the subscription request process described in conjunction with operations 215 and 216 (e.g., operation 214) on the AC status report or AC service status report regarding at least one EEC 203 for the registered EEC.

[0069] The EES 202 transmits a subscription request message for the AC status information to the EEC 203 (e.g., operation 215). The subscription request message for the AC status and / or AC service status information report includes at least one of an AC list, an AC status report event list, edge awareness information of the AC, EAS service area information, AC status report type, AC status report indicator, AC status report subscription information, or AC status trigger condition.

[0070] The subscription request message can also include whether the report is a one-time report or a continuous report, and if the report is a continuous report, it can also include the conditions for completing the report (e.g., the maximum number of reports, the time period during which the maximum number of reports can be made, and the number of occurrences of events within the report completion time). The AC status report event list can include AC status information and AC status change information, as well as AC service status and AC service status change information, through which it is possible to predict whether traffic is generated between the AC and the EAS. For example, the AC status information is described below in conjunction with Embodiment 4. The status information of the AC service is described below in conjunction with Embodiment 5.

[0071] Upon receiving the subscription request message for the AC status information report, if the subscription request for the AC status information report of the EES 202 is successfully registered, the EEC 203 sends a response message to the EES 202 for the subscription request message (e.g., operation 216). When the subscription request for the AC status information report is a one-time request, the EEC 203 can send the AC status information together with the response message.

[0072] In an embodiment 2 of the present disclosure, according to the AC status and the AC status change reporting service and / or the AC service status and the AC service status change reporting service subscribed in embodiment 1 of the present disclosure, when the AC status is changed to a status that matches the reporting condition, a process of providing the EEC with reporting the status of the AC to the EES that has requested the AC status report is provided. When receiving a report of a change in the AC status of the UE, the EES reports the current AC status change of the UE to the EAS that has requested the AC status change report. The AC status change report can be used by the orchestrator to generate a new instance (instantiate) for the EAS or remove an existing generated instance.

[0073] Figure 3 FIG. 4 is a flowchart showing a process 300 of detecting and reporting the AC status and the AC service status according to Embodiment 2 of the present disclosure.

[0074] Referring Figure 3 to FIG. 4, the EEC 303 may obtain the AC status and / or the AC service status, or detect a change in the AC status or a change in the AC service status (e.g., operation 311). A change in the AC status refers to a change in the AC status on the mobile operating system due to a user's action. The AC status and the status change may have a status having the following attributes as shown in Embodiment 4 of the present disclosure described below. Figure 6 and the status shown in Embodiment 4 of the present disclosure described below.

[0075] - A status according to whether the AC 302 is installed on the mobile operating system in the UE 301.

[0076] - A status according to whether the AC 302 is executed on the mobile operating system in the UE 301.

[0077] - A status divided into a foreground or background status or a visible or invisible status according to whether the AC 302 is displayed on the user screen of the mobile operating system, whether the AC 302 has the right to control the user screen, or whether the AC 302 has the right to control user interaction.

[0078] A change in the AC status may have the characteristic of status movement, in which the AC 302 generated by the user's action on the mobile operating system is installed, executed, paused, terminated, and the AC 302 is moved to the foreground screen or the background screen.

[0079] As an example of a status having the characteristics of the AC status and the status change, there may be a status and a status transition method in Embodiment 4 described below.

[0080] In Figure 2In operation 215, when receiving a report request for a status change of the AC, the EEC 303 can detect the status change of the AC, such as installation, start of execution, stop of execution, termination, or change to a visible or invisible state of the requested AC.

[0081] When, in Figure 2 operation 215, the movement of the AC to a specific state is requested as a reporting condition, the EEC can detect the movement of the AC to the specific state.

[0082] The AC service state and state change can have a state with the following attributes including as Figure 7 shown in Example 5 described below.

[0083] - A state regarding whether application services can be generated without user intervention. Examples of such states can be classified as application services not ready or application services ready.

[0084] - A state regarding whether the application is installed on the UE's operating system or executed on the mobile operating system. Examples of such states can be classified as application unavailable, application inactive, and application services ready.

[0085] - An application service generation state, which can be classified as whether application services are about to be generated, whether they have been generated, or whether it is a dormant period during which no services are generated. Examples of such states can include application service dormant, application service arrival, and application service exchange.

[0086] The AC service state change can have the characteristic that the service generation or generation preparation of the AC is detected and the state movement of the state movement is detected. Examples of states with the characteristics of the AC service state and state transition can have the states and state transition methods in Example 5 described below.

[0087] In Figure 2 operation 215, when receiving a request to report the status change of the AC service, the EEC 303 can detect a change in the AC service ready state (e.g., a change from AC service not ready to AC service ready), or a change in the AC service state between the AC service dormant, AC service arrival, and AC service generation states. For example, when a DNS query occurs from the AC or a DNS query to the destination EAS occurs, the AC service dormant state can transition to the application service arrival state. When application services generated from the AC are detected, or when the generation of application services from the AC to the destination EAS is detected, the application service dormant state is changed to the application service exchange state.

[0088] When in Figure 2When the movement of the AC service state to a specific state is requested in operation 215 as a reporting condition, the EEC 303 can detect the movement of the AC to the specific state.

[0089] When detecting the movement of the AC state to a state that satisfies the reporting condition, the change of the AC state, the movement of the AC service state to a state that satisfies the reporting condition, or the change of the AC service state, the EEC 303 can send an AC state / state change and / or an AC service state / state change report message to the EES 304 (e.g., operation 312). The AC state and / or the AC service state report message can include an EEC identifier, a list of AC identifiers to be reported, a differentiator for distinguishing the transaction of the subscription request from other transactions, AC state information per AC identifier, AC service state information per AC identifier, AC previous state information per AC identifier when the AC state is changed, the previous state information of the AC service per AC identifier when the AC service state is changed, the identifier of a specific EAS or the fully qualified domain name (FQDN) information of a specific EAS when the service uses a specific EAS as the destination, IP address information, or uniform resource locator (URL) information. The AC state / state change report and / or the AC service state / state change report message can be transmitted together with the EAS discovery process.

[0090] According to an embodiment, when receiving a report of the AC state / state change and / or the AC service state / state change from the EEC 303, the EES 304 can request the orchestrator and execute a preset process (e.g., operation 313). The preset process can include an operation of calling an API that manages the lifecycle of the EAS 305, an operation of reporting the AC state / state change and / or the AC service state / state change of the AC of the UE at a specified location, or an operation of determining and reporting the horizontal expansion or horizontal reduction on the EAS corresponding to the AC. In addition, the preset process can include at least one of an operation of instantiating an EES instance according to the AC state / condition change and / or the AC service state / condition change of the orchestrator operating as an EAS, an operation of additionally instantiating the EES instance, or an operation of deleting the EES instance. When operation 313 is executed, operations 211 and 214 of Figure 2 can be omitted.

[0091] When receiving the AC status / status change and / or AC service status / status change from the EEC 303, the EES 304 reports at least one of the AC status information, AC status change information, AC service status information, or AC service status change information to the EAS 305 or the orchestrator that has requested the report of the AC status / status change and / or AC service status / status change (e.g., operation 314). The EES 304 may provide a report to the orchestrator including information about the EAS 305 corresponding to the AC 302. The EAS 305 corresponding to the AC 302 means the application server that provides services for the AC 302.

[0092] When receiving the AC status / status change and / or AC service status / status change report, the orchestrator may obtain the information of the EAS 305 corresponding to the AC 302 and perform operations such as generating, adding, and deleting EAS instances (e.g., operation 315).

[0093] In an embodiment 3-1, the EES receives a subscription request for the AC status and AC service status reports of the UE from the EAS, and the EES records the subscription request.

[0094] When the EEC registers in the EES, the EES identifies whether the EEC belongs to the target of the AS status and / or AC service status report, and if the EEC belongs to the target of the report, the EES passes a registration response message to the EEC, which includes a target AC list, conditional information of the target AC, whether the report request is a one-time status report request, report conditions including conditions and expiration conditions, and an identifier for identifying the report subscription. When receiving the AC status / status change and / or AC service status / status change report from the EEC, the EES passes the reported status to the EAS or the orchestrator that requested the report. The EES may directly determine the increase / decrease and instantiation of the number of instances of the EAS corresponding to the AC, or pass a message to the orchestrator to perform a process for determining whether to instantiate the EAS or whether to increase or decrease the number of instances of the EAS.

[0095] Figure 4A and Figure 4B is a flowchart showing the AS status and / or AC service status reporting process during the EEC registration process according to Embodiment 3-1 of the present disclosure.

[0096] Refer to Figure 4A and Figure 4B , the EAS 401 transmits a request for the AC status / status change report and / or AC service status / status change report to the EES 402 (e.g., operation 411).

[0097] In this case, the status report request message can be a one-time report request, or can be a report request for the status change of the designated AC for each EEC (or for each GPSI).

[0098] When the EES 402 receives a request for the AC status / status change and / or the AC service status / status change, if the request is not a one-time request, the EES 201 receives a list of target UEs or target EECs, the report of the AC status / status change and / or the AC service status / status change, and the expiration condition, assigns a transaction identifier to the corresponding report, and records such information (operation 412). When the corresponding event report is received in the future, the information that can identify the requester of the event report is retained together.

[0099] When the event subscription is successfully completed, the EES 402 passes the response message to the EAS 401 for the report request (for example, operation 413). When the report is not a one-time report and the event report condition and the expiration condition are included in the request message, the transaction identifier information that can identify the subscription request and is assigned in operation 412 can be included and passed.

[0100] According to an embodiment, the EES 402 that has received the status reports of multiple ACs from one or more EECs identifies the status of the ACs of one or more EECs requested from the EAS 401 (for example, operation 212). The EES 202 reports the identified AC status of the EEC to the EAS 201. In this case, the EES 202 passes the AC status report including the information about the AC status and / or the EEC that matches the conditions of the requested AC and the AC status to the EAS 201 together with the response message of operation 413.

[0101] The EEC 403 executes the process registered in the EES 402 according to the specified conditions. When the UE moves to the area where the EES 402 is provided, or when the EEC receives the selection information of the EES from the ECS and the EEC selects the EES, as the specified conditions, the EEC403 executes the process registered in the EES 402. When the EEC 403 executes the process registered in the EES 402, the EEC 403 can include all or some of the AC list installed on the UE in the registration request message and pass them (operation 414). The EEC 403 in the UE can include at least one of the AC identifier, the EEC type (an indicator of whether the EEC is downloadable or embedded), an indicator of whether the AC status / status change and / or the AC service status / status change report function is supported, the supported AC status / status change and / or the AC service status / status change list, or the mobile operating system identifier in the registration request message and pass it to the EES 402.

[0102] The EES 402 receives a registration request message from the EEC 403. Upon receiving the registration request message, the EES 402 may identify the available EAS list corresponding to each AC list. In addition, the EES 402 may identify whether the EEC 403 belongs to the target of the AS status and / or AC service status report. Whether the EEC 403 belongs to the target of the report can be identified by the following information:

[0103] - EEC identifier;

[0104] - Identifier of the UE equipped with the EEC. For example, the number of the UE device, such as the Permanent Equipment Identifier (PEI);

[0105] - Subscriber information of the UE equipped with the EEC, (Generic Public Subscription Identifier (GPSI));

[0106] - Location information of the UE (e.g., location information in 3GPP or Data Network Access (DNA) identifier, GPS coordinate information or address information, such as lot number, building number, etc.);

[0107] - Service area information of the UE; and / or

[0108] - IP address information of the UE.

[0109] When the EEC 403 belongs to the target of the report, the EES 402 designates a target AC for the UE. The target AC may include a list of the AC identifier or condition information of the target AC. The conditions of the target AC may include the following examples:

[0110] – Information where the AC ID is represented by a regular expression between the AC installed on the UE or the running AC, such as com.example

[0111] - List of newly installed ACs on the UE;

[0112] - List of newly executed ACs on the UE;

[0113] - List of all ACs in the visible state among the apps currently running on the UE; and

[0114] - List of ACs that have changed from the invisible state to the visible state among the apps currently executed on the UE.

[0115] When the EEC 403 is the target of the report, the EES 402 sends a response message to the EEC 403 for the registration request (operation 416). The response message includes at least one of an AC list, an AC status report event list, edge awareness information of the AC, EAS service area information, an AC status report type, an AC status report indicator, AC status report subscription information, or an AC status trigger condition.

[0116] Upon receiving the response message, the EEC 403 identifies whether the report is a one-time report, and if the report is a one-time report, the EEC 403 performs the report only once.

[0117] If there are reporting conditions, the EEC 403 records the identifier for identifying the EEC subscription request, the reporting conditions, and the expiration conditions, and records the conditions for triggering the reporting conditions and the expiration conditions.

[0118] The EEC 403 identifies the reporting conditions of the currently installed AC (operation 417).

[0119] For the installed AC, the EEC 403 identifies the reporting conditions, and when the reporting conditions are met, passes the AS status report and / or AC service status report message to the EES 402 (operation 418). The message passed to the EES 402 may include at least one of an EEC identifier, a list of AC identifiers to be reported, a differentiator for distinguishing the transaction for which the subscription is requested from other transactions, AC status information per AC identifier, the previous AC status per AC identifier when the AC is changed, the AC service status per AC identifier, or the previous AC service status information per AC identifier when the AC service is changed. When the reporting conditions are met and the reporting request is a one-time request, the report is performed only once. When the reporting request received from the EES 402 is not a one-time request and it includes reporting conditions and expiration conditions, the EEC 403 may record the reporting request and perform operation 418 when the reporting conditions are met. When an event that meets the report expiration condition occurs, no further reporting is performed and the recorded reporting request is deleted.

[0120] When the EAS 401 or the orchestrator requests an AC status / status change and / or an AC service status / status change report through operation 411, the EES 402 may pass the information reported from the EEC 403 to the corresponding EAS 401 or the orchestrator (operation 420-1). The EAS 401 or the orchestrator may receive an AC status / status change and / or an AC service status / status change report from the EES 402 and determine the operations for generating, adding, deleting, upgrading, or downgrading the EAS instances related to the AC (e.g., operation 420-2).

[0121] According to an embodiment, when receiving the AS status / status change and / or AC service status from the EEC 403, the EES 402 may execute a preset procedure (e.g., operation 419). The preset process may include an operation of calling an API that manages the life cycle of the EAS 401, or an operation of performing an AC status / status change and / or AC service status / status change report on the AC of the UE at a specified location. When operation 419 is executed by the EEC 402, operations 411 and 413 may be omitted.

[0122] When the preset process in the EES 402 includes an operation of adding, generating, or deleting an EAS instance according to the AC status / status change and / or AC service status / status change, the EES 402 may determine whether to scale out or scale in the EAS corresponding to the AC (e.g., operation 421-1). Scaling out is an operation for increasing the number of EAS instances, and scaling in is an orchestration operation for reducing the number of EAS instances of the EAS 401. The EES 402 may send a request for the determined scaling out or scaling in to the EAS 401 or the orchestrator (e.g., operation 421-2).

[0123] When reporting the AC status / status change and / or AC service status / status change according to the preset procedure, the EES 402 may perform context registration or release on the EAS 401 corresponding to the orchestrator (e.g., operation 422). For example, when the AC status event reported from the EEC403 is an AC start event or an AC service about-to-start event, it may perform a context registration or release process on the EAS401 corresponding to the AC. The orchestrator receiving the request for context registration or release of the EAS 401 may generate a new EAS instance, or perform a function of increasing or decreasing the number of existing EAS instances.

[0124] In an embodiment 3-2 of the present disclosure, a method for allowing the EAS corresponding to the AC to be dynamically instantiated is provided, in which the EES receives an AC profile (including an AC ID) associated with the EAS through a registration request from the EAS, determines a trigger condition for the EEC to send a discovery request when the EEC transmits the registration request, sends the trigger condition for performing EAS discovery to the EEC, and then receives an EAS discovery request message from the EEC that detects a status change of the AC.

[0125] Figure 5 is a flowchart showing the process of dynamically instantiating the EAS by the EES according to Embodiment 3-2 of the present disclosure.

[0126] Reference Figure 5, EAS 501 sends a registration request message to EES 502 to perform an EAS registration process (e.g., operation 511). According to an embodiment, when the EAS that can be instantiated is managed in an edge hosting environment, the EAS registration process may be performed by an orchestrator that manages the edge hosting environment rather than the EAS. In this case, the EAS registration process may be performed by an orchestrator that manages the lifecycle of EAS 501 through the edge hosting environment on behalf of EAS 501. When the orchestrator performs the registration process, the EAS ID does not refer to the ID of a specific instance, but may collectively refer to multiple instantiated EAS instances. When the orchestrator performs the registration process, the EAS ID refers to the aggregated EAS, and multiple instantiated EAS entities have the same EAS ID. According to another embodiment, the registration process performed by EAS 501 on EES 502 may be performed by a newly instantiated EAS. In this case, the EAS registration process may be performed to register a newly instantiated EAS instance to allow EES 502 to discover another EES or EAS instance available to EEC 503. The registration request message sent from EAS 501 to EES 502 may include at least one of the EAS ID or information about the AC for which EAS 501 provides services (i.e., AC profile). The AC profile may include additional information about the AC as well as the AC ID. In addition, the registration request message sent from EAS 501 to EES 502 may include the URL information of the orchestrator. EES 502 stores and manages the EAS ID and / or AC profile information included in the registration request message received from EAS 501 (operation 512). When receiving the registration request message from EAS 501, EES 502 sends a message in response to the registration request message to EAS 501 (e.g., operation 513).

[0127] Continuing to refer to Figure 5 , EEC 503 sends a registration request message to EES 502 to perform the registration process of EES 502 (e.g., operation 514). The registration request message sent from EEC 503 to EES 502 includes the EEC ID, the EEC type (e.g., an identifier indicating whether it is an embedded type or an AC type), the operating system ID, the ID of the AC currently installed on the UE, and / or a list of ACs associated with the edge computing services currently provided by EEC 503, or a list of IDs of ACs currently recognizable by EEC 503 on the UE and / or a list of IDs of ACs currently recognizable by EEC 502 running on the UE.

[0128] According to an embodiment, when EEC 503 supports the EAS discovery trigger condition, EEC 503 may include an EAS discovery trigger capability indicator in the registration request message sent to EES 502.

[0129] When receiving a registration request message from the EEC 503, the EES 502 identifies the AC list sent from the UE. The EES 502 identifies the available EAS list corresponding to the AC list sent from the UE, and determines a trigger condition to perform EAS discovery for the corresponding EAS (e.g., operation 515). Such a trigger condition can be preset in the EES 502, or can be information received from the ECS or a separate policy server. As an example, the trigger condition can be set in the EES 502 through an authorization setting response message during a service authorization setting (e.g., service activation) process from the ECS.

[0130] According to an embodiment, the conditions for triggering EAS discovery may include all or some of the following conditions:

[0131] When a new AC is installed or reinstalled in the UE;

[0132] When the AC installed on the UE changes to an execution state;

[0133] When the AC transmits a request to use edge computing to the EEC;

[0134] When the AC detects traffic to be transmitted to the EAS;

[0135] When the AC performs a DNS query to transmit traffic to the EAS;

[0136] The AC state (if any) described in connection with the fourth embodiment;

[0137] The change in the AC state described in connection with the fourth embodiment;

[0138] The AC service state described in connection with the fifth embodiment; and / or

[0139] When the AC service state changes as described in connection with Embodiment 5.

[0140] Each of the above EAS discovery trigger conditions can be designated as an EAS discovery trigger indicator index, as shown in Table 1 below.

[0141] Table 1. EAS Discovery Trigger Indicator Index

[0142] Index EAS Discovery Trigger Conditions 1 When a new AC is installed or reinstalled in the UE 2 When the AC installed on the UE changes to the execution state 3 When the AC detects a service for transmitting traffic to the EAS 4 When the AC performs a DNS query to transmit traffic to the EAS 5 Change in AC Status 6 Change in AC Service Status

[0143] In response to the registration request message received from the EEC 503, the EES 502 sends a registration response message (e.g., operation 516) to the EEC 503 that includes the EAS discovery trigger condition (e.g., the EAS discovery trigger indicator index information indicating the EAS discovery trigger condition).

[0144] According to an embodiment, when the EAS discovers that the trigger condition is a change in the service state or a specific AC state, the EES 502 may send the corresponding AC ID to the UE together, or send a list of EAS IDs corresponding to the AC ID to the UE.

[0145] When the EEC 503 registers in the EES 502, the EES 502 may send an EEC registration response message including at least one of the following information to the EEC 503:

[0146] - A list of currently available EASs in the list of ACs installed on the UE received from the EEC 503;

[0147] - A list of EASs that can currently be instantiated by the EAS in the list of ACs installed on the UE received from the EEC 503;

[0148] - EAS discovery trigger condition information of the AC;

[0149] - A list of EASs that have dynamically requested EAS instantiation through EAS discovery in the list of EASs registered in the EES 502; or

[0150] - A list of ACs corresponding to the EAS 501 that has dynamically requested EAS instantiation.

[0151] According to an embodiment, the EEC 503 may provide a function of detecting an EAS discovery trigger, or may support a function of sending an EAS discovery request according to an EAS discovery trigger condition received from the EES 502.

[0152] When receiving the registration response message from the EES 502, the EEC 503 identifies at least one of the following:

[0153] - Detection of a change in the AC state;

[0154] - Detection of an AC using the service connection with the EAS 501; or

[0155] - Detection of an AC that sends services to the EAS 501.

[0156] The identification process of the EEC 503 as described above corresponds to the process of identifying whether the EEC 503 meets the EAS discovery trigger condition included in the registration response message (e.g., operation 517).

[0157] When receiving the EAS discovery trigger condition included in the registration response message from EES 502, when the EAS discovery trigger condition is satisfied, EEC 503 sends an EAS discovery request message to EES 502 (e.g., operation 518). The EAS discovery request message sent from EEC 503 to EES 502 may include the following information:

[0158] - EEC ID;

[0159] - A list of IDs of the installed or running ACs;

[0160] - A list of AC profiles including the status of the ACs; and / or

[0161] - The EAS discovery trigger indicator index when sending the EAS discovery request message when the EAS discovery trigger condition is satisfied (corresponding to the index shown in Table 1, for example).

[0162] According to another embodiment, even when the EAS discovery trigger condition is not received, if there are settings of EEC 502 itself or settings of the operator, and the following conditions are satisfied, EEC 502 may send an EAS discovery request message to EES 502.

[0163] When the AC status changes as described in connection with Embodiment 4, more specifically:

[0164] ■ When a new AC is installed (i.e., the AC status changes to the installed state);

[0165] ■ When the AC changes to the running state;

[0166] ■ When the AC changes to the foreground; and / or

[0167] ■ When the UI application requests and focuses on user interaction.

[0168] When the AC service status changes as described in connection with Embodiment 5, more specifically:

[0169] ■ When the AC detects sending traffic to the EAS;

[0170] ■ When the AC sends a DNS query to convey traffic to the EAS, or when the AC detects the sending of a DNS query; and / or

[0171] ■ When the AC changes from a state of not conveying traffic to a state of setting traffic.

[0172] When the EEC 503 sends an EAS discovery request message to the EES 502, the EEC 503 may include an indicator in the EAS discovery request message indicating the AC status as described in connection with the fourth embodiment or the AC service status as described in connection with the fifth embodiment, and send it to the EES 502.

[0173] Upon receiving the EAS discovery request message from the EEC 503, the EES 502 performs necessary operations (e.g., operation 519).

[0174] According to an embodiment, upon receiving the EAS discovery request message from the EEC 503, the EAS 502 identifies whether the AC status in the AC ID or AC profile included in the EAS discovery request message satisfies a specified condition. For example, the EAS 502 identifies whether the AC ID included in the EAS discovery request message corresponds to the AC ID or the AC profile stored in operation 512.

[0175] According to an embodiment, the EES 502 identifies whether an EAS discovery trigger indicator index is included in the EAS discovery request message and whether there is an operation to be performed according to the corresponding EAS discovery trigger indicator index. For example, the EAS 502 may search for the corresponding EAS 501 according to the EAS discovery trigger indicator index and perform an operation to trigger the EAS instantiation of the EAS 501 through an orchestrator.

[0176] According to an embodiment, the EES 502 may select an EAS ID corresponding to the AC ID included in the EAS discovery filter and may perform an operation to trigger the dynamic instantiation of the EAS 501.

[0177] According to another embodiment of the present disclosure, the process of triggering the instantiation of the EAS 501 through the orchestrator of the EAS501 corresponding to the AC received by the EES 502 from the EEC 503 may be performed through information about the AC included in the registration request message received from the EEC 503. For example, after Figure 5 operation 515, the EES 502 determines whether to horizontally scale down or horizontally scale up the EAS corresponding to the AC and sends a request for the determined horizontal scale-up or scale-down (e.g., dynamic instantiation) to the orchestrator. For example, the EES 502 may determine the EAS instantiation through the following information included in the registration request message received from the EEC 503:

[0178] - List of AC IDs;

[0179] - List of AC profiles;

[0180] - AC status information or changed AC status information;

[0181] - AC service status information or changed AC service status information; and / or

[0182] - A list of AC IDs where the installation of the AC is detected in the EEC 503.

[0183] In addition, the EES 501 can register or release the context of the EAS 501 corresponding to the orchestrator. When receiving a request from the EES 501, the orchestrator can determine operations for creating, adding, deleting, upgrading, or downgrading EAS entities related to the AC.

[0184] The conditions for the occurrence of the status information of the UE app (i.e., the AC) and the change of the status information are described in conjunction with Embodiment 4.

[0185] Figure 6 is a flowchart showing the state transition of the UE app status according to the user's work in Embodiment 4 of the present disclosure.

[0186] In conjunction with Figure 6 The six states described all represent the status of the app (i.e., the AC) in the UE. When describing the states below Figure 6 the application, the AC, and the UE app, as well as the UE application, can be used interchangeably.

[0187] Referring to Figure 6 each of the six states of the UE app can be defined as follows.

[0188] 1) Application unavailable (601) state

[0189] This is the state where the application is not installed. In this state, the application can be downloaded from the app store (or play store). The downloaded and then installed application can transition to the application available state. When the AC in the application available state is removed by the UE's operating system, it becomes the application unavailable state.

[0190] 2) Application available (602) state

[0191] This is the state where the application is installed. This state can be the application inactive state or the application active state. When the AC is downloaded and then fully installed on the UE, the AC becomes the application available state. When the AC is removed, it becomes the application unavailable state.

[0192] 3) Application inactive (603) state (when the application is installed but not running)

[0193] This is a sub - state of the application available state. This is the state where the application is installed but not running. In this state, the application cannot generate services. Examples of the application inactive state include the following situations:

[0194] - The state where the application has been installed but not yet started;

[0195] - The state where the application has been paused by the mobile operating system or the user; and / or

[0196] - The state where the application has been terminated by the mobile operating system or the user.

[0197] 4) Application active (604) state (application service ready state)

[0198] This is a sub - state of the application available state. In this state, the application is running. After the application is installed, it starts and transitions to the application active state. Or when a paused application is resumed, the application becomes active. In the application active state, the application can generate application services regardless of the user's actions.

[0199] 5) Application active visible (605) state

[0200] The application active visible state is a sub - state of the application active state. In the application active visible state, the application can be shown to the user, and the application can control the user interaction with the user through the user interface. In the application active visible state, application services can be transmitted to the server or EAS, or generated as a result of user actions. The application can enter the application active visible state while the application starts in the application inactive state. In the application active invisible state, when the application has the right to control the user interface or is focused, the application can transition to the active visible state. When the application in the application active visible state loses the right to control the user screen by the operating system or another application, the application can transition to the active invisible state. The application active visible state can include the state where the screen of the application is in the foreground.

[0201] 6) Application active invisible (606) state

[0202] This is a sub - state of the application active state. In the application active invisible state, the application has no right to control the user's actions and is invisible to the user. Even in the application active invisible state, the AC can transmit or receive application services regardless of the user's actions. In the application active invisible state, the application services started in the application active visible state can be continuously sent and received. When the application is paused or terminated in the application active invisible state, the application can transition to the inactive state. When the application happens to have user control rights or obtains application focus in the application active visible state, the application can transition to the application active visible state. When the application loses focus or user control rights in the application active visible state, the application can transition to the application active invisible state.

[0203] When describing the main operations described in this disclosure, in conjunction with Figure 6The described states can be described as similar types of states with different names or combinations thereof.

[0204] In one embodiment 5 of the present disclosure, conditions for changing the service state information and application service state information of the UE app or AC are described.

[0205] Figure 7 It is a flowchart showing the state transition of the UE app service state according to Embodiment 5 of the present disclosure.

[0206] Combined Figure 7 The described states all represent the service states of the app (i.e., AC) in the UE. Hereinafter, when describing Figure 7 the states, the application service and the AC service can be used interchangeably.

[0207] Refer to Figure 7 , the state of the UE app can be defined as follows.

[0208] 1) Application unavailable (701) state

[0209] This is the state where the application is not installed on the UE. This is the same state as the application unavailable state of the fourth embodiment. No application service occurs in the application unavailable state.

[0210] 2) Application available (702) state

[0211] This is the state where the application is running. This is the same state as the application available state of the fourth embodiment.

[0212] 3) Application inactive (703) state

[0213] This is the state where the application is installed on the UE but not running. This is the same state as the application inactive state of Embodiment 4. In the application inactive state, the application cannot generate services.

[0214] 4) Application service not ready (704) state

[0215] The application service not ready state is a state where the application service cannot be generated and may include the application unavailable state and the application inactive state.

[0216] 5) Application service ready (705) state

[0217] This is a sub - state of the application available state. This is the same state as the application active state shown in Embodiment 4. Since the application is in the running state, the application can send and receive application services at any time, regardless of the user's actions. In the application inactive state or the application service not ready state, the application can start and transition to the application service ready state. When the application is suspended or terminated in the application service ready state, the application can transition to the application service not ready state or the application inactive state. The application service ready state can have additional sub - states, such as application service sleep, application service arrival, and application service exchange states.

[0218] 6) Application service sleep (706) state

[0219] This is a sub - state of the application service ready state. When the application service starts in the application inactive state or the application service not ready state, the application can transition to the application service sleep state. When a DNS query occurs from the AC or a DNS query to the destination EAS occurs in the application service sleep state, the application can transition to the application service arrival state. Alternatively, when an application service (for the destination EAS) occurs, the application can transition to the application service exchange state.

[0220] 7) Application service arrival (707) state

[0221] This is a sub - state of the application service ready state. This is the state where it is detected that the application service is to be sent, received, or is about to be sent or received. For example, when a DNS query is detected, the application becomes the application service arrival state. When no service is generated between the application in the UE and the destination EAS during a given time (e.g., 1 second) in the application service arrival state, the application can transition from the application service arrival state to the application service sleep state.

[0222] 8) Application service exchange (708) state

[0223] This is a sub - state of the application service ready state. When an application service generated from the AC is detected, or when the generation of an application service from the AC to the destination EAS is detected, the application service sleep state is changed to the application service exchange state. Examples of such application services can include messages for creating a TCP connection between the application in the UE and the destination EAS address and messages for establishing an HTTP connection. When no service is generated between the application in the UE and the destination EAS during a preset time (e.g., 10 seconds) in the application service exchange state, the application can transition to the application service sleep state. The occurrence of a DNS query to the destination EAS address does not allow the application to transition to the application service arrival state.

[0224] Figure 8is a block diagram showing the configuration of a UE according to various embodiments of the present disclosure.

[0225] Referring to Figure 8 , the UE 800 may include a transceiver 801 and a controller 802 to communicate with other entities in a wireless communication system.

[0226] The transceiver 801 may transmit and receive signals to / from other network entities and may include the CP of the UE. The controller 802 may control the transmission and reception of the transceiver and may include the EEC and AC of the UE.

[0227] Figure 9 is a block diagram showing the configuration of a server according to various embodiments of the present disclosure.

[0228] Figure 9 The server of

[0229] Referring to Figure 9 , the server 900 that communicates with other entities or UEs in a wireless communication system may include a transceiver 901 and a controller 902.

[0230] The transceiver 901 may transmit and receive signals to / from other network entities. The controller 902 may control the transceiver 901 and process the transmitted and received signals.

[0231] It should be noted that Figures 1 to 9 the configuration view, the example view of the edge computing service providing method, the example view of the operation process, and the configuration view are not intended to limit the scope of the present disclosure. In other words, all components, entities, or operation steps shown in Figures 1 to 9 should not be construed as necessary components for practicing the present disclosure. Instead, the present disclosure may be implemented using only some components without departing from the gist of the present disclosure.

[0232] The above operations of the base station or the UE may be implemented by providing a memory device that stores its corresponding code in any component of the base station device or the UE device. That is, the controller in the eNB or the UE may execute the above operations by reading and executing program code stored in the memory device by a processor or a central processing unit (CPU).

[0233] As described herein, various components or modules in an entity, a UE, or a base station device may operate using a hardware circuit (e.g., a complementary metal oxide semiconductor-based logic circuit), firmware, software, and / or using a combination of hardware, firmware, and / or software (such as that embedded in a machine-readable medium). As an example, electronic circuits such as transistors, logic gates, or ASICs may be used to perform various electronic structures and methods.

[0234] Although specific embodiments of the present disclosure have been described above, various changes can be made thereto without departing from the scope of the present disclosure. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined by the appended claims and their equivalents.

[0235] Although the present disclosure has been described with various embodiments, various changes and modifications can be conceived by those skilled in the art. The present disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method for an Edge-Enabled Server (EES), the method comprising: Receiving, from an Edge-Enabled Client (EEC), a first message including an identifier (ACID) of an Application Client (AC), an identifier (EECID) of the EEC, and an identifier of a specific Edge Application Server (EAS); And Triggering an EAS management system to instantiate an EAS serving the AC.

2. The method according to claim 1, further comprising: Determining an EAS that matches the ACID.

3. The method according to claim 1, wherein, Triggering the EAS management system to instantiate the EAS includes: Invoking an Application Programming Interface (API) that manages the lifecycle of the EAS; and Sending, to the EAS management system, the information included in the first message.

4. The method according to claim 1, wherein, The first message includes one of an AC status report message and an AC service status report message.

5. The method according to claim 1, wherein The first message further includes at least one of status information of the AC, previous status information of the AC if at least one AC is changed, status information of the service of the AC, or previous status information of the service of the AC if the service of the AC is changed.

6. The method according to claim 1, further comprising: Receiving, from the EAS, a second message requesting to report status information of the AC; Storing a reporting condition included in the second message for reporting status information of the AC; And Sending a response message to the EAS in response to the second message.

7. The method according to claim 6, wherein Sending the response message includes: Determining whether the AC and the status information of the AC match the current status information of the AC; and Based on a result of determining that the AC and the status information of the AC match the current status information of the AC, sending a response message to the EAS in response to the second message.

8. The method according to claim 6, wherein Receiving the first message includes: Sending a report subscription request message for status information of the AC to the EEC, the report subscription request message including a reporting condition for reporting status information of the AC; and Based on the reporting condition, receiving the first message from the EEC.

9. The method according to claim 8, wherein, The report subscription request message further includes at least one of an AC status report type, an AC status report indicator, or an AC status report subscription.

10. An Edge-Enabled Server (EES) comprising: A transceiver; And A processor configured to: Control the transceiver to receive, from an Edge-Enabled Client (EEC), a first message including an identifier (ACID) of an Application Client (AC), an identifier (EECID) of the EEC, and an identifier of a specific Edge Application Server (EAS); And Trigger an EAS management system to instantiate an EAS serving the AC.

11. The EES according to claim 10, wherein, The processor is configured to determine an EAS that matches the ACID.

12. The EES according to claim 10, wherein The processor is configured to: Invoke an Application Programming Interface (API) that manages the lifecycle of the EAS; and Control the transceiver to send the information included in the first message to the EAS management system.

13. The EES according to claim 10, wherein The first message includes one of an AC status report message and an AC service status report message.

14. The EES according to claim 10, wherein, The first message further includes at least one of the status information of the AC, the previous status information of the AC if at least one AC is changed, the status information of the service of the AC, or the previous status information of the service of the AC if the service of the AC is changed.

Images