Edge computing service support method considering application server information

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. An embodiment of the present invention provides a method performed by a session management function (SMF) in a wireless communication system. The method may comprise the steps of: receiving edge application server (EAS) load information from a network exposure function (NEF); transmitting the EAS load information to an edge application server discovery function (EASDF); receiving a domain name system (DNS) notification including a plurality of EAS IP addresses from the EASDF; determining the priorities of the plurality of EAS IP addresses on the basis of the EAS load information; and transmitting, to the EASDF, priority information on the plurality of EAS IP addresses.

Description

Method for supporting edge computing services considering application server information

[0001] The present invention relates to wireless communication systems, and more specifically, to a method for discovering and selecting edge computing services in mobile communication systems. Specifically, the present invention proposes a method for considering edge application-related information when processing DNS messages to obtain edge application server address information.

[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] In existing mobile core networks, edge application server discovery and selection have been based on the Domain Name System (DNS). This DNS-based method of edge application server discovery and selection considers only the terminal location and the transmission distance between the data center hosting the edge application server. This approach presents a problem: if the load on the edge application server is excessive, the selection of an edge application server that cannot seamlessly provide edge computing services can be problematic if only the terminal location and transmission distance from the data center are considered.

[0009] According to one embodiment of the present invention, a method performed by a session management function (SMF) in a wireless communication system may be disclosed, the method including: receiving edge application server (EAS) load information from a network exposure function (NEF); transmitting the EAS load information to an edge application server discovery function (EASDF); receiving a domain name system (DNS) notification including a plurality of EAS IP addresses from the EASDF; determining priorities for the plurality of EAS IP addresses based on the EAS load information; and transmitting priority information for the plurality of EAS IP addresses to the EASDF.

[0010] According to one embodiment, the EAS load information may be provided to the NEF from an application function (AF).

[0011] In one embodiment, the DNS notification includes a fully qualified domain name (FQDN), and multiple EAS IP addresses may be associated with applications corresponding to the FQDN.

[0012] According to one embodiment, the EAS load information may include load information for one EAS instance, load information for a group of EAS instances sharing the same EAS application ID, an EAS instance ID, an EAS ID, or an EAS IP address.

[0013] According to one embodiment, the EAS load information may include overall load information for an edge hosting environment (EHE) where EAS servers are deployed, an identifier of the EHE, or a data network access identifier (DNAI).

[0014] According to another embodiment of the present invention, a method performed by an edge application server discovery function (EASDF) in a wireless communication system may be disclosed, the method including: receiving EAS (edge ​​application server) load information from a session management function (SMF); receiving a DNS (domain name system) query from a user terminal; transmitting a DNS notification for the DNS query to the SMF; and receiving priority information for a plurality of EAS IP addresses included in the DNS notification from the SMF.

[0015] According to an embodiment of the present invention, a method for supporting edge computing services that takes edge application server load information into consideration can be disclosed.

[0016] According to an embodiment of the present invention, consideration of edge application server load information can be performed by EASDF, and EASDF can obtain load information on edge application servers from a Management system that performs management for NEF, AF or a specific EAS and select edge application servers based thereon, or can predict load of edge application servers based on data collected by itself and select edge application servers based thereon.

[0017] Figure 1 illustrates a 5G system structure that supports edge computing in the present invention.

[0018] Figures 2a and 2b are drawings for explaining various methods (Option A to D) in which EAS load information is provided to the EASDF.

[0019] FIGS. 3A and 3B are diagrams for explaining an operation in which EAS load information is provided or updated to an EASDF according to one embodiment of the present invention.

[0020] FIG. 4 is a diagram illustrating the structure of a terminal according to one embodiment of the present invention.

[0021] FIG. 5 is a diagram illustrating a network entity according to one embodiment of the present invention.

[0022] The operating principles of the present invention are described in detail with reference to the attached drawings. 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 disclosure to refer to network entities, network functions, and objects of an Edge Computing system, as well as terms used to refer to messages and identification information, 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] Figure 1 illustrates a 5G system structure that supports edge computing in the present invention.

