Method and device for subscribing to user plane function service and processing traffic in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. According to an embodiment of the present disclosure, a method performed by a user plane function (UPF) entity in a wireless communication system may comprise the steps of: transmitting, to a network repository function (NRF) entity, a registration request message including network function (NF) profile information about a UPF; and receiving a registration response message from the NRF entity, wherein the NF profile information about the UPF entity includes UPF information.

Description

Method and device for subscription and traffic processing of user plane function service in wireless communication system

[0001] The present disclosure relates to a method and apparatus for subscribing to a user plane function (UPF) service and processing traffic of the user plane function service in a wireless communication system.

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

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

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

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

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

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

[0008] The present disclosure provides a method and apparatus for subscribing to a user plane function (UPF) service (e.g., a UPF event exposure service) in a wireless communication system.

[0009] The present disclosure relates to a design method for modularizing a UPF in a wireless communication system and a method and device for registering, removing, searching, and updating a modularized UPF in an NRF (Network Repository Function).

[0010] The present disclosure provides a method and device for effectively performing service subscription in a wireless communication system.

[0011] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0012] According to one embodiment of the present disclosure, a method of a user plane function (UPF) entity in a wireless communication system includes the steps of transmitting a registration request message including network function (NF) profile information of the UPF to a network repository function (NRF) entity; and receiving a registration response message from the NRF entity; wherein the NF profile information of the UPF entity includes UPF function information.

[0013] According to one embodiment of the present disclosure, a method of a network repository function (NRF) entity in a wireless communication system includes the steps of: receiving a registration request message including network function (NF) profile information of a user plane function (UPF) from a UPF entity; storing the NF profile information; and transmitting a registration response message to the UPF entity; wherein the NF profile information of the UPF entity includes UPF function information.

[0014] According to one embodiment of the present disclosure, in a wireless communication system, a user plane function (UPF) entity includes a transceiver; and at least one processor; wherein the at least one processor is configured to transmit a registration request message including network function (NF) profile information of the UPF to a network repository function (NRF) entity, and to receive a registration response message from the NRF entity, wherein the NF profile information of the UPF entity may include UPF function information.

[0015] According to one embodiment of the present disclosure, in a wireless communication system, a network repository function (NRF) entity includes a transceiver; and at least one processor; wherein the at least one processor is configured to receive a registration request message including network function (NF) profile information of a user plane function (UPF) from a UPF entity, store the NF profile information, and transmit a registration response message to the UPF entity, wherein the NF profile information of the UPF entity includes UPF function information.

[0016] The present disclosure addresses signaling overhead and processing load issues in a wireless communication system and provides an efficient UPF service subscription procedure.

[0017] The present disclosure provides a design method for decomposition or modularization of a UPF (User Plane Function) and a method and device for effectively supporting registration / removal / search / update of a modularized UPF in NRF.

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

[0019] FIG. 1 illustrates the structure of a 5G network according to an embodiment of the present disclosure.

[0020] FIG. 2 illustrates an operation for subscribing to a UPF service (e.g., UPF Event Exposure service) according to an embodiment of the present disclosure.

[0021] FIG. 3 illustrates an operation for subscribing to a UPF service (e.g., UPF Event Exposure service) according to an embodiment of the present disclosure.

[0022] FIG. 4 illustrates a portion of a UE Requested PDU Session Establishment procedure according to an embodiment of the present disclosure.

[0023] FIG. 5 illustrates an operation for subscribing to a UPF service via UDM according to an embodiment of the present disclosure.

[0024] FIG. 6 illustrates an operation for subscribing to a UPF service via SMF according to an embodiment of the present disclosure.

[0025] FIG. 7 illustrates a flowchart for the operation of UDM according to an embodiment of the present disclosure.

[0026] FIG. 8 is a diagram illustrating the configuration of a network entity according to an embodiment of the present disclosure.

[0027] FIG. 9 illustrates an example of a modularized UPF design according to one embodiment of the present disclosure.

[0028] FIG. 10 illustrates an example of a deployment in which heavy UPF and light UPF are mixed according to one embodiment of the present disclosure.

[0029] FIG. 11 illustrates an example of a set of UPF instances for UPF functionality within UPF module information, which is an extension value of a UPF NF (Network Function) profile according to one embodiment of the present disclosure.

[0030] FIG. 12 illustrates a procedure for registering a newly created UPF instance with NRF according to one embodiment of the present disclosure.

[0031] FIG. 13 illustrates a procedure for deregistering a UPF instance from NRF when the UPF instance is removed according to one embodiment of the present disclosure.

[0032] FIG. 14 illustrates a procedure for updating changed NF profile information to NRF when NF profile information of a UPF instance is changed according to one embodiment of the present disclosure.

[0033] FIG. 15 illustrates a procedure for searching for a UPF instance via NRF according to one embodiment of the present disclosure.

[0034] Figure 16 illustrates the configuration of a terminal according to an embodiment of the present disclosure.

[0035] FIG. 17 illustrates the configuration of a base station or network entity according to an embodiment of the present disclosure.

[0036] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

[0037] In describing the embodiments herein, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0038] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0039] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is 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. Like reference numerals refer to like elements throughout the specification.

[0040] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0041] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0042] Here, the term '~ unit' used in the present embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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 '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.

[0043] In this disclosure, phrases such as "A / B", "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as "first", "second", or "first" or "second" may be used merely to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

[0044] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge. Terms used in the following description to identify a connection node, terms referring to network entities or NFs (network functions), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms that refer to objects having equivalent technical meanings may be used.

[0045] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0046] FIG. 1 illustrates the structure of a 5G network according to an embodiment of the present disclosure.

[0047] Referring to Figure 1, the network entities or network nodes that constitute the 5G network are described as follows.

