Method for providing edge computing service information through wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data rates. The invention provides a method for providing edge computing service information through application triggering in an edge computing system. More specifically, the present disclosure provides a method and device for providing interworking among an edge enabler client (EEC), an edge enabler server, and an edge configuration server (ECS) constituting an edge computing system in a wireless communication system using a device trigger or an application trigger.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system and an edge computing system, and more particularly to a method and device for providing edge computing service information through a mobile communication system. Background Art

[0002] 5G mobile communication technology defines a wide frequency band to realize fast transmission speed and new services, and can be realized not only in a frequency band of 6 GHz or less ("below 6 GHz"), such as 3.5 GHz, but also in an ultra-high frequency band ("above 6 GHz") called mmWave, such as 28 GHz and 39 GHz. In addition, in the case of 6G mobile communication technology called a super 5G system, in order to realize a transmission speed 50 times faster than that of 5G mobile communication technology and an ultra-low latency reduced to 1 / 10 compared to 5G mobile communication technology, implementation in a terahertz band (for example, such as a 95 GHz to 3 terahertz (3THz) band) is being considered.

[0003] In the early days of 5G mobile communication technology, with the goal of meeting the service support and performance requirements of enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine-type communication (mMTC), beamforming and massive MIMO have been standardized to mitigate the path loss of radio waves in the UHF band and increase the propagation distance of radio waves, support various parameter sets (multiple subcarrier spacing operation, etc.) to effectively use UHF resources and dynamic operation of time slot formats, definition and operation of bandwidth parts (BWPs), new channel coding methods such as low-density parity-check (LDPC) codes for large-capacity data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing to provide dedicated networks dedicated to specific services.

[0004] Currently, considering the services that 5G mobile communication technology is intended to support, as well as physical layer standardization of technologies such as Vehicle-to-Everything (V2X) for helping driving determine autonomous vehicles and increasing user convenience based on the location and status information of vehicles transmitted by the vehicles, New Radio Unlicensed (NR-U) for system operation that meets various regulatory requirements in unlicensed bands, NR UE power saving, Non-Terrestrial Network (NTN) (which is direct UE-satellite communication for securing coverage in areas where communication with terrestrial networks is not possible), and positioning technology in progress), discussions are underway to improve the initial 5G mobile communication technology and enhance its performance.

[0005] In addition, standardization is also underway in the field of air interface architecture / protocol for technologies such as the Industrial Internet of Things (IIoT) that supports new services through connections and convergence with other industries, Integrated Access and Backhaul (IAB) for providing nodes for extending network service areas by integrating wireless backhaul links and access links, mobility enhancements including conditional handover and dual active protocol stack (DAPS) handover, and 2-step RACH for a simplified random access procedure for NR, and standardization is also underway in the field of system architecture / service for a 5G baseline architecture (e.g., service-based architecture, service-based interface) for applying the following technologies: Network Function Virtualization (NFV) and Software Defined Network (SDN) technologies, Mobile Edge Computing (MEC) for receiving services based on the location of the UE, etc.

[0006] When such 5G mobile communication systems are commercialized, connected devices that are in an explosive growth trend will be connected to the communication network; therefore, it is expected that functional and performance enhancements of 5G mobile communication systems and integrated operations of connected devices will be required. To this end, new research will be conducted on extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., 5G performance improvement and complexity reduction using artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, the development of such 5G mobile communication systems will be the basis for the development of full-duplex technology for improving the frequency efficiency and system network of 6G mobile communication technology, satellite, AI-based communication technology that utilizes artificial intelligence (AI) from the design stage and achieves system optimization by internalizing end-to-end AI support functions, and next-generation distributed computing technology that enables complex services beyond the limits of UE computing capabilities by utilizing ultra-high-performance communication and computing resources and new waveforms for ensuring coverage in the terahertz band of 6G mobile communication technology. Full-dimensional MIMO (FD-MIMO), multi-antenna transmission technology such as array antennas and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable smart surface (RIS) technology. Summary of the invention

[0008] Technical issues