[0026] A 5G system architecture supporting edge computing services may include various network functions (NFs), and FIG. 1 illustrates some of them, including an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a unified data management (UDM), a data network (DN) or a local part of DN that enables local access to the data network, a user plane function (UPF), a (radio) access network (R)AN, and user equipment (UE).

[0027] Each NF supports the following functions:

[0028] - AMF provides functions for access and mobility management at the UE level, and one UE can be connected to one AMF by default.

[0029] - DN refers to, for example, operator services, Internet access, or third-party services. DN transmits downlink protocol data units (PDUs) to UPF or receives PDUs transmitted from UEs from UPF. The local part of DN refers to a data network that allows local access to a portion of the DN and has a short data transmission path. In the present invention, DN may be used to refer to a DN where an edge application server supporting edge computing services is deployed.

[0030] - PCF receives information about packet flows from application servers and provides the function to determine policies such as mobility management and session management. Specifically, PCF supports functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane functions(e.g., AMF, SMF, etc.) can enforce the policy rules, and implementing a front end to access relevant subscription information for policy decision within the unified data repository (UDR).

[0031] - SMF provides session management functions, and when a UE has multiple sessions, each session can be managed by a different SMF.

[0032] - UDM stores user subscription data, policy data, etc.

[0033] - UPF transmits downlink PDUs received from DN to UE via (R)AN, and transmits uplink PDUs received from UE via (R)AN to DN. ULCL (uplink classifier) ​​refers to UPF that has the function of classifying and transmitting uplink. L-UPF (local UPF) performs the role of termination (PDU Session Anchor) of sessions transmitted to local part of DN.

[0034] - EASDF processes domain name system queries transmitted by terminals according to rules provided by SMF. For example, EASDF can perform actions such as forwarding DNS queries transmitted by terminals to a DNS server, receiving DNS responses, sending related reports to SMF, and providing DNS responses to terminals.

[0035] Edge Application Server load information (EAS load information) can be defined as follows:

[0036] EAS load information may be information indicating the load according to the available capacity of virtualization infrastructure component resources required to operate EAS for one of the following granularities: [per EAS or per EHE, per EAS Application ID, per EAS IP, per DNAI, per locality]

[0037] ● Per EAS Load information: Load information for one EAS instance or a group of EAS instances sharing the same EAS Application ID, which can be expressed in combination with one of the following information: EAS instance ID, EAS ID, EAS Application ID, or EAS IP address.

[0038] ● Per EHE (edge ​​hosting environment) Load information: Overall load information for the edge hosting environment where edge application server(s) are deployed, which can be expressed in combination with EHE identifier or DNAI (or DNAI list) information that can identify the EHE.

[0039] EAS load information can be expressed as one of (High, middle, low) information, or as information indicating the availability of detailed resources. For example, it can include information such as Available Compute resource, Available Memory resource, and Available Storage resource as Available percentage per virtualization infrastructure component resource. This information can be expressed as resource usage information for an EAS instance as “usage of assigned virtual resources currently in use for specific EAS instance(s): mean usage of virtual CPU, memory, disk).” In addition, EAS load information can include status information (registered, suspended, undiscoverable) for the EAS instance. In addition, EAS load information can include real-time or average capacity values ​​of a network interface or communication device of the EAS instance. For example, it can include transmission capacity (bps) or network bandwidth information of the EAS instance. In addition, EAS load information can include EAS resource configuration information that can indicate resource life cycle change information of a specific EAS instance.EAS resource configuration information may include information about events in which resources required to run an EAS instance are newly allocated or reclaimed, such as EAS operational or interrupted during virtual / physical resource reconfiguration.

