COMMUNICATION METHOD AND APPARATUS IN A WIRELESS COMMUNICATION SYSTEM SUPPORTING EDGE COMPUTING

Abstract

A communication method by an EEC of a UE in a wireless communication system supporting edge computing is disclosed, which includes the steps of receiving an AC registration request message including an AC profile, an ECS address, and a user consent indicating whether to allow external exposure of the AC profile from an AC executed in the terminal, selecting an edge configuration server (ECS) for performing service provisioning based on the AC registration request message, performing a service provisioning procedure for the selected ECS, performing EEC registration and EAS discovery for an EES acquired through the service provisioning procedure, and transmitting EAS information acquired through EAS discovery acquired from the EES to the AC.

Description

[Technical field]

[0001] The present disclosure relates to edge computing technology, and more particularly to a communication method and apparatus in a wireless communication system that supports edge computing. [Background technology]

[0002] Since the commercialization of the 4G communication system, efforts have been made to develop an improved 5G or pre-5G communication system to meet the increasing demand for wireless data traffic. For this reason, the 5G or pre-5G communication system is also called a "Beyond 4G Network" communication system or a "Post LTE System."

[0003] To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz band, etc.). To mitigate the path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, beamforming, massive multiple-input multiple-output (massive MIMO), full dimensional multiple-input multiple-output (FD-MIMO), array antenna, analog beam forming, and large scale antenna technologies are being discussed in the 5G communication system.

[0004] In addition, to improve the system network, technologies being developed for the 5G communication system include advanced small cells, cloud Radio Access Network (cloud RAN), ultra-dense networks, Device to Device (D2D) communications, wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and receiver interference cancellation.

[0005] In addition, for 5G systems, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding) and advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed.

[0006] Meanwhile, the Internet is evolving from a human-centered connection network where humans generate and consume information to an IoT (Internet of Things) network where information is exchanged and processed between distributed components such as things. IoE (Internet of Everything) technology is also emerging, combining big data processing technology through connections with cloud servers with IoT technology. To realize IoT, technological elements such as sensing technology, wired and wireless communication, network infrastructure, service interface technology, and security technology are required, so recently, technologies such as sensor networks for connecting things, M2M (Machine to Machine) communication, and MTC (Machine Type Communication) are being researched.

[0007] In an IoT environment, intelligent IT (Internet Technology) services that create new value in human life can be provided by collecting and analyzing data generated between connected things. Through the fusion and combination of existing IT (Information Technology) with various industries, IoT has the potential to be applied to various fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0008] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, 5G communication technologies such as sensor networks, M2M (Machine to Machine) communication, and MTC (Machine Type Communication) are being realized using techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access network (cloud RAN), the aforementioned big data processing technology, can also be considered an example of the fusion of 5G technology and IoT technology. Summary of the Invention [Problem to be solved by the invention]

[0009] In order for a server installed outside a mobile communication system such as 3GPP (registered trademark) (3rd generation partnership project) to provide a service to a user equipment (UE) in the mobile communication system, a terminal identifier for linking with a network function (NF) of the mobile communication system may be required. However, it may be difficult to set a terminal identifier (e.g., UE ID) used in the mobile communication system in advance in a server installed outside the mobile communication system. Furthermore, the use of an Internet Protocol (IP) address of a terminal (UE) may also be restricted. This is because a UE cannot be identified by an IP address when network address translation (NAT) is used. Therefore, a technology for assigning a different temporary identifier for each service used has become necessary so that a user's personal information cannot be tracked.

[0010] An embodiment of the present disclosure may provide an edge enabler layer operation within a terminal to provide services to dedicated applications, and may provide operations related to interworking between an external edge computing server and a core network (CN) of a mobile communication network to which the terminal is connected.

[0011] An embodiment of the present disclosure can provide operations for collaboration between an application client (AC) and an edge enabler layer in a terminal, and between an edge computing server and a core network. [Means for solving the problem]

[0012] To support edge-specific application services, an embodiment of the present disclosure can provide interworking between an application client (AC) in a terminal and an edge enabler client (EEC) included in an edge enabler layer, and thus provide operations between an edge computing server included in the edge enabler layer and a mobile communication core network.

[0013] In the embodiment of the present disclosure, information set in an application client (AC) can be acquired by an edge enabler client (EEC).

[0014] An embodiment of the present disclosure can provide information obtained from the AC from the edge enabler layer to an edge computing server.

[0015] The embodiment of the present disclosure can reconcile the inconsistency of configuration information between the edge computing server and the mobile communication core network according to the information provided by the AC.

[0016] The embodiments of the present disclosure may provide a method of cooperation between an EEC and an AC to provide continuous services to the AC during a change of an edge computing server.

[0017] According to one embodiment, a communication method by an edge enabler client (EEC) of a terminal (UE) in a wireless communication system supporting edge computing may include a step of receiving an AC registration request message from an application client (AC) running in the terminal, the AC registration request message including an AC profile, an edge configuration server (ECS) address, and a user consent indicating whether to allow external exposure of the AC profile; a step of selecting an edge configuration server (ECS) for performing service provisioning based on the AC registration request message; a step of performing a service provisioning procedure for the selected ECS; a step of performing EEC registration and edge application server (EAS) discovery for an edge enabler server (EES) obtained through the service provisioning procedure; and a step of transmitting EAS information obtained through the EAS discovery from the EES to the AC.

[0018] According to one embodiment, a communication method by an edge enabler client (EEC) of a terminal (UE) in a wireless communication system supporting edge computing includes the steps of: receiving an AC registration request message including a storage address of AC-related information from an application client (AC) running in the terminal; acquiring the AC-related information from the storage address; the AC-related information including an AC profile, an edge configuration server (ECS) address, and a user consent indicating whether to allow external exposure of the AC profile; selecting an edge configuration server (ECS) for performing service provisioning based on the AC registration request message; performing a service provisioning procedure for the selected ECS; performing EEC registration and edge application server (EAS) discovery for an edge enabler server (EES) acquired through the service provisioning procedure; and transmitting the EAS information acquired through the EAS discovery from the EES to the AC.

[0019] According to one embodiment, a communication method by an edge enabler client (EEC) of a terminal (UE) in a wireless communication system supporting edge computing includes the steps of: receiving an AC registration request message including a data network name (DNN), a public land mobile network (PLMN) ID, traffic descriptor information, and a DNN substitution permission instruction from an application client (AC) running in the terminal; transmitting a service provisioning request message including the DNN, traffic descriptor information, and a UE route selection policy (URSP) guidance execution instruction to an edge configuration server (ECS) based on the AC registration request message; receiving a service provisioning response message including a URSP result from the ECS in response to the service provisioning request message; and transmitting to the AC an indication indicating that an edge computing service is available and an indication indicating whether the DNN set in the AC is available as a traffic descriptor in response to receiving the service provisioning response message.

[0020] According to one embodiment, a communication method by an edge enabler client (EEC) of a terminal (UE) in a wireless communication system supporting edge computing includes a step of receiving an AC subscription request message from an application client (AC) executed in the terminal, the AC including an address at which the AC receives notification messages, an application package name of the AC, an operation identifier required to induce a specific operation of the AC, and an indication indicating a change of a target edge application server (EAS); a step of transmitting a subscription request message to a source edge enabler server (EES) in response to the indication indicating the change of the target EAS; a step of transmitting an AC subscription response message corresponding to the AC subscription request message to the AC; a step of the terminal performing an application context reallocation procedure for maintaining service continuity by moving from the source EES to a target EES; and a step of transmitting an indication indicating a result of the application context reallocation procedure and target edge application server (EAS) information to the AC.

[0021] According to one embodiment, an edge enabler client (EEC) of a terminal may be configured to perform at least one or a combination of methods according to the embodiments of the present disclosure.

[0022] According to one embodiment, an edge configuration server (ECS) can be configured to perform at least one or a combination of methods according to embodiments of the present disclosure. Effect of the Invention

