Enhanced 5GS user plane processing for XR services

Abstract

A method and apparatus for processing Extended Reality (XR) traffic is disclosed. In one embodiment, a Session Management Function (SMF) comprises a processor and a transceiver coupled to the processor, the processor is configured to: construct stream information and PDU set aggregation packet processing information for a particular User Equipment (UE) or Protocol Data Unit (PDU) session, the stream information including at least one stream indicator indicating a respective stream associated with XR traffic, the PDU set aggregation packet processing information including an indication of a PDU set aggregation packet processing associated with each stream indicator, and transmit the constructed stream information and PDU set aggregation packet processing information to a User Plane Function (UPF) or a Radio Access Network (RAN) node via the transceiver.

Description

[Technical field]

[0001] The subject matter disclosed herein relates generally to wireless communications, and more specifically, to 5GS user plane processing enhancements for XR services. [Background technology]

[0002] The following abbreviations are defined herein, at least some of which may be referenced in the description that follows. New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM or Flash memory), Compact Disc Read-Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), User Equipment (UE), Evolved Node B (eNB), Next Generation Node B (gNB), Uplink (UL), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Orthogonal Frequency Division Multiplexing (ORDM), OFDM, Radio Resource Control (RRC), User Entity / Device (Mobile Terminal), Extended Reality (XR), Augmented Reality (AR), Virtual Reality (VR), Cloud Gaming (CG), Quality of Service (QoS), Field of View (FOV), Group of Picture (GoP), Intra Frame (Intraframe (I-frame), Predictive frame (P-frame), Bi-directional frame (B-frame), XR and Media service (XRM), Protocol Data Unit (PDU), Application Function (AF), Radio Access Network (RAN), 5G System (5GS), User Plane Function (UPF), Intermediate UPF (I-UPF), Session Management Function (SMF), service data flow (SDF), serial number (SN), Internet Protocol (IP), QoS Flow ID (QFI), GPRS Tunnelling Protocol User Plane (GTP-U), 5G QoS Identifier (5QI), slice / service type type:SST), Single Network Slice Selection Assistance Information (S-NSSAI), Service Differentiator (SD), Data Network Name (DNN), 5G core (5GC), Application Service Provider (ASP), Policy Control Function (PCF), Network Exposure Function (NEF), Packet Flow Description (PFD), Packet Flow Description Function (PFC),Description Function:PFDF), Operations and Maintenance:OAM, Policy and Charging Control:PCC, Packet Detection Rule:PDR, Forwarding Action Rule:FAR, Core network (CN), Technical Specification (TS), Access and Mobility Management Function (AMF), Unified Data Repository (UDR), Data Network (DN), Information Element (IE), Session Management Function (SMF).

[0003] Extended Reality (XR), including Augmented Reality (AR) and Virtual Reality (VR), and Cloud Gaming (CG) are important media applications for 5G. XR or CG applications may have multiple data streams with different traffic characteristics (e.g., traffic types) and QoS requirements in both DL and UL. For example, FOV (Field of View) streams, omnidirectional streams, video and audio streams, haptic streams, etc. Packets of the same video stream may have different frame types (e.g., I-frames, P-frames, B-frames).

[0004] I-frames are complete images, as intra-coded images, that can be encoded and decoded independently, like a JPG image file.

[0005] As a prediction image, a P frame does not contain a complete frame, but only the changes in the image compared to the previous frame. If the reference frame is lost, the P frame cannot be decoded and displayed.

[0006] As bidirectionally predicted images, B frames contain the changes between the previous and next reference frames. The more reference frames there are, the higher the compression ratio can be. However, B frames can only be decoded if the previous and next reference frames are available.

[0007] A Group of Pictures (GOP) contains a collection of consecutive video frames. The first frame in a GOP is an I-frame. Subsequent frames can be P-frames or B-frames.

[0008] A PDU set consists of one or more PDUs carrying the payload of one information unit (e.g., a frame or a video slice of an XRM service) generated at the application level, which have the same importance requirement at the application layer. All PDUs in a PDU set are required by the application layer to use the corresponding information unit. In some cases, even if some PDUs are missing, the application layer can still recover part of the information unit.

[0009] Considering the nature of PDU sets, PDUs in one PDU set need to be processed jointly, which is called PDU set joint packet processing. For example, 5GS shall ensure that all PDUs in one PDU set are received or successfully delivered to the UE, unless the application function (AF) indicates that an incomplete PDU set is acceptable. On the other hand, to perform joint decoding, PDUs in one PDU set need to be successfully delivered to the UE within a given time. Packets of the same video stream, but with different frame types (e.g., I-frames and P-frames) or different positions in the GoP (Group of Pictures), have different importance and contribute differently to the user experience. Prioritizing the transmission of more important streams helps to improve capacity. In case of congestion, packets of less important streams can be dropped to alleviate and restore congestion. Considering the fact that P-frames and B-frames cannot be decoded and displayed if a reference frame (e.g., I-frame) is lost, there is a dependency between different PDU sets. If the Reference PDU Set is lost, other frames that depend on the Reference PDU Set may be dropped.

[0010] As mentioned above, in some cases, even if some PDUs are missing, the application layer can still recover part of the information unit. The following example considers partial recovery of a set of PDUs. Example 1

[0011] If a PDU set contains multiple encoding units, some of the encoding units can be restored individually. If a PDU set contains a single encoding unit, some of the PDUs cannot be restored if some PDUs are missing. Example 2

[0012] Different applications have different ways of dealing with an incomplete set of PDUs, and some decoders may accept an incomplete set of PDUs while others may not. Example 3

[0013] Since different UEs have different codecs or decoding capabilities, some UEs may be able to perform partial recovery of a PDU set even if some PDUs of the PDU set are missing, while other UEs cannot.

[0014] Therefore, the above PDU set aggregation packet processing is not necessarily implemented by the UPF and / or RAN node (e.g., NG-RAN node). In the above examples 1 and 2, the PDU set aggregation packet processing mainly depends on the application type or traffic mode. On the other hand, the PDU set aggregation packet processing depends on the decoding capability of the UE in example 3. Considering the fact that partial reconstruction may be tolerated by the receiving decoder, there is another use case. If the reference PDU set (e.g., I-frame) allows partial reconstruction of the incomplete case, the PDU set dependent on the reference PDU set may still be useful in the receiving decoder. [Prior art documents] [Non-patent literature]

[0015] [Non-Patent Document 1] 4.3.6.2 of TS 23.502 [Non-Patent Document 2] 4.3.2.2.1 of TS 23.502 [Non-Patent Document 3] TS 38.413 [Non-Patent Document 4] 4.3.3.2 in TS 23.502 [Non-Patent Document 5] 4.15.6.6 of TS 23.502 [Non-Patent Document 6] TS 23.502 4.3.6.4 [Non-Patent Document 7] 4.3.3.2.1 of TS 23.502 [Non-Patent Document 8] TS 38.415 Summary of the Invention [Problem to be solved by the invention]

[0016] The present disclosure aims to solve the following problems:

[0017] If not all PDUs are received or delivered correctly, how can 5GS know whether partial recovery is acceptable to the application layer? In other words, does it need to perform PDU set integration packet processing?

[0018] If all PDUs of a Reference PDU Set have not been received or delivered, how can 5GS know whether a PDU Set that depends on the Reference PDU Set is still useful?