[0040] EAS load information can be provided and stored in correspondence with a DNN or S-NSSAI. For example, if there is a data network or network slice allocated for a specific EAS provisioning service, DNN or S-NSSAI information can be included in the EAS load information, or EAS load information can be transmitted together with a DNN or S-NSSAI when provided from one network function (e.g., AF or NEF) to another network function (e.g., SMF, UDR, EASDF).

[0041] Figures 2a and 2b are drawings for explaining various methods (Option A to D) in which EAS load information is provided to the EASDF.

[0042] In the above figures 2a and 2b, operations A-1 to A-6 show the procedure for how EAS load information is set to EASDF through NEF and SMF.

[0043] A-1. When providing EAS deployment information to NEF, AF may also provide EAS load information. EAS load information may be provided as part of the edge deployment information in Table 1 below or as separate information.

[0044] ParametersDescriptionAF IDAddressing information of Application Function responsible for the DNAI in the record.[Optional]. See NOTE 1.DNNDNN for the EAS Deployment Information.[optional]S-NSSAIS-NSSAI for the EAS Deployment Information.[optional]External Group Identifier / Internal Group IdentifierGroup ID for the EAS Deployment information.[optional]. See NOTE 2.Application IDIdentifies the application for which the EAS Deployment Information corresponds to.[optional]FQDN(s)Supported FQDN(s) for application(s) deployed in the Local part of the DN.DNAI(s)DNAI(s) for the EAS Deployment information.[optional]DNS Server Informationlist of DNS server identifier (consisting of IP address and port) for each DNAI.[optional]EAS IP address range InformationIP address(es) of the EASs in the Local part of the DN or the IP address ranges (IPv4 subnetwork(s) and / or IPv6 prefix(es) of the Local part of the DN where the EAS is deployed for each DNAI.[optional]N6 traffic routing informationInformation about how to forward edge traffic in the local part of DN corresponding to DNAI.[optional]EAS Load InformationLoad information of the EAS identified or associated by the Application ID, Port ID, FQDN, DNAI, or EAS IP address.

[0045] Table 1: Description of EAS Deployment Information

[0046] When EAS load information is provided from AF, AF may be provided with at least one of the following information: AF ID, Application ID, Port ID, FQDN, IP address, EAS ID, DNAI.

[0047] A-2. NEF can perform authorization to determine whether an AF is capable of providing EAS information.

[0048] A-3. If authorization is successfully completed in Step A-2, the NEF can receive EAS load information from the AF and store the information in the UDR. For example, the NEF can transmit the EAS load information received from the AF to the UDR and store it in the form of Application data or Exposure data in the UDR.

[0049] A-4. NEF may send a response message to AF indicating that it has successfully stored EAS load information.

[0050] A-5. The NEF can provide the SMF with EAS load information received from the AF. When providing EAS load information to the SMF, the NEF can provide it as part of edge deployment information or as separate information. The EAS load information provided by the NEF to the SMF can include information provided by the AF and information obtained from the Management System. The method by which the NEF obtains EAS load information will be explained in the description of the operation of Option E.

[0051] A-6. The SMF may provide EAS load information and edge deployment information to the EASDF. If the SMF provides only EAS load information, at least some of the information contained in the edge deployment information (Table 1) may also be provided so that it can be combined with the edge deployment information previously provided to the EASDF.

[0052] The SMF may perform a subscription request procedure in advance to obtain EAS load information from the NEF. For example, the SMF may (i) send an EAS load information notification subscribe request message to the NEF. The EAS load information notification subscribe request message may include at least one of an EAS load information notification as an event ID, an EAS load reporting condition, load information granularity, a reporting period, a DNN, an S-NSSAI, EAS IP address information, an FQDN, an Application ID / EAS ID, and a DNAI. EAS load information is information that can change dynamically, and the EAS load reporting condition value can be set to enable reporting only when a specific condition is satisfied (e.g., when the EAS load is high or reaches a specific percentage value). The SMF may configure a reporting period to receive EAS load information at a specific time interval. The SMF may use the DNN or S-NSSAI to configure load information notification for a specific session or a specific application group. To receive load information notifications for a specific EAS, you can set at least one of the EAS IP address, FQDN, Application ID, and EAS ID. SMF can set a DNAI value to obtain load information for the hosting environment where the EAS is deployed.(ii) When NEF receives a subscribe request containing the above information from SMF, NEF may acquire relevant information from AF or Management System (e.g., ECSP Producer of provisioning MnS, or MANO device) and perform monitoring, and may transmit a notification message containing EAS load information to SMF according to conditions specified by SMF.

[0053] Option B (B1~B2) operation describes how the EASDF obtains EAS load information from the AF.

[0054] B-1. The AF can perform EASDF discovery and selection using at least one of the EASDF N6 IP address, S-NSSAI, DNN, EAS ID, Application ID, EAS FQDN, DNAI, and EAS IP address. For example, the AF can provide the aforementioned information to the NRF and receive EASDF information corresponding to the aforementioned information. Alternatively, the AF can provide the aforementioned information to the SMF and receive information about the EASDF (the SMF can be provided with information about the EASDF that has been selected or will be selected in the future for a specific session).

[0055] Alternatively, the AF may perform selection for the EASDF based on a subscribe request message received from the EASDF in advance. For example, the EASDF may invoke a service provided by the AF to transmit an EASDF load information notification subscribe request message to the AF. The subscribe request message may include at least one of the following: EAS load information notification as an event ID, EAS load reporting condition, load information granularity, reporting period, DNN, S-NSSAI, EAS IP address information, FQDN, Application ID / EAS ID, and DNAI. (The meaning of each element information is described above through the operation-related description in A-6.)

[0056] B-2. AF can transmit EAS load information to the EASDF specified in step B-1.

[0057] B-3. ​​The EASDF can send a message to the AF notifying that it has successfully received EAS load information. The EASDF, which has received EAS load information from the AF, can store the EAS load information and use it by mapping the EAS load information to edge deployment information or DNS handling rules provided (or to be provided) by the SMF. In addition, the EASDF can transmit the acquired EAS load information to the SMF. For example, the EASDF can provide the EAS load information to the SMF that has provided an EAS-related DNS handling rule that matches the acquired EAS load information.

[0058] Option C (C1~C3) operation shows how EASDF collects records for DNS queries on its own and estimates and uses EAS load information based on DNS query records.

[0059] C-1. EASDF can collect records of DNS queries transmitted from terminals. For example, EASDF can collect records of DNS queries received from terminals and generate statistics on the number of DNS queries received by FQDN. In addition, EASDF can generate statistics on EAS IP addresses obtained as a result of resolution of DNS queries received from terminals. EASDF can record information on the number of DNS queries generated and the number of DNS responses resulting from DNS resolution for EAS IP addresses or EAS-related FQDNs. EASDF can store and manage these DNS processing-related records as EASDF DNS handling record information.

[0060] C-2. EASDF can estimate EAS load information based on the number of DNS queries and DNS responses that occurred for a specific EAS IP address or FQDN.

[0061] C-3. EASDF can transmit to SMF the number of DNS queries and DNS responses or estimated EAS load information estimated based on the number of DNS queries and DNS responses. EASDF can provide records of DNS queries and responses or estimated EAS load information to SMF in various ways, as follows. For example, SMF can transmit to EASDF a one-time request for provision of EASDF DNS handling records or a notification subscription request. EASDF can provide EASDF DNS handling records or estimated EAS load information to SMF based on SMF's one-time request or EASDF DNS handling record notification subscription request.

[0062] Option D (D1~D2) operation describes how EASDF obtains EAS load information from the Management system.

[0063] D-1. EASDF can request EAS load information from a Management system. EASDF can select a Management system (e.g., ECS Producer of Provisioning MnS) that manages a specific EAS and receive EAS load information from the selected Management system. EASDF can request EAS load information from a Management system that can be identified by a specific EAS IP address range, EAS FQDN, or DNAI.

[0064] D-2. The management system can perform authorization for EASDF requests and provide EAS load information to EASDF.

[0065] D-3. The EASDF stores EAS load information received from the management system and can use it by mapping the EAS load information with edge deployment information or DNS handling rules provided (or to be provided) by the SMF. Furthermore, the EASDF can transmit the acquired EAS load information to the SMF. For example, the EASDF can provide the EAS load information to an SMF that has provided an EAS-related DNS handling rule that matches the acquired EAS load information.

[0066] Option E (E1~E4) operation describes how NEF obtains and manages EAS load information from the Management system, and how EASDF obtains EAS load information from NEF.

[0067] NEF can request EAS load information from a Management System. NEF can select a Management System (e.g., ECS Producer of Provisioning MnS) that manages a specific EAS and receive EAS load information from the selected Management System. NEF can request EAS load information by selecting a Management System that can be identified by a specific EAS IP address range, EAS FQDN, or DNAI.

[0068] E-1. The Management system can perform authorization for NEF requests and provide EAS load information to NEF.

[0069] E-2. The NEF can store EAS load information received from the management system, map it to edge deployment information previously acquired and stored, and store it or provide it to another NF. For example, the NEF can store EAS load information within the UDR. In this case, the NEE can map the received EAS load information to edge deployment information and store it within the UDR.

[0070] E-3. NEF can notify the Management system that it has successfully stored EAS load information.

[0071] E-4. NEF can transmit acquired EAS load information to EASDF. EASDF can perform subscription request procedure in advance to obtain EAS load information from NEF. For example, EASDF can (i) transmit EAS load information notification subscribe request message to NEF. EAS load information notification subscribe request message can include at least one of EAS load information notification as event ID, EAS load reporting condition, load information granularity, reporting period, DNN, S-NSSAI, EAS IP address information, FQDN, Application ID / EAS ID, DNAI. EAS load information is information that can change dynamically, and EAS load reporting condition value can be set as information used to set reporting only when a specific condition is satisfied (e.g., when EAS load is high or reaches a specific percentage value). EASDF can set reporting period to receive EAS load information at a specific time interval. EASDF can be configured to receive load information notifications for specific sessions or application groups using DNN or S-NSSAI. EASDF can configure at least one of the following values ​​to receive load information notifications for a specific EAS: EAS IP address, FQDN, Application ID, or EAS ID.EASDF can set a DNAI value to obtain load information about the hosting environment where EAS is deployed. (ii) When NEF receives a subscribe request containing the above information from EASDF, it can obtain related information from AF or Management System (e.g., ECSP Producer of provisioning MnS, or MANO device) and perform monitoring, and can send a notification message containing EAS load information to SMF according to the conditions specified by EASDF.

[0072] 1. After the preceding actions are completed, a DNS query from the terminal may occur. The DNS query from the terminal may be selected by the SMF and transmitted to the EASDF configured in the terminal.

[0073] 2. When the EASDF receives a DNS query from a terminal, it can send a notification to the SMF. The notification can include DNS message reporting information (EAS FQDN information and terminal IP address) and DNS message ID included in the DNS query. In addition, the EASDF can send the DNS query to a local DNS server based on the DNS handling rule received from the SMF or send it to a DNS server by adding an enhanced DNS client subnet option. When the EASDF receives a DNS response from a DNS server, it can notify the SMF of the information included in the DNS response. If the DNS response contains multiple EAS IP address information, the EASDF can select one EAS IP address information and send it to the SMF by considering the EAS load information. Alternatively, if the EAS load information is stored in the EASDF, the EASDF can provide the SMF with the EAS load information corresponding to each EAS IP address.

[0074] 3. SMF can perform UP path configuration (e.g., ULCL insertion) and EAS selection based on information received from EASDF.

[0075] When performing EAS selection, SMF can consider EAS load information obtained through the previous steps Option A to E (obtained from EASDF or obtained directly by SMF).

[0076] 4. SMF can send a DNS context update message to EASDF.

[0077] 5. EASDF can send a DNS response to the terminal according to the instructions in the DNS context update message received from SMF.

[0078] The above operation steps 1 to 5 can be performed in various ways, and the related detailed operations can be performed according to the description related to FIG. 3.

[0079] FIGS. 3A and 3B are diagrams for explaining an operation in which EAS load information is provided or updated to an EASDF according to one embodiment of the present invention.

[0080] The following steps will be described with reference to Figures 3a and 3b.

[0081] 1. The terminal can perform the PDU session creation procedure with the SMF. During the PDU session creation procedure, the SMF can check whether the terminal is authorized for EAS discovery via EASDF. If the authorization is successful, the SMF can perform the following procedure.

[0082] 2. During the PDU session creation procedure, SMF can select EASDF.

[0083] 3. The SMF can transmit the terminal IP address, UE ID, DNN, notification endpoint, and DNS message handling rule to the EASDF. The SMF can provide information indicating whether EAS load information is taken into account (e.g., an EAS load information-based discovery indication) as part of or together with the DNS message handling rule.

[0084] In addition, according to the Option 1 operation, the SMF may provide EAS load information to the EASDF together. For example, the SMF may provide EAS load information corresponding to information in the Edge deployment information. According to one embodiment of the invention, the SMF may provide the EAS load information for each EAS IP address to the EASDF. In addition, the SMF may set a weight factor or priority for each EAS IP address according to the EAS load information and provide the same to the EASDF (for example, a higher weight factor or priority may be set to an IP address of an EAS with a lower EAS load). In a subsequent operation, when there are multiple EAS IP addresses included in a DNS response, the EASDF may select the EAS with the lowest load by considering the EAS load information, weight factor, or priority provided by the SMF.

[0085] 4. EASDF may send a response message to SMF notifying that the information received from SMF through step 3 has been successfully set.

[0086] 5. The terminal can send a DNS query to EASDF.

[0087] 6. EASDF can send notifications about DNS queries to SMF according to DNS handling rules.

[0088] 7. SMF can provide the latest (updated) DNS handling rules and EAS load information to EASDF.

[0089] [Option 2] SMF verifies the FQDN included in the notification received from EASDF, and if it determines that EAS load information should be considered for the application corresponding to the FQDN, it can set a weight factor or priority for each EAS IP address according to the EAS load information and provide it to EASDF (for example, a higher weight factor or priority can be set for the IP address of an EAS with a lower EAS load). SMF can make this determination by considering Edge Deployment Information, the configured operator policy, and whether the DNS response may contain multiple EAS IP addresses for the FQDN.

[0090] In subsequent operations, if there are multiple EAS IP addresses included in the DNS response, EASDF can select the EAS with the lowest load by considering EAS load information, weight factor, or priority provided by SMF.

[0091] 8. EASDF applies the DNS handling rule received from SMF and sends the DNS query to the DNS server.

[0092] 9. EASDF receives a DNS response from the DNS server.

[0093] 10. If a DNS response contains multiple EAS IP addresses, EASDF can select a single EAS IP address based on EAS load information, or check the corresponding EAS load information for each EAS IP address. Furthermore, EASDF can assign or set a weight factor or priority based on the EAS load information corresponding to each EAS IP address.

[0094] 11. The EASDF may send a notification to the SMF regarding the DNS response. The notification may include at least one of the following combinations of information: a DNS message ID, a terminal identifier, a UE IP address, an EAS FQDN, or (i) multiple EAS IP addresses, (ii) multiple EAS IP addresses and EAS load information or a weight factor / priority assigned by the EASDF corresponding to each EAS IP address, or (iii) an EAS IP address (e.g., information selected by the EASDF considering the EAS load information).

[0095] 12. SMF can send an acknowledgment message to EASDF for the notification in the previous step.

[0096] 13. The SMF may perform UP path configuration, including ULCL / BP insertion, by considering the EAS IP address included in the notification received in step 11. (i) If the EASDF provides multiple EAS IP addresses, the SMF may select one EAS IP address by considering the EAS load information available to the SMF. (ii) If the EASDF provides multiple EAS IP addresses and the EAS load information corresponding to each EAS IP address or the weight factor / priority assigned by the EASDF, the SMF may select one EAS IP address by considering the EAS load information or the weight factor / priority provided by the EASDF. (iii) If one EAS IP address is provided, the SMF may perform UP path configuration immediately.

[0097] SMF can perform UP path configuration by considering the EAS IP address determined through the above operations (i) to (iii). For example, SMF can select and configure L-PSA (local PDU Session Anchor) UPF and ULCL / BP UPF.

[0098] 14. The SMF may send an acknowledgment to the EASDF regarding the EAS IP address selected in step 13 or the EASDF's selection of the EAS IP address. Additionally, the SMF may provide a DNS handling rule that instructs the EASDF to send a DNS response to the terminal.

[0099] 15. EASDF can provide acknowledgment for receipt of step 14 message.

[0100] 16. EASDF transmits the EAS IP address selected through the operations of the previous steps to the terminal.

[0101] According to one embodiment related to the operation of FIGS. 2 and 3, the SMF may obtain EAS load information from a network function or device such as an EASDF, an AF, a NEF, a Management system, etc., determine a DNS handling rule by considering the obtained EAS load information, and provide the determined DNS handling rule to the EASDF. In addition, the SMF may perform UPF (local PSA UPF or Uplink-classifier / Branching point UPF) and DNAI selection by considering the EAS load information obtained from a network function or device such as an EASDF, an AF, a NEF, a Management system, etc.

[0102] According to one embodiment related to the operation of FIGS. 2 and 3, the NEF can obtain EAS load information from a network function or device such as an AF or a Management system, and store and manage the obtained EAS load information in correspondence with Edge Deployment information. The NEF can associate the EAS load information and the Edge Deployment information and store them in the UDR. When the NEF receives a request for EAS load information from another network function (e.g., SMF or EASDF), the NEF can obtain and provide the EAS load information stored in the UDR, or provide the EAS load information stored in the NEF itself.

[0103] FIG. 4 is a diagram illustrating the structure of a terminal according to one embodiment of the present invention.

[0104] Referring to FIG. 4, the terminal may include a transceiver (410), a control unit (420), and a storage unit (430). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0105] The transceiver (410) can transmit and receive signals with other network entities. The transceiver (410) can receive system information from a base station, for example, and can receive a synchronization signal or a reference signal.