[0023] An embodiment of the present disclosure can provide a temporarily set terminal identifier to a server (e.g., an edge computing server) installed outside a mobile communication network operated by an operator, thereby allowing the server to use the opening function of the 3GPP (registered trademark) network to provide services to a user.

[0024] An embodiment of the present disclosure provides a different temporary terminal identifier for each service or application server, and sets the temporary terminal identifier in the client of the edge computing service in the terminal, thereby minimizing the exposure of fixed terminal identifiers and the tracking of personal information regarding users.

[0025] The above and other aspects, features, and advantages of particular embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings. [Brief description of the drawings]

[0026] [Figure 1] FIG. 1 illustrates an application layer network structure and interfaces supporting edge computing according to one embodiment of the present disclosure. [Diagram 2] 1 is a flowchart illustrating an example of a procedure for providing application client (AC) information according to an embodiment of the present disclosure. [Diagram 3] 11 is a flowchart illustrating another example of a procedure for providing application client (AC) information according to an embodiment of the present disclosure. [Figure 4] 11 is a flowchart illustrating a procedure for executing a URSP guide based on application client (AC) information according to an embodiment of the present disclosure. [Diagram 5] 1 is a flowchart illustrating a procedure for obtaining application client (AC) information and providing a notification service according to an embodiment of the present disclosure. [Figure 6] FIG. 2 is a block diagram showing a configuration of a terminal (UE) according to an embodiment of the present disclosure. [Figure 7] FIG. 2 is a block diagram illustrating a configuration of a network entity according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Hereinafter, the operation principle of the embodiment will be described in detail with reference to the accompanying drawings. The terms described below are defined in consideration of the functions in the embodiment. These terms may vary depending on the intention or practice of the user or operator, and therefore their definitions should be determined by the contents of this specification.

[0028] The terms referring to network entities and edge computing system objects, messages, and identification information used in the present disclosure are exemplified for convenience of explanation. Therefore, the embodiments of the present disclosure are not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0029] Hereinafter, for convenience, this disclosure will use terms and names defined in the 5G system standard, but is not limited by these terms and names and can be similarly applied to systems conforming to other standards.

[0030] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Note that detailed descriptions of well-known functions and configurations that may unnecessarily obscure the gist of the present disclosure will be omitted.

[0031] The various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features described herein to a specific embodiment, but should be understood to include various modifications, equivalents, or alternatives of the embodiment. With respect to the description of the drawings, similar or related components may use similar reference numerals. The singular form of a noun corresponding to an item may include one or more of the said item, unless otherwise clearly indicated in the relevant context.

[0032] In the present disclosure, each of the phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may include any of the items listed together in the corresponding phrase of the phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish the component from other corresponding components, and do not limit the component in other aspects (e.g., importance or order). When a (e.g., first) component is referred to as being "coupled" or "connected" to another (e.g., second) component, in combination with or without the terms "functionally" or "communicatively," this means that the several components may be connected to the other components directly (e.g., by wire), wirelessly, or via a third component.

[0033] The term "module" as used in this disclosure may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integrated component or the smallest unit or part of said component that performs one or more functions. According to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0034] Various embodiments of the present disclosure may be implemented as software (e.g., a program) including one or more instructions stored in a storage medium (e.g., an internal memory or an external memory) readable by an electronic device. For example, a processor of the electronic device may retrieve and execute at least one of the one or more stored instructions from the storage medium. This enables the device to operate to perform at least one function according to the retrieved at least one instruction. The one or more instructions may include a code generated by a compiler or a code that may be executed by an interpreter. The electronic device readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory" only means that the storage medium is a tangible device and does not include a signal (e.g., electromagnetic wave), and the term does not distinguish between a case where data is stored semi-permanently and a case where data is stored temporarily in the storage medium.

[0035] According to one embodiment, the methods according to various embodiments of the present disclosure may be provided in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., CD-ROM, DVD-ROM) or may be distributed through an application store (e.g., Play Store, etc.). TM The computer program product may be distributed online (e.g., downloaded or uploaded) via a mobile device, a mobile network, or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a part of the computer program product may be at least temporarily stored or temporarily generated on a machine-readable storage medium, such as a memory of a manufacturer's server, an application store's server, or an intermediary server.

[0036] According to an embodiment, each of the components (e.g., modules or programs) may include one or more entities. According to various embodiments, one or more of the components or operations may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into one component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as performed by the corresponding component of the multiple components before integration. According to various embodiments, operations performed by modules, programs, or other components may be performed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be performed in a different order, or omitted, or one or more other operations may be added.

[0037] The 5G network technology and edge computing technology described in the drawings and descriptions of this disclosure refer to standards (e.g., TS23.558) defined by the ITU (international telecommunication union) or 3GPP (registered trademark), and each of the components included in the network environment of Figure 1 described below may represent a physical entity unit, or a software or module unit capable of performing an individual function.

[0038] In the embodiment of the present disclosure, the electronic device may refer to various devices used by a user. For example, the electronic device may refer to a terminal, a user equipment (UE), a mobile station, a subscriber station, a remote terminal, a wireless terminal, or a user device. For convenience, the electronic device is exemplified as a user equipment (UE), and the embodiment of the present disclosure will be described below.

[0039] In an embodiment of the present disclosure, an access network (AN) may provide a channel for wireless communication with an electronic device. The AN may refer to a radio access network (RAN), a base station, an eNB, an eNodeB, a 5G node, a transmission / reception point (TRP), or a 5th generation NodeB (5GNB). Furthermore, according to an embodiment of the present disclosure, a core network (CN) may manage at least one of subscriber information, mobility, access authorization, data packet traffic, or charging policy of a UE. The core network (CN) may include at least one of a user plane function (UPF) node, an access & mobility management function (AMF) node, a session management function (SMF) node, a unified data management (UDM) node, a network exposes function (NEF) node, a policy control function (PCF) node, or an application function (AF) node, and the functions and operations of the nodes (or entities) included in the core network (CN) may refer to standard specifications (e.g., TS 23.501) defined by 3GPP (registered trademark).

[0040] Edge computing is a technology proposed to enable efficient service provision by reducing end-to-end network latency and load by hosting operator and / or third-party services in close proximity to access points such as base stations. Such edge computing technology can reduce data processing time by processing data generated by UE in real time in close proximity to the site where the data is generated without transmitting the data to a central cloud network (hereinafter referred to as "central cloud"). As an example, edge computing technology can be applied to technology fields such as autonomous vehicles, which require rapid processing in various situations that may occur while driving.

[0041] Edge computing is a concept of network architecture that enables cloud computing functions and service environments, and the network for edge computing can be deployed in close proximity to UEs. Edge computing can provide advantages such as reduced latency, increased bandwidth, reduced backhaul truck pick-up, and new service prospects compared to cloud environments. Core networks (CNs) proposed by 3GPP (registered trademark) for 5G or 6G or higher can expose network information and functions to edge computing applications (hereinafter referred to as edge applications).

[0042] FIG. 1 is a diagram illustrating an application layer network structure and interfaces supporting edge computing according to one embodiment of the present disclosure.

[0043] Referring to FIG. 1, a terminal (UE) 101 may include at least one application client (AC) 102 and an edge enabler client (EDE) 103. The application client (AC) 102 may be an application-level client for providing a specific application service to a user when an edge computing service is provided. The application client (AC) 102 may be used for a multi-access edge computing (MEC) service. The application client (AC) 102 is an application program that runs on a mobile operating system (OS) of the terminal 101, and may be identified as an application identifier in the core network 104. In an environment that provides a mobile operating system, the application client (AC) 102 may be identified by an operating system identifier (OS Identifier) ​​and an application identifier (OSAppID) unique to each operating system.

[0044] Although not shown, the terminal 101 may further include a communication processor (CP) for communicating with other mobile communication networks, for example, at least one or two mobile communication networks. Also, although not shown, the terminal 101 may further include an edge configuration client (EDC).

