KR20230068251A - Method and apparatus for supporting an edge application server in a wireless communication system supporting edge computing - Google Patents

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate and, more specifically, to a method and an apparatus for efficiently supporting an edge application server (EAS) in a wireless communication system supporting edge computing. In accordance with an embodiment of the present invention, the method performed by an edge enabler server (EES), includes the following procedures of: receiving a registration request message including network slice information related to an edge application server (EAS), which is not set on the EES, from the EAS; selecting a terminal to be provided with the EAS information about the EAS and a method for providing the EAS information; and performing an operation based on the selected providing method such that the EAS information is provided to the terminal.

Description

Method and apparatus for supporting edge application server in wireless communication system supporting edge computing

The present disclosure relates to a method and apparatus for providing an edge computing service in a wireless communication system supporting edge computing.

5G mobile communication technology defines a wide frequency band to enable fast transmission speed and new services. It can also be implemented in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called a system after 5G communication (Beyond 5G), in order to achieve transmission speed that is 50 times faster than 5G mobile communication technology and ultra-low latency reduced to 1/10, tera Implementations in Terahertz bands (eg, such as the 3 Terahertz (3 THz) band at 95 GHz) are being considered.

In the early days of 5G mobile communication technology, there was a need for enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). Beamforming and Massive MIMO to mitigate the path loss of radio waves in the ultra-high frequency band and increase the propagation distance of radio waves, with the goal of satisfying service support and performance requirements, and efficient use of ultra-high frequency resources Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation for slot format, initial access technology to support multi-beam transmission and broadband, BWP (Band-Width Part) definition and operation, large capacity New channel coding methods such as LDPC (Low Density Parity Check) code for data transmission and Polar Code for reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services Standardization of network slicing that provides a network has been progressed.

Currently, discussions are underway to improve and enhance performance of the initial 5G mobile communication technology in consideration of the services that the 5G mobile communication technology was intended to support. NR-U (New Radio Unlicensed) for the purpose of system operation that meets 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 the terrestrial network is impossible, positioning, etc. Physical layer standardization of the technology is in progress.

In addition, IAB (Industrial Internet of Things (IIoT)), which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, to support new services through linkage and convergence with other industries (Industrial Internet of Things, IIoT) Integrated Access and Backhaul), Mobility Enhancement technology including conditional handover and Dual Active Protocol Stack (DAPS) handover, 2-step random access that simplifies the random access procedure (2-step RACH for Standardization in the field of air interface architecture/protocol for technologies such as NR) is also in progress, and 5G　baseline for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies Standardization in the field of system architecture/service is also in progress for an architecture (eg, service based architecture, service based interface), mobile edge computing (MEC) for which services are provided based on the location of a terminal, and the like.

When such a 5G mobile communication system is commercialized, the explosively increasing number of connected devices will be connected to the communication network, and accordingly, it is expected that the function and performance enhancement of the 5G mobile communication system and the integrated operation of connected devices will be required. To this end, augmented reality (AR), virtual reality (VR), mixed reality (MR), etc. to efficiently support extended reality (XR), artificial intelligence (AI) , AI) and machine learning (ML), new research on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication will be conducted.

In addition, the development of such a 5G mobile communication system is a new waveform, Full Dimensional MIMO (FD-MIMO), and Array Antenna for guaranteeing coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technologies such as large scale antennas, metamaterial-based lenses and antennas to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), RIS ( Reconfigurable Intelligent Surface) technology, as well as full duplex technology to improve frequency efficiency and system network of 6G mobile communication technology, satellite, and AI (Artificial Intelligence) are utilized from the design stage and end-to-end (End-to-End) -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI-supported functions and next-generation distributed computing technology that realizes complex services beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources could be the basis for

Meanwhile, 3GPP, which is in charge of cellular mobile communication standards, names a new core network structure as 5G core (5GC) to seek evolution from the existing 4G LTE system to the 5G system, and standardization is in progress.

5GC supports the following differentiated functions compared to the evolved packet core (EPC), which is the network core for existing 4G.

First, in 5GC, a network slice function is introduced. As a requirement of 5G, 5GC must support various types of user equipment (UE) types and services. For example, enhanced mobile broadband (eMBB), ultra reliable low latency communications (URLLC), and massive machine type communications (mMTC). Each of these terminals/services has different requirements for the core network. For example, in case of eMBB service, high data rate is required, and in case of URLLC service, high stability and low delay are required. One of the technologies proposed to satisfy these various service requirements is network slicing.

Network slicing is a method of creating multiple logical networks by virtualizing one physical network, and each network slice instance (NSI) can have different characteristics. Accordingly, each NSI can satisfy various service requirements by having a network function (NF) suitable for its characteristics. It is possible to efficiently support various 5G services by allocating an NSI suitable for the characteristics of the service requested by each terminal.

Second, 5GC can facilitate network virtualization paradigm support through separation of mobility management function and session management function. In 4G LTE, all terminals can receive services through signaling exchange with a single core device called a mobility management entity (MME) in charge of registration, authentication, mobility management, and session management functions. However, in 5G, as the number of terminals explodes and the mobility and traffic/session characteristics that must be supported according to the type of terminal are subdivided, when all functions are supported in a single device such as the MME, an extension to add entities for each required function is required. scalability is inevitably reduced. Accordingly, various functions are being developed based on a structure in which a mobility management function and a session management function are separated in order to improve scalability in terms of function/implementation complexity and signaling load of a core device in charge of a control plane.

Meanwhile, an edge computing system has recently appeared. In an edge computing system, a user equipment (UE) establishes a data connection to an edge data network (EDN) located close to its location to receive edge computing services in order to use low-latency or broadband services. there is. These edge computing services include an Edge Hosting Environment running on an Edge Enabler Server (EES) of a specific Edge Data Network or an Edge Application Server running on an Edge Computing Platform. The service can be provided through (Edge Application Server: EAS). That is, the UE may receive an edge computing service from an edge application server (EAS) closest to the region where the UE is located.

