Method and device for user traffic management in wireless communication system

Abstract

The present disclosure relates to a method performed by a terminal in a wireless communication system, the method comprising the steps of: acquiring UE route selection policy (URSP) information; identifying, on the basis of the URSP information, application information that generated a data flow; mapping, on the basis of the identified application information, the data flow to a predetermined quality of service (QoS) flow of a protocol data unit (PDU) session; inserting the identified application information into a GPRS tunneling protocol-user plane (GTP-U) extension header of the data flow; and transmitting the data flow.

Description

Method and device for managing user traffic in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for managing user data traffic of each application separately.

[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] The present disclosure provides a method and device for distinguishing and managing user traffic generated by multiple applications installed on a user device in a wireless communication system.

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

[0010] The disclosed embodiment provides a device and method capable of effectively providing a service in a wireless communication system.

[0011] FIG. 1 illustrates a wireless communication system according to one embodiment of the present disclosure.

[0012] FIG. 2 illustrates an operation in which data traffic generated by two applications installed on a user terminal according to one embodiment of the present disclosure is transmitted to a data network via a network.

[0013] FIG. 3 illustrates a TCP Header and an IP Header (IPv4) among the TCP / IP protocol stacks according to one embodiment of the present disclosure.

[0014] FIG. 4 illustrates a process of mapping a service data flow to a QoS Flow in a 5G system according to one embodiment of the present disclosure.

[0015] FIG. 5 illustrates operations between an application and a modem to transmit a service data flow to a DN when the service data flow is generated within a terminal according to one embodiment of the present disclosure.

[0016] FIG. 6 illustrates an application (terminal platform) providing application-related information and extended QoS Rules according to one embodiment of the present disclosure.

[0017] FIG. 7 illustrates an extended GTP-U (GPRS Tunneling Protocol-User Plane) header for transmitting application information that generated a service data flow in a network according to one embodiment of the present disclosure.

[0018] FIG. 8 illustrates an extended GTP-U (GPRS Tunneling Protocol-User Plane) header for transmitting application information that generated a service data flow in a network according to one embodiment of the present disclosure.

[0019] FIG. 9 illustrates an SM Policy Association setup procedure according to one embodiment of the present disclosure.

[0020] FIG. 10 illustrates an N4 Session setup procedure according to one embodiment of the present disclosure.

[0021] FIG. 11 illustrates a flowchart of a method for managing user traffic according to one embodiment of the present disclosure.

[0022] FIG. 12 illustrates a configuration of a terminal according to one embodiment of the present disclosure.

[0023] FIG. 13 is a diagram illustrating a configuration of a base station or network entity according to one embodiment of the present disclosure.

[0024] In a method performed by a terminal of a wireless communication system according to one embodiment of the present disclosure, the method may include: obtaining URSP (UE route selection policy) information; identifying application information that generates a data flow based on the URSP information; mapping the data flow to a predetermined QoS (quality of service) flow of a PDU (protocol data unit) session based on the identified application information; inserting the identified application information into a GTP-U (GPRS tunneling protocol-User plane) extension header of the data flow; and transmitting the data flow.

[0025] The above GTP-U extension header can be set to a PDU (protocol data unit) session container type.

[0026] The above GTP-U extension header can be set to an application description type.

[0027] The above application information may include operating system (OS) identification information and application identification information.

[0028] The above application information is included in an application descriptor, and the application descriptor may be included in a traffic descriptor.

[0029] In a method performed by a session management function (SMF) of a wireless communication system according to one embodiment of the present disclosure, the method may include: performing a user plane function (UPF) associated with a PDU session for receiving a data flow and an N4 session establishment procedure; obtaining extended packet detection rule (PDR) information for processing a data flow based on application information through the N4 session establishment procedure; and controlling transmission of the data flow based on the extended PDR information and application information included in the data flow received through the PDU session.

[0030] Application information included in the above data flow may be included in a GTP-U (GPRS tunneling protocol-User plane) extension header.

