Traffic routing method and device in edge computing service

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure proposes a method and a device for transmitting information for supporting a local offloading service in a wireless communication system.

Description

Traffic routing method and device in edge computing services

[0001] The present invention relates to a wireless communication system, and more specifically, to a method for managing information to support traffic routing related to edge computing services 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 frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and Massive Machine-Type Communications (mMTC), technologies included beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands; support for various numerologies (such as operating multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources; initial access techniques to support multi-beam transmission and broadband; the definition and operation of Band-Width Parts (BWP); Low Density Parity Check (LDPC) codes for high-volume data transmission; new channel coding methods such as Polar Codes for the reliable transmission of control information; and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

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

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

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; as well as full-duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] Meanwhile, if the load on managing edge computing sessions is concentrated on centrally located network functions, excessive signaling may occur between the central data center and local data centers.

[0009] The embodiments disclosed in the present invention aim to provide a method and apparatus capable of effectively providing services in a mobile communication system.

[0010] When a local data center is established or an edge application server is deployed in an existing local data center to support edge computing services through a mobile communication network, the management of service-related information of said edge application server can be performed within the mobile communication network. In order for the management of service-related information of the edge application server to be performed within the mobile communication network, signaling between network functions for storing and managing edge computing service-related information is required.

[0011] Some network functions that exchange information related to edge computing services may be deployed in the local data center, while others may be deployed in the central data center. Whenever an edge application server is newly deployed or there are operational changes within the local data center, continuous signaling occurs between the local data center and the central data center, and the load may be concentrated on local data center operations and central network functions.

[0012] The technical problems to be solved by the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

[0013] A method of an I-SMF entity controlling edge computing in a wireless communication system according to an embodiment of the present invention may include: receiving at least one of a local offloading policy and traffic routing information (local session management policy) from a session management function (SMF); transmitting a message requesting information related to an edge computing service to a network exposure function (NEF); receiving a message containing the information related to the edge computing service from the NEF; and performing a user plane path configuration using the information related to the edge computing service.

[0014] The method and apparatus according to an embodiment of the present invention can provide a data path delay measurement method for selecting an efficient traffic path toward a local data center based on edge computing service-related information and traffic routing information.

[0015] FIG. 1 is a drawing illustrating the network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0016] FIG. 2 illustrates the structure of a system supporting edge computing roaming services according to embodiments of the present disclosure.

[0017] FIG. 3a is a diagram illustrating part of an offloading service support procedure that considers N6 delay requirements based on traffic routing information in an I-SMF according to one embodiment of the present disclosure.

[0018] FIG. 3b is a diagram illustrating the remaining part of an offloading service support procedure that considers N6 delay requirements based on traffic routing information in an I-SMF according to one embodiment of the present disclosure.

[0019] FIG. 4a is a diagram illustrating part of an offloading service support procedure that considers N6 delay requirements based on traffic routing information in an I-SMF according to one embodiment of the present disclosure.

[0020] FIG. 4b is a diagram illustrating the remaining part of an offloading service support procedure that considers N6 delay requirements based on traffic routing information in an I-SMF according to one embodiment of the present disclosure.

[0021] FIG. 5 is a block diagram showing an example of the configuration of a terminal (UE) according to one embodiment of the present disclosure.

[0022] FIG. 6 is a block diagram showing an example of the configuration of a network entity according to one embodiment of the present disclosure.

[0023] Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings.

[0024] In describing the present disclosure, technical details that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure are omitted. This is intended to convey the essence of the present disclosure more clearly without obscuring it by omitting unnecessary explanations. Furthermore, the terms described below are defined considering their functions within the present disclosure, and these definitions may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0025] In the following description of the present invention, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions may unnecessarily obscure the essence of the invention. Embodiments of the present invention will be described below with reference to the attached drawings.

[0026] The operating principle of the present invention will be explained in detail below with reference to the attached drawings. Furthermore, the terms described below are defined in consideration of their functions in the present invention. Since these may vary depending on the intentions or conventions of the user or operator, their definitions should be determined according to the content throughout this specification.

[0027] In describing the embodiments of this disclosure, technical details that are well known in the technical field to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0028] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0029] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. The embodiments provided are merely to make the present disclosure complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components.

[0030] Hereinafter, a base station (hereinafter BS) is an entity that performs resource allocation for terminals and may be at least one of gNode B, eNode B, Node B (or xNode B (where x is an alphabet including g and e)), a radio access unit, a base station controller, a satellite, an airborn, or a node on a network. A terminal (user equipment, hereinafter UE) may include a Mobile Station (MS), a Vehicular, a Satellite, an Airborn, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this disclosure, a Downlink (DL) refers to a radio transmission path for a signal transmitted by a base station to a terminal, and an Uplink (UL) refers to a radio transmission path for a signal transmitted by a terminal to a base station. Additionally, a Sidelink (SL) may exist, which refers to a radio transmission path for a signal transmitted by a terminal to another terminal.

[0031] In addition, while LTE, LTE-A, or 5G systems may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5G-Advance or NR-Advance or 6th generation mobile communication technology (6G) developed after 5G mobile communication technology (or new radio, NR) may be included, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0032] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0033] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0034] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0035] Terms used in the following description to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0036] For convenience of explanation below, some terms and names defined in the 3GPP (3rd generation partnership project) LTE (long term evolution) standards and / or 3GPP NR (new radio) standards may be used. However, the present disclosure is not limited by the above terms and names and may be equally applied to systems conforming to other standards.

[0037] Specific terms used in the following description are provided to aid in understanding the present disclosure, and the use of such specific terms may be modified in other forms without departing from the technical spirit of the present disclosure.

[0038] 3GPP, which is responsible for cellular mobile communication standards, has named a new core network structure "5G Core" (5GC) and is proceeding with standardization to facilitate the evolution from 4G LTE systems to 5G systems. Compared to the Evolved Packet Core (EPC), which is the network core for 4G, 5GC supports the following differentiated features.

[0039] Network Slice functionality is introduced in 5GC. As a requirement for 5G, 5GC must support various types of terminals and services (e.g., enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLC), and Massive Machine Type Communications (mMTC)). Each of these terminals / services has different requirements for the core network. For example, eMBB services may require a high data rate, while URLLC services may require high stability and low latency. Network Slice technology has been proposed to satisfy these diverse service requirements.

[0040] Network slicing refers to a method of creating multiple logical networks (e.g., network slices) by virtualizing a single physical network. An active network slice can be referred to as a network slice instance, and each network slice instance (hereinafter NSI) can have different characteristics. Mobile operators can satisfy various service requirements for terminals / services by configuring network functions (hereinafter NF) suitable for the characteristics of each NSI. For example, mobile operators can efficiently support various 5G services (e.g., eMBB, URLLC, or mMTC) by allocating an NSI that matches the characteristics of the service required by each terminal.

[0041] 5GC facilitates support for network virtualization paradigms by separating mobility management functions and session management functions. In 4G LTE, all terminals can receive services from the network through signaling exchanges with a single core entity called the Mobility Management Entity (MME), which is responsible for registration, authentication, mobility management, and session management functions. In 5G, as the number of terminals (e.g., including MTC terminals) increases explosively and the mobility and traffic / session characteristics that must be supported vary depending on the terminal type, having a single entity (e.g., MME) support all functions inevitably leads to reduced scalability, which requires adding entities for specific functions. Therefore, to improve scalability in terms of the functional / implementation complexity and signaling load of the core entity responsible for the control plane, various functions are being developed based on a structure that separates mobility management functions and session management functions.