The present disclosure provides a method and apparatus for efficiently supporting an edge application server (EAS) in a wireless communication system supporting edge computing.

In addition, the present disclosure provides a method and apparatus for efficiently supporting an edge application server (EAS) using a specific network slice in a wireless communication system supporting edge computing.

In addition, the present disclosure provides a method and apparatus for supporting an edge application server (EAS) to which a network slice that is not previously set in an edge enabler server (EES) is applied in a wireless communication system supporting edge computing.

In addition, the present disclosure provides a method and apparatus for providing edge application server (EAS) information that is not previously set in an edge enabler server (EES) to a terminal in a wireless communication system supporting edge computing.

According to an embodiment of the present disclosure, a method performed in an edge enabler server (EES) in a wireless communication system supporting edge computing includes a network related to the EAS from an edge application server (EAS) that is not set in the EES. A process of receiving a registration request message including slice information, a process of selecting a terminal to which EAS information for the EAS is to be provided and a method for providing the EAS information, and the process of selecting the EAS information to be provided to the terminal. It includes a process of performing an operation based on the providing method.

In addition, according to an embodiment of the present disclosure, in a wireless communication system supporting edge computing, an edge enabler server (EES), via a transceiver, from an edge application server (EAS) that is not set in the EES through the transceiver. Receiving a registration request message including network slice information related to the EAS, selecting a terminal to which EAS information for the EAS is to be provided and a method for providing the EAS information, and providing the EAS information to the terminal and a processor configured to perform an operation based on the selected presentation method.

1 is a diagram showing an example configuration of an edge computing system supporting edge computing according to an embodiment of the present disclosure;
2 is a diagram illustrating an example of a procedure for connecting a terminal and an EAS by provisioning of a dedicated EAS in an edge computing system supporting edge computing according to an embodiment of the present disclosure;
3 is a diagram showing an example of a procedure for connecting a terminal and an EAS using URSP Influence of a dedicated EAS in an edge computing system supporting edge computing according to an embodiment of the present disclosure;
4 is a diagram showing an example of a procedure for connection between a terminal and an EAS using URSP Influence of a dedicated EAS in an edge computing system supporting edge computing according to an embodiment of the present disclosure;
5 is a diagram showing an example of a procedure for connecting a terminal and an EAS using URSP Influence of a dedicated EAS in an edge computing system supporting edge computing according to an embodiment of the present disclosure;
6 is a diagram illustrating an example of a configuration of a network entity according to an embodiment of the present disclosure.

Hereinafter, various embodiments will be described in detail with accompanying drawings. In addition, in describing the embodiments of the present disclosure, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the embodiments, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the embodiments, which may vary according to the intention or custom of a user or operator. Therefore, the definition should be made based on the contents throughout this specification.

For the same reason, in the accompanying drawings, some components are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. In each figure, the same reference number is assigned to the same or corresponding component.

Advantages and features of the present disclosure, and methods for achieving them, will become clear with reference to embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, but only the present embodiments make the present disclosure complete, and those of ordinary skill in the art to which the present disclosure belongs It is provided to fully inform you of the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numbers designate like elements throughout the specification.

At this time, it will be understood that each block of the process flow chart diagrams and combinations of the flow chart diagrams can be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). Create means to perform functions. These computer program instructions may also be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular way, such that the computer usable or computer readable memory The instructions stored in are also capable of producing an article of manufacture containing instruction means that perform the functions described in the flowchart block(s). The computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to generate computer or other programmable data processing equipment. Instructions for performing processing equipment may also provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is possible for the functions mentioned in the blocks to occur out of order. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in reverse order depending on their function.

At this time, the term '~unit' used in this embodiment means software or a hardware component such as FPGA or ASIC, and '~unit' performs certain roles. However, '~ part' is not limited to software or hardware. '~bu' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. Therefore, as an example, '~unit' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in a device or a secure multimedia card.

Hereinafter, the base station is a subject that performs resource allocation of the terminal, and eNode B (eNB), Node B, BS (Base Station), RAN (Radio Access Network), AN (Access Network), RAN node, NR NB, gNB, It may be at least one of a radio access unit, a base station controller, or a node on a network. In addition, the base station includes an Integrated Access and Backhaul-donor (IAB-donor), which is a gNB that provides network access to the terminal (s) through a network of backhaul and access links in the NR system, and the terminal (s) ) and an IAB-node, which is a radio access network (RAN) node supporting NR backhaul links to the IAB-donor or other IAB-nodes. . The terminal is wirelessly connected through the IAB-node and can transmit and receive data with an IAB-donor connected to at least one IAB-node through a backhaul link. A user equipment (UE) may include a terminal, a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. In the present disclosure, downlink (DL) is a radio transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a radio transmission path of a signal transmitted from a terminal to a base station. In addition, although embodiments of the present disclosure are described below using a system based on LTE or LTE-A as an example, embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. In addition, the embodiments of the present disclosure can be applied to other communication systems through some modification within a range that does not greatly deviate from the scope of the judgment of a person with skilled technical knowledge.

In the specific description of the embodiments of the present disclosure, New RAN (NR), a radio access network on the 5G communication standard specified by the 3rd Generation Partnership Project (3GPP), a wireless communication standardization organization, and the packet core (5G System, or 5G Core Network, or NG Core: Next Generation Core), but the main gist of the present disclosure is to provide a slight It can be applied as a modification, which will be possible with the judgment of those skilled in the art of the present disclosure.

For convenience of description below, some of the terms and names defined in the 3GPP (5G, NR, Long Term Evolution (LTE) or similar system standards) may be used. However, the present disclosure is not limited by the above terms and names, and may be equally applied to systems conforming to other standards. In addition, the present disclosure may be applied to a wireless communication system supporting network slice (or network slicing).