[0019] How does the UPF know when to deliver a set of PDUs, how does it determine if a set of PDUs has been lost or dropped, and how does the UPF notify downstream UPFs and the AN of packet drops?

[0020] How does the UPF, the RAN node (e.g., NG-RAN node), and / or the UE know which type of PDU set it can drop in case of congestion? [Means for solving the problem]

[0021] A method and apparatus for processing XR and media traffic is disclosed.

[0022] In one embodiment, the SMF comprises a processor and a transceiver coupled to the processor, the processor being configured to: construct, for a particular UE or PDU session, stream information and PDU set aggregation packet processing information, the stream information including at least one stream indicator indicating a stream each associated with XR traffic, the PDU set aggregation packet processing information including an instruction for PDU set aggregation packet processing associated with each stream indicator; and transmit, via the transceiver, the constructed stream information and PDU set aggregation packet processing information to a UPF or RAN node.

[0023] In some embodiments, the processor is configured to construct stream information and associated PDU set integrated packet processing information based on pre-configuration, the stream information including at least one of a 5QI, an SST or an S-NSSAI, a DNN, and an appId.

[0024] In some embodiments, the processor is configured to construct stream information and associated PDU set integrated packet processing information based on PCC rules provided by the PCF, the stream information including at least one of a QFI, a stream ID, a frame type, an importance value, and a service data flow filter.

[0025] In some embodiments, if the PDU set consolidation packet processing indication is true, the associated PDU set consolidation packet processing information further includes at least one of a dependency discard indication, a discard timer, and a discard type.

[0026] In one embodiment, the processor is configured to send constructed stream information, including at least one of a QFI, an appId, a service data flow filter, a frame type, and an importance value, and associated PDU set integrated packet processing information to the UPF.

[0027] In another embodiment, the processor is configured to transmit the constructed stream information, including at least one of a QFI, a stream ID, a frame type, and an importance value, and the associated PDU set aggregate packet processing information to the RAN node.

[0028] In another embodiment, a network node (e.g., a User Plane Function (UPF) or RAN node) of the network architecture comprises a processor and a transceiver coupled to the processor, wherein the processor is configured to receive, via a receiver, stream information and associated PDU set aggregation packet processing information for a particular UE and PDU session from a Session Management Function (SMF) of the network architecture, where the stream information includes at least one stream indicator indicating a stream each associated with XR traffic, and the PDU set aggregation packet processing information includes a PDU set aggregation packet processing instruction associated with each stream indicator, and to process each stream indicated by the at least one stream indicator included in the stream information in accordance with the PDU set aggregation packet processing instruction associated with the stream indicator indicating that stream.

[0029] In some embodiments, the processor is configured to provide discarded PDU set information associated with the PDU set to a downstream node if the PDU set is not completely received.

[0030] In some embodiments, the stream information includes at least one of a 5QI, an SST or an S-NSSAI, a DNN, an appId, a QFI, a stream ID, a frame type, an importance value, and a service data flow filter.

[0031] In some embodiments, if the PDU set consolidation packet processing indication is true, the associated PDU set consolidation packet processing information further includes at least one of a dependency discard indication, a discard timer, and a discard type.

[0032] In another embodiment, the method comprises constructing, from a Session Management Function (SMF), stream information and PDU set aggregation packet processing information for a particular UE or PDU session, where the stream information includes at least one stream indicator indicating a stream each associated with XR traffic, and the PDU set aggregation packet processing information includes an indication of a PDU set aggregation packet processing associated with each stream indicator, and transmitting the constructed stream information and PDU set aggregation packet processing information to a UPF or RAN node via a transceiver.

[0033] In a further embodiment, the method comprises the steps of receiving, for a particular UE and PDU session, stream information and associated PDU set aggregation packet processing information, where the stream information includes at least one stream indicator indicating a stream each associated with XR traffic, and the PDU set aggregation packet processing information includes a PDU set aggregation packet processing instruction associated with each stream indicator, and processing each stream indicated by the at least one stream indicator included in the stream information in accordance with the PDU set aggregation packet processing instruction associated with the stream indicator indicating that stream.

[0034] A more particular description of the embodiments briefly described above will be made by reference to specific embodiments illustrated in the accompanying drawings, in which the embodiments will be described and explained with further particularity, with the understanding that these drawings illustrate only some embodiments and are therefore not limiting in scope, and through which the embodiments will be described and explained with further particularity and detail. [Brief description of the drawings]

[0035] [Figure 1] FIG. 2 illustrates a first sub-embodiment of the first embodiment. [Diagram 2] FIG. 2 illustrates a second sub-embodiment of the first embodiment. [Diagram 3] FIG. 13 is a diagram illustrating an example of a fourth embodiment. [Figure 4] FIG. 1 is a schematic flow chart diagram illustrating a method embodiment. [Diagram 5] FIG. 11 is a schematic flow chart diagram illustrating a further embodiment of a method. [Figure 6] FIG. 2 is a schematic block diagram illustrating another apparatus according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0036] As will be appreciated by those skilled in the art, certain aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Thus, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which may be generally referred to herein as a "circuit," "module," or "system." Furthermore, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as "code." The storage devices may be tangible, non-transitory, and / or non-transmittal. The storage devices may not embody signals. In certain embodiments, the storage devices employ only signals to access the code.

[0037] Certain functional units described herein may be labeled as "modules" to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit comprising custom very large scale integrated (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0038] Modules may also be implemented in code and / or software for execution by various types of processors. An identified module of code may include one or more physical or logical blocks of executable code that may be organized as, for example, an object, procedure, or function. However, executable files of an identified module need not be physically located together, but may include different instructions stored in different locations that, when logically combined, comprise a module and achieve the specified purpose of the module.

[0039] Indeed, a module of code may comprise a single instruction or multiple instructions and may be distributed over multiple different code segments, among different programs, and across multiple memory devices. Similarly, operational data may be identified and illustrated herein in modules and may be embodied in any suitable form and organized in any suitable type of data structure. This operational data may be collected as a single data set or distributed in various locations, including different computer-readable storage devices. If a module or portions of a module are implemented in software, the software portions are stored in one or more computer-readable storage devices.

[0040] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device that stores the code. The storage device may be, but is not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0041] A non-exhaustive list of more specific examples of storage devices includes an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM or flash memory), a portable compact disk read only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this specification, a computer-readable storage medium may be any tangible medium that contains or can store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0042] Code for carrying out the operations of the embodiments may include any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and the like, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code may be performed entirely on the user's computer, may run partially on the user's computer, may run partially on the user's computer as a standalone software package, partially on the remote computer, or may run entirely on a remote computer or server. In the last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), and a connection to an external computer may be made (e.g., through the Internet using an Internet Service Provider).

[0043] Reference throughout this specification to "one embodiment," "an embodiment," or similar terms means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Thus, phrases such as "in one embodiment," "in an embodiment," and the like, used throughout this specification, may, but do not necessarily, all refer to the same embodiment, but mean "one or more but not all embodiments," unless expressly specified otherwise. Terms such as "including," "comprising," "having," and derivatives thereof mean "including but are not limited to," unless expressly specified otherwise. An enumerated list of items does not imply that some or all of the items are mutually exclusive, unless expressly specified otherwise. Additionally, the terms "a," "an," and "the" also refer to "one or more," unless expressly specified otherwise.