[0042] FIG. 1 is a diagram illustrating the network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0043] A network entity included in the network structure of the 5G system of Fig. 1 may include a network function (hereinafter NF) depending on the system implementation.

[0044] Referring to FIG. 1, the network structure of a 5G system may include various network entities. For example, a 5G system may include at least one of an authentication server function (AUSF) entity, a core access and mobility management function (AMF) entity, a session management function (SMF) entity, a policy control function (PCF) entity, an application function (AF) entity, a unified data management (UDM) entity, a data network (DN), a network exposure function (NEF) entity, a network slicing selection function (NSSF) entity, a user plane function (UPF) entity, a radio access network (R)AN, or a terminal (e.g., a user device (UE or terminal).

[0045] Each NF entity of the 5G system can support the following functions.

[0046] AUSF can process and store data for UE authentication.

[0047] The AMF provides functions for connectivity and mobility management at the UE level, and one AMF can be connected per UE. Specifically, the AMF provides signaling between CN (core network) nodes for mobility between 3GPP access networks, termination of radio access network (RAN) CP (control plane) interfaces (e.g., N2 interfaces), termination of NAS (non-access stratum) signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (e.g., registration area management), connection management, idle mode UE reachability (e.g., which may include control and execution of paging retransmission), mobility management control (e.g., subscription and policy), support for intra-system and inter-system mobility, support for network slicing, SMF selection, lawful interception (e.g., for AMF events and interfaces to LI systems), provision of session management (SM) message delivery between the UE and the SMF, and a transparent proxy for SM message routing. It can support functions such as access authentication, access authorization including roaming authorization checks, provision of SMS message delivery between UE and SMSF, security anchor function (hereinafter SAF) and / or security context management (hereinafter SCM).Some or all of the functions of an AMF entity can be supported within a single instance of a single AMF entity.

[0048] DN may mean, for example, operator services, internet access, or third-party services. DN may transmit downlink protocol data units (hereinafter PDU) to a UPF entity or receive PDUs transmitted from a UE from a UPF entity.

[0049] A PCF entity can receive information about packet flows from an application server and provide functions for determining policies such as mobility management and session management. Specifically, a PCF entity can support functions such as supporting a unified policy framework for controlling network behavior, providing policy rules so that control plane function entity(s) (e.g., AMF entity, SMF entity, etc.) can enforce policy rules, and implementing a front end to access relevant subscription information for policy decisions within a user data repository (hereinafter UDR).

[0050] SMF entities provide session management functions, and if a UE has multiple sessions, each session can be managed by a different SMF entity. Specifically, the SMF entity can support functions such as session management (e.g., session establishment, modification, and termination including maintaining a tunnel between the UPF entity and the (R)AN node), UE IP (internet protocol) address allocation and management (e.g., including optional authentication), selection and control of UP functions, setting up traffic steering to route traffic from the UPF entity to an appropriate destination, termination of interfaces toward policy control functions, enforcement of control parts of policies and QoS (quality of service), lawful interception (e.g., for SM events and interfaces to LI systems), termination of SM parts of NAS messages, downlink data notification, initiation of AN-specific SM information (e.g., transmitted to (R)AN (102) via N2 through the AMF entity), determination of session and service continuity (SSC) mode of the session, and roaming functions. Some or all of the functions of an SMF entity can be supported within a single instance of an SMF entity.

[0051] A UDM entity can store user subscription data, policy data, etc. A UDM entity (109) may include at least one of two parts, namely an application front end (FE) and a user data repository (UDR).

[0052] The FE may include a UDM FE responsible for location management, subscription management, and credential processing, and a PCF entity responsible for policy control. The UDR may store data required for the functions provided by the UDM-FE and policy profiles required by the PCF entity. The data stored in the UDR may include user subscription data, such as subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data, as well as policy data. The UDM-FE may support functions such as access to subscription information stored in the UDR, authentication credential processing, user identification handling, access authentication, enrollment / mobility management, subscription management, and SMS management.

[0053] The UPF entity can forward downlink PDUs received from the DN to the UE (101) via (R)AN, and forward uplink PDUs received from the UE (101) to the DN (110) via (R)AN. Specifically, the UPF entity can support functions such as an anchor point for intra / inter RAT (radio access technology) mobility, an external PDU session point for interconnection to a data network, packet routing and forwarding, packet inspection and policy rule enforcement in the user plane, lawful intercept, traffic usage reporting, an uplink classifier to support routing of traffic flows to a data network, a branching point to support multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, or uplink / downlink rate enforcement), uplink traffic verification (e.g., SDF mapping between service data flow (hereinafter SDF) and QoS flow), transport level packet marking within the uplink and downlink, downlink packet buffering, and downlink data notification triggering. Some or all of the functions of a UPF entity can be supported within a single instance of UPF.

[0054] AF entities can interact with the 3GPP core network to provide services (e.g., supporting functions such as application impact on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control).

[0055] (R)AN can collectively refer to a new radio access network that supports both evolved E-UTRA, which is an evolved version of 4G radio access technology, and new radio access technology (new radio, hereinafter NR) (e.g., gNB).

[0056] The gNB performs functions for radio resource management (e.g., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs on uplink / downlink (e.g., scheduling)), IP (Internet Protocol) header compression, encryption and integrity protection of user data streams, selection of an AMF upon UE attachment when routing to an AMF is not determined from information provided to the UE, routing of user plane data to UPF(s), routing of control plane information to an AMF, connection setup and termination, scheduling and transmission of paging messages (e.g., originating from an AMF), scheduling and transmission of system broadcast information (e.g., originating from an AMF or operation and maintenance (O&M)), measurement and measurement reporting setup for mobility and scheduling, transport level packet marking on the uplink, session management, and network slicing. It can support functions such as QoS flow management and mapping to data wireless bearers, support for UEs in inactive mode, NAS message distribution function, NAS node selection function, wireless access network sharing, dual connectivity, and tight interworking between NR and E-UTRA.

[0057] UE can refer to a user device. A user device may be referred to by terms such as terminal, ME (mobile equipment), or MS (mobile station). Furthermore, a user device may be a portable device, such as a laptop, mobile phone, PDA (personal digital assistant), smartphone, or multimedia device. Alternatively, it may be a non-portable device, such as a PC (personal computer) or onboard vehicle.