The 5G system supports network slices, and traffic for different network slices can be handled by different protocol data unit (PDU) sessions. The PDU session may mean an association between a data network providing a PDU connection service and a terminal. The network slice is a set of network functions (NFs) for supporting various services having different characteristics, such as broadband communication service, mission critical service such as massive IoT, V2X, etc., and logically organizes the network. It can be understood as a technique for configuring and separating different network slices. Therefore, even if a communication failure occurs in a certain network slice, communication in other network slices is not affected, so that stable communication service can be provided. In the present disclosure, "slice" may be used interchangeably as a term meaning "network slice". In such a network environment, a terminal can access multiple network slices when receiving various services. The network function (NF) may be implemented as a network element as a software instance running on hardware or a virtualized function instantiated on an appropriate platform.

A mobile communication service provider may configure the network slice and allocate network resources suitable for a specific service for each network slice or set of network slices. The network resource may mean an NF, a logical resource provided by the NF, or radio resource allocation of a base station.

For example, a mobile communication operator may configure network slice A to provide mobile broadband service, network slice B to provide vehicle communication service, and network slice C to provide IoT service. That is, in the 5G network as described above, a corresponding service can be efficiently provided to a terminal through a network slice specialized to suit the characteristics of each service. In a 5G system, a network slice may be represented by Single-Network Slice Selection Assistance Information (S-NSSAI). The S-NSSAI includes a slice/service type (SST) value and a slice differentiator (SD) value. The SST may indicate characteristics of services supported by the network slice (eg, enhanced mobile broadband (eMBB), IoT, ultra reliability low latency communication (URLC), V2X, etc.). The SD may be a value used as an additional identifier for a specific service referred to as SST.

1 is a diagram illustrating an example configuration of a wireless communication system supporting edge computing according to an embodiment of the present disclosure.

Referring to FIG. 1 , a UE 101 may include at least one application client (AC) 102 and an edge enabler client (EEC) 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. Application client (AC) 102 may be used for multi-access edge computing (MEC) services. The application client (AC) 102 is an application program that operates on a mobile operating system (OS) of the terminal 101 and may be identified by an application identifier in the core network 104 . In a communication environment providing a mobile operating system, an application client (AC) 102 may be identified using an operating system identifier (OS Identifier) and a unique application identifier (OSAppID) for each operating system. An edge enabler client (EEC) 103 provides necessary support functions for an application client (AC) 102 . For example, the edge enabler client (EEC) 103 retrieves configuration information so that application data traffic can be exchanged between the application client (AC) 102 and the edge application server (EAS) 106, and the application client ( AC) 102 , the Edge Enabler Client (EEC) 103 may discover an Edge Application Server (EAS) 106 available in the Edge Data Network (EDN) 105 .

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 more mobile communication networks. Also, although not shown, the terminal 101 may further include an edge configuration client (ECC).

The 3GPP core network 104 is illustrated 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 core network 104 may include at least one base station (node B) that communicates directly with the terminal 101 over-the-air (OTA), and further includes a core network configuration above it. can do. If the 3GPP core network 104 includes a 5GC, the 5GC includes an access and mobility management function (AMF), a session management function (SMF), and a policy control function. It may include at least one of a control function (PCF) and a user plane function (UPF). When the 3GPP core network 104 includes an EPC, the EPC includes at least one network node corresponding to 5GC (e.g., a mobility management entity (MME) that manages mobility, a policy and charging (PCRF) that manages operator policy) rule function), a serving gateway (SGW) that manages sessions, and a packet data network gateway (PGW) that handles user traffic).

An application client (AC) 102 of the terminal 101 may access an edge data network (EDN) 105 through the 3GPP core network 104 . In one embodiment, the edge data network (EDN) 105 may be implemented through a network slicing technique, and a plurality of edge data networks that may interoperate with the core network 104 may be configured in the same form. Edge Data Network (EDN) 105 may be a data network of 5GC or a packet data network of EPC network. As an example, an edge data network (EDN) 105 may include an edge hosting platform, an edge enabler server (EES) 107 and one or more edge application servers (EAS) (106). Edge Enabler Server (EES) 107 provides necessary support functions for Edge Application Server (EAS) 106 and Edge Enabler Client (EEC) 111 . For example, the Edge Enabler Server (EES) 107 provides setting information to the Edge Application Server (EAS) 106 to exchange (transmit and receive) application data traffic, and the Edge Enabler Client (EEC) Information related to the edge application server (EAS) 106 may be provided to (111). In one embodiment, the Edge Enabler Server (EES) 106 is not shown, but may include an Edge Enabler client manager, an Edge Enabler platform, and an Edge Enabler application programming interface (API) server.

The edge application server (EAS) 106 may be a virtual machine (VM) image operating in an edge hosting environment or a ^third party application server program operating in a virtualization container. there is. An edge application server (EAS) 106 may be configured to provide ultra-low latency services at a location close to the terminal 101 . An edge hosting platform may be platform software including a virtualization layer capable of executing a plurality of edge application programs. In the present disclosure, an edge hosting platform may be used as the same concept as an edge hosting environment.

In addition, the edge computing system of FIG. 1 includes an edge enabler server (EES) 107, an edge configuration server (ECS) 108, and an edge enabler client (EEC) 103, Edge computing services may be provided to the application client 102 .

The edge enabler server (EES) 107 is a server for providing edge computing services, and is used by the edge enabler client (EEC) 103 of the terminal 101 on an edge hosting environment (or edge hosting platform) Manages a list of available application programs, manages configuration information for edge application programs (eg, at least one edge application server (EAS) 106) operating on the edge hosting platform, and An application programming interface (API) for functions provided by the 3GPP core network 104 may be provided to application programs.

The Edge Enabler Server (EES) 107 negotiates/communicates with the Edge Enabler Client (EEC) 103 of the terminal 101 to establish an application client 102 of the terminal and an edge application server in the edge hosting environment ( EAS) 106 can be connected. The negotiation may proceed through a mutual operation between an edge enabler client (EEC) 103 and an edge enabler server (EES) 107, and an edge enabler client performing the same mutual operation as the negotiation ( EEC) 103 and Edge Enabler Server (EES) 107 may be referred to as an edge enabling layer.

