N4 session context update method and device considering UPF module

Abstract

A method performed by a user plane function (UPF) entity in a wireless communication system according to an embodiment of the present disclosure comprises the steps of: receiving, from a session management function (SMF) entity, an N4 session establishment request message including a packet detection rule (PDR) and a packet functionality rule (PFR) corresponding to the PDR; determining at least one UPF function required to be applied to a service data flow on the basis of the PDR and the PFR; and transmitting the service data flow to which the at least one UPF function is applied, wherein the PFR includes information on the at least one UPF function required to be applied to the service data flow.

Description

Method and device for updating N4 SESSION CONTEXT considering UPF module

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for updating an N4 Session Context when a User Plane Function (UPF) is mudule-ized.

[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 band, such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band (Above 6GHz), also called millimeter wave (mmWave), such as 28GHz and 39GHz. 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 ultra-low latency 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 ultra-wideband services (eMBB: enhanced Mobile Broadband), ultra-reliable / ultra-low-latency communications (URLLC: Ultra-Reliable Low-Latency Communications), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO (Massive MIMO) to alleviate 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 sub-carrier 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 codes for reliable transmission of control information, L2 pre-processing, and specific services. Standardization has been progressed for network slicing, which provides specialized, dedicated networks.

[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 (IIoT: Industrial Internet of Things) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) to provide 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) to simplify random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture: SBA, Service-based Interface: SBI) 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] When such 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, which will require enhanced functions and performance of 5G mobile communication systems and integrated operation of 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 antennas, and large-scale antennas, 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, and AI (Artificial Intelligence) from the design stage and internalize end-to-end AI support functions to realize system optimization, and ultra-high-performance communication and computing resources to realize services with complexity that exceeds the limits of terminal computing capabilities. It could serve as a basis for the development of next-generation distributed computing technologies.

[0008] As described above and with the development of mobile communication systems, various services have become available, and methods for effectively providing these services are required.

[0009] The present disclosure provides a method and device for effectively updating an N4 Session Context in a wireless communication system.

[0010] Based on the discussion described above, the present disclosure provides a method for processing a control signal in a wireless communication system, which may include: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0011] The disclosed embodiment provides a device and method for effectively updating an N4 Session Context in a wireless communication system.

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

[0013] FIG. 2 illustrates an example of a UPF module according to one embodiment of the present disclosure.

[0014] FIG. 3 illustrates an example of deploying Light UPF and Heavy UPF according to one embodiment of the present disclosure.

[0015] FIG. 4 illustrates a traffic filter that classifies service data flows by type according to one embodiment of the present disclosure.

[0016] FIG. 5a and FIG. 5b illustrate a flowchart of a PDU (protocol data unit) Session creation procedure according to one embodiment of the present disclosure.

[0017] Figure 6 illustrates the configuration of a terminal according to one embodiment of the present disclosure.

[0018] FIG. 7 illustrates a configuration of a base station according to one embodiment of the present disclosure.

[0019] FIG. 8 illustrates a configuration of a network entity according to one embodiment of the present disclosure.

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

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

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

[0023] The advantages and features of the present disclosure, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below 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. The 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.

[0024] Furthermore, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0025] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), 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 the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although LTE, LTE-A, or 5G systems may be described as examples below, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0026] 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).

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

[0028] 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 regenerate one or more processors. Thus, 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'. In addition, the components and '~ units' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in the embodiment, '~bu' may include one or more processors.

[0029] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE (Institute of Electrical and Electronics Engineers)'s 802.16e.

[0030] As a representative example of the above broadband wireless communication system, the LTE system adopts the Orthogonal Frequency Division Multiplexing (OFDM) method in the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, gNode B, or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0031] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0032] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0033] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, due to the nature of the service. This may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, very long battery lifespans, such as 10 to 15 years, may be required.