[0058] NEFs can provide means to securely expose internal exposure / re-exposure, application functions, services and capabilities for edge computing provided by 3GPP network functions (e.g., third party). NEF(s) can receive information from other NF(s) (e.g., based on the exposed capability(s) of other NF(s). NEFs can store the received information as structured data using a standardized interface to a data storage network function. The stored information may be re-exposed by the NEF entity to other NF entity(s) and AF entity(s) and used for other purposes, such as analysis.

[0059] NRF can support service discovery features. NF can receive NF discovery requests from NF instances and provide information about discovered NF instances to the NF instances. Additionally, it can maintain available NF instances and the services they support.

[0060] In FIG. 1, for convenience, a reference model is illustrated for the case where a UE accesses one DN using one PDU session, but the present disclosure is not limited thereto and may include the case where one or more DNs are accessed using one or more PDU sessions.

[0061] A UE can simultaneously access two or more data networks (e.g., local and central) using multiple PDU sessions. In this case, two or more SMFs may be selected for different PDU sessions. However, each SMF can control both the local UPF and the central UPF within the PDU session.

[0062] A UE can simultaneously access two or more data networks (e.g., local and central) provided within a single PDU session.

[0063] In 3GPP systems, a conceptual link connecting NFs within a 5G system can be defined as a reference point. For example, the reference point(s) included in the 5G system of FIG. 1 may be as follows.

[0064] - N1: Reference point between UE and AMF

[0065] - N2: Reference point between (R)AN and AMF

[0066] - N3: Reference point between (R)AN and UPF

[0067] - N4: Reference point between SMF and UPF

[0068] - N5: Reference point between PCF and AF

[0069] - N6: Reference point between UPF and DN

[0070] - N7: Reference point between SMF and PCF

[0071] - N8: Reference point between UDM and AMF

[0072] - N9: Reference point between 2 core UPFs

[0073] - N10: Reference point between UDM and SMF

[0074] - N11: Reference point between AMF and SMF

[0075] - N12: Reference point between AMF and AUSF

[0076] - N13: Reference point between UDM and AUSF

[0077] - N14: Reference point between 2 AMFs

[0078] - N15: Reference point between PCF and AMF in non-roaming scenarios, reference point between PCF and AMF within the visited network in roaming scenarios

[0079] FIG. 2 illustrates the structure of a system supporting edge computing roaming services according to embodiments of the present disclosure. The system of FIG. 2 may include the structure of the 5G core network of FIG. 1 as part.

[0080] A 5G system architecture supporting edge computing services may include various network functions (NFs), and FIG. 2 illustrates some of these, including an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), unified data management (UDM), a data network (DN) or a local part of the data network capable of local access, a user plane function (UPF), a (radio) access network ((R)AN), and a terminal (UE). A 5G system supporting edge computing services may include various network functions (NFs). Referring to FIG. 2, a 5G system terminal (user equipment, UE) supporting edge computing services may include 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), unified data management (UDM), a data network (DN), a user plane function (UPF), a local part of the DN capable of local access to the data network, and an L-UPF (local UPF). The local part of the DN may include an edge application server (EAS).

[0081] Each NF illustrated in FIG. 2 can provide substantially the same functions as those described in FIG. 1. In addition, to support an edge computing roaming service, the NFs can support the following functions.

[0082] - AMF: The AMF provides functions for connectivity and mobility management at the UE level, and by default, one AMF can be connected per UE.

[0083] - DN: For example, it may mean operator services, internet access, or third-party services. The DN can transmit downlink protocol data units (PDUs) to the UPF or receive PDUs transmitted from the UE from the UPF.

[0084] - PCF: The PCF can receive information about packet flows from the application server and provide the ability to determine policies such as mobility management and session management. The PCF can support at least one of the following functions: support for a unified policy framework to control network behavior; provide policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce policy rules; and provide a front-end implementation to access relevant subscription information for policy decisions within the unified data repository (UDR).

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

[0086] - UDM: UDM can store user sign-up data, policy data, etc.

[0087] - UPF: The UPF forwards downlink PDUs received from the DN to the UE via the (R)AN, and can forward uplink PDUs received from the UE to the DN via the (R)AN.

[0088] - Local part of DN: A local part of DN is a part of a DN that may refer to a data network with short data transmission paths where local access is possible. Additionally, a local part of DN may refer to a DN where edge application servers (EAS) supporting edge computing services are deployed. An edge data network (EDN) may refer to a data network where edge computing servers are deployed. A local part of DN can be considered as a local portion of a data network or a local data network (local DN).

[0089] - ULCL(uplink classifier): ULCL can refer to a UPF that has the function of classifying and transmitting uplink signals.

[0090] - L-UPF (local UPF): L-UPF can act as the session end (PDU Session Anchor) for sessions transmitted to a local part of the DN.

[0091] - EASDF (Edge Application Server Discovery Function): The EASDF can process DNS (Domain Name System) queries transmitted from the terminal based on rules provided by the SMF. For example, the EASDF can forward DNS queries sent by the terminal to a DNS server, receive DNS responses, send relevant reports to the SMF, and perform actions such as providing DNS responses to the terminal.

[0092] - I-SMF (Intermediate SMF) can manage sessions related to geographically deployed edge computing services. I-SMF can apply policies related to edge computing service sessions deployed in a specific region to ULCL or L-UPF. I-SMF can configure DNS processing rules for EASDFs that handle DNS queries related to services deployed in a specific region.

[0093] When management of edge application server deployment information is performed through SMF / NEF (Network Exposure Function) / UDR, due to the characteristics of EAS hosted in a cloud environment, the overhead of 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 related edge deployment information may increase.

[0094] Unlike a conventional I-SMF in which the I-SMF selects a UPF by transmitting I-SMF-related N4 session information from the SMF, an I-SMF according to one embodiment of the present disclosure can directly receive local offloading policy information from the PCF during a PDU session establishment procedure or a PDU session change procedure, and directly perform the creation of N4 session information and the notification procedure for user plane events in the I-SMF.

[0095] During the terminal registration process, the AMF may receive SMF selection subscription data from the UDM, which includes local offloading policy indication information for each DNN and S-NSSAI. During the terminal's PDU session establishment process, the AMF may select an I-SMF that supports the local offloading policy based on the terminal's location information, S-NSSAI and DNN information received from the terminal, and the SMF selection subscription data received during the registration process. The I-SMF receives a request message for PDU session establishment from the AMF, which includes the local offloading policy indication and PDU session-related information (DNN, S-NSSAI) received from the terminal, and can select a UPF managed by an appropriate I-SMF to perform the N4 session establishment operation. Subsequently, the I-SMF may transmit a request for PDU session creation, which includes the DNAI list and local offloading policy indication supported by the I-SMF, to the SMF. The SMF transmits the local offloading policy indication to the PCF to receive PCC rules containing the local offloading policy. After receiving PCC rules containing local offloading policies from PCF, SMF can pass the local offloading policies to I-SMF.