[0044] Furthermore, the described features, structures, or characteristics of various embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, and the like, to provide a thorough understanding of the embodiments. However, one skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details or using other methods, components, materials, and the like. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0045] Aspects of various embodiments are described below with reference to schematic flowchart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowchart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flowchart illustrations and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to generate a machine whose instructions, when executed via a processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart illustrations and / or schematic block diagrams for a block or group of blocks.

[0046] Code may also be stored in a storage device, where the instructions stored in the storage device can direct a computer, other programmable data processing apparatus, or other device to function in a particular manner to produce an article of manufacture including instructions implementing functions specified in the schematic flow chart illustrations and / or schematic block diagrams for a block or group of blocks.

[0047] The code may also be loaded into a computer, other programmable data processing apparatus, or other device to generate a computer-implemented process such that the code executed on the computer or other programmable apparatus provides a process for implementing the functions specified in the flowcharts and / or block diagrams for a block or groups of blocks such that a series of operational steps are executed on the computer, other programmable apparatus, or other device.

[0048] The schematic flow chart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flow chart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions of code for implementing a specified logical function(s).

[0049] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may be performed substantially concurrently or in the reverse order, depending on the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, depicted in the figures.

[0050] Various arrow and line types may be employed in the flowcharts and / or block diagrams, but it is understood that they are not limiting the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the illustrated embodiment. For example, the arrows may indicate waiting or monitoring periods of unspecified duration between recited steps of the illustrated embodiment. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or operations, or a combination of dedicated hardware and code.

[0051] The description of an element in each drawing may refer to the element in a previous drawing. The same number refers to the same element in all drawings, including alternative embodiments of the same element.

[0052] Before describing the procedure of the present disclosure, an overview of the distribution of XR traffic, which may be traffic generated by XR, CG applications, or other types of media applications, is provided. XR traffic originates from an application server. In this disclosure, the application server and the application function (AF) may not be distinguished. In other words, it can be said that XR traffic originates from the AF.

[0053] XR traffic is sent from the AF to the UPF and is forwarded by Service Data Flows (SDFs) or IP packet flows. Each packet is a PDU.

[0054] The established PDU session is between the UPF and the UE. There may be various QoS flows in the established PDU session. Typically, XR traffic is transferred from the UPF to the RAN node (e.g., NR-RAN node: gNB) and from the RAN node to the UE in the QoS flow of the PDU session. There may be an intermediate UPF (I-UPF) between the UPF and the RAN node.

[0055] Different packets (e.g., different PDUs) of XR traffic may have different importance requirements. A stream may be defined as being associated with packets of XR traffic with a particular importance requirement. For example, an I-frame stream has a higher importance requirement than a P-frame stream. Thus, streams with different importance requirements may be processed in different ways.

[0056] Therefore, there is a need to identify different streams (ie, streams having different importance requirements) and associate different processes with the different streams.

[0057] This disclosure proposes different stream indicators to indicate different streams. The stream indicators are collectively referred to as stream information. Furthermore, this disclosure proposes "user plane processing auxiliary information" which is used to describe the processing auxiliary information. The "user plane processing auxiliary information" may include "PDU set aggregation packet processing information" and optionally "distribution information".

[0058] The "PDU set consolidation packet processing information" includes a "PDU set consolidation packet processing instruction", and may further include a "dependency discard instruction", a "discard timer", a "discard type", etc. Note that the expression "discard" can be replaced with "drop".

[0059] The "PDU set aggregation packet processing instruction" is performed for each stream indicator.

[0060] For example, if the stream information includes stream indicator #1 and stream indicator #2, the "PDU set aggregation packet processing information" includes a "PDU set aggregation packet processing instruction" associated with stream indicator #1 and a "PDU set aggregation packet processing instruction" associated with stream indicator #2. Alternatively, the PDU set aggregation packet processing instruction can be associated with all XR streams. In other words, all XR streams can be identified by one stream indicator.

[0061] A stream indicated by one indicator is expected to be processed according to the "PDU Set Aggregation Packet Processing Instructions" associated with one stream indicator. For example, if there are two indicators, indicator #1 and indicator #2, the stream indicated by indicator #1 is processed according to the "PDU Set Aggregation Packet Processing Instructions" associated with stream indicator #1, and the stream indicated by indicator #2 is processed according to the "PDU Set Aggregation Packet Processing Instructions" associated with stream indicator #2.

[0062] The "PDU set consolidation packet processing indication" is used to indicate whether to discard (or drop) the incomplete PDU set or to discard (or drop) the remaining PDUs of the incomplete PDU set. The "PDU set consolidation packet processing indication" can have the value "true" or "false", or the value "1" or "0". For example, "true" or "1" means that PDU set consolidation packet processing is required, i.e. partial recovery of the PDU set is not possible. If some PDUs are lost or not successfully delivered within the given PDU set delay budget, the PDUs of the PDU set are dropped. On the other hand, "false" or "0" means that PDU set consolidation packet processing is not required, i.e. partial recovery of the PDU set is possible and no PDUs of the PDU set need to be dropped.

[0063] Here, we assume that there are two different streams: stream indicator #1 indicates an I-frame stream and stream indicator #2 indicates a P-frame stream. Thus, the "PDU set aggregation packet processing indication" associated with stream indicator #1 can be "false" or "0", i.e., no PDU set aggregation packet processing is required for the I-frame stream. Meanwhile, the "PDU set aggregation packet processing indication" associated with stream indicator #2 can be "true" or "1", i.e., PDU set aggregation packet processing is required for the P-frame stream.

[0064] If the "PDU set consolidation packet processing indication" associated with one stream indicator (e.g., indicating a P-frame stream) is set to "true" or "1", the "PDU set consolidation packet processing information" may further include at least one of a "dependency discard indication", a "discard timer", and a "discard type" associated with the one stream indicator. For example, the "PDU set consolidation packet processing information" may further include at least one of a "dependency discard indication", a "discard timer", and a "discard type" associated with stream indicator #2 (indicating a P-frame stream).

[0065] On the other hand, if the "PDU Set Consolidation Packet Processing Indication" associated with another stream indicator (e.g., indicating an I-frame stream) is set to "false" or "0", i.e., no PDU set consolidation packet processing is required for the stream indicated by the other stream (e.g., an I-frame stream), then the "PDU Set Consolidation Packet Processing Information" does not include the "Dependency Discard Indication", "Discard Timer", and "Discard Type" associated with the other stream indicator.

[0066] The "dependency discard indication" is used to indicate whether the PDU sets that depend on the incomplete PDU set should be discarded (or dropped). The "dependency discard indication" can have a value of "true" or "false", or a value of "1" or "0". For example, "true" or "1" means that the PDU sets that depend on the incomplete PDU set should be discarded, and "false" or "0" means that the PDU sets that depend on the incomplete PDU set should not be discarded.

[0067] The "discard timer" is used to determine when a PDU set should be discarded. For example, the "discard timer" is started upon reception of the first PDU of the PDU set. If the PDU set is not successfully received (e.g., at least one PDU of the PDU set was lost or not successfully received) when the "discard timer" expires, the PDU set is discarded.

[0068] "Discard type" is used to indicate the kind of packets (eg, traffic type, frame type, importance value) that can be discarded (or dropped) in a congestion situation.

