Method and apparatus for managing session in wireless communication system

The method addresses network congestion in XR applications by dividing packets into PDU sets based on service characteristics and optimizing QoS, ensuring efficient processing of both downlink and uplink traffic in XR applications, thereby enhancing performance and user experience.

WO2024232691A1PCT designated stage expired Publication Date: 2024-11-14SAMSUNG ELECTRONICS CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006269
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-09
Filing Date
2024-05-09
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in efficiently managing network congestion, particularly in Metaverse/XR applications, where large amounts of traffic need to be processed, and existing methods mainly focus on downlink traffic transmission without effectively handling uplink traffic considering service characteristics.

Method used

The proposed method involves dividing packets with different media characteristics into PDU sets based on service traffic characteristics, using RTP bundling and GTP-U headers to provide PDU set information to the RAN for scheduling, and updating policy information to optimize QoS for XR services.

Benefits of technology

This approach effectively handles network congestion by prioritizing and scheduling packets based on service characteristics, ensuring efficient processing of both downlink and uplink traffic in XR applications, thereby enhancing the performance and user experience in high-frame and high-capacity services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006269_14112024_PF_FP_ABST
    Figure KR2024006269_14112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method performed by a policy control function (PCF) entity in a wireless communication system, according to the present disclosure, may comprise the steps of: receiving, from an application function (AF) entity by using a network exposure function (NEF) entity, a first message including a packet data unit (PDU) set handling indicator and PDU set handling information for a multiplexing service; determining, on the basis of the first message, whether multiplexing service-based PDU set handling is supported; and transmitting, to the AF entity by using the NEF entity, a second message indicating whether multiplexing service-based PDU set handling is supported.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for managing sessions in a wireless communication system

[0001] The present disclosure relates to a wireless communication system. Specifically, the disclosure relates to a method and device for generating information for processing PDUs (protocol data units) with the same characteristics as a set when packets of different media types are transmitted through a single service floor in a wireless communication system, taking into account service characteristics. The disclosure also relates to a method and device for supporting RAN scheduling based on PDU sets.

[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] In the case of metaverse and extended reality (XR) applications, since terminals must transmit a large amount of traffic via downlink / uplink, effectively processing the traffic is a significant technical issue that must be resolved, unlike existing applications. Unlike existing studies that have mainly focused on effectively transmitting downlink traffic to terminals, metaverse / XR traffic is a new challenge that must be solved by effectively processing downlink traffic by considering the service characteristics of each packet. Therefore, in the present disclosure, when congestion occurs during processing in a network entity (e.g., RAN), instead of randomly dropping packets in the scheduler to resolve the congestion situation, in the XR service, the traffic characteristic information provided by the current service is utilized through the actual application function (AF) entity or application server (AS), and when packets are dropped, packets with the same characteristics are processed as units (e.g., PDU set) and the like are considered, thereby providing a method for efficiently processing this when network congestion occurs.In addition, in order to process packets in UPF by utilizing service characteristics rather than simply forwarding existing data using 5-tuple as above, the method of recognizing and extracting RTP (Real-time Transport Protocol) and NAL (Network Adaptation Layer) unit header information of actual data and classifying the same packets into groups (PDU sets) based on the information, and generating PDU set information based on the extracted information or information received from AS and providing it to RAN through GTP (GPRS Tunnelling Protocol)-U header to perform scheduling based on the information is provided.

[0009] According to one aspect of the present disclosure, a device and method for generating information for processing packets having the same characteristics by taking into account service traffic characteristics in a communication system can be provided.

[0010] According to one aspect of the present disclosure, a device and method may be provided for transmitting a service request including information (PDU set information) for processing packets having the same characteristics by considering service traffic characteristics when packets having different media characteristics are transmitted through a single service floor in a communication system and indicator information (RTP Bundling indication) indicating that packets having different media characteristics are transmitted within a single service floor, from an AF to a PCF, and generating policy information including QoS update of an RTP bundled service floor, etc., based on the RTP bundling service request.

[0011] According to one aspect of the present disclosure, a device and method for generating policy information updates and corresponding PCF event reporting information based on QoS monitoring reporting information while using a service using an RTP bundled single service floor may be provided.

[0012] According to one embodiment of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system may include the steps of: receiving a first message including a policy update requirement associated with an AF session from an application function (AF) through a network exposure function (NEF) entity; determining whether to accept the policy update requirement based on packet data unit (PDU) set information and information about an RTP bundling service request in the first message; transmitting, to the AF through the NEF entity, a second message including an indicator indicating that the policy update request has been accepted if the policy update requirement is determined to be accepted; and transmitting, to a session management function (SMF) entity, a third message including an indicator indicating the policy update requirement.

[0013] According to embodiments proposed in the present disclosure, in a wireless communication system, when providing a service composed of one or more media, the AF may provide a protocol descriptor including characteristic information of one or more media constituting the service floor in order to request support for PDU set-based scheduling from the RAN in consideration of the characteristics of the service. The PCF may determine a policy update for the protocol descriptor including the characteristic information of the media, and may provide the SMF with a PCC rule including information for generating PDU set information or recognizing PDU set information transmitted in a packet header when processing packets within the service floor in the UPF. In the AF, when an RTP bundling service request is transmitted to the PCF based on a requirement to transmit one or more media types, such as WebRTC, within a single service floor, the PCF determines whether to accept the request based on the information, and if the requirement of the AF is not accepted, a policy information update may be performed using an individual service floor for each media type, and the result value for the request may be transmitted to the AF. If all packets within a single service floor are transmitted from AS to UPF through an extension header containing PDU set information, the PDU set information is included in the GTP-U extension header and transmitted to RAN. Alternatively, if one or more media packets within a service floor do not receive PDU set information from AS, the UPF performs packet detection and generation operations to generate PDU set information. The relevant information for this can be transmitted from PCF to SMF through PCC rules.To this end, the PDU set information in the service requirement message of the AF or in the protocol descriptor can include indicator information such as whether all packets in the corresponding service floor support it. The QoS monitoring reporting information of the corresponding QoS floor through QoS monitoring such as data rate monitoring can be requested to the PCF through the service requirement message through the RTP bundling service, and the PCF can make a decision on whether to continue the service through RTP bundling based on the result of the reporting. Through this, when a high-frame and high-capacity application traffic service such as an XR service occurs in an actual network, an appropriate XR service application service is provided according to the network situation by considering the service characteristics of the packet (such as importance between packets), and a device and method for providing a scheduling service based on the service characteristics (PDU set information) of the packet even in a service where packets of different media types such as RTP bundling are multiplexed into a single service floor are provided.

[0014] FIG. 1 illustrates a network structure and interface of a wireless communication system according to one embodiment of the present disclosure.

[0015] FIG. 2 illustrates an operation for performing RAN scheduling based on PDU set handling of different media type packets within a single service floor in a wireless communication system according to an embodiment of the present disclosure.

[0016] FIG. 3 illustrates an operation when a PCF entity rejects acceptance of a service request transmitted from an AF entity in a wireless communication system according to an embodiment of the present disclosure.

[0017] FIG. 4 is a diagram illustrating a policy update operation based on QoS monitoring reporting information through QoS monitoring during service use through RTP bundling in a wireless communication system according to an embodiment of the present disclosure.

[0018] Figure 5 illustrates an operation for performing PDU set-based RAN scheduling operation for packets transmitted through one or more service floors having the same media type.

[0019] FIG. 6 illustrates a flowchart for explaining a method for supporting scheduling for an RTP bundled service using a protocol description including RTP bundling related information transmitted via an AF entity in a wireless communication system according to an embodiment of the present disclosure.

[0020] FIG. 7 is a flowchart illustrating a method for supporting a PDU set-based RAN scheduling operation when a PCF entity rejects acceptance of an RTP bundling-based service request transmitted from an AF entity in a wireless communication system according to an embodiment of the present disclosure.

[0021] FIG. 8 illustrates a flowchart for explaining a method for supporting policy updates based on QoS monitoring reporting values ​​while using an RTP bundled base service in a wireless communication system according to an embodiment of the present disclosure.

[0022] Figure 9 illustrates a flowchart illustrating a method for supporting one or more individual service floor-based services having the same media type.

[0023] FIG. 10 is a diagram illustrating the structure of a terminal according to an embodiment of the present disclosure.

[0024] FIG. 11 is a diagram illustrating the structure of a base station according to an embodiment of the present disclosure.

[0025] FIG. 12 is a diagram illustrating the structure of a network function (or network entity) according to one embodiment of the present disclosure.

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

[0027] In describing this disclosure, descriptions of technical details that are well-known in the technical field to which this disclosure pertains and are not directly related to this disclosure will be omitted. This is to avoid obscuring the gist of this disclosure by omitting unnecessary explanations and to convey it more clearly. Furthermore, the terms described below are defined based on their functions in this disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification as a whole.

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

[0029] Hereinafter, a base station (BS) is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B (or an xNode B (where x is an alphabet including g or e)), a wireless access unit, a base station controller, a satellite, an airborn, or a node on a network. A user equipment (UE) may include a mobile station (MS), a vehicle, a satellite, an airborn, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) is a wireless transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) is a wireless transmission path of a signal transmitted from a terminal to an air station. Additionally, a sidelink (SL) may exist, which means a wireless transmission path of a signal transmitted from a terminal to another terminal.

[0030] In addition, although LTE, LTE-A, or 5G systems may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, this may include 5G-Advance or NR-Advance, or 6th generation mobile communication technology (6G) developed after 5G mobile communication technology (or new radio, NR), and the 5G described below may also include the 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 range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

[0031] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings 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 flowchart 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 flowchart 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).

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

[0033] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), 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 or may be configured to play one or more processors. Therefore, as an example, the '~ part' 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 '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0034] 3GPP, responsible for cellular mobile communications standards, is standardizing a new core network architecture called 5G Core (5GC) to facilitate the evolution of 4G LTE systems to 5G systems. Compared to the Evolved Packet Core (EPC), the network core for 4G, 5GC supports the following differentiated features:

[0035] 5GC introduces the Network Slice feature. As a requirement of 5G, 5GC must support a variety of terminal types and services, such as enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine Type Communications (mMTC). These terminals and services each have different requirements for the core network. For example, eMBB services may require high data rates, while URLLC services may require high reliability and low latency. To meet these diverse service requirements, Network Slice technology has been proposed.