[0096] I-SMF obtains DNN (Data Network Name) and S-NSSAI (Single Network Slice Selection Assistance Information) information regarding a PDU session from the SMF, and can execute a local offloading policy for the PDU session identified by the said DNN and S-NSSAI. I-SMF obtains EASDF or local NEF information related to the PDU session and, in conjunction with the said EASDF or local NEF, can perform actions necessary for managing the relevant PDU session or configure processing rules for DNS messages transmitted through the relevant PDU session. Specifically, I-SMF can perform EASDF discovery operations based on at least one of the following information: S-NSSAI, DNN, the N6 IP address of the EASDF, the N6 IP address of the PSA UPF, Location as per NF profile, DNAI, and Supported DNS security protocols. Subsequently, I-SMF can transmit configuration information (DNS message handling rule) for processing DNS messages within the EASDF, generated based on the EDI information, to the EASDF selected in the above process.I-SMF may use at least one of the following information to generate DNS message processing rules associated with PDU sessions: Local configuration associated with the (DNN, S-NSSAI, Internal Group Identifier) ​​of the PDU Session and / or EAS Deployment Information provided by the AF or preconfigured in the I-SMF and / or Information derived from the UE location such as candidate L-PSA(s) supported by I-SMF and / or PDU Session information, like PDU Session L-PSA(s) and ULCL / BP; and / or N6 delay measurement results; and / or Internal Group Identifier received in the Session Management Subscription data from the UDM; and / or IP address or DNAI (e.g., common EAS, common DNAI) cached locally or retrieved from UDR via PCF. The information for setting the EDNS Client Subnet Option or Local DNS Server Address provided by I-SMF to the EASDF is part of the DNS message processing rules for processing DNS Queries from the UE. I-SMF can update DNS message processing rules for EASDF, for example, update the EDNS client subnet (ECS) option to be used for a given FQDN or the local DNS server.The ECS options updated in the above I-SMF may include configuration information related to DNS Query message configuration and transmission, taking into account N6 latency information measured by the I-SMF. The I-SMF may transmit selected EASDF-related information (IP address of EASDF) to the AMF, and transmit the EASDF-related information (IP address of EASDF) to the terminal by including it in the PDU session establishment acceptance message. The terminal may transmit the DNS query message to the EASDF (local EASDF) received from the I-SMF. Based on the FQDN information within the DNS query message received from the terminal, if the FQDN within the DNS query message is a DNS query message that can be processed by a Local DNS server according to the DNS processing rules set in the I-SMF, the EASDF may transmit it to the Local DNS server configured in the EASDF to receive a DNS response message. The DNS response message received from the Local DNS server may include the FQDN-related EAS information (e.g., IP address(s) of EAS) requested by the terminal. The EASDF can request an appropriate EAS selection operation by transmitting one or more received EAS-related information to the I-SMF. The I-SMF can select an appropriate EAS from among the EASs received by the EASDF from the Local DNS server, transmit the corresponding information to the EASDF, and request the delivery of the selected EAS information to the terminal via a DNS response message.For the selection of a Candidate DNAI for an FQDN of a UE, I-SMF may consider the UE location, network topology, EDI, N6 delay measurements between Candidate UPF(s) supported by I-SMF and Candidate DNAI(s) supported by I-SMF, and relevant policy information regarding PDU Sessions transmitted from PCF, or may consider information pre-configured in I-SMF. In the above expression, Candidate UPF(s) supported by I-SMF and Candidate DNAI supported by I-SMF refer to Candidate UPF(s) and Candidate DNAI managed by I-SMF. I-SMF may perform an appropriate EAS selection operation based on traffic routing information received through SMF. I-SMF determines the associated N6 traffic routing information for the Candidate DNAI supported by I-SMF based on the N6 traffic routing information for the DNAI included in the EDI, and can configure the Local PSA UPF selected by I-SMF with the forwarding action derived from the N6 traffic routing information. I-SMF can perform the selection of the Local PSA supported by I-SMF based on the N6 delay determined through the N6 delay measurement procedure. In the case of UL CL, the Traffic Detection Rule and Traffic Routing Rule can be determined based on the IP Address Range(s) per DNAI included in the EAS Deployment Information received by I-SMF, or the PCC Rule received from the PCF, or pre-configured information.After measuring N6 latency for a connection with an already established EAS, I-SMF can perform an operation of re-selection of L-PSA UPF supported by I-SMF and / or an edge relocation based on the N6 latency measurement information, and then trigger an EAS re-discovery procedure.

[0097] FIGS. 3a and 3b are drawings illustrating an offloading service support procedure that considers N6 delay requirements based on traffic routing information in an I-SMF according to an embodiment of the present disclosure.

[0098] In step 0a, AF may send a Subscribe request message to the UDR to receive update notifications regarding DNAI-specific traffic routing requirement information (e.g., N6 delay requirements or N6 delay support indication). The subscribe request message may include at least one of the following: a list of information to be notified from the UDR, DNN, S-NSSAI, PLMN ID, the address (IP or Ethernet) of one or more UE(s), one or more GPSIs, SUPI (Subscription Permanent Identifier), etc., and UE Group ID.The list of information to be received as a notification from the above UDR may include at least one of the following: External Group Identifier(s), External Application Identifier or traffic filtering information, AF-Service-Identifier, a list of DNAI(s) and corresponding routing profile ID(s) or N6 traffic routing information, Indication of traffic correlation, Indication of application relocation possibility, Indication of UE IP address preservation, Early and / or late notifications about UP path management events, Notification Target Address, immediate reporting flag, Temporal validity condition, Spatial validity condition, User Plane Latency Requirements, Information for EAS IP Replacement in 5GC, Indication for EAS Relocation and AF indication for simultaneous connectivity over source and target PSA at edge relocation, EAS Correlation indication, External Subscriber Category(s), SFC Identifier(s), Metadata, Common EAS IP address, Traffic Correlation ID, and FQDN(s). The UDR sends a subscribe response message to the PCF in response to the PCF's subscribe request message.The subscribe response message may contain information regarding the successful processing result of the subscribe. The AF may transmit DNAI-specific traffic routing requirement information (e.g., AF traffic influence request information) to the NEF. The NEF may perform authorization regarding whether the AF can provide AF traffic influence request information. According to one embodiment of the present invention, the NEF may perform authorization regarding whether the AF can provide AF traffic influence request information. If the NEF successfully performs authorization for the AF's request information, the NEF may perform a storage / update operation on the UDR for AF request information containing AF traffic influence request information for traffic routing (e.g., N6 delay requirements or N6 delay support indication). If the PCF performs a subscription operation to the UDR to receive notifications of the AF request information when the AF request information changes or is received, the UDR may transmit the updated AF request information to the PCF via a Nudr_DM_Notify message. The notification information may include AF traffic routing information (AF traffic influence request information for traffic routing).

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

[0100] [Table 1]

[0101]

[0102] The NEF transmits a subscribe response message to the I-SMF in response to the subscribe request message of the I-SMF. The subscribe response message may contain information regarding the result of the successful processing of the subscribe. The AF may transmit information related to edge computing services (e.g., EAS Deployment Information) to the NEF. The NEF may perform authorization regarding whether the AF can provide the information related to edge computing services. According to one embodiment of the present invention, the NEF may perform authorization regarding whether the AF can provide EAS deployment information. If the authorization is successfully performed, the NEF may process requests for application within the mobile network regarding the edge computing service information received subsequently, in accordance with the subscribe request received from the I-SMF. Additionally, the NEF may identify a DNN or S-NSSAI corresponding to the AF identifier or AF service identifier information provided by the AF. NEF can identify a subscribe request received from a corresponding PDU session or a previous LECF for a DNN / S-NSSAI directly provided by AF, or a DNN or S-NSSAI corresponding to AF identifier or AF service identifier information. If there was a subscribe request received from an I-SMF corresponding to edge computing service-related information received from AF, NEF may decide to provide AF request information to the I-SMF.If a subscription / notification corresponding to a subscribe request received from I-SMF that corresponds to the edge computing service-related information received from AF has been created, NEF may decide to notify I-SMF of the relevant information, and in this process, may decide not to store the relevant information in the UDR. Whether or not to store the relevant information in the UDR may be determined according to the operator policy set in NEF. NEF may provide AF with the authorization result regarding the edge computing service-related information (e.g., EAS Deployment Information) received from AF. NEF may transmit a notification message containing the edge computing service-related information received from AF to I-SMF based on the result of the authorization operation regarding whether AF can provide the relevant edge computing service-related information. The notification message may include at least one of a notification identifier, DNN, S-NSSAI, PLMN ID, UE ID (GPSI, SUPI, etc.), UE Group ID, and edge computing service-related information (EAS deployment information) received from AF.

