Method and apparatus for managing information for edge computing service

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method of a local network entity for controlling edge computing in a wireless communication system according to an embodiment of the present disclosure may comprise the steps of: receiving at least one of a local edge control policy and a local session management policy from a session management function (SMF); transmitting a first message for requesting edge computing service-related information to a network exposure function (NEF); receiving, from the NEF, a second message including the edge computing service-related information; and performing edge application server discovery function (EASDF) configuration or user plane (UP) path configuration by using the edge computing service-related information.

Description

Information management method and device for edge computing services

[0001] The present invention relates to a wireless communication system, and more particularly, to a method for managing edge computing service-related information in a mobile communication system.

[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] Meanwhile, if the burden of managing edge computing sessions is concentrated on centrally located network functions, excessive signaling between the central data center and local data centers may occur.

[0009] When building a local data center to support edge computing services over a mobile network or deploying edge application servers within an existing local data center, the management of service-related information for these edge application servers can be performed within the mobile network. To manage this information within the mobile network, signaling between network functions is required to store and manage edge computing service-related information.

[0010] Some network functions that exchange information related to edge computing services may be located in local data centers, while others may be located in central data centers. Whenever new edge application servers are deployed or operational changes occur within a local data center, continuous signaling occurs between the local and central data centers, potentially placing a heavy load on local data center operations and central network functions.

[0011] A method of a local network entity controlling edge computing in a wireless communication system according to an embodiment of the present invention may include the steps of: receiving at least one of a local edge control policy and a local session management policy from a session management function (SMF); transmitting a first message requesting edge computing service-related information to a network exposure function (NEF); receiving a second message including the edge computing service-related information from the NEF; and performing configuration for an edge application server discovery function (EASDF) or a user plane (UP) path configuration using the edge computing service-related information.

[0012] A local network entity controlling edge computing in a wireless communication system according to an embodiment of the present invention includes a transceiver; and a control unit. The control unit can receive at least one of a local edge control policy and a local session management policy from a session management function (SMF). The control unit can control a first message requesting edge computing service-related information to be transmitted to a network exposure function (NEF). The control unit can receive a second message including the edge computing service-related information from the NEF. The control unit can use the edge computing service-related information to configure an edge application server discovery function (EASDF) or perform UP (user plane) path configuration.

[0013] A method and device according to an embodiment of the present invention can efficiently exchange, store, and manage edge computing service-related information between a central data center and a local data center.

[0014] FIG. 1 illustrates a 5G system architecture supporting edge computing according to one embodiment of the present invention.

[0015] FIG. 2 illustrates a method for setting edge computing service related information according to one embodiment of the present invention.

[0016] FIG. 3 illustrates a method for setting edge computing service related information according to another embodiment of the present invention.

[0017] FIG. 4 is a block diagram showing the structure of a local network entity according to an embodiment of the present invention.

[0018] FIG. 5 is a block diagram showing the structure of a network entity according to an embodiment of the present invention.

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

[0020] The terms used in this publication, such as "network entities," "network functions," and "edge computing system objects," "terms referring to messages," and "terms referring to 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.

[0021] 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.

[0022] Figure 1 illustrates a 5G system architecture supporting edge computing according to one embodiment of the present invention. Edge computing can refer to a distributed computing technology that introduces computation and data storage where needed to improve response times and conserve bandwidth. Edge computing can process, analyze, and / or store data close to its source, enabling rapid analysis and response.

[0023] A 5G system supporting edge computing services may include various network functions (NFs). Referring to FIG. 1, a 5G system supporting edge computing services may include a user equipment (UE), a (radio) access network (R)AN, an uplink classifier (ULCL), a local edge control network function (local edge control NF), an edge application server discovery function (EASDF), 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), a user plane function (UPF), a local part of the DN that enables local access to the data network, and a local UPF (L-UPF). The local part of the DN may include an edge application server (EAS).

[0024] Each NF supports the following functions:

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

[0026] - DN can mean, for example, an operator service, an Internet connection, or a third-party service. DN can transmit a downlink protocol data unit (PDU) to the UPF or receive a PDU transmitted from the UE from the UPF.

[0027] - The local part of DN can refer to a data network with a short data transmission path that allows local access to a portion of the DN. It can also be used to refer to a DN where an edge application server supporting edge computing services is deployed.

