Method and apparatus for servicing traffic in consideration of characteristics of media in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transfer rates. A method performed by a session management function (SMF) entity in a wireless communication system may comprise the steps of: receiving an uplink (UL) protocol description from a policy control function (PCF) entity, wherein the UL protocol description is transmitted from an application function (AF) entity to the PCF entity; and transmitting the UL protocol description for UL protocol data unit (PDU) set handling of UE.

Description

Method and device for servicing traffic by considering the characteristics of media in a wireless communication system

[0001] The present disclosure relates to a communication method and device for supporting Quality of service (QoS) by considering application-level traffic characteristics in a wireless communication system.

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

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

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

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

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

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

[0008] Meanwhile, in wireless communication systems, the need for a method to service traffic by reflecting the characteristics of the media has emerged in order to perform ultra-high-speed, low-latency communication such as XR services.

[0009] The purpose of the present disclosure is to propose a method for providing a service by reflecting application-level characteristics in order to satisfy the user's perceived performance well in the case of ultra-high-speed, low-latency communication such as XR service in a wireless communication system.

[0010] According to one embodiment of the present disclosure, a method performed by a session management function (SMF) entity in a wireless communication system may include: receiving an uplink (UL) protocol description from a policy control function (PCF) entity, wherein the UL protocol description is transmitted from an application function (AF) entity to the PCF entity; and transmitting the UL protocol description for UL protocol data unit (PDU) set handling of a terminal.

[0011] Meanwhile, according to another embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may include: transmitting a PDU session formation request message; receiving a PDU session formation acceptance message including an uplink (UL) protocol description from a session management function (SMF) entity as a response to the PDU session formation request message; and triggering UL protocol data unit (PDU) set handling based on the UL protocol description.

[0012] Meanwhile, according to another embodiment of the present disclosure, in a wireless communication system, a session management function (SMF) entity may include a transceiver; and a control unit for receiving an uplink (UL) protocol description from a policy control function (PCF) entity through the transceiver, wherein the UL protocol description is transmitted from an application function (AF) entity to the PCF entity, and for controlling transmission of the UL protocol description for handling a UL protocol data unit (PDU) set of a terminal.

[0013] Meanwhile, according to another embodiment of the present disclosure, in a wireless communication system, a terminal may include a transceiver; and a control unit that transmits a PDU session formation request message through the transceiver, receives a PDU session formation acceptance message including an uplink (UL) protocol description from a session management function (SMF) entity as a response to the PDU session formation request message, and triggers UL protocol data unit (PDU) set handling based on the UL protocol description.

[0014] According to one embodiment of the present disclosure, in the case of ultra-high-speed, low-latency communication such as XR service in a wireless communication system, the service can be efficiently provided by reflecting application-level characteristics in order to well satisfy the user's perceived performance.

[0015] FIG. 1 is a diagram showing an example of a transmission path of application data in a wireless communication system according to an embodiment of the present disclosure;

[0016] FIG. 2 is a sequence diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0017] FIG. 3 is a sequence diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0018] FIG. 4 is a sequence diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0019] FIG. 5 is a sequence diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0020] FIG. 6 is a sequence diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0021] FIG. 7 is a block diagram illustrating the structure of a terminal according to an embodiment of the present disclosure;

[0022] FIG. 8 is a block diagram illustrating the structure of a network function (NF) entity according to one embodiment of the present disclosure.

[0023] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known 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 overall content of this specification.

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

[0025] The advantages and features of the present disclosure, and 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. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the present disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[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] The term '~part' used in the present embodiment means a software or hardware component, and the '~part' performs certain roles. However, the '~part' is not limited to software or hardware. The '~part' 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 '~part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~parts' may be combined into a smaller number of components and '~parts' or further separated into additional components and '~parts'. In addition, the components and '~parts' may be implemented to 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] In the present disclosure, a user equipment (UE) may be referred to as a terminal, MS (Mobile Station), cellular phone, smartphone, computer, or various electronic devices capable of performing communication functions.

[0030] Furthermore, the embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types to the embodiments of the present disclosure described below. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0031] In specifically describing the embodiments of the present disclosure, the communication system may utilize various wired or wireless communication systems, for example, the 3GPP, a wireless communication standard standardization organization, may utilize the New RAN (NR), which is a wireless access network in the 5G communication standard, and the Packet Core (5G System, or 5G Core Network, or NG Core: Next Generation Core), which is a core network. In addition, it may be applied to other communication systems with similar technical backgrounds with slight modifications within a range that does not significantly deviate from the scope of the present disclosure, and this will be possible at the discretion of a person skilled in the art of the present disclosure.

[0032] The terms used in the description of the present disclosure below to identify connection nodes, terms referring to network entities (NFs), terms referring to messages, terms referring to interfaces between NFs (Network Functions), 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.

[0033] The present disclosure provides a method and device for reflecting application-level characteristics in QoS policies and packet processing in a wireless communication system to effectively satisfy user perception performance when performing ultra-high-speed, low-latency communications such as XR services. In particular, the present disclosure relates to a method for supporting PDU SET QoS for uplink data.

[0034] Specifically, the 5G system supports network slices, and traffic for different network slices can be processed by different PDU (protocol data unit) sessions. The PDU session may refer to an association between a data network that provides a PDU connection service and a terminal. The network slice can be understood as a technology that logically configures a network as a set of network functions (NFs) to support various services with different characteristics, such as broadband communication services, massive IoT, V2X, and other mission-critical services, and separates different network slices. Therefore, even if a communication failure occurs in a network slice, the communication in other network slices is not affected, enabling the provision of stable communication services. In the present disclosure, “slice” may be used interchangeably with the term “network slice.” In such a network environment, a terminal can access multiple network slices when receiving various services. In addition, the network function (NF) may be implemented as a network element as a software instance running on hardware or as a virtualized function instantiated on an appropriate platform.

[0035] A mobile communication operator can configure the above network slices and allocate network resources suitable for specific services for each network slice or for each set of network slices. The above network resources may refer to NFs, logical resources provided by the NF, or wireless resource allocation of a base station.

[0036] For example, a mobile communication operator can configure network slice A to provide a mobile broadband service, network slice B to provide a vehicle communication service, and network slice C to provide an XR service described later. For example, in this way, a 5G network can efficiently provide a corresponding service to a terminal through a network slice specialized according to the characteristics of each service. In a 5G system, a network slice can be represented by S-NSSAI (Single-Network Slice Selection Assistance Information). The S-NSSAI can include an SST (Slice / Service Type) value and an SD (Slice Differentiator) value. The SST can indicate the characteristics of a service supported by the network slice (e.g., enhanced mobile broadband (eMBB), IoT, URLLC (ultra reliability low latency communication), V2X, XR service, etc.). The SD can be a value used as an additional identifier for a specific service referred to as SST.