[0103] During the terminal registration procedure in Step 1, the AMF can receive SMF selection subscription data containing local offloading policy indication information for each DNN and S-NSSAI from the UDM.

[0104] In step 2, the UE can perform a PDU session establishment request operation. The AMF can receive a PDU session establishment request message containing S-NSSAI and DNN information from the terminal.

[0105] During the process of establishing a PDU session of the terminal in Step 3, the AMF can select an I-SMF that supports a local offloading policy based on the terminal's location information, S-NSSAI and DNN information received from the terminal, and SMF selection subscription data received in the registration procedure.

[0106] In steps 4 and 5, the I-SMF may receive a request message for establishing a PDU session from the AMF, which includes local offloading policy directives and PDU session-related information (DNN, S-NSSAI) received from the terminal. Afterward, the I-SMF may send a response message to the AMF regarding the request message for establishing the PDU session.

[0107] In step 6a, the I-SMF can select the L-PSA UPF managed by the I-SMF.

[0108] In step 6b, the I-SMF can perform the N4 session establishment operation with the P-PSA UPF selected in step 6a.

[0109] In step 7, I-SMF can forward a request to create a PDU session to SMF, including a DNAI list and local offloading policy directives supported by I-SMF.

[0110] In step 8, the SMF receives session management subscription data from the UDM and can check whether the corresponding PDU session establishment request information can be used based on the DNN, SUPI, and S-NSSAI.

[0111] In Step 9, the SMF can request the delivery of PCC rules containing the local offloading policy by passing the local offloading policy directive to the PCF. Additionally, the SMF can receive AF influence on traffic routing information transmitted from the AF along with the PCC rules. The PCF can perform creation or update operations on PCC rules to include the local offloading policy and AF influence on traffic routing Enforcement Control to be transmitted to the I-SMF within the PCC rules. The above AF influence on traffic routing Enforcement Control can be created based on the AF traffic influence request information received from the UDR through Step 0a. The list of AF influence on traffic routing Enforcement Controls that the SMF receives from the PCF via PCC rules may include at least one of the information listed in Table 2 below.

[0112] [Table 2]

[0113]

[0114] In step 10, the PCF may transmit to the SMF a PCC rule containing AF influence on traffic routing information, which includes a local offloading policy and one or more pieces of information within the AF influence on traffic routing Enforcement Control in Table 2 above.

[0115] In Step 11, the SMF can perform a filtering operation on AF influence on traffic routing information (AF influence on traffic routing control parameters) based on the DNAI list information supported by I-SMF regarding the AF influence on traffic routing Enforcement Control information received through the PCC rule. If the DNAI list supported by I-SMF is included along with a Local offloading policy indication within the message transmitted to the PCF in Step 9, the PCF can instead perform a filtering operation based on the DNAI list supported by I-SMF regarding the information within AF influence on traffic routing Enforcement Control within the PCC rule. If the SMF receives a PCC rule containing information within AF influence on traffic routing Enforcement Control filtered based on the DNAI list supported by I-SMF from the PCF, the SMF can skip Step 11 and perform the operation in Step 12 of transmitting the received information directly to the I-SMF.

[0116] In Step 12, the SMF can transmit the local offloading policy within the PCC rule and AF influence on traffic routing information received from the PCF to the I-SMF. Upon receiving the local offloading policy, the I-SMF can request updated information regarding edge computing services through the NEF.

[0117] In step 13, the I-SMF can perform UP path configuration (e.g., N6 delay measurement) operations using edge computing service-related information received from the NEF. If the I-SMF receives information that needs to be configured in the UPF, such as information required for traffic routing configuration within the edge computing service-related information received from the NEF or AF traffic influence information received from the PCF via the SMF (e.g., N6 traffic routing information, DNAI information, traffic description, etc.), it can perform operations to configure the corresponding information in the UPF. If the I-SMF receives information related to UP path configuration, such as information required for traffic routing configuration within the edge computing service-related information received from the NEF or AF traffic influence information received from the PCF via the SMF (e.g., N6 traffic routing information, DNAI information, traffic description, etc.), it can perform operations to modify the UP path, such as ULCL insertion / PSA UPF insertion / PSA UPF relocation.

[0118] In Step 13a, the I-SMF can select N6 delay measurement information (e.g., N6 Delay measurement protocol) for measuring N6 delay at the DNAI-specific L-PSA UPF selected and managed by the I-SMF based on the EAS Deployment Information received from the NEF. The operation for measuring N6 delay can be determined for each DNAI based on the edge computing service information received from the NEF. Additionally, if one or more N6 Delay measurement protocol information for N6 Delay measurement per DNAI is transmitted within the edge computing service information, the I-SMF may select an appropriate N6 Delay measurement protocol based on local operator settings, etc., or N6 Delay measurement protocol information ordered according to the priority set by the AF may be included in the edge computing service information and transmitted to the I-SMF.

[0119] In step 13b, the I-SMF may select an L-PSA UPF(s) managed by the I-SMF that supports the N6 Delay measurement protocol selected in step 13a.

[0120] In step 14, the I-SMF may transmit information for N6 delay measurement per DNAI supported by the I-SMF (e.g., N6 Delay measurement protocol and / or N6 Delay measurement requirements) to candidate L-PSA UPFs based on information related to N6 delay measurement within the EDI information (e.g., N6 Delay measurement protocol) and information regarding N6 delay requirements within the AF influence on traffic routing information. The N6 delay measurement requirements information may include information regarding N6 delay requirements received from the AF and information regarding the N6 delay reporting period or method. According to an embodiment of the present invention, the I-SMF may perform an N6 delay measurement request operation to the L-PSA UPFs supported by the I-SMF through the Nupf_EventExposure_Subscribe message. The above N6 delay measurement related Event Exposure Subscribe (Nupf_EventExposure_Subscribe) request message may include an N6 delay measurement request including an Event ID ('N6 delay measurement'), a Notification Target Address (I-SMF info), and Event Reporting Information. Alternatively, I-SMF may perform the N6 delay measurement request operation using N4 information with L-PSA UPFs supported by I-SMF. Based on the requirement information for N6 delay measurement within the N4 information received from I-SMF, UPF may report the N6 delay measurement value measured by I-SMF using the N4 Session Level Reporting Procedure when specific conditions (e.g., when a periodic or constant N6 delay threshold is exceeded) are satisfied.

[0121] In step 15, the I-SMF can perform an operation to configure by considering the N6 delay measurement received from the Candidate L-PSA UPFs for each DNAI supported by the I-SMF, and by transmitting N4 rule information for the (re)selection operation of an appropriate L-PSA UPF. For the selection of a Candidate DNAI for an FQDN for a UE, the I-SMF may consider the UE location, network topology, EDI, the N6 delay measurement between the Candidate UPF(s) supported by the I-SMF and the Candidate DNAI(s) supported by the I-SMF, and relevant policy information regarding the PDU Session transmitted from the PCF, or information pre-configured in the I-SMF. I-SMF determines the associated N6 traffic routing information for the Candidate DNAI supported by I-SMF based on the N6 traffic routing information for the DNAI included in the EDI, and can configure the Local PSA UPF selected by I-SMF using the forwarding action derived from the N6 traffic routing information. I-SMF can perform the Selection of L-PSA UPF supported by I-SMF based on the N6 delay determined through the N6 delay measurement procedure. In the case of UL CL, the Traffic Detection Rule and Traffic Routing Rule can be determined based on the IP Address Range(s) per DNAI included in the EAS Deployment Information received by I-SMF, or the PCC Rule received from the PCF, or pre-configured information.After measuring N6 latency for a connection with an already established EAS, I-SMF can perform a re-selection of L-PSA UPF supported by I-SMF and / or an edge relocation operation based on the N6 latency measurement information, and then trigger an EAS re-discovery procedure.

