Method and apparatus for providing edge service in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to one embodiment of the present disclosure, a method of a first edge configuration server (ECS) entity in a wireless communication system comprises the steps of: receiving a service provisioning request message including a bundle identifier (ID) from an edge enabler client (EEC); identifying edge enabler server (EES) information corresponding to the bundle ID; and transmitting a service provisioning information retrieval request message to a second ECS if the EES information corresponding to the bundle ID is not stored in the first ECS, wherein the service provisioning information retrieval request message includes the bundle ID.

Description

Method and device for providing edge services in a wireless communication system

[0001] The present disclosure relates generally to providing edge services in wireless communication systems, and more specifically to a device and method for providing edge computing services in a wireless communication system supporting Federation.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The present disclosure provides a general device and method for providing edge computing bundle EAS service in a wireless communication system and a device and method for supporting Federation service.

[0009] According to one embodiment of the present disclosure, a method of a first edge configuration server (ECS) in a wireless communication system includes the steps of: receiving a service provisioning request message including a bundle identifier (ID) from an edge enabler client (EEC); identifying edge enabler server (EES) information corresponding to the bundle ID; and transmitting a service provisioning information retrieval request message to a second ECS when the EES information corresponding to the bundle ID is not stored in the first ECS; wherein the service provisioning information retrieval request message includes the bundle ID.

[0010] According to one embodiment of the present disclosure, in a wireless communication system, a first edge configuration server (ECS) comprises: a transceiver; and at least one processor; wherein the at least one processor is configured to receive a service provisioning request message including a bundle identifier (ID) from an edge enabler client (EEC), identify edge enabler server (EES) information corresponding to the bundle ID, and transmit a service provisioning information retrieval request message to a second ECS when the EES information corresponding to the bundle ID is not stored in the first ECS, wherein the service provisioning information retrieval request message includes the bundle ID.

[0011] According to one embodiment of the present disclosure, a method of an edge enabler client (EEC) in a wireless communication system includes the step of transmitting a service provisioning request message including a bundle identifier (ID) to a first edge configuration server (ECS). In one embodiment, the bundle ID corresponds to edge enabler server (EES) information, and the EES information corresponding to the bundle ID is used to transmit a service provisioning information retrieval request message to a second ECS, and the service provisioning information retrieval request message includes the bundle ID.

[0012] According to one embodiment of the present disclosure, in a wireless communication system, an edge enabler client (EEC) entity includes a transceiver; and at least one processor, wherein the at least one processor is configured to transmit a service provisioning request message including a bundle identifier (ID) to a first edge configuration server (ECS), wherein the bundle ID corresponds to edge enabler server (EES) information, and the EES information corresponding to the bundle ID is used to transmit a service provisioning information retrieval request message to a second ECS, and the service provisioning information retrieval request message includes the bundle ID.

[0013] The device and method according to various embodiments of the present disclosure can provide a device and method for providing edge computing services in a wireless communication system.

[0014] According to the present disclosure, quality requirements for bundled services created through service sharing and agreements between edge computing service providers are created, determined, and applied to supplement blind spots in edge data network services and improve service quality.

[0015] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0016] FIG. 1 illustrates an example of an edge computing system structure and a core network interconnection structure that support Federation according to an embodiment of the present disclosure.

[0017] FIG. 2 illustrates a method for obtaining bundle information from a federated agreement edge configuration server and requesting bundle EAS discovery in a wireless communication system according to exemplary embodiments of the present disclosure.

[0018] FIG. 3 illustrates a method for requesting QoS requirements for a bundled EAS service to a CN (core network) in a wireless communication system according to an embodiment of the present disclosure.

[0019] FIG. 4 illustrates a structural diagram of a network entity according to an embodiment of the present disclosure.

[0020] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0021] In an edge computing system, a user equipment (UE) can establish a data connection to an edge data network (EDN) located close to its location to utilize low-latency or broadband services, thereby receiving edge computing services. These edge computing services can be provided through an edge hosting environment (EVE) operated by an edge enabler server (EES) of a specific edge data network, or an edge application server (EAS) running on an edge computing platform. In other words, a UE can receive edge computing services from an edge application server (EAS) closest to its location.

[0022] The operating principles of the present invention are described in detail with reference to the attached diagram. The terms described below are defined based on their functions within the present invention. These terms may vary depending on the intent or custom of the user or operator, and therefore their definitions should be determined based on the overall content of this specification.

[0023] The terms used in this publication to refer to network entities and objects within the Edge Computing system, terms referring to messages, terms referring to identification information, and the like are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms that refer to objects with equivalent technical meanings may be used.