[0036] Network slicing can refer to a method of virtualizing a single physical network to create multiple logical networks (e.g., network slices). An activated network slice can be called a network slice instance, and each network slice instance (NSI) can have different characteristics. By configuring a network function (NF) for each NSI according to its characteristics, a mobile carrier can satisfy various service requirements according to terminals / services. For example, a mobile carrier can efficiently support various 5G services (e.g., eMBB, URLLC, or mMTC) by allocating an NSI according to the characteristics of the service required for each terminal.

[0037] 5GC can easily support the network virtualization paradigm by separating the mobility management function from the session management function. In 4G LTE, all terminals can receive services from the network through signaling exchanges with a single core entity called the mobility management entity (MME), which is responsible for registration, authentication, mobility management, and session management. In 5G, the number of terminals (including MTC terminals) will explode, and the mobility and traffic / session characteristics that must be supported depending on the terminal type will become more specialized. Therefore, supporting all functions from a single entity (such as the MME) will inevitably reduce scalability by adding entities for each required function. Therefore, various functions are being developed based on a structure that separates the mobility management function from the session management function to improve scalability in terms of the functional / implementation complexity and signaling load of the core entity responsible for the control plane.

[0038] According to one embodiment of the present disclosure, a method performed by a PCF entity that supports RAN (radio access network) scheduling based on a PDU (protocol data unit) set, which is a unit of packets classified by traffic characteristics among download packets in a wireless communication system, may be proposed, including an operation of receiving, from an AF, a Protocol description message including RTP payload type information such as codec information (Codec type), sampling rate, etc., and an indicator (PDU set information supported for all packets within service flow) indicating whether packets within a corresponding service flow include PDU set information in an RTP header extension, and an operation of transmitting, to a UPF entity, a Session Establishment Request message including a PDR (packet detection rule) for processing a generation rule of PDU set information and a related parameter of the PDU set information.

[0039] According to the present disclosure, a method performed by a policy control function (PCF) entity that supports RAN (radio access network) scheduling based on a PDU (protocol data unit) set, which is a unit of packets classified by traffic characteristics among download packets of a wireless communication network, may be proposed, including an operation of receiving a policy authorization request message including PDU set handling information and PDU set information related parameters from a network exposure function (NEF), an operation of generating a PDU set information generation rule based on the PDU set handling information and the PDU set information related parameters, and an operation of transmitting a policy control update message including the PDU set information generation rule and the PDU set information related parameters to a session management function (SMF) entity.

[0040] According to one embodiment of the present disclosure, a method performed by a Policy Control Function (PCF) entity in a wireless communication system may include an operation of determining generation of PDU set information having the same characteristics based on PDU set processing information in a UPF entity at a request of an AF entity, an operation of determining whether scheduling is supported based on the PDU set information generated in the UPF and transmitting the corresponding information through a GTP-U header to a Radio Access Network (RAN) entity based on the PDU set information generation information, and an operation of receiving PDU set information through the GTP-U header.

[0041] According to one embodiment of the present disclosure, a communication system provides a PCF entity, the PCF entity including a transceiver and at least one processor, wherein the at least one processor is configured to receive, through the transceiver, a PDU set processing assistance message including information related to whether generation of PDU set processing information for PDU set unit processing reflecting a requirement for PDU set unit processing is supported in an AF entity, and to transmit, through the transceiver, a protocol data unit (PDU) session management (SMF) update request message including information related to whether generation of PDU set processing information is supported in an UPF to a session management function (SMF) entity based on the PDU set processing assistance message, and to receive, through the transceiver, a PDU session SM update response message from the SMF entity in response to the PDU session SM update request message.

[0042] According to the present disclosure, a PCF (policy control function) device that supports RAN (radio access network) scheduling based on a PDU (protocol data unit) set, which is a unit of packets classified by traffic characteristics among download packets of a communication network, may be proposed, including a processor configured to control a transceiver and a transceiver to receive a policy authorization request message including PDU set handling information and PDU set information related parameters from a network exposure function (NEF) when transmitting multimedia type packets through a single service floor based on RTP bundling, generate a rule for generating RTP bundling-based PDU set information based on the RTP bundling-based PDU set handling information and the RTP bundling-based PDU set information related parameters, and transmit a policy control update message including the rule for generating RTP bundling-based PDU set information and the related parameters of RTP bundling-based PDU set information to a session management function (SMF).

[0043] According to one embodiment of the present disclosure, a method of operating a policy control function (PCF) entity in a wireless communication system is provided, and the method of operating may include receiving, from an application function (AF) entity, a protocol description message including a PDU set handling indication and PDU set information and indicating whether generation of PDU set information for a PDU set-based service in an XR service is supported, transmitting, to a session management function (SMF) entity based on the protocol description message, a protocol data unit (PDU) session management (SMF) policy update request message including PDU set information generation related parameters related to whether generation of PDU set information is required in a UPF, and receiving, in response to the PDU session SM policy update request message, a PDU session SM update response message from the SMF entity. An SMF entity received from a PCF entity may include an action of sending an N4 session creation or modification request message including PDU set information creation or detection rules within a policy update request message to a UPF entity and an action of receiving an N4 creation and modification request response message.

[0044] According to one embodiment of the present disclosure, a method of operating a policy control function (PCF) in a wireless communication system is provided, and the method of operating may include an operation of receiving a QoS monitoring request message including QoS monitoring requirement information of an RTP bundled QoS floor from an application function (AF), an operation of transmitting a session management (SM) policy control update notification request message including QoS monitoring policy information to a session management function (SMF) entity based on the QoS monitoring request message, and an operation of receiving an SM policy control update notification response message from the SMF entity in response to the SM policy control update notification request message.

[0045] According to one embodiment of the present disclosure, a method of operating a session management function (SMF) in a wireless communication system is provided, the method of operating may include: receiving a QoS monitoring reporting message based on a QoS monitoring requirement from a RAN or UPF; transmitting a session management (SM) policy control update request message including the QoS monitoring reporting message to a policy control function (PCF) entity based on the QoS monitoring reporting message; and receiving an SM policy control update response message from the PCF entity in response to the SM policy control update request message.

[0046] According to one embodiment of the present disclosure, a method of operating a User Plane Function (UPF) in a wireless communication system is provided, and the method of operating may include an operation of receiving a Protocol Description message including information related to whether PDU set information is supported in an AS from an Application Function (AF), an operation of transmitting a Protocol Data Unit (PDU) Session Management (SMF) Update Request message including information related to whether the PDU set information is supported in an AS to a Session Management Function (SMF) entity based on the Protocol Description message, and an operation of receiving a PDU Session SM Update Response message from the SMF entity in response to the PDU Session SM Update Request message.

[0047] FIG. 1 illustrates a network structure and interface of a 5G system according to one embodiment of the present disclosure.

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

[0049] Referring to FIG. 1, the network structure of a 5G system (100) may include various network entities. For example, the 5G system (100) may include an authentication server function (AUSF) entity (108), an access and mobility management function (AMF) entity (103), a session management function (SMF) entity (105), a policy control function (PCF) entity (106), an application function (AF) entity (107), a unified data management (UDM) entity (109), a data network (DN) (110), a network exposure function (NEF) entity (113), a network slicing selection function (NSSF) entity (114), a user plane function (UPF) entity (104), and a (radio) access network: (R)AN)(102), or a terminal, for example, a user equipment (UE)(101).

[0050] Each NF entity of the 5G system (100) can support the following functions.

[0051] AUSF (108) can process and store data for authentication of UE (101).

[0052] AMF (103) provides functions for access and mobility management per UE, and one UE can be connected to one AMF by default. Specifically, the AMF (103) provides signaling between CN nodes for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), termination of non-access stratum (NAS) signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE reachability (including control and performance of paging retransmission), mobility management control (subscription and policy), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (for AMF events and interfaces to the LI system), provision of forwarding of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, access authorization including roaming authorization check. The AMF entity (103) may support functions such as authorization, provision of SMS message transmission between the UE and the SMSF, security anchor function (SAF), and / or security context management (SCM). Some or all of the functions of the AMF entity (103) may be supported within a single instance of one AMF entity.

[0053] DN (110) refers to, for example, an operator service, Internet access, or a third-party service. DN (110) can transmit a downlink protocol data unit (PDU) to UPF entity (104) or receive a PDU transmitted from UE (101) from UPF entity (104).

[0054] The PCF entity (106) may receive information about packet flows from an application server and provide a function to determine policies such as mobility management and session management. Specifically, the PCF entity (106) may support functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane function entity(ies) (e.g., AMF entity, SMF entity, etc.) can enforce the policy rules, and implementing a front end for accessing related subscription information for policy determination within a user data repository (UDR).

[0055] The SMF entity (105) provides a session management function, and when the UE (101) has multiple sessions, each session can be managed by a different SMF entity. Specifically, the SMF entity (105) supports functions such as session management (e.g., session establishment, modification, and termination, including tunnel maintenance between the UPF entity (104) and (R)AN (102) nodes), UE IP address allocation and management (optionally including authentication), selection and control of UP functions, traffic steering setup to route traffic from the UPF entity (104) to the appropriate destination, termination of the interface to policy control functions, enforcement of the control portion of policies and quality of service (QoS), lawful intercept (for SM events and interfaces to the LI system), termination of the SM portion of NAS messages, downlink data notification, initiation of AN specific SM information (delivered to the (R)AN (102) via N2 via the AMF entity (103)), determination of the session and service continuity (SSC) mode of the session, roaming functions, etc. Some or all of the functions of an SMF entity (105) may be supported within a single instance of an SMF entity.

[0056] The UDM entity (109) stores user subscription data, policy data, etc. The UDM entity (109) may include at least one of two parts: an application front end (FE) and a user data repository (UDR).

[0057] An FE may include a UDM FE, which is responsible for location management, subscription management, and credential processing, and a PCF entity, which is responsible for policy control. The UDR stores data required for the functions provided by the UDM-FE and policy profiles required by the PCF entity. The data stored in the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. The UDM-FE can access subscription information stored in the UDR and support functions such as authentication credential processing, user identification handling, access authentication, registration / mobility management, subscription management, and SMS management.

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

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

[0060] (R)AN(102) is a general term for a new radio access network that supports both evolved E-UTRA, an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB).

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

[0062] UE (101) refers to a user equipment. The user equipment may be referred to by terms such as terminal, mobile equipment (ME), or mobile station (MS). Furthermore, the user equipment may be a portable device such as a laptop, mobile phone, personal digital assistant (PDA), smartphone, or multimedia device, or may be a non-portable device such as a personal computer (PC) or vehicle-mounted device.

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

[0064] The NRF entity (115) supports service discovery. It receives NF discovery requests from NF instances and provides information about discovered NF instances to the NF instances. It also maintains available NF instances and the services they support.