[0045] The 3GPP (registered trademark) core network 104 is shown as an example of a wireless mobile communication network, and may include, for example, an evolved packet core (EPC) and / or a 5G core network (5GC). The 3GPP (registered trademark) core network 104 may include at least one base station (node ​​B) that directly communicates with the terminal 101 over the air (OTA), and may further include a higher-level core network configuration. When the 3GPP (registered trademark) core network 104 includes 5GC, the core network configuration may include at least one of an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), or a user plane function (USP). When the 3GPP (registered trademark) core network 104 includes an EPC, the core network configuration may include at least one network node corresponding to 5GC.

[0046] An application client (AC) 102 of a terminal 101 can access an edge data network (EDG) 105 through a 3GPP core network 104. In one embodiment, the edge data network (EDG) 105 can be implemented by a network slicing technology, and multiple edge data networks that can interface with the core network 104 can be configured in the same form. The edge data network (EDN) 105 can be a packet data network of a 5GC data network or an EPC network. As an example, the edge data network 105 can include an edge hosting platform and can include an edge enabler server (EES) 107 and one or more edge application servers (EAS) 106. In one embodiment, the edge enabler server (EES) 107 can include an edge enabler client manager, an edge enabler platform, and an edge enabler API (application programming interface) server.

[0047] The edge application server (EAS) 106 may be a third-party application server program running in a virtual machine (VM) image or virtualization container running in an edge hosting environment. The edge application server (EAS) 106 may be configured to provide ultra-low latency services at a location close to the terminal 101. The edge hosting platform may be platform software including a virtualization layer capable of running multiple edge application programs. In this disclosure, the edge hosting platform may be used with the same concept as the edge hosting environment.

[0048] The edge computing system is composed of an edge enabler server (EES) 107, an edge configuration server (ECS) 108, and an edge enabler client (EEC) 103, and can provide edge computing services to an application client 102 of a terminal 101.

[0049] The edge enabler server (EES) 107 is a server for providing edge computing services, and the edge enabler client (EEC) 103 of the terminal 101 can manage a list of application programs available on the edge hosting environment (or edge hosting platform), manage configuration information of edge application programs (e.g., at least one edge application server (EAS) 106) running on the edge hosting platform, and provide the edge application programs with application programming interfaces (APIs) for functions provided by the 3GPP (registered trademark) core network.

[0050] The edge enabler server (EES) 107 can negotiate with the edge enabler client (EEC) 103 of the terminal 101 to connect the application client 102 of the terminal with the edge application server (EAS) 106 in the edge hosting environment. This negotiation can proceed through an interaction between the edge enabler client (EEC) 103 and the edge enabler server (EES) 107, and the edge enabler client (EEC) 103 and the edge enabler server (EES) 107 that perform the interoperation such as the negotiation may be referred to as an edge enabling layer.

[0051] The edge enabler client (EEC) 103 may be a software module of the terminal 101 and a software agent having a function of providing an edge computing service. The edge enabler client (EEC) 103 may perform an operation of connecting a network interface so that data of the application client (AC) 102 is transmitted to an edge application server (EAS) 106 that provides an edge computing service by determining which application can use the edge computing service. An operation of establishing a data connection for using the edge computing service may be performed in a 3GPP® communication layer via a mobile communication function (e.g., a mobile terminal (MT)) of the terminal 101. The 3GPP® communication layer may perform a modem operation for using a mobile communication system, establish a wireless connection for data communication, register a terminal in the mobile communication system, establish a connection for data transmission in the mobile communication system, and play a role of transmitting and receiving data.

[0052] The edge enabler client (EEC) 103 can perform at least one of the following functions: authentication function for accessing an edge computing server (e.g., edge enabler server (EES) 107 and / or edge configuration server (ECS) 108); function for obtaining access information of the edge data network (EDN) 105 and the edge enabler server (EES) 107 in cooperation with the edge configuration server (ECS) 108; function for obtaining information regarding one or more edge application servers (EAS) 106 from the edge enabler server (EES) 107; or function for routing traffic of one or more application clients (AC) 102 in the terminal 101 to one or more edge application servers (EAS) 106 based on the information regarding the one or more edge application servers (EAS) 106.

[0053] Although not shown, the edge data network 105 may include an orchestrator for edge hosting platform (not shown). The orchestrator is a management system that manages the edge hosting platform and the lifecycle of edge application programs that run on the edge hosting platform, and can perform the functions of an orchestrator defined by ETSI MANO (European telecommunication standards institute management and network operation).

[0054] An edge configuration server (ECS) 108, which is distinguished from an edge data network (EDN) 105 and can communicate with an edge enabler client (EEC) 103 of the terminal 101 via a 3GPP (registered trademark) core network 104, may be an initial connection server that can be provided with configuration information for the terminal 101 to use a mobile edge computing (MEC) service. The edge configuration server (ECS) 108 has deployment information of an edge enabler server (EES) 107 and can provide the terminal 101 with configuration information related to the edge data network (EDN) 105 for using the edge computing service.

[0055] The configuration information may include at least one of EDN connection information (e.g., data network name (DNN) or single network slice selection assistance information (S-NSSAI)) associated with the edge data network (EDN) 105, service area information (e.g., cell list, list of tracking areas, public land mobile network (PLMN) ID) of the edge data network (EDN) 105, or connection information (e.g., uniform resource identifier (URI)) of the edge enabler server (EES) 107.

[0056] The service area of ​​the edge data network (EDN) 105 may be an area set by the edge enabler server (EES) 107. Based on the information about the service area of ​​the edge data network (EDN) 105, the terminal 101 can obtain information about the edge enabler server (EES) 107 accessible at the current location. If the edge configuration server (ECS) 108 of the edge data network (EDN) 105 has information about the edge application server (EAS) 106 running in the edge hosting environment of the specific edge enabler server (EES) 107, the terminal 101 can obtain information from the edge configuration server (ECS) 108 via the edge enabler client (EEC) 103.

[0057] In Fig. 1, EDGE-1 to EGGE-8 mean network interfaces (i.e., reference points) between objects, and the explanation of EDGE-1 to EGGE-8 is as shown in the following . Note that the explanation of EDGE-1 to EGGE-8 is not limited to the following .

[0058] [Table 1]

[0059] The application network structure for supporting edge computing in FIG. 1 may be managed by a mobile communication operator and a separate edge computing operator, and thus, a plurality of separate edge computing operators may exist within one mobile communication operator network. The application layer network structure for supporting edge computing in FIG. 1 may support such an operator configuration.

[0060] The application layer network structure shown in Fig. 1 can support multiple edge computing operators in one mobile communication network. The application layer network structure can transmit information about multiple edge computing service operators available in one mobile communication network and setting information for connecting to the edge computing network installed by the operator to a terminal.

[0061] The application layer network structure shown in FIG. 1 can transmit, to a terminal, information regarding an edge network service provider selected by a mobile communications carrier from among multiple edge computing carriers existing in one mobile communications network, and configuration information for connecting to an edge computing network installed by the selected edge network service provider.

[0062] FIG. 2 is a flowchart illustrating an example of a procedure for providing application client (AC) information according to an embodiment of the present disclosure.

[0063] 2, in operation 201, an application client (AC) 102 may send an AC registration request message to an edge enabler client (EEC) 103. In one embodiment, the condition for performing the sending of the AC registration request message may include at least one of the following: installation of the AC 102 in the terminal 101, running of the AC 102, or generation of data traffic in the AC 102. In one embodiment, the AC registration request message may include at least one of the following information:

[0064] - an AC profile configured in the AC 102 (e.g., including at least one of an AC identifier, an AC type, or a key performance indicator); Table 2 below shows an example of an AC profile.

[0065] [Table 2]