An edge enabler client (EEC) 103 is a software module of the terminal 101 and may be a software agent having functions for providing edge computing services. The edge enabler client (EEC) 103 determines which applications can use the edge computing service, and sends the application client (AC) 102 to the edge application server (EAS) 106 that provides the edge computing service. An operation may be performed to connect network interfaces so that data can be transmitted. An operation of establishing a data connection for using the edge computing service may be performed in a 3GPP communication layer through a mobile communication function (eg, mobile terminal (MT)) of the terminal 101 . The 3GPP communication layer can perform a modem operation for using the mobile communication system, establishes a wireless connection for data communication, registers a terminal in the mobile communication system, establishes a connection for data transmission to the mobile communication system, , it can play a role in transmitting and receiving data.

Edge Enabler Client (EEC) 103 provides authentication functions to connect to Edge Computing Servers (e.g., Edge Enabler Server (EES) 107 and/or Edge Configuration Server (ECS) 108); A function of obtaining access information for an edge data network (EDN) 105 and an edge enabler server (EES) 107 in conjunction with an edge configuration server (ECS) 108, one or more edge application servers (EAS) A function of obtaining information about 106 from an edge enabler server (EES) 107, or one or more application clients in the terminal 101 based on information about one or more edge application servers (EAS) 106 It may perform at least one of the functions of routing traffic of (AC) 102 to one or more edge application servers (EAS) 106 .

Although not shown, the edge data network (EDN) 105 may include an orchestrator for an edge hosting platform (not shown). The orchestrator may be a management system that manages the management of the edge hosting platform and the life cycle of edge application programs operating on the edge hosting platform. For example, in ETSI MANO (European telecommunication standards institute management and network operation) You can perform the functions of the orchestrator you defined.

An edge configuration server that is distinct from the edge data network (EDN) 105 and can communicate with the edge enabler client (EEC) 103 of the terminal 101 through the 3GPP core network 104: ECS) 108 may be an initial access server through which the terminal 101 may receive setting information for using a mobile edge computing (MEC) service. The Edge Configuration Server (ECS) 108 knows deployment information of the Edge Enabler Server (EES) 107, and sets settings related to the Edge Data Network (EDN) 105 for using edge computing services. Configuration information may be provided to the terminal 101 .

The setting information includes EDN connection information related to the edge data network (EDN) 105 (eg, including at least one of a data network name (DNN) or S-NSSAI), an edge data network (EDN) ) 105 service area information (eg, cell list, tracking area list, PLMN (public land mobile network) ID), or connection information of the edge enabler server (EES) 107 ( For example, it may include at least one of uniform resource identifiers (URIs).

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 on an edge enabler server (EES) 107 accessible from the current location. An edge configuration server (ECS) 108 of an edge data network (EDN) 105 is running in an edge hosting environment of a specific edge enabler server (EES) 107 for an edge application server (EAS) 106 If the information is known, the UE 101 can obtain the information from the Edge Configuration Server (ECS) 107 through the Edge Enabler Client (EEC) 103.

1, EDGE-1 to EGGE-9 denote network interfaces (ie, reference points) between objects. A description of EDGE-1 to EGGE-9 may refer to 3GPP standard TS 23.558.

The edge computing system for supporting edge computing of FIG. 1 may be managed by a mobile communication service provider and a separate edge computing service provider, and thus, a plurality of separate edge computing service providers may exist in one mobile communication service provider network. The edge computing system for supporting edge computing of FIG. 1 may support such a configuration of a business operator.

The edge computing system disclosed in FIG. 1 may support a plurality of edge computing operators within a single mobile communication network, for example. In addition, the edge computing system of FIG. 1 may transmit setting information for accessing a plurality of edge computing service providers available in one mobile communication network and edge computing networks installed by operators to the terminal 101 .

In addition, the edge computing system disclosed in FIG. 1 includes an edge network service provider selected by a mobile communication operator from among a plurality of edge computing providers existing in a single mobile communication network and settings for accessing an edge computing network installed by the selected edge network service provider. Information can be delivered to the terminal 101.

In the edge computing system as shown in FIG. 1 , the EEC 103 in the terminal 101 may receive DNN and S-NSSAI information in units of EDN from the ECS 108 and access the EES 107 and the EAS 106 . In this case, when a UE Route Selection Policy (URSP) is applied to the UE 101, the URSP may be preferentially considered. The URSP includes policy information related to access network search and selection, and may be provided to the terminal 101 in the network.

When the EAS 106 is installed in the EDN 105 through instantiation, it is registered in the EES 107 and information of the EAS 106 is stored in the ECS 108. The information of the EAS 106 may be transmitted to the EEC 103 as a response to an EAS discovery request from the EEC 103 .

Meanwhile, a dedicated edge application server (EAS) to which a specific network slice is applied may not be previously set in the EES. For connection with such a dedicated EAS, the UE 101 may request EAS discovery by sending an EAS discovery request message to the EES 107. However, if information set in advance in the EES 107 does not match the EAS to which the specific network slice is applied or if information about the EAS is not registered in the EES 107, the EAS to which the specific network slice is applied A procedure of registering EDN may be required, and the corresponding EDN information is provided to the terminal 101, and the EEC 103 of the terminal 101 sends an EAS discovery request message back to the corresponding EDN based on the received EDN information. Sending procedures may be required. In addition, when the URSP is not applied to the terminal 101, there is no DNN and S-NSSAI setting method for each service. When installing a dedicated EAS using a new DNN and S-NSSAI, the EAS 106 may transmit its own DNN and S-NSSAI information and a request to apply the URSP to the UE 101 to the 5GC. In this case, a procedure for the EES 107 to transmit a request for applying the URSP to 5GC may be required. In addition, the EES 107 must be able to deliver information provided by the corresponding EAS to a terminal requesting EAS discovery as well as a terminal requiring connection with the corresponding EAS. In this case, EES 107 may need information (eg indicator) to provide URSP guidance to 5GC by identifying information provided from the EAS.

Therefore, the present disclosure proposes a method for the EES to receive information on the dedicated EAS and a method for supporting the EES for a terminal to connect to the dedicated EAS. In addition, the present disclosure proposes an EES support method for resolving information mismatch between EDN configuration information allocated to an edge data network (EDN) and information applied to an edge application server (EAS) service. In the present disclosure, as an example of a method for supporting the EES for the dedicated EAS, a UE may request a discovery request for the dedicated EAS to the EES in order to use the dedicated EAS. In addition, in the present disclosure, the dedicated EAS includes DNN / network slice information (for example, S-NSSAI) (optionally paired with PLMN ID) related to the dedicated EAS through a registration request to the EES, a URSP generation request indicator, and related to the dedicated EAS At least one of the replacement permission indicators may be provided. In addition, in the present disclosure, the EES receiving the registration request from the dedicated EAS may determine/select a terminal to which at least one of the information provided from the dedicated EAS is to be delivered. In addition, the present disclosure proposes a method for EES to transmit including EAS information for the dedicated EAS in a URSP Guidance request using 5GC API, a method for selecting a terminal for which URSP update will be performed, and a method for constructing a routing selection descriptor do. Meanwhile, in the present disclosure, the term of the dedicated EAS is for convenience of explanation, and various terms representing EAS requiring registration/setting in the EES may be used instead of the term of the dedicated EAS.

Hereinafter, various embodiments according to the present disclosure will be described.

2 is a diagram illustrating an example of a procedure for connection between a terminal and an EAS by provisioning of a dedicated EAS in a wireless communication system supporting edge computing according to an embodiment of the present disclosure. In FIG. 2, it is assumed that the EAS 106 is a dedicated EAS 106 to which a network slice not previously set in the EES 107 is applied, as in the above-described example. The embodiment of FIG. 2 will be described with reference to the configuration of FIG. 1 .

Referring to FIG. 2, in step 201, the dedicated EAS 106 may be instantiated to provide EDN service and transmit an EAS registration request message to the EES 107. The EAS registration request message transmitted by the EAS 106 may include at least one of PLMN ID, S-NSSAI, and DNN/Slice info replacement allowance indication related to the dedicated EAS 106. The instantiation means a state in which the EAS 106 is driven and a service can be provided.

- DNN/Slice info replacement allowance indication: An indicator indicating whether the use of other DNNs is permitted (or allowing use). When there is a corresponding indicator, the EES 107 can set a DNN other than the DNN provided by the existing DNN or EDN in the terminal 101 or 5GC.

In step 203, the EES 107 may receive the EAS registration request message, register the EAS 106, and (re)set EES configuration information for the corresponding EAS 106. When the setting for the EAS 106 is completed, the EES 107 may transmit an EAS response message to the EAS registration request to the EAS 106. The EAS registration response message may include Result of slice information provisioning.

- Result of slice information provisioning: Information indicating whether the DNN/Slice information requested by the EAS (106) for registration has been successfully set in the EES (107). When the DNN/Slice information requested for registration is not set in the EES 107 due to rejection or registration failure of the EES 107, the EAS 106 and the EES 107 may each perform the following operations. The setting refusal or registration failure occurs when authentication fails (for example, the device is not subscribed to the corresponding DNN, or the data is different from the group-related data, or the device subscription or group-related data is AF or specific AF or MTC (Machine type communications) ) This may occur in various situations, such as when the URSP rule cannot be dynamically modified by the provider or by the ECSP Policy. ) can be attempted.