[0031] The above GTP-U extension header can be set to a PDU (protocol data unit) session container type or an application descriptions type.

[0032] The packet detection information within the above extended PDR information may include OS (operating system) identification information and application identification information.

[0033] The method includes the steps of transmitting an Npcf_SMPolicyControl_Create message for setting an SM (session management) policy to a PCF (policy control function); and receiving an Npcf_SMPolicyControl_Create Response message indicating that an SM (session management) policy has been set from the PCF, wherein the Npcf_SMPolicyControl_Create Response message includes QoS (quality of service) rule information including application information, and the QoS rule information can be used to perform QoS flow mapping considering the application information.

[0034] According to one embodiment of the present disclosure, a terminal of a wireless communication system includes: a transceiver; and at least one processor coupled to the transceiver, wherein the at least one processor is configured to obtain URSP (UE route selection policy) information, identify application information that generates a data flow based on the URSP information, map the data flow to a predetermined QoS (quality of service) flow of a PDU (protocol data unit) session based on the identified application information, insert the identified application information into a GTP-U (GPRS tunneling protocol-User plane) extension header of the data flow, and transmit the data flow.

[0035] The above GTP-U extension header can be set to a PDU (protocol data unit) session container type or an application descriptions type.

[0036] The above application information may include operating system (OS) identification information and application identification information.

[0037] In an SMF (session management function) of a wireless communication system according to one embodiment of the present disclosure, the SMF includes a transceiver; and at least one processor coupled to the transceiver, wherein the at least one processor performs a user plane function (UPF) associated with a PDU session for receiving a data flow and an N4 session establishment procedure, obtains extended packet detection rule (PDR) information for processing a data flow based on application information through the N4 session establishment procedure, and controls transmission of the data flow based on the extended PDR information and application information included in the data flow received through the PDU session.

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

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

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

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

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

[0043] 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, the downlink (DL) refers to a wireless transmission path of a signal transmitted from the base station to the terminal, and the uplink (UL) refers to a wireless transmission path of a signal transmitted from the terminal to the 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 the 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 with 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.

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

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

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

[0047] 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's 802.16e.

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

[0049] As a future communication 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-Reliable Low Latency Communication (URLLC).

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

[0051] 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, such as basements, beyond cell coverage due to the nature of the service, and thus 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, they may require extremely long battery lifespans, such as 10 to 15 years.

[0052] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). 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, services supporting URLLC 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 a shorter transmission time interval (TTI) than other services, and design requirements may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

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

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

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

[0056] 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 the standard specification (TS 23.501), a detailed description will be omitted.

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

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

[0059] FIG. 1 illustrates a wireless communication system according to an embodiment of the present disclosure. The wireless communication system of FIG. 1 may be a 5G (5th generation) system and may be used interchangeably with an NR (new radio) system.

[0060] Referring to FIG. 1, a 5G network may include network entities (NEs) or network functions (NFs) described below. Of course, a 5G network may include more or fewer network entities (or network functions) than the network entities (or network functions) illustrated in FIG. 1.

[0061] According to one embodiment of the present disclosure, (R)AN ((Radio) Access Network) is an entity that performs radio 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, a base station controller, or a node on a network.

[0062] According to one embodiment of the present disclosure, a terminal may include a UE (User Equipment), an NG UE (Next Generation UE), an MS (Mobile Station), a cellular phone, a smartphone, a computer, an IoT (Internet of Things) device, or any device capable of performing a communication function and a multimedia system capable of performing a communication function.

[0063] According to one embodiment of the present disclosure, a wireless communication system may evolve from a 4G system (e.g., long term evolution (LTE), long term evolution advanced (LTE-A)) to a 5G system, and the 5G system may include a new core network (CN), such as Next Generation Core (NG Core) or 5G Core Network (5GC). The new core network may be a network that virtualizes some or all of the existing network entities (NEs) and implements them as network functions (NFs). According to one embodiment of the present disclosure, a network function may mean a network entity, a network component, or a network resource, and is not limited to the above examples.