[0066] -DNN set in the AC (may be the same value as the DNN that identifies the edge data network (EDN)) - At least one of an ECS address that identifies an edge configuration server (ECS) configured in AC102 (e.g., edge configuration server 108 in FIG. 1), an ECS provider identifier (or an identifier of an edge computing service provider), or an indicator indicating whether another ECS other than the ECS address configured in AC102 is available.

[0067] - User consent on whether to allow external exposure of the AC profile: If user consent is included in the AC registration request message, the EEC 103 can include the AC profile in a service provisioning request message (e.g., in operation 203) for provision to the edge enabler server (EES) 107 or edge configuration server (ECS) 108, or in an EAS discovery request message (e.g., in operation 204).

[0068] - Invocation information (e.g., application package name / identifier) ​​that can be used to invoke AC102 from other applications or devices (e.g., EEC103) in terminal 101 (which may vary depending on the OS of terminal 101): This invocation information can be used by EEC103 to invoke AC102 and guide it to perform a specific action (e.g., an action requesting user consent to external exposure of the AC profile).

[0069] - Information required to induce a specific operation of AC102 (e.g., operation ID or activity name): If necessary, information used by EEC103 to invoke AC102 to induce a specific operation may include, for example, initialization of the cached server address. This operation ID / activity name can be used to request AC102 via the OS of terminal 101 to induce a specific operation (e.g., an operation requesting user consent to external exposure of an AC profile).

[0070] -EAS selection request delegation indicator: the indicator can be used to instruct the EEC 103 to select at least one of the discovered edge application servers (EASs) (e.g., EAS 106) and perform an operation of informing the AC 102 if the indicator is not included in the AC registration request message or if the indicator includes content instructing to inform all discovered EASs, the EEC 103 can convey information (e.g., addresses or identifiers) of all discovered EASs by message to the AC 102 (e.g., in operation 205).

[0071] - In operation 202, in response to the AC registration request message received from the AC 102, the EEC 103 may perform at least one of the following operations and send an AC registration response message to the AC 102:

[0072] - The EEC 103 can store the AC profile received from the AC 102 for use in service provisioning or EAS discovery procedures.

[0073] The EEC 103 may store the ECS address and ECS provider identifier received from the AC 102 in the same manner as the ECS address already stored by the EEC 103. If an indicator indicating whether an ECS other than the configured ECS address is available is provided by the AC 102 as an ECS address, the EEC 103 may use the other ECS information (e.g., including at least one of an ECS address configured in the EEC 103, an ECS address provided by the 5GC via signaling, or an ECS address derived from the serving PLMN identifier) ​​instead of the ECS address provided by the AC 102.

[0074] - In operation 202-1, the EEC 103 may select an edge configuration server (ECS) (eg, ECS 108) to perform the service provisioning procedure based on the information provided by the AC 102.

[0075] In one embodiment, the target ECS for performing service provisioning can be selected as follows.

[0076] - If an ECS address is provided by AC102 and there is no ECS address configured in EEC103 or provided by the 5GC (e.g., core network 104), EEC103 can perform service provisioning using the ECS address provided by AC102.

[0077] - When an ECS address is provided by AC 102 and there is an ECS address configured in EEC 103, EEC 103 may preferentially perform service provisioning for the ECS having the ECS address obtained from AC 102. In one embodiment, if service provisioning of an ECS having an ECS address obtained from AC 102 fails, EEC 103 may re-perform service provisioning using the ECS address configured in EEC 103.

[0078] In operation 203, the EEC 103 may perform a service provisioning procedure on the selected ECS to select an edge enabler server (EES) (e.g., EES 107) of an edge data network (EDN) (e.g., EDN 105) to connect to. The service provisioning procedure may provide the terminal 101 with information necessary to access edge computing services, and may include, for example, a service provisioning request message and a service provisioning response message.

[0079] - If user consent to the AC profile and external exposure of the AC profile is provided by the AC 102, the EEC 103 may include the AC profile in the service provisioning request message sent to the ECS 108. If an available edge computing service provider is specified in the user consent, the EEC 103 may compare the specific edge computing service provider with the ECS provider identifier included in the AC registration request message to determine whether to include the AC profile in the service provisioning request message. In one embodiment, if the edge computing service provider specified by the user consent matches the ECS provider identifier included in the AC registration request message, the EEC 103 may determine to include the AC profile in the service provisioning request message.

[0080] If there is no user consent in the AC registration request message, the EEC 103 may decide to use the AC profile only in the terminal 101 and not include the AC profile in the service provisioning request message sent to the ECS 108 .

[0081] The EEC 103 may obtain configuration information related to the EES 107 in the EDN 105 from a service provisioning response message received as a response corresponding to the service provisioning request message.

[0082] In operation 204, the EEC 103 may send an EEC registration request message and / or an EAS discovery request message to the EES 107 obtained through service provisioning from the ECS 108. The EEC registration request message and / or the EAS discovery request message may include an AC profile obtained from the AC 102 if the AC registration request message includes user consent, similar to operation 203. The EEC 103 may receive at least one response message corresponding to the EEC registration request message and / or the EAS discovery request message from the EES 107. The response message may include EAS information (e.g., an address and / or an identifier).

[0083] In operation 205, the EEC 103 may deliver the EAS information obtained from the EES 107 to the AC 102 via an EAS profile info delivery message. If multiple EAS information are obtained through the service provisioning procedure, the EEC 103 may determine which EAS information to include in the EAS profile info delivery message depending on whether the AC registration request message received in operation 201 includes an EAS selection request delegation indicator.

[0084] In one embodiment, if the AC registration request message in operation 201 does not include an EAS selection delegation request indicator or the EAS selection delegation request indicator included in the AC registration request message instructs that all EAS information found be provided to the AC 102, the EEC 103 may provide all EAS information acquired from the EES 107 to the AC 102 via an EAS profile information transfer message. Otherwise, for example, if the AC registration request message includes an EAS selection delegation request indicator or includes an EAS selection delegation request indicator and the EAS selection delegation request indicator does not instruct that all EAS information be provided to the AC 102, the EEC 103 may select one EAS from the multiple EAS information acquired from the EES 107 and provide it to the AC 102 via an EAS profile information transfer message. The AC 102 may access an EAS (e.g., the EAS 106) according to the EAS information provided by the EEC 103 to provide an edge computing service.

[0085] In one embodiment of operation 205, when the EEC 103 provides the EAS information to the AC 102, the EEC 103 may provide a DNN value indicating an EDN to be connected to access the EAS (e.g., an EDN in which the EAS is installed) together with the EAS address information. The AC 102 may provide the DNN value representing the EDN provided by the EEC 103 to the modem to transmit and receive data traffic with the EAS, thereby leading to the generation of a PDU session of the DNN in a PDU session generation procedure.

[0086] When multiple EAS information is provided from the EEC 103, the AC 102 may select an actually connected EAS (e.g., the EAS 106) based on the multiple EAS information, and access the selected EAS 106 to provide edge computing services. In operation 206, the AC 102 may communicate information about the selected EAS 106 to the EEC 103. In one embodiment, the EEC 103 may provide the EAS information indicating the EAS 106 selected by the AC 102 to the EES 107.

[0087] In one embodiment, if the AC registration request message received by the EEC 103 from the AC 102 does not include user consent allowing external exposure of the AC profile, the EEC 103 may send the service provisioning request message of operation 203 to the ECS 108 without including the AC profile, and may receive a result of service provisioning failure from the ECS 108 via a service provisioning response message.

[0088] In one embodiment, the EEC 103 can confirm that the service provisioning failure cause included in the service provisioning response message is that the AC profile is not provided, or can request user consent from the AC 102 to obtain the AC profile based on the EEC 103's own judgment after the service provisioning failure.

[0089] Specifically, the EEC 103 may use the invocation information (e.g., application package name / identifier) ​​provided by the AC 102 to send a user consent request message including an ECS provider identifier (or an edge computing service provider identifier) ​​to the AC 102. The AC 102 may inform the EEC 103 of whether user consent has been obtained after performing an operation (e.g., a user interface) to obtain user consent to provide the AC profile to the ECS provider, which may be identified as the ECS provider identifier or edge computing service provider identifier provided by the EEC 103.