[0024] For convenience, the present invention uses terms and names defined in the 5G system standards, but is not limited by the terms and names, and can be equally applied to systems conforming to other standards.

[0025] The present disclosure provides a method for an application client to use a bundled service consisting of multiple edge computing applications (Bundle Edge Application Server). rd We propose a method for obtaining bundle information from a party's edge server and requesting communication resource allocation and update to a communication system to provide services optimized for the bundle.

[0026] The present disclosure provides a method for an application client to use a bundled service composed of multiple edge computing applications (Bundle Edge Application Servers) through a Federation agreement between edge computing configuration servers. rd We propose a method for obtaining bundle information from a party's edge server and requesting communication resource allocation and update to a communication system to provide services optimized for the bundle.

[0027] FIG. 1 illustrates an example of an edge computing system structure and a core network interconnection structure that support Federation according to an embodiment of the present disclosure.

[0028] Referring to FIG. 1, the UE (100) may include an Application client (103) and an Edge Enabler Client (105), the 3GPP Core Network (110) may include NEF, NEF+PCF, and / or PCF (115), and the Edge Data Network (120) may include Edge Application Server(s) (125) and an Edge Enabler Server (127).

[0029] The network and Edge Computing entities appearing in Figure 1 are described as follows.

[0030] An Edge Computing system may be composed of an Edge Enabler Server (127), an Edge Data Network Configuration Server, and an Edge Enabler Client (EEC) (105). The Edge Enabler Server (127) is placed on an Edge Hosting Environment (or Edge Computing Platform) and has information about an Edge Application Server (125) running on the Edge Hosting Environment.

[0031] The Edge Enabler Server (127) performs a function of connecting the Application Client (130) of the terminal and the Edge Application Server (125) within the Edge Hosting Environment by negotiating with the terminal. A terminal that supports the Edge Computing system may have a built-in Edge Enabler Client (105), and the negotiation may be performed through mutual connection between the Edge Enabler Client (105) and the Edge Enabler Server (127). The layer where the mutual connection between the Edge Enabler Client (105) and the Edge Enabler, such as the above negotiation, is performed may be referred to as the Edge Enabling Layer. The terminal referred to in the present invention may include not only smartphones but also IoT devices and vehicles.

[0032] The Edge Configuration Server knows the deployment information of the Edge Enabler Servers (127) and can perform a function to transmit the configuration information for using the Edge Computing service to the terminal. The configuration information may include Edge Data Network connection information (e.g., Data Network Name, S-NSSAI, etc.), Edge Data Network Service Area (e.g., Cell list, List of Tracking Area, PLMN ID), or Edge Enabler Server connection information (e.g., URI). The Edge Data Network Service Area may be an Edge Enabler Server (127) availability area set by the Edge Enabler Server (127). Based on this, the terminal can receive information on the Edge Enabler Server (127) that can be accessed at a specific location. If the Edge Data Network Configuration Server can know information on the Edge Application Server (125) running in the Edge Hosting Environment of a specific Edge Enabler Server (127), the terminal can also obtain the information through the Edge Enabler Client (105).

[0033] An Edge Application Server (125) refers to a third-party application server running within an Edge Computing system. It is a third-party application server running on the infrastructure provided by the Edge Hosting Environment, and can provide ultra-low latency services because it can provide services close to the terminal.

[0034] The terminal may include an Application Client (103), an Edge Enabler Client (105) that links the Application Client (103) with Edge Computing services, and a Mobile Terminal (MT) that connects to the mobile communication system. The Application of the terminal refers to a client application program that is provided by a third party and runs within the terminal for a specific application service. Multiple Applications may run within the terminal. At least one of these Applications may use the MEC (multi-access edge computing) service.

[0035] The Edge Enabler Client (105) within the terminal refers to a client that performs operations within the terminal required to use the Edge Computing service. The Edge Enabler Client (105) can determine which application can use the Edge Computing service and perform an operation to connect a network interface so that data of the terminal application client can be transmitted to the Edge Application Server that provides the Edge Computing service. An operation to establish a data connection for using the Edge Computing service can be performed in the 3GPP communication layer through the mobile terminal. The 3GPP communication layer refers to a layer that performs modem operations for using a mobile communication system, and performs the role of establishing a wireless connection for data communication, registering a terminal with a mobile communication system, establishing a connection for data transmission with the mobile communication system, and transmitting and receiving data.