[0064] According to one embodiment of the present disclosure, 5GC may include NFs 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 NFs illustrated in FIG. 1.

[0065] According to one embodiment of the present disclosure, an Access and Mobility Management Function (AMF) may be a network function that manages access and mobility of a terminal (UE). For example, the AMF may perform network functions such as terminal registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0066] According to one embodiment of the present disclosure, a Session Management Function (SMF) 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 Protocol Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining tunnels between the UPF and the RAN required for this, selecting and controlling a User Plane (UP), controlling traffic processing in the UPF, and controlling the collection of charging data.

[0067] According to one embodiment of the present disclosure, a Policy Control Function (PCF) 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.

[0068] According to one embodiment of the present disclosure, Unified Data Management (UDM) may be a network function that stores subscriber information. For example, UDM may 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.

[0069] According to one embodiment of the present disclosure, the Network Exposure Function (NEF) 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 services on the 5G network in a Unified Data Repository (UDR).

[0070] According to one embodiment of the present disclosure, a User Plane Function (UPF) may be a function that acts as a gateway to transmit user data (PDU) to a Data Network (DN). More specifically, the UPF may perform a data processing function 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 creation, and buffering.

[0071] According to one embodiment of the present disclosure, a Network Repository Function (NRF) can perform a function of storing profiles of NFs and discovering NFs.

[0072] According to one embodiment of the present disclosure, an Authentication Server Function (AUSF) can perform terminal authentication in a 3GPP access network and a non-3GPP access network.

[0073] According to one embodiment of the present disclosure, the Network Slice Selection Function (NSSF) can perform a function of selecting a Network Slice Instance provided to a terminal.

[0074] According to one embodiment of the present disclosure, the Network Data Analytics Function (NWDAF) collects data from multiple NFs (NFs) for the purpose of efficiently operating the 5GC network. The collected data is analyzed using a machine learning (ML) model, and the analyzed results are provided back to the NFs, thereby helping each NF provide efficient network services.

[0075] According to one embodiment of the present disclosure, an Application Function (AF) can perform communication with a network operator so that an external server (Application Server) can utilize network services provided by the network operator. The AF can be divided into an internal AF and an external AF depending on the service provider. An internal AF implemented by a network operator can directly communicate with NFs within the network operator. An AF implemented by a service provider, such as a third party, may need to go through an NEF to communicate with NFs within the network operator.

[0076] According to one embodiment of the present disclosure, a DN (Data Network) may be a data network through which a terminal transmits and receives data in order to use a network operator's service or a third-party service.

[0077] According to one embodiment of the present disclosure, a 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 an IoT device is referred to as an ambient IoT device (or simply Ambient IoT).

[0078] In this disclosure, we propose a method for distinguishing user traffic generated by multiple applications installed on a user terminal by application and managing the traffic generated by each application.

[0079] FIG. 2 illustrates an operation in which data traffic generated by two applications installed on a user terminal according to one embodiment of the present disclosure is transmitted to a data network via a network.

[0080] A user terminal may have application #1 (e.g., YouTube application) and application #2 (e.g., Explorer application) installed. Traffic generated by both applications may be transmitted via the network to an application server (e.g., YouTube Server) installed on the data network. Furthermore, traffic generated from the application server installed on the data network may also be transmitted via the network to the application installed on the user terminal.

[0081] According to one embodiment of the present disclosure, when distinguishing user traffic in a modem of a terminal, the distinction can be made using a Packet Filter Set. The Packet Filter Set can be composed of at least one of the following values: source / destination IP address or IPv6 prefix, source / destination port number, Protocol ID, Type of Service (TOS) (IPv4), Traffic Class (IPv6) and Mask, Flow Label (IPv6), Security Parameter Index, Packet Filter Direction. If it is an Ethernet Packet Filter Set, it can be composed of at least one of source / destination MAC address, Ethertype, Customer-VLAN tag (C-TAG) and / or Service-VLAN tag (S-TAG) VID, Customer-VLAN tag (C-TAG) and / or Service-VLAN tag (S-TAG) PCP / DEI, IP Packet Filter Set, Packet Filter Direction.