- The EES 107 may be set to QoS guaranteed in the corresponding EES 107.

In step 204, the EES 107 may perform at least one operation of target UE selection and provisioning method selection in order to perform an operation for provisioning of the dedicated EAS 106.

Referring to the Target UE selection, the EES 107 may select the UE 101 to perform EAS information provisioning through one or more of the following operations 1) to 5).

1) When the corresponding EAS information is included in the filter information received from the EEC 103 of the terminal 101, the EAS Type may be included in the EAS Profile included in the EAS Discovery request message transmitted by the EEC 103. When the EAS Type matches the DNN/Slice type of the dedicated EAS 106, the EES 107 can select the corresponding terminal 101. In this case, as in step 202 of FIG. 2 , an EAS discovery request message including an EAS Type may be transmitted from the terminal 101 to the EES 107 .

2) EES 107 may perform Target UE selection upon receiving an EEC registration request message from UE 101. The EEC registration request message may include an EEC Context including an AC Profile. The AC Profile may include an AC Type, and when the AC Type included in the AC Profile supports the DNN/Slice type of the dedicated EAS 106, the EES 107 may select the corresponding terminal 101.

3) The EES 107 may select the terminal 101 according to ECSP (Edge Computing Service Provider) policy.

4) The EES 107 may perform target UE selection for the UE 101 within a specific area set in the EES 107.

5) A subscriber list for target UE selection may be set in the EES 107.

In the case of the operations 1) and 2) among the operations 1) to 5) for the Target UE selection, an EAS discovery request message or an EEC registration request from the terminal 101 to the EES 107 as in step 202 of FIG. Messages can be sent. In the case of operations 3) to 5), the operation of step 202 of FIG. 2 may be omitted. Accordingly, the operation of step 202 may be selectively performed.

As for the provisioning method selection, in response to the reception of the EAS discovery request message or the EEC registration request message from the terminal 101, the EES 107 may select a method for provisioning the corresponding EAS information to the terminal 101. there is.

In the embodiment of FIG. 2 , the EEC 103 may provide filter information for EAS discovery to the EES 107 through an EAS discovery request message or an EEC registration request message. The EES 107 receives the filter information, and when the EAS Type included in the received filter information matches the DNN/Slice type of the dedicated EAS 106 or the AC Type included in the received filter information is dedicated When the EAS 106 supports the DNN/Slice type, for the selected terminal 101, the EES 107 provides S-NSSAI and DNN information related to the dedicated EAS 106 (Provisioning method selection). You can select discovery response or EAS discovery notification.

at step 205. The EES 107 may provision S-NSSAI and DNN related to the dedicated EAS 106 to the selected terminal 101 in step 204 using the selected method (EAS discovery response, EAS discovery notification, etc.).

In step 206, the EES 107 may notify the EAS 106 of the provisioning result to the selected terminal 101.