[0028] - PCF can provide the function of receiving information about packet flow from application server and determining policy such as mobility management, session management, etc. PCF can support at least one function among supporting unified policy framework for controlling network operation, providing policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce the policy rules, and implementing a front end for accessing related subscription information for policy decision in unified data repository (UDR).

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

[0030] - UDM can store user subscription data, policy data, etc. UDM can store the stored information in a separate network function or device called UDR.

[0031] - UDR stores user subscription data, policy data, application data, structured data for exposure that can be used to provide network functions externally, and can provide information stored in other network functions or devices.

[0032] - UPF can forward downlink PDUs received from DN to UE via (R)AN, and forward uplink PDUs received from UE via (R)AN to DN.

[0033] - ULCL (uplink classifier) ​​can refer to a UPF that has the ability to classify and transmit uplink.

[0034] - L-UPF (local UPF) can perform the role of termination (PDU Session Anchor) of a session transmitted as a local part of DN.

[0035] - The EASDF can process DNS (domain name system) queries sent by UEs according to rules provided by the SMF. For example, it can perform actions such as forwarding DNS queries sent by UEs to DNS servers, receiving DNS responses, sending related reports to the SMF, and providing DNS responses to the UEs.

[0036] - LECF (Local Edge Control NF) can manage sessions related to edge computing services deployed locally. LECF can apply policies related to edge computing service sessions deployed in a specific region to ULCL or L-UPF. LECF can configure DNS processing rules for EASDF that processes DNS queries related to services deployed in a specific region. Local Edge Control NF may also be named local session management function. In one embodiment, LECF can be defined as an independent NF or a local SMF.

[0037] When the management of edge computing service-related information (edge ​​application server deployment information) is performed through SMF / NEF (Network Exposure Function) / UDR, the overhead for signaling within the core network (e.g., signaling between NFs hosted in different operator data centers and / or signaling between NFs and Application Functions) that accompanies changes in the related edge deployment information may increase due to the nature of EAS hosted in a cloud environment.

[0038] FIG. 2 illustrates a method for setting edge computing service related information according to one embodiment of the present invention.

[0039] Referring to FIG. 2, a system for edge computing may include EASDF, Local edge control function (LECF), SMF, UDR, NEF (Network Exposure Function), AF, and UPF.

[0040] In step 0, the Local Edge Control Function (LECF) can receive a local edge control policy or a local session management policy from the SMF during PDU session creation. The LECF can obtain DNN (Data Network Name) and S-NSSAI (Single Network Slice Selection Assistance Information) information for the PDU session from the SMF, and can enforce the local session management policy for the PDU session specified by the DNN and S-NSSAI. The LECF can obtain EASDF or local NEF information related to the PDU session from the SMF, and can perform operations required for managing the related PDU session or processing rules for DNS messages transmitted through the related PDU session in conjunction with the EASDF or local NEF.

[0041] In step 1, the LECF may transmit a subscribe request message to the NEF to receive a report on edge computing service-related information (e.g., EAS deployment information). The subscribe request message may include at least one of a list of information to be notified from the NEF, a DNN, an S-NSSAI, a PLMN ID, a UE ID (e.g., a Generic Public Subscription Identifier (GPSI), a Subscription Permanent Identifier (SUPI), etc.), and a UE Group ID. The list of EAS deployment information to be notified from the NEF by the LECF may include at least one of the information listed in Table 2 below.

[0042] ParametersDescriptionAF IDAddressing information of Application Function responsible for the DNAI in the record.DNNDNN for the EAS Deployment Information.S-NSSAIS-NSSAI for the EAS Deployment Information.External Group Identifier / Internal Group IdentifierGroup ID for the EAS Deployment information.Application IDIdentifies the application for which the EAS Deployment Information corresponds to.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.DNS Server Informationlist of DNS server identifier (consisting of IP address and port) for each DNAI.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.N6 traffic routing informationInformation about how to forward edge traffic in the local part of DN corresponding to DNAI.

[0043] In step 2, NEF sends a subscribe response message to LECF in response to LECF's subscribe request message. The subscribe response message may contain information about the successful processing result of the subscribe.

[0044] In step 3, AF may transmit edge computing service related information (e.g., EAS Deployment Information) to NEF.