[0082] Figure 3 illustrates a TCP Header and an IP Header (IPv4) among the TCP / IP protocol stacks according to one embodiment of the present disclosure. While the present disclosure is based on the TCP protocol and the IPv4 protocol, the present disclosure can also be applied to other protocols utilizing the TCP / IP protocol.

[0083] According to one embodiment of the present disclosure, if the user data generated or received by the application installed on the terminal is based on the TCP / IP protocol, it may include a TCP header and an IP header as shown in FIG. 3. The IP header may include a Source IP address field, which is the IP address of the sender terminal, and a Destination IP address field, which is the IP address of the sender terminal. In addition, the IP header may include a Type of Service (ToS) field, which indicates the service type and congestion notification of the IP packet. Additionally, the IP header may include a Protocol field, which indicates the type of upper protocol transmitted by the IP packet, such as TCP, UDP, ICMP, or IGMP.

[0084] According to one embodiment of the present disclosure, a TCP header may include a Source Port field that identifies an application (process) of a sender terminal and a Destination Port field that identifies an application (process) of a receiver terminal.

[0085] According to one embodiment of the present disclosure, the IP header and TCP header included in the packets of the service data flow may include information that distinguishes the service data flow using the Packet Filter Set described in FIG. 2. That is, the terminal may distinguish the service data flow using the IP header and TCP header of the packets of the service data flow.

[0086] FIG. 4 illustrates a process of mapping a service data flow to a QoS Flow in a 5G system according to one embodiment of the present disclosure.

[0087] According to one embodiment of the present disclosure, a service data flow transmitted through an uplink (UL) may be mapped to a QoS flow using QoS rules of a terminal, and a service data flow transmitted through a downlink (DL) may be mapped to a QoS flow using a Packet Detection Rule (PDR) in an uplink packet filter (UPF). Both the QoS rules and the PDR may include a Packet Filter Set.

[0088] For example, when a user uses a communication service (such as surfing the Internet, listening to music, or watching a movie) using an application installed on a terminal, the application can generate a service data flow (IP packet) and transmit it to an application server on the Internet. The IP packet generated by the application can be transmitted to a modem in the terminal. The modem in the terminal that receives the IP packet can allocate a QFI (QoS Flow Identify) to apply a QoS corresponding to the IP packet and transmit it to a Data Network (DN, e.g., the Internet), and transmit the IP packet using the QoS Flow corresponding to the QFI. At this time, the terminal (the modem in the terminal) can use QoS Rules to map the IP packet to an appropriate QoS Flow. According to one embodiment, the QoS Rules may be information received from the network when the terminal creates a PDU Session or may be preset values.

[0089] According to one embodiment of the present disclosure, a terminal can map an IP packet to a QoS Flow using Packet Filter Set information included in QoS Rules and transmit the IP packet to a DN through an AN (Access Node) and a UPF using the QoS Flow.

[0090] According to one embodiment of the present disclosure, a DL service data flow can be transmitted to a corresponding application through an AN and a terminal by performing a QoS Flow mapping process in a UPF.

[0091] As explained above, the current 5G system uses a Packet Filter Set to distinguish service data flows. Therefore, if two applications use the same service using the same application server as in the embodiment of Fig. 2, it may be impossible to distinguish the two service data flows and apply differentiated QoS and provide differentiated services by distinguishing the two service data flows in the network.

[0092] For example, in the embodiment of FIG. 2, in order to provide uninterrupted service to users who use video streaming using application #1 (YouTube), enhanced QoS may be applied, or data communication service may be provided free of charge to users who use video streaming service using application #1, and conversely, enhanced QoS may not be supported and data communication fees may not be supported for users who use video streaming service using application #2 (Explorer). In other words, differentiation of data communication services provided depending on the application may be necessary, but it is currently difficult to distinguish service data flows corresponding to each application.