[0048] (R)AN ((Radio) Access Network) (100) is an entity that performs wireless resource allocation of a terminal, and may be at least one of an eNode B, a Node B, a BS (Base Station), an NG-RAN (NextGeneration Radio Access Network), a 5G-AN, a wireless access unit, a base station controller, or a node on a network.

[0049] The terminal (105) may include a UE (User Equipment), an NG UE (NextGeneration UE), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, although the embodiments of the present disclosure will be described below using a 5G system as an example, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0050] As wireless communication systems evolve from 4G to 5G, a new core network, NextGen Core (NG Core) or 5GC (5G Core Network), is defined. This new core network virtualizes all existing network entities (NEs) into network functions (NFs). According to one embodiment of the present disclosure, a network function (NF) may refer to a network entity, a network component, or a network resource.

[0051] According to one embodiment of the present disclosure, 5GC may include NFs as illustrated in FIG. 1. Of course, the present invention is not limited to the example illustrated in FIG. 1, and 5GC may include more or fewer NFs than the number of NFs illustrated in FIG. 1.

[0052] An Access and Mobility Management Function (AMF) (110) may be a network function that manages access and mobility of a terminal (UE). For example, AMF may perform network functions such as registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0053] The SMF (Session Management Function) (115) may be a network function that manages a Packet Data Network (PDN) connection provided to a user equipment (UE). The PDN connection may be referred to as a Packet Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management functions through establishing, modifying, and releasing sessions and maintaining a tunnel between the UPF (131) and the RAN required for this, allocation and management of the IP (Internet protocol) address of the UE, selection and control of the user plane, control of traffic processing in the UPF (120), and control of collection of charging data.

[0054] PCF (Policy Control Function) (125) may be a network function that applies a mobile communication service provider's service policy, charging policy, and policy for PDU Session to a terminal.

[0055] Unified Data Management (UDM) (130) may be a network function that stores subscriber information. For example, UDM (130) may perform functions such as generating authentication information for 3GPP security, processing user identifiers (user IDs), managing a list of network functions supporting UE (105), and managing subscription information.

[0056] The Network Exposure Function (NEF) (135) may be a function that provides information about a terminal to a server outside the 5G network. Furthermore, the NEF may provide the function of storing information necessary for 5G network services in the UDR.

[0057] The UPF (User Plane Function) (120) may be a function that performs the role of a gateway that transmits user data (PDU) to a DN (Data Network). More specifically, the UPF may perform the role of processing data so that data transmitted by a terminal can be transmitted to an external network or data received from an external network can be transmitted to the terminal. For example, the UPF (131) may perform network functions such as serving as an anchor between radio access technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report creation, and buffering.

[0058] NRF (Network Repository Function) (140) can perform the function of discovering NF.

[0059] AUSF (Authentication Server Function) (145) can perform terminal authentication in 3GPP access networks and non-3GPP access networks.

[0060] NSSF (Network Slice Selection Function) (150) can perform the function of selecting a Network Slice Instance provided to a terminal.

[0061] DN (Data Network) (155) may be a data network through which terminals transmit and receive data in order to use a network operator's service or a third-party service.

[0062] The Application Function (AF) (160) is a control unit function within or outside the core network that can provide application services to subscribers. For example, this may be for a video streaming service. If the AF (160) is trusted, it can interact directly with the core network function, or if it is a third party, it can interact with the Network Equipment Function (NEF) (135). The Service Communication Proxy (SCP) (165) can provide various functions, ranging from simplifying the network topology by applying signal aggregation and routing to load balancing, overload handling, message parameter adjustment, and integration with legacy systems.

[0063] According to one embodiment of the present disclosure, a service subscription method is proposed for a network device or network function located inside or outside a 5G Core Network to use a UPF service (e.g., UPF event exposure service) provided by a UPF (user plane function).

[0064] FIG. 2 illustrates an operation for subscribing to a UPF service (e.g., UPF event exposure service) according to an embodiment of the present disclosure.

[0065] Figure 2 illustrates two methods defined for subscribing to a UPF service (e.g., a UPF event exposure service). The UPF event exposure service is an event exposure service defined in 3GPP for 5G systems, which allows UPF to expose relevant events to subscribed service consumers (e.g., NWDAF, local NEF, AF, etc.) when they occur.

[0066] Figure 2 illustrates a previously proposed service subscription method for a consumer NF (network function) (200) to use the UPF service provided by the UPF (220). UPF service subscription methods are broadly divided into an indirect subscription method, in which subscription is made through another NF (i.e., SMF), as illustrated in Figure 2(a), and a direct subscription method, in which subscription is made directly to the UPF, as illustrated in Figure 2(b).

[0067] In addition, the indirect subscription method illustrated in FIG. 2(a) is a method used when subscribing to a service for a specific UPF, such as a specific UE, a specific IP (internet protocol) flow, or a specific PDU (packet data unit) session. This is because the only NF that can identify a specific UPF is the SMF (210). Referring to FIG. 2(a), in step 230, the consumer NF (200) can transmit an Nsmf_EventExposure_Subscribe Request message to the SMF (210). In step 235, the SMF (210) can transmit an Nupf_EventExposure_Subscribe Request message to a specific UPF (220).

[0068] In addition, the direct subscription method illustrated in FIG. 2(b) refers to a method used when subscribing to a service for a general UPF rather than a specific UPF, such as any UE or any UPF. Referring to FIG. 2(b), in step 240, the consumer NF (220) may transmit a Nupf_EventExposure_Subscribe Request message to the UPF (220).

[0069] FIG. 3 illustrates an operation for subscribing to a UPF service (e.g., a UPF event exposure service) according to an embodiment of the present disclosure. FIG. 3 illustrates a method for subscribing to a UPF service via SMF.

[0070] In step 301, a UPF service consumer NF (or, UPF event consumer NF) (300) requests information on an SMF responsible for a specific UPF from a UDM (310) using a Nudm_UECM_Get service (message). In one embodiment, the UPF service consumer NF (300) may be an NWDAF. For convenience, the UPF service consumer NF may be referred to as a consumer NF hereinafter. The Nudm_UECM_Get message may set an SMF for the UE ID, DNN, S-NSSAI, and the NF type value, which is the type of NF information to be requested, responsible for the UPF to be found.