[0045] In step 4, the NEF may perform authorization on whether the AF can provide the edge computing service related information. In one embodiment, the NEF may perform authorization on whether the AF can provide EAS deployment information. If the authorization is successfully performed, the NEF may process a request for application of edge computing service related information received later within the mobile communication network according to a subscribe request received from the LECF. In addition, the NEF may specify a DNN or S-NSSAI corresponding to the AF identifier or AF service identifier information provided by the AF. The NEF may identify a corresponding PDU session or a subscribe request received from a previous LECF for the DNN / S-NSSAI directly provided by the AF, or the DNN or S-NSSAI corresponding to the AF identifier or AF service identifier information.

[0046] If there is a subscribe request received from the LECF corresponding to the edge computing service-related information received from the AF, the NEF may decide to provide the AF request information to the LECF. If there is a subscription / notification generated according to the subscribe request received from the LECF corresponding to the edge computing service-related information received from the AF, the NEF may decide to notify the LECF of the corresponding information, and during this process, the NEF may decide not to store the corresponding information in the UDR. Whether or not to store the corresponding information in the UDR may be determined according to the operator policy set in the NEF.

[0047] In step 5, NEF can provide the authorization result for the message received in step 3 to AF.

[0048] In step 6, the NEF may transmit a notification message containing edge computing service-related information received from the AF according to the operation performed in step 4 to the LECF. The notification message may include at least one of a notification identifier, a DNN, an S-NSSAI, a PLMN ID, a UE ID (such as GPSI, SUPI), a UE Group ID, and information received from the AF (EAS deployment information).

[0049] In step 7, the LECF may perform a setup operation or an UP path configuration operation for the EASDF using the edge computing service-related information received from the NEF. In one embodiment, the LECF may create / modify / delete a DNS context within the EASDF while providing the EASDF with a baseline DNS pattern or DNS handling rule based on the EAS Deployment Information received from the NEF.

[0050] The LECF may receive EASDF information from the SMF, consider EASDF information set in the LECF, or consider information obtained from the NRF to specify the EASDF to which the edge computing service-related information received from the NEF should be transmitted.

[0051] When LECF receives information that must be set in UPF, such as information required for setting up traffic routing in edge computing service-related information received from NEF or AF traffic influence information (e.g., N6 traffic routing information, DNAI information, traffic description, etc.), it can perform an operation to set the corresponding information in UPF.

[0052] When LECF receives information related to UP path configuration, such as information required for setting up traffic routing in edge computing service-related information received from NEF or AF traffic influence information (e.g., N6 traffic routing information, DNAI information, traffic description, etc.), it can perform actions to modify the UP path, such as ULCL insertion / PSA UPF insertion / PSA UPF relocation.

[0053] The LECF may perform an operation of providing or setting information received from the AF to the EASDF or UPF based on edge computing service-related information received from the NEF, and may report the provided or set edge computing service-related information to the SMF managing the PDU session to which the information applies. The report message may include at least one of LECF information, edge computing service-related information (N6 traffic routing information, DNAI information, traffic description information, EAS deployment information, etc.), EASDF information (identifier and address), UPF (identifier and address), etc.

[0054] In step 8, the LECF can perform UPF and UP path configuration operations using the edge computing service-related information obtained from the SMF or NEF through the preceding steps.

[0055] FIG. 3 illustrates a method for setting edge computing service related information according to another embodiment of the present invention.

[0056] Referring to FIG. 3, a system for edge computing may include EASDF, Local edge control function (LECF), SMF, UDR, NEF, AF, and UPF.

[0057] In step 0, the local edge control function (LECF) can receive a local edge control policy or a local session management policy from the SMF during the PDU session creation. The LECF can obtain the DNN and S-NSSAI information for the PDU session from the SMF, and enforce the local session management policy for the PDU session specified by the DNN and S-NSSAI.

[0058] In step 1, the SMF may transmit a subscribe request message to the NEF to receive a report on edge computing service-related information (e.g., EAS deployment information). The subscribe request message may include at least one of a list of information to be notified from the NEF, a DNN, an S-NSSAI, a PLMN ID, a UE ID (such as GPSI or SUPI), and a UE Group ID. The list of EAS deployment information to be notified from the NEF by the SMF may include at least one of the information listed in Table 2 below.

[0059] When the SMF decides to apply local edge control to a specific PDU session or a specific region, it can decide to send a subscribe request message to the NEF to directly receive edge computing service-related information for the session. The SMF can decide to apply local edge control by considering regional operator policies set in the SMF, policy information received from the PCF, or subscription data information received from the UDM.