[0037] Services that require services characterized by high transmission speed and low latency (HDRLL; High Data Rate Low Latency) include, for example, extended reality (XR) services, augmented reality (AR) services, virtual reality (VR) services, or cloud gaming services. The VR service is a service that provides a virtual environment implemented by a computer device using a VR headset, etc. The AR service is a service that can combine a virtual environment with the real world using location, geographic information, etc. The XR service is a service that can not only combine a real environment and a virtual environment, but also provide the user with information such as touch, hearing, and smell, thereby enhancing the user's sense of experience.

[0038] In describing the communication service providing the application-based QoS in this disclosure, the embodiments of this disclosure are described based on XR services for convenience. However, this disclosure is applicable not only to XR services but also to various data services. Therefore, it should be noted that the embodiments of this disclosure are not limited to XR services.

[0039] According to the present disclosure, when various types of XR service data, such as audio, video, and haptic, are transmitted to a user, packets corresponding to the Application Data Unit (ADU) of the Application must be transmitted to the terminal according to the characteristics of the Application to become meaningful information. In this case, if a packet belonging to an ADU is not transmitted properly or the transmission of a certain packet fails, even if the transmitted packet belonging to the ADU is transmitted to the terminal, the ADU information may not be transmitted to the user. In this case, if the packet that cannot be properly displayed to the terminal is not transmitted through the communication network even if it is transmitted, resources for transmitting unnecessary packets can be saved, which can help the performance of the communication network. In addition, when the traffic of the Application to serve the user is generated as ADUs according to the characteristics of the media, and the packets corresponding to the ADU are transmitted through the communication network, each ADU can have a correlation with each other according to the characteristics of the media. For example, in the case of a specific ADU, it contains information that is very important and absolutely necessary when sending information to the user, and in the case of some ADUs, even if the packet corresponding to the ADU is transmitted to the terminal without the important ADU, it cannot be shown to the user. In this way, the relationship and importance with other ADUs can be determined depending on the ADU. That is, for example, when packets of a certain ADU are transmitted, packets of ADUs that are lower in importance but have a higher relationship than the ADU above can be processed with a lower priority in scheduling and packet processing, so that packets can be scheduled or, if necessary, packets can be discarded. As above, by utilizing the application-level information, when processing packets, resources used in the network can be effectively used to improve the user's service experience.

[0040] The above ADU can be viewed as a collection of media units (MUs) or packet data units (PDUs) in a communication network, and thus can be called a PDU set. In describing the present disclosure, the ADU, MU, and PDU set can be used interchangeably, but can be understood as basically the same concept. However, in the case of ADU or MU, they can be viewed as units of application data transmitted outside of the communication network, and when ADU is serviced within the communication network, they can be referred to as a PDU set.

[0041] Packets corresponding to the above ADU are based on the existing packet-level QoS processing when serviced on the communication network, and application-level QoS processing is additionally applied as needed. In addition, in order to process the above application-level QoS processing on the communication network, in the case of downlink data, the PSA (PDU Session Anchor) UPF of the communication network includes some information in the GTP header of the packet according to the ADU characteristics, so that application-level QoS processing can be performed within the communication network, for example, in the UPF or RAN.

[0042] In particular, this document deals with a method for processing uplink data traffic, focusing on a method for controlling data processing according to the characteristics of the PDU Set by finding out information at the PDU Set level of uplink data traffic provided from the upper layer of the terminal, for example, PDU Set information.

[0043] FIG. 1 is a diagram illustrating an example of a transmission path of application data in a wireless communication system according to an embodiment of the present disclosure.

[0044] The example in Fig. 1 shows transmission paths through which XR data according to an XR service used by a user (user 1) is transmitted uplink from a terminal to an application function (AF) / application server (AS) via an NG-RAN (Next Generation-Radio Access Network) node and a UPF (User Plane Function).

[0045] In the present disclosure, the 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 the 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. In the drawings, reference symbols shown as Nx, such as N1, N2, N3, ..., represent known interfaces between NFs in a 5G core network (CN), and since the related description may refer to the standard specification (TS 23.501), a detailed description thereof will be omitted. In addition, since the basic related description of the handover procedure may refer to the standard specification (TS 23.502), a detailed description of the handover procedure may be omitted as necessary in the description of the present patent technology.

[0046] The wireless communication system of FIG. 1 includes a radio access network (NG-RAN) and a 5G core network (5GC). The NG-RAN (110) may be a base station (e.g., gNB, IAB (Integrated Access and Backhaul), etc.) that supports a wireless access technology in a 5G system. The NG-RAN (110) may provide XR service-related information and / or data transmitted from an AF / AS (170) of an external network via a core network (e.g., 5GC) to at least one terminal (100) including XR devices. In addition, the NG-RAN (110) may provide XR service-related information and / or data received from the at least one terminal (100) to the AF / AS ().

[0047] According to one embodiment, 5GC in FIG. 1 may include network entities such as Access and Mobility Management Function (AMF) (120), Session Management Function (SMF) (130), User Plane Function (UPF) (140), Policy Control Function (PCF) (150), etc.

[0048] The above AMF (120) is an entity for managing access and mobility of the terminal (100). The AMF (120) can serve as a terminal-core network endpoint that connects the terminal (100) to other entity(ies) of the 5GC via the NG-RAN (110). For example, the AMF (120) can perform network functions such as registration, connection, reachability, mobility management, access confirmation, authentication, and mobility event generation of the terminal (100).

[0049] The above SMF (130) can perform a management function for a PDU (Protocol Data Unit) session of the terminal (100). For example, the SMF (130) can perform a session management function through the establishment, modification, and release of sessions and the maintenance of a tunnel between the UPF (140) and the NG-RAN (110) required therefor, an IP (Internet Protocol) address allocation and management function of the terminal (100), user plane selection and control, traffic processing control in the UPF, and network functions such as charging data collection control.

[0050] The above UPF (140) performs a role of processing user data (e.g., XR data) of the terminal (100), and may perform a role of processing XR data so that the XR data generated by the terminal (100) can be transmitted to the AF / AS (170) or data received from the AF / AS (170) can be transmitted to the terminal (100). For example, the UPF (140) may perform a network function such as performing an anchor role between radio access technologies (RATs), providing a connection between a PDU session and the AF / AS, packet routing and forwarding, packet inspection, applying a user plane policy, creating a traffic usage report, buffering, etc.