[0071] In step 302, UDM (310) transmits the responsible SMF information to consumer NF (300) through the Nudm_UECM_Get response message.

[0072] In step 303, the consumer NF (300) may send an Nsmf_EventExposure_Subscribe message to the responsible SMF to subscribe to the UPF service. This message may include at least one of the following information:

[0073] - Notification Target Address (UPF event consumer address), Notification Correlation Information.

[0074] - Indication of UPF Event Exposure Service and Target subscription UPF Event Id.

[0075] - Event Filter Information: S-NSSAI, DNN, DNAI, UPF Id, Traffic Description for the target traffic (eg Application Id), Area of ​​Interest, SSID / BSSID.

[0076] - Target of Event Reporting: a UE.

[0077] - Reporting suggestion information.

[0078] - Target Subscription information: Type of Measurement and granularity of the information requested.

[0079] In step 304a / 304b, the SMF (330) can identify, based on the parameters of the received message, the UPF responsible for a specific UE, a specific PDU Session, and a specific IP Flow among the UPFs it is responsible for. The SMF (330) can include the information received from the consumer NF (300) in an N4_Session_Modification message or a Nupf_EventExposure_Subscribe message and transmit it to the responsible UPF (340) in order to subscribe to the UPF service requested by the consumer NF (300). At this time, which of the two messages above is used may vary depending on the type of UPF service requested.

[0080] In step 305, if there is data to be transmitted to the UPF event consumer NF (300) related to the service requested by the UPF (340), the UPF (340) can include this in the Nupf_EventExposure_Notify message and transmit it to the consumer NF (300).

[0081] In order to solve the problems of the signaling overhead of the UPF service indirect subscription procedure using SMF and the load imposed on the SMF (in particular, changing the subscription message to an N4 Session message), the present invention proposes a UPF service indirect subscription procedure using UDM.

[0082] FIG. 4 illustrates a portion of a UE Requested PDU Session Establishment procedure according to an embodiment of the present disclosure.

[0083] Steps 401 to 419 illustrated in FIG. 4 may include a requested PDU session establishment procedure requested by the UE (400) as presented in 3GPP TS 23.502.

[0084] In step 416c, if the request type is an initial request, i.e., a request to create a new PDU Session, and information about the corresponding PDU Session has not yet been registered in the UDM (420), the SMF (410) may register information about the corresponding PDU Session in the UDM using the Nudm_UECM_Registration message. This message may include at least one of the following information: SUPI, DNN, S-NSSAI of HPLMN, PDU Session ID, SMF Identity, Serving Node PLMN ID, and [NID].

[0085] In addition, the Nudm_UECM_Registration of step 416c may additionally include at least one of the following: UE IP address (IPv4 / IPv6), UE MAC address, and (Anchor) UPF Information (UPF IP Address, UPF NF Id). The Nudm_UECM_Registration of step 416c may further include other information in addition to the information listed above.

[0086] Table 1 shows the UE context in SMF data added in the UDM through the Nudm_UECM_Registration message of FIG. 4.

[0087] UE context in SMFdataSUPIKey.PDU Session Id(s)List of PDU Session Id(s) for the UE.For emergency PDU Session Id:Emergency InformationThe SMF+PGW-C FQDN for emergency session used for interworking with EPC.For each non-emergency PDU Session Id:DNNDNN for the PDU Session.SMFAllocated SMF for the PDU Session. Includes SMF IP Address and SMF NF Id.SMF+PGW-C FQDNThe S5 / S8 SMF+PGW-C FQDN used for interworking with EPS (see NOTE 5).PCF IDThe PCF ID serving the PDU Session / PDN Connection.UE IP addressIt can be either IPv4 address or IPv6 Prefix.UE MAC addressMAC address of UEUPFAllocated (Anchor) UPF for the PDU Session. Includes UPF IP address and UPF NF Id.

[0088] Figure 5 illustrates an operation for subscribing to a UPF service via UDM according to an embodiment of the present disclosure. In step 501, a consumer NF (500) may transmit a Nudm_EventExposure_Subscribe Request message to a UDM (510) to subscribe to a UPF service. This message may include at least one of the following information:

[0089] - Notification Target Address (UPF event consumer address), Notification Correlation Information.

[0090] - Indication of UPF Event Exposure Service and Target subscription UPF Event Id.

[0091] - Event Filter Information: S-NSSAI, DNN, DNAI, Traffic Description for the target traffic (eg, Application Id), Area of ​​Interest, SSID / BSSID.

[0092] - Target of Event Reporting: a UE.

[0093] - Reporting suggestion information.

[0094] - Target Subscription information: Type of Measurement and granularity of the information requested.

[0095] In step 502, UDM (510) can specify a UPF based on UE context in SMF data information and transmit a Nupf_EventExopsure_Subscribe Request message including the information received from consumer NF (500) in step 501 to the corresponding UPF (520).

[0096] If service-related data requested by the consumer NF (500) to the UPF (520) occurs in step 503, the UPF (520) can include this in the Nupf_EventExposure_Notify message and transmit it to the consumer NF (500).

[0097] FIG. 6 illustrates an operation for subscribing to a UPF service via SMF according to an embodiment of the present disclosure. FIG. 6 illustrates a method for subscribing to a UPF service using SMF when UPF information is not included in the UE context in SMF data of UDM (610).

[0098] In step 601, consumer NF (600) may transmit a Nudm_EventExposure_Subscribe Requeest message to UDM (610) to subscribe to the UPF service. The Nudm_EventExposure_Subscribe Request message may include at least one of the following information.

[0099] - Notification Target Address (UPF event consumer address), Notification Correlation Information.