[0060] ParametersDescriptionAF IDAddressing information of Application Function responsible for the DNAI in the record.DNNDNN for the EAS Deployment Information.S-NSSAIS-NSSAI for the EAS Deployment Information.External Group Identifier / Internal Group IdentifierGroup ID for the EAS Deployment information.Application IDIdentifies the application for which the EAS Deployment Information corresponds to.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.DNS Server Informationlist of DNS server identifier (consisting of IP address and port) for each DNAI.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.N6 traffic routing informationInformation about how to forward edge traffic in the local part of DN corresponding to DNAI.

[0061] In step 2, NEF sends a subscribe response message to SMF in response to SMF's subscribe request message. The subscribe response message may contain information about the successful processing result of the subscribe.

[0062] In step 3, AF can transmit edge computing service related information (e.g., EAS Deployment Information or AF traffic influence related information) to NEF.

[0063] In step 4, the NEF may perform authorization on whether the AF can provide the edge computing service related information. In one embodiment, the NEF may perform authorization on whether the AF can provide EAS deployment information. If the authorization is successfully performed, the NEF may process a request for application of edge computing service related information received later within the mobile communication network according to a subscribe request received from the SMF. In addition, the NEF may specify a DNN or S-NSSAI corresponding to the AF identifier or AF service identifier information provided by the AF. The NEF may identify a PDU session corresponding to the DNN / S-NSSAI directly provided by the AF, or a DNN or S-NSSAI corresponding to the AF identifier or AF service identifier information, or a subscribe request received from a previous LECF.

[0064] NEF may decide to provide AF request information to SMF if there is a subscribe request received from SMF corresponding to edge computing service related information received from AF. NEF may decide to notify LECF of the corresponding information if a subscription / notification is created according to a subscribe request received from SMF corresponding to edge computing service related information received from AF. In this process, NEF may decide not to store the corresponding information in UDR (Unified Data Repository). Whether or not to store the corresponding information in UDR may be determined according to the operator policy set in NEF.

[0065] In step 5, the NEF may send a message to the UDR to store the information received from the AF within the UDR based on the decision made in the previous step. The message may include the information received from the AF, the DNN / S-NSSAI, the terminal identifier, the AF identifier, etc.

[0066] In step 6, UDR can store the information received from NEF and transmit the resulting message to NEF.

[0067] In step 7, NEF can provide the processing result for the message received in step 3 to AF.

[0068] In step 8, the NEF may transmit a notification message including edge computing service related information received from the AF according to the operation performed in step 4 to the SMF. The notification message may include at least one of a notification identifier, a DNN, an S-NSSAI, a PLMN ID, a UE ID (such as GPSI, SUPI), a UE Group ID, and information received from the AF (EAS deployment information).

[0069] In step 9, the SMF may decide to provide the edge computing service related information received from the NEF to the LECF. If local edge control is applied to a PDU session to which the edge computing service related information received from the NEF should be applied, the SMF may decide to perform a local edge control policy setting or a local session management policy setting operation to apply the information to the EASDF or UPF through the LECF.

[0070] In Alt1 of Step 10, the SMF may perform a subscribe modification operation to enable the LECF to receive notifications or reports regarding edge computing service-related information received from the NEF. The SMF may send a subscribe modification request message to the NEF. The subscribe modification request message may include at least one of a subscription correlation ID and a notification target address set by the LECF information.

[0071] In Alt 2 of Step 10, or when the SMF sends a notification message to the LECF in the preceding Step 9, it may provide a subscription correlation ID to instruct the EASDF to directly modify or create a subscription for the NEF. The notification message that the SMF sends to the LECF in Step 9 may include at least one of a subscription correlation ID, an NEF address, and identifier information. The LECF may use the information received from the SMF to send a subscription modification request message to the NEF. The message that the LECF sends to the NEF may include a subscription correlation ID and a notification target address set to the LECF.

[0072] In step 11, the LECF may perform a configuration operation or an UP path configuration operation for the EASDF using the edge computing service-related information obtained from the SMF or NEF through the preceding steps. In one embodiment, the LECF may create / modify / delete a DNS context within the EASDF while providing the EASDF with a baseline DNS pattern or DNS handling rule based on the EAS Deployment Information received from the NEF.

[0073] The LECF may receive EASDF information from the SMF, consider EASDF information set in the LECF, or consider information obtained from the NRF to specify the EASDF to which the edge computing service-related information received from the SMF or NEF should be transmitted.