[0122] In steps 16 and 17, local result information regarding the terminal's PDU session establishment request can be transmitted to the terminal via AMF.

[0123] According to one embodiment of the present invention, the I-SMF can perform an EASDF discovery operation based on at least one of the following information: S-NSSAI, DNN, the N6 IP address of the EASDF, the N6 IP address of the PSA UPF, Location as per NF profile, DNAI, and Supported DNS security protocols. Subsequently, the I-SMF can transmit configuration information (DNS message handling rule) for processing DNS messages within the EASDF, generated based on EDI information, to the EASDF selected in the above process. To generate a DNS message processing rule related to a PDU session, the I-SMF includes Local configuration associated with the (DNN, S-NSSAI, Internal Group Identifier) ​​of the PDU Session and / or EAS Deployment Information provided by the AF or preconfigured in the I-SMF and / or Information derived from the UE location such as candidate L-PSA(s) supported by I-SMF and / or PDU Session information, like PDU Session L-PSA(s) and ULCL / BP; and / or N6 delay measurement results; and / or Internal Group Identifier received in the Session Management Subscription data from the UDM; and / or IP address or DNAI (e.g., common EAS, common DNAI) cached locally or retrieved from UDR via PCF; at least one of this information may be used.The information provided by I-SMF to EASDF for configuring the EDNS Client Subnet Option or Local DNS Server Address is part of the DNS message processing rules for processing DNS Queries from the UE. I-SMF can update the DNS message processing rules for EASDF, for example, by updating the EDNS Client Subnet (ECS) option or local DNS server to be used for a given FQDN. The ECS option updated by I-SMF may include configuration information related to DNS Query message configuration and transmission, taking into account N6 latency information measured by I-SMF.

[0124] FIGS. 4a and 4b are drawings illustrating an offloading service support procedure that considers N6 delay requirements based on traffic routing information in an I-SMF according to an embodiment of the present disclosure.

[0125] In Step 0, the UE can perform a PDU session establishment request operation. During the terminal registration procedure, the AMF may receive SMF selection subscription data from the UDM, which includes local offloading policy indication information for each DNN and S-NSSAI. During the terminal's PDU session establishment process, the AMF may select an I-SMF that supports the local offloading policy based on the terminal's location information, S-NSSAI and DNN information received from the terminal, and the SMF selection subscription data received during the registration procedure. The I-SMF receives a request message for PDU session establishment from the AMF, which includes the local offloading policy indication and PDU session-related information (DNN, S-NSSAI) received from the terminal, and can select a UPF managed by an appropriate I-SMF to perform an N4 session establishment operation. Subsequently, the I-SMF may transmit a PDU session creation request to the SMF, which includes the DNAI list and local offloading policy indication supported by the I-SMF. SMF can receive PCC rules containing local offloading policies by transmitting local offloading policy directives to PCF. After receiving PCC rules containing local offloading policies from PCF, SMF can transmit the local offloading policies to I-SMF. If I-SMF, having received the local offloading policies from SMF, subsequently transmits PCOs within PDU session establishment request messages indicating that the relevant terminal supports EDC functions (Edge DNS Client functionality), I-SMF can perform EASDF discovery and selection operations.I- SMF can receive UE subscription information from the UDM, including an indication on UE authorization for EAS discovery via EASDF, to determine whether the terminal can perform EAS discovery via EASDF, and can check whether the terminal has been authorized for EAS discovery via EASDF.

[0126] I-SMF may send a subscribe request message to NEF to receive reports on edge computing service-related information (e.g., EAS deployment information). The subscribe request message may include at least one of the following: a list of information to be notified from NEF, DNN, S-NSSAI, PLMN ID, UE ID (GPSI (Generic Public Subscription Identifier), SUPI (Subscription Permanent Identifier), etc.), and UE Group ID. The list of EAS deployment information to be notified from NEF by I-SMF may include at least one of the information listed in Table 3 below.

[0127] [Table 3]

[0128]

[0129] The NEF transmits a subscribe response message to the I-SMF in response to the I-SMF's subscribe request message. The subscribe response message may contain information regarding the result of the successful processing of the subscribe. The AF may transmit information related to edge computing services (e.g., EAS Deployment Information) to the NEF. The NEF may perform authorization regarding whether the AF can provide the information related to edge computing services. According to one embodiment of the present invention, the NEF may perform authorization regarding whether the AF can provide EAS deployment information. If the authorization is successfully performed, the NEF may process requests for application within the mobile network regarding the edge computing service information received subsequently, in accordance with the subscribe request received from the I-SMF. Additionally, the NEF may identify a DNN or S-NSSAI corresponding to the AF identifier or AF service identifier information provided by the AF. NEF can identify a subscribe request received from a corresponding PDU session or a previous LECF for a DNN / S-NSSAI directly provided by AF, or a DNN or S-NSSAI corresponding to AF identifier or AF service identifier information. If there was a subscribe request received from an I-SMF corresponding to edge computing service-related information received from AF, NEF may decide to provide AF request information to the I-SMF.If a subscription / notification corresponding to a subscribe request received from I-SMF that corresponds to the edge computing service-related information received from AF has been created, NEF may decide to notify I-SMF of the relevant information, and in this process, may decide not to store the relevant information in UDR. Whether or not to store the relevant information in UDR may be determined according to the operator policy set in NEF. NEF may provide AF with the authorization result regarding the edge computing service-related information (e.g., EAS Deployment Information) received from AF. NEF may transmit a notification message containing the edge computing service-related information received from AF to I-SMF based on the result of the authorization operation regarding whether AF can provide the relevant edge computing service-related information. The notification message may include at least one of a notification identifier, DNN, S-NSSAI, PLMN ID, UE ID (GPSI, SUPI, etc.), UE Group ID, and edge computing service-related information (EAS deployment information) received from AF. Additionally, PCF may send a subscribe request message to UDR to receive a report on changes to AF requests. The subscribe request message may include at least one of the following: Data Set = Application Data; Data Subset = AF traffic influence request information; Data Key = S-NSSAI and / or DNN and / or Internal Group Identifier or SUPI.

[0130] In Step 1, AF can determine to generate AF requirements for the transmission of DNAI-specific traffic routing requirement information (e.g., AF request to influence traffic routing including N6 delay requirements or N6 delay support indication).

[0131] In Step 2, the AF may transmit AF requirement information to the NEF, including DNAI-specific traffic routing requirement information (e.g., AF request to influence traffic routing including N6 delay requirements or N6 delay support indication). The NEF may perform authorization regarding whether the AF can provide information related to the DNAI-specific traffic routing requirements. According to one embodiment of the present invention, the NEF may perform authorization regarding whether the AF can provide AF request to influence traffic routing information.