[0100] - Indication of UPF Event Exposure Service and Target subscription UPF Event Id.

[0101] - Event Filter Information: S-NSSAI, DNN, DNAI, Traffic Description for the target traffic (eg, Application Id), Area of ​​Interest, SSID / BSSID.

[0102] - Target of Event Reporting: a UE.

[0103] - Reporting suggestion information.

[0104] - Target Subscription information: Type of Measurement and granularity of the information requested.

[0105] In step 602, the UDM (610) searches for UE context in SMF data information to identify the UPF for which the consumer NF (600) wishes to subscribe to the UPF service, and if it identifies that there is no UPF information, it can generate an Nsmf_EventExpsure_Subscribe Request message including the information received from the consumer NF in step 601 and transmit it to the SMF (630) in charge of the UPF for which the consumer NF (600) wishes to subscribe to the UPF service.

[0106] In step 603a / 603b, the SMF (630) can identify, based on the parameters of the received message, the UPF responsible for a specific UE, a specific PDU Session, and a specific IP Flow among the UPFs it is responsible for. The SMF (630) can include the information received from the consumer NF (600) in an N4_Session_Modification message or a Nupf_EventExposure_Subscribe Request message and transmit it to the corresponding UPF (620) in order to subscribe to the UPF service requested by the consumer NF (600). At this time, which of the two messages above is used may vary depending on the type of UPF service requested.

[0107] If service-related data requested by the consumer NF (600) to the UPF (620) occurs in step 604, the UPF can include it in the Nupf_EventExposure_Notify message and transmit it to the consumer NF (600).

[0108] FIG. 7 illustrates a flowchart for the operation of UDM according to an embodiment of the present disclosure.

[0109] In one embodiment, in step 710, the UDM may receive a registration message from a session management function (SMF). The UPF-related information may include at least one of a UPF Internet Protocol (IP) address and a UPF Network Function (NF) identifier (ID). The registration message may include at least one of a User Equipment (UE) Internet Protocol (IP) address and a UE Media Access Control (MAC) address. In one embodiment, the UDM may determine a UPF associated with a specific UE based on the UE IP address or the UE MAC address.

[0110] In one embodiment, the UPF (user plane function) related information may be stored in the UE context in SMF data of the UDM. The service related information may include at least one of a UPF event service indicator, a UPF event identifier, and event filter information. The first service subscription request message may include a Nudm_EventExposure_Subscribe Request message, and the second service subscription request message may include a Nupf_EventExposure_Subscribe Request message.

[0111] At step 720, the UDM may receive a first service subscription request message from a network function (NF). In one embodiment, the NF may include a network data analytics function (NWDAF).

[0112] In step 730, the UDM may determine a UPF based on the UPF-related information contained in the registration message, if any, and the service-related information contained in the first service subscription message. In step 740, the UDM may transmit a second service subscription request message including the service-related information to the determined UPF.

[0113] In one embodiment, if the UPF-related information is not stored, the UDM may determine a second SMF to support UPF subscription based on the service-related information, and transmit a third service subscription request message to the second SMF.

[0114] FIG. 8 is a diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.

[0115] A network entity according to one embodiment of the present disclosure may include a processor (820) that controls the overall operation of the network entity, a transceiver (800) including a transmitter and a receiver, and a memory (810). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than those illustrated in FIG. 8.

[0116] According to one embodiment of the present disclosure, the transceiver (800) can transmit and receive signals with at least one of other network entities or terminals. The signals transmitted and received with at least one of the other network entities or terminals may include control information and data.

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

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

[0119] The at least one processor may receive a registration message from a first session management function (SMF). The at least one processor may control to receive a first service subscription request message from a network function (NF). If UPF-related information included in the registration message is stored, the at least one processor may determine a UPF based on the UPF-related information and the service-related information included in the first service subscription message. The at least one processor may control to transmit a second service subscription request message including the service-related information to the determined UPF.

[0120] In one embodiment, a UDM entity characterized in that the UPF-related information includes at least one of a UPF IP (internet protocol) address and a UPF NF (network function) ID (identifier).

[0121] In one embodiment, the registration message may include at least one of a user equipment (UE) Internet protocol (IP) address and a UE media access control (MAC) address.

[0122] In one embodiment, the UPF related information may be stored in the UE context in SMF data of the UDM.

[0123] In one embodiment, the service-related information may include at least one of an indicator of a UPF event service, a UPF event ID (identifier), and event filter information.

[0124] In one embodiment, the at least one processor may determine a UPF associated with a specific UE based on the UE IP address or the UE MAC address. In one embodiment, the NF may include a network data analytics function (NWDAF).

[0125] In one embodiment, the at least one processor may be configured to determine a second SMF to support UPF subscription based on the service-related information when the UPF-related information is not stored, and transmit a third service subscription request message to the second SMF. In one embodiment, the first service subscription request message may include a Nudm_EventExposure_Subscribe Request message. In one embodiment, the second service subscription request message may include a Nupf_EventExposure_Subscribe Request message.

[0126] According to one embodiment of the present disclosure, a method for subscribing to a service of unified data management (UDM) in a wireless communication system includes: receiving a registration message from a first session management function (SMF); receiving a first service subscription request message from a network function (NF); determining a UPF based on the UPF-related information included in the registration message and the service-related information included in the first service subscription message, when UPF-related information included in the registration message is stored; and transmitting a second service subscription request message including the service-related information to the determined UPF.

[0127] According to one embodiment of the present disclosure, the UPF-related information may include at least one of a UPF IP (internet protocol) address and a UPF NF (network function) ID (identifier).

[0128] In one embodiment, the registration message may include at least one of a user equipment (UE) Internet protocol (IP) address and a UE media access control (MAC) address.

[0129] In one embodiment, the UPF related information may be stored in the UE context in SMF data of the UDM.

[0130] In one embodiment, the service-related information may include at least one of an indicator of a UPF event service, a UPF event ID (identifier), and event filter information.