[0009] If the edge data network configuration information or edge application server (EAS) information stored in the ECS or EES is changed, a notification service according to such a change should be provided to the EEC. In this case, in order to provide the notification service, the connection state between the EEC and the EES / ECS should be continuously maintained, and when the keep-alive operation for this is performed, the terminal power consumption may increase. As a method for solving this problem, there is a device trigger method provided by a wireless communication system, but because the processes to be performed between the EEC and the EES are diverse, a method for determining which process to be performed is required.

[0010] Solution to the problem

[0011] According to an embodiment of the present disclosure for solving the above-mentioned problem, a method performed by a terminal in a communication system may include: sending a request message by an edge enabler client (EEC) of the terminal to a server of an edge data network (EDN), the request message including an indication that an EEC trigger is requested, and the server of the EDN includes an edge configuration server (ECS) or an edge enabler server (EES); based on the request message, receiving a message including information about a trigger payload from the server; and performing a process based on trigger payload selection, wherein the trigger payload may include information indicating a process through EDGE-1 or a process through EDGE-4.

[0012] In addition, according to an embodiment of the present disclosure, a method performed by a server of an edge data network (EDN) in a communication system may include: receiving a request message from a terminal, the request message including an indication that an edge enabler client (EEC) trigger is requested; and sending a message including information about a trigger payload to the terminal based on the request message, the trigger payload including information indicating a process through EDGE-1 or a process through EDGE-4, wherein the server may include an edge configuration server (ECS) or an edge enabler server (EES), and wherein a process based on the trigger payload selection may be performed with the ECS or the EES.

[0013] In addition, according to an embodiment of the present disclosure, a terminal in a communication system may include: a transceiver; and a controller, which includes an edge enabler client (EEC), configured to control the transceiver to send a request message including an indication that an EEC trigger is requested to a server of an edge data network (EDN), the server including an edge configuration server (ECS) or an edge enabler server (EES) to control the transceiver to receive a message including information about a trigger payload from the server based on the request message, and perform a process based on the trigger payload selection, wherein the trigger payload may include information indicating a process through EDGE-1 or a process through EDGE-4.

[0014] In addition, according to an embodiment of the present disclosure, a server of an edge data network (EDN) in a communication system may include: a transceiver; and a controller, configured to control the transceiver to receive a request message including an indication that an edge enabler client (EEC) trigger is requested from a terminal, and control the transceiver to send a message including information about a trigger payload to the terminal based on the request message, the trigger payload including information indicating a process through EDGE-1 or a process through EDGE-4, wherein the server of the EDN may include an edge configuration server (ECS) or an edge enabler server (EES), and wherein the process selected based on the trigger payload may be performed with the ECS or the ESS.

[0015] Advantageous Effects of the Invention

[0016] The present invention provides a method for selecting and executing necessary processes between EEC and EES / ECS while solving the above-mentioned problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Regarding the description of the drawings, the same or similar reference numerals may be used for the same or similar components.

[0018] Figure 1 is a block diagram showing the structure of an edge computing system according to an embodiment of the present disclosure.

[0019] Figure 2 is a signal flow chart illustrating an EEC triggering process of an ECS according to an embodiment of the present disclosure.

[0020] Figure 3 is a signal flow diagram illustrating an EEC triggering process of an EES according to an embodiment of the present disclosure.

[0021] Figure 4 is a block diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.

[0022] Figure 5 is a block diagram showing the structure of a server on an edge computing system according to an embodiment of the present disclosure.

[0023] Figure 6 is a block diagram showing the structure of a network function entity according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0024] Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. The terms described below are defined in consideration of the functions in the present disclosure. Because this may vary according to the intention or habit of the user or operator, the definition should be determined according to the content throughout this specification.

[0025] For ease of description, the terms used in the present disclosure referring to network entities and objects of the edge computing system, terms referring to messages, terms referring to identification information, etc. are exemplified. Therefore, it is obvious to those skilled in the art that the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0026] Hereinafter, for convenience, the present disclosure uses terms and names defined in the 5G system standard, but it is not limited to the terms and names and can be equally applied to systems conforming to other standards.