[0132] In step 3a, if the authorization for the AF's request information is successfully performed in the NEF, the NEF can perform a save / update operation in the UDR for the AF request information containing AF traffic influence request information for traffic routing information (e.g., N6 delay requirements or N6 delay support indication).

[0133] In step 3b, NEF can transmit result information regarding AF's request information to AF.

[0134] In Step 4, if the PCF performs the action of subscribing to the notification of the information when the AF request is changed or received in Step 0, the UDR may transmit the updated AF request information to the PCF via the Nudr_DM_Notify message. The notification information may include AF traffic influence request information for traffic routing.

[0135] The PCF can perform a PCC rule update operation to transmit updated AF influence on traffic routing information to the SMF based on AF traffic routing information received from the UDR. The PCF can perform a PCC rule creation or update operation to include within the PCC rule an AF influence on traffic routing Enforcement Control updated based on the AF traffic routing information received from the AF, and a Local offloading policy to be transmitted to the I-SMF based on the Local offloading policy indication received from the SMF during the PDU session establishment request operation in Step 0 above. The list of AF influence on traffic routing Enforcement Controls to be received by the SMF from the PCF via the PCC rule may include at least one of the information listed in Table 4 below.

[0136] [Table 4]

[0137]

[0138] In step 5, the PCF can transmit to the SMF a PCC rule containing AF influence on traffic routing information, which includes a local offloading policy and one or more pieces of information within the AF influence on traffic routing Enforcement Control in Table 4 above.

[0139] In step 6, the SMF can perform a filtering operation on AF influence on traffic routing information (AF influence on traffic routing control parameters) based on the AF influence on traffic routing Enforcement Control information received through PCC rules and the DNAI list information supported by I-SMF.

[0140] In Step 7, the SMF can transmit the local offloading policy within the PCC rule and AF influence on traffic routing information received from the PCF to the I-SMF. Upon receiving the local offloading policy, the I-SMF can request updated edge computing service-related information through the NEF.

[0141] In step 8, I-SMF can receive updated edge computing service-related information by requesting the delivery of edge computing service-related information from NEF.

[0142] In step 9, the I-SMF can perform UP path configuration (e.g., N6 delay measurement) operations using updated edge computing service-related information. When the I-SMF receives information that needs to be configured in the UPF, such as information required for traffic routing configuration within edge computing service-related information received from the NEF or AF traffic influence information received from the PCF via the SMF (e.g., N6 traffic routing information, DNAI information, traffic description, etc.), it can perform operations to configure the corresponding information in the UPF. When the I-SMF receives information related to UP path configuration, such as information required for traffic routing configuration within edge computing service-related information received from the NEF or AF traffic influence information received from the PCF via the SMF (e.g., N6 traffic routing information, DNAI information, traffic description, etc.), it can perform operations to modify the UP path, such as ULCL insertion / PSA UPF insertion / PSA UPF relocation.

[0143] In Step 9a, the I-SMF can select N6 delay measurement information (e.g., N6 Delay measurement protocol) for measuring N6 delay at the DNAI-specific L-PSA UPF selected and managed by the I-SMF based on the EAS Deployment Information received from the NEF. The operation for measuring N6 delay can be determined for each DNAI based on the edge computing service information received from the NEF. Additionally, if one or more N6 Delay measurement protocol information for N6 Delay measurement per DNAI is transmitted within the edge computing service information, the I-SMF may select an appropriate N6 Delay measurement protocol based on local operator settings, etc., or N6 Delay measurement protocol information ordered according to the priority set by the AF may be included in the edge computing service information and transmitted to the I-SMF.

[0144] In step 9b, the I-SMF can select the L-PSA UPF(s) supported by the I-SMF that support the N6 Delay measurement protocol selected in step 9a.

[0145] In step 10, the I-SMF may transmit information for N6 delay measurement per DNAI supported by the I-SMF (e.g., N6 Delay measurement protocol and / or N6 Delay measurement requirements) to the Candidate L-PSA UPFs based on information related to N6 delay measurement within the EDI information (e.g., N6 Delay measurement protocol) and information regarding N6 delay requirements within the AF influence on traffic routing information. The N6 delay measurement requirements information may include information regarding N6 delay requirements received from the AF and information regarding the N6 delay reporting period or method. According to an embodiment of the present invention, the I-SMF may perform an N6 delay measurement request operation to the L-PSA UPFs supported by the I-SMF through the Nupf_EventExposure_Subscribe message. The above N6 delay measurement related Event Exposure Subscribe (Nupf_EventExposure_Subscribe) request message may include an N6 delay measurement request including Event ID ('N6 delay measurement'), Notification Target Address (I-SMF info), Event Reporting Information, etc. Alternatively, I-SMF may perform an N6 delay measurement request operation using N4 information with L-PSA UPFs supported by I-SMF. Based on the requirement information for N6 delay measurement within the N4 information received from I-SMF, UPF may report the N6 delay measurement value measured by I-SMF using the N4 Session Level Reporting Procedure when specific conditions (e.g., when a periodic or constant N6 delay limit value is exceeded) are satisfied.

[0146] In Step 11, the I-SMF can perform an operation to configure by transmitting N4 rule information and (re)selecting an appropriate L-PSA UPF, taking into account the N6 delay measurements received from the Candidate L-PSA UPFs for each DNAI supported by the I-SMF. For the selection of a Candidate DNAI for an FQDN for a UE, the I-SMF may consider the UE location, network topology, EDI, N6 delay measurements between the Candidate UPF(s) supported by the I-SMF and the Candidate DNAI(s) supported by the I-SMF, and relevant policy information regarding the PDU Session transmitted from the PCF, or may consider information pre-configured in the I-SMF. I-SMF determines the associated N6 traffic routing information for the Candidate DNAI supported by I-SMF based on the N6 traffic routing information for the DNAI included in the EDI, and can configure the Local PSA UPF selected by I-SMF using the forwarding action derived from the N6 traffic routing information. I-SMF can perform the Selection of L-PSA UPF supported by I-SMF based on the N6 delay determined through the N6 delay measurement procedure. In the case of UL CL, the Traffic Detection Rule and Traffic Routing Rule can be determined based on the IP Address Range(s) per DNAI included in the EAS Deployment Information received by I-SMF, or the PCC Rule received from the PCF, or pre-configured information.After measuring N6 latency for a connection with an already established EAS, I-SMF can perform a re-selection of L-PSA UPF supported by I-SMF and / or an edge relocation operation based on the N6 latency measurement information, and then trigger an EAS re-discovery procedure. In steps 12 and 13, local result information regarding the terminal's PDU session establishment request can be transmitted to the terminal via AMF.

[0147] According to one embodiment of the present invention, the I-SMF may transmit configuration information (DNS message handling rule) for processing DNS messages within the updated EASDF, generated based on updated EDI information, to the EASDF selected in the process. To update DNS message processing rules related to a PDU session, the I-SMF may use at least one of the following information to update DNS message processing rules: Local configuration associated with the (DNN, S-NSSAI, Internal Group Identifier) ​​of the PDU Session and / or EAS Deployment Information provided by the AF or preconfigured in the I-SMF and / or Information derived from the UE location such as candidate L-PSA(s) supported by I-SMF and / or PDU Session information, like PDU Session L-PSA(s) and ULCL / BP; and / or N6 delay measurement results; and / or Internal Group Identifier received in the Session Management Subscription data from the UDM; and / or IP address or DNAI (e.g., common EAS, common DNAI) cached locally or retrieved from UDR via PCF. The information provided by I-SMF to EASDF for setting the EDNS Client Subnet Option or Local DNS Server Address is part of the DNS message processing rules for processing DNS Queries from the UE.I-SMF can update DNS message processing rules for EASDF, for example, update EDNS client subnet (ECS) options or local DNS servers to be used for a given FQDN. The ECS options updated in the I-SMF may include configuration information related to DNS Query message configuration and transmission that takes into account N6 latency information measured in the I-SMF.