[0131] In one embodiment, determining the UPF may include determining a UPF associated with a particular UE based on the UE IP address or the UE MAC address.

[0132] In one embodiment, the NF may include a network data analytics function (NWDAF).

[0133] In one embodiment, the method may include an operation of determining a second SMF to support UPF subscription based on the service-related information when the UPF-related information is not stored; and an operation of transmitting a third service subscription request message to the second SMF.

[0134] In one embodiment, the first service subscription request message may include a Nudm_EventExposure_Subscribe Request message, and the second service subscription request message may include a Nupf_EventExposure_Subscribe Request message.

[0135] According to one embodiment of the present disclosure, a unified data management (UDM) entity for service subscription in a wireless communication system includes a transceiver; and a processor, wherein the processor is configured to receive a registration message from a first session management function (SMF), receive a first service subscription request message from a network function (NF), determine a UPF based on the UPF-related information included in the registration message and the service-related information included in the first service subscription message when UPF-related information included in the registration message is stored, and transmit a second service subscription request message including the service-related information to the determined UPF.

[0136] In one embodiment, a UDM entity characterized in that the UPF-related information includes at least one of a UPF IP (internet protocol) address and a UPF NF (network function) ID (identifier).

[0137] According to one embodiment of the present disclosure, the present disclosure provides a design method for decomposing or modularizing a UPF (User Plane Function) and a method and device for supporting effective registration / removal / search / update of a modularized UPF in an NRF.

[0138] According to one embodiment of the present disclosure, the present disclosure proposes a design method for a modularized UPF formed by a plurality of modules and functions (hereinafter referred to as modules), and a method for registering, searching, removing, and updating a created UPF instance in NRF when a modularized UPF instance is created.

[0139] [UPF Module Design]

[0140] FIG. 9 illustrates an example of a modularized UPF design / design according to one embodiment of the present disclosure.

[0141] The services provided by UPF can be divided into mandatory functionality and optional functionality. Mandatory functionality may be functions required for services that UPF must provide, as defined in the standard, while optional functionality may be functions required to provide additional services beyond the UPF's functions, as defined in the standard. For example, UPF must receive user packets from DNs and transmit them to UEs, and receive user packets from UEs and transmit them to DNs. A packet processing module may be required for UPF to receive user packets from DNs and transmit them to UEs, and receive user packets from UEs and transmit them to DNs. However, shallow / deep packet inspection, which inspects user packets received from UEs or DNs, is not defined in the standard as a service / function that UPF must provide.

[0142] When UPF is modularized by function, the resources for each module can be expanded / contracted, thereby expanding the flexibility of UPF resource provision. In other words, since UPF is modularized by function, the resources for each module of UPF can be expanded / contracted, thereby expanding the flexibility of resource provision for UPF. Furthermore, since non-essential additional functions can be added / deleted from UPF at any time as needed, it can be offered at a lower price compared to UPF that has all the functions, including essential and additional functions. To achieve this, each module must be able to operate independently without affecting the other.

[0143] In the present disclosure, a UPF that modularizes all functions according to the module design, such as the UPF illustrated on the left side of FIG. 9, and includes only essential functions excluding additional functions, is defined as a Light UPF. That is, in the present disclosure, a UPF that supports only essential functions excluding additional functions and in which the functions supported by the UPF are modularized is defined as a Light UPF. In addition, in the present disclosure, a UPF that does not modularize the functions supported by the UPF, such as the UPF illustrated on the right side of FIG. 9, and includes both essential functions and additional functions, is defined as a Heavy UPF.

[0144] FIG. 10 illustrates an example of a deployment in which a Heavy UPF and a Light UPF are mixed according to one embodiment of the present disclosure.

[0145] In an environment where only Heavy UPF is deployed, data transmission and reception with the DN can be performed using the same UPF regardless of the requirements of the service data flow used by the UE. In other words, when only Heavy UPF is deployed, the same UPF can be used for data transmission and reception between the UE and the DN regardless of the requirements of the service data flow provided to the UE. However, in an environment where Light UPF is used, Light UPF, which provides different additional functions, can be selected depending on the requirements of the UE service data flow. For example, in the case of a service data flow for a banking service, data communication between the UE and the DN is performed using Light UPF, which provides a firewall function because security is important, and in the case of a service data flow for a video streaming service, data communication between the UE and the DN is performed using Light UPF, which provides a caching function that can reduce transmission delay.

[0146] When various service data flows exist, as in the example of Fig. 10, a Consumer Network Function (NF) must search for a Light UPF suitable for each service data flow and handle the service data flow. The present disclosure proposes a method for a Consumer Network Function (NF) to search for a Light UPF suitable for a service data flow. The method for a Consumer NF to search for a Light UPF suitable for a service data flow proposed in the present disclosure may include at least one of a series of procedures for registering, removing, searching, and updating a Light UPF instance in an NRF.

[0147] According to one embodiment of the present disclosure, a generic NF profile used to register an NF Instance with NRF may include at least one of the following parameters:

[0148] (1) NF (Network Function) instance ID (Identifier)

[0149] (2) NF type

[0150] (3) Network Slice-related identifier(s). Examples include Single-Network Slice Selection Assistance Information (S-NSSAI) and Network Slice Instance Identifier (NSI ID).

[0151] (4) Fully Qualified Domain Name (FQDN) or Internet Protocol (IP) address of NF

[0152] (5) NF capacity information

[0153] (6) NF priority information

[0154] (7) NF load information

[0155] According to one embodiment of the present disclosure, an NF profile for registering a UPF Instance to NRF may include at least one of the following parameters.

[0156] (1) NAT (Network Address Translation) information

[0157] (2) The range of IP addresses the NAT uses for the DN. For example, this may include public IP addresses.

[0158] (3) List of (S-NSSAI, DNN)

[0159] (4) UE IPv4 Address Ranges and / or IPv6 Prefix Range(s) per (S-NSSAI, DNN)