[0065] Meanwhile, for convenience of explanation, FIG. 1 illustrates a reference model for a case where a UE (101) accesses one DN (110) using one PDU session, but the present disclosure is not limited thereto.

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

[0067] Additionally, the UE (101) may simultaneously access two or more (i.e., local and central) data networks provided within a single PDU session.

[0068] In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. For example, the reference point(s) included in the 5G system (100) of FIG. 1 are as follows.

[0069] - N1: Reference point between UE (101) and AMF (103)

[0070] - N2: Reference point between (R)AN(102) and AMF(103)

[0071] - N3: Reference point between (R)AN(102) and UPF(104)

[0072] - N4: Reference point between SMF (105) and UPF (104)

[0073] - N5: Reference point between PCF (106) and AF (107)

[0074] - N6: Reference point between UPF (104) and DN (110)

[0075] - N7: Reference point between SMF (105) and PCF (106)

[0076] - N8: Reference point between UDM (109) and AMF (103)

[0077] - N9: Reference point between two core UPFs (104)

[0078] - N10: Reference point between UDM (109) and SMF (105)

[0079] - N11: Reference point between AMF (103) and SMF (105)

[0080] - N12: Reference point between AMF (103) and AUSF (108)

[0081] - N13: Reference point between UDM (109) and AUSF (108)

[0082] - N14: Reference point between two AMFs (103)

[0083] - N15: Reference point between PCF and AMF in non-roaming scenario, reference point between PCF and AMF in visited network in roaming scenario.

[0084] FIG. 2 illustrates an operation for performing RAN scheduling based on PDU set handling of packets of different media types (e.g., video, audio, etc.) within a single service floor in a wireless communication system according to an embodiment of the present disclosure.

[0085] Referring to FIG. 2, an AF entity can generate a protocol descriptor including information such as a PDU set handling indication and the codec and sampling rate of packets for each media type, a media configuration type within the service floor (Group_RTP_Bundle), and whether PDU set handling is provided for packets within the service floor from the AS (PDU set handling support for all pdu indication) in order to request a service based on PDU set handling of the corresponding service floor, and transmit the protocol descriptor to the PCF entity.

[0086] In Fig. 2, the PCF entity determines whether to accept the request based on the identifier and information for PDU set handling received from the AF entity, and if the service request can be accepted, the identifier and related information for PDU set handling received from the AF can be included and transmitted to the SMF when creating / updating a PCC rule. If the PCF entity cannot support the PDU set handling service of the corresponding service floor using RTP bundling including mutual media types based on the service requirements received from the AF entity, the PCF entity can transmit a rejection message for the request to the AF entity in response to the AF requirement related message. If the AF cannot support the PDU set handling service of the corresponding service floor using the corresponding RTP bundling, it can transmit this to the AS so that packets of different media types of the corresponding service can be used for the service by using each service floor.

[0087] In Fig. 2, if the PCF entity decides to provide the service using RTP bundling, it can decide to update the QoS of the service floor based on a new QoS that reflects the characteristics of the bundled service floor and include this in the updated PCC rule. The PCF entity can recognize that the RAN performs separate processing based on PDU set handling of packets within the service floor from the PDU set handling indicator received from the AF entity, and to support this, it can generate a PDU set QoS Profile of packets transmitted in the RTP bundled service floor based on a protocol descriptor or predefined information and include this when creating or updating the PCC rule.

[0088] If there is no indicator (PDU set information support indication) indicating that PDU set information is provided for all packets in the protocol description transmitted to AF, or if PDU set information is provided in the packet header extension field for video packets and PDU set information may not be provided separately from the AS for audio packets, the UPF entity must perform PDU set information generation for audio packets. In this case, since the PDU set QoS profile is transmitted as a single packet for interactive audio, the mapping can be performed in the same way as the existing QoS profile. That is, for PDU set handling of audio packets, the PSDB (PDU set Delay Budget) in the PDU set QoS profile of the audio packets is mapped to the PDB (Packet delay budget) value in the QoS profile, and the PSER (PDU set Error Rate) can be mapped to the PER (Packet Error Rate) value. Additionally, the PDU set importance value between the PDU sets of the corresponding audio packets can be generated by utilizing the value of the Priority level within the basic 5QI of each media service characteristic. For example, when using the QoS characteristic values ​​mapped to 5QI, it can be set by considering the media characteristics as audio (5QI = 1) and video (5QI = 2), and when they are set to Priority levels 20 and 40, respectively, the PDU set importance value can be set higher for the PDU set of the audio packet than for the video packet.However, since the above operation sets a separate QoS value to support the RTP bundle in the case of the RTP bundle, the standard 5QI value for each media type can be used only in the operation to generate PDU set information for the corresponding media type when there are packets in the RTP bundle service floor for which PDU set information is not separately provided by AS.

[0089] The PCF entity can forward to the SMF entity a PCC rule that includes updated QoS information based on the PDU set QoS profile and RTP bundling-related information for supporting the PDU set handling service in the RAN, and protocol descriptor information indicating that the PDU set information is included in the header extension field of the corresponding packets in the UPF entity.

[0090] Based on the PCC rules received from the PCF entities, the SMF entities can generate updated QFIs, QoS rules, SDF templates, etc. using the QoS information of the RTP bundled service floor and transmit them to the RAN and UPF entities. The SMF entities can transmit information for RAN scheduling based on PDU set handling, such as PDU set QoS profiles and QFIs, QoS rules, and QoS profiles received through the PCC rules, to the RAN. In addition, the SMF entities can transmit information to the UPF entities, such as whether the updated QFI values ​​and PDU set information in the packet detection rule (PDR) of the service floor are transmitted from the AS, and the rules for including the corresponding PDU set information information in the GTP-U header confirmation field, through the N4 rule update.

[0091] The UPF entity can then forward PDU set information to the RAN by including it in the GTP-U header confirmation field when an RTP bundled service floor is input. Furthermore, based on the updated QoS information considering RTP bundling based on the information in the N4 rule, the UPF entity can mark the QFI value transmitted from the SMF as an RTP bundled QoS floor.

[0092] In RAN, based on the PDU set QoS profile and PDU set information received from SMF and UPF entities, when a congestion situation occurs, packets within the RTP bundled QoS floor can be scheduled on a PDU set basis.

[0093] FIG. 3 illustrates an operation when a PCF rejects acceptance of a service request transmitted from an AF in a wireless communication system according to an embodiment of the present disclosure.

[0094] FIG. 3 illustrates an operation in which an AF entity provides relevant information for performing RAN scheduling based on PDU set handling of packets of different media types (e.g., video, audio, etc.) within a single service floor when servicing packets in a wireless communication system according to an embodiment of the present disclosure, and an operation when a PCF that receives the information refuses to provide a service through the RTP bundling.

[0095] Referring to FIG. 3, the AF entity may generate a protocol descriptor including information such as a PDU set handling indication and the codec of packets for each media type, a sampling rate, a media configuration type (Group_RTP_Bundle) within the service floor, and whether PDU set handling is provided by the AS for packets within the service floor (PDU set handling support for all pdu indication) in order to request a service based on PDU set handling of the corresponding service floor, and transmit the generated protocol descriptor to the PCF. Additionally, in consideration of the case where the corresponding RTP bundling request is rejected, an alternative protocol descriptor may be included in the protocol descriptor or transmitted separately to the PCF. At this time, the alternative protocol descriptor may include information that distinguishes media characteristic information for each protocol descriptor for each service floor within the protocol descriptor for RTP bundling.

[0096] In Fig. 3, the PCF entity determines whether to accept the request based on the identifier and information for PDU set handling received from the AF entity, and if the service request can be accepted, the identifier and related information for PDU set handling received from the AF entity can be included and transmitted to the SMF entity when creating / updating a PCC rule. If the PCF entity cannot support the PDU set handling service of the corresponding service floor using RTP bundling including mutual media types based on the service requirements received from the AF entity, the PCF entity can transmit a rejection message for the request to the AF entity in response to the AF requirement related message. If the AF entity cannot support the PDU set handling service of the corresponding service floor using the corresponding RTP bundling, the AF entity can transmit this to the AS so that packets of different media types of the corresponding service can be provided as services using each service floor.

[0097] In Fig. 3, if the PCF entity determines that it cannot or will not provide a service through RTP bundling, it can determine to update the PCC rule based on the alternative protocol descriptor information transmitted from the AF. In addition, the PCF entity can notify the AF entity that the service through the RTP bundling has been rejected in the service request message response received from the AF entity. The AF entity that has received the service rejection result can inform the AS that it must transmit packets with different media types that constitute the service to each service floor. After receiving a service request using an individual service floor from the AF entity, the AS can include PDU set information in the packet header extension field for each service floor and transmit it to the UPF entity. A PCF entity can recognize that the RAN performs PDU set handling-based processing of packets within the corresponding service floor from the PDU set handling indicator received from the AF entity, and to support this, it can create PDU set QoS Profiles for each service floor based on an alternative protocol descriptor or predefined information and include them when creating or updating PCC rules.

[0098] Thereafter, the PCF entity may forward to the SMF entity the PCC rules including PDU set QoS profiles for supporting PDU set handling service in the RAN and alternative protocol descriptor information indicating that PDU set information is included in the header extension field of the corresponding packets in the UPF entity.

[0099] Based on the PCC rules received from the PCF entities, the SMF entities can generate updated QFIs, QoS rules, SDF templates, etc. using the QoS information of each service floor and transmit them to the RAN and UPF. The SMF entities can transmit information for RAN scheduling based on PDU set handling, such as PDU set QoS profiles for each service floor received through the PCC rules, and QFIs, QoS rules, and QoS profiles, to the RAN. In addition, the SMF entities can transmit information to the UPF entities, such as whether the updated QFI values ​​and PDU set information are transmitted from the AS (PDU set handling support for all pdu indication) within the packet detection rule (PDR) of each service floor through N4 rule updates, and rules for including the corresponding PDU set information information in the GTP-U header confirmation field.

[0100] The UPF entity can then mark the PDU set information in each packet header extension field in the GTP-U header confirmation field and forward it to the RAN when each service floor is forwarded to the UPF entity. In addition, based on the information in the N4 rule, the QFI values ​​forwarded from the SMF entity can be marked for each QoS floor based on the updated QoS information for each service floor that takes into account the characteristics of each media.

[0101] In RAN, based on the PDU set QoS profile and PDU set information received from SMF and UPF entities, scheduling operations can be performed on packets within the QoS floor in units of PDU sets when a congestion situation occurs.