[0074] When LECF receives information that must be set in UPF, such as information required for setting up traffic routing in edge computing service-related information received from SMF or NEF or AF traffic influence information (e.g., N6 traffic routing information, DNAI information, traffic description, etc.), it can perform an operation to set the corresponding information in UPF.

[0075] When LECF receives information related to UP path configuration, such as information required for setting up traffic routing in edge computing service-related information received from SMF or NEF or AF traffic influence information (e.g., N6 traffic routing information, DNAI information, traffic description, etc.), it can perform actions to modify UP path, such as ULCL insertion / PSA UPF insertion / PSA UPF relocation.

[0076] The LECF may perform an operation of providing or setting information received from the AF to the EASDF or UPF based on edge computing service-related information received from the SMF or NEF, and may report the provided or set edge computing service-related information to the SMF that manages the PDU session to which the information applies. The report message may include information about LECF information, edge computing service-related information (N6 traffic routing information, DNAI information, traffic description information, EAS deployment information, etc.), EASDF information (identifier and address), UPF (identifier and address), etc.

[0077] FIG. 4 is a block diagram showing the structure of a local network entity according to an embodiment of the present invention.

[0078] The local network entity of FIG. 4 may be implemented as a Local Edge Control NF (LECF) as described above in FIGS. 1 to 3 . The local network entity may manage sessions related to locally deployed edge computing services. In one embodiment, the local network entity may be implemented as an independent NF or as a local SMF.

[0079] Referring to FIG. 4, a local network entity according to an embodiment of the present disclosure may be composed of a transceiver (410), a memory (420), and a control unit (430). Depending on the communication method of the local network entity described above, the transceiver (410), the memory (420), and the control unit (430) of the local network entity may operate.

[0080] However, the components of the local network entity are not limited to the examples described above. For example, the local network entity may include more or fewer components than the aforementioned components. Furthermore, the transceiver (410), memory (420), and control unit (430) may be implemented in a single chip form. Furthermore, the control unit (430) may include one or more processors.

[0081] The transceiver (410) is a general term for a receiver and a transmitter, and can transmit and receive signals with other network devices. The transceiver (410) may also be referred to as a transceiver. The transceiver (410) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver (410), and the components of the transceiver (410) are not limited to the RF transmitter and RF receiver.

[0082] In addition, the transmitter / receiver unit (410) can receive a signal through a wireless channel and output it to the control unit (430), and transmit the signal output from the control unit (430) through the wireless channel.

[0083] The memory (420) can store programs and data required for the operation of the local network entity. Furthermore, the memory (420) can store information or data contained in signals acquired from the local network entity. The memory (420) may be configured as a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media. Furthermore, the memory (420) may not exist separately but may be included in the control unit (430).

[0084] The control unit (430) can control a series of processes so that the local network entity can operate according to the embodiments of the present invention described above. For example, the control unit (430) can receive control signals and data signals through the transceiver unit (410) and process the received control signals and data signals. In addition, the control unit (430) can transmit the processed control signals and data signals through the transceiver unit (410). There may be a plurality of control units (430), and the control units (430) can perform component control operations of the local network entity by executing a program stored in the memory (420).

[0085] The control unit (430) can receive at least one of a local edge control policy and a local session management policy from a session management function (SMF). The control unit (430) can control to transmit a first message requesting edge computing service related information to a network exposure function (NEF). The control unit (430) can receive a second message including the edge computing service related information from the NEF. The control unit (430) can use the edge computing service related information to perform configuration for an edge application server discovery function (EASDF) or a user plane (UP) path configuration.

[0086] FIG. 5 is a block diagram showing the structure of a network entity according to an embodiment of the present invention.

[0087] The network entity of FIG. 5 can be implemented as any one of EASDF, SMF, UDR, NEF, AF, and UPF illustrated in FIGS. 1 to 3.

[0088] Referring to FIG. 5, a network entity according to an embodiment of the present disclosure may be composed of a transceiver (510), a memory (520), and a control unit (530). Depending on the communication method of the network entity described above, the transceiver (510), the memory (520), and the control unit (530) of the network device may operate.

[0089] However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more or fewer components than the aforementioned components. Furthermore, the transceiver (510), memory (520), and control unit (530) may be implemented in a single chip. Furthermore, the control unit (530) may include one or more processors.

[0090] The transceiver (510) is a general term for a receiver and a transmitter, and can transmit and receive signals with other network devices. The transceiver (510) may also be referred to as a transceiver. The transceiver (510) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver (510), and the components of the transceiver (510) are not limited to the RF transmitter and RF receiver.