[0160] (5) Supported UPF event exposure service and supported Event ID(s)

[0161] eg local notification of QoS Monitoring to AF

[0162] (6) IP address range, for example, DNAI for UPF, etc.

[0163] According to one embodiment of the present disclosure, in order to register a Light UPF Instance with NRF, at least one parameter among the following parameters (UPF Module Information) may be extended / added to the UPF NF profile.

[0164] A. UPF Module Information

[0165] List of functionality components currently served by Ai UPF

[0166] Ai1. ID(s) of set of UPF Instances for UPF functionality

[0167] Ai1.A. Format of ID: Type of functionality set: Number of additional functionality: Unique ID in NRF

[0168] Ai2. Type of functionality set

[0169] Ai3. Name of functionality

[0170] Ai3.A. [Mandatory] Data Storage, Data Processing, Packet Processing, Packet Buffer, Policy Rule Enforcement, Traffic Usage Reporting, Traffic Verification, Quality of Service (QoS) Handling

[0171] Ai3.Ai The above functions can be grouped as a set of mandatory functionalities.

[0172] Ai3.B. [Optional] NAT, Domain Name System (DNS) snooping, firewall, traffic optimization, shallow / deep packet inspection

[0173] Ai4. Capacity and load information of module

[0174] Ai5. Flexibility of modules (scale up or scale down)

[0175] Ai6. Other information

[0176] Ai6.A. For example, there may be policy, authorization, and so on.

[0177] A.ii. List of Addable Functionality Components

[0178] A.ii.1. Supportable functionalities that are currently turned off due to no service request

[0179] According to one embodiment of the present disclosure, UPF module information (Module Information) may indicate services that a Light UPF Instance can provide, i.e., module (functionality) information. According to one embodiment of the present disclosure, UPF Module Information may include information about a list of functionality components currently served by UPF and information about a list of addable functionality components. The list of functionality components is a list of activated services, and the addable functionality components is a list of deactivated services because there is currently (or at a specific point in time) no service data flow requesting the service. That is, when a service data flow requesting the service occurs, the addable functionality can be activated.

[0180] At least one parameter that may be included in each functionality component according to one embodiment of the present disclosure is described below.

[0181] The ID(s) of a set of UPF instances for a UPF function are a set of IDs configured by grouping UPF instances having a specific functionality combination. The ID(s) of a set of UPF instances for a UPF function are proposed to quickly search for a Light UPF Instance including a specific functionality combination that is frequently requested, since a specific functionality combination is frequently requested. According to one embodiment of the present disclosure, the ID(s) of a set of UPF instances for a UPF function may be configured in the following format.

[0182] Format of ID: Type of functionality set: Number of additional functionality: Unique ID in NRF.

[0183] According to one embodiment of the present disclosure, the type of functionality set is a value that identifies a specific functionality combination.

[0184] According to one embodiment of the present disclosure, the number of additional functionality may be the number of optional functionality excluding a specific functionality combination that a UPF Instance can provide.

[0185] According to one embodiment of the present disclosure, the Unique ID in NRF may be a value that allows each Light UPF Instance to be uniquely identified in NRF.

[0186] According to one embodiment of the present disclosure, the name of functionality may be a functionality provided by the Light UPF Instance, and at least one of the following parameters may be included in the name of functionality.

[0187] [Mandatory] Data Storage, Data Processing, Packet Processing, Packet Buffer, Policy Rule Enforcement, Traffic Usage Reporting, Traffic Verification, Quality of Service (QoS) Handling

[0188] [Optional] NAT, Domain Name System (DNS) snooping, firewall, traffic optimization, shallow / deep packet inspection

[0189] According to one embodiment of the present disclosure, the capacity and load information of the module may include capacity and load information of functionality.

[0190] According to one embodiment of the present disclosure, the flexibility of a module (scale up or scale down) may include information about the extent to which the capacity of functionality can be increased and decreased.

[0191] According to one embodiment of the present disclosure, functional components may further include various additional values ​​for UPF functionality in addition to the information / parameters described above. For example, functional components may further include policy or authorization information for using UPF functionality.

[0192] FIG. 11 illustrates an example of a set of UPF instances for UPF functionality within UPF module information, which is an extension value of a UPF NF (Network Function) profile, according to an embodiment of the present disclosure. That is, FIG. 11 illustrates an example of a set of UPF instances for UPF functionality within UPF module information, which is a parameter added to a UPF NF (Network Function) profile.

[0193] According to one embodiment of the present disclosure, four Light UPF Instances may be included in a set, as illustrated in FIG. 11. Each of the four Light UPF Instances included in the set may commonly include a Firewall module and a Deep Packet Inspection module among optional modules. The Firewall module and the Deep Packet Inspection module may be UPF modules frequently requested in connection with service data flows requesting financial services.

[0194] That is, Light UPF Instances that provide a combination of modules frequently requested by service data flows can be configured as a single set. According to one embodiment of the present disclosure, a single UPF Instance can also be included in another set. That is, multiple Set IDs can be assigned to a single UPF Instance.

[0195] According to one embodiment of the present disclosure, a Set ID may be defined in the following format: type of functionality set: number of additional functionality: unique ID in NRF.

[0196] Referring to FIG. 11, a Light UPF that includes only a Firewall module and a Deep Packet Inspection module may be assigned a Set ID such as Firewall / DPI (corresponding to the type of feature set): 0 (corresponding to the number of additional features): 12345 (corresponding to a unique ID in NRF).

[0197] The set ID described with reference to FIG. 11 is only one example among various examples that can express a set of UPF instances, and it is obvious that configuring the set ID in various other formats is also included in the scope of the technical idea proposed in the present disclosure.