[0093] Accordingly, the present disclosure below proposes a method and device capable of providing different communication services for each application, such as differentially providing QoS that distinguishes not only the IP packet itself but also the application that generated the IP packet in distinguishing the service data flow.

[0094] FIG. 5 illustrates operations between an application and a modem to transmit a service data flow to a DN when the service data flow is generated within a terminal according to one embodiment of the present disclosure.

[0095] According to one embodiment of the present disclosure, in a 5G network, URSP (UE Route Selection Policy) information can be used to select a path for transmitting a service data flow generated by a terminal to a data network. Selecting a path in a 5G network means selecting a PDU Session. If a session suitable for the generated service data flow exists among the PDU Sessions previously generated by the terminal, the service data flow is transmitted to a DN using the session. If a suitable session does not exist, the terminal can create a session suitable for the service data flow using a PDU Session creation procedure and transmit the service data flow to a DN using the session.

[0096] According to one embodiment, the URSP information may include a list of prioritized URSP rules. According to one embodiment, each URSP rule may include at least one of a Rule precedence for application priority, a Traffic descriptor for distinguishing service data flows, and a List of Route Selection Descriptors for selecting a path for the service data flows distinguished by the Traffic descriptor.

[0097] According to one embodiment, a traffic descriptor may include at least one of application descriptors, IP descriptors, domain descriptors, non-IP descriptors, and a data network name (DNN). Of course, the above examples are not limited and may include more or less information than the information described above. Since the information described above corresponds to a name, a detailed description thereof will be omitted.

[0098] According to one embodiment, each Route Selection Descriptor may include at least one of Route Selection Descriptor Precedence, Route Selection Components, and Route Selection Validation Criteria for application priority of each Route Selection Descriptor. Of course, the present invention is not limited to the above examples, and may include more or less information than the information described above. Since the information described above corresponds to names, a detailed description thereof will be omitted.

[0099] According to one embodiment, Route Selection Components may include at least one of Session and Service Continuity (SSC) Mode Selection, Network Slice Selection, DNN Selection, PDU Session Type Selection, and Access Type preference. Of course, the present invention is not limited to the above examples and may include more or less information than the information described above. Since the information described above corresponds to names, a detailed description thereof will be omitted.

[0100] According to one embodiment of the present disclosure, an application (terminal platform, iOS, Android) may transmit traffic descriptor information constituting a URSP Rule to a modem in addition to an IP packet in order to transmit a service data flow to a DN. Among the values ​​constituting the traffic descriptor information, the application descriptor information may be composed of an operating system identifier (OSId) and an operating system application identifier (OSAppId). The OSId information may be information indicating the operating system (OS) of the terminal. For example, it may be identification information of the OS of the terminal, such as iOS or Android. The OSAppId information may be information indicating an application in the corresponding OS. For example, it may be identification information indicating an application in the OS of the terminal, such as YouTube or Explorer.

[0101] According to one embodiment of the present disclosure, information configuring QoS Rules that map a service data flow to a QoS Flow does not include information about an application that generated the service data flow, but URSP Rules information that selects a path for the service data flow may include information about an application. Information about an application that generates a service data flow is information that can only be known to a terminal, and in order to use information about an application that generates a service data flow in a network, the terminal must transmit information about an application that generates a service data flow to the network.

[0102] FIG. 6 illustrates an application (terminal platform) providing application-related information and extended QoS Rules according to one embodiment of the present disclosure.

[0103] According to one embodiment of the present disclosure, in order to consider the application that generated the service data flow when mapping the service data flow to the QoS Flow, the information configuring the QoS Rules may be added not only to the Packet Filter Set but also to the Application Information. The Application Information may be composed of the OSId and the OSAppId. In addition, the application (terminal platform, running within the terminal) may provide the Application Description information to the modem for service data flow path setting (e.g., path setting according to URSP) and for QoS Flow mapping.