[0069] As mentioned above, the “dependency discard indication”, “discard timer”, and “discard type” associated with a stream indicator can be included in the “PDU set consolidation packet processing information” only if the “PDU set consolidation packet processing indication” associated with the stream indicator is “true” or “1”. However, even if the “PDU set consolidation packet processing indication” associated with a stream is “true” or “1”, the “PDU set consolidation packet processing information” may not include any of the “dependency discard indication”, “discard timer”, and “discard type” associated with the stream indicator. For example, the UPF or RAN node determines the “dependency discard indication”, “discard timer”, and / or “discard type” by pre-configuration. Alternatively, the RAN node performs PDU set consolidation packet processing as a transmitter (e.g., when transmitting a PDU set), i.e., determines whether the PDUs of the PDU set have been successfully delivered to the UE based on the UE feedback or based on the PDU set delay budget. However, the UPF and RAN nodes do not perform PDU set consolidation packet processing as a receiver (e.g., when receiving a PDU set).

[0070] The present disclosure proposes that each PDU destined for (i.e., transmitted to) a UPF and / or a RAN node (e.g., an NG-RAN node) includes PDU set related information, which is used to identify 1) which PDU set the PDU belongs to, 2) the importance of the PDU set, and 3) dependencies between PDU sets.

[0071] For example, each PDU may include some or all of the PDU set related information as follows:

[0072] 1) PDU set SN (serial number), SN within the PDU set, PDU set end marker, PDU number (or size) of the PDU set. In general, in order for a UPF and / or RAN node to identify "which PDU set a PDU belongs to", it needs to know at least one of the PDU set SN, SN within the PDU set, and (PDU set end marker, and PDU number of the PDU set).

[0073] 2) Importance: For example, an Importance IE may be inserted into each PDU of a PDU set or into some PDUs of a PDU set.

[0074] 3) Dependency Indicator: The dependency indication has values ​​of "standalone", "backward", and "forward and backward", or the dependency indication has values ​​of "I-frame", "P-frame", and "B-frame".

[0075] 4) Stream ID or QFI or (QFI and Stream ID). It is assumed that the UPF can identify different streams of XR traffic by the stream ID provided by the application layer. Furthermore, the UPF is configured by the SMF to identify different streams of XR traffic by the frame type or importance value provided by the application layer. Thus, the stream ID can be replaced by the frame type or importance value. The UPF delivers the PDUs of the PDU set of one stream to the RAN node in the N3 GTP-U tunnel based on the granularity of the PDU session. If one QoS flow contains a single XR traffic stream, the RAN node needs to be able to identify the PDU set per QoS flow, for example, by the QoS flow ID (QFI). If one QoS flow contains multiple streams, the RAN node needs to be able to identify the PDUs set by both the QFI and the stream ID. Considering the above, the SMF provides the QFI or (QFI and Stream ID) to the RAN node to be able to identify the PDU set of each stream.

[0076] The PDU-set related information can be provided from the application layer as a new IE in the IP header, or an extended IP header, or a new header between the IP header and the content. It is assumed that the UPF only forwards the IP packets containing the PDU-set related information. Alternatively, it is assumed that the UPF copies the PDU-set related information provided by the application server and pastes it into a newly defined container in the extended GTP-U header, e.g. an application-specific container, or a PDU-set-specific container.

[0077] Examples of stream indicators may be:

[0078] (1) Specific 5QI values ​​for XR traffic:

[0079] A first example of a stream indicator is a specific 5QI value for XR traffic. Several pre-configured 5QI values ​​or new standardized 5QI values ​​can be defined for XR traffic, for example, 5QI values=11, 12, 13 are specified or pre-configured for XR traffic. The PCF includes the pre-configured 5QI value (or the new standardized 5QI value) with a service data flow (SDF) filter or flow description in a PCC rule, so that the SMF recognizes that the SDF or IP packet flow contains XR traffic based on the pre-configured 5QI value or the new standardized 5QI value. It is also assumed that the SMF is pre-configured with a mapping relationship between the 5QI value and the "PDU set integrated packet processing information". For example, if 5QI values=11, 12, 13 are for XR traffic, the SMF is pre-configured with "PDU Set Aggregation Packet Processing Information" including a "PDU Set Aggregation Packet Processing Indication" associated with 5QI=11, a "PDU Set Aggregation Packet Processing Indication" associated with 5QI=12, and a "PDU Set Aggregation Packet Processing Indication" associated with 5QI=13. Note that the same "PDU Set Aggregation Packet Processing Indication" can be mapped to multiple 5QI values. For example, the "PDU Set Aggregation Packet Processing Information" can include a "PDU Set Aggregation Packet Processing Indication" associated with 5QI=11 and 5QI=12.

[0080] (2) a specific SST or S-NSSAI or DNN defined for XR traffic;

[0081] A second example of stream information is a slice / service type (SST) or S-NSSAI and optionally a DNN. A new network slice type, i.e., a new slice / service type (SST), is defined to support XR and media services. For example, SST=6 is defined to represent XR traffic. During the PDU session establishment procedure, the AMF provides the S-NSSAI of the PDU session, including the SST and a service differentiation factor (SD), to the SMF. The SMF identifies that the PDU session is for XR and media services based on the SST value or S-NSSAI. The SMF may also take the DNN into account, e.g., a combination of the S-NSSAI or the SST and the DNN may be used by the SMF to identify XR traffic. It is also assumed that the SMF has a preconfigured mapping relationship between the SST or S-NSSAI or (SST or S-NSSAI and DNN) and the "PDU set integrated packet processing information".

[0082] The mapping of the SST or S-NSSAI or (SST or S-NSSAI and DNN) and the "PDU set aggregation packet processing information" can be provided by the Application Function (AF). In particular, the AF can provide an AF request with an AF service identifier and the "PDU set aggregation packet processing information" based on the procedure defined in 4.3.6.2 of TS 23.502. Then, the 5GC (e.g., NEF) converts the AF service identifier to the target DNN and S-NSSAI. In this way, the SMF obtains the mapping of the SST or S-NSSAI or (S-NSSAI, DNN) and the "PDU set aggregation packet processing information".

[0083] (3) Application Identifier (i.e., AppId) or AppId and Packet Flow Description Identifier (i.e., Packet Flow Description Identifier: pfdId)

[0084] When the UPF is configured to detect a specific application provided by an ASP, for example, when the PCF provides a PCC rule including an AppId, a third example of a stream indicator may be an AppId or (AppId and pfdId). That is, the AppId or a combination of AppId and pfdId may be used to identify XR traffic. The AppId or (AppId and PFD) and the associated "PDU set aggregation packet processing information" may be provided from the AF to the NEF. Or, the associated "PDU set aggregation packet processing information" may be included in the PFD. In this state, the AppId and PFD (including the associated "PDU set aggregation packet processing information") are provided from the AF to the NEF (e.g., the PFDF in the NEF). The SMF may obtain a mapping of the AppId or (AppId and pfdId) and the associated "PDU set aggregation packet processing information" according to the AppId or (AppId and pfdId) from the NEF (e.g., the PFDF in the NEF).

[0085] The above examples apply to all UEs. The following examples apply to specific UEs or PDU sessions.

[0086] (4) QFI, or a combination of QFI and stream ID (or frame type or importance value)