[0198] According to one embodiment of the present disclosure, in FIG. 11, when a Session Management Function (SMF) requests an NRF for a list of Light UPF Instances that can provide Firewall and Deep Packet Inspection (DPI) functions for service data flow, the NRF can provide the SMF with a list of UPF Instances by checking only the Set ID. If there is no Set ID, the NRF must check all functionality names in the functionality components of all UPF Instances, which may take a long time to search for UPF Instances. In addition, according to one embodiment of the present disclosure, the SMF can select a UPF Instance by checking information on additional functionality other than the requested functionality included in the Set ID of each UPF Instance. According to one embodiment of the present disclosure, the information on the additional functionality may be configured in a form such as a number.

[0199] According to one embodiment of the present disclosure, since the fewer the number of additional functions provided by a UPF, the higher the probability that the service data flow load is lower, the SMF may select a Light UPF with a lower load based on information about the additional functions. In this case, the SMF may select a Light UPF with a smaller number of additional functions based on the number of additional additional functions supported by the UPF, but at least one other element of the UPF NF profile may be considered in the SMF's selection of the Light UPF.

[0200] FIG. 12 illustrates a procedure for registering a newly created UPF instance with NRF according to one embodiment of the present disclosure. In FIG. 12 , the UPF may be a light UPF.

[0201] According to one embodiment of the present disclosure, in step 1220, UPF (1200) may generate a request message to request registration of itself to NRF (1210) and transmit the generated request message to NRF (1210). At this time, the request message may be an Nnrf_NFManagement_NFRegister Request message. The generated request message may include a UPF NF profile. In addition, the NF profile may include UPF Module Information.

[0202] According to one embodiment of the present disclosure, in step 1230, the NRF (1210) can verify and store the NF profile included in the request message received from the UPF (1200), and mark the UPF (1200) that transmitted the request message as a Light UPF in order to distinguish the UPF (1200) from a Heavy UPF. In addition, based on information about the list of functionality components included in the UPF Module Information, the NRF assigns ID(s) of a set of UPF instances to the UPF (1200) that transmitted the request message, and updates the Set ID assigned to the UPF (1200) that transmitted the request message in the UPF Module Information table. That is, the Set ID assigned to the UPF (1200) that transmitted the request message can be added to the UPF Module Information table.

[0203] According to one embodiment of the present disclosure, in step 1240, the NRF (1210) may transmit an Acknowledgement to the UPF (1200) that transmitted the request message through a response message. The response message may be Nnrf_NFManagement_NFRegister response. The response message may include an ID(s) of a set of UPF instances for UPF functionality that the NRF (1210) allocated to the UPF (1200) that transmitted the request message.

[0204] FIG. 13 illustrates a procedure for deregistering a UPF instance from NRF when the UPF instance is removed, according to one embodiment of the present disclosure.

[0205] According to one embodiment of the present disclosure, in step 1320, UPF (1300) may transmit a request message to NRF (1310) to request deregistration of itself. The request message may be an Nnrf_NFManagement_NFDeregister Request message.

[0206] According to one embodiment of the present disclosure, in step 1330, the NRF (1310) may record that the UPF Instance associated with the UPF (1300) that transmitted the request message is no longer valid, and may delete the NF profile associated with the UPF (1300) that transmitted the request message. In addition, the ID(s) of the set of UPF instances for UPF functionality of the UPF (1300) that transmitted the request message may be deleted from the UPF Module Information table.

[0207] According to one embodiment of the present disclosure, in step 1340, the NRF (1310) may transmit an Acknowledgement to the UPF (1300) that transmitted the request message requesting deregistration through a response message. The response message may be an Nnrf_NFManagement_NFDeregister response message.

[0208] FIG. 14 illustrates a procedure for updating changed NF profile information to NRF when NF profile information of a UPF instance is changed, according to one embodiment of the present disclosure.

[0209] According to one embodiment of the present disclosure, in step 1420, UPF (1400) may transmit a request message to NRF (1410) to notify NRF (1410) of a change in its NF profile. The request message may be an Nnrf_NFManagement_NFUpdate Request message.

[0210] According to one embodiment of the present disclosure, with respect to UPF Module Information, when a functionality included in a list of functionality components or a list of addable functionality components is activated by a new service data flow, or when a previously activated functionality is deactivated, the UPF NF Profile may be updated. In addition, changes related to UPF Module Information may be updated in the NRF (1410).

[0211] According to one embodiment of the present disclosure, in step 1430, the NRF (1410) may assign ID(s) of a set of UPF instances for UPF functionality or delete existing ID(s) of a set of UPF instances for UPF functionality, depending on activation or deactivation of additional functionality of the UPF (1400) that transmitted the request message, and the NRF (1410) may update the newly assigned or deleted ID(s) of a set of UPF instances for UPF functionality in the UPF Module Information table.

[0212] According to one embodiment of the present disclosure, in step 1440, the NRF (1410) may transmit an Acknowledgement for an NF profile update to the UPF (1400) that transmitted the request message through a response message. The response message may be an Nnrf_NFManagement_NFUpdate response message. The response message may include a value of a set of UPF Instances for UPF functionality newly assigned by the NRF (1410) or a value of a set of UPF Instances for UPF functionality deleted by the NRF (1410).

[0213] FIG. 15 illustrates a procedure for searching for a UPF instance via NRF according to one embodiment of the present disclosure.

[0214] According to one embodiment of the present disclosure, in step 1520, a Consumer NF (1500) requiring a UPF Instance service may transmit a request message to the NRF (1510) for requesting UPF Instance discovery to the NRF (1510). The request message may be an Nnrf_NFDiscovery_Request message. The request message may include information about a list of UPF functionalities of the UPF transmitting the request message. In addition, each UPF functionality may be provided with (mandatory / optional) option and priority information. At this time, the optional UPF Functionality cannot have a higher priority than the mandatory UPF Functionality.

[0215] According to one embodiment of the present disclosure, in step 1530, NRF (1510) may perform an authorization check of a request message (or Nnrf_NFDiscovery_Request message) transmitted by Consumer NF (1500).