3 is a diagram illustrating an example of a procedure for connection between a terminal and an EAS using URSP Influence of a dedicated EAS in a wireless communication system supporting edge computing according to an embodiment of the present disclosure. In FIG. 3, it is assumed that the EAS 106 is a dedicated EAS 106 to which a network slice not previously set in the EES 107 is applied. The embodiment of FIG. 3 will be described with reference to the configuration of FIG. 1 .

Referring to FIG. 3 , in step 301, the dedicated EAS 106 may be instantiated to provide EDN service and transmit an EAS registration request message to the EES 107. The EAS registration request message transmitted by the EAS 106 may include at least one of the PLMN ID, S-NSSAI, DNN / Slice info replacement allowance indication, and indication to request URSP guidance related to the dedicated EAS 106.

- DNN/Slice info replacement allowance indication: An indicator indicating whether the use of other DNNs is allowed. When there is a corresponding indicator, the EES 107 can set a DNN other than the existing DNN or EDN DNN in the UE 101 or 5GC.

- indication to request URSP guidance: An indicator created by EAS (106) for URSP guidance influence. Upon receiving this indicator, the EES 107 uses a network exposure function (NEF) API in 5GC to send a URSP to the terminal 101 for connection between the terminal 101 and the EAS 106 under the influence of an application function (AF). You can send a URSP guidance request to provide. The EES 107 can be selected from the EAS 106 and the EEC 103 in consideration of the PLMN IDs of the EAS 106 and the UE 101. The EES 107 may include an AF descriptor in a URSP guidance request message using information received from the EAS 106 and the EEC 103 and transmit the message to the NEF.

In addition, the EES 107 may send a URSP guidance request message to 5GC using the API of UDR or PCF (not shown) in 5GC.

In step 302, the EES 107 may receive the EAS registration request message, register the EAS 106, and (re)set EES configuration information for the corresponding EAS 106. When the setting for the EAS 106 is completed, the EES 107 may transmit an EAS response message to the EAS registration request to the EAS 106. The EAS registration response message may include Result of slice information provisioning.

- Result of slice information provisioning: Information indicating whether the DNN/Slice information requested by the EAS (106) for registration has been successfully set in the EES (107). When the DNN/Slice information requested for registration is not set in the EES 107 due to rejection or registration failure of the EES 107, the EAS 106 and the EES 107 may each perform the following operations.

- EAS 106 may attempt registration to EES 107 to ensure corresponding QoS.

- The EES 107 may be set to QoS guaranteed in the corresponding EES 107.

Meanwhile, when the EES 107 receives the DNN/Slice info replacement allowance indication through the EAS registration request message, it may configure a routing selection descriptor with EDN slice information.

In addition, when the EES 107 receives the indication to request URSP guidance from the EAS 106, it may determine whether URSP guidance can be performed for the PLMN ID identified in the 5GC in relation to the EAS 106.

When determining whether the URSP guidance operation can be performed, the EES 107 may configure a traffic descriptor and a routing selection descriptor based on information received from the EAS 106 through an EAS registration request message. The traffic descriptor is one of components included in the URSP, and is information describing a data flow for finding a matching application for rule application. The routing selection descriptor is information for determining a method of routing a matching flow, for example, a PDU session type and/or optionally a Service and Session Continuity (SSC) mode, one or more S-NSSAIs, one or more DNNs, and a preference. It may include one or more of access types, multiple access preferences, time criteria, and location criteria.

In addition, in step 303, the EES 107 receives at least one of terminal type information, a serving PLMS ID, and information indicating whether or not the terminal 101 has URSP capability from an EEC registration request message or an EAS discovery request message transmitted by the terminal 101. can do. The at least one piece of information may be used as filter information for determining URSP guidance of the EAS 106 in which the EES 107 is specified. As described in the example of FIG. 2, since the EEC registration request message or the EAS discovery request message can be selectively transmitted, the operation of step 303 can be selectively performed.

In step 304, the EES 107 may perform one or more of operations a), b), and c) below to perform an operation for provisioning of the dedicated EAS 106.

a) Target UE selection

b) Provisioning method selection

c) AF request creation for URSP guidance

Referring to the Target UE selection, the EES 107 may select the UE 101 to perform EAS information provisioning through one or more of the operations 1) to 5) in the embodiment of FIG. 2 .

As for the provisioning method selection, in response to the reception of the EAS discovery request message or the EEC registration request message from the terminal 101, the EES 107 can select a method for provisioning corresponding EAS information to the terminal 101. can That is, the EES 107 receives the filter information from the EEC 103 of the terminal 101 through an EAS discovery request message or an EEC registration request message, and the EAS Type included in the filter information is the DNN of the dedicated EAS 106. /Slice type or if the AC type included in the filter information supports the DNN/Slice type of the dedicated EAS 106 For the selected terminal 101, the EES 107 uses the dedicated EAS 106 and URSP guidance can be selected as a method of providing related S-NSSAI and DNN information (Provisioning method selection).

Specifically, in step 304, when the EES 107 receives a URSP guidance indicator from the terminal 101 through the EAS registration request message, it determines whether URSP guidance can be performed. When the EES (107) decides to perform the URSP guidance operation, the EES (107) configures a traffic descriptor and a routing selection descriptor based on the information received from the EAS (106) to generate an AF request according to the URSP guidance. can

In step 305, the EES 107 may transmit an AF request according to the URSP guidance configured in step 304 to the NEF of the 5GC 104 to request URSP guidance influence.

In step 306, the NEF of the 5GC 104 may perform a UE configuration update for URSP Provisioning to the UE 101. The NEF may transmit a UE configuration update command including a URSP to the UE. Based on the URSP, the UE can receive S-NSSAI and DNN settings for the EAS 106.

In step 307, the NEF of the 5GC 104 may provide the EES 107 with a response message for the URSP Provisioning. The response message may include a URSP provisioning approval message or a UE Configuration Update (UCU) success message.

After that, in step 308, the EES 107 may notify the EAS 106 of the URSP Provisioning result.