[0106] The control unit (420) can control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the control unit (420) can control the terminal to transmit a DNS query to the EASDF.

[0107] The storage unit (430) can store at least one of the information transmitted and received through the transmission and reception unit (410) and the information generated through the control unit (420). For example, the storage unit (430) can store a DNS query, an IP address of a terminal, a terminal identifier, and a response to a DN query.

[0108] FIG. 5 is a diagram illustrating a network entity according to one embodiment of the present invention.

[0109] The network entity illustrated in FIG. 5 may be composed of one of various types of network entities disclosed in the present invention, for example, UPF, AMF, SMF, PCF, UDM, EASDF, DN, etc.

[0110] Referring to FIG. 5, a network entity may include a transceiver (510), a control unit (520), and a storage unit (530). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0111] The transceiver (510) can transmit and receive signals with other network entities. The transceiver (510) can receive system information from, for example, a terminal, a base station, or other network entity, and can receive a synchronization signal or a reference signal.

[0112] The control unit (520) can control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the control unit (520) can control the selection of an EAS based on load information for a specific EAS according to the embodiment disclosed in the present invention.

[0113] The storage unit (530) can store at least one of the information transmitted and received through the transmission and reception unit (510) and the information generated through the control unit (520). For example, the storage unit (530) can store EAS load information, EAS deployment information, etc.