[0148] FIG. 5 is a block diagram showing an example of the configuration of a terminal (UE) according to one embodiment of the present disclosure.

[0149] As illustrated in FIG. 5, the terminal of the present disclosure may include a processor (530), a transceiver (510), and a memory (520). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. In addition, the processor (530), the transceiver (510), and the memory (520) may be implemented in the form of a single chip.

[0150] According to one embodiment, the processor (530) can control a series of processes that allow the terminal to operate according to the embodiments of the present disclosure described above. The processor (530) may be one or more, and the processor (530) may execute a program stored in memory (520).

[0151] The transceiver (510) can transmit and receive signals with a base station or network entity. The signal may include control information and data. The transceiver (1510) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (510), and the components of the transceiver (510) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (510) can receive a signal through a wireless channel and output it to a processor (530), and transmit the signal output from the processor (530) through a wireless channel.

[0152] According to one embodiment, the memory (520) may store programs and data necessary for the operation of the terminal. Additionally, the memory (520) may store control information or data included in signals transmitted and received by the terminal. The memory (520) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the memory (520) may be a plurality of. According to one embodiment, the memory (520) may store a program for performing the embodiments of the present disclosure described above.

[0153] FIG. 6 is a block diagram showing an example of the configuration of a network entity according to one embodiment of the present disclosure.

[0154] As illustrated in FIG. 6, the network entity of the present disclosure may include a processor (630), a transceiver (610), and a memory (620). However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more components or fewer components than the components described above. Furthermore, the processor (630), the transceiver (610), and the memory (620) may be implemented in the form of a single chip.

[0155] The processor (630) can control a series of processes to enable each network entity to operate according to the embodiments of the present disclosure described above. The processor (630) may be one or more, and the processor (630) may execute a program stored in memory (620).

[0156] The transceiver (610) can transmit and receive signals with a terminal or other network entity. The signal may include control information and data. The transceiver (610) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely an example of the transceiver (610), and the components of the transceiver (610) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (610) can receive a signal through a wireless channel and output it to a processor (630), and transmit the signal output from the processor (630) through a wireless channel.

[0157] According to one embodiment, the memory (620) may store programs and data necessary for the operation of the base station. Additionally, the memory (620) may store control information or data included in signals transmitted and received by the base station. The memory (620) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memory (620). According to one embodiment, the memory (620) may store a program for performing the embodiments of the present disclosure described above.

[0158] Meanwhile, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present invention and to aid in understanding the present invention, and are not intended to limit the scope of the present invention. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present invention are possible. Furthermore, each of the above embodiments may be combined and operated together as needed. For example, at least a portion of each of the embodiments of the present invention may be combined and operated by a base station, a terminal, or a specific network entity.

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

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

[0161] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory, hereinafter ROM), Electrically Erasable Programmable Read Only Memory (hereinafter EEPROM), magnetic disc storage device, Compact Disc-ROM (hereinafter CD-ROM), Digital Versatile Discs (hereinafter DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in a memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0162] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0163] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0164] The operations of the network entity or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the network entity or terminal device. That is, the control unit of the network entity or terminal device can execute the operations described above by reading the program code stored in the memory device by a processor or CPU (Central Processing Unit) and executing it.

[0165] Various components of network entities, base stations, or terminal devices and modules described herein may be operated using hardware circuits, such as, for example, complementary metal oxide semiconductor-based logic circuits, firmware, software, and / or a combination of hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.

[0166] Although specific embodiments have been described in the detailed description of the disclosure, it is understood that various modifications are possible without departing from the scope of the disclosure. Therefore, the scope of the disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. In the method of the I-SMF (intermediate-session management function) of a communication system, A step of receiving information related to the N6 delay measurement instruction from the AF (application function); A step of receiving EDI (edge ​​application server deployment information) from NEF (network exposure function); A step of identifying information related to N6 delay measurement based on EDI; and A method characterized by including the step of instructing a user plane function (UPF) to measure N6 delay based on the above information regarding N6 delay measurement.

2. In Paragraph 1, A method characterized by the above N6 delay measurement information including a measurement protocol.

3. In Paragraph 1, A method characterized by further including the step of receiving information about the N6 delay measurement result from UPF when the N6 delay measurement result satisfies a specific condition.

4. In Paragraph 3, A method characterized by further including the step of performing L-PSA (local PDU session anchor) UPF re-selection based on the above N6 delay measurement results.

5. In the method of the UPF (user plane function) of a communication system, A step of receiving instructions to measure N6 delay from the I-SMF (intermediate-session management function) based on information related to N6 delay measurement; and Includes a step of performing N6 delay measurement, A method characterized by the above N6 delay measurement information being based on EDI (edge ​​application server deployment).

6. In Paragraph 5, The above N6 delay measurement information includes a measurement protocol, and A method characterized in that the above N6 delay measurement is performed based on the above measurement protocol.

7. In Paragraph 5, A method characterized by further including the step of transmitting information about the N6 delay measurement result to I-SMF when the N6 delay measurement result satisfies a specific condition.

8. In Paragraph 7, A method characterized by performing L-PSA (local PDU session anchor) UPF re-selection by I-SMF based on the above N6 delay measurement results.

9. In the I-SMF (intermediate-session management function) of a communication system, Transmitter / receiver; and Receive information related to the N6 delay measurement instruction from AF (application function), and Receive EDI (edge ​​application server deployment information) from NEF (network exposure function), and Identify N6 delay measurement related information based on EDI, and I-SMF characterized by including a control unit configured to instruct a UPF (user plane function) to measure N6 delay based on the above information regarding N6 delay measurement.

10. In Paragraph 9, The above N6 delay measurement information is characterized by including a measurement protocol in the I-SMF.

11. In paragraph 9, the control unit is, I-SMF characterized by being further configured to receive information about the N6 delay measurement result from UPF when the N6 delay measurement result satisfies a specific condition.

12. In Clause 11, the control unit is, I-SMF characterized by being further configured to perform L-PSA (local PDU session anchor) UPF re-selection based on the above N6 delay measurement results.

13. In the user plane function (UPF) of a communication system, Transmitter / receiver; and Based on information regarding N6 delay measurement, it receives instructions to measure N6 delay from the I-SMF (intermediate-session management function), and It includes a control unit configured to perform N6 delay measurement, and UPF characterized by the above N6 delay measurement information being based on EDI (edge ​​application server deployment).

14. In Paragraph 13, The above N6 delay measurement information includes a measurement protocol, and UPF characterized in that the above N6 delay measurement is performed based on the above measurement protocol.

15. In paragraph 13, the control unit above, A UPF characterized by being further configured to transmit information about the N6 delay measurement result to the I-SMF when the N6 delay measurement result satisfies specific conditions.

Images