[0087] The UPF can identify different streams of XR traffic by the stream ID provided by the application server. Additionally, the UPF can identify different streams of XR traffic by the frame type or importance value provided by the application server. Thus, the stream ID can be replaced by the frame type or importance value. If one QoS flow contains a single XR traffic stream, the RAN node must be able to identify the PDU set per QoS flow, for example by the QFI. If one QoS flow contains multiple streams, the RAN node must be able to identify the PDUs set by both the QFI and the stream ID.

[0088] (5) PDU Session ID, or (PDU Session ID and QFI) or (PDU Session ID, QFI and Stream ID)

[0089] XR traffic can be identified by a combination of PDU Session ID and QFI, or a combination of PDU Session ID, QFI and Stream ID, where the F-SEID is the PDU Session ID used by the SMF and UPF to identify the PDU session, or a mapping of "PDU Set Aggregated Packet Processing Information" associated with (PDU Session ID and QFI), or (PDU Session ID, QFI and Stream ID) can be provided by the SMF to the UPF.

[0090] (6) Flow description

[0091] XR traffic can be identified by a flow description. The AF may provide a frame type or importance associated with the flow description. The flow description provided by the AF may be obtained by the PCF. The PCF may provide the SMF with a service data flow template that may include the flow description as a service data flow filter. Thus, the SMF configures the UPF with the frame type or importance associated with the packet filter set (i.e., the flow description). The UPF can then identify the frame type or importance based on the packet filter set.

[0092] The "user plane processing auxiliary information" may further include "distribution information." The "distribution information" may include "number of PDUs or percentage threshold for distribution," "distribution timer," "delay timer," and the like.

[0093] The "PDU number or percentage threshold for delivery" indicates a threshold for delivering PDUs of a particular PDU set to a downstream node (e.g., I-UPF, RAN node) or UE. This means that delivery of PDUs of a PDU set to a downstream node or UE is started when the number of PDUs of the PDU set (i.e., equal to the number threshold) is received or when a part of the total number of PDUs of the PDU set is received. For example, assume that one PDU set consists of 8 PDUs and the UPF and / or RAN node may start delivery of PDUs of one PDU set when at least 4 (i.e., the number threshold) PDUs or 50% (i.e., the percentage threshold) of the PDU set are received. If the "PDU number threshold for delivery" is configured as 1, the PDUs are delivered to the downstream UPF or RAN node or directly to the UE as soon as they are received. If the "PDU percentage threshold for delivery" is configured as 100%, the PDUs of one PDU set are delivered until all PDUs of one PDU set are received.

[0094] The "Delivery Timer" is used to determine when to deliver the PDUs of the PDU set. The "Delivery Timer" is started upon receipt of the first PDU of the PDU set. When the "Delivery Timer" expires, delivery of the PDUs of the PDU set is initiated.

[0095] The "delay timer" is used to determine when delivery of the PDUs of the PDU set stops and the remaining PDUs of the PDU set (i.e., undelivered PDUs) are discarded. The "delay timer" is started upon delivery of the first PDU of the PDU set. When the "delay timer" expires, delivery of the PDUs of the PDU set (e.g., to downstream nodes or UEs) stops and the remaining PDUs of the PDU set (i.e., undelivered PDUs) are discarded.

[0096] In general, the UPF applies a "PDU count or percentage threshold for delivery" or a "delivery timer". The UPF and RAN nodes apply a "delay timer".

[0097] The "delivery information" may also be associated with a stream indicator.

[0098] According to the first embodiment, the SMF configures the UPF and / or RAN nodes with "stream information" and "user plane processing auxiliary information" in the control plane.

[0099] For simplicity of explanation, it is assumed that the "user plane processing auxiliary information" only includes the "PDU set aggregation packet processing information".

[0100] As mentioned above, examples of stream indicators in the "Stream Information" may be a 5QI, an SST or an S-NSSAI, (SST or S-NSSAI and DNN), an AppId, (AppId and pfdId), a QFI, (QFI and Stream ID), a PDU Session ID, (PDU Session ID and QFI), (PDU Session ID and QFI and Stream ID), a flow description, or a service data flow filter, or a packet filter set.

[0101] The mapping of "stream information" and "PDU set aggregation packet processing information" may be pre-configured in the SMF (e.g., through an OAM configuration provided by the operator or through a per-node configuration from the AF via the NEF or via the PCF), or may be provided by the PCF based on PCC rules or provided by the AF. For example, the AF provides "stream information" and "PDU set aggregation packet processing information" to the NEF (e.g., the PFDF in the NEF), which provides them to the SMF. The AF provides "stream information" and PDU set aggregation processing information to the PCF (e.g., via the NEF), which provides them to the SMF in PCC rules.

[0102] Thus, the SMF may construct "stream information" and "PDU set aggregation packet processing information", where the "stream information" includes at least one stream indicator each indicating a stream associated with XR traffic, and the "PDU set aggregation packet processing information" includes "PDU set aggregation packet processing instructions" associated with each stream indicator included in the "stream information".

[0103] According to a first sub-embodiment of the first embodiment, the SMF provides "stream information" and "PDU set aggregation packet processing information" in a modified PDU session establishment procedure.

[0104] FIG. 1 shows a modified PDU session establishment procedure according to a first sub-embodiment of the first embodiment.

[0105] The conventional PDU session establishment procedure is described in 4.3.2.2.1 in TS 23.502. According to the first sub-embodiment of the first embodiment, steps 1-9 and 13-21 of the conventional PDU session establishment procedure are not changed. In the modified PDU session establishment procedure according to the first sub-embodiment of the first embodiment, steps 10a, 10b, 11, and 12 are modified.

[0106] The UE triggers the PDU session establishment procedure in steps 1 to 9, which are the same as steps 1 to 9 of the conventional PDU session establishment procedure. The AMF selects an SMF and informs the SMF to establish or modify a PDU session for the UE. The SMF retrieves the PCC rules for the PDU session from the PCF, including an SDF template. The SDF template is either an application identifier (appId) or a list of service data flow filters.

[0107] In step 10a, the SMF sends an N4 Session Establishment / Modification Request with stream information #1 and "PDU set aggregated packet processing information" to the UPF. The stream information #1 can be at least one of 5QI, SST or S-NSSAI, DNN, appId, pfdId, for example, 5QI, SST or S-NSSAI, (SST or S-NSSAI and DNN), appId, (AppId and pfdId). As mentioned above, some examples of stream information apply to all UEs, while some other examples of stream information apply to a specific UE or PDU session. However, when the SMF provides stream information in the PDU session establishment procedure, the provided stream information is for a specific UE or PDU session. The stream information #1 is used by the UPF to identify XR traffic by stream indicator. Using stream information #1 and the "PDU set aggregation packet processing information" (including "PDU set aggregation packet processing instructions" associated with each stream indicator included in stream information #1), the UPF can process each stream indicated by the stream indicator included in stream information #1 in accordance with the PDU set aggregation packet processing instructions associated with the stream indicator indicating that stream.

[0108] Specifically, the stream information #1 and the "PDU set aggregation packet processing information" can be included in a forwarding action rule (FAR) associated with the packet detection rule (PDR). Alternatively, the SMF can provide only the stream information (e.g., appId) in the PDR to the UPF, and the UPF can obtain the "PDU set aggregation packet processing information" associated with the appId previously provided by the SMF based on the N4 PFD management procedure. In this way, the SMF does not need to provide the "PDU set aggregation packet processing information" to the UPF in the N4 Session Establishment / Modification Request message.