[0091] In addition, the transmitter / receiver unit (510) can receive a signal through a wireless channel and output it to the control unit (530), and transmit the signal output from the control unit (530) through the wireless channel.

[0092] The memory (520) can store programs and data required for the operation of the network entity. Furthermore, the memory (520) can store information or data contained in signals acquired from the network entity. The memory (520) may be configured as a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media. Furthermore, the memory (520) may not exist separately but may be included in the control unit (530).

[0093] The control unit (530) can control a series of processes so that the network entity can operate according to the embodiments of the present invention described above. For example, the control unit (530) can receive control signals and data signals through the transceiver unit (510) and process the received control signals and data signals. In addition, the control unit (530) can transmit the processed control signals and data signals through the transceiver unit (510). There may be multiple control units (530), and the control units (530) can perform component control operations of the network entity by executing a program stored in the memory (520).

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

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

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

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

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

[0099] While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.

Claims

1. In a method of SMF (session management function) in a wireless communication system, A step of transmitting a subscription request message requesting a report on EAS (edge application server) deployment information to NEF (network exposure function); A step of receiving a subscription response message corresponding to the subscription request message from the NEF; and Comprising a step of receiving a notification message including the EAS distribution information from the NEF, A method characterized in that the above SMF is a local SMF for local offloading management.

2. In paragraph 1, the subscription request message, A method characterized by including at least one of a data network name (DNN) to be subscribed to, a single network slice selection assistance information (S-NSSAI), an application identifier (ID), and an internal group identifier (ID).

3. In the second paragraph, the subscription request message, A method characterized by further including at least one of an ID (AF ID) for an AF (application function), a fully qualified domain name (FQDN) supported for an application deployed in a local data network part, a data network access identifier (DNAI) for the EAS deployment information, DNS server information, and EAS IP address range information.

4. In paragraph 1, A method characterized by further comprising a step of managing an edge application server discovery function (EASDF) and a baseline DNS pattern based on the EAS distribution information.

5. In paragraph 4, A step of providing the above baseline DNS pattern to the EASDF; and A method characterized by further comprising the step of creating, modifying, or deleting a DNS context within the EASDF.

6. In paragraph 1, A method further comprising the step of receiving at least one of a local edge control policy and a local session management policy from another SMF.

7. In paragraph 6, A method characterized by further including a step of performing a setting for an edge application server discovery function (EASDF) or a UP (user plane) path configuration using edge computing service related information received from the NEF.

8. In paragraph 1, A step of receiving edge computing service-related information including information required for setting up traffic routing or AF traffic influence information from the NEF; and A method characterized by further comprising a step of setting the edge computing service related information to a UPF (user plane function).

9. In a SMF (session management function) device in a wireless communication system, Transmitter and receiver; and A control unit comprising: Controls the transmission of a subscription request message requesting a report on EAS (edge application server) deployment information to NEF (network exposure function), Receive a subscription response message corresponding to the subscription request message from the NEF, Receive a notification message including the above EAS distribution information from the NEF, A device characterized in that the above SMF is a local SMF for local offloading management.

10. In paragraph 9, the subscription request message, A device characterized by including at least one of a data network name (DNN), a single network slice selection assistance information (S-NSSAI), an application identifier (ID), and an internal group identifier (ID) to be subscribed to.

11. In paragraph 10, the subscription request message, A device characterized by further including at least one of an ID (AF ID) for an AF (application function), a fully qualified domain name (FQDN) supported for an application deployed in a local data network part, a data network access identifier (DNAI) for the EAS deployment information, DNS server information, and EAS IP address range information.

12. In paragraph 9, the control unit: A device characterized by managing an edge application server discovery function (EASDF) and a baseline DNS pattern based on the above EAS distribution information.

13. In paragraph 12, the control unit: Provide the above baseline DNS pattern as the EASDF, A device characterized by creating, modifying, or deleting a DNS context within the EASDF.

14. In paragraph 9, the control unit: Receive at least one of a local edge control policy and a local session management policy from another SMF, A device characterized in that it performs setting of EASDF (edge application server discovery function) or UP (user plane) path configuration using edge computing service related information received from the above NEF.

15. In paragraph 9, the control unit: Receive information related to edge computing services, including information required for setting up traffic routing or AF traffic influence information, from the NEF; A device characterized by setting the edge computing service related information to a UPF (user plane function).

Images