[0034] Finally, URLLC refers to cellular-based wireless communication services used for specific mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, URLLC-enabled services must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0035] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0036] In this disclosure, phrases such as “A and / or 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).

[0037] 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 form to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0038] In the present disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and components included in the network structure of Fig. 1 may each mean a physical entity, or may mean software performing an individual function, or hardware combined with software. Reference symbols shown as Nx, such as N1, N2, N3, ..., in the drawings represent known interfaces between NFs in a 5G core network (CN), and since a related description may refer to a standard specification (e.g., TS 23.501), a detailed description will be omitted.

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

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

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

[0042] Referring to FIG. 1, a 5G network may include network entities (NE) or network functions (NF) described below.

[0043] (R)AN ((Radio) Access Network) 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 (Next Generation Radio Access Network), a 5G-AN (5G Access Network), a 5G NR (5G New Radio), a radio access unit, a base station controller, or a node on a network.

[0044] The terminal may include a UE (User Equipment), NG UE (Next Generation UE), MS (Mobile Station), cellular phone, smartphone, computer, IoT (Internet of Things) device, or multimedia system capable of performing communication functions.

[0045] Furthermore, while the embodiments of the present disclosure are described below using a 5G system as an example, the embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure can 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.

[0046] As wireless communication systems evolve from 4G to 5G, a new core network (CN) called the Next Generation 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 may refer to a network entity, a network component, or a network resource.

[0047] 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 of FIG. 1, and 5GC may include more or fewer NFs than the NFs illustrated in FIG. 1.

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

[0049] A Session Management Function (SMF) may be a network function that manages a Packet Data Network (PDN) connection provided to a user equipment (UE). A PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, an SMF may perform network functions such as session management through the establishment, modification, and release of sessions and the maintenance of tunnels between the UPF and the RAN required for this; user plane (UP) selection and control; traffic processing control in the UPF; and charging data collection control.

[0050] PCF (Policy Control Function) may be a network function that applies the mobile carrier's service policy, charging policy, and PDU Session policy to the terminal.

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

[0052] The Network Exposure Function (NEF) may provide terminal information to servers outside the 5G network. Additionally, NEF may provide the information necessary for 5G network services and store it in the Unified Data Repository (UDR).

[0053] The User Plane Function (UPF) may function as a gateway that transmits user data (PDU) to the Data Network (DN). 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 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 generation, and buffering.

[0054] NRF (Network Repository Function) can store the profiles of NFs and perform the function of discovering NFs.

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

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

[0057] The Network Data Analytics Function (NWDAF) collects data from multiple NFs (Network Functions) to ensure efficient operation of the 5GC network. This data is analyzed using a machine learning (ML) model, and the results are provided to the NFs, helping them provide efficient network services.

[0058] An Application Function (AF) can communicate with a network operator to enable external servers (Application Servers) to utilize network services provided by the network operator. Depending on the deployment entity, AFs can be categorized as internal AFs and external AFs. Internal AFs deployed by network operators can communicate directly with network functions (NFs) within the network operator. AFs deployed by third-party service providers (3rd-party service providers) must go through an NEF to communicate with NFs within the network operator.

[0059] DN (Data Network) can be a data network where terminals transmit and receive data to use network operator services or third-party services.

[0060] The terminal may include an IoT device. The IoT device may include a device that does not use battery power or operates with very little power, and such IoT devices are referred to as ambient IoT devices (or simply Ambient IoT).

[0061] According to one embodiment of the present disclosure, when a UPF is composed of one or more modules and functions (hereinafter, referred to only as modules), a method is proposed in which an SMF updates an N4 Session Context for controlling the UPF.

[0062] [UPF Modular]

[0063] FIG. 2 illustrates an example of a UPF module according to one embodiment of the present disclosure.