[0051] The PCF (150) above is an NF that manages operator policy information for providing services in the 5G system. The NEF (160) may be responsible for externally transmitting or receiving events occurring in the 5G system and supported capabilities. For example, the NEF (160) may perform functions such as safely supplying AF / AS (170) information to the 5GC, converting internal / external information, and storing and redistributing information received from other NFs in the UDR.

[0052] The terminal (100) can connect to the NG-RAN (110) and register with the 5G system. For example, the terminal (100) can connect to the NG-RAN (110) and perform a terminal registration procedure with the AMF (120). During the registration procedure, the AMF (120) can determine a network slice available to the terminal connected to the NG-RAN (110) and allocate it to the terminal (100). The terminal (100) can select a network slice and establish a PDU session for communication with the AF / AS (170). One PDU session can include one or more QoS (Quality of Service) Flows. Each QoS Flow can provide different transmission performances required for each application service by setting different QoS parameters.

[0053] In particular, the present disclosure assumes that the terminal (100) and the NG-RAN (110) exchange capabilities for Uplink PDU Set handling of the terminal (100) at the AS (Access Stratum) level so that the terminal (100) knows whether it can apply Uplink PDU Set handling through the NG-RAN (110) node.

[0054] For example, the function corresponding to the Uplink PDU Set handling may include a function in which the terminal (100) can find out PDU Set information from uplink data traffic, a function in which all PDUs corresponding to a certain PDU Set are discarded together in uplink data traffic, or a function in which scheduling is differentiated according to the PDU Set importance by considering importance information of the PDU Set in uplink data traffic, in part or all of the functions.

[0055] The process of exchanging capabilities for handling Uplink PDU Sets of the above terminals (100) with each other is made known to each other through the process of checking the function of the terminal (100) in the NG-RAN (110) when the terminal (100) connects to the NG-RAN (110).

[0056] The above PDU Set information may include the sequence number of the PDU Set to which the PDU of the data traffic belongs, the PDU Set importance indicating the importance of the PDU Set, the total size of the PDU Set, or part or all of the sequence number for the PDU within the PDU Set.

[0057] In addition, in the present disclosure, the Uplink PDU Set handling capability of a terminal is used interchangeably with the uplink PDU Set QoS handling capability, but when a distinction is necessary, uplink PDU Set handling and uplink PDU Set QoS handling are used in a manner that they are mentioned separately.

[0058] FIG. 2 is a diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0059] According to the embodiment illustrated in FIG. 2, even if the terminal does not inform the SMF of its capability for uplink PDU set handling, in the case of a network slice used for XR, the terminal can be informed that UL PDU Set handling is required, thereby enabling the terminal to perform PDU Set handling for uplink.

[0060] Referring to FIG. 2, when a terminal (200) connects to an NG-RAN (210) as in step 0, the terminal (200) can transmit its own capability at the request of the NG-RAN (210). At this time, if the terminal (200) has the capability to process a PDU Set for uplink data, the capability of the terminal (200) can be transmitted to the NG-RAN (210). According to one embodiment, in order to notify the capability to process the PDU Set, the terminal (200) may notify the capability to discard all PDUs corresponding to one PDU Set at once when necessary for each PDU Set, or notify the capability to differentiate scheduling for each PDU Set in a congested situation depending on the importance of the PDU Set, or notify the capability to find out PDU Set information through some or all of the following.

[0061] Additionally, the terminal (200) can also know whether the NG-RAN (210) (e.g., base station) is an NG-RAN capable of processing the uplink PDU Set.

[0062] In step 1, the AF (application function) / AS (application server) (260) can transmit an AS session QoS create message or an AS session QoS update message to the PCF (230) through the NEF (250), including QoS information at the PDU Set level from which it wishes to receive service and a protocol description, which is information that can help the network find out PDU Set information. The QoS information at the PDU Set level is expressed as a PDU Set QoS parameter and can include, for example, a delay budget (PSDB) of the PDU Set, an error rate (PSER) of the PDU Set, or PDU set Integrated Handling Information (PSIHI) indicating whether all PDUs of the PDU Set are required. Protocol description may include information about the transmission protocol, such as the RTP protocol or the data encoding protocol type or encoding rate, and information about MPEG-1, H.262 / MPEG-2, H.263, H.264 / MPEG-4 AVC, HEVC, etc., which support GOP (Group of Picture).

[0063] In particular, the above PDU Set QoS parameters and Protocol description may be used separately for uplink and downlink, or may be used without distinguishing between uplink and downlink by applying the same values ​​to uplink and downlink.

[0064] Authentication can be performed at NEF (250) according to the request of step 1. If authenticated, NEF (250) can transmit to PCF (230) the received PDU Set QoS parameters and protocol description as in step 3. In step 4, PCF (230) can obtain QoS policy for PDU Set for corresponding QoS flow or media flow. QoS policy for PDU Set may be stored in PCF (230) or may be received from AS / AF (260) through the same process as steps 1 / 2 / 3.

[0065] The above process can be performed after the terminal (200) creates the corresponding PDU Session, and can be achieved through a process of updating the QoS policy for the PDU Set for the PDU Session, and the process can follow the same procedure as the general QoS policy updating process. In the present disclosure, for convenience of explanation according to one embodiment, the PDU Session establishment is described mainly after completing the steps 1 / 2 / 3 / 4, but an operation is also possible according to an embodiment in which the QoS policy for the PDU Set is updated and the corresponding QoS policy update is applied through PDU session modification to apply the updated QoS policy. In this case, the general PDU Session modification procedure can also be followed. In addition, information such as values ​​resulting from the update in the information provided to the terminal (200) and the NG-RAN (210), for example, that the QoS profile provided to the NG-RAN (210) includes PDU Set QoS parameters for uplink, that the QoS rule provided to the terminal (200) includes an indication indicating that uplink PDU Set handling is required, that the QoS rule includes a protocol description for uplink that can help the terminal (200) find out PDU Set information, or that the terminal (200) is sent a QoS profile including PDU Set QoS parameters for uplink, is transmitted during the PDU Session modification process.In the case of the above uplink protocol description or uplink PDU Set QoS parameters, the protocol description and PDU Set QoS parameters may be used for both uplink and downlink without distinguishing between uplink and downlink.