[0036] The Edge Enabler Server (127), Edge Configuration Server (130, 135), and Edge Application Server (125) can be interconnected with a mobile communication core network (3GPP core network). For example, they can request user terminal-related information or related services to a network function (NF) constituting the core network through the Network Exposure Function (NEF). For example, servers within the edge computing system can perform specific policy creation / update / subscription requests, etc. to a policy control function (PCF) network function through the Network Exposure Function. FIG. 2 below illustrates a method for obtaining bundle information and related EES information from an Edge Configuration Server (130, 135) agreed upon as a Federation in a wireless communication system according to various embodiments of the present disclosure, and requesting bundle EAS discovery.

[0037] FIG. 2 illustrates a method for obtaining bundle information from a federated agreement edge configuration server (ECS) and requesting bundle EAS discovery in a wireless communication system according to various embodiments of the present disclosure.

[0038] In the present disclosure, the Application Client (hereinafter referred to as AC) (200) may optionally provide AC Profile and / or bundle information to the Edge Enabler Client (hereinafter referred to as EEC) (210) through an Application Programming Interface (hereinafter referred to as API) provided by the EEC (210), such as pre-registration, registration update, Edge Application Server (EAS) discovery, EEC service subscription, etc. The AC Profile may include at least one of bundle information (Bundle ID, Bundle requirement, Bundle Type, Main EAS, Required QoS for Bundle) set by the Application service provider.

[0039] The Bundle Type of an EAS providing a bundled service included in an Information Element related to a bundle can be classified into a type referring to a set of specific edge application servers (EAS) that have a data session created between an AC (200) and an EAS, or a type referring to a set of EASs that are connected to an AC (200) through a data session and consume multiple other EASs to provide services to the AC. The two sets can be distinguished in edge computing by the Bundle Type information included in the Information Element related to the bundle. In the case of a Main EAS, it can perform the role of relocating an application context for a bundled EAS when performing an edge service.

[0040] Required QoS for Bundle refers to the quality of service requirements set by the application service provider for EAS to be provided as a bundled service. The above requirements may not apply when EAS is provided as a standalone service. QoS requirements may be requested by EAS during bundled service discovery or data session connection, or EES may identify bundle usage and request AF influence from the core network to apply or update new QoS.

[0041] According to various embodiments of the present disclosure, in a wireless communication system, an edge computing service provider (hereinafter referred to as ECSP) can provision or discover edge resources configured on its server through a Federation agreement with another ECSP. In FIG. 1, ECS 1 (220) and ECS 2 (240) can exchange or store ECS Profile information including Bundle ID information with edge configuration servers of other ECSPs through an EDGE-10 reference point, and in FIG. 1, ECS 1 can obtain Bundle ID information configured in ECS 2 in advance through Federation or configure Partner ECS Profile information in advance.

[0042] At step 260, a Federation agreement can be established between ECS1 (ECSP1) (220) and ECS2 (ECSP2) (240) to share profiles. That is, ECS1 (220) can provision or discover edge resources configured on its server through a Federation agreement with ECS2 (240).

[0043] In step 261, EEC (210) may send a Service Provisioning Request message to ECS 1 (220) to find a suitable edge server. The request message may include an AC profile (AC ID, EAS ID, and / or AC profile [Bundle ID, and / or required QoS for Bundle]) received from AC, or bundle information (EAS ID, Bundle ID, and / or required QoS for Bundle) in the EAS Discovery filter.

[0044] In step 262, ECS 1 (220) can identify an EES list having a Bundle ID corresponding to the Service provisioning request message received from EEC (210). If the Bundle ID received from the terminal is in the Bundle ID corresponding to the federation information of the Partner ECS Profile stored in ECS 1 (220), or if EES information corresponding to the Bundle ID received in ECS 1 (220) cannot be found, steps 263 and 264 can be performed. If the received Bundle ID is not in the Partner ECS Profile stored in ECS 1 (220) or there is no federated Partner ECS information, steps 263 and 264 can be omitted and step 265 can be performed.

[0045] In step 263, ECS 1 (220) may send a Service provisioning information retrieval request message to Partner ECS 2 (s) (240) having a Bundle ID in an AC profile or EAS discovery filter in the message received from EEC (210). The message may include ECS address, Federation information [Federation identifier, and / or ECSP identifier], and / or AC Profile(s) [Bundle ID, and / or required QoS for Bundle] information.