[0064] The services provided by UPF can be divided into mandatory functionality and optional functionality. Mandatory functionality includes functions required to provide the mandatory services of UPF defined in the standard, while optional functionality may include functions required to provide additional services in addition to the mandatory services of UPF defined in the standard. For example, UPF can receive user packets from DNs and transmit them to terminals, and send user packets received from terminals to DNs. To provide these services, UPF requires a Packet Processing module. However, Shallow / Deep Packet Inspection, which examines user packets received from terminals or DNs, is not a service of UPF defined in the standard.

[0065] Modularizing each UPF function allows for the flexible expansion or reduction of resources required for each module's operation, enabling efficient use of allocated resources. Furthermore, non-essential features can be added or removed from the UPF at any time as needed. This allows UPFs with only essential features to be offered at a relatively lower price than existing fully-functional UPFs.

[0066] In this disclosure, all functions of the UPF are modularized according to the modular design. Referring to FIG. 2, a UPF that includes only essential functions excluding additional functions among the functions of the UPF is called a Light UPF. In addition, a UPF that has all functions including essential functions and additional functions without modularizing the functions of the UPF, like the UPF on the right side of FIG. 2, is called a Heavy UPF. In this disclosure, the distinction between UPFs as Light UPF and Heavy UPF is only to facilitate the description of one embodiment, and the names for distinguishing them are not limited to this (Light UPF, Heavy UPF).

[0067] FIG. 3 illustrates an example of deploying Light UPF and Heavy UPF according to one embodiment of the present disclosure. In a scenario where only Heavy UPF is deployed, the same UPF is used to process the service data flow regardless of the type of service data flow used by the terminal. However, in a scenario where Light UPF is deployed, the Light UPF that will handle the service data flow may be selected in consideration of the additional functions additionally provided by the UPF depending on the type of service data flow used by the terminal. For example, in the case of a service data flow for a banking service, a Light UPF that provides a firewall additional function may be selected because security is important. In the case of a service data flow for a video streaming service, a Light UPF that provides a caching additional function may be selected because packet latency, which may cause buffering, is important.

[0068] FIG. 4 illustrates a traffic filter that classifies service data flows by type according to one embodiment of the present disclosure.

[0069] A traffic filter can be implemented in a terminal. The traffic filter can classify the service data flows used by the terminal by type using one or more of the following information. The following information is merely an example and does not limit the present disclosure. Other information may be used to classify the types of service data flows.

[0070] - 5-tuple: source IP address, source port number, destination IP address, destination port number, protocol in use.

[0071] - Application ID: An ID used to distinguish applications on a terminal platform or operating system (OS), for example, Android or iOS.

[0072] Service data flows can be categorized into the following types, and the additional UPF functions required for them can be listed as follows. However, the following classification of service data flows and the additional UPF functions required for each classification are merely examples and do not limit the present disclosure. In addition, service data flows can be categorized into other types, and the additional UPF functions required for each type may also vary.

[0073] - High Data Rate or Low Latency requiring services.

[0074] * One example is High resolution video streaming application (e.g. 4K, 8K, VR, AR and so on).

[0075] * Required UPF add-ons: Traffic optimization module, Caching module.

[0076] - High Security requiring services.

[0077] * One example, Financial and government application.

[0078] * Required UPF add-ons: Firewall module, DNS snooping detection module.

[0079] - Services that require monitoring (Malicious services).

[0080] * One embodiment, Blocked application, Lawful interception required application.

[0081] * Required UPF add-on: Shallow or Deep Packet Inspection module.

[0082] Table 1 illustrates a Packet Functionality Rule (PFR) for applying a UPF module to a service data flow according to one embodiment.

[0083]

[0084] A PFR may contain information about the UPF modules that the UPF should apply to a service data flow. A PFR may be generated by the PCF or SMF and transmitted to the UPF during the N4 Session creation procedure. A PFR may be generated based on one or more of the following information: UE subscription data, URSP rules, and service data flow description information received from the UE.

[0085] Table 2 illustrates a modified Packet Detection Rule (PDR) to apply PFR according to one embodiment.