[0066] According to an embodiment, a part where a terminal (200) applies an uplink PDU Set through a PDU Session establishment process will be described. As in step 5, the terminal (200) can transmit a PDU session establishment request including XR-only network slice information to the SMF (220). The SMF (220) can request a QoS policy from the PCF (230) as in step 6. As in step 7, the SMF (220) can receive uplink PDU Set QoS parameters and uplink Protocol description to be applied to the PDU Set. The SMF (220) can transmit the uplink PDU Set QoS parameters to the NG-RAN (210) in a QoS profile including the QoS parameters for uplink as in step 9 according to the received QoS policy information. As in step 10, the SMF (220) may transmit a message to the terminal (200), for example, a QoS rule sent to the PDU Session establishment accept message, including that PDU Set handling for uplink is required or that PDU Set handling for uplink is allowed. Meanwhile, the terminal (200) that has received the QoS rule may apply uplink PDU Set handling to the corresponding QoS flow, as in step 11.Meanwhile, when the terminal (200) starts to apply uplink PDU Set handling, the terminal (200) can search for PDU Set information for uplink PDU through information such as RTP extended header generated by the upper layer for the corresponding QoS flow, and perform a process of finding out the importance value of the corresponding PDU Set, the sequence number of the PDU Set, the size information of the PDU Set, the sequence number of the PDU within the PDU Set, or whether it is the last PDU of the PDU Set. Accordingly, the terminal (200) can perform a process of requesting resources for transmitting uplink data from the NG-RAN (210) by considering the PDU Set information.

[0067] However, even if the terminal (200) receives a notification from the SMF (220) that PDU Set handling for uplink is required or PDU Set handling for uplink is permitted, if the terminal (200) does not have the capability to perform uplink PDU Set handling or if the NG-RAN (210) that the terminal (200) is accessing does not have the capability to perform uplink PDU set handling, the terminal (200) may not perform PDU Set handling for uplink data traffic and may provide service according to the handling for general PDUs.

[0068] Meanwhile, FIG. 3 is a diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0069] According to the embodiment of FIG. 3, the terminal (300) informs the SMF (320) of its capability for uplink PDU set handling and informs that UL PDU Set processing is required only for the terminal (300) having the capability, thereby enabling the terminal (300) to perform PDU Set processing for uplink.

[0070] Referring to FIG. 3, when a terminal (300) accesses an NG-RAN (310) as in step 0, the terminal (300) can transmit its own capability at the request of the NG-RAN (310). At this time, if the terminal (300) has the capability to process a PDU Set for uplink data, the capability of the terminal (300) can be transmitted to the NG-RAN (310). According to one embodiment, in order to notify the capability to process the PDU Set, the terminal (300) may notify the capability to discard all PDUs corresponding to one PDU Set at once when necessary for each PDU Set, or notify the capability to differentiate scheduling for each PDU Set in a congested situation depending on the importance of the PDU Set, or notify the capability to find out PDU Set information through some or all of the following.

[0071] Additionally, the terminal (300) can also know whether the NG-RAN (310) (e.g., base station) is an NG-RAN capable of processing the uplink PDU Set.

[0072] In step 1, the AF (application function) / AS (application server) (360) can transmit an AS session QoS create message or an AS session QoS update message to the PCF (330) through the NEF (350), including QoS information at the PDU Set level from which it wishes to receive service and a protocol description, which is information that can help the network find out PDU Set information. The QoS information at the PDU Set level is expressed as a PDU Set QoS parameter and can include, for example, a delay budget (PSDB) of the PDU Set, an error rate (PSER) of the PDU Set, or PDU set Integrated Handling Information (PSIHI) indicating whether all PDUs of the PDU Set are required. Protocol description may include information about the transmission protocol, such as the RTP protocol or the data encoding protocol type or encoding rate, and information about MPEG-1, H.262 / MPEG-2, H.263, H.264 / MPEG-4 AVC, HEVC, etc., which support GOP (Group of Picture).

[0073] In particular, the above PDU Set QoS parameters and Protocol description may be used separately for uplink and downlink, or may be used without distinguishing between uplink and downlink by applying the same values ​​to uplink and downlink.

[0074] Authentication can be performed at NEF (350) according to the request of step 1. If authenticated, NEF (350) can transmit the received PDU Set QoS parameters and protocol description to PCF (330) as in step 3. In step 4, PCF (330) can obtain QoS policy for PDU Set for corresponding QoS flow or media flow. QoS policy for PDU Set may be stored in PCF (330) or may be received from AS / AF (360) through the same process as steps 1 / 2 / 3.

[0075] The above process can be performed after the terminal (300) creates the corresponding PDU Session, and can be achieved through a process of updating the QoS policy for the PDU Set for the PDU Session, and the above process can follow the same procedure as the general QoS policy updating process. In the present disclosure, for convenience of explanation according to one embodiment, the PDU Session establishment is described after completing the steps 1 / 2 / 3 / 4, but an operation is also possible according to an embodiment in which the QoS policy for the PDU Set is updated and the corresponding QoS policy update is applied through PDU session modification in order to apply the updated QoS policy. In this case, the general PDU Session modification procedure can also be followed. In addition, information such as values ​​resulting from the update in the information provided to the terminal (300) and the NG-RAN (310), for example, that the QoS profile provided to the NG-RAN (310) includes PDU Set QoS parameters for uplink, that the QoS rule provided to the terminal (300) includes an indication indicating that uplink PDU Set handling is required, that the uplink protocol description that can help the terminal (300) find out PDU Set information is included, or that the terminal (300) is sent with a QoS profile including PDU Set QoS parameters for uplink, is transmitted during the PDU Session modification process.In the case of the above uplink protocol description or uplink PDU Set QoS parameters, the protocol description and PDU Set QoS parameters may be used for both uplink and downlink without distinguishing between uplink and downlink.

[0076] According to an embodiment, the part where the terminal (300) applies the uplink PDU Set through the PDU Session establishment process is described. As in step 5, the terminal (300) can transmit a PDU session establishment request including XR-only network slice information to the SMF (320). At this time, if the terminal (300) has a capability for uplink PDU Set handling, it can transmit an indicator indicating the capability to the SMF (320).

[0077] SMF (320) can request QoS policy from PCF (330) as in step 6. At this time, SMF (320) can transmit not only indicating that the PDU session requested from terminal (300) is a DNN or XR-only network slice, but also including capability for uplink PDU set handling of terminal (300).