[0104] According to one embodiment of the present disclosure, when mapping a service data flow to a QoS Flow, a modem within a terminal can allocate QFIs and map them to a QoS Flow by considering not only IP packets but also the application that generated the service data flow.

[0105] FIG. 7 illustrates an extended GTP-U (GPRS Tunneling Protocol-User Plane) header for transmitting application information that generated a service data flow in a network according to one embodiment of the present disclosure.

[0106] According to one embodiment of the present disclosure, a terminal can convey application-related information to a network by adding the OSAppId and OSId fields to the PDU Session Container, which is an Extension Header of a GTP-U header. Referring to FIG. 7, the terminal can add the OSAppId and OSId fields to a GTP-U Extension Header in which the Next Extension Header Type is set to PDU Session Container.

[0107] Additionally, terminals and networks can also allocate QFI values ​​of service data flows by considering application information.

[0108] FIG. 8 illustrates an extended GTP-U (GPRS Tunneling Protocol-User Plane) header for transmitting application information that generated a service data flow in a network according to one embodiment of the present disclosure.

[0109] According to one embodiment of the present disclosure, a new GTP-U Extension Header can be defined. FIG. 8 illustrates an Application Descriptions Extension Header, a new GTP-U Extension Header containing application information. Referring to FIG. 8, a terminal can add the OSAppId and OSId fields to a GTP-U Extension Header with the Next Extension Header Type set to Application Descriptions.

[0110] Additionally, terminals and networks can also allocate QFI field values ​​in the PDU Session Container Extension Header by considering application information.

[0111] FIG. 9 illustrates an SM Policy Association setup procedure according to one embodiment of the present disclosure.

[0112] According to one embodiment of the present disclosure, an SM (session management) Policy Association procedure can be performed between an SMF and a PCF for policy information to be applied to a PDU Session during a PDU Session creation procedure.

[0113] In step 1, SMF can send Npcf_SMPolicyControl_Create to PCF to set SM Policy policy. Of course, there is no limitation on the message name.

[0114] In Step 2, PCF can obtain information for SM Policy setting from UDR by sending and receiving UDR and Nudr_Query and Nudr_subscribe. Of course, this is not limited to message names.

[0115] In step 3, PCF starts initial spending limit report retrieval, and in step 4, PCF can decide SM Policy.

[0116] In step 5, PCF can notify that SM Policy has been set through Npcf_SMPolicyControl_Create Response, and the SM Policy information can include Application Information (OSId, OSAppId) in the information that configures QoS Rules. Of course, it is not limited to the message name.

[0117] FIG. 10 illustrates an N4 Session setup procedure according to one embodiment of the present disclosure.

[0118] According to one embodiment of the present disclosure, during a PDU Session creation procedure, the SMF may establish a UPF and an N4 Session that handle the corresponding PDU Session. In step 1, the SMF may identify a trigger for PDU Session creation or UPF relocation.

[0119] Step 2 SMF can create an N4 session context and send it to UPF via the N4 Session Establishment Request message. Of course, there are no restrictions on the message name.

[0120] According to one embodiment of the present disclosure, the N4 session context may include the following information: N4 Session ID, S-NSSAI, PDU Session Type, APN / DNN, Packet Detection Rules (PDR), Forwarding Action Rules (FAR), Multi-Access Rules (MAR), Usage Routing Rules (URR), QoS Enforcement Rules (QER), Session Reporting Rules (SRR). Of course, the present invention is not limited to the above examples.

[0121] In Step 3, UPF can transmit an extended Packet Detection Rule (PDR) to process the service data flow by using the application information transmitted by the terminal via the N4 Session Establishment Response message, distinguishing the application that generated the service data flow and mapping the service data flow QoS. Of course, this is not limited to the message name, and UPF can also transmit the extended PDR using other steps.

[0122] According to one embodiment of the present disclosure, the extended PDR is as follows, but is not limited to the following examples.