[0090] The EEC 103 may operate to request user consent from the AC 102 as part of an EAS discovery procedure with the EES 107 (operation 204). In one embodiment, upon receiving an EAS discovery response message from the EES 107 indicating failure of the EAS discovery request in operation 203, the EEC 103 may operate to request user consent from the AC 102, as described above. As described above, the EEC 103 may request user consent to provide an AC profile to the EES provider while providing an EES provider identifier to the AC 102.

[0091] FIG. 3 is a flowchart illustrating another example of a procedure for providing application client (AC) information according to an embodiment of the present disclosure.

[0092] 3, in operation 301, the application client (AC) 102 may send an AC registration request message to the edge enabler client (EEC) 103. In one embodiment, the AC registration request message may be sent after the installation of the application client (AC) 102 is completed and the storage location (built-in memory or external storage device (e.g., shared storage space) of the terminal 101) of information related to the AC 102 (e.g., AC profile) is confirmed. In one embodiment, the AC registration request message may include at least one of the following information:

[0093] - A storage address indicating where AC-related information is stored (e.g., an app-specific storage URI or a shared storage URI) - invocation information (e.g. application package name / identifier) ​​that can be used to invoke the AC 102 from other applications or devices (e.g. EEC 103) in the terminal 101 -EAS selection request delegation indicator: This indicator can be used to instruct the EEC 103 to select at least one EAS (e.g., EAS 106) among multiple edge application servers (EASs) that it has discovered and to perform an operation of notifying the AC 102. If the indicator is not included in the AC registration request message or the instruction includes content instructing to notify all discovered EASs, the EEC 103 can transmit information (e.g., addresses or identifiers) of all discovered EASs to the AC 102 via a message (e.g., operation 306).

[0094] In operation 302, the EEC 103 may use the storage address received from the AC 102 via the AC registration request message to obtain at least one of the following AC-related information:

[0095] - an AC profile configured in the AC 102 (e.g., including at least one of an AC identifier, an AC type, or a key performance indicator); - A DNN configured in the AC (which may be a DNN that identifies an edge data network (EDN)) - At least one of an ECS address that identifies an edge configuration server (ECS) configured in AC102 (e.g., edge configuration server 108 in FIG. 1), an ECS provider identifier (or an identifier of an edge computing service provider), or an indicator indicating whether another ECS other than the ECS address configured in AC102 is available.

[0096] - User consent on whether to allow external exposure of the AC profile: If the EEC 103 obtains user consent, the EEC 103 can include the AC profile in a service provisioning request message (e.g., at operation 304) or an EAS discovery request message (e.g., at operation 305) to provide an edge enabler server (EES) 107 or an edge configuration server (ECS) 108dp.

[0097] - Invocation information (e.g., application package name / identifier) ​​that can be used to invoke AC102 from other applications or devices (e.g., EEC103) in terminal 101 (which may vary depending on the OS of terminal 101): this invocation information can be used by EEC103 to invoke AC102 and direct it to perform a specific action (e.g., an action requesting user consent for external exposure of the AC profile).

[0098] Information required to induce a specific action of AC102 (e.g., action identifier or activity name): Information used in EEC103 to call AC102 to induce the specific action as necessary may include, for example, initialization of the cached server address. The action identifier / activity name may be used to request AC102 to induce the specific action (e.g., an action requesting user consent for external exposure of an AC profile) via the OS of terminal 101.

[0099] In operation 303, the EEC 103 may confirm that the storage location provided by the AC 102 through the AC registration request message allows AC-related information to be obtained in a service provisioning procedure (e.g., operation 304) or an EAS discovery procedure (e.g., operation 305), and may send an AC registration response message to the AC 102. If the AC-related information cannot be obtained in the storage location, the EEC 103 may include an indicator requesting AC-related information in the AC registration response message sent to the AC 102. In one embodiment, the indicator may indicate at least one of an ECS address request indication, a traffic descriptor request indication, a configured DNN request indication, or a request for user consent to external sharing and exposure of the AC profile.

[0100] 2. Operation 303-1, operation 304, operation 305, operation 306, and operation 307 may be the same as operation 202-1, operation 203, operation 204, operation 205, and operation 206 in FIG.

[0101] In operation 303-1, the EEC 103 may select an edge enabler server (EES) (e.g., EES 107) and at least one edge configuration server (ECS) (e.g., ECS 108) of an edge data network (EDN) (e.g., EDN 105) to access based on the AC-related information. In operation 304, the EEC 103 may execute a service provisioning procedure for the selected ECS. If a user consent is obtained for the AC profile and the external exposure of the AC profile, in the service provisioning procedure, the EEC 103 may include the AC profile in a service provisioning request message sent to the ECS 108. Through a service provisioning response message corresponding to the service provisioning request message, the EEC 103 may obtain configuration information related to the EES 107 in the EDN 105.

[0102] In operation 305, the EEC 103 may send an EEC registration request message and / or an EAS discovery request message to the EES 107 based on the configuration information. The EEC registration request message and / or the EAS discovery request message may include an AC profile obtained from the AC 102 if a user consent is included in the AC registration request message. The EEC 103 may receive at least one response message corresponding to the EEC registration request message and / or the EAS discovery request message from the EES 107. The response message may include EAS information (e.g., an address and / or an identifier).

[0103] In operation 306, the EEC 103 may deliver the EAS information acquired from the EES 107 to the AC 102 via an EAS profile info delivery message. If multiple pieces of EAS information are acquired through a service provisioning procedure and the AC registration request message received in operation 301 includes an EAS selection request delegation indicator, the EEC 103 may select one EAS from the multiple pieces of EAS information acquired from the EES 107 and provide it to the AC 102 via an EAS profile info delivery message. The AC 102 may access an EAS (e.g., the EAS 106) according to the EAS information provided by the EEC 103 to provide an edge computing service.

[0104] When multiple EAS information are provided from the EEC 103 to the AC 102, the AC 102 may select an EAS (e.g., the EAS 106) to actually access based on the multiple EAS information, and access the selected EAS 106 to provide edge computing services. In operation 307, the AC 102 may communicate information regarding the selected EAS 106 to the EEC 103. In one embodiment, the EEC 103 may provide the EAS information indicating the EAS 106 selected by the AC 102 to the EES 107.

[0105] In one embodiment, upon receiving an EAS discovery response message from the ECS 108 indicating failure of the EAS discovery request in operation 304, the EEC 103 may operate to request user consent from the AC 102, as described above. As described above, the EEC 103 may request user consent for providing an AC profile to the ECS provider while providing an ECS provider identifier to the AC 102.

[0106] In an embodiment described below, the EEC 103 can derive a UE route selection policy (URSP) using AC-related information (e.g., application information) obtained from the AC 102. The URSP rules can be used to steer packing between applications and protocol data unit (PDU) sessions of the terminal 101.

[0107] In one embodiment, when the EEC 103 receives a DNN from the AC 102 or traffic descriptor information that can be matched to the traffic descriptor and a DNN replacement allowance [granted] indication from the AC 102, the EEC 103 can guide the URSP determination / provisioning of the ECS 108 based on the DNN or traffic descriptor information and the DNN replacement allowance indication. In one embodiment, the traffic descriptor information can include at least one of a domain descriptor, a connection capability, slice information, or a traffic type, for example. In one embodiment, the DNN replacement allowance indication can include a PLMN ID indicating a PLMN where the replacement is allowed by AC-provider.

[0108] FIG. 4 is a flowchart illustrating a procedure for executing a URSP guide based on application client (AC) information according to an embodiment of the present disclosure.