[0078] Accordingly, in step 7, if there is an uplink PDU Set QoS policy for the request, the PCF (330) can transmit the PDU Set QoS parameters and the Protocol description to be applied to the PDU Set to the SMF (320). At this time, the PCF (330) can send the uplink PDU Set QoS parameters and the uplink protocol description to the SMF (320) only when the terminal (300) has the capability for uplink PDU Set handling. However, if the PCF (330) does not receive capability information for uplink PDU Set handling for the terminal (300), if there is an uplink PDU Set QoS policy, the PCF (330) can transmit the uplink PDU Set QoS parameters and the uplink protocol description to the SMF (320).

[0079] When the SMF (320) receives the uplink PDU Set QoS parameters and uplink Protocol description to be applied to the PDU Set, the SMF (320) can transmit the PDU Set QoS parameters for uplink to the QoS profile to the NG-RAN (310) as in step 9 according to the received QoS policy information. As in step 10, the SMF (320) can transmit a message to the terminal (300), for example, a PDU Session establishment accept message, including in the QoS rule that PDU Set handling for uplink is required or PDU Set handling for uplink is allowed. Meanwhile, the terminal (300) that has received the QoS rule can apply uplink PDU Set handling to the corresponding QoS flow as in step 11. Meanwhile, when the terminal (300) starts to apply uplink PDU Set handling, the terminal (300) can search for PDU Set information for uplink PDU through information such as RTP extended header generated by the upper layer for the corresponding QoS flow, and perform a process of finding out the importance value of the corresponding PDU Set, the sequence number of the PDU Set, the size information of the PDU Set, the sequence number of the PDU within the PDU Set, or whether it is the last PDU of the PDU Set. Accordingly, the terminal (300) can perform a process of requesting resources for transmitting uplink data from the NG-RAN (310) by considering the PDU Set information.

[0080] However, even if the terminal (300) receives a notification from the SMF (320) that PDU Set handling for uplink is required or that PDU Set handling for uplink is permitted, if the NG-RAN (310) that the terminal (300) is accessing does not have uplink PDU set handling capability, the terminal (300) may not perform PDU Set handling for uplink data traffic and may provide service according to handling for general PDUs.

[0081] FIG. 4 is a diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0082] According to the embodiment of FIG. 4, the terminal (400) informs the SMF (420) of its capability for uplink PDU set handling and informs that UL PDU Set processing is required only for the terminal (400) having the capability, thereby enabling the terminal (400) to perform PDU Set processing for uplink.

[0083] Referring to FIG. 4, when a terminal (400) connects to an NG-RAN (410) as in step 0, the terminal (400) can transmit its own capability at the request of the NG-RAN (410). At this time, if the terminal (400) has the capability to process a PDU Set for uplink data, the capability of the terminal (400) can be transmitted to the NG-RAN (410). According to one embodiment, in order to notify the capability to process the PDU Set, the terminal (400) may notify the capability to discard all PDUs corresponding to one PDU Set at once when necessary for each PDU Set, or notify the capability to differentiate scheduling for each PDU Set in a congested situation depending on the importance of the PDU Set, or notify the capability to find out PDU Set information through some or all of the following.

[0084] Additionally, the terminal (400) can also know whether the NG-RAN (410) (e.g., base station) is an NG-RAN capable of processing the uplink PDU Set.

[0085] In step 1, the AF (application function) / AS (application server) (460) can transmit an AS session QoS create message or an AS session QoS update message to the PCF (430) through the NEF (450), including QoS information at the PDU Set level from which it wishes to receive service and a protocol description, which is information that can help the network find out PDU Set information. The QoS information at the PDU Set level is expressed as a PDU Set QoS parameter and can include, for example, a delay budget (PSDB) of the PDU Set, an error rate (PSER) of the PDU Set, or PDU set Integrated Handling Information (PSIHI) indicating whether all PDUs of the PDU Set are required. Protocol description may include information about the transmission protocol, such as the RTP protocol or the data encoding protocol type or encoding rate, and information about MPEG-1, H.262 / MPEG-2, H.263, H.264 / MPEG-4 AVC, HEVC, etc., which support GOP (Group of Picture).

[0086] In particular, the above PDU Set QoS parameters and Protocol description may be used separately for uplink and downlink, or may be used without distinguishing between uplink and downlink by applying the same values ​​to uplink and downlink.

[0087] Authentication can be performed at NEF (450) according to the request of step 1. If authenticated, NEF (450) can transmit the received PDU Set QoS parameters and protocol description to PCF (430) as in step 3. In step 4, PCF (430) can obtain QoS policy for PDU Set for corresponding QoS flow or media flow. QoS policy for PDU Set may be stored in PCF (430) or may be received from AS / AF (460) through the same process as steps 1 / 2 / 3.

[0088] The above process can be performed after the terminal (400) creates the corresponding PDU Session, and can be achieved through a process of updating the QoS policy for the PDU Set for the PDU Session, and the above process can follow the same procedure as the general QoS policy updating process. In the present disclosure, for convenience of explanation according to one embodiment, the PDU Session establishment is described mainly after completing the steps 1 / 2 / 3 / 4, but an operation is also possible according to an embodiment in which the QoS policy for the PDU Set is updated and the corresponding QoS policy update is applied through PDU session modification to apply the updated QoS policy. In this case, the general PDU Session modification procedure can also be followed. In addition, information such as values ​​resulting from the update in the information provided to the terminal (400) and the NG-RAN (410), for example, that the QoS profile provided to the NG-RAN (410) includes PDU Set QoS parameters for uplink, that the QoS rule provided to the terminal (400) includes an indication indicating that uplink PDU Set handling is required, that the uplink protocol description that can help the terminal (400) find out PDU Set information is included, or that the terminal (400) is sent a QoS profile including PDU Set QoS parameters for uplink, is transmitted during the PDU Session modification process.In the case of the above uplink protocol description or uplink PDU Set QoS parameters, the protocol description and PDU Set QoS parameters may be used for both uplink and downlink without distinguishing between uplink and downlink.

[0089] According to an embodiment, the part where the terminal (400) applies the uplink PDU Set through the PDU Session establishment process is described. As in step 5, the terminal (400) can transmit a PDU session establishment request including XR-only network slice information to the SMF (420). At this time, if the terminal (400) has a capability for uplink PDU Set handling, it can transmit an indicator indicating the capability to the SMF (420).

[0090] SMF (420) can request QoS policy from PCF (430) as in step 6. At this time, SMF (420) can transmit not only indicating that the PDU session requested from terminal (400) is a DNN or XR-only network slice, but also including capability for uplink PDU set handling of terminal (400).