[0046] At step 264, ECS 2 (240) can identify the message received from ECS 1 (220) and send EDN Configuration information [List of EESs {EASID(s) [Bundle ID and / or required QoS for Bundle]] containing EES information associated with the Bundle ID configured in ECS 2 (240) as a response message for Service provisioning information retrieval to ECS 1 (220).

[0047] In step 265, ECS 1 (220) may provide EDN configuration information including EES information (e.g., list of EESs) associated with the identified Bundle ID to EEC (210) as a Service provisioning response message. The message may include Bundle ID and / or required QoS for Bundle, etc. In one embodiment, the message may include at least one of Bundle Type and Main EAS. That is, the Service provisioning response message may include [List of EESs {EASID(s)[Bundle ID, required QoS for Bundle, Bundle Type and / or Main EAS]}].

[0048] In step 266, EEC (210) identifies EES information related to all Bundle IDs received from ECS 1 (220) and, if an EAS discovery request is received from AC (200), may send an EAS discovery request message to all EESs associated with all Bundle IDs related to the corresponding EAS, including Bundle ID and / or required QoS for Bundle information included in AC profile. If EAS discovery is triggered directly from EEC (210), an EAS discovery request message may be sent to all EESs associated with the corresponding Bundle ID. The EAS discovery request message may include Discovered EAS list (s) [EAS profile {Bundle ID, required QoS for Bundle, EAS type and / or Main EAS}] information.

[0049] In step 267, EES 1 (230) and EES 2 (250) that received the EAS discovery request may transmit an EAS discovery response to EEC (210) in response to the EAS discovery request. In one embodiment, as shown in the drawing, not only EES 1 (230) and EES 2 (250), but also at least one EES that received the EAS discovery request may transmit an EAS discovery response to EEC (210) in response to the EAS discovery request.

[0050] FIG. 3 illustrates a method for requesting QoS requirements for a bundled EAS service to a core network (CN) in a wireless communication system according to various embodiments of the present disclosure.

[0051] In step 351, the EEC (310) may transmit an EAS discovery request message to the EES (330). The message may include bundle information (Bundle ID, required QoS for Bundle, Bundle Type, and / or Main EAS) provided from ECS 1 (220) in FIG. 2 or stored in the AC Profile received from the AC (200). The EES (330) may be the Main EES according to the Bundle Type. The Main EES may refer to an EES in which the Main EAS is registered. When the Main EES receives the message, it may then perform the role of requesting the CN for QoS requirements for the bundle shown in steps 352 and 353. In one embodiment, when the Main EES does not exist, the EES that received the EAS discovery request message in step 351 may then perform the operations shown in steps 352 and 353.

[0052] In step 352, EES (330) can identify the bundle information (Bundle ID and / or required QoS for Bundle) received from EEC (310) and determine whether to request bundle QoS requirements from CN. EES (330) can perform the following actions to request QoS requirements from CN.

[0053] - You can receive an EAS Discovery request and determine the QoS for providing the bundled service by checking the Bundle ID and / or required QoS for Bundle included in the message.

[0054] - You can check the start of the bundle service, check the activated Bundle ID in EAS (320), or check the change of the activated Bundle ID.

[0055] In step 353, the EES (330) may request the CN to apply QoS requirements for the bundle through the network function (Nnef_AFsessionWithQoS) of the Network Exposing Function (NEF). The message may include Bundle ID and / or required QoS for Bundle information. If the CN operator determines that the EES (330) is trusted, the EES (330) may utilize the network function (Npcf_PolicyAuthorization) of the Policy control Function (PCF) of the CN to request the CN to apply QoS requirements for the bundle. The message may include Bundle ID and / or required QoS for Bundle information. In addition, if the EES (330) requests notification of whether bundle-related QoS is applied through the network function (QoS Monitoring) of the CN, the EES (330) may receive QoS-related notifications for the bundle.

[0056] In step 354, the EES (330) may transmit a response message to the EAS discovery request message received from the EEC (310). The message may include a bundle QoS-related notification message received from the CN and may be transmitted to the EEC (310) or AC (300).

[0057] In step 355, EAS (320) may request bundle QoS-related notifications using the available Bundle IDs. The message may include Bundle IDs that have been or will be activated in EAS (320) and / or required QoS for Bundle information. EAS (320) may receive bundle QoS-related event notifications directly or through EES (330).

[0058] In step 356, EAS (320) may receive an event notification related to bundle QoS set from CN, or may determine whether to change or maintain the previously set QoS when Bundle ID is activated or the activated bundle is changed in EAS (320).

[0059] If EAS (320) decides to update QoS requirements in step 357, it may directly request CN (e.g., NEF) to apply QoS requirements of changed bundle through network function (Nnef_AFsessionWithQoS) of CN with available Bundle ID, or may request through EES (330). The message may include Bundle ID and / or required QoS for Bundle information to provide bundle service by checking Bundle ID activated in EAS (320) or checking Bundle ID change activated.

[0060] EAS (320) can receive a response message for applying QoS requirements requested from CN directly or through EES (330). The request message can include Bundle ID and / or required QoS for Bundle information that is or will be activated in EAS (320). If EAS (320) determines that CN's operator trusts EAS (320), EES (330) can utilize network function (Npcf_PolicyAuthorization) of Policy control Function (PCF) of CN to request CN to apply QoS requirements for bundle. The message can include Bundle ID and / or required QoS for Bundle information. The request message can include Bundle ID and / or required QoS for Bundle information that is or will be activated in EAS (320).

[0061] FIG. 4 illustrates a structural diagram of a network entity according to an embodiment of the present disclosure.

[0062] The network entities illustrated in FIG. 4 may include network entities mentioned in the present disclosure, such as an application client (AC), an edge enabler client (EEC), an edge configuration server (ECS), an edge enabler server (EES), a network exposure function (NEF), and a policy control function (PCF).

[0063] A network node according to one embodiment of the present disclosure may include a processor (420) that controls the overall operation of the network node, a transceiver (400) including a transmitter and a receiver, and a memory (410). Of course, the present invention is not limited to the above example, and the network node may include more or fewer components than those illustrated in FIG. 4.

[0064] According to one embodiment of the present disclosure, the transceiver (400) can transmit and receive signals with network entities or other network nodes. The signals transmitted and received with the network entities may include control information and data. In addition, the transceiver (400) can receive signals via a wireless channel, output them to the processor (420), and transmit the signals output from the processor (420) via the wireless channel.

[0065] According to one embodiment of the present disclosure, the processor (420) can control a network node to perform any one of the operations described above. Meanwhile, the processor (420), the memory (410), and the transceiver (400) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (420) and the transceiver (400) can be electrically connected. In addition, the processor (420) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0066] According to one embodiment of the present disclosure, the processor (420) may be controlled to receive a service provisioning request message including a bundle identifier (ID) and requested QoS information for the bundle from an edge enabler client (EEC). The processor (420) may identify edge enabler server (EES) information corresponding to the bundle ID. If the EES information corresponding to the bundle ID is not stored in the first ECS, the processor (420) may be configured to transmit a service provisioning information retrieval request message to a second ECS. The service provisioning information retrieval request message includes the bundle ID and requested QoS information for the bundle.