[0109] 4, in operation 401, the EEC 103 may receive an AC registration request message from the AC 102, the AC registration request message including at least one DNN (hereinafter referred to as AC-provided DNN), at least one PLMN ID, traffic descriptor information that may match the traffic descriptor, or at least one of a DNN substitution permission indication. In one embodiment, the traffic descriptor information may include at least one of a domain descriptor, a connection capability, a traffic type, an AC-provided domain name (e.g., a fully qualified domain name (FQDN)), a traffic category, or requested network connection capabilities that can be matched with traffic descriptor in URSP (e.g., ims, xr / vr).

[0110] In one embodiment, the DNN replacement permission indication may include a list of PLMN IDs indicating a PLMN where the replacement is allowed by an AC-provider. In one embodiment, the list of PLMN IDs may indicate PLMN#1 (107a) and PLMN#2 (107b).

[0111] In one embodiment, the DNN provided by the AC 102 may be set according to an agreement between an operator of a particular mobile communication network and an AC provider, and the DNN may be valid only in the mobile communication network. The DNN or traffic descriptor information may be sent to the EEC 103 via an AC registration request message of the AC 102, for example. Also, the ECS address set in the AC 102 may be provided to the EEC 103 together with the DNN or traffic descriptor information.

[0112] In operation 402, the EEC 103 may send an AC registration response to the AC registration request message to the AC 102. The AC registration response message may include a result indicating successful receipt and storage of the information provided by the AC 102.

[0113] In operation 403, the EEC 103, through operations such as interlocking with the MT, can confirm whether the terminal 101 has accessed / registered to 5GC and whether the terminal 101 supports URSP, and can transmit a service provisioning request message and a URSP guidance request message to the ECS 108 for AF-guidance to USRP determination / provisioning of the ECS 108. In one embodiment, the service provisioning request message can include information provided by the AC 102 in operation 401 and an instruction to execute URSP guidance.

[0114] In one embodiment, the EEC 103 may operate as follows.

[0115] A. When the list of {DNN, PLMN ID} pairs is provided by the AC 102, the EEC 103 can send the AC-provided DNN, AC-provided domain name (e.g., FQDN), traffic category, or requested network connection capabilities that can be matched with traffic descriptor in URSP (e.g., ims, xr / vr,) and an indication to request URSP guidance: indication to request to perform AF-guidance to URSP to the ECS 108. For example, the information can be conveyed in a service provisioning request message. Through the information, the EEC 103 can enable the ECS 108 to perform AF-guidance to URSP determination.

[0116] In one embodiment, the EEC 103 can include an indication to guide URSP rules for any UE in a message (e.g., a service provisioning request message or a URSP guidance request message) sent to the ECS 108. The indication to guide URSP rules for any UE is for the purpose of allowing the URSP to be applied to other terminals using the same service. Depending on the information provided by the AC 102, the EEC 103 can operate as follows:

[0117] - If multiple {DNN, PLMN ID} pairs are provided by AC102, EEC103 can either include the AC-provided DNN corresponding to the serving PLMN ID to which terminal 101 is currently connected in a service provisioning request message and send it to ECS108, or send a list of {DNN, PLMN ID} pairs received from AC102 to ECS108.

[0118] - If the EEC 103 knows the URSP rule currently set in the terminal 101, the EEC 103 can determine whether a collision occurs in the URSP rule. In one embodiment, the EEC 103 can check whether the DNN (DNN value included in a route selection descriptor in the URSP rule set in the terminal or provided by the core network) according to the URSP rule of the terminal 101 is the same as the DNN in the EDN setting information provided by the ECS 108, and recognize that a collision has occurred if they are different. In one embodiment, the EEC 103 can include an URSP guidance execution instruction in a service provisioning request message sent to the ECS 108 if the AC-provided DNN is different from the EDN setting information.

[0119] B. When the AC 102 is provided with traffic descriptor information (e.g., at least one of an AC-provided domain name (e.g., FQDN), a traffic category, or requested network connection capabilities) that can match the traffic descriptor without providing a DNN, the EEC 103 can check a route selection component that matches the traffic descriptor information in the URSP rule set in the terminal 101. When the DNN that matches the traffic descriptor information is different from the DNN included in the EDN setting information, the EEC 103 can provide an URSP guidance execution instruction to the ECS 108 together with the traffic descriptor information (e.g., at least one of an AC-provided domain name (e.g., FQDN), a traffic category, or requested network connection capabilities). In one embodiment, even if there is no EDN configuration information in the EEC 103, the EEC 103 can provide URSP guidance execution instructions to the ECS 108 along with traffic descriptor information.

[0120] According to one embodiment, in operation 403, the EEC 103 can provide the URSP guidance execution instructions and traffic descriptor information to the ECS 108 via a separate URSP guidance initiation procedure rather than a service provisioning procedure.

[0121] In operation 403-1, the ECS 108 can determine whether a URSP guidance execution instruction is included in the message (e.g., service provisioning request message) received from the EEC 103, and process the service provisioning request according to the service provisioning request message. If the service provisioning request message includes a URSP guidance execution instruction, in operation 404, the ECS 108 can send an AF request message for AF-guidance to determine URSP rules to an NF node (e.g., NEF or PCF) of the core network to which the terminal 101 is connected and registered.