[0091] Accordingly, in step 7, if there is an uplink PDU Set QoS policy for the request, the PCF (430) can transmit the PDU Set QoS parameters and the Protocol description to be applied to the PDU Set to the SMF (420). At this time, the PCF (430) can send the uplink PDU Set QoS parameters and the uplink protocol description to the SMF (420) only when the terminal (400) has the capability for uplink PDU Set handling. However, if the PCF (430) does not receive capability information for uplink PDU Set handling for the terminal (400), if there is an uplink PDU Set QoS policy, the PCF (430) can transmit the uplink PDU Set QoS parameters and the uplink protocol description to the SMF (420).

[0092] When the SMF (420) receives the uplink PDU Set QoS parameters and uplink Protocol description to be applied to the PDU Set, the SMF (420) can transmit the PDU Set QoS parameters for uplink to the QoS profile to the NG-RAN (410) as in step 9 according to the received QoS policy information. As in step 10, the SMF (420) transmits a message to the terminal (400), for example, a PDU Session establishment accept message, including in the QoS rule that PDU Set handling for uplink is required or PDU Set handling for uplink is allowed. Alternatively, the SMF (420) can transmit the message to the terminal (400) by including the uplink protocol description.

[0093] Meanwhile, the terminal (400) that receives information that PDU Set handling for uplink is required or that PDU Set handling for uplink is allowed or receives uplink protocol description as described above can recognize that uplink PDU Set handling can be applied to the corresponding QoS flow as in step 13. Meanwhile, when the terminal (400) starts to apply uplink PDU Set handling as in step 14, the terminal (400) searches for PDU Set information for uplink PDU through information such as RTP extended header generated in the upper layer with reference to the protocol description information received for the corresponding QoS flow, and can perform a process of finding out the importance value of the corresponding PDU Set, the sequence number of the PDU Set, the size information of the PDU Set, the sequence number of the PDU within the PDU Set, or whether it is the last PDU of the PDU Set. Accordingly, the terminal (400) can perform a process of requesting resources for transmitting uplink data from the NG-RAN (410) by considering the PDU Set information.

[0094] However, even if the terminal (400) receives a notification from the SMF (420) that PDU Set handling for uplink is required or PDU Set handling for uplink is allowed, or receives an uplink protocol description, if the NG-RAN (310) that the terminal is accessing does not have uplink PDU set handling capability, the terminal (400) may not perform PDU Set handling for uplink data traffic and may provide service according to handling for general PDUs.

[0095] Meanwhile, FIG. 5 is a diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0096] According to the embodiment of FIG. 5, even if the terminal (500) does not inform the SMF (520) of its capability for uplink PDU set handling, in the case of a network slice used for XR, the terminal (500) is informed that UL PDU Set processing is required, so that the terminal (500) can perform PDU Set processing for uplink.

[0097] Referring to FIG. 5, when a terminal (500) accesses an NG-RAN (510) as in step 0, the terminal (500) can transmit its own capability at the request of the NG-RAN (510). At this time, if the terminal (500) has the capability to process a PDU Set for uplink data, the capability of the terminal (500) can be transmitted to the NG-RAN (510). According to one embodiment, in order to notify the capability to process the PDU Set, the terminal (500) may notify the capability to discard all PDUs corresponding to one PDU Set at once when necessary for each PDU Set, or notify the capability to differentiate scheduling for each PDU Set in a congested situation depending on the importance of the PDU Set, or notify the capability to find out PDU Set information through some or all of the following.

[0098] Additionally, the terminal (500) can also know whether the NG-RAN (510) (e.g., base station) is an NG-RAN capable of processing the uplink PDU Set.

[0099] In step 1, the application AF (application function) / AS (application server) (560) can transmit an AS session QoS create message or an AS session QoS update message to the PCF (530) through the NEF (550), including QoS information at the PDU Set level from which it wishes to receive service and a protocol description, which is information that can help the network find out PDU Set information. The QoS information at the PDU Set level is expressed as a PDU Set QoS parameter and can include, for example, a delay budget (PSDB) of the PDU Set, an error rate (PSER) of the PDU Set, or PDU set Integrated Handling Information (PSIHI) indicating whether all PDUs of the PDU Set are required. Protocol description may include information about the transmission protocol, such as the RTP protocol or the data encoding protocol type or encoding rate, and information about MPEG-1, H.262 / MPEG-2, H.263, H.264 / MPEG-4 AVC, HEVC, etc., which support GOP (Group of Picture).

[0100] In particular, the above PDU Set QoS parameters and Protocol description may be used separately for uplink and downlink, or may be used without distinguishing between uplink and downlink by applying the same values ​​to uplink and downlink.

[0101] Authentication can be performed at NEF (550) according to the request of step 1. If authenticated, NEF (550) can transmit the received PDU Set QoS parameters and protocol description to PCF (530) as in step 3. In step 4, PCF (530) can obtain QoS policy for PDU Set for corresponding QoS flow or media flow. QoS policy for PDU Set may be stored in PCF (530) or may be received from AS / AF (560) through the same process as steps 1 / 2 / 3.

[0102] The above process can be performed after the terminal (500) creates the corresponding PDU Session, and can be achieved through a process of updating the QoS policy for the PDU Set for the PDU Session, and the above process can follow the same procedure as the general QoS policy updating process. In the present disclosure, for convenience of explanation according to one embodiment, the PDU Session establishment is described after completing the steps 1 / 2 / 3 / 4, but an operation is also possible according to an embodiment in which the QoS policy for the PDU Set is updated and the corresponding QoS policy update is applied through PDU session modification in order to apply the updated QoS policy. In this case, the general PDU Session modification procedure can also be followed. In addition, information such as values ​​resulting from the update in the information provided to the terminal (500) and the NG-RAN (510), for example, that the QoS profile provided to the NG-RAN (510) includes PDU Set QoS parameters for uplink, that the QoS rule provided to the terminal (500) includes an indication indicating that uplink PDU Set handling is required, that the uplink protocol description that can help the terminal (500) find out PDU Set information is included, or that the terminal (500) is sent a QoS profile including PDU Set QoS parameters for uplink, is transmitted during the PDU Session modification process.In the case of the above uplink protocol description or uplink PDU Set QoS parameters, the protocol description and PDU Set QoS parameters may be used for both uplink and downlink without distinguishing between uplink and downlink.

[0103] According to an embodiment, the part where the terminal (500) applies the uplink PDU Set through the PDU Session establishment process is described. As in step 5, the terminal (500) can transmit a PDU session establishment request including XR-only network slice information to the SMF (520).