[0067] According to one embodiment of the present disclosure, the processor (420) is configured to transmit a service provisioning information retrieval request message to the second ECS when the bundle ID matches a bundle ID of an ECS profile of the second ECS that is previously stored. The processor (420) is configured to receive, from the second ECS, a service provisioning information retrieval response message including EES information corresponding to the bundle ID, wherein the service provisioning information retrieval response message includes the bundle ID and QoS information requested for the bundle.

[0068] According to one embodiment of the present disclosure, the processor (420) is configured to transmit a service provisioning response message including EES information corresponding to the bundle ID to the EEC, wherein the service provisioning response message includes the bundle ID and requested QoS information for the bundle. In one embodiment, the EES information includes a type of EAS registered with the EES and an indicator indicating whether the EAS is a main EAS.

[0069] According to one embodiment of the present disclosure, the memory (410) can store data such as basic programs, application programs, and setting information for the operation of the network node. In particular, the memory (410) provides the stored data upon request of the processor (420). The memory (410) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (410). In addition, the processor (420) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (410).

[0070] According to one embodiment of the present disclosure, the present disclosure includes a process in which an EEC receives a Service provision response message from an ECS 1, a process in which all EESs corresponding to a Bundle ID received from the ECS 1 are identified and an EAS discovery request message is sent to each of the related EESs, a process in which the EEC identifies and determines whether to change the QoS of an existing data session due to bundle EAS activation, and a method in which, when a bundle QoS needs to be requested, an AF session with QoS creation request message is sent using an API exposed by an NEF or PCF of a 5GC core network to request the application of a QoS of a bundle required for the corresponding ID and a Bundle ID in the EAS discovery message requested by the EEC.