4 is a diagram illustrating an example of a procedure for connection between a terminal and an EAS using URSP Influence of a dedicated EAS in a wireless communication system supporting edge computing according to an embodiment of the present disclosure.

In FIG. 4, it is assumed that the EAS 106 is a dedicated EAS 106 to which a network slice not previously set in the EES 107 is applied. The embodiment of FIG. 4 will be described with reference to the configuration of FIG. 1 . In the embodiment of FIG. 4, a method of selecting a terminal 101 to which EAS information is provisioned and provisioning EAS information to the terminal 101 through signaling between the EES 107, EAS 106, and/or EEC 103 , and operations of steps 401 to 404 for constructing an AF request according to URSP guidance are the same as those of steps 301 to 304 in the above-described embodiment of FIG. 3, so detailed descriptions thereof will be omitted. FIG. In the embodiment of the EES 107, which configures the AF request according to URSP guidance, may transmit the configured AF request to the NEF of 5GC in step 405 to request URSP guidance influence.

In step 406, the NEF of the 5GC receiving the AF request indicates to the EES 107 that the UE Configuration Update failed or the update could not be performed if the URSP Provisioning was approved but the UE Configuration Update failed or could not be updated. A response message containing information may be sent.

The EES 107 receiving the response message in step 407 sends the terminal 101 selected for EAS information provisioning using the method selected in step 404 (EAS discovery response, EAS discovery notification, etc.) related to the EAS 106. S-NSSAI, DNN can be provisioned.

After that, in step 408, the EES 107 may notify the EAS 106 of the EAS information provisioning result.

According to the embodiments of the present disclosure, the instantiated EAS is registered in the EES along with S-NSSAI and DNN information related to the EAS, and directly delivers the EAS information to the UE through the EES so that the UE is connected to the EAS. A URSP update can be requested to 5GC through the EES AF request so that the terminal can be connected to the EAS through the URSP update. In addition, according to the embodiments of the present disclosure described above, the EES may perform a terminal selection operation for provisioning information of a dedicated EAS to which a specific network slice is applied to the terminal, and EEC Registration to obtain information for terminal selection. A UE may be selected by obtaining AC information supporting EAS through request and EAS discovery operations. In addition, according to the embodiments of the present disclosure described above, the EES may determine whether to perform URSP guidance for the EAS based on the filter in information received from the EEC. If there is no filter information provided by EEC, URSP guidance can be performed depending on whether ECSP policy or EEC-selected EAS declaration message is received. EES may notify EAS after receiving the EAS information provisioning result.

5 is a diagram illustrating an example of a procedure for connection between a terminal and an EAS using URSP Influence of a dedicated EAS in a wireless communication system supporting edge computing according to an embodiment of the present disclosure.

In FIG. 5, it is assumed that the EAS 106 is a dedicated EAS 106 to which a network slice not previously set in the EES 107 is applied.

In step 501, the EAS 106 includes at least one of slice information (optionally paired with PLMN ID), a URSP generation request indicator, and EAS service slice information replacement in the URSP Guidance request message using the API of the EES 107 to obtain the EES ( 107) may directly send a URSP setup request message (ie, a URSP Guidance request message).

In step 502, the EEC 103 of the UE 101 may transmit an EAS Discovery request message or an EEC registration request message including filter information to the EES 107.

In step 503, the EES 107 may select a target terminal based on information included in the request message received from the EAS 106 in step 501 and registered EEC information. In addition, a target terminal may be selected based on information included in an EAS discovery request message or an EEC registration request message received from the EEC 103.

Specifically, referring to the Target UE selection in step 503, the EES 107 may select the UE 101 to perform EAS information provisioning through one or more of the following operations 1) to 5).

1) When the corresponding EAS information is included in the filter information received from the EEC 103 of the terminal 101, the EAS Type may be included in the EAS Profile included in the EAS Discovery request message transmitted by the EEC 103. When the EAS Type matches the DNN/Slice type of the dedicated EAS 106, the EES 107 can select the corresponding terminal 101. In this case, as shown in step 502 of FIG. 5 , an EAS discovery request message including an EAS Type may be transmitted from the EEC 103 to the EES 107 .

2) EES 107 may perform Target UE selection upon receiving an EEC registration request message from EEC 103 of UE 101. The EEC registration request message may include an EEC Context including an AC Profile. The AC Profile may include an AC Type, and when the AC Type included in the AC Profile supports the DNN/Slice type of the dedicated EAS 106, the EES 107 may select the corresponding terminal 101.

3) The EES 107 may select the terminal 101 according to ECSP (Edge Computing Service Provider) policy.

4) The EES 107 may perform target UE selection for the UE 101 within a specific area set in the EES 107.

5) A subscriber list for target UE selection may be set in the EES 107.

The operation of step 502 may be selectively performed as in the embodiment of FIG. 2 .

In step 504, the EES 107 determines whether or not it is possible to perform the URSP setting and when it determines to perform the operation, it can construct an AF request and request it to the 5GC (NEF) 104.

The AF request may include a traffic descriptor and a routing selection descriptor based on information received by the EES 107 from the EAS 106.

In step 505, the 5GC (NEF) 104 may update the terminal settings for URSP Provisioning to the terminal 101. The NEF of 5GC may transmit a UE configuration update command including a URSP to the UE 101. Based on the URSP, the terminal 101 can receive S-NSSAI and DNN settings for the EAS 106.

In step 506, the NEF of the 5GC 104 may provide the EES 107 with a response message for the URSP Provisioning. The response message may include a URSP provisioning approval message or a UE Configuration Update (UCU) success message.

The NEF of 5GC 104 receiving the AF request indicates to the EES 107 that the UE Configuration Update failed or could not be updated when URSP Provisioning was approved but UE Configuration Update failed or could not be updated. A response message containing information may be sent.

After that, in step 507, the EES 107 may transmit a URSP application or update result of EAS information to the EAS 106 as a response message.