[0102] FIG. 4 illustrates a policy update operation based on QoS monitoring reporting information through QoS monitoring during service use through RTP bundling in a wireless communication system according to an embodiment of the present disclosure.

[0103] Specifically, FIG. 4 illustrates an operation in which AF provides relevant information for performing RAN scheduling based on PDU set handling of packets of different media types (e.g., video, audio, etc.) within a single service floor when servicing packets, in a wireless communication system according to an embodiment of the present disclosure, and an operation in which RTP bundling is no longer provided on the corresponding QoS floor through QoS monitoring during service use through RTP bundling.

[0104] Referring to FIG. 4, the AF entity may generate a protocol descriptor including information such as a PDU set handling indication and the codec of packets for each media type, a sampling rate, a media configuration type (Group_RTP_Bundle) within the service floor, and whether PDU set handling is provided by the AS for packets within the service floor (PDU set handling support for all pdu indication) in order to request a service based on PDU set handling of the corresponding service floor, and transmit the generated protocol descriptor to the PCF. Additionally, in consideration of the case where the corresponding RTP bundling request is rejected, an alternative protocol descriptor may be included in the protocol descriptor or transmitted separately to the PCF. At this time, the alternative protocol descriptor may include information that distinguishes media characteristic information for each protocol descriptor for each service floor within the protocol descriptor for RTP bundling.

[0105] In Fig. 4, the PCF entity determines whether to accept the request based on the identifier and information for handling the PDU set received from the AF entity, and if the service request can be accepted, the PCF entity can transmit the identifier and related information for handling the PDU set received from the AF entity to the SMF entity when creating / updating a PCC rule.

[0106] If the PCF entity decides to provide the service using RTP bundling, it can decide to update the QoS of the service floor based on the new QoS that reflects the characteristics of the bundled service floor and include this in the updated PCC rule. The PCF entity can recognize that the RAN performs separate processing based on PDU set handling of packets within the service floor from the PDU set handling indicator received from the AF entity. To support this, the PCF can generate a PDU set QoS Profile for packets transmitted on the RTP bundled service floor based on a protocol descriptor or predefined information and include this when creating or updating the PCC rule. Afterwards, the PCF can forward the PCC rule to the SMF, including the PDU set QoS profile for supporting the PDU set handling service in the RAN, the updated QoS information based on RTP bundling-related information, and the protocol descriptor information indicating that the UPF entity includes PDU set information in the header extension field of the packets.

[0107] Based on the PCC rules received from the PCF entities, the SMF entities can generate updated QFIs, QoS rules, SDF templates, etc. using the QoS information of the RTP bundled service floor and transmit them to the RAN and UPF entities. The SMF entities can transmit information for RAN scheduling based on PDU set handling, such as PDU set QoS profiles and QFIs, QoS rules, and QoS profiles received through the PCC rules, to the RAN. In addition, the SMF entities can transmit information to the UPF entities about whether the updated QFI values ​​and PDU set information in the packet detection rule (PDR) of the service floor are transmitted from the AS and the rules for including the corresponding PDU set information information in the GTP-U header confirmation field through the N4 rule update.

[0108] The UPF entity can then forward PDU set information to the RAN by including it in the GTP-U header confirmation field when an RTP bundled service floor is input. Furthermore, based on the updated QoS information that takes RTP bundling into account based on the information in the N4 rule, the UPF entity can mark the QFI value forwarded from the SMF entity as an RTP bundled QoS floor.

[0109] In RAN, based on the PDU set QoS profile and PDU set information received from SMF and UPF entities, when a congestion situation occurs, packets within the RTP bundled QoS floor can be scheduled on a PDU set basis.

[0110] As above, when using a service using an RTP bundled service floor, the PCF entity can recognize that it is difficult to use the service through the RTP bundling through QoS monitoring reporting such as data rate monitoring values ​​from the RAN or UPF entity and decide to change the service policy using individual service floors for each media type.

[0111] Requirements for QoS monitoring can be included by the PCF entity when creating or updating the PCC rule. In addition, when monitoring the QoS of the QoS floor using RTP bundling, the threshold for reporting the data rate monitoring value can be received through the AF entity, or the QoS monitoring requirements of the corresponding RTP bundled QoS floor can be determined according to the network operator's policy, and based on this, the RAN or UPF entity can perform the QoS monitoring operation of the corresponding QoS floor within the PCC rule. In addition, the QoS monitoring requirements can request reporting of the corresponding QoS monitoring reporting value to the SMF entity for use by the PCF entity, and the PCF entity can receive the corresponding QoS monitoring reporting value from the SMF through a separate PCRT (Policy control reporting trigger), etc., and then forward it back to the PCF entity.

[0112] The PCF entity can determine that it can no longer provide an RTP bundled QoS service based on QoS monitoring requirements and QoS monitoring reporting values ​​delivered from the RAN or UPF entity. In this case, the PCF can determine to create a service floor for each media type based on the alternative protocol descriptor information in the service requirement message through RTP bundling of the existing AF, and perform a PCC rule update operation based on the information.

[0113] A PCF entity can forward a PCF event reporting result including the fact that RTP bundling can no longer be guaranteed to the AF entity through the AF entity. The reporting result value can be used by the AF entity to notify the AF entity of the event-related information related to RTP bundling when an event related to RTP bundling occurs through a subscription request for reporting related to PCF events related to RTP bundling after the AF entity has forwarded the RTP bundling service requirement.

[0114] If the PCF entity in FIG. 4 determines that it cannot or will not provide a service through RTP bundling, it can determine a PCC rule update based on the alternative protocol descriptor information transmitted from the AF entity.

[0115] An AF entity that receives an event notification message from a PCF entity can inform the AS that packets with different media types that constitute the corresponding service should be transmitted to each service floor.

[0116] After receiving a service request using an individual service floor from an AF entity, AS can include PDU set information in the packet header extension field for each service floor and forward it to the UPF entity.

[0117] A PCF entity can recognize that RAN performs PDU set handling-based processing of packets within the corresponding service floor from the PDU set handling indicator received from the AF entity, and in order to support PDU set handling-based processing, it can create PDU set QoS Profiles for each service floor based on an alternative protocol descriptor or predefined information and include them when creating or updating PCC rules.

[0118] A PCF entity may forward PCC rules to an SMF entity, including PDU set QoS profiles for supporting PDU set handling services in the RAN and alternative protocol descriptor information indicating that PDU set information is included in the header extension fields of the corresponding packets in the UPF entity.

[0119] Based on the PCC rules received from the PCF entities, the SMF entities can generate updated QFIs, QoS rules, SDF templates, etc. using the QoS information of each service floor and transmit them to the RAN and UPF. The SMF entities can transmit information for RAN scheduling based on PDU set handling, such as PDU set QoS profiles for each service floor received through the PCC rules, and QFIs, QoS rules, and QoS profiles, to the RAN.

[0120] Through N4 rule update, the SMF entity can convey to the UPF entity information such as whether the updated QFI value and PDU set information are transmitted from the AS (PDU set handling support for all pdu indication) in the packet detection rule (PDR) of each service floor, and the rule for including the corresponding PDU set information in the GTP-U header confirmation field.

[0121] The UPF entity can then mark the PDU set information in each packet header extension field in the GTP-U header confirmation field and forward it to the RAN when each service floor is forwarded to the UPF. In addition, the UPF entity can mark the QFI values ​​forwarded from the SMF entity for each QoS floor based on the updated QoS information for each service floor that takes into account the characteristics of each media based on the information in the N4 rule.

[0122] In RAN, based on the PDU set QoS profile and PDU set information received from SMF and UPF entities, scheduling operations can be performed on packets within the QoS floor in units of PDU sets when a congestion situation occurs.

[0123] Figure 5 illustrates an operation for performing PDU set-based RAN scheduling operation for packets transmitted through one or more service floors having the same media type.

[0124] The PCF entity can recognize that the RAN performs PDU set handling-based processing of packets within the corresponding service floor from the PDU set handling indicator in the service requirements received from the AF entity. In addition, the UPF entity can recognize whether the packets within the corresponding service floor include PDU set information in the header extension field or whether the PDU set information should be generated in the UPF based on the information in the protocol descriptor from the AF entity in order to perform operations related to generating or recognizing PDU set information for PDU set handling. For example, in FIG. 5, the PCF entity can recognize that in the case of service floor 1 transmitting a packet of video 1 transmitted from AS1, PDU set information can be received from AS1, and in the case of service floor 2 transmitting a packet of video 2 transmitted from AS2, it can recognize that AS2 does not generate or provide separate PDU set information through the information in the protocol descriptor.

[0125] To support PDU set handling, a PCF entity can create a PDU set QoS Profile based on a protocol descriptor or predefined information and include it when creating or updating a PCC rule.

[0126] The PCF entity can convey the PDU set QoS profile for supporting the PDU set handling service in the RAN and the characteristic information of the service floors delivered to the UPF. For example, in Fig. 5, in the case of service floor 1, since PDU set information is included and included in the RTP header extension, an indicator (PDU set information support indication) indicating that a separate PDU set information generation operation is not required, and in the case of service floor 2, a PCC rule including related information for performing a separate PDU set information generation operation can be conveyed to the SMF.

[0127] The SMF entity can generate updated QFI and QoS rules, SDF templates, etc. based on the PCC rules received from the PCF entity and transmit them to the RAN and UPF entities.

[0128] An SMF entity can transmit information for RAN scheduling based on PDU set handling, such as PDU set QoS profile and QFI, QoS rule, and QoS profile, received through PCC rules to the RAN.

[0129] The SMF entity can, through N4 rule update, transmit to the UPF entity the updated QFI value within the packet detection rule (PDR) of each service floor, whether PDU set information is transmitted from the AS (PDU set information support indication), the rule for including the corresponding PDU set information within the GTP-U header confirmation field, and the related information for generating and generating the PDU set information of the corresponding service floor when separate PDU set information is not provided.

[0130] The UPF entity can then mark the PDU set information in the packet header extension field in the GTP-U header confirmation field and transmit it to the RAN when packets of each service floor are transmitted to the UPF in the case of service floor 1. In addition, the UPF entity can generate PDU set information in the case of service floor 2 and mark it in the GTP-U header confirmation field and transmit it to the RAN.

[0131] A UPF entity can use relevant QoS information to mark packets transmitted through different service floors, updated for each service floor considering the same media characteristics, to be transmitted to the same QoS floor based on information within the N4 rules.

[0132] In RAN, based on the PDU set QoS profile and PDU set information received from SMF and UPF entities, scheduling operations can be performed on packets within the QoS floor in units of PDU sets when a congestion situation occurs.