[0122] In one embodiment, the ECS 108 may determine which PLMN to select and send the AF request message based on the information provided by the EEC 103. In one embodiment, the ECS 108 may select a network function node 104a belonging to a serving PLMN (e.g., PLMN#1, 5GC) of the terminal 101 based on the AC-provided PLMN ID provided by the EEC 103 via the service provisioning request message in operation 403 and a serving PLMN ID to which the terminal 101 is currently connected, and send the AF request message to the selected network function node 104a.

[0123] The AF request message may include an application traffic descriptor that stores at least one of the AC-provided DNN, AC-provided domain name (e.g., FQDN), traffic category, or requested network connection capabilities provided from the EEC 103 in operation 403, and may include EDN connection information (e.g., DNN and / or S-NSSAI) of the EDN (e.g., EDN 105) as a route selection parameter.

[0124] If the ECS 108 receives an "indication to guide URSP rules for any UE" from the EEC 103 via a service provisioning request message or a URSP guidance request message in operation 403, the ECS 108 may include the indication in an AF request message and send it to the network function node 104a. In one embodiment, if a service area of ​​the EDN 105, EES 107, or EAS 106 is defined, the ECS 108 may set a "spatial validity condition" in the AF request message to a value indicating the defined service area (e.g., a tracking area identity (TAI) or geographical area information) and send it to the network function node 104a.

[0125] In operation 405, the network function node 104a (e.g., NEF) may perform a URSP determination based on the AF request message received from the ECS 108, generate a URSP rule, and trigger a procedure to communicate the generated URSP rule to the terminal 101. In one embodiment, information about the URSP rule may be communicated to the terminal 101 via the mobile communication network by at least one network function node of the core network.

[0126] In operation 406, the network function node 104a may confirm that the URSP rule has been successfully delivered to the terminal 101 via the mobile communication network and may send a response message to the AF request message to the ECS 108. The response message may include an indication that the URSP rule has been successfully established in the terminal 101.

[0127] In operation 407, the ECS 108 may send a response message (e.g., a service provisioning response message) to the EEC in response to the message (e.g., the service provisioning request message) received from the EEC 103 in operation 403. The service provisioning response message may include the EDN configuration information as well as a result ("URSP determination") indicating that AF direction to the URSP was successfully performed.

[0128] In operation 408, the EEC 103 confirms the success of the EDN configuration information and AF guidance to the URSP transmitted from the ECS 108, and transmits an EC guidance notification message to the AC 102, including an indication that the edge computing service is available ('Indication that EC is available') and an indication of whether the DNN currently configured in the AC 102 can be used as a traffic descriptor (e.g., a notification that the DNN configured in the AC 102 should not be used as a traffic descriptor). In one embodiment, the edge computing guidance notification message may inform the AC 102 that the URSP rule is valid. In one embodiment, the EEC 103 may transmit the EAS information acquired through the EAS discovery procedure to the AC 102 by including it in the edge computing guidance notification message after completing the EAS discovery procedure using the EDN configuration information provided by the ECS 108.

[0129] FIG. 5 is a flowchart illustrating a procedure for obtaining application client (AC) information and providing a notification service according to an embodiment of the present disclosure.

[0130] 5, in operation 501, the application client (AC) 102 may send an AC subscription request message (or an AC information subscription request message) to the edge enabler client (EEC) 103. In one embodiment, the transmission of the AC subscription request message may be performed after the installation of the application client (AC) 102 is completed and the storage location (the internal memory or an external storage device (e.g., a shared storage space) of the terminal 101) of information related to the AC 102 (e.g., an AC profile) is confirmed. In one embodiment, the AC subscription request message may include at least one of the following information:

[0131] - Notification target address: the address at which the AC 102 receives notification messages from the EEC 103 - invocation information (e.g. application package name / identifier) ​​that can be used to invoke the AC 102 from another application or device (e.g. EEC 103) in the terminal 101 - Information required to induce a specific action of AC102 (e.g., action identifier or activity name): If necessary, the action identifier / activity name can be used to request AC102 to induce a specific action (e.g., "initialization of the cached server address") via the OS of terminal 101 as information used by EEC103 to call AC102 to induce the specific action.

[0132] - Mobility related event identifier (event ID): may indicate at least one of "change of target EAS", "target EAS discovery for ACR (application context relocation)", or "ACR event".

[0133] In operation 502, the EEC 103 may store the information included in the AC registration request message received from the AC 102 as subscription information. In one embodiment, the EEC 103 may send a subscribe request message (e.g., an EAS discovery subscription request message or an ACR information subscription request message) to a required notification server to the EES (e.g., the source EES 107d) according to the mobility-related event identifier.

[0134] In one embodiment, if the EEC 103 receives a “change of target EAS” event identifier from the AC 102, it can include the event identifier and EAS discovery filters set to “EAS availability change” in an EAS discovery subscription request message to the EES 107d. In one embodiment, if the EEC 103 is provided with an event identifier set to “ACR event” by the AC 102, it can include the event identifier set to “ACR complete” in an ACR information subscription request message to the EES 107d. In one embodiment, if the EEC 103 receives an event identifier set to "target EAS discovery for ACR" from the AC 102, the EEC 103 may send an ACR information subscription request message to the EES 107d, including the event identifier set to "target information notification."

[0135] In operation 503, the EEC 103 may transmit to the AC 102 an AC join response message in response to the AC join request message received from the AC 102. The AC join response message may include information indicating whether the EEC 103 can sense and provide an event for which the AC 102 requires notification.

[0136] In operation 504, the EEC 103 may perform an application context relocation (ACR) procedure to maintain service continuity in response to the movement of the terminal 101. The application context relocation procedure may include a procedure of relocating an EEC context from the source EES 107d to the target EES 107c according to a decision of the EEC 103. While performing the application context relocation procedure, the EEC 103 may identify information regarding the target EAS (not shown) to which the AC 102 is connected and the execution result of the application context relocation procedure (successful or not).

[0137] In operation 505, the EEC 103 may check the execution result of the application context reallocation procedure and provide an event notification message including an ACR result indication indicating the execution result and the target EAS information to the AC 120. In one embodiment, when the EEC 103 recognizes via operation 501 that it cannot find a new target EAS or the application context reallocation procedure was not successfully executed and the AC 102 is using its own cache, the EEC 103 may send an 'Indication to initialize cached EAS address' to the AC 102 together with an ACR result indication indicating the failure of the application context reallocation procedure.

[0138] FIG. 6 is a block diagram showing a configuration of a terminal (UE) according to an embodiment of the present disclosure.

[0139] 6, a terminal (UE) (e.g., terminal 101) may be implemented to include a processor 605 capable of performing wireless communication according to a communication method defined in a wireless communication system supporting edge computing according to the above-described embodiment, a transceiver 610, and a memory 615. In one embodiment, the processor 605, the transceiver 610, and the memory 615 may be implemented in the form of at least one chip.

[0140] The processor 605 controls the operation of the transceiver 610 and, using programs (e.g., an application client (AC) 102 and an edge enabler client (EEC)) installed and / or stored in the memory 615, can provide AC information according to the embodiments of Figures 1 to 5 and combinations of at least two of these embodiments, and can control the entire components of the terminal 101 so that configuration information related to edge computing services can be provided from the edge configuration server (ECS) 108 and the edge enabler server (EES) 107.

[0141] Fig. 7 is a block diagram showing a configuration of a network entity according to an embodiment of the present disclosure. The illustrated network entity may be, for example, at least one of the components of the EAS, EES, ECS, and core network described in Fig. 1 to Fig. 5. The network entity may also be implemented in the form of, for example, a server.

[0142] Referring to FIG. 7, the network entity may be implemented to include a processor 705 capable of performing wired / wireless communication in accordance with a communication method defined in a wireless communication system supporting edge computing, a communication interface 710, and a memory 715.

[0143] The processor 705 controls the operation of the communication interface 710 and, using the programs installed and / or stored in the memory 715 (functions of each component of the EAS, EES, ECS, or core network described in Figures 1 to 5), can obtain AC information and control the entire components of the network entity so that the terminal 101 can be provided with configuration information related to the edge computing service by the embodiments of Figures 1 to 5 and a combination of at least two of these embodiments.

[0144] According to one embodiment, a communication method by an edge enabler client (EEC) of a terminal (UE) in a wireless communication system supporting edge computing includes a step 201 of receiving an AC registration request message from an application client (AC) running in the terminal, the AC registration request message including an AC profile, an edge configuration server (ECS) address, and a user consent indicating whether or not to allow external exposure of the AC profile; a step 202-1 of selecting an edge configuration server (ECS) for performing service provisioning based on the AC registration request message; a step 203 of performing a service provisioning procedure for the selected ECS; a step 204 of performing EEC registration and edge application server (EAS) discovery for an edge enabler server (EES) obtained through the service provisioning procedure; and a step 205 of transmitting EAS information obtained through the EAS discovery from the EES to the AC.

[0145] In one embodiment, the process of selecting the ECS may include, if there is no ECS address configured in the EEC or no ECS address provided by the core network, selecting the ECS using the ECS address included in the AC registration request message, and, if there is an ECS address configured in the EEC or no ECS address provided by the core network, selecting the ECS by preferentially using the ECS address included in the AC registration request message.

[0146] In one embodiment, the process of performing the service provisioning procedure may include an operation of sending a service provisioning request message including the AC profile to the selected ECS if the user consent included in the AC registration request message indicates that external exposure of the AC profile is permitted.

[0147] In one embodiment, the AC registration request message may include an application package name that can be used to invoke the AC from the EEC and an action identifier required to direct the AC to perform an action to obtain user consent on whether to allow external exposure of the AC profile.

[0148] In one embodiment, the AC registration request message may include an EAS selection request delegation instruction indicating whether to notify the AC of all of the discovered EASs or to notify the AC of at least one selected of the discovered EASs when multiple EASs are discovered through the EAS discovery.

[0149] According to one embodiment, a communication method by an edge enabler client (EEC) of a terminal (UE) in a wireless communication system supporting edge computing includes a step 301 of receiving an AC registration request message including a storage address of AC-related information from an application client (AC) running in the terminal, a step 302 of acquiring the AC-related information from the storage address, the AC-related information including an AC profile, an edge configuration server (ECS) address, and a user consent indicating whether or not to allow external exposure of the AC profile, and a step 303-1 of selecting an edge configuration server (ECS) for performing service provisioning based on the AC registration request message, a step 304 of performing a service provisioning procedure for the selected ECS, a step 305 of performing EEC registration and edge application server (EAS) discovery for the edge enabler server (EES) acquired by the service provisioning procedure, and a step 306 of transmitting EAS information acquired from the EES through EAS discovery to the AC.

[0150] In one embodiment, the AC-related information may include an application package name that can be used to invoke an AC from the EEC and an action identifier required to direct the AC to perform an action to obtain user consent on whether to allow external exposure of the AC profile.

[0151] In one embodiment, the AC registration request message may include an EAS selection request delegation instruction indicating whether to notify the AC of all of the discovered EASs or to notify the AC of at least one selected of the discovered EASs when multiple EASs are discovered through the EAS discovery.

[0152] According to one embodiment, a communication method by an edge enabler client (EEC) of a terminal UE in a wireless communication system supporting edge computing includes a process 401 of receiving an AC registration request message including a data network name (DNN), a public land mobile network (PLMN) ID, traffic descriptor information, and a DNN substitution permission instruction from an application client (AC) running in the terminal; a process 403 of sending a service provisioning request message including the DNN, traffic descriptor information, and a UE route selection policy (URSP) guidance execution instruction to an edge configuration server (ECS) based on the AC registration request message; a process 407 of receiving a service provisioning response message including a URSP result from the ECS in response to the service provisioning request message; and a process 408 of sending to the AC an indication indicating that an edge computing service is available and an indication indicating whether the DNN set in the AC can be used as a traffic descriptor in response to receiving the service provisioning response message.

[0153] According to one embodiment, a communication method by an edge enabler client (EEC) of a terminal (UE) in a wireless communication system supporting edge computing includes a step 501 of receiving an AC subscription request message from an application client (AC) executed in the terminal, the AC including an address at which the AC receives notification messages, an application package name of the AC, an action identifier required to induce a specific action of the AC, and an indication indicating a change of a target edge application server (EAS); a step 502 of sending a subscription request message to a source edge enabler server (EES) in response to the indication indicating the change of the target EAS; a step 503 of sending an AC subscription response message corresponding to the AC subscription request message to the AC; a step 504 of the terminal performing an application context reallocation procedure for maintaining service continuity by moving from the source EES to a target EES; and a step 505 of sending an indication indicating a result of the application context reallocation procedure and target edge application server (EAS) information to the AC.

[0154] According to one embodiment, an edge enabler client (EEC) of a terminal may be configured to perform at least one or a combination of the methods according to the embodiments of the present disclosure.

[0155] An edge configuration server (ECS) according to one embodiment may be configured to perform at least one or a combination of methods according to embodiments of the present disclosure.

[0156] Although this disclosure describes an edge computing server (e.g., EES or ECS), any application server capable of interfacing with a 3GPP network system may be included within the scope of various embodiments of this disclosure.

[0157] In the present disclosure, specific embodiments have been described, but it goes without saying that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims below, but also by equivalents to the scope of the claims. [Explanation of symbols]

[0158] 101 Terminal 102 Application client (AC) 103 Edge enabler client (EDE) 104 3GPP(registered trademark) Core Network 104a Network Function Node 105 Edge Data Network (EDG) 106 Edge application server (EAS) 107 Edge enabler server (EES) 108 Edge configuration server (ECS) 108dp Edge Configuration Server (ECS) 201 Operation 202 Operation 203 Operation 204 Operation 205 Operation 206 Operation 301 operation 302 operation 303 operation 304 operation 305 operation 306 operation 307 operation 401 operation 402 operation 403 operation 404 operation 405 operation 406 operation 407 operation 408 operation 501 operation 502 operation 503 operation 504 operation 505 operation 605 Processor 610 Transmitter / Receiver 615 Memory 705 Processor 710 Communication Interface 715 Memory

Claims

1. A method of communication by a terminal (UE) in a wireless communication system supporting edge computing, comprising: sending an AC registration request message for an AC registration request by an application client (AC) of the terminal to an edge enabler client (EEC) of the terminal; sending, by the EEC, an AC registration response message corresponding to the AC registration request message to the AC; The AC registration request message includes an AC profile, an Edge Configuration Server (ECS) address, and an ECS provider ID; The communication method, wherein the AC registration response message includes information indicating that the AC registration request is successful.

2. 2. The communication method of claim 1, further comprising: selecting the ECS using the ECS address included in the AC registration request message if there is no ECS address pre-configured in the EEC or provided by a core network.

3. 2. The method of claim 1, further comprising: if a user consent included in the AC registration request message indicates that external exposure of the AC profile is permitted, transmitting, by the AC, a service provisioning request message including the AC profile to the ECS.

4. The AC registration request message 2. The method of claim 1, further comprising: an application package name that can be used to invoke the AC from the EEC; and an action identifier required to direct the AC to perform an action to obtain user consent regarding whether to allow external exposure of the AC profile.

5. The AC registration request message 2. The method of claim 1, further comprising an EAS selection request delegation instruction indicating whether to notify the AC of all of the discovered EASs or to notify the AC of at least one selected EAS from the discovered EASs.

6. A communication method by an edge enabler client (EEC) of a terminal (UE) in a wireless communication system supporting edge computing, comprising: receiving an AC registration request message from an application client (AC) running in the terminal, the AC registration request message including a data network name (DNN), a public land mobile network (PLMN) ID, traffic descriptor information, and a DNN substitution permission indication; sending a service provisioning request message to an edge configuration server (ECS) based on the AC registration request message, the service provisioning request message including the DNN, traffic descriptor information, and a UE route selection policy (URSP) guidance execution instruction; receiving a service provisioning response message from the ECS in response to the service provisioning request message, the service provisioning response message including a URSP result; In response to receiving the service provisioning response message, transmitting to the AC an indication that an edge computing service is available and an indication that a DNN configured in the AC can be used as a traffic descriptor.

7. A terminal (UE) of a wireless communication system that supports edge computing, A transmitter / receiver, a processor executing an edge enabler client (EEC), the processor comprising: Sending an AC registration request message to an edge enabler client (EEC) of the terminal for an AC registration request by an application client (AC) of the terminal; configured to send, by the EEC, an AC registration response message corresponding to the AC registration request message to the AC; The AC registration request message includes an AC profile, an Edge Configuration Server (ECS) address, and an ECS provider ID; The AC registration response message is configured to include information indicating that the AC registration request is successful. A terminal characterized by:

8. The processor: The terminal of claim 7, further configured to: select the ECS using the ECS address included in the AC registration request message when there is no ECS address pre-configured in the EEC or provided by a core network.

9. The processor:

8. The terminal according to claim 7, wherein, when a user consent included in the AC registration request message indicates that external exposure of the AC profile is permitted, the AC sends a service provisioning request message including the AC profile to the ECS.

10. The AC registration request message 8. The terminal according to claim 7, further comprising an application package name that can be used to call the AC from the EEC, and an action identifier required to cause the AC to perform an action to obtain user consent regarding whether to allow external exposure of the AC profile.

11. The AC registration request message 8. The terminal of claim 7, further comprising an EAS selection request delegation instruction indicating whether to notify the AC of all of the discovered EASs or to notify the AC of at least one selected EAS from the discovered EASs.

12. A terminal (UE) in a wireless communication system that supports edge computing, comprising: A transmitter / receiver, a processor executing an edge enabler client (EEC), the processor comprising: receiving an AC registration request message from an application client (AC) running in the terminal, the AC registration request message including a data network name (DNN), a public land mobile network (PLMN) ID, traffic descriptor information, and a DNN substitution permission indication; Sending a service provisioning request message to an edge configuration server (ECS) based on the AC registration request message, the service provisioning request message including the DNN, traffic descriptor information, and a UE route selection policy (URSP) guidance execution indicator; receiving a service provisioning response message from the ECS in response to the service provisioning request message, the service provisioning response message including a URSP result; A terminal configured to transmit, in response to receiving the service provisioning response message, to the AC, an indicator indicating that an edge computing service is available and an indicator indicating whether a DNN configured in the AC can be used as a traffic descriptor.

Images