[0114] The embodiments of the present invention disclosed in this specification and drawings are merely specific examples intended to facilitate easy explanation of the technical content of the present invention and aid understanding thereof, and are not intended to limit the scope of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical concepts of the present invention are possible in addition to the embodiments disclosed herein.

Claims

1. In a method performed by SMF (session management function) in a wireless communication system, A step of receiving EAS (edge ​​application server) load information from NEF (network exposure function); A step of transmitting the above EAS load information to EASDF (edge ​​application server discovery function); A step of receiving a DNS (domain name system) notification containing multiple EAS IP addresses from the EASDF; A step of determining priorities for multiple EAS IP addresses based on the above EAS load information; and A method comprising the step of transmitting priority information for the plurality of EAS IP addresses to the EASDF.

2. In paragraph 1, A method wherein the above EAS load information is provided from an AF (application function) to the NEF.

3. In paragraph 1, The above DNS notification includes a fully qualified domain name (FQDN), and multiple EAS IP addresses are associated with applications corresponding to the FQDN.

4. In paragraph 1, A method wherein the EAS load information includes load information for one EAS instance, load information for a group of EAS instances sharing the same EAS application ID, an EAS instance ID, an EAS ID, or an EAS IP address.

5. In paragraph 1, A method wherein the EAS load information includes overall load information for an edge hosting environment (EHE) where EAS servers are deployed, an identifier of the EHE, or a data network access identifier (DNAI).