[0133] FIG. 6 illustrates a flowchart for explaining a method for supporting scheduling for an RTP bundled (or multiplexed) service using a protocol description including RTP bundling (or multiplexing) related information transmitted via AF in a wireless communication system according to an embodiment of the present disclosure.

[0134] In step 601, the AF entity can determine support for PDU set-based service to support scheduling in RAN and RTP bundling service (or multiplexing service) to transmit packets with different media types within a single service floor by utilizing PDU set handling function and PDU set information according to user selection or service provider policy.

[0135] In step 603, based on the decision made in step 601, the AF entity may transmit PDU set handling-related information including a PDU set handling indication and a protocol description to be used when supporting a PDU set-based service to the NEF entity, and receive a response thereto. The PDU set handling-related information may be included in an AF session-related QoS requirements (AFsessionWithQoS) message transmitted from the AF entity to the NEF entity.

[0136] Information related to PDU set handling may be configured as a protocol descriptor including information such as a PDU set handling indication in an AF session-related QoS requirement request message, a codec and sampling rate of packets for each media type, a media configuration type within a service floor (Group_RTP_Bundle), and an indicator indicating whether PDU set handling is provided for packets within the corresponding service floor received from an AS (application server) entity (PDU set handling support for all pdu indication).

[0137] In step 605, the NEF entity may transmit PDU set handling information or requirements (such as PDU set information generation and related parameters) to be used when supporting a service based on the PDU set received from the AF entity to the PCF entity using a PolicyAuthorization message. If a separate policy authorization service process has not been performed through an existing service, the service-related PDU set handling support information may be transmitted to the PCF entity using a Policy Authorization Creation (Npcf_PolicyAuthorization_Create) request message, or if an existing service process has been created, a Policy Authorization Update (Npcf_PolicyAuthorization_Update) request message. In addition, in order to receive additional RTP bundling service-related reporting messages, the NEF entity may request reporting of the corresponding RTP bundling event using a Policy Authorization Subscribe (Npcf_PolicyAuthorization_Subscribe) request message.

[0138] In step 607, the PCF entity can determine whether to accept a request for an RTP bundling-based service or an RTP bundling-based PDU set handling service based on the identifier and information for PDU set handling received from the AF entity. If the PCF entity can accept the RTP bundling-based service request of the AF entity, the identifier and related information for PDU set handling received from the AF entity can be included and transmitted to the SMF entity when creating / updating a PCC rule. If the PCF entity cannot support the PDU set handling service of the corresponding service floor using RTP bundling including mutual media types based on the service requirements received from the AF entity, the PCF entity can transmit a rejection message for the RTP bundling-based service request to the AF entity in response to the AF requirement-related message through steps 609 and 611. If the AF entity cannot support the PDU set handling service of the service floor using the RTP bundling, it can forward it to the AS so that packets of different media types of the service can be provided using each service floor.

[0139] If the PCF entity decides to provide the service using RTP bundling through step 607, it can decide to update the QoS of the service floor based on the new QoS that reflects the characteristics of the bundled (or multiplexed) service floor and include it in the updated PCC rule. The PCF entity can recognize that the RAN performs separate processing based on PDU set handling of packets within the service floor from the PDU set handling indicator received from the AF entity, and to support this, it can generate a PDU set QoS Profile of packets transmitted in the RTP bundled service floor based on a protocol descriptor or predefined information and include it when creating or updating the PCC rule.

[0140] If there is no PDU set information support indication in the protocol description transmitted from the AF entity through steps 603 and 605, or if PDU set information is provided in the packet header extension field for individual video packets and PDU set information for audio packets may not be provided separately from the AS, the UPF entity may perform PDU set information generation for audio packets for which separate PDU set information is not provided from the AS. In addition, when the PCF entity generates a PDU set QoS profile for the audio packet, it may perform mapping in the same way as the existing QoS profile for interactive audio transmitted as a single packet. That is, in order to handle the PDU set of audio packets, the PSDB (PDU set Delay Budget) in the PDU set QoS profile of the audio packets is mapped to the PDB (Packet delay budget) value in the QoS profile, and the PSER (PDU set Error Rate) can be mapped to the PER (Packet Error Rate) value. In addition, the PDU set importance value between the PDU sets of the audio packets can be generated by utilizing the value of the Priority level in the basic 5QI of each media service characteristic. For example, when using the QoS characteristic values ​​mapped to 5QI, it can be set by considering the media characteristics as audio (5QI = 1) and video (5QI = 2), and when they are set to Priority levels 20 and 40, respectively, the PDU set importance value can be set higher for the PDU set of the audio packet than for the video packet.However, since the above operation sets a separate QoS value to support the RTP bundle in the case of the RTP bundle, if there are packets in the RTP bundle service floor for which the AS does not separately provide PDU set information, the standard 5QI value for each media type can be used only in the operation to generate PDU set information for the corresponding media type.

[0141] In steps 609 and 611, the PCF entity may indicate that the policy update request related to the PDU set handling service via RTP bundling has been accepted based on the service requirements received from the AF entity in steps 603 and 605 by responding with a Policy Authorization Update Request and an AF Session Related Requirements Update Request message.

[0142] In step 613, the PCF entity may transmit updated PCC rules, including updated QoS information based on the PDU set QoS profile and RTP bundling-related information for supporting the PDU set handling service in the RAN, and protocol descriptor information indicating that the PDU set information is included in the header extension field of the corresponding packets in the UPF entity, to the SMF entity through a Session Policy Control Update Notification (Npcf_SMPolicyControl_UpdateNotify) request message.

[0143] In steps 615 and 617, the SMF entity may transmit PDU set handling information, including PDU set information detection rules and related parameter information for supporting a PDU set-based service received through the PCF in step 613, to the UPF via an N4 session modification request message and receive a response. The N4 session modification request message may include a packet detection rule (PDR).

[0144] In step 619, the SMF entity can forward the N2 SM information and N1 SM container including updated QFI and QoS rules, etc., using the QoS information of the RTP bundled service floor based on the PCC rules received from the PCF entity in step 613 to the AMF entity via the N1N2MessageTransfer (Namf_Communication_N1N2MessageTransfer) message.

[0145] In step 621, the AMF entity may forward the N2 SM information and N1 SM container including updated QFI and QoS rules, PDU set QoS profile, etc. to support the RTP bundling service and PDU set handling service received from the SMF entity in step 619 to the RAN using an N2 message.

[0146] At step 623, the RAN may forward the N1 SM container including updated QoS rules, etc. to the UE to support the RTP bundling service.

[0147] In steps 625 to 629, the RAN transmits a response message of the N2 message to the AMF entity in response to the N2 message, and the AMF entity can transmit and receive a message indicating that the N2 SM information including updated QFI and QoS rules and the N1 SM container have been reflected to the SMF entity based on the received response message of the N2 message.

[0148] In step 631, the UPF entity can detect PDU set information in the RTP packet header extension field transmitted from the AS in the DN to the UPF entity through the N6 section. The UPF entity can transmit the detected PDU set information to the RAN through the GTP-U header. Specifically, the PDU Set information can be composed of at least one of a PDU Set Sequence Number, an End PDU of the PDU Set, a PDU Set Size in bytes, a PDU Sequence Number within a PDU Set, and a PDU Set Importance.

[0149] At step 633, the UPF entity may forward downlink data containing PDU set information to the RAN.

[0150] In step 635, the RAN can perform scheduling operation on packets within the RTP bundled QoS floor in units of PDU sets when a congestion situation occurs based on the PDU set QoS profile and PDU set information received in step 621.

[0151] FIG. 7 is a flowchart illustrating a method for supporting a PDU set-based RAN scheduling operation when a PCF entity rejects acceptance of an RTP bundling-based service request transmitted from an AF entity in a wireless communication system according to an embodiment of the present disclosure.

[0152] In step 701, the AF entity can determine support for PDU set-based service to support scheduling in RAN and RTP bundling service to transmit packets with different media types within a single service floor by utilizing PDU set handling function and PDU set information according to user selection or service provider policy.

[0153] In step 703, based on the decision made in step 701, the AF entity may transmit PDU set handling related information including a PDU set handling indication and a protocol description to be used when supporting a PDU set-based service to the NEF entity, and receive a response. The PDU set handling related information may be included in an AF session related QoS requirements (AFsessionWithQoS) message transmitted from the AF entity to the NEF entity.

[0154] Information related to PDU set handling may be configured as a protocol descriptor including information such as a PDU set handling indication in an AF session related QoS requirement request message (602), a codec of packets for each media type, a sampling rate, a media configuration type within a service floor (Group_RTP_Bundle), and whether PDU set information for packets within the corresponding service floor is provided from the AS (PDU set information support indication).

[0155] In step 705, the NEF entity can transmit PDU set handling information or requirements (such as PDU set information generation and related parameters) to be used when supporting a service based on the PDU set received from the AF entity to the PCF entity using a PolicyAuthorization message. If a separate policy authorization service process has not been performed through an existing service, the service-related PDU set handling support information received can be transmitted to the PCF entity using a Policy Authorization Creation (Npcf_PolicyAuthorization_Create) request message, or if an existing service process has been created, a Policy Authorization Update (Npcf_PolicyAuthorization_Update) request message. In addition, in order to receive messages related to reporting events related to RTP bundling that occur in the PCF entity for additional RTP bundling service-related reporting, the corresponding RTP bundling event reporting can be requested using a Policy Authorization Subscribe (Npcf_PolicyAuthorization_Subscribe) request message.

[0156] At step 707, the PCF entity may decide to reject the service request based on the service requirements related to handling the PDU set considering the RTP bundling received from the AF entity.

[0157] In steps 709 and 711, the rejection of the request for support of PDU set handling service via RTP bundling in PCF in step 707 may be notified through the Policy Authorization Update Request and AF Session Related Requirements Update Request message responses.

[0158] In order to request a service based on PDU set handling of the corresponding service floor, the AF entity can generate a protocol descriptor containing information such as PDU set handling indication, codec of packets for each media type, sampling rate, media composition type within the service floor (Group_RTP_Bundle), and whether PDU set handling of packets within the corresponding service floor is provided from the AS (PDU set handling support for all pdu indication), and transmit the generated protocol descriptor to the PCF entity.

[0159] Additionally, in case the RTP bundling request is rejected, an alternative protocol descriptor may be included in the protocol descriptor or transmitted separately to the PCF. In this case, the alternative protocol descriptor may include information that distinguishes media characteristic information for each service floor in the protocol descriptor for RTP bundling as a protocol descriptor for each service floor. If an alternative protocol descriptor considering an individual service floor is included in the service requirement message transmitted from the AF entity to the PCF entity in steps 703 and 705, steps 713 to 717 may be omitted.