[0109] Instead, the AF provides the appId-to-PFD mapping to the SMF via the NEF (e.g., the PFDF in the NEF). The SMF then provides the appId-to-PFD mapping to the UPF by the N4 PFD management procedure. Then, during the PDU session establishment or modification procedure, the PCF may provide only the appId to the SMF in the PCC rule. Also, the SMF provides only the appId to the UPF, and the UPF can obtain the PFD associated with the appId.

[0110] In step 10b, the UPF responds to the SMF with an N4 Session Establishment / Modification Response message.

[0111] In step 11, the SMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF, including the PDU session ID and N2 SM information of the RAN node. The N2 SM information includes the stream information #2 and the "PDU set aggregation packet processing information" (including the "PDU set aggregation packet processing indication" associated with each stream indicator included in the stream information #2). For example, the N2 SM information includes the QFI, the QoS profile, the CN tunnel information, and / or the S-NSSAI from the allowed NSSAI, and the "PDU set aggregation packet processing information". For example, the "PDU set aggregation packet processing information" may apply to the entire PDU session or to a specific QoS flow. That is, the "PDU set aggregation packet processing information" may be associated with a specific QFI, or with all QFIs, or with a specific QFI and stream ID (or frame type, or importance value). Optionally, the SMF may provide the UE's "discard timer" and "discard type" in the N1 SM information included in the message, for example the N1 SM information includes a PDU session establishment acknowledgement with a "discard timer" and a "discard type". The "discard timer" and "discard type" may be associated with a PDU session ID or may be associated with a QFI.

[0112] In step 12, the AMF sends an N2 PDU Session Request message with N2 SM information to the RAN node. Specifically, the N2 SM information corresponds to the PDU Session Resource Setup Request Transfer IE defined in TS 38.413. That is, the PDU Session Resource Setup Request Transfer IE includes stream information #2 and "PDU set aggregation packet processing information".

[0113] Steps 13 to 21 of the conventional PDU session establishment procedure are then executed.

[0114] Also, the SMF may be informed in advance whether the UPF has the capability to perform special user plane processing, for example, during the N4 association procedure, the UPF informs the SMF of the capability of special user plane processing. Alternatively, the SMF may be pre-configured with the capabilities of the UPF by OAM. The special user plane processing includes adding an extended GTP-U header with PDU set related information, PDU set aggregation packet processing, differentiated QoS processing, etc. As long as the SMF identifies that the PDU session carries XR traffic, the SMF needs to select a UPF with the special user plane processing capability or functionality for the PDU session.

[0115] According to a second sub-embodiment of the first embodiment, the SMF provides "stream information" and "PDU set aggregation packet processing information" in a modified PDU session modification procedure.

[0116] FIG. 2 shows a modified PDU session modification procedure according to a second sub-embodiment of the first embodiment.

[0117] The conventional PDU session modification procedure is described in 4.3.3.2 in TS 23.502. According to the second sub-embodiment of the first embodiment, steps 3, 4, 5, and 6 are modified, but the other steps are unchanged.

[0118] Step 0: The XR application in the UE requests connectivity.

[0119] Step 1, a PDU session establishment procedure is performed, thereby establishing a default QoS flow for the PDU session.

[0120] Step 2: The XR application of the UE exchanges data with the application server through the established PDU session. The UE may provide a decoding function, for example, to perform partial recovery of the PDU set. The application server determines whether partial recovery of the PDU set is possible in the UE based on the UE's decoding capability and other information, such as encoding scheme, frame type, or importance. The application server constructs 5GS "user plane processing auxiliary information", which includes "PDU set integration packet processing information" and / or "delivery information".

[0121] Step 3: The AF provides the 5GC (e.g., PCF, or PCF and NEF) with the stream information and the associated "PDU set aggregation packet handling information", where the stream information for a particular UE or PDU session may include a UE address or (UE address and flow description). That is, the "PDU set aggregation packet handling information" can be applied to the entire PDU session identified by the UE address. Alternatively, the "PDU set aggregation packet handling information" can be applied to a specific flow or stream of a PDU session identified by (UE address and flow description). For example, the AF triggers the setup of an AF session with the required QoS and the "PDU set aggregation packet handling information" based on TS 23.502 4.15.6.6. Alternatively, the AF provides the "PDU set aggregation packet handling information" to the 5GC (e.g., PCF) based on the procedure in TS 23.502 4.3.6.4 (forwarding AF requests targeted to individual UE addresses to the associated PCF).

[0122] Step 4: The PCF executes a PCF-initiated SM policy-related modification procedure to provide the SMF with PCC rules including SDF templates (e.g., service data flow filters) and corresponding "PDU set aggregation packet processing information". For example, the PCF provides the UE ID (e.g., SUPI), PDU Session ID, and service data flow filters together with the "PDU set aggregation packet processing information". Then, the SMF knows that the "PDU set aggregation packet processing information" applies to the service data flows of the UE's PDU sessions. Here, at least one of the PDU Session ID and the service data flow filter can be regarded as stream information.

[0123] Step 5, the SMF sends an N4 Session Modification request to the UPF, which includes the N2 SM information with stream information #1 and “PDU set aggregated packet processing information”. The description is the same as step 10a in Figure 1. The stream information #1 can be at least one of a packet filter set (or a service data flow filter or flow description) and a QFI.

[0124] Step 6, the SMF sends RAN node N2 SM information including Stream Info #2 and "PDU Set Aggregation Packet Processing Information" via AMF as steps 11 and 12 in Figure 4. The only difference between step 6 in Figure 2 and step 12 in Figure 1 is that the message including N2 SM information is different. Stream Info #2 can be QFI or (QFI and Stream ID), and Stream ID can be replaced by frame type or importance value.

[0125] The other steps are the same as the PDU session modification procedure defined in TS 23.502, 4.3.3.2.1.

[0126] A third sub-embodiment of the first embodiment relates to a UE handover from a source gNB to a target gNB.

[0127] The source gNB needs to provide the target gNB with "PDU set aggregation packet processing information" associated with Stream Info #2 in order to enable the target gNB to know whether a dropping of a PDU set should be performed if the PDU set is received or delivered incompletely and whether to drop the PDU set if the dependent reference PDU set is already incomplete. For example, the "PDU set aggregation packet processing information" associated with the stream information (Stream Info #2) may be included in the PDU Session Resources To Be Setup List IE of the Handover Request message over the Xn interface.

[0128] For the same reason, the gNB-CU must provide the gNB-DU with "PDU set aggregation packet processing information" associated with stream information #2. For example, the "PDU set aggregation packet processing information" associated with stream information #2 may be included in the DRB to Be Setup List IE of the UE CONTEXT SETUP / MODIFICATION REQUEST message via the F1 interface.

[0129] According to a second embodiment, an application provides PDU set aggregation packet processing instructions for each PDU set.

[0130] According to the second embodiment, whether PDU set aggregation packet processing should be performed dynamically depends on a specific PDU set. For example, an indication of PDU set aggregation packet processing should be added to the PDU set related information piggybacked in each PDU. For each PDU set, the UPF or RAN node decides whether to drop the whole PDU set if it is incomplete based on the indication of PDU set aggregation packet processing. For example, if the indication of PDU set aggregation packet processing is true for PDU set #1, PDU set #1 is discarded if it is incomplete. If the indication of PDU set aggregation packet processing is false for PDU set #2, PDU set #2 is not discarded even if it is incomplete. Parameters for determining how to discard or drop a PDU set (e.g., at least one of "dependency discard indication", "discard timer", and "discard type") may be preconfigured in the UPF.