[0123] 확장된 PDR(Extension of Packet Detection Rule)AttributeDescriptionN4 Session IDIdentifies the N4 session associated to this PDR.Rule IDUnique identifier to identify this rule.PrecedenceDetermines the order, in which the detection information of all rules is applied.PacketDetectionInformationSource interfaceContains the values "access side", "core side", "SMF", "N6-LAN", "5G VN internal".UE IP addressOne IPv4 address and / or one IPv6 prefix with prefix length.Network instanceIdentifies the Network instance associated with the incoming packet.CN tunnel infoCN tunnel info on N3, N9 interfaces, i.e. F-TEID.Packet Filter SetDetails see clause 5.7.6.Application identifier Application InformationOSId and OSAppIdQoS Flow IDContains the value of 5QI or non-standardized QFI.Ethernet PDU Session InformationRefers to all the (DL) Ethernet packets matching an Ethernet PDU session.Framed Route InformationRefers to Framed Routes defined in clause 5.6.14.FQDN Filter for DNS QueryContains one or more FQDN, FQDN range, and / or any FQDN.Protocol DescriptionIndicates service protocol used by the flow.Packet replication and detection carry oninformationPacket replication skip informationContains UE address indication or N19 / N6 indication. If the packet matches the packet replication skip information, i.e. source address of the packet is the UE address or the packet has been received on the interface in the packet replication skip information, the UP function neither creates a copy of the packet nor applies the corresponding processing (i.e. FAR, QER, URR). Otherwise the UPF performs a copy and applies the corresponding processing (i.e. FAR, QER, URR).Carry on indicationInstructs the UP function to continue the packet detection process, i.e. lookup of the other PDRs.Outer header removalInstructs the UP function to remove one or more outer header(s) (e.g. IP+UDP+GTP, IP + possibly UDP, VLAN tag), from the incoming packet.Forwarding Action Rule IDThe Forwarding Action Rule ID identifies a forwarding action that has to be applied.Multi-Access Rule IDThe Multi-Access Rule ID identifies an action to be applied for handling forwarding for a MA PDU Session.List of Usage Reporting Rule ID(s)Every Usage Reporting Rule ID identifies a measurement action that has to be applied.List of QoS Enforcement Rule ID(s)Every QoS Enforcement Rule ID identifies a QoS enforcement action that has to be applied.

[0124] According to one embodiment of the present disclosure, Application Information may be added to Packet Detection Information of Packet Detection Rule of Table 1.

[0125] FIG. 11 illustrates a flowchart of a method for managing user traffic according to one embodiment of the present disclosure.

[0126] According to one embodiment of the present disclosure, UL IP packets can be subjected to QoS Flow mapping considering applications by means of extended QoS Rules in a terminal, and DL IP packets can be subjected to QoS Flow mapping considering applications by means of extended PDRs in UPF. In addition, by using the Application information of the extended GTP-U header, the network can provide differentiated services by considering the application that created the service data flow when managing the service data flow.

[0127] Fig. 12 is a drawing showing the configuration of a terminal according to an embodiment of the present disclosure.

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

[0129] According to one embodiment of the present disclosure, the transceiver (1200) 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 (1200) can receive signals via a wireless channel, output them to the processor (1220), and transmit the signals output from the processor (1220) via the wireless channel.

[0130] According to one embodiment of the present disclosure, the processor (1220) can control the terminal to perform any one of the operations of the above-described embodiments. Meanwhile, the processor (1220), the memory (1210), and the transceiver (1200) 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 (1220) and the transceiver (1200) can be electrically connected. In addition, the processor (1220) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

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

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

[0133] A network entity according to an embodiment of the present disclosure may include a processor (1320) that controls the overall operation of the network entity, a transceiver (1300) including a transmitter and a receiver, and a memory (1310). 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. 13. The network entity of FIG. 13 may include a network entity or network function included in the wireless communication system described in FIG. 1. For example, the network entity may include AMF, SMF, PCF, UDM, NEF, UDR, UDF, AUSF, AF, EASDF, NWDAF, SCP, NSSF, etc. illustrated in FIG. 1, but is not limited to the above example.