[0027] Figure 1 is a block diagram illustrating an example of an edge computing system.

[0028] The edge computing system may include an edge enabler server (EES) 110 , an edge configuration server (ECS) 120 , and an edge enabler client (EEC) 140 .

[0029] The EES 110 is building an edge hosting environment (or edge computing platform) and knows information about edge application servers (EAS) 130 running in the edge hosting environment. The EES 110 communicates with user devices ( Figure 1 The UE 10 of the edge computing system may be configured to negotiate with the application client 150 of the UE 10 and the EAS 130, and perform functions of connecting the application client 150 of the UE 10 and the EAS 130 in the edge hosting environment. The UE supporting the edge computing system may have a built-in EEC 140, and the negotiation may be performed through the interconnection between the EEC 140 and the EES 110. For the above-mentioned negotiation, the layer that performs the interconnection between the EEC 140 and the EES 110 may be referred to as an edge enabling layer. The UE 10 described in the present disclosure includes not only smart phones, but also Internet of Things (IoT) devices and vehicles.

[0030] The ECS 120 knows the deployment information of the EES 110 and performs the function of delivering configuration information for using edge computing services to the UE. Here, the configuration information may include edge data network connection information (e.g., data network name, signal network slice selection assistance information (S-NSSAI), etc.), edge data network service area information (e.g., cell list, tracking area list, public land mobile network (PLMN) identification (ID) or edge enabler server connection information (e.g., uniform resource identifier (URI)). The edge data network service area information may be information about the available area of ​​the edge enabler server configured by the EES 110. Based on this, the UE can obtain edge enabler server information accessible at a specific location. When the ECS 120 can obtain information about the edge enabler server running within the edge hosting environment of a specific edge enabler server, the UE 10 can obtain information about the edge application server through the EEC 140.

[0031] EAS 130 means a third-party application server running within an edge computing system. More specifically, EAS 130 is a third-party application server running on the premise of an infrastructure provided in an edge hosting environment, and can provide ultra-low latency services because EAS 130 can provide services at a location close to the UE.

[0032] In the UE 10, there may be an application client 150, an EEC 140 linking an edge computing service with the application client 150, and a mobile terminal (MT) not shown in the figure and accessing a mobile communication system. The application of the UE 10 is an application provided by a third party and means a client application for a specific application service running in the UE. Several applications may be run in the UE. At least one of these applications may use mobile edge computing or multi-access edge computing (MEC) services.

[0033] The EEC 140 in the UE 10 means a client that performs operations required to use edge computing services within the UE. The EEC 140 can determine which application can use the edge computing service and perform operations to connect the network interface so that data of the UE application client 150 can be sent to the EAS 130 that provides edge computing services. Here, operations to establish a data connection for using edge computing services can be performed at the 3GPP communication layer by the mobile terminal. The 3GPP communication layer means a layer that performs modem operations for using a mobile communication system and performs the roles of establishing a wireless connection for data communication, registering the UE in the mobile communication system, establishing a connection for data transmission to the mobile communication system, and sending and receiving data.

[0034] Figure 2is a signal flow chart illustrating an EEC triggering process of an ECS according to an embodiment of the present disclosure.

[0035] refer to Figure 2 , the EEC 240 identifies whether at least one of a short message service (SMS) over a non-access stratum (NAS) or an SMS over an Internet Protocol (IP) is supported within the UE 20. In addition, when the UE 20 supports at least one of the SMS over NAS or the SMS over IP, and the EEC 240 supports a device trigger or an application trigger operation (for example, when the EEC can perform decoding on a payload within the SMS message and perform a process according to information in the payload indicated by the ECS 220), the EEC 240 may send an EEC trigger service request to the ECS 220 (S200a), which triggers the execution of a process to the EEC using EDGE-1 or EDGE-4.

[0036] Here, the EEC trigger service request transmission message may include at least one of information such as an EEC trigger request indication, a trigger service description (service provision), a trigger service period, a trigger service area, a port ID, a UE ID, or an EEC ID. In addition, the trigger service description may include information about a process that should be triggered or a service that should be called in the EEC. In addition, the trigger service period and the trigger service area information may include information about the time and area where the ECS 220 should perform the EEC trigger.

[0037] The ECS 220 sends a response (S200b) to the EEC 240 regarding whether the ECS 220 can successfully support the EEC triggered service corresponding to the request of the EEC 240. For example, in the case where the ECS 220 can successfully support the EEC triggered service, the ECS 220 can generate a triggered service indication (or a triggered service subscription indication) and provide the triggered service indication to the EEC 240 through the response message of S200b. The ECS 220 can map, store and manage the generated triggered service indication and the EEC ID, UE ID, triggered service description (service provision), triggered service period, triggered service area or port ID. In addition, the EEC 240 can map, store and manage the triggered service indication, EEC ID, UE ID, triggered service description (service provision), triggered service period, triggered service area or port ID, etc. received from the ECS 220. Here, the triggered service indication and the stored information can be used so that the EEC 240 or the ECS 220 stops or modifies the EEC triggered service in the future. For example, the EEC 240 may request to stop the EEC triggered service while sending the triggered service indication, EEC ID, UE ID, and triggered service description to the ECS 220. The ECS 220, which has received the stop request from the EEC 240, may determine the service to be stopped between the EEC triggered service stop target and the corresponding EEC 240 based on the triggered service indication, EEC ID, UE ID, and triggered service description included in the EEC triggered service stop request, and send the result on whether to stop to the EEC 240. As another example, the ECS 220 itself (without a separate request from the EEC) may determine to stop the EEC triggered service for a specific EEC 240. In this case, the ECS 220 may notify the EEC triggered service stop while sending the EEC triggered service indication, EEC ID, and stop target EEC triggered service description to the stopped EEC triggered service target EEC 240.

[0038] The ECS 220 may determine whether an EEC trigger is required (S201). For example, the ECS 220 may detect a change in edge data network configuration information (EES address information, data network name (DNN) or S-NSSAI of the edge data network, EES service area information, edge data network (EDN) service area information, etc.), or may determine to perform an EEC trigger when the edge data network configuration information needs to be updated according to the movement of the UE 20 including the EEC 240.

[0039] When it is determined to perform the EEC trigger, the ECS 220 may request a trigger delivery service and provide a trigger payload or a trigger service period to the network open function (NEF) 22, including a UE identifier, a general public subscription identifier (GPSI), an application function (AF) ID, a trigger reference number, an application port ID, a valid period, a priority, trigger information (trigger service description, an indication of performing service provisioning, an EEC ID, and ECS information (ECS address and identifier)) (S202).

[0040] The NEF 22 may select an SMS-SC and an SMS service center (SMS-SC) 21 associated with a 5G core network function (eg, user data management, access and mobility management functions), and transmit the trigger received from the ECS 220 to the selected SMS-SC 21 ( S203 ).

[0041] Furthermore, the NEF 22 may send a response message indicating that the trigger has been successfully delivered to the SMS-SC 21 to the ECS 220 ( S204 ).

[0042] The SMS-SC 21 sends the SMS to the MT 260 of the UE associated with the 5G core network (S205).

[0043] Furthermore, the SMS-SC 21 transmits message delivery report information on whether the SMS is successfully transmitted to the UE 20 to the NEF 22 ( S206 ).

[0044] NEF 22 may provide ECS 220 with information on whether the trigger message has been successfully transmitted to UE 20 and acquired from SMC-SC 21 (S207). In this case, when ECS 220 receives such information from NEF 22, ECS 220 may predict that EEC 240 will perform service provisioning.

[0045] The MT 260 of the UE may request to perform service provision while providing the EEC 240 with the port ID, the EECID, the ECS information, and the triggered service description information included in the SMS received from the SMS-SC 21 ( S208 ).

[0046] EEC 240 executes the service provision request based on the information received through the above process (S209). When executing the service provision request, EEC 240 can obtain updated edge data configuration information (EES address information, DNN or S-NSSAI of edge data network, EES service area information, EDN service area information, etc.) from ECS 220.

[0047] Figure 3is a signal flow diagram illustrating an EEC triggering process of an EES according to an embodiment of the present disclosure.

[0048] refer to Figure 3 , the EEC 340 identifies whether the UE 30 supports at least one of SMS over NAS or SMS over IP. In addition, when the UE supports at least one of SMS over NAS or SMS over IP, and the EEC 340 supports a device trigger or an application trigger operation (for example, when the EEC can perform decoding on a payload in the SMS message and perform a process according to information indicated by the ECS in the payload), the EEC 340 can send an EEC trigger service request to the EES 310 (S300a).

[0049] Here, the EEC trigger service request transmission message may include at least one of information such as an EEC trigger request indication, a trigger service description (service provision, EAS discovery, EEC registration, application context relocation request), a trigger service period, a trigger service area, a port ID, or an EEC ID. In addition, the trigger service description may include information about a process that should be triggered or a service that should be called in the EEC 340, or may include EES providing service process information (at least one process or service information of EAS discovery, EEC registration, or application context relocation), where the EEC 340 wants to receive a request for execution through the EEC trigger service. In addition, the trigger service period and the trigger service area information may include information about the time and area where the EES 310 should perform the EEC trigger.

[0050] EES 310 sends a response (S300b) about whether EES 310 can successfully support the EEC trigger service according to the request of EEC 340. For example, in the case that EES 310 can successfully support the EEC trigger service, EES 310 can generate a trigger service indication (or a trigger service subscription indication) and provide the trigger service indication to EEC 340 through the response message of S300b. EES 310 can map, store and manage the generated trigger service indication and EEC ID, UE ID, trigger service description (service provision), trigger service period, trigger service area or port ID. In addition, EEC 340 can map, store and manage the trigger service indication, EEC ID, UE ID, trigger service description (service provision), trigger service period, trigger service area or port ID received from EES 310. Here, when EEC 340 or EES 310 stops or modifies the EEC trigger service in the future, the trigger service indication and the stored information can be used. For example, the EEC 340 may request to stop the EEC triggered service while sending the triggered service indication, EEC ID, UE ID, and triggered service description to the EES 310. The EES 310, which has received the stop request from the EEC 340, may determine to stop the service with the EEC triggered service stop target EEC 340 through the triggered service indication, EEC ID, UE ID, and triggered service description included in the EEC triggered service stop request, and send information indicating whether to stop the EEC triggered service to the EEC 340. As another example, the EES 310 itself may determine to stop the EEC triggered service for a specific EEC 340. In this case, the EES 310 may notify the EEC triggered service stop while sending the EEC triggered service indication, EEC ID, EES ID, and stop target EEC triggered service description to the stopped EEC triggered service target EEC 340.

[0051] The EES 310 may detect a change in EAS profile information (EAS address information, EAS DNN or S-NSSAI, EAS service area information, EAS data network access indication, EAS service KPI information, etc.), or may determine to perform an EEC trigger when an EAS information update, application context relocation, or EEC registration is required according to the movement of the UE 30 including the EEC 340 (S301).

[0052] For example, the EES 310 identifies the EAS profile information provided by the EAS 331 through the EAS registration process between the EAS 331 and the EES 310, and may update the EAS profile information by determining to perform an EEC trigger based on the EAS profile information. In addition, as an example, in the case where it is determined that a new EAS selection and application context relocation (ACR) are required according to the movement of the UE 30 or the EAS overload, the EEC trigger may be determined by the EES 310. In addition, as an example, in the case where the EAS management system (MnS) 332 requests the EES 310 for information related to the potential service demand of the EAS 331 in order to determine whether to perform EAS termination in consideration of the EAS usage frequency or the service provision status, in order to identify the potential service request demand of the EAS 331 from the EEC 340 currently registered in the EES 310, the EES 310 may determine to perform an EEC trigger so that the EEC registration process can be performed.

[0053] The EES 310 that has determined to perform the EES trigger may request a trigger delivery service, and at the same time provide the NEF 32 with a UE identifier, GPI, AF ID, trigger reference number, application port ID, valid period, priority, trigger information (trigger service description, indication of performing service provision, or trigger payload (including EAS discovery, EEC ID, EES information (EES address and identifier), EAS identifier and address information), trigger service period, etc. as shown in the figure (S302).

[0054] The NEF 32 may select an SMS-SC 31 and an SMS service center (SMS-SC) 31 associated with a 5G core network function (eg, user data management, access and mobility management functions), and transmit the trigger received from the EES 310 to the selected SMS-SC 31 ( S303 ).

[0055] Furthermore, the NEF 32 may send a response message indicating that the trigger has been successfully delivered to the SMS-SC 31 to the EES 310 ( S304 ).

[0056] The SMS-SC 31 sends the SMS to the MT 360 of the UE 30 associated with the 5G core network (S305).

[0057] Furthermore, the SMS-SC 31 transmits message delivery report information on whether the SMS is successfully transmitted to the UE 30 to the NEF 32 ( S305 ).

[0058] NEF 32 may provide EES 310 with information on whether the trigger message has been successfully sent to UE 30 and received from SMS-SC 31. In this case, when EES 310 receives corresponding information from NEF 32, EES 310 may predict that EEC 340 will perform a procedure according to the triggered service description.

[0059] The MT 360 of the UE 30 may trigger the execution of the EDGE-1 procedure while providing the EEC 340 with the port ID, EEC ID, EES information (identifier and address information), triggered service description information, and triggered service period included in the received SMS (S308).

[0060] The EEC 340 performs an appropriate process based on the information received through the above-mentioned process ( S309 ).

[0061] For example, the EEC 340 performs a process identified based on the trigger service description information of the EES 310 identified by the EES information. As another example, in the case where the trigger service description information includes information about the EAS discovery process, the EEC 340 sends an EAS discovery request to the EES 310 based thereon. As another example, when the EAS profile information is included in the trigger service description information, the EEC 340 may use the corresponding EAS profile information as the EAS discovery filter information to send the EAS discovery request to the EES 310. In addition, as an example, in the case where the trigger service description information includes information about the application context relocation process, the EEC 340 uses the edge data network configuration information stored in the UE 30 to obtain the edge data network configuration information, or performs service provisioning in the ECS, and then uses the corresponding edge data network configuration information to perform the EAS discovery process for the identified EE 310. In addition, the EEC 340 may send an application context relocation request including the EAS information (address and identifier) ​​acquired through the EAS discovery process and information about the EES 310 (address and identifier) ​​to the EES 310 that has performed the EEC trigger, wherein the EES 310 is a target of performing the EAS discovery process.

[0062] In addition, as an example, in the case where the triggering service description information includes information about the EEC registration process, the EEC 340 may determine whether to perform the EEC registration process on the EES 310. For example, in the case where the triggering service description information includes information about the EEC registration process and information about a specific EAS, the EEC 340 may determine whether to send an EEC registration request message to the EES 310 by considering whether an application client that can request a service from the specific EAS is installed in the UE 30 or whether the installed application client requests a service.

[0063] Figure 4 is a block diagram showing the structure of a UE according to an embodiment of the present disclosure, Figure 5 is a block diagram showing the structure of a server on an edge computing system according to an embodiment of the present disclosure, Figure 6 is a block diagram showing the structure of a network function entity according to an embodiment of the present disclosure.

[0064] refer to Figure 4 , the UE according to an embodiment of the present disclosure may include a transceiver 410, a controller 420, and a storage device 430. In the present disclosure, the controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0065] The transceiver 410 may send and receive signals in association with other network entities or servers. The transceiver 410 may be executed to perform the above-referenced Figure 2 and Figure 3 The controller 420 may control the overall operation of the UE according to the embodiments proposed in the present disclosure. For example, the controller 420 may control the signal flow between each block to perform operations according to the above signal flow diagram. In addition, the controller 420 may perform the function of controlling the client operation of the EEC and the application, which may be interoperable with the EES / ECS according to the above disclosed embodiments.

[0066] The storage device 430 may store at least one of information transmitted and received by the transceiver 410 or information generated by the controller 420 .

[0067] refer to Figure 5 , a server according to an embodiment of the present disclosure may include a transceiver 510, a controller 520, and a storage device 530. In the present disclosure, a controller may be defined as a circuit, a dedicated integrated circuit, or at least one processor. The server of the present disclosure may include, for example, an EAS, an EES, or an ECS on the above-mentioned edge computing system.

[0068] The transceiver 510 may send and receive signals to and from other network entities or UEs. The controller 520 may control the overall operation of the server according to the embodiments proposed in the present disclosure. For example, the controller 520 may control the signal flow between each block to perform operations according to the above-mentioned signal flow diagram.

[0069] The storage device 530 may store at least one of information transmitted and received by the transceiver 510 or information generated by the controller 520 .

[0070] refer to Figure 6, the network entity according to an embodiment of the present disclosure may include a transceiver 610, a controller 620 and a memory 630. In the present disclosure, the controller may be defined as a circuit, a dedicated integrated circuit or at least one processor. The network entity of the present disclosure may include, for example, an NEF for interworking with a UE through a 5GC or a network function (NF) on a 5GC.

[0071] The transceiver 610 may send and receive signals to and from other network entities, servers, or UEs. The controller 620 may control the overall operation of the server according to the embodiments proposed in the present disclosure. For example, the controller 620 may control the signal flow between each block to perform operations according to the above-mentioned signal flow diagram.

[0072] The memory 630 may store at least one of information transmitted and received by the transceiver 610 or information generated by the controller 620 .

[0073] In the detailed description of the present disclosure, specific embodiments have been described, but 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 described later, but also by the equivalents of the scope of the claims.

[0074] In the above specific embodiments of the present disclosure, the components included in the present disclosure have been expressed in the singular or plural, depending on the specific embodiment presented. However, for ease of description, singular or plural expression is appropriately selected for the presented situation, and the present disclosure is not limited to singular or plural components, and even if a component is expressed in the plural, it can also be composed of the singular, or even if a component is expressed in the singular, it can also be composed of the plural.

[0075] The embodiments disclosed in the above-described specification and the accompanying drawings are merely specific examples for easily describing the contents of the present disclosure and helping to understand them, and they are not intended to limit the scope of the present disclosure. Therefore, in addition to the embodiments disclosed herein, all changes or modifications derived based on the technical ideas of the present disclosure should be interpreted as being included within the scope of the present disclosure.

[0076] According to an embodiment of the present disclosure, continuously updated edge computing service information may be provided to the EEC in the terminal without continuously maintaining the connection status between the EEC and the ECS or EES.

[0077] Furthermore, according to an embodiment of the present disclosure, the EEC may appropriately perform necessary procedures to acquire EAS information or edge data network configuration information according to trigger information received through the core network without directly communicating with the EES / ECS.

Claims

1. A method performed by a terminal in a communication system, the method comprising: An edge enabler client (EEC) of the terminal sends a request message to a server of an edge data network (EDN), wherein the request message includes an indication indicating that an EEC trigger is requested, and the server of the EDN includes an edge configuration server (ECS) or an edge enabler server (EES); receiving, based on the request message, from the server a message including information about a trigger payload; as well as executing a process based on said trigger payload selection, The trigger payload includes information indicating a process through EDGE-1 or a process through EDGE-4.

2. The method according to claim 1, in, The request message is sent based on application triggering being supported, and The message is received from the server via a Short Message Service (SMS)-Service Center (SC) (SMS-SC).

3. The method according to claim 1, in, The process over EDGE-1 includes an edge application server (EAS) discovery process, and the process over EDGE-4 includes a service provisioning process, and The trigger payload also includes information about a server associated with the selected process.

4. The method according to claim 3, in, The information about the server associated with the selected process includes an identifier and an address of the server associated with the selected process, and Wherein, in the case that the selected process is an EAS discovery process, the information about the server associated with the selected process includes an identifier and an address of the EES.

5. A method performed by a server of an edge data network (EDN) in a communication system, the method comprising: receiving a request message from a terminal, the request message including an indication that an edge enabler client (EEC) trigger is requested; as well as sending, based on the request message, a message including information about a trigger payload to the terminal, the trigger payload including information indicating a procedure through EDGE-1 or a procedure through EDGE-4, Wherein, the server comprises an edge configuration server (ECS) or an edge enabler server (EES), and Wherein, the process based on the trigger payload selection is performed with the ECS or the EES.

6. The method according to claim 5, in, The message is sent based on a trigger delivery request message sent from the server to a network opening function (NEF) based on the indication, The trigger delivery request message further includes at least one of a general public subscription identifier (GPSI), an application function (AF) identifier (ID), a trigger reference number, or an application port ID. The message is sent from the NEF to the terminal via a Short Message Service (SMS)-Service Center (SC) (SMS-SC).

7. The method according to claim 5, in, The process over EDGE-1 includes an edge application server (EAS) discovery process, and the process over EDGE-4 includes a service provisioning process, and The trigger payload also includes information about a server associated with the selected process.

8. The method according to claim 7, in, The information about the server associated with the selected process includes an identifier and an address of the server associated with the selected process, and Wherein, in the case that the selected process is an EAS discovery process, the information about the server associated with the selected process includes an identifier and an address of the EES.

9. A terminal in a communication system, the terminal comprising: Transceiver; and The controller, including the edge enabler client (EEC), is configured to: controlling the transceiver to send a request message to a server of an edge data network (EDN), the request message including an indication indicating that an EEC trigger is requested, the server of the EDN including an edge configuration server (ECS) or an edge enabler server (EES), controlling the transceiver to receive a message including information about a trigger payload from the server based on the request message, and executing a process based on said trigger payload selection, The trigger payload includes information indicating a process through EDGE-1 or a process through EDGE-4.

10. The terminal according to claim 9, in, The controller is further configured to control the transceiver to send the request message to the server based on application trigger being supported, and The message is received from the server via a Short Message Service (SMS)-Service Center (SC) (SMS-SC).

11. The terminal according to claim 9, in, The process over EDGE-1 includes an edge application server (EAS) discovery process, and the process over EDGE-4 includes a service provisioning process, and The trigger payload also includes information about a server associated with the selected process.

12. The terminal according to claim 11, in, The information about the server associated with the selected process includes an identifier and an address of the server associated with the selected process, and Wherein, in the case that the selected process is an EAS discovery process, the information about the server associated with the selected process includes an identifier and an address of the EES.

13. A server of an edge data network (EDN) in a communication system, the server comprising: Transceiver; and The controller is configured as: controlling the transceiver to receive a request message from a terminal, the request message including an indication indicating that an edge enabler client (EEC) trigger is requested, and Based on the request message, controlling the transceiver to send a message including information about a trigger payload to the terminal, the trigger payload including information indicating a process through EDGE-1 or a process through EDGE-4, Wherein, the server of the EDN includes an edge configuration server (ECS) or an edge enabler server (EES), and Wherein, the process of payload selection based on the trigger is performed with the ECS or the ESS.

14. The server according to claim 13, in, The controller is further configured to send a trigger delivery request message to a network open function (NEF) based on the indication, wherein the message is sent based on the trigger delivery request message, The trigger delivery request message further includes at least one of a general public subscription identifier (GPSI), an application function (AF) identifier (ID), a trigger reference number, or an application port ID. The message is sent from the NEF to the terminal via a Short Message Service (SMS)-Service Center (SC) (SMS-SC).

15. The server according to claim 13, in, The process over EDGE-1 includes an edge application server (EAS) discovery process, and the process over EDGE-4 includes a service provisioning process, wherein the trigger payload also includes information about a server associated with the selected process, wherein the information about the server associated with the selected process includes an identifier and an address of the server associated with the selected process, and Wherein, in the case that the selected process is an EAS discovery process, the information about the server associated with the selected process includes an identifier and an address of the EES.

Images