[0131] According to the third embodiment, the control plane solution (eg according to the first embodiment) and the user plane solution (eg according to the second embodiment) are combined.

[0132] For example, 1) the SMF configures the UPF and / or RAN node with the "PDU set aggregation packet processing information" excluding the "PDU set aggregation packet processing instruction", 2) the "PDU set aggregation packet processing instruction" is included in the PDU set related information piggybacked in each PDU. The UPF first checks whether the "PDU set aggregation packet processing instruction" is true or false for each PDU. If it is true, the UPF decides how to process the PDU set according to the "PDU set aggregation packet processing information" excluding the "PDU set aggregation packet processing instruction" (e.g., at least one of "dependency discard instruction", "discard timer", and "discard type") provided by the SMF.

[0133] According to the fourth embodiment, the UPF provides a downstream node (eg, an I-UPF or a RAN node) with discarded PDU set information in the user plane.

[0134] After the SMF configures the UPF with the "PDU set consolidation packet processing information", the UPF performs special user plane processing. When the UPF delivers some of the PDUs of the incomplete PDU set to the downstream node, if the UPF determines that the PDU set is incomplete (i.e., some PDUs of the PDU set cannot be successfully received), the UPF may provide discard PDU set information to the downstream node (i.e., the incomplete PDU set is discarded or the undelivered PDUs of the incomplete PDU set are not delivered). Upon receiving the discard PDU set information, the downstream node stops transmitting the remaining PDUs of the PDU set identified by the discard PDU set information.

[0135] Fig. 3 shows an example of the fourth embodiment. PDU set #1 consists of 8 PDUs, PDUs #1-3 have already been delivered to downstream nodes, e.g. I-UPF or RAN nodes. Furthermore, the RAN node has sent PDU #1 to the UE. The UPF determines that PDU set #1 is incomplete, e.g. PDU #4 has not been received after the "discard timer" expires. The UPF decides to drop the remaining PDUs of the PDU set and also informs the downstream node (I-UPF or RAN node) of the "discard PDU set information" (i.e. the remaining PDUs of PDU set #1 are dropped by UPF and are not delivered to downstream nodes). When the "Discard PDU Set Information" is received by the downstream node, if the downstream node has not transmitted all PDUs of the received PDU set #1 to a further downstream node (e.g., a RAN node or a UE), the downstream node must discard PDU #2 and PDU #3 that have not been transmitted to the further downstream node, thereby avoiding the waste of radio resources for delivering PDU #2 and PDU #3 to the further downstream node.

[0136] The discard PDU set information provided by the UPF should include the discard PDU set SN (e.g., PDU set #1) and stream information. The stream information can be at least one of QFI and stream ID (or frame type or importance value). For example, the discard PDU set information includes the QFI and discard PDU set SN of a single stream in one QoS flow case, and includes the QFI, stream ID, and discard PDU set SN of multiple streams in one QoS flow case.

[0137] As an example, a discard PDU set information IE is added to the DL PDU SESSION INFORMATION (PDU type 0) of the PDU session container defined in TS 38.415. Since the DL PDU INFORMATION (PDU type 0) already has a QoS flow identifier, the discard PDU set SN and (optionally) the stream ID can be provided in the discard PDU set information.

[0138] Another example is based on the assumption that a new container (e.g., an application-aware container, or a PDU set-aware container) is defined for XR traffic and inserted into the extended GTP-U header of the N3 / N9 interface, and a discard PDU set information IE can be added to the new container.

[0139] 4 is a schematic flow chart diagram illustrating an embodiment of a method 400 according to the present application. In some embodiments, the method 400 is performed by a network function such as an SMF or a network function equipped with an SMF. In certain embodiments, the method 400 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0140] The method 400 comprises constructing (410) stream information and PDU set aggregation packet processing information for a particular UE or PDU session, where the stream information includes at least one stream indicator indicating a stream each associated with XR traffic, and the PDU set aggregation packet processing information includes an instruction for PDU set aggregation packet processing associated with each stream indicator, and transmitting (420) the constructed stream information and PDU set aggregation packet processing information to a UPF or RAN node via a transceiver.

[0141] In some embodiments, the stream information and associated PDU set aggregate packet processing information are constructed based on a pre-configuration, and the stream information includes at least one of a 5QI, an SST or an S-NSSAI, a DNN, and an appId.

[0142] In some embodiments, the stream information and associated PDU set integrated packet processing information are constructed based on PCC rules provided by the PCF, and the stream information includes at least one of a QFI, a stream ID, a frame type, an importance value, and a service data flow filter.

[0143] In some embodiments, if the PDU set consolidation packet processing indication is true, the associated PDU set consolidation packet processing information further includes at least one of a dependency discard indication, a discard timer, and a discard type.

[0144] In one embodiment, the constructed stream information, including at least one of a QFI, an appId, a service data flow filter, a frame type, and an importance value, and the associated PDU set aggregate packet processing information are sent to the UPF.

[0145] In another embodiment, the constructed stream information, including at least one of a QFI, a stream ID, a frame type, and an importance value, and the associated PDU set aggregate packet processing information are transmitted to a RAN node.

[0146] 5 is a schematic flow chart diagram illustrating an embodiment of a method 500 according to the present application. In some embodiments, the method 500 is performed by a network node, such as a UPF or a RAN node (e.g., an NG-RAN node). In certain embodiments, the method 500 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0147] The method 500 may comprise a step (510) of receiving stream information and associated PDU set aggregation packet processing information from a session management function (SMF) for a particular UE and PDU session, the stream information including at least one stream indicator each indicating a stream associated with XR traffic, and the PDU set aggregation packet processing information including a PDU set aggregation packet processing instruction associated with each stream indicator, and a step (520) of processing each stream indicated by the at least one stream indicator included in the stream information in accordance with the PDU set aggregation packet processing instruction associated with the stream indicator indicating that stream.

[0148] In some embodiments, the method further comprises providing to a downstream node discarded PDU set information associated with the PDU set if the PDU set is not completely received.

[0149] In some embodiments, the stream information includes at least one of a 5QI, an SST or an S-NSSAI, a DNN, an appId, a QFI, a stream ID, a frame type, an importance value, and a service data flow filter.

[0150] In some embodiments, if the PDU set consolidation packet processing indication is true, the associated PDU set consolidation packet processing information further includes at least one of a dependency discard indication, a discard timer, and a discard type.

[0151] FIG. 6 is a schematic block diagram illustrating an apparatus according to one embodiment.

[0152] A network function or network node or network entity (e.g., SMF or UPF or RAN node) includes a processor, a memory, and a transceiver. The processor implements the functions, processes, and / or methods proposed in FIG. 16 or FIG. 17.

[0153] The SMF comprises a processor and a transceiver coupled to the processor, and the processor is configured to: construct, for a particular UE or PDU session, stream information and PDU set aggregation packet processing information, where the stream information includes at least one stream indicator indicating a stream each associated with XR traffic, and the PDU set aggregation packet processing information includes an instruction for PDU set aggregation packet processing associated with each stream indicator; and transmit, via the transceiver, the constructed stream information and PDU set aggregation packet processing information to a UPF or RAN node.