According to the embodiments of the present disclosure, the instantiated EAS is registered in the EES along with S-NSSAI and DNN information related to the EAS, and directly delivers the EAS information to the UE through the EES so that the UE is connected to the EAS. A URSP update can be requested to 5GC through the EES AF request so that the terminal can be connected to the EAS through the URSP update. In addition, according to the embodiments of the present disclosure described above, the EES may perform a terminal selection operation for provisioning information of a dedicated EAS to which a specific network slice is applied to the terminal, and EEC Registration to obtain information for terminal selection. A UE may be selected by obtaining AC information supporting EAS through request and EAS discovery operations. In addition, according to the embodiments of the present disclosure described above, the EES may determine whether to perform URSP guidance for the EAS based on the filter in information received from the EEC. If there is no filter information provided by EEC, URSP guidance can be performed depending on whether ECSP policy or EEC-selected EAS declaration message is received. EES may transmit a response message to EAS after receiving a result of applying or updating EAS information.

6 is a diagram illustrating an example of a configuration of a network entity according to an embodiment of the present disclosure. The network entity of FIG. 6 may be one of a terminal (or EEC) described in the embodiments of FIGS. 1 to 5 or a network function (NF) such as EAS, EES, or NEF.

A network entity according to an embodiment of the present disclosure is a transceiver including a processor 601, a transmitter, and a receiver for controlling overall operations of the network entity according to one or a combination of two or more of the embodiments of FIGS. 1 to 5 603 and memory 605. Of course, it is not limited to the above example, and the network entity may include more or fewer components than the configuration shown in FIG. 6 . According to an embodiment of the present disclosure, the transceiver 603 may transmit/receive a signal with at least one of other network entities or terminals. A signal transmitted/received with at least one of other network entities or terminals may include at least one of control information and data.

In FIG. 6 , the processor 601 may overall control the operation of a corresponding network entity to perform an operation according to one or a combination of two or more of the above-described embodiments of FIGS. 1 to 5 . Meanwhile, the processor 601, the transceiver 603, and the memory 605 do not necessarily have to be implemented as separate modules, but may be implemented as a single chip. The processor 501 and the transceiver 603 may be electrically connected. Also, the processor 501 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver 603 may include a communication interface for transmitting and receiving signals to and from other network entities wired/wireless.

According to an embodiment of the present disclosure, the memory 605 may store data such as a basic program for operation of a corresponding network entity, an application program, and setting information. Also, the memory 605 provides stored data according to the request of the processor 601 . The memory 605 may include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. Also, the number of memories 605 may be plural. Also, the processor 601 may perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory 605 .

In addition, the program may be performed through a communication network such as the Internet, an Intranet, a Local Area Network (LAN), a Wide LAN (WLAN), or a Storage Area Network (SAN), or a communication network composed of a combination thereof. It can be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

It should be noted that the above configuration diagram, exemplary diagram of a control/data signal transmission method, operational procedure exemplary diagram, and configuration diagram are not intended to limit the scope of the present disclosure. That is, all components, network entities, or operational steps described in the embodiments of the present disclosure should not be interpreted as being essential components for the implementation of the disclosure, and the scope in which the essence of the disclosure is not impaired even if only some components are included is included. can be implemented within In addition, each embodiment can be operated in combination with each other as needed. For example, a network entity and a terminal may be operated by combining parts of the methods proposed in the present disclosure.

In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in singular or plural numbers according to the specific embodiments presented. However, singular or plural expressions are selected appropriately for the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural are composed of the singular number or singular. Even the expressed components may be composed of a plurality.

Meanwhile, 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 and should not be defined, but should be defined by not only the scope of the claims to be described later, but also those equivalent to the scope of these claims.

Claims (10)

In a method performed in an edge enabler server (EES) in a wireless communication system supporting edge computing,
receiving a registration request message including network slice information related to the EAS from an edge application server (EAS) not configured in the EES;
selecting a terminal to which EAS information for the EAS is to be provided and a method for providing the EAS information; and
And performing an operation based on the selected providing method to provide the EAS information to the terminal.
According to claim 1,
Further comprising receiving a first message including filter information for providing the EAS information from the terminal,
If the first message is an EAS Discovery request message, the filter information includes EAS type information, and if the first message is an EEC registration request message, the filter information is DNN (data network name) or network A method of including application client (AC) type information related to slice support.
According to claim 1,
The selecting process may include selecting the terminal to which the EAS information is to be provided based on at least one of filter information received from the terminal, an Edge Computing Service Provider (ECSP) policy, area information set in the EES, and a subscriber list. How to include.
According to claim 1,
The process of performing the operation based on the selected providing method further includes providing the EAS information directly to the terminal by the EES using one of an EAS search response and an EAS search notification to the terminal.
According to claim 1,
The process of performing an operation based on the selected providing method is, when the EES receives information related to a URSP guidance request from the EAS, a process of transmitting a request message according to URSP guidance to a network exposure function (NEF) of the core network How to include more.
In an edge enabler server (EES) in a wireless communication system supporting edge computing,
transceiver; and
Through the transceiver, a registration request message including network slice information related to the EAS is received from an edge application server (EAS) that is not set in the EES, and a terminal to which EAS information for the EAS will be provided and the EAS information EES comprising a processor configured to select a method for providing, and to perform an operation based on the selected providing method so that the EAS information is provided to the terminal.
According to claim 6,
The processor is further configured to receive a first message including filter information for providing the EAS information from the terminal through the transceiver,
If the first message is an EAS Discovery request message, the filter information includes EAS type information, and if the first message is an EEC registration request message, the filter information is DNN (data network name) or network EES including application client (AC) type information related to slice support.
According to claim 6,
The processor is further configured to select the terminal to which the EAS information will be provided based on at least one of filter information received from the terminal, an Edge Computing Service Provider (ECSP) policy, area information set in the EES, and a subscriber list EES .
According to claim 6,
wherein the processor is further configured so that the EES directly provides the EAS information to the terminal using one of an EAS discovery response and an EAS discovery notification to the terminal.
According to claim 6,
The processor is further configured to transmit a request message according to URSP guidance to a network exposure function (NEF) of a core network when information related to a URSP guidance request is received from the EAS through the transceiver EES.

Images