[0216] According to one embodiment of the present disclosure, in step 1540, if the Authorization check performed in step 1530 is passed, the NRF (1510) may search the UPF Module Information table based on information about the list of UPF functionalities included in the request message (or Nnrf_NFDiscovery_Request message) and transmit a response message including a list of NF profiles of UPF Instances that satisfy the list of UPF functionalities requested by the Consumer NF (1500) to the Consumer NF (1500). The response message may be an Nnrf_NFDiscovery_Request_Response message.

[0217] FIG. 16 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0218] A terminal according to one embodiment of the present disclosure may include a processor (920) that controls the overall operation of the terminal, a transceiver (900) including a transmitter and a receiver, and a memory (910). Of course, the terminal is not limited to the above example, and the terminal may include more or fewer components than those illustrated in FIG. 16.

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

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

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

[0222] FIG. 17 is a diagram illustrating the configuration of a base station or network entity according to an embodiment of the present disclosure.

[0223] A network entity according to one embodiment of the present disclosure may include a processor (1720) that controls the overall operation of the network entity, a transceiver (1700) including a transmitter and a receiver, and a memory (1710). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than those illustrated in FIG. 17.

[0224] According to one embodiment of the present disclosure, the transceiver (1700) can transmit and receive signals with at least one of other network entities or terminals. The signals transmitted and received with at least one of the other network entities or terminals may include control information and data.

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

[0226] According to one embodiment of the present disclosure, the memory (1710) can store data such as basic programs, application programs, and configuration information for the operation of a network entity. In particular, the memory (1710) provides the stored data upon request from the processor (1720).

[0227] The memory (1710) may be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there may be a plurality of memories (1710). In addition, the processor (1720) may perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (1710).

[0228] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made within a scope that does not detract from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

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

[0230] The various components and modules of the entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or 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.

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

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

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

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

[0235] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the following claims but also by equivalents of the scope of the claims. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, each of the above embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

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

Claims

1. In a method of a UPF (user plane function) entity in a wireless communication system, A step of transmitting a registration request message including NF (network function) profile information of UPF to an NRF (network repository function) entity; and comprising the step of receiving a registration response message from the NRF entity; A method characterized in that the NF profile information of the above UPF entity includes UPF function information.

2. In paragraph 1, the UPF function information is: A method characterized by including at least one of NAT (network address translation) function information, packet inspection function information, firewall-related information, and DNS (domain name system) snooping-related information.

3. In paragraph 1, When the NF profile information of the UPF entity is changed, a step of transmitting an update request message to the NRF entity notifying a change in the NF profile information of the UPF entity; and A step of receiving an update response message from the above NRF entity; A method characterized in that the changed NF profile information of the above UPF entity includes changed UPF function information.

4. In paragraph 1, the UPF function information is: A method characterized by being used for discovery of UPF entities.

5. A method according to claim 4, characterized in that the NAT function information included in the UPF function information is used for discovery of the UPF entity.

6. In a method of NRF (network repository function) entity in a wireless communication system, A step of receiving a registration request message including NF (network function) profile information of a UPF (user plane function) from a UPF (user plane function) entity; A step of storing the above NF profile information; and comprising the step of transmitting a registration response message to the above UPF entity; A method characterized in that the NF profile information of the above UPF entity includes UPF function information.

7. In paragraph 6, the UPF function information is: A method characterized by including at least one of NAT (network address translation) function information, packet inspection function information, firewall-related information, and DNS (domain name system) snooping-related information.

8. In paragraph 6, When the NF profile information of the UPF entity is changed, a step of receiving an update request message from the UPF entity notifying a change in the NF profile information of the UPF entity; and a step of updating the above NF profile information; and comprising the step of transmitting an update response message to the above UPF entity; A method characterized in that the changed NF profile information of the above UPF entity includes changed UPF function information.

9. In paragraph 6, A step of receiving a request message for discovery of a UPF entity from a consumer NF entity; comprising the step of transmitting a response message to the above consumer NF entity; The request message for discovery of the above UPF entity includes the requested UPF capability information, A method characterized in that the response message includes a list of profiles of at least one UPF entity that supports at least one of the requested UPF capability information.

10. A method according to claim 9, characterized in that the NAT (network address translation) function information included in the requested UPF function information is used for discovery of the UPF entity.

11. In a wireless communication system, for a UPF (user plane function) entity, Transmitter and receiver; and comprising at least one processor; wherein the at least one processor comprises: Send a registration request message containing the NF (network function) profile information of the UPF to the NRF (network repository function) entity, and configured to receive a registration response message from the above NRF entity, A UPF entity characterized in that the NF profile information of the above UPF entity includes UPF function information.

12. In paragraph 11, the UPF function information is: A UPF entity characterized by including at least one of NAT (network address translation) function information, packet inspection function information, firewall-related information, and DNS (domain name system) snooping-related information.

13. In the 11th paragraph, at least one processor, If the NF profile information of the above UPF entity is changed, an update request message is transmitted to the NRF entity to notify the change of the NF profile information of the above UPF entity, and configured to receive an update response message from the above NRF entity, The changed NF profile information of the above UPF entity is characterized by including changed UPF function information, and A UPF entity, characterized in that the UPF function information is used for discovery of the UPF entity, and the NAT function information included in the UPF function information is used for discovery of the UPF entity.

14. In a wireless communication system, for the NRF (network repository function) entity, Transmitter and receiver; and comprising at least one processor; wherein the at least one processor comprises: Receive a registration request message containing NF (network function) profile information of UPF from a UPF (user plane function) entity, Store the above NF profile information, and configured to send a registration response message to the above UPF entity, An NRF entity characterized in that the NF profile information of the above UPF entity includes UPF function information.

15. In paragraph 14, the UPF function information is: An NRF entity characterized by including at least one of NAT (network address translation) function information, packet inspection function information, firewall-related information, and DNS (domain name system) snooping-related information.

Images