[0086]

[0087]

[0088] For service data flows distinguished by PDR, PFR distinguished by the corresponding Packet Functionality Rule ID can be applied.

[0089] FIGS. 5A and 5B illustrate a flowchart of a PDU Session creation procedure according to one embodiment of the present disclosure. FIGS. 5A and 5B can describe sequential procedures for creating a PDU Session.

[0090] The terminal can transmit information about service data flows generated by the traffic filter to the network.

[0091] In Step 1, the terminal can generate a PDU Session Establishment Request message and transmit it to the network to request the creation of a new PDU Session. This message may include information about the service data flow generated by the traffic filter (e.g., description information of the service data flow). This information can be transmitted to the SMF via the RAN and AMF.

[0092] In step 2, AMF can perform SMF selection procedure.

[0093] In step 3, AMF can send the Nsmf_PDUSession_CreateSMContext Request message to SMF.

[0094] In step 4, SMF and UDM can perform subscription retrieval / Subscription procedures for updates.

[0095] In step 5, SMF can send the Nsmf_PDUSession_CreateSMContext Response message to AMF.

[0096] In step 6, a PDU Session authentication / authorization procedure may be performed to create a PDU Session directed to a specific DN.

[0097] In step 7a, the SMF can perform a PCF selection procedure.

[0098] In step 7b, an SM Policy Association Establishment procedure or an SMF-initiated SM Policy Association Modification procedure may be performed between an SMF entity and a PCF entity. In step 7b, the SMF may transmit description information of service data flow information to the PCF. The SMF or PCF may generate PFR information using at least some of the UE subscription data, URSP rules, or description information of service data flow information.

[0099] In step 8, SMF can perform the UPF selection procedure.

[0100] At step 9, SMF is initiated and SM Policy Association Modification can be performed between SMF entities and PCF entities.

[0101] An N4 Session may be created between the SMF and the UPF in step 10a or step 10b. In step 10a, the SMF sends an N4 Session Establishment / Modification Request message to the UPF. The N4 Session Establishment Request message may include at least some of the N4 Session ID, Packet Detection Rules (PDR), Forwarding Action Rules (FDR), Multi-Access Rules (MAR), Usage Reporting Rules (URR), QoS Enforcement Rules (QER), Session Reporting Rules (SRR), Trace Requirements, Port Management Information, Bridge / Router Information, or Packet Functionality Rules (PFR).

[0102] At step 10b, UPF may send an N4 Session Establishment / Modification Response message to SMF.

[0103] At step 11, SMF and AMF can perform Namf_Communication_N1N2MessageTransfer.

[0104] At step 12, AMF may send an N2 PDU Session Request (NAS msg) to (R)AN.

[0105] In step 13, the UE and (R)AN may perform AN-specific resource setup (PDU Session Establishment Accept).

[0106] At step 14, (R)AN may send an N2 PDU Session Response message to AMF.

[0107] Afterwards, the terminal can transmit the first uplink data to the UPF.

[0108] In step 15, AMF may send an Nsmf_PDUSession_UpdateSMContext Request message to SMF.

[0109] In step 16a, the SMF may send an N4 Session Modification Request message to the UPF. In step 16b, the UPF may send an N4 Session Modification Response message to the SMF. In step 16c, the SMF and UDM may perform registration. The UPF may transmit the first downlink data to the UE.

[0110] In step 17, SMF may send an Nsmf_PDUSession_UpdateSMContext Response message to AMF.

[0111] At step 18, SMF may send an Nsmf_PDUSession_SMContextStatusNotify message to AMF.

[0112] In step 19, SMF can set IPv6 Address Configuration to the terminal through UPF.

[0113] At step 20, SMF is initiated and SM Policy Association Modification can be performed between SMF entities and PCF entities.

[0114] At step 21, an Unsubscription procedure can be performed between SMF and UDM.

[0115] FIG. 6 is a diagram showing the configuration of a terminal according to one embodiment of the present disclosure.