[0160] In step 713, the AF entity can determine whether to support PDU set handling service for each service floor by using packets of different media types for each service floor.

[0161] In step 715, based on the decision made in step 713, the AF entity may transmit PDU set handling related information including a PDU set handling indication and a protocol description to be used when supporting a PDU set-based service to the NEF entity, and receive a response. The PDU set handling related information may be included in an AF session related QoS requirements (AFsessionWithQoS) message transmitted from the AF entity to the NEF entity.

[0162] Information related to PDU set handling may be configured as a protocol descriptor including information such as a PDU set handling indication, a codec of packets for each media type, a sampling rate, a media configuration type within a service floor (Individual service flows), and whether packets within each service floor provide PDU set information (PDU set information support indication) within an AF session-related QoS requirement request message (608). After receiving a service request using an individual service floor from an AF entity, the AS may include PDU set information within a packet header extension field for each service floor and forward it to the UPF entity.

[0163] In step 717, the NEF entity may transmit PDU set handling information or requirements (such as PDU set information generation and related parameters) to be used when supporting a service based on the PDU set received from the AF entity to the PCF entity using a PolicyAuthorization message.

[0164] In step 719, the PCF entity can determine whether to accept the request based on the identifier and the protocol descriptor information for each individual service floor for requesting support for PDU set handling when using a service through an individual service floor received from the AF entity. If the PDU set handling service request through an individual service floor can be accepted, the identifier and the protocol descriptor information for each individual service floor for supporting PDU set handling received from the AF can be included when creating / updating a PCC rule.

[0165] Based on the requirement to support handling of PDU sets through individual service floors received through steps 715 and 717 in steps 721 and 723, the RAN can transmit a response message indicating that the scheduling request based on PDU sets per individual service floor has been accepted.

[0166] In step 725, the PCF may transmit an updated PCC rule including updated QoS information for each service floor, considering PDU set QoS profiles and media types for each service floor for supporting PDU set handling service in the RAN, and protocol descriptor information indicating that PDU set information is included in the header extension field of the corresponding packets in the UPF, to the SMF entity through a Session Policy Control Update Notification (Npcf_SMPolicyControl_UpdateNotify) request message.

[0167] In steps 727 and 729, the SMF entity may transmit to the UPF, through an N4 session modification request message, related information for PDU set handling, including PDU set information detection rules and related parameter information for service support based on PDU sets for each individual service floor based on the updated PCC rules received through the PCF entity, and receive a response. The N4 session modification request message may include a packet detection rule (PDR).

[0168] In step 731, the SMF entity can forward the N2 SM information including the updated QFI and QoS profiles of individual service floors, PDU set QoS profiles, etc., and the N1 SM container including the QoS rules of individual service floors, etc., based on the PCC rules received from the PCF entity in step 725, to the AMF entity via the N1N2MessageTransfer (Namf_Communication_N1N2MessageTransfer) message.

[0169] In step 733, the AMF entity may forward an N1 SM container containing N2 SM information and QoS rules, including updated QFIs and QoS profiles, PDU set QoS profiles, etc. to support PDU set handling of the service composed of individual service floors received in step 731, to the RAN using an N2 message.

[0170] At step 735, the RAN may forward the N1 SM container containing updated QoS rules, etc. to the UE to support services composed of individual service floors.

[0171] In steps 737 to 741, the RAN transmits a response message of the N2 message to the AMF entity in response to the N2 message, and the AMF entity can transmit and receive a message indicating that the N2 SM information including updated QFI and QoS rules, etc. and the N1 SM container have been reflected based on the response message of the N2 message received from the SMF entity.

[0172] In step 743, the UPF entity can detect PDU set information in the RTP packet header extension field transmitted from the AS in the DN to the UPF entity through the N6 section. The UPF entity can then mark the PDU set information in each packet header extension field in the GTP-U header confirmation field and transmit it to the RAN when packets of each service floor are transmitted to the UPF entity. In addition, based on the information in the N4 rule, the UPF entity can mark the QFI value transmitted from the SMF entity for each QoS floor based on the updated QoS information for each service floor that takes into account the characteristics of each media. Specifically, the PDU Set information may be composed of at least one of a PDU Set Sequence Number, an End PDU of the PDU Set, a PDU Set Size in bytes, a PDU SN within a PDU Set, and a PDU Set Importance.

[0173] At step 745, the UPF entity may forward downlink data containing PDU set information to the RAN.

[0174] In step 747, the RAN can perform a PDU set unit scheduling operation on packets within each QoS floor when a congestion situation occurs based on the PDU set QoS profile and PDU set information for each individual service floor received in step 733.

[0175] FIG. 8 illustrates a flowchart for explaining a method for supporting policy updates based on QoS monitoring reporting values ​​while using an RTP bundled base service in a wireless communication system according to an embodiment of the present disclosure.

[0176] In step 801, as shown in FIG. 6, the AF entity requests support for PDU set handling based on the RTP bundled service floor, and the PCF entity can determine a policy for scheduling operation based on the RTP bundled service floor in the RAN based on the service request and transmit the relevant information to the SMF entity through PCC rule update. At this time, the SMF entity can transmit related information for PDU set handling to the RAN and UPF based on the updated PCC rule. Thereafter, the UPF entity can detect PDU set information in the packet header extension field in the RTP bundled service floor and mark it in the GTP-U header extension field and transmit it to the RAN. In addition, the RAN can perform PDU set-based scheduling of the RTP bundled QoS floor by using the PDU set QoS profile received from the SMF entity and the PDU set information transmitted from the UPF.

[0177] In steps 803 to 807, QoS monitoring operations for data rate monitoring may be performed by the RAN or UPF entity according to QoS monitoring requirements.

[0178] In steps 803 to 805, the RAN performs data rate monitoring based on the requirements for QoS monitoring in the updated PCC rule generated by the PCF entity in step 801. If the data rate monitoring value of the RTP bundled QoS floor exceeds a threshold, this can be transmitted to the SMF entity through QoS monitoring reporting. The data rate monitoring value can include threshold information, etc. in the requirements for QoS monitoring, and the requirements for QoS monitoring can be transmitted through AF or preset according to operator policy.

[0179] In step 807, the UPF entity performs data rate monitoring based on the requirements for QoS monitoring in the updated PCC rule generated by the PCF entity in step 801. If the data rate monitoring value of the RTP bundled QoS floor exceeds the threshold, the UPF entity can forward the QoS monitoring reporting information to the SMF entity through N4 Session report.

[0180] In step 809, the SMF entity may forward the QoS monitoring reporting information of the RTP bundled QoS floor to the PCF via an SM Policy Control (SMPolicyControl) update request. In addition, within the QoS monitoring requirement, the PCF entity may request the forwarding of the QoS monitoring reporting information to the SMF entity instead of directly forwarding the QoS monitoring reporting value to an AF entity, etc., in order to use the QoS monitoring reporting value. The PCF entity may request the forwarding of the QoS monitoring reporting information to the PCF entity when the QoS monitoring reporting information is forwarded to the SMF entity via a separate PCRT (Policy control reporting trigger), etc.

[0181] In step 811, the PCF entity may determine that the RTP bundled QoS service can no longer be provided based on the QoS monitoring reporting information transmitted from the RAN or UPF entity based on the QoS monitoring requirements and may decide to update the policy. At this time, if the PCF entity has received replacement protocol descriptor information including individual service floor information in the service requirement message through RTP bundling of the existing AF entity in step 801 and has determined that the PCF cannot or will not provide the service through RTP bundling, the PCF entity may decide to update the PCC rule based on the replacement protocol descriptor information transmitted from the AF entity. If the replacement protocol descriptor information is received in step 801 as above, steps 819 and 821 may be omitted.

[0182] In steps 813 and 815, the PCF entity can forward the PCF event reporting results including the fact that RTP bundling can no longer be guaranteed to the AF entity. The PCF event reporting operation can be performed after the AF entity forwards the RTP bundling service requirement in step 801, and the AF entity can notify the AF entity of event-related information when an RTP bundling-related event occurs through a PCF entity-related reporting subscription request for RTP bundling-related PCF events to the PCF entity.

[0183] In step 817, the AF entity that has received the event notification message from the PCF entity can determine that packets having different media types constituting the corresponding service should be transmitted for each service floor. In addition, if an alternative protocol descriptor is not transmitted to the PCF entity in step 801, a protocol descriptor considering each service floor can be generated. Thereafter, the AF entity can transmit a request for packet transmission for each service floor to the AS. After receiving a service request using each service floor from the AF entity, the AS can include PDU set information in a packet header extension field for each service floor and transmit it to the UPF entity.

[0184] In step 819, based on the decision made in step 817, the AF entity may transmit PDU set handling related information, including a PDU set handling indication and a protocol description to be used when supporting a PDU set-based service to the NEF entity. The PDU set handling related information may be included in the AF session related QoS requirements (AFsessionWithQoS) message transmitted from the AF entity to the NEF entity.

[0185] Information related to PDU set handling may be configured as a protocol descriptor including information such as a PDU set handling indication in the AF session-related QoS requirement request message, the codec of packets for each media type, the sampling rate, the media composition type within the service floor (Individual service flows), and whether packets within each service floor provide PDU set information (PDU set information support indication). After receiving a service request using an individual service floor from an AF entity, the AS may include PDU set information in the packet header extension field for each service floor and forward it to the UPF entity.

[0186] In step 821, the NEF entity can transmit PDU set handling information or requirements (such as PDU set information generation and related parameters) to be used when supporting a service based on the PDU set received from the AF entity to the PCF entity using a PolicyAuthorization message.

[0187] In step 823, the PCF entity can determine whether to accept the request based on the identifier and the protocol descriptor information for each individual service floor for requesting support for PDU set handling when using a service through an individual service floor received from the AF entity. If the PDU set handling service request through an individual service floor can be accepted, the identifier and the protocol descriptor information for each individual service floor for supporting PDU set handling received from the AF entity can be included when creating / updating a PCC rule.

[0188] The response message may indicate that the PDU set handling support requirement via the individual service floor received from the AF entity in steps 825 and 827 has been accepted.

[0189] In step 829, the PCF entity may send an updated PCC rule, including updated QoS information for each service floor, considering PDU set QoS profiles and media types for each service floor for supporting PDU set handling service in the RAN, and protocol descriptor information indicating that PDU set information is included in the header extension field of the corresponding packets in the UPF, to the SMF entity via a Session Policy Control Update Notification (Npcf_SMPolicyControl_UpdateNotify) request message.