[0104] SMF (520) can request QoS policy from PCF (530) as in step 6. At this time, SMF (520) can transmit information including information indicating that the PDU session requested from the terminal (500) is a DNN or XR-only network slice.

[0105] Therefore, in step 7, PCF (530) can transmit to SMF (520) uplink PDU Set QoS parameters and uplink protocol description if there is an uplink PDU Set QoS policy for the request.

[0106] When the SMF (520) receives the uplink PDU Set QoS parameters and uplink Protocol description to be applied to the PDU Set, the SMF (520) can transmit the PDU Set QoS parameters for uplink to the QoS profile to the NG-RAN (510) as in step 9 according to the received QoS policy information. As in step 10, the SMF (520) can transmit a message to the terminal (500), for example, a PDU Session establishment accept message, including in the QoS rule that PDU Set handling for uplink is required or PDU Set handling for uplink is allowed. Alternatively, the SMF (520) can transmit the uplink PDU Set QoS parameters to the terminal (500) by including them in the message that the SMF (520) transmits to the terminal (500).

[0107] Meanwhile, the terminal (500) that receives information that PDU Set handling for uplink is required or that PDU Set handling for uplink is allowed or that uplink PDU Set QoS parameters are received as described above can recognize that uplink PDU Set handling can be applied to the corresponding QoS flow as in step 13. Meanwhile, when the terminal (500) starts to apply uplink PDU Set handling as in step 14, the terminal (500) searches for PDU Set information for uplink PDU through information such as RTP extended header generated in the upper layer for the corresponding QoS flow, and can perform a process of finding out the importance value of the corresponding PDU Set, the sequence number of the PDU Set, the size information of the PDU Set, the sequence number of the PDU within the PDU Set, or whether it is the last PDU of the PDU Set. Accordingly, the terminal (500) can perform a process of requesting resources for transmitting uplink data from the NG-RAN (510) by considering the PDU Set information.

[0108] However, even if the terminal (500) receives a notification from the SMF (520) that PDU Set handling for uplink is required or PDU Set handling for uplink is allowed, or receives uplink QoS parameters, if the terminal (500) does not have the capability to perform uplink PDU Set handling, or if the NG-RAN (510) that the terminal (500) is accessing does not have the capability to perform uplink PDU set handling, the terminal (500) may not perform PDU Set handling for uplink data traffic and may provide service according to the handling for general PDUs.

[0109] Meanwhile, FIG. 6 is a diagram illustrating a method for triggering a terminal to provide PDU Set QoS for uplink data traffic in a wireless communication system according to an embodiment of the present disclosure.

[0110] According to the embodiment of FIG. 6, even if the terminal (600) does not inform the SMF (620) of its capability for uplink PDU set handling, in the case of a network slice used for XR, the terminal (600) is informed that UL PDU Set processing is required, so that the terminal (600) can perform PDU Set processing for uplink.

[0111] Referring to FIG. 6, when a terminal (600) accesses an NG-RAN (610) as in step 0, the terminal (600) can transmit its own capability at the request of the NG-RAN (610). At this time, if the terminal (600) has the capability to process a PDU Set for uplink data, the capability of the terminal (600) can be transmitted to the NG-RAN (610). According to one embodiment, in order to notify the capability to process the PDU Set, the terminal (600) may notify the capability to discard all PDUs corresponding to one PDU Set at once when necessary for each PDU Set, or notify the capability to differentiate scheduling for each PDU Set in a congested situation depending on the importance of the PDU Set, or notify the capability to find out PDU Set information through some or all of the following.

[0112] Additionally, the terminal (600) can also know whether the NG-RAN (610) (e.g., base station) is an NG-RAN capable of processing the uplink PDU Set.

[0113] In step 1, the application AF (application function) / AS (application server) (660) can transmit an AS session QoS create message or an AS session QoS update message to the PCF (630) through the NEF (650), including QoS information at the PDU Set level from which it wishes to receive service and a protocol description, which is information that can help the network find out PDU Set information. The QoS information at the PDU Set level is expressed as a PDU Set QoS parameter and can include, for example, a delay budget (PSDB) of the PDU Set, an error rate (PSER) of the PDU Set, or PDU set Integrated Handling Information (PSIHI) indicating whether all PDUs of the PDU Set are required. Protocol description may include information about the transmission protocol, such as the RTP protocol or the data encoding protocol type or encoding rate, and information about MPEG-1, H.262 / MPEG-2, H.263, H.264 / MPEG-4 AVC, HEVC, etc., which support GOP (Group of Picture).

[0114] In particular, the above PDU Set QoS parameters and Protocol description may be used separately for uplink and downlink, or may be used without distinguishing between uplink and downlink by applying the same values ​​to uplink and downlink.

[0115] Authentication can be performed at NEF (650) according to the request of step 1. If authenticated, NEF (650) can transmit the received PDU Set QoS parameters and protocol description to PCF (630) as in step 3. In step 4, PCF (630) can obtain QoS policy for PDU Set for corresponding QoS flow or media flow. QoS policy for PDU Set may be stored in PCF (630) or may be received from AS / AF (660) as in steps 1 / 2 / 3.

[0116] The above process can be performed after the terminal (600) creates the corresponding PDU Session, and can be achieved through a process of updating the QoS policy for the PDU Set for the PDU Session, and the above process can follow the same procedure as the general QoS policy updating process. In the present disclosure, for convenience of explanation according to one embodiment, the PDU Session establishment is described after completing the steps 1 / 2 / 3 / 4, but an operation is also possible according to an embodiment in which the QoS policy for the PDU Set is updated and the corresponding QoS policy update is applied through PDU session modification to apply the updated QoS policy. In this case, the general PDU Session modification procedure can also be followed. In addition, information such as values ​​resulting from the update in the information provided to the terminal (600) and the NG-RAN (610), for example, that the QoS profile provided to the NG-RAN (610) includes PDU Set QoS parameters for uplink, that the QoS rule provided to the terminal (600) includes an indication indicating that uplink PDU Set handling is required, that the uplink protocol description that can help the terminal (600) find out PDU Set information is included, or that the terminal (600) is sent a QoS profile including PDU Set QoS parameters for uplink, is transmitted during the PDU Session modification process.In the case of the above uplink protocol description or uplink PDU Set QoS parameters, the protocol description and PDU Set QoS parameters may be used for both uplink and downlink without distinguishing between uplink and downlink.

[0117] According to an embodiment, the part where the terminal (600) applies the uplink PDU Set through the PDU Session establishment process is described. As in step 5, the terminal (600) can transmit a PDU session establishment request including XR-only network slice information to the SMF (620).