[0116] A terminal according to one embodiment of the present disclosure may include a processor (620) that controls the overall operation of the terminal, a transceiver (600) including a transmitter and a receiver, and a memory (610). 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. 6.

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

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

[0119] According to one embodiment of the present disclosure, the memory (610) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (610) provides the stored data upon request of the processor (620). The memory (610) 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 (610). In addition, the processor (620) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (610).

[0120] FIG. 7 is a diagram showing the configuration of a base station according to one embodiment of the present disclosure.

[0121] As illustrated in FIG. 7, the base station of the present disclosure may include a processor (control unit) (720), a transceiver (700), and a memory (storage unit) (710). However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the processor (720), the transceiver (700), and the memory (710) may be implemented in the form of a single chip. The processor (720) of FIG. 7 may include at least one controller.

[0122] The processor (720) may control a series of processes so that the base station can operate according to the embodiments of the present disclosure described above. For example, the processor may control components of the base station to perform a method for scheduling a terminal according to whether the base station mode is the base station energy saving mode or the base station normal mode according to the embodiments of the present disclosure. There may be one or more processors (720), and the processors (720) may execute a program stored in the memory (710) to perform the method for scheduling a terminal according to whether the base station mode of the present disclosure described above is the base station energy saving mode or the base station normal mode.

[0123] The transceiver (700) can transmit and receive signals with a terminal or a network entity. The signals transmitted and received with the terminal, another base station, or a network entity can include control information and data. The transceiver (700) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (700) is only one embodiment, and the components of the transceiver (700) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (700) can receive a signal through a wireless channel, output it to the processor (720), and transmit the signal output from the processor (720) through the wireless channel.

[0124] According to one embodiment, the memory (710) can store programs and data required for the operation of the base station. In addition, the memory (710) can store control information or data included in signals transmitted and received by the base station. The memory (710) 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 (710). According to one embodiment, the memory (710) can store a program for performing a method for scheduling a terminal depending on whether the base station mode of the embodiments of the present disclosure described above is a base station energy saving mode or a base station normal mode.

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

[0126] 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 disclosure is not limited to the above example, and the network entity may include more or fewer components than the configuration illustrated in FIG. 8. In addition, according to one embodiment of the present disclosure, the network entity may mean a network function (NF), and the NF may include a RAN, an AMF, a PCF, a UDM, an NEF, an UPF, an NRF, an AUSF, an NSSF, an NWDAF, an AF, and a DN.

[0127] 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 base stations. The signals transmitted and received with at least one of other network entities or base stations can include control information and data.

[0128] According to one embodiment of the present disclosure, the processor (820) can control the 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. According to one embodiment of the present disclosure, the processor (820) can control a series of processes by which the NF can operate according to the embodiments of the present disclosure described above. For example, the processor (820) can control the components of the network entity to perform the network slice change support method according to the embodiments described above. The processor (820) can control components of the network entity to perform the embodiments of the present disclosure described above by executing a program stored in the memory (810).

[0129] 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 the network entity. In particular, the memory (810) provides the stored data upon request of the processor (820). In addition, the memory (810) can store control information or data included in signals transmitted and received by the network entity. 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 of the present disclosure based on a program for performing the above-described embodiments stored in the memory (810).

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

[0131] 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).

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

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

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

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

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

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

[0138] While the detailed description of the present disclosure has described specific embodiments, it should be understood 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 claims described below 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, the respective embodiments may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined 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 may be implemented in other systems such as LTE, LTE-A, and LTE-A-Pro systems.

[0139] 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 wireless communication system, in the UPF (user plane function) entity, a transceiver; and A controller coupled to the above transceiver, wherein the controller comprises: Receive an N4 session establishment request message including a packet detection rule (PDR) and a packet functionality rule (PFR) corresponding to the PDR from an SMF (session management function) entity, Determine at least one UPF function to be applied to the service data flow based on the above PDR and the above PFR, configured to transmit the service data flow to which at least one UPF function is applied; The above PFR is a UPF entity that includes information about at least one UPF function to be applied to the service data flow.