[0134] According to one embodiment of the present disclosure, the transceiver (1300) 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.

[0135] According to one embodiment of the present disclosure, the processor (1320) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (1320), the memory (1310), and the transceiver (1300) 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 (1320) and the transceiver (1300) can be electrically connected. In addition, the processor (1320) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

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

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

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

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

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

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

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

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

[0144] 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 to which the present disclosure pertains 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.

[0145] 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. A method performed by a terminal of a wireless communication system, wherein the method comprises: Step of obtaining URSP (UE route selection policy) information; A step of identifying application information that generated a data flow based on the above URSP information; A step of mapping the data flow to a predetermined quality of service (QoS) flow of a PDU (protocol data unit) session based on the identified application information; A step of inserting the identified application information into the GTP-U (GPRS tunneling protocol-User plane) extension header of the data flow; and A method comprising the step of transmitting the above data flow.

2. In paragraph 1, A method wherein the above GTP-U extension header is set to a PDU (protocol data unit) session container type.

3. In paragraph 1, A method wherein the above GTP-U extension header is set to an application descriptions type.

4. In paragraph 1, A method wherein the above application information includes operating system (OS) identification information and application identification information.

5. In paragraph 1, A method wherein the above application information is included in an application descriptor, and the application descriptor is included in a traffic descriptor.

6. In a method performed by an SMF (session management function) of a wireless communication system, the method comprises: A step of performing a UPF (user plane function) and N4 session establishment procedure associated with a PDU session for receiving data flow; A step of obtaining extended PDR (packet detection rule) information for processing data flow based on application information through the above N4 session establishment procedure; and A method comprising the step of controlling transmission of the data flow based on the extended PDR information and application information included in the data flow received through the PDU session.

7. In paragraph 6, A method wherein application information included in the above data flow is included in a GTP-U (GPRS tunneling protocol-User plane) extension header.

8. In paragraph 7, A method wherein the above GTP-U extension header is set to a PDU (protocol data unit) session container type or an application descriptions type.

9. In paragraph 6, A method wherein OS (operating system) identification information and application identification information are included in the packet detection information within the above extended PDR information.

10. In paragraph 6, the method, A step of sending an Npcf_SMPolicyControl_Create message to the PCF (policy control function) for setting the SM (session management) policy; and Including a step of receiving an Npcf_SMPolicyControl_Create Response message indicating that a SM (session management) policy policy has been set from the PCF; The above Npcf_SMPolicyControl_Create Response message includes QoS (quality of service) rule information including application information. A method wherein the above QoS rule information is used to perform QoS flow mapping considering the above application information.

11. In a terminal of a wireless communication system, the terminal, Transmitter and receiver; and At least one processor coupled to the transceiver, wherein the at least one processor comprises: Obtain URSP (UE route selection policy) information, Identify the application information that generated the data flow based on the above URSP information, Based on the identified application information, the data flow is mapped to a predetermined QoS (quality of service) flow of a PDU (protocol data unit) session, Insert the above identified application information into the GTP-U (GPRS tunneling protocol-User plane) extension header of the data flow, A terminal that transmits the above data flow.

12. In paragraph 11, The terminal wherein the above GTP-U extension header is set to a PDU (protocol data unit) session container type or an application descriptions type.

13. In paragraph 11, The above application information is a terminal including OS (operating system) identification information and application identification information.

14. In paragraph 11, A terminal wherein the above application information is included in an application descriptor, and the application descriptor is included in a traffic descriptor.

15. In the SMF (session management function) of a wireless communication system, the SMF, Transmitter and receiver; and At least one processor coupled to the transceiver, wherein the at least one processor comprises: Performs the UPF (user plane function) and N4 session establishment procedure associated with the PDU session for receiving data flow, Through the above N4 session establishment procedure, extended PDR (packet detection rule) information for processing data flow based on application information is obtained. An SMF that controls transmission of the data flow based on the extended PDR information and application information included in the data flow received through the PDU session.

Images