[0190] In step 831, the SMF entity may transmit related information for PDU set handling, including PDU set information detection rules and related parameter information for supporting services based on PDU sets for each individual service floor based on the updated PCC rules received through the PCF entity, to the UPF entity through an N4 session modification request message and receive a response. The N4 session modification request message may include a packet detection rule (PDR).

[0191] In step 833, the SMF entity may forward the N2 SM information including the updated QFI and QoS profiles of individual service floors, PDU set QoS profiles, etc., and the N1 SM container including the QoS rules of individual service floors, etc., based on the PCC rules received from the PCF entity in step 829, to the AMF entity via the N1N2MessageTransfer (Namf_Communication_N1N2MessageTransfer) message.

[0192] In step 835, the AMF entity may forward an N1 SM container containing N2 SM information and QoS rules, including updated QFIs and QoS profiles, PDU set QoS profiles, etc. to support handling of PDU sets of services composed of individual service floors received in step 833, to the RAN using an N2 message.

[0193] At step 837, the RAN may forward the N1 SM container containing updated QoS rules, etc. to the UE to support services composed of individual service floors.

[0194] In steps 839 to 843, the RAN transmits a response message of the N2 message to the AMF entity in response to the N2 message, and the AMF entity can transmit and receive a message indicating that the N2 SM information including updated QFI and QoS rules and the N1 SM container have been reflected to the SMF entity based on the received response message of the N2 message.

[0195] In step 845, the UPF may detect PDU set information in the RTP packet header extension field transmitted to the UPF from the AS in the DN through the N6 section. The UPF may then mark the PDU set information in each packet header extension field in the GTP-U header confirmation field and transmit it to the RAN when packets of each service floor are transmitted to the UPF. In addition, based on the information in the N4 rule, the QFI value transmitted from the SMF may be marked for each QoS floor based on the updated QoS information for each service floor that takes into account the characteristics of each media. Specifically, the PDU Set information may be configured with at least one of a PDU Set Sequence Number, an End PDU of the PDU Set, a PDU Set Size in bytes, a PDU Sequence Number within a PDU Set, and a PDU Set Importance.

[0196] In step 847, the RAN can perform a PDU set unit scheduling operation on packets within each QoS floor when a congestion situation occurs based on the PDU set QoS profile and PDU set information for each individual service floor received in step 835.

[0197] FIG. 9 illustrates a flowchart for describing a method for supporting one or more individual service floor-based PDU set handling services having the same media type.

[0198] In step 901, the AF may determine to support PDU set handling services for one or more individual service floors having the same media type.

[0199] In step 903, based on the decision made in step 901, the AF entity may transmit PDU set handling related information including a PDU set handling indication and a protocol description to be used when supporting a PDU set-based service to the NEF entity. The PDU set handling related information may be included in the AF session related QoS requirements (AFsessionWithQoS) message transmitted from the AF entity to the NEF entity.

[0200] Information related to PDU set handling may be configured as a protocol descriptor including information such as a PDU set handling indication, a codec of packets per service floor, a sampling rate, a media composition type within a service floor (Individual service flows), and whether packets within each service floor support PDU set information (PDU set information support indication) within an AF session-related QoS requirement request message (802). After receiving a service request using an individual service floor from an AF entity, the AS may include PDU set information in a packet header extension field of the service floor and forward it to the UPF entity. In addition, in the case of a service floor connected from an existing AS where one or more service floors cannot generate or mark PDU set information, the PDU set information support indicator may not be included in the protocol description, thereby allowing the UPF to forward information including information for performing a PDU set information generation operation when updating PCC rules in the PCF.

[0201] In step 905, the NEF entity can transmit PDU set handling information or requirements (such as PDU set information generation and related parameters) to be used when supporting a service based on the PDU set received from the AF entity to the PCF entity using a PolicyAuthorization message.

[0202] In step 907, the PCF entity can recognize that the RAN performs PDU set handling-based processing of packets within the corresponding service floor from the PDU set handling indicator in the service requirements received from the AF entity. In addition, the UPF entity can recognize whether packets within the corresponding service floor include PDU set information in a header extension field or whether PDU set information should be generated by the UPF entity based on information in the protocol descriptor from the AF in order to perform operations related to generating or recognizing PDU set information for PDU set handling. The PCF entity can generate a PDU set QoS Profile based on the protocol descriptor or predefined information to support PDU set handling and include it when generating or updating a PCC rule.

[0203] In steps 909 and 911, the PCF entity may notify a response to a request for updating PDU set handling information (PDU set handling information) or requirements (PDU set information generation and related parameters, etc.) to be used when supporting a PDU set-based service based on the QoS requirements received from the AF entity through steps 903 and 905, through a requirement update request message response.

[0204] In step 913, the PCF entity may send an updated PCC rule, including a PDU set QoS profile for supporting PDU set handling service in RAN, updated QoS information for each individual service floor, and protocol descriptor information indicating that PDU set information is included in the header extension field of the corresponding packets in UPF, to the SMF entity via a Session Policy Control Update Notification (Npcf_SMPolicyControl_UpdateNotify) request message.

[0205] In steps 915 and 917, the SMF entity can transmit to the UPF entity the updated QFI value and PDU set information in the packet detection rule (PDR) of each service floor through N4 rule update, whether the PDU set information is transmitted from the AS (PDU set information support indication), a rule to include the corresponding PDU set information information in the GTP-U header confirmation field, and if separate PDU set information is not provided, the generation of the PDU set information of the corresponding service floor and related information for generation.

[0206] In step 919, the SMF entity can forward the N2 SM information including the updated QFI and QoS profiles of individual service floors, PDU set QoS profiles, etc., and the N1 SM container including the QoS rules of individual service floors, etc., based on the PCC rules received from the PCF entity in step 913, to the AMF entity via the N1N2MessageTransfer (Namf_Communication_N1N2MessageTransfer) message.

[0207] In step 921, the AMF entity may forward an N1 SM container containing N2 SM information and QoS rules, including updated QFI and QoS profiles, PDU set QoS profiles, etc. to support handling of PDU sets of services composed of individual service floors received in step 919, to the RAN using an N2 message.

[0208] At step 923, the RAN may forward an N1 SM container including updated QoS rules, etc. to the UE to support services composed of individual service floors.

[0209] In steps 925 to 929, the RAN transmits a response message of the N2 message to the AMF entity in response to the N2 message, and the AMF entity can transmit and receive a message indicating that the N2 SM information including updated QFI and QoS rules and the N1 SM container have been reflected to the SMF entity based on the received response message of the N2 message.

[0210] In step 931, the UPF entity can detect if the PDU set information in the RTP packet header extension field transmitted from the AS to the UPF entity via the N6 section within the DN is marked and transmitted from the AS. The UPF entity can mark the PDU set information in the packet header extension field in the GTP-U header confirmation field and transmit it to the RAN.

[0211] If there is no PDU set information in a separate packet header extension field, the UPF entity can generate PDU set information and transmit it to the RAN through the GTP-U header confirmation field. The UPF entity can mark packets transmitted through different service floors that are updated for each service floor considering the same media characteristics based on the information in the N4 rule to be transmitted to the same QoS floor using related QoS information. Specifically, the PDU Set information can be composed of at least one of a PDU Set Sequence Number, an End PDU of the PDU Set, a PDU Set Size in bytes, a PDU Sequence Number within a PDU Set, and a PDU Set Importance. As above, when generating PDU set information for packets within a service floor transmitted from different ASs, if each is mapped to a different QoS floor, the UPF entity can perform the PDU set information generation operation.

[0212] When different service floors are mapped to the same QoS floor, an operation process may be required to create separate PDU set information. For example, the PDU set sequence number, the end PDU of the PDU set, the PDU set size in bytes, and the PDU SN within a PDU set within the PDU set information can be marked for each service floor even when mapped to the same QoS. However, the PDU set importance may require separate management as it is information indicating the importance between PDU sets.

[0213] If media packets in different service floors in a UPF entity are of different media types, i.e., in the case of video or audio, the UPF entity may generate separate PDU set importance information according to the policy of the network operator or service provider and include it in the PDU set information and transmit it to the RAN. For example, as shown in FIGS. 2 and 3, there may be no indicator (PDU set information support indication) indicating that PDU set information is provided for all packets in the protocol description information transmitted from the AF, or the PDU set information may be individually provided in the packet header extension field only in the protocol description information of video packets through an indicator. In the case of audio packets, PDU set information may not be provided from the AS, and by not providing a separate indicator in the protocol descriptor, the UPF entity or PCF entity may be notified whether the corresponding PDU set information is transmitted from the AS. In the absence of a separate directive as above, the PCF entity may recognize that it must perform PDU set information generation in the UPF for the audio packet and may include the relevant information in the PCC rule and transmit it to the UPF entity. In addition, the PCF entity may recognize that it does not receive a separate PDU set QoS profile or relevant information from the AF entity and may decide to perform mapping in the same manner as the existing QoS profile in the case of an interactive audio service packet transmitted as a single packet, thereby determining to generate a PDU set QoS profile for the audio packet.For example, when generating PDU set QoS profile information for audio service packets transmitted as a single packet for handling PDU sets of audio packets, PSDB (PDU set Delay Budget) can be mapped to the PDB (Packet delay budget) value within the QoS profile, and PSER (PDU set Error Rate) can be mapped to the PER (Packet Error Rate) value to perform the audio PDU set QoS profile generation operation.

[0214] Additionally, the PDU set importance value in the PDU set information of the audio packet can be generated by utilizing the Priority level value in the basic 5QI of each media service characteristic. For example, when using the QoS characteristic values ​​mapped to 5QI, it can be set by considering the media characteristics as audio (5QI = 1) and video (5QI = 2), and if they are set to Priority levels 20 and 40, respectively, the PDU set importance value can be set higher for the PDU set of the audio packet than for the video packet. However, since the above operation sets a separate QoS value to support the RTP bundle in the case of the RTP bundle, if there is a packet in the RTP bundle service floor for which the AS does not separately provide PDU set information, the standard 5QI value for each media type can be used only in the case of generating the PDU set information for the corresponding media type.