2. In paragraph 1, The above control unit, A UPF entity configured to transmit the service data flow to which at least one UPF function is applied, to an entity determined based on a forwarding action rule (FAR) included in the N4 session establishment request message.

3. In paragraph 1, The above PDR is a UPF entity that includes an identifier for identifying whether the service data flow is subject to the application of the PFR.

4. In paragraph 1, The above PFR is, A UPF entity comprising at least some of information for determining an order in which the at least one UPF function is applied, information for identifying the at least one UPF function, information about parameters for the at least one UPF function, information about a direction of the service data flow to which the at least one UPF function is to be applied, information for identifying whether the at least one UPF function is mandatory or optional, and information for identifying restrictions on using the at least one UPF function.

5. In paragraph 1, The above PFR is generated based on at least some of the information about the service data flow received from the UE (user equipment) subscription data, the URSP (UE route selection policy) rule, or the terminal by the PCF (policy control function) entity or the SMF entity, Information about the above service data flow, a UPF entity including information about at least one UPF function required for the above service data flow.

6. A method performed by a UPF (user plane function) entity in a wireless communication system, A step of receiving an N4 session establishment request message including a packet detection rule (PDR) and a packet functionality rule (PFR) corresponding to the PDR from a session management function (SMF) entity; A step of determining at least one UPF function to be applied to a service data flow based on the PDR and the PFR; and Comprising a step of transmitting the service data flow to which at least one UPF function is applied, A method wherein the PFR includes information about at least one UPF function to be applied to the service data flow.

7. In paragraph 6, The step of transmitting the service data flow to which at least one UPF function is applied is as follows: A method comprising the step of transmitting to an entity determined based on a forwarding action rule (FAR) included in the above N4 session establishment request message.

8. In paragraph 6, A method wherein the PDR includes an identifier for identifying whether the service data flow is subject to the application of the PFR.

9. In a wireless communication system, for the SMF (session management function) entity, a transceiver; and A controller coupled to the above transceiver, wherein the controller comprises: It is configured to send an N4 session establishment request message including a packet detection rule (PDR) and a packet functionality rule (PFR) corresponding to the PDR to a user plane function (UPF) entity, The above PFR is an SMF entity containing information about at least one UPF function to be applied to a service data flow.

10. In paragraph 9, The above control unit, An SMF entity configured to receive, from the UPF entity, the service data flow to which the at least one UPF function is applied.

11. In paragraph 9, The above PDR is an SMF entity that includes an identifier for identifying whether the service data flow is subject to the application of the PFR.

12. In paragraph 9, The above PFR is, An SMF entity including at least some of the following: information for determining an order in which the at least one UPF function is applied, information for identifying the at least one UPF function, information about parameters for the at least one UPF function, information about a direction of the service data flow to which the at least one UPF function is to be applied, information for identifying whether the at least one UPF function is mandatory or optional, and information for identifying restrictions on using the at least one UPF function.

13. In paragraph 9, The above control unit, Receive information about the service data flow from the terminal, Further configured to determine the PFR based on at least some of UE (user equipment) subscription data, URSP (UE route selection policy) rule, or information about the service data flow, Information about the above service data flow, an SMF entity including information about at least one UPF function required for the above service data flow.

14. A method performed by an SMF (session management function) entity in a wireless communication system, A step of transmitting an N4 session establishment request message including a packet detection rule (PDR) and a packet functionality rule (PFR) corresponding to the PDR to a user plane function (UPF) entity, A method wherein the above PFR includes information about at least one UPF function to be applied to a service data flow.

15. In paragraph 14, A method further comprising the step of receiving, from the UPF entity, the service data flow to which the at least one UPF function is applied.

Images