[0118] In this way, when a PDU Session is created as in step 6, and downlink data traffic occurs in the terminal (600) as in step 7, and a value including PDU Set information is included in the extended header of the RTP header of the received data, the terminal (600) can indirectly detect that PDU Set handling has been applied to the downlink data as in step 8. Accordingly, the terminal (600) indirectly knows that PDU Set handling for uplink is necessary, and when the terminal (600) starts to apply uplink PDU Set handling as in step 9, the terminal can search for PDU Set information for uplink PDU through information such as RTP extended header created in the upper layer for the corresponding QoS flow, and perform a process of finding out the importance value of the corresponding PDU Set, the sequence number of the PDU Set, the size information of the PDU Set, the sequence number of the PDU within the PDU Set, or whether it is the last PDU of the PDU Set. Accordingly, the terminal (600) can perform a process of requesting resources for transmitting uplink data from the NG-RAN by considering the above PDU Set information.

[0119] However, even if the terminal (600) detects that PDU Set handling for uplink is required, if the NG-RAN (610) that the terminal (600) is accessing does not have uplink PDU set handling capability, the terminal (600) does not perform PDU Set handling for uplink data traffic and provides service according to handling for general PDU.

[0120] Meanwhile, FIG. 7 is a drawing illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0121] Referring to FIG. 7, the terminal may include a transceiver (710), a control unit (720), and a storage unit (730). In the present invention, the control unit (720) may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0122] The transceiver (710) can transmit and receive signals with other network entities. For example, the transceiver (710) can transmit terminal capability information to a base station and transmit a PDU session formation request message to an SMF.

[0123] The control unit (720) can control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the control unit (720) can control the signal flow between each block to perform operations according to the flowchart described above.

[0124] The storage unit (730) can store at least one of the information transmitted and received through the transmission and reception unit (710) and the information generated through the control unit (920).

[0125] FIG. 8 is a diagram illustrating a network function entity according to an embodiment of the present disclosure. The network function entity of FIG. 8 may be any one of a function entity / server such as AMF, SMF, PCF, UPF, NEF, or AF / AS according to an embodiment of the present disclosure.

[0126] Referring to FIG. 8, the network function entity may include a transceiver (810), a control unit (820), and a storage unit (830). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0127] The transceiver (810) can transmit and receive signals with other network entities. According to one embodiment of the present disclosure, in the case of SMF, the transceiver (810) can receive a PDU session formation request message from a terminal and transmit and receive a QoS policy formation request / response with the PCF.

[0128] The control unit (820) can control the overall operation of the network function entity according to the embodiment proposed in the present invention. For example, the control unit (820) can control the signal flow between each block to perform operations according to the flowchart described above.

[0129] The storage unit (830) can store at least one of the information transmitted and received through the transceiver unit (810) and the information generated through the control unit (820). In the specific embodiments of the present disclosure described above, the components included in the invention are expressed singularly or plurally according to the specific embodiments presented. However, the singular or plural expressions are selected appropriately for the presented situation for the convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural may be composed of singular elements, or even components expressed in singular may be composed of plural elements.

[0130] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are only specific examples to easily explain the technical contents of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modified examples based on the technical idea of ​​the present disclosure are possible. In addition, the above-mentioned respective embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined with each other to operate a base station and a terminal. In addition, other modified examples based on the technical idea of ​​the above-mentioned embodiments can be implemented in various systems such as an FDD LTE system, a TDD LTE system, a 5G or NR system, etc.

Claims

1. A method performed by a session management function (SMF) entity in a wireless communication system, A step of receiving an uplink (UL) protocol description from a policy control function (PCF) entity, wherein the UL protocol description is transmitted from an application function (AF) entity to the PCF entity; and A method comprising: a step of transmitting the UL protocol description for handling a UL protocol data unit (PDU) set of a terminal; 2. In paragraph 1, The above UL protocol description is transmitted along with the quality of service (QoS) rule. A method characterized in that the above QoS rule is associated with a PDU set QoS parameter.

3. In paragraph 2, A method characterized in that the UL protocol description and the PDU set QoS parameter are received from the AF entity via the PCF entity.

4. In paragraph 1, The above UL protocol description is, A method characterized in that it is used for PDU set handling in uplink transmission of the above terminal.

5. In a method performed by a terminal in a wireless communication system, Step of transmitting a PDU session formation request message; A step of receiving a PDU session formation acceptance message including an uplink (UL) protocol description from a session management function (SMF) entity as a response to the PDU session formation request message; and A method comprising: a step of triggering UL protocol data unit (PDU) set handling based on the above UL protocol description; 6. In paragraph 5, The above UL protocol description is transmitted along with the quality of service (QoS) rule. A method characterized in that the above QoS rule is associated with a PDU set QoS parameter.

7. In paragraph 5, A method characterized in that the UL protocol description and the PDU set QoS parameter are received from the AF entity via the PCF entity.

8. In a wireless communication system, for a session management function (SMF) entity, Transmitter and receiver; and Receiving an uplink (UL) protocol description from a policy control function (PCF) entity through the transceiver, wherein the UL protocol description is transmitted from an application function (AF) entity to the PCF entity, and An SMF entity including a control unit for controlling transmission of the UL protocol description for handling a UL protocol data unit (PDU) set of a terminal.

9. In paragraph 8, The above UL protocol description is transmitted along with the quality of service (QoS) rule. An SMF entity characterized in that the above QoS rule is associated with a PDU set QoS parameter.

10. In paragraph 9, An SMF entity, characterized in that the UL protocol description and the PDU set QoS parameter are received from the AF entity via the PCF entity.

11. In paragraph 8, The above UL protocol description is, An SMF entity characterized by being used for PDU set handling in uplink transmission of the above terminal.

12. In a terminal in a wireless communication system, Transmitter and receiver; and Transmitting a PDU session formation request message through the above-mentioned transceiver, In response to the above PDU session formation request message, a PDU session formation acceptance message including an uplink (UL) protocol description is received from a session management function (SMF) entity, A terminal including a control unit that triggers UL protocol data unit (PDU) set handling based on the above UL protocol description.

13. In paragraph 12, The above UL protocol description is transmitted along with the quality of service (QoS) rule. A terminal characterized in that the above QoS rule is associated with a PDU set QoS parameter.

14. In paragraph 12, A terminal characterized in that the UL protocol description and the PDU set QoS parameter are received from the AF entity via the PCF entity.

Images