[0071] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0072] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0073] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0074] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0075] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0076] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method of a first ECS (edge ​​configuration server) in a wireless communication system, A step of receiving a service provisioning request message including a bundle ID (identifier) ​​from an EEC (edge ​​enabler client); A step of identifying EES (edge ​​enabler server) information corresponding to the above bundle ID; and Including a step of transmitting a service provisioning information retrieval request message to a second ECS when the EES information corresponding to the bundle ID is not stored in the first ECS; A method characterized in that the above service provisioning information retrieval request message includes the bundle ID.

2. In paragraph 1, at least one of the service provisioning request message and the service provisioning information retrieval request message, A method characterized by including quality of service (QoS) information required for a bundle.

3. In the first paragraph, the step of transmitting a service provisioning information retrieval request message; A method characterized by comprising: a step of transmitting a service provisioning information retrieval request message to the second ECS when the bundle ID matches a bundle ID of an ECS profile of the second ECS that has been previously stored; 4. In paragraph 1, A step of receiving a service provisioning information retrieval response message including EES information corresponding to the bundle ID from the second ECS; A method characterized in that the above service provisioning information retrieval response message includes the bundle ID.

5. In paragraph 1, A step of transmitting a service provisioning response message including EES information corresponding to the bundle ID to the EEC; A method characterized in that the service provisioning response message includes the bundle ID.

6. In paragraph 5, The above EES information includes at least one of the type of EAS (edge ​​application server) registered in the EES and an indicator indicating whether the EAS is a main EAS, and A method characterized in that the above EES information is used to transmit an EAS discovery request message.

7. In a method of EEC (edge ​​enabler client) in a wireless communication system, A step of transmitting a service provisioning request message including a bundle ID to a first ECS (edge ​​configuration server); The above bundle ID corresponds to EES (edge ​​enabler server) information, The EES information corresponding to the above bundle ID is used to transmit a service provisioning information retrieval request message to the second ECS, and A method characterized in that the above service provisioning information retrieval request message includes the bundle ID.

8. In paragraph 7, A step of receiving a service provisioning response message including EES information corresponding to the bundle ID from the first ECS; and A step of transmitting an EAS (edge ​​application server) discovery request message to at least one EES based on the above EES information; A method characterized in that the EES information includes at least one of a type of at least one EAS registered in the EES and an indicator indicating whether the EAS is a main EAS.

9. In the first ECS (edge ​​configuration server) in a wireless communication system, Transmitter and receiver; and comprising at least one processor; wherein the at least one processor comprises: Receive a service provisioning request message including a bundle ID from the EEC (edge ​​enabler client), Identify the EES (edge ​​enabler server) information corresponding to the above bundle ID, and If the EES information corresponding to the bundle ID is not stored in the first ECS, it is configured to transmit a service provisioning information retrieval request message to the second ECS, A first ECS, characterized in that the above service provisioning information retrieval request message includes the bundle ID.

10. In paragraph 1, at least one of the service provisioning request message and the service provisioning information retrieval request message, A first ECS characterized by including quality of service (QoS) information required for a bundle.

11. In the 9th paragraph, at least one processor, A first ECS characterized in that it is configured to transmit a service provisioning information retrieval request message to the second ECS when the bundle ID matches a bundle ID of an ECS profile of the second ECS that is previously stored.

12. In the 9th paragraph, at least one processor, configured to receive a service provisioning information retrieval response message including EES information corresponding to the bundle ID from the second ECS, and A first ECS, characterized in that the above service provisioning information retrieval response message includes the bundle ID.

13. In the 9th paragraph, the at least one processor, configured to transmit a service provisioning response message including EES information corresponding to the bundle ID to the EEC; The service provisioning response message includes the above bundle ID, and A first ECS, characterized in that the EES information includes at least one of a type of EAS registered in the EES and an indicator indicating whether the EAS is a main EAS.

14. In a wireless communication system, for an EEC (edge ​​enabler client) entity, Transmitter and receiver; and comprising at least one processor; wherein the at least one processor comprises: It is configured to send a service provisioning request message including a bundle ID to the first ECS (edge ​​configuration server), The above bundle ID corresponds to EES (edge ​​enabler server) information, The EES information corresponding to the above bundle ID is used to transmit a service provisioning information retrieval request message to the second ECS, and An EEC entity characterized in that the above service provisioning information retrieval request message includes the bundle ID.

15. In paragraph 14, at least one processor, Receive a service provisioning response message including EES information corresponding to the bundle ID from the first ECS, and configured to transmit an EAS (edge ​​application server) discovery request message to at least one EES based on the above EES information, An EEC entity, characterized in that the EES information includes at least one type of at least one EAS registered in the EES, and an indicator indicating whether the EAS is a main EAS.

Images