6. A method performed by EASDF (edge ​​application server discovery function) in a wireless communication system, A step of receiving EAS (edge ​​application server) load information from SMF (session management function); A step of receiving a DNS (domain name system) query from a user terminal; A step of transmitting a DNS notification for the DNS query to the above SMF; and A method comprising the step of receiving, from the SMF, priority information for a plurality of EAS IP addresses included in the DNS notification.

7. In paragraph 6, The above DNS notification includes a fully qualified domain name (FQDN), and multiple EAS IP addresses are associated with applications corresponding to the FQDN.

8. In paragraph 6, A method wherein the EAS load information includes load information for one EAS instance, load information for a group of EAS instances sharing the same EAS application ID, an EAS instance ID, an EAS ID, or an EAS IP address.

9. In the SMF (session management function) of a wireless communication system, Transmitter and receiver; and Includes a control unit, The above control unit, Receive EAS (edge ​​application server) load information from NEF (network exposure function), The above EAS load information is transmitted to EASDF (edge ​​application server discovery function). From the above EASDF, a DNS (domain name system) notification containing multiple EAS IP addresses is received, Based on the above EAS load information, priorities for multiple EAS IP addresses are determined, An SMF configured to transmit priority information for the plurality of EAS IP addresses to the EASDF.

10. In paragraph 9, The above EAS load information is provided from the AF (application function) to the NEF, SMF.

11. In paragraph 9, The above DNS notification includes a fully qualified domain name (FQDN), and multiple EAS IP addresses are associated with the SMF, which corresponds to the application corresponding to the FQDN.

12. In paragraph 9, The above EAS load information includes load information for a single EAS instance, load information for a group of EAS instances sharing the same EAS application ID, SMF including EAS instance ID, EAS ID or EAS IP address.

13. In paragraph 9, The above EAS load information includes the overall load information for the EHE (edge ​​hosting environment) where EAS servers are deployed, an SMF including the identifier or DNAI (data network access identifier) ​​of the EHE.

14. In EASDF (edge ​​application server discovery function) in wireless communication systems, Transmitter and receiver; and Includes a control unit, The above control unit, Receive EAS (edge ​​application server) load information from SMF (session management function), Receives a DNS (domain name system) query from the user terminal, To the above SMF, send a DNS notification for the above DNS query, An EASDF configured to receive priority information for multiple EAS IP addresses included in the DNS notification from the SMF.

15. In paragraph 14, The above EAS load information includes load information for a single EAS instance, load information for a group of EAS instances sharing the same EAS application ID, EASDF including EAS instance ID, EAS ID or EAS IP address.

Images