[0215] If media packets within different service floors in the UPF entity are of the same media type, i.e., if they are services in the same video format, the PDU set importance value in the PDU set information can be set according to the policy of the network operator or service provider. If, depending on the user's usage pattern, a service such as streaming video is used as an additional usage type while using the main XR service, the streaming video of the additional usage type can be set to a lower priority than the PDU set importance value of the main XR service in the UPF entity. In this way, when generating PDU set information for packets of the same media type within service floors that are transmitted to different ASs depending on the user's subscription type or service usage pattern, the UPF entity can decide to generate or update the PDU set importance of packets within each service floor according to the policy of the network operator or service provider.

[0216] At step 933, the UPF entity may forward downlink data containing PDU set information to the RAN.

[0217] In step 935, the RAN can perform a PDU set unit scheduling operation on packets within the QoS floor based on the PDU set QoS profile and PDU set information received in step 921.

[0218] FIG. 10 is a diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0219] As illustrated in FIG. 10, the terminal of the present disclosure may include a transceiver (1010), a memory (1020), and a terminal control unit (or processor 1030). The terminal control unit (1030), the transceiver (1010), and the memory (1020) may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the terminal control unit (1030), the transceiver (1010), and the memory (1020) may be implemented in the form of a single chip.

[0220] The transceiver (1010) is a general term for the terminal's receiving unit and the terminal's transmitting unit, and can transmit and receive signals with a base station or a network entity. The signals transmitted and received with the base station may include control information and data. To this end, the transceiver (1010) may be configured with an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts the received signal. However, this is only one embodiment of the transceiver (1010), and the components of the transceiver (1010) are not limited to an RF transmitter and an RF receiver.

[0221] In addition, the transceiver (1010) may include a wired / wireless transceiver and may include various configurations for transmitting and receiving signals. In addition, the transceiver (1010) may receive a signal through a wireless channel and output it to the terminal control unit (1030), and transmit the signal output from the terminal control unit (1030) through the wireless channel. In addition, the transceiver (1010) may receive a communication signal and output it to the terminal control unit (1030), and transmit the signal output from the terminal control unit (1030) to a base station or network entity through a wired / wireless network.

[0222] The memory (1020) can store programs and data necessary for the operation of the terminal. In addition, the memory (1020) can store control information or data included in signals acquired from the terminal. The memory (1020) 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.

[0223] The terminal control unit (1030) can control a series of processes so that the terminal can operate according to the embodiments of the present disclosure described above. The terminal control unit (1030) may include at least one processor. For example, the terminal control unit (1030) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

[0224] FIG. 11 is a diagram illustrating the structure of a base station according to one embodiment of the present disclosure. The base station illustrated in FIG. 11 may correspond to the RAN (radio access node) described above in FIGS. 1 to 9.

[0225] As illustrated in FIG. 11, the base station of the present disclosure may include a transceiver (1110), a memory (1120), and a base station controller (or processor, 1130). The base station controller (1130), the transceiver (1110), and the memory (1120) may operate according to the communication method of the base station described above. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. According to one embodiment, the base station of FIG. 11 may be implemented so that its entire function is separated into a CU and a DU, in which case the CU and the DU may each perform some of the functions performed by the base station of FIG. 11. In addition, the base station controller (1130), the transceiver (1110), and the memory (1120) of FIG. 11 may be implemented in the form of a single chip.

[0226] The transceiver (1110) is a general term for the receiving unit and the transmitting unit of the base station, and can transmit and receive signals with a terminal and / or a network entity. At this time, the transmitted and received signals may include control information and data. To this end, the transceiver (1110) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts the received signal. However, this is only one embodiment of the transceiver (1110), and the components of the transceiver (1110) are not limited to the RF transmitter and RF receiver. The transceiver (1110) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals.

[0227] In addition, the transceiver (1110) can receive a signal through a communication channel (e.g., a wireless channel) and output it to the base station control unit (1130), and transmit the signal output from the base station control unit (1130) through the communication channel. In addition, the transceiver (1110) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a terminal or network entity through a wired or wireless network.

[0228] The memory (1120) can store programs and data required for the operation of the base station. In addition, the memory (1120) can store control information or data included in signals acquired from the base station. The memory (1120) 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.

[0229] The base station control unit (1130) can control a series of processes so that the base station can operate according to the embodiments of the present disclosure described above. The base station control unit (1130) can include at least one processor. The methods according to the embodiments described in the claims or specification of the present disclosure can be implemented in the form of hardware, software, or a combination of hardware and software.

[0230] FIG. 12 is a diagram illustrating the structure of a network function (or network entity) according to one embodiment of the present disclosure. The network function (or network entity) illustrated in FIG. 12 may correspond to various functions or entities of the core network described above in FIGS. 1 to 9.

[0231] As illustrated in FIG. 12, the network function (NF) (or network entity) of the present disclosure may include a transceiver (1210), a memory (1220), and an NF control unit (or processor, 1230). The NF control unit (1230), the transceiver (1210), and the memory (1220) of the network function (or network entity) may operate according to the communication method of the network function (or network entity) described above. However, the components of the network function (or network entity) are not limited to the examples described above. For example, the network function (or network entity) may include more or fewer components than the components described above.

[0232] The transceiver (1210) is a general term for the receiving unit of a network function (or network entity) and the transmitting unit of a base station, and can transmit and receive signals with terminals, base stations, and / or other network functions (or network entities). At this time, the transmitted and received signals may include control information and data. For this purpose, the transceiver (1210) can communicate with nodes or base stations of the core network through wired or wireless transceivers. However, this is only one embodiment of the transceiver (1210), and the components of the transceiver (1210) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts the frequency, and may include various configurations for transmitting and receiving signals.

[0233] In addition, the transceiver (1210) can receive a signal through a communication channel (e.g., a wireless channel or a channel of a core network) and output it to the NF control unit (1230), and transmit the signal output from the NF control unit (1230) through the communication channel. In addition, the transceiver (1210) can receive a communication signal and output it to the NF control unit (1230), and transmit the signal output from the NF control unit (1230) to a terminal, a base station, or a network entity through a wired or wireless network.

[0234] The memory (1220) can store programs and data required for the operation of a network function (or network entity). Furthermore, the memory (1220) can store control information or data included in signals acquired from the network function (or network entity). The memory (1220) can be configured as a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media.

[0235] The NF control unit (1230) may control a series of processes so that a network function (or network entity) can operate according to the embodiments of the present disclosure described above. The NF control unit (1230) may include at least one processor. The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

[0237] 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 may include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0238] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or 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.

[0239] Additionally, the program may be stored on 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 implementing 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 implementing an embodiment of the present disclosure.

[0240] In the specific embodiments of the present disclosure described above, components included in the present 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.

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

Claims

1. A method performed by a PCF (policy control function) entity in a wireless communication system, A step of receiving a first message including a PDU (packet data unit) set handling indicator and PDU set handling information for a multiplexing service from an AF (application function) entity through a NEF (network exposure function) entity; A step of determining whether to support PDU set handling based on the multiplexing service based on the first message; and A method comprising the step of transmitting a second message to the AF entity via the NEF entity, indicating whether to support PDU set handling based on the multiplexing service.

2. In claim 1, if it is decided to support PDU set handling based on the multiplexing service, the method comprises: A step of updating the quality of service (QoS) of a multiplexed service floor based on the PDU set handling indicator and the PDU set handling information; A step of updating the above updated QoS to the PCC (policy and charging control) rule; and A method further comprising the step of transmitting a third message including the updated PCC rule to a session management function (SMF) entity.

3. In claim 1, A method wherein the above PDU set handling information includes a codec of packets for each media type, a sampling rate, a media type for packets within a service floor, and a PDU set handling indicator for packets within a service floor received from an AS (application server) entity.

4. In claim 1, A method in which the PDU set handling indicator and the PDU set handling information are received and included in a protocol descriptor.

5. A method performed by an AF (application function) entity in a wireless communication system, Step for determining support for multiplexing services; Based on the above decision, a step of transmitting a first message including a PDU (packet data unit) set handling indicator and PDU set handling information for the multiplexing service to a PCF (policy control function) entity through a NEF (network exposure function) entity; A method comprising the step of receiving a second message from the PCF entity via the NEF entity, the second message indicating whether PDU set handling based on the multiplexing service is supported.

6. In claim 5, A method wherein the above PDU set handling information includes a codec of packets for each media type, a sampling rate, a media type for packets within a service floor, and a PDU set handling indicator for packets within a service floor received from an AS (application server) entity.

7. In claim 5, A method in which the PDU set handling indicator and the PDU set handling information are transmitted while being included in a protocol descriptor.

8. In a wireless communication system, in the PCF (policy control function) entity, transceiver; and A controller coupled with the above transmitter and receiver is included, The above controller, Receive a first message including a PDU (packet data unit) set handling indicator and PDU set handling information for a multiplexing service from an AF (application function) entity through a NEF (network exposure function) entity, Based on the first message above, determine whether to support PDU set handling based on the multiplexing service, A PCF entity configured to transmit a second message to the AF entity via the NEF entity, indicating whether PDU set handling based on the multiplexing service is supported.

9. In claim 8, if it is decided to support PDU set handling based on the multiplexing service, the controller, Update the QoS (quality of service) of the multiplexed service floor based on the above PDU set handling indicator and the above PDU set handling information, Update the above updated QoS to the PCC (policy and charging control) rule, A PCF entity configured to send a third message containing the updated PCC rule to a session management function (SMF) entity.

10. In claim 8, The above PDU set handling information is a PCF entity that includes the codec of packets for each media type, sampling rate, media type for packets within the service floor, and PDU set handling indicator for packets within the service floor received from an AS (application server) entity.

11. In claim 8, A PCF entity that receives the PDU set handling indicator and the PDU set handling information included in the protocol descriptor.

12. In the AF (application function) entity in a wireless communication system, transceiver; and A controller coupled with the above transmitter and receiver is included, The above controller, Decide on support for multiplexing services, Based on the above decision, a first message including a PDU (packet data unit) set handling indicator and PDU set handling information for the multiplexing service is transmitted to a PCF (policy control function) entity through a NEF (network exposure function) entity, An AF entity configured to receive a second message from the PCF entity via the NEF entity, indicating whether PDU set handling based on the multiplexing service is supported.

13. In claim 12, The above PDU set handling information is an AF entity including the codec of packets for each media type, sampling rate, media type for packets within the service floor, and PDU set handling indicator for packets within the service floor received from an AS (application server) entity.

14. In claim 12, An AF entity in which the PDU set handling indicator and the PDU set handling information are transmitted included in a protocol descriptor.

Citation Information

Patent Citations

  • Method and apparatus for supporting clock synchronization of user equipment in wireless communication system

    US20220322257A1

  • Systems and methods to optimize registration and session establishment in a wireless network

    US20230137283A1