[0154] In some embodiments, the processor is configured to construct stream information and associated PDU set integrated packet processing information based on pre-configuration, the stream information including at least one of a 5QI, an SST or an S-NSSAI, a DNN, and an appId.

[0155] In some embodiments, the processor is configured to construct stream information and associated PDU set integrated packet processing information based on PCC rules provided by the PCF, the stream information including at least one of a QFI, a stream ID, a frame type, an importance value, and a service data flow filter.

[0156] In some embodiments, if the PDU set consolidation packet processing indication is true, the associated PDU set consolidation packet processing information further includes at least one of a dependency discard indication, a discard timer, and a discard type.

[0157] In one embodiment, the processor is configured to send constructed stream information, including at least one of a QFI, an appId, a service data flow filter, a frame type, and an importance value, and associated PDU set integrated packet processing information to the UPF.

[0158] In another embodiment, the processor is configured to transmit the constructed stream information, including at least one of a QFI, a stream ID, a frame type, and an importance value, and the associated PDU set aggregate packet processing information to the RAN node.

[0159] The UPF or RAN node comprises a processor and a transceiver coupled to the processor, and the processor is configured to receive, via the receiver, from a session management function (SMF) stream information and associated PDU set aggregation packet processing information for a particular UE and PDU session, where the stream information includes at least one stream indicator indicating a stream each associated with XR traffic, and the PDU set aggregation packet processing information includes a PDU set aggregation packet processing instruction associated with each stream indicator, and to process each stream indicated by the at least one stream indicator included in the stream information in accordance with the PDU set aggregation packet processing instruction associated with the stream indicator indicating that stream.

[0160] In some embodiments, the processor is configured to provide discarded PDU set information associated with the PDU set to a downstream node if the PDU set is not completely received.

[0161] In some embodiments, the stream information includes at least one of a 5QI, an SST or an S-NSSAI, a DNN, an appId, a QFI, a stream ID, a frame type, an importance value, and a service data flow filter.

[0162] In some embodiments, if the PDU set consolidation packet processing indication is true, the associated PDU set consolidation packet processing information further includes at least one of a dependency discard indication, a discard timer, and a discard type.

[0163] The layers of the radio interface protocol may be implemented by a processor. The memory is connected to the processor for storing various information for driving the processor. The transceiver is connected to the processor for transmitting and / or receiving messages or information. Needless to say, the transceiver may be implemented as a transmitter for transmitting information and as a receiver for receiving information.

[0164] The memory may be located within or external to the processor and may be connected to the processor by various means well known in the art.

[0165] In the above-described embodiments, the components and features of the embodiments are combined in a predetermined manner. Each component or feature should be considered as optional unless explicitly stated otherwise. Each component or feature may be implemented in a manner that is not associated with other components or features. Furthermore, an embodiment may be constructed by associating several components and / or features. The order of operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment, or may be replaced by corresponding components and features of another embodiment. It is clear that claims not explicitly recited in the claims may be combined to form an embodiment or included in a new claim.

[0166] The embodiments may be implemented by hardware, firmware, software, or a combination thereof. In the case of a hardware implementation, the exemplary embodiments described herein may be implemented by using one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.

[0167] The embodiments may be embodied in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope. [Explanation of symbols]

[0168] 400 ways 500 ways

Claims

1. A processor; a transceiver coupled to the processor; wherein the processor: constructing, for a particular user equipment (UE) or protocol data unit (PDU) session, stream information and PDU set aggregation packet processing information, the stream information including at least one stream indicator indicating a stream associated with Extended Reality (XR) traffic, and the PDU set aggregation packet processing information including an indication of a PDU set aggregation packet processing associated with each stream indicator; transmitting the constructed stream information and PDU set aggregate packet processing information to a User Plane Function (UPF) or a Radio Access Network (RAN) node via the transceiver; A Session Management Function (SMF) in a network architecture that is configured to:

2. 2. The SMF of claim 1, wherein the processor is configured to construct the stream information and the associated PDU set integrated packet processing information based on a pre-configuration, and the stream information includes at least one of a 5G QoS identifier (5QI), a slice / service type (SST) or single network slice selection assistance information (S-NSSAI), a data network name (DNN), and an application identifier (appId).

3. 2. The SMF of claim 1, wherein the processor is configured to construct the stream information and the associated PDU set integrated packet processing information based on a Policy and Charging Control (PCC) rule provided by a Policy Control Function (PCF), and the stream information includes at least one of a QoS Flow ID (QFI), a stream ID, a frame type, an importance value, and a service data flow filter.

4. 2. The SMF of claim 1, wherein if the indication of PDU set consolidation packet processing is true, the associated PDU set consolidation packet processing information further includes at least one of a dependency discard indication, a discard timer, and a discard type.

5. 2. The SMF of claim 1, wherein the processor is configured to send the constructed stream information, including at least one of a QFI, an appId, a service data flow filter, a frame type, and an importance value, and the associated PDU set consolidated packet processing information to the UPF.

6. 2. The SMF of claim 1, wherein the processor is configured to transmit the constructed stream information, including at least one of a QFI, a stream ID, a frame type, and an importance value, and the associated PDU set aggregated packet processing information to the RAN node.

7. A processor; a transceiver coupled to the processor; wherein the processor: receiving, via the receiver, from a Session Management Function (SMF) of the network architecture, stream information and associated PDU set aggregation packet processing information for a particular User Equipment (UE) and Protocol Data Unit (PDU) session, the stream information including at least one stream indicator indicating a respective stream associated with Extended Reality (XR) traffic, the PDU set aggregation packet processing information including an indication of a PDU set aggregation packet processing associated with each stream indicator; processing each stream indicated by at least one stream indicator included in the stream information according to the PDU set aggregation packet processing instruction associated with the stream indicator indicating the stream; A network node of a network architecture, the network node being configured to:

8. 8. The network node of claim 7, wherein the network node is a User Plane Function (UPF) or a Radio Access Network (RAN) node.

9. The network node of claim 7 , wherein the processor is configured to provide discarded PDU set information associated with a PDU set to a downstream node if the PDU set is not completely received.

10. 8. The network node of claim 7, wherein the stream information includes at least one of a 5G QoS Identifier (5QI), a slice / service type (SST) or single network slice selection assistance information (S-NSSAI), a data network name (DNN), an application identifier (appId), a QoS flow ID (QFI), a stream ID, a frame type, an importance value, and a service data flow filter.

11. 8. The network node of claim 7, wherein if the indication of PDU set consolidation packet processing is true, the associated PDU set consolidation packet processing information further includes at least one of a dependency discard indication, a discard timer, and a discard type.

12. constructing stream information and PDU set aggregation packet processing information for a particular user equipment (UE) or protocol data unit (PDU) session, the stream information including at least one stream indicator indicating a stream associated with Extended Reality (XR) traffic, and the PDU set aggregation packet processing information including an indication of a PDU set aggregation packet processing associated with each stream indicator; sending the constructed stream information and the PDU set aggregated packet processing information to a User Plane Function (UPF) or a Radio Access Network (RAN) node; A method performed in a Session Management Function (SMF) of a network architecture comprising:

Images