Method for prioritizing protocol data unit (PDU) set based on importance of PDU set using transmission level tag

Abstract

A method includes obtaining a first packet data unit (PDU) set importance value for a first PDU set within a quality of service (QoS) flow. A first differentiated service code point (DSCP) value is allocated for the first PDU set based on the first PDU set importance value. A header of each transport network packet carrying a PDU in the first set of PDUs is marked with the allocated first DSCP value. Transmission of PDUs in the first set of PDUs is prioritized based on the allocated first DSCP value.

Description

Cross Reference to Related Applications

[0001] This application claims the benefit of priority of GB Application No. 2312300.3 filed on 11 August 2023, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] Various example embodiments relate generally to wireless networks, and more particularly to allocating differentiated services code points (DSCPs) based on protocol data unit (PDU) set importance. BACKGROUND

[0003] To support extended reality (XR) applications, mechanisms for integrated and differentiated protocol data unit (PDU) set handling can be employed. Current mechanisms proposed for handling differentiated PDU sets include marking all PDUs within a quality of service (QoS) flow with a differentiated services code point (DSCP) for all PDU sets. SUMMARY

[0004] In an aspect of the disclosure, a method includes obtaining a first PDU set importance value for a first set of packet data units (PDUs) within a quality of service (QoS) flow. A first differentiated services code point (DSCP) value is allocated for the first set of PDUs based on the first PDU set importance value. A header of each transport network packet carrying a PDU in the first set of PDUs is marked with the allocated first DSCP value, and transmission of the PDUs in the first set of PDUs is prioritized based on the allocated first DSCP value.

[0005] In an aspect of the method, a second set of PDUs within the QoS flow can include a second PDU set importance value.

[0006] In an aspect of the method, the first PDU set importance value can indicate a lower drop eligibility than the second PDU set importance value.

[0007] In an aspect of the method, the method can further include allocating a second DSCP value for the second set of PDUs.

[0008] In an aspect of the method, the first DSCP value can include a lower drop priority for the PDUs than the second DSCP value.

[0009] In an aspect of the method, marking the header of each transport network packet carrying a PDU in the first set of PDUs can include marking an IP header of each transport network packet with the first DSCP value.

[0010] In an aspect of the method, the method can include marking a header of each transport network packet carrying a PDU in the second set of PDUs with the second DSCP value.

[0011] In an aspect of the method, the prioritizing the transmission can include prioritizing transmission of the PDUs in the first set of PDUs over the PDUs in the second set of PDUs at a transport level.

[0012] In an aspect of the method, the transport level includes an N3 transport layer or an N9 transport layer.

[0013] In an aspect of the method, the assigning the first DSCP value can be further based on a forwarding action rule (FAR).

[0014] In an aspect of the method, the marking the header of each transport network packet can be performed by a user plane function (UPF), wherein the FAR can be received from a session management function (SMF).

[0015] In an aspect of the method, the FAR can indicate that the assigning the first DSCP value based on the first set of PDUs importance value is performed based on a UPF-based determination.

[0016] In an aspect of the method, the FAR can indicate that the assigning the first DSCP value based on the first set of PDUs importance value is performed based on a UPF-based determination using an assured forwarding (AF) traffic class.

[0017] In an aspect of the method, the FAR can indicate that the assigning the first DSCP value based on the first set of PDUs importance value is performed based on a UPF-based determination using a mapping between a PDU set importance value and a DSCP value, wherein the PDU set importance value includes the first set of PDUs importance value.

[0018] In an aspect of the method, the mapping can be included in a QoS enforcement rule (QER).

[0019] In an aspect of the method, the obtaining a first set of PDUs importance value in a first set of PDUs within a quality of service (QoS) flow can include determining the first set of PDUs importance value based on a value of a set of PDUs importance header field in the PDUs in the set of PDUs.

[0020] In an aspect of the method, the set of PDUs importance header field in the PDUs in the set of PDUs can be a field in a real-time transport protocol (RTP) header extension.

[0021] In an aspect of the disclosure, an apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform any of the preceding methods.

[0022] In an aspect of the disclosure, a processor-readable medium storing instructions that, when executed by at least one processor of an apparatus, cause the apparatus at least to perform any of the preceding methods.

[0023] According to some aspects, the subject matter of the independent claims is provided. Some further aspects are defined in the dependent claims. BRIEF DESCRIPTION OF DRAWINGS

[0024] Some example embodiments will now be described with reference to the accompanying drawings.

[0025] Figure 1 is a diagram of example embodiments of wireless networking between a network system and a user equipment (UE) according to one illustrated aspect of the present disclosure; Figure 2 is a diagram of example components of a network system according to one illustrated aspect of the present disclosure; Figure 3 is a diagram of example quality of service (QoS) flows including example protocol data unit (PDU) sets according to one illustrated aspect of the present disclosure; Figure 4 is a flow diagram of an example method of marking PDUs in a PDU set according to one illustrated aspect of the present disclosure; Figure 5 is a flow diagram of an example method of marking PDUs in a PDU set according to another illustrated aspect of the present disclosure; and Figure 6 is a diagram of example embodiments of components of a UE or network apparatus according to one illustrated aspect of the present disclosure. DETAILED DESCRIPTION

[0026] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, one skilled in the relevant arts will recognize that aspects can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers are not shown or described in detail to avoid obscuring aspects described herein.

[0027] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrase “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics can be combined in any suitable manner in one or more aspects.

[0028] The embodiments described in this disclosure can be implemented in wireless networking devices such as, but not limited to, devices that utilize Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on Basic Wideband Code Division Multiple Access (W-CDMA), High Speed Packet Access (HSPA), Long Term Evolution (LTE), LTE-Advanced, Enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advanced, 6G (and beyond), and 802.11ax (Wi-Fi 6) and other wireless networking systems. The term “eLTE” herein denotes LTE evolution connected to a 5G core. LTE is also referred to as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0029] The present disclosure can use the term “serving network device” to refer to a network node or network device (or a portion thereof) that serves a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with” (and variations thereof) include communications that can or can not involve communication through one or more intermediary devices or nodes. The term “acquire” (and variations thereof) includes acquiring in a first instance or reacquiring after the first instance. The term “connect” can mean a physical connection or a logical connection.

[0030] The present disclosure uses 5G NR as an example of a wireless network, and can use a smartphone and / or an extended reality headset as an example of a UE. It should be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0031] Figure 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 can include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test devices). The network nodes 120 will be described in more detail below. As used herein, the term “network device” can refer to any component of the network system 100, such as the servers 110, the network nodes 120, the network devices 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network devices include, but are not limited to, devices implementing aspects of 5G NR, and the like. The present disclosure describes embodiments related to 5G NR and embodiments related to aspects defined by the Third Generation Partnership Project (3GPP). However, embodiments related to other wireless networking technologies are contemplated to be within the scope of the present disclosure.

[0032] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as a gNB) may include, for example, nodes that provide NR user plane and control plane protocol termination to the UE and are connected to the 5G core (5GC) via an NG interface, such as, according to Section 3.2 of 3GPP TS 38.300 V 16.6.0 (2021-06), which is incorporated herein by reference.

[0033] gNB supports various protocol layers, such as Layer 1 (L1) - the physical layer, Layer 2 (L2) and Layer 3 (L3).

[0034] NR's Layer 2 (L2) is divided into the following sublayers: Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), among which, for example: The physical layer provides a transmission channel to the MAC sublayer; The MAC sublayer provides logical channels to the RLC sublayer; The RLC sublayer provides RLC channels to the PDCP sublayer; The PDCP sublayer provides radio payload to the SDAP sublayer; The SDAP sublayer provides Quality of Service (QoS) streams to 5GC; The control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0035] Layer 3 (L3) includes, for example, Radio Resource Control (RRC), as per Section 6 of 3GPP TS 38.300 V 16.6.0 (2021-06), which is incorporated herein by reference.

[0036] The gNB Central Unit (gNB-CU) includes, for example, a logical node that hosts, for example, the gNB's Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols, or the en-gNB's RRC and PDCP protocols. This logical node controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, Central Unit, Centralized Unit, or Control Unit.

[0037] A gNB Distributed Unit (gNB-DU) comprises, for example, a logical node hosting a gNB or en-gNB at the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers, and its operation is partially controlled by the gNB-CU. A gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to herein as a DU or Distributed Unit.

[0038] As used herein, the term "network node" can refer to any one or any combination of gNB, gNB-CU, or gNB-DU. RAN (Radio Access Network) nodes or network nodes (such as, for example, gNB, gNB-CU, or gNB-DU or portions thereof) can be implemented using, for example, means having at least one processor and / or at least one memory having processor-readable instructions ("program") configured to support and / or provide and / or process CU and / or DU-related functionalities and / or features and / or at least one protocol (sub)layer (e.g., layer 2 and / or layer 3) of the RAN (Radio Access Network). The separation of different functions between central and distributed units is possible. Examples of such means and components will be described below with reference to Figure 10.

[0039] The gNB-CU and gNB-DU portions can be, for example, co-located or physically separated. The gNB-DU can even be further divided into two parts, for example, one including processing equipment and the other including an antenna. The Central Unit (CU) can also be referred to as a Baseband Unit / Radio Equipment Controller / Cloud RAN / Virtual RAN (BBU / REC / C-RAN / V-RAN), Open RAN (O-RAN), or a portion thereof. The Distributed Unit (DU) can also be referred to as a Remote Radio Head / Remote Radio Unit / Radio Equipment / Radio Unit (RRH / RRU / RE / RU), or a portion thereof. In the various exemplary embodiments of this disclosure below, a network node supporting at least one of the Layer 3 protocols of the Central Unit functionality or radio access network can be, for example, a gNB-CU. Similarly, a network node supporting at least one of the Layer 2 protocols of the Distributed Unit functionality or radio access network can be, for example, a gNB-DU.

[0040] A gNB-CU can support one or more gNB-DUs. A gNB-DU can support one or more cells, and therefore can support serving cells for user equipment (UE) or candidate cells for handover, dual connectivity and / or carrier aggregation and other procedures.

[0041] User equipment (UE) 150 may be or include wireless or mobile devices, devices having a radio interface for interacting with a RAN (Radio Access Network), smartphones, in-vehicle devices, IoT devices, or M2M devices, and other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to enable the device to perform at least certain operations, such as an RRC connection to the RAN. Figure 6 Examples of components describing the UE are provided. In an embodiment, UE 150 may be configured to generate messages (e.g., including a cell ID) to be transmitted via radio toward the RAN (e.g., to reach and communicate with the serving cell). In an embodiment, UE 150 may generate, transmit, and receive RRC messages containing one or more RRC PDUs (Packet Data Units). Those skilled in the art will understand the RRC protocol and other processes that the UE may perform.

[0042] Continue to refer to Figure 1 In an example of a 5G NR network, network system 100 provides one or more cells that define the coverage area of ​​network system 100. As described above, network system 100 may include a gNB of the 5G NR network, or may include any other means configured to control radio communications and manage radio resources within the cell. As used herein, the term "resource" may refer to radio resources such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In embodiments, network node 120 may be referred to as a base station.

[0043] Figure 1 Examples are provided, and are merely illustrative of network system 100 and UE 150. Those skilled in the art will understand that network system 100 includes... Figure 1 Components not shown in the diagram, and it will be understood that other user equipment can communicate with network system 100.

[0044] Figure 2 yes Figure 1 A block diagram of example components of network system 100. A 5G NR network can be described as an example of network system 100, and the aspects described below are intended to apply to other types of network systems as well. The network system can be configured according to... Figure 1The signals and connections shown operate to enable UE 150 to communicate with network system 100 via radio access network 225. Additionally, the network system can be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless otherwise stated, the terms “component,” “function,” and “service” are used interchangeably herein and can refer to instructions executed by and implemented by one or more processors.

[0045] The following describes example functionality of the components. This example functionality is merely illustrative, and it should be understood that additional operations and functions can be performed by the components described herein. Furthermore, connections between components can be virtual connections over service interfaces, allowing any component to communicate with any other component. In this way, any component can act as a service "producer" to provide services for network functionality to any other component acting as a service "consumer."

[0046] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an Authentication Server Function (AUSF) 211, an Access and Mobility Function (AMF) 212, and a Session Management Function (SMF) 213. The core network 210 may also include a Network Slice Selection Function (NSSF) 214, a Network Open Function (NEF) 215, a Network Repository Function (NRF) 216, and a Unified Data Management Function (UDM) 217, which may include a Unified Data Repository (UDR) 224.

[0047] Additional components and functions of the core network 210 may include application functions 218, policy control functions (PCF) 219, network data analysis functions (NWDAF) 220, analytical data repository functions (ADRF) 221, management data analysis functions (MDAF) 222, and operation and management functions (OAM) 223.

[0048] The user plane includes UE 150, Radio Access Network (RAN) 225, User Plane Function (UPF) 226, and Data Network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 describes one or more components, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connectivity for data transmitted through the RAN 225. For example, DN226 identifies services from service providers, Internet access, and third-party services.

[0049] AMF 212 handles connectivity and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses to determine successful authentication. SMF 213 performs Packet Data Unit (PDU) session management and manages session context with UPF 226.

[0050] NSSF 214 can select a Network Slice Instance (NSI) and determine the allowed Network Slice Selection Assistance Information (NSSAI). This selection and determination are used to set up AMF 212 to provide services to UE 150. NEF 215 protects access to network services for third parties to create private network services. NRF 216 acts as a repository for storing network functions to allow function registration and discovery of each other.

[0051] UDM 217 generates authentication vectors for use by AUSF 211 and ADM 212, and provides user identity processing. UDM 217 can connect to UDR 224, which stores data associated with authentication, applications, etc. AF 218 provides application services (e.g., streaming services) to users. PCF 219 provides policy control functionality. For example, PCF 219 can assist in network slicing and mobility management, as well as provide Quality of Service (QoS) and accounting functionality.

[0052] NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analytics and provide insights to functions that leverage that analytics when providing services. ADRF 221 allows consumers to store, retrieve, and remove data and analytics. MDAF 222 provides additional data analytics services for network functions. OAM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0053] Figure 2 These are merely examples of components of a network system, and variations are contemplated within the scope of this disclosure. In embodiments, the network system may include... Figure 2 Other components not shown. In embodiments, the network system may not include... Figure 2 Each component is shown. In embodiments, components and connections can utilize [the following]. Figure 2 The connections shown are implemented using different connections. These and other embodiments are contemplated within the scope of this disclosure.

[0054] Recent advancements in wireless communication technologies, such as 5G NR, can provide high-speed connectivity, high bandwidth, and ultra-reliable, low-latency communication. These advancements enable a wide variety of applications and / or services.

[0055] The terms “service” and “application” are used interchangeably in this document, such that a description referring to one term should be regarded as a description referring to the other term.

[0056] Some services, such as extended reality (XR) applications, video streaming, and cloud-based gaming, may have unique business characteristics that differ from traditional applications. For example, an application-level unit of information (e.g., a video frame or video slice from an encoder) can be carried in a set of protocol data units (PDUs), which can be referred to as a PDU set.

[0057] Another unique business characteristic of these services is that at the application level, one PDU set can have a higher importance level than another. For example, media streaming applications can generate data or information in units of I-frames, B-frames, and P-frames, each of which can correspond to a PDU set. An I-frame is a reference frame (the complete frame itself). A P-frame can carry changes relative to previous frames. A B-frame can carry changes between the current frame and previous frames and / or between the current frame and subsequent frames. Because a P-frame or B-frame may depend on the reference frame (I-frame) used for decoding, the PDU set corresponding to an I-frame may be more important than the PDU set corresponding to a P-frame or B-frame. Furthermore, applications can use layered encoding of data, where certain information units (such as frames) form a basic quality layer for the overall data stream, while other information units provide an enhanced quality layer on top of the basic layer. Enhanced layer information units depend on the basic layer. Therefore, from a network perspective, a PDU set carrying basic layer information units should be treated with higher importance than enhanced layer information units. Given the possibility of different information units (e.g., frames) and layer types, there may also be multiple importance levels for a PDU set. Typically, this type of importance distinction should primarily affect the probability of successful delivery of a PDU set, rather than, for example, delivery delay.

[0058] Therefore, it may be desirable to add service characteristic awareness (e.g., XR awareness) on the transmitter side to enhance capacity. This awareness can be achieved through several service-aided information elements. One of these elements can be PDU set importance (PSI). PSI identifies the relative importance of a PDU set compared to other PDU sets within a Quality of Service (QoS) flow. In other words, different PDU sets within a QoS flow can have different PSIs to influence the probability of successful delivery within the QoS flow.

[0059] In some examples, downlink (DL) PDU set-based QoS processing can be performed as defined in Section 5.37.5.2 of 3GPP TS 23.501 v18.2.2 (2023-07) (“TS 23.501 document”), which is incorporated herein by reference. For example, the PDU Session Anchor (PSA) User Plane Function (UPF) (e.g., at the core network) can identify PDUs belonging to a PDU set and determine PDU set information for each PDU set. PDU set information may include, but is not limited to, a PDU set sequence number, an indication of the last PDU in the corresponding PDU set, PDU sequence numbers within the PDU set, the PDU set size in bytes, and the PSI. In some cases, the PSA UPF can send the PDU set along with the corresponding PDU set information to the appropriate Next Generation Radio Access Network (NG-RAN). For example, the PSA UPF can use the General Packet Radio Service (GPRS) Tunneling Protocol (GTP) to send PDU sets to the NG RAN, and can include PDU set information in the GTP-User Plane (GTP-U) header. Priority levels associated with QoS flows can indicate the priority of scheduling resources among QoS flows and can be used to distinguish QoS flows from the same UE and / or from different UEs, for example, as defined in Section 5.7.3.3 of TS 23.501 document.

[0060] In some examples, the PDU set information can be different for different PDU sets within a QoS flow.

[0061] As described above, mechanisms for processing Differentiated Protocol Data Unit (PDU) sets can be employed to support XR applications. The term "PDU set" can refer to one or more PDUs carrying a payload of a single information unit (e.g., a video frame or video slice used for XR services) generated at the application level. For downlink XR services, PDU set detection can be performed by the UPF, and downlink packets sent from the UPF to the NG-RAN are subsequently marked. Synthesis and differentiation processing can be performed based on QoS parameters applicable to the group of PDUs forming the PDU set.

[0062] The AF can send a request to the NEF / PCF for the NEF / PCF to provide values ​​for the QoS parameters of the PDU set and to provide information indicating the application protocol (e.g., Real-time Transport Protocol (RTP) / Secure RTP (SRTP)), header information (e.g., Frame Mark Header Extension), and payload type (e.g., H.264) used by the service data stream sent to the UPF on the downlink.

[0063] As used herein, the term "QoS flow" can refer to the granularity of QoS that distinguishes service flows within or across a PDU session, a logical connection established within the network for that PDU session. Each QoS flow can be identified by QoS parameters that describe the characteristics of the service flow for that QoS. Mapping packets or service flows to QoS flows is typically based on Layer 2 / 3 / 4 packet headers (Ethernet, IP, TCP / UDP).

[0064] As used herein, communication with the Radio Access Network (RAN) can refer to and mean communication with a portion of the RAN (such as with network nodes (e.g., DU and / or CU)) or another portion of the RAN. As used herein, communication with the core network can refer to and mean communication with one or more services / applications of the core network (such as AMF or another service of the core network).

[0065] To manage QoS, PDU sets can include PDU set importance values, allowing PDUs within a PDU set to be processed based on these values. For example, PDU set importance values ​​can be used in downlink traffic to determine a PDU's eligibility for dropping based on the PDU set to which it belongs and the PDU set importance value of that PDU set.

[0066] Furthermore, PDU set importance values ​​can identify the relative importance of a PDU set compared to other PDU sets within a QoS stream. For example, PDU set importance values ​​can differentiate between different PDU sets based on the type of application / media layer payload / attribute represented in the PDU set (e.g., a PDU set with PDUs carrying video data streams can be assigned a different importance value compared to a PDU set with PDUs carrying F-frames, or a PDU set with PDUs carrying basic quality layer information units can be assigned a different importance value compared to a PDU set with PDUs carrying enhanced quality layer information units).

[0067] Therefore, in order to distinguish PDU sets from one another, PDUs within a PDU set can be tagged with Differentiated Service Code Point (DSCP) values ​​at the transport layer (e.g., an Internet Protocol (IP) network connecting UPF and RAN nodes). Those skilled in the art will understand DSCP. DSCP value tagging can provide priority for tagged PDUs and, in some example embodiments, can be included as an Information Element (IE) in a Forwarding Action Rule (FAR).

[0068] DSCP can be associated with Guaranteed Forwarding (AF) service categories, as those skilled in the art will understand. DSCP allows for differentiated services to be provided based on DSCP values, as provided, for example, by the Internet Engineering Task Force (IETF) Request for Comment (RFC) 2597. Additionally, for example, IETF RFC 7657 describes techniques for using differentiated services for QoS-differentiated AF service categories for real-time services such as RTP streams.

[0069] In some example embodiments, several AF classes can be defined. For example, four AF classes (designated AF1x-AF4x) can be defined. Furthermore, in some embodiments, some AF classes (e.g., higher-numbered classes) can receive higher priority forwarding processing than other AF classes (e.g., lower-numbered classes).

[0070] In some examples, PDU set importance values ​​and DSCP marking for all PDUs in a QoS flow can be performed at the QoS flow level. That is, all PDUs within a QoS flow can include the same DSCP, meaning their drop eligibility / probability is equal within the transport network. However, marking PDUs within a QoS flow using DSCP values ​​based on PDU set importance values ​​can allow different DSCPs to be used to mark PDUs from different PDU sets within the same QoS flow. In this way, the drop eligibility / probability of PDUs for the backhaul network (e.g., N3 / N9 networks) can be affected.

[0071] Therefore, as described herein, for example, a DSCP value can be assigned to each PDU set within a QoS flow based on the PDU set importance value, and the DSCP value can be used to tag the PDUs in the PDU set. The DSCP value can be utilized (e.g., for transmissions over a backhaul network) by prioritizing PDU transmissions based on the DSCP value used to tag the PDUs.

[0072] Figure 3This is a diagram illustrating an example QoS flow including an example PDU set 300 according to one aspect of this disclosure. Any number of PDU sets 300 (e.g., 300a, 300b, ..., 300n) can be provided within a QoS flow. In some example embodiments, each PDU set 300 may include multiple PDUs 310 (e.g., PDU1, PDU2, ..., PDUn). Furthermore, each PDU 310 may include a DSCP value marker 320. In various example embodiments, the DSCP value marker 320 may be included in an Information Element (IE) that is transmitted along with the PDU 310 marked with the DSCP value 320. Those skilled in the art will understand that the DSCP value 320 is included in the IE. The PDU may be carried within an IP transport network packet by means of tunneling, in which case the DSCP IE is included in the transport network header.

[0073] like Figure 3 As shown, for example, PDU set 300a includes PDU 310a. PDU set 300b includes PDU 310b. PDU set 300n includes PDU 310n. Furthermore, based on the PDU set importance value for this PDU set 300, the transport network IP header associated with each PDU 310 is marked using DSCP 320. Marking the transport network header (e.g., IP header) associated with each PDU in the PDU set using DSCP, as used herein, may include: generating each transport network header with an identifier indicating the assigned DSCP value included therein.

[0074] For example, PDU 310a is tagged with DSCP value 320a. PDU 310b is tagged with DSCP value 320b. PDU 310n is tagged with DSCP value 320n. In some example embodiments, DSCP values ​​320a, 320b, and 320n may include different values. Therefore, although PDU 310a and PDU 310n are included in the same QoS stream, the transmission of PDU 310a may be handled differently at the transport level from the transmission of PDU 310n based on the DSCP value 320 for the respective PDU 310.

[0075] For illustrative purposes, in Figure 3 The use of "n" (e.g., 300n) indicates the last entity of the same reference element as element "a" (e.g., 300a). That is, in Figure 3 This is not intended to indicate the set number of PDU sets, for example, between PDU set 300b and PDU set 300n.

[0076] Now for reference Figure 4 and5 This will describe the flowcharts for various operations. As follows, Figure 2 The UPF 226 described in [the document] can be executed. Figure 4 and Figure 5 The operations described herein. In some example embodiments, the UPF 226 may receive information from other components (such as the SMF 213), as described below. The UPF and SMF are merely examples, and it is conceivable that... Figure 4 and / or Figure 5 One or more operations can be performed by one or more other components, such as by Figure 2 The core network shown is executed by one or more other components.

[0077] Figure 4 This is a flowchart of an example method 400 for tagging PDUs in a PDU set according to aspects shown in this disclosure. In some example embodiments, PDU tagging includes tagging PDUs using a DSCP assigned to the PDU set. In block 410, the PDU sets within a QoS flow and their importance (e.g., PDU set importance value (PSI value)) are obtained. For example, as described above, each PDU set within a QoS flow includes a PDU set importance value that identifies the discard eligibility / probability for PDUs belonging to that PDU set. (Refer again) Figure 3 In various example embodiments, PDU set 300a may receive a first PDU set value, while PDU set 300b may receive a second PDU set value. In some examples, the first PDU set value may include a value indicating a higher importance level compared to the second PDU set value, such that PDUs belonging to PDU set 300a are more important than PDUs belonging to PDU set 300b, and therefore PDUs belonging to PDU set 300b may receive a higher discard eligibility / probability compared to PDUs belonging to PDU set 300a. That is, generally, a higher importance level may be associated with a lower discard eligibility, and a lower importance level may be associated with a higher discard eligibility.

[0078] Therefore, in box 420, a transport network (e.g., IP network) DSCP value is assigned to each PDU set based on the PDU set importance value for that PDU set. For example, if PDU set 300a includes a higher PDU set importance value than PDU set 300b, the higher DSCP value, as described above, can be assigned to PDU set 300a instead of PDU set 300b. In this example, the AF drop priority for PDUs belonging to PDU set 300b can include a higher probability of being dropped compared to PDUs belonging to PDU set 300a, even if both PDU sets 300a and 300b are included in the same QoS flow.

[0079] In various example embodiments, the determination of the importance value of the PDU set can be based on (e.g., as determined by...) Figure 2 The DSCP value for a PDU set is assigned according to the UPF 226 described in the document, where a mapping from the importance value of the PDU set to the DSCP value is applied to assign the DSCP value (e.g., AF41, AF42, AF43). In various example embodiments, the forwarding action rule (FAR) may instruct: based on, for example... Figure 2 The importance of the PDU set as determined by UPF 226 is used to perform DSCP tagging.

[0080] In other example embodiments, DSCP values ​​can be predefined as AF classes (e.g., AF4x). The discard priority for PDUs in that PDU set can then be set based on the PDU set importance value (e.g., AF41, AF42, AF43), where AF41 can indicate PDUs with higher importance than AF42, and so on. In this example, FAR can indicate that the DSCP should be assigned to the aforementioned AF class, while... Figure 2 The UPF 226 described herein applies mappings within AF classes (e.g., AF41, AF42, AF43) based on the PDU set importance value of the PDU set.

[0081] Once a DSCP value has been assigned to a set of PDUs, in box 430, the IP transport network header associated with each set of PDUs is marked with the DSCP value, which is assigned for the PDU set to which the PDU belongs. For example, PDU 310a of PDU set 300a may be marked with a first DSCP value, and PDU 310b may be marked with a second DSCP value. The first DSCP value may indicate a higher priority for PDU 310a than the priority indicated by the second DSCP value for PDU 310b of PDU set 310a. However, this is provided for illustrative purposes only, and in some examples, the second DSCP value may indicate a higher priority for PDU 310b than the priority indicated by the first DSCP value for PDU 310a.

[0082] In box 440, the transmission of a PDU can be prioritized based on the DSCP value for the PDU set to which the PDU belongs. For example, as described above, if the first DSCP value indicates a higher priority for PDU 310a than the priority indicated by the second DSCP value for PDU 310b in PDU set 310b, PDU 310a can receive a higher transmission priority than PDU 310b (e.g., at the transport layer). Furthermore, the drop priority for PDU 310a can be lower than the drop priority for PDU 310b. Therefore, PDU 310b may experience a higher probability of being dropped during transmission than PDU 310a.

[0083] Figure 4 The operations described are merely illustrative, and variations are contemplated within the scope of this disclosure. In embodiments, the operations may include... Figure 4 Other boxes not shown in the diagram. In embodiments, the operation may not include... Figure 4 Each box is shown. In an embodiment, the operation can be in conjunction with... Figure 4 The different sequences shown are implemented. These and other embodiments are contemplated within the scope of this disclosure. Those skilled in the art will understand that although the various example components are described as performing various functions, other components may perform the functions described in method 400.

[0084] In another example embodiment, the importance value of a PDU set can be set based on predefined knowledge of the importance of the PDU set. For example, the importance of the PDU set can be provided by application function 218. Figure 5 This is a flowchart of an example method 500 for marking PDUs in a PDU set according to another aspect shown in this disclosure. Specifically, example method 500 may include deriving a DSCP tag from the importance of the PDU set, which has already been specified in the PDU set, for example, in a header field carried in the PDU set, such as a header field in a Real-Time Transport Protocol (RTP) header extension.

[0085] In various example embodiments, SMF 213 can derive a transport DSCP tag from the PDU set importance value for a given PDU set, communicate it to UPF 226, and UPF 226 accordingly tags the DSCP in downlink packets (e.g., N3 / N9 interfaces). For example, SMF 213 can configure the necessary information based on the UE's (e.g., UE 150) subscription information, for a given Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), application, local policy, or policy provided by PCF 219.

[0086] In various other example embodiments, application function 218 may provide the 5GS (NEF / PCF) with a list of importance values ​​used by the application. Upon receiving this information as part of a PCC rule, SMF 213 may use the PDU set importance values ​​to derive the DSCP and provide UPF 226 with a mapping from application importance values ​​to DSCP. SMF 213 may instruct UPF 226 to utilize PDU set importance values ​​directly from protocol-specific headers (e.g., the SA4 RTP PDU set header extended importance field).

[0087] In box 510, a transport network (e.g., IP network) DSCP value is assigned to a PDU set based on the PDU set importance value specified for each PDU set. Similar to method 400 above, for example, if PDU set 300a includes a higher PDU set importance value than PDU set 300b, a DSCP with the higher value as described above can be assigned to PDU set 300a instead of PDU set 300b. In this example, the AF drop priority for PDUs belonging to PDU set 300b can include a higher probability of being dropped compared to PDUs belonging to PDU set 300a, even if both PDU sets 300a and 300b are included in the same QoS flow.

[0088] In various example embodiments, FAR can indicate: based on, for example Figure 2 The importance of the PDU set determined by UPF 226 described herein is used to perform DSCP tagging. In various other example embodiments, QoS Enforcement Rules (QERs) may provide specific mapping rules. For example, importance values ​​0-5 may be mapped to AF43, importance values ​​6-11 may be mapped to AF42, and / or importance values ​​12-15 may be mapped to AF41. These rules are merely exemplary, and those skilled in the art will understand that variations of these mappings may be utilized.

[0089] For example, where SMF 213 provides rules, awareness, or control over the allocation of importance values ​​through UPF 226, UPF 226 can utilize the importance values ​​set by the application (e.g., in RTP PDU set header extensions). In various other example embodiments, QER can instruct UPF 226 to perform importance determination based on the importance header according to the protocol description. This can be applied, for example, to protocol descriptions such as RTP / SRTP+RTP PDU set header extensions (or any protocol / header with explicit importance values).

[0090] In various other example embodiments, application function 218 may provide a list of importance values ​​used by the application. Upon receiving this information as part of a PCC rule, SMF 213 may use it to provide UPF 226 with a mapping from application importance values ​​to DSCPs. As described above, SMF 213 may configure necessary information based on the UE's (e.g., UE 150) subscription information for a given DNN, S-NSSAI, application, local policy, or policy provided by the PCF for a given application.

[0091] Once a DSCP value is assigned for a PDU set, in box 520, the IP transport network header associated with each PDU set is marked with the DSCP value assigned for the PDU set to which the PDU belongs. For example, similar to method 400, PDU 310a of PDU set 300a may be marked with a first DSCP value, while PDU 310b may be marked with a second DSCP value. The first DSCP value may indicate a higher priority for PDU 310a than the priority indicated by the second DSCP value for PDU 310b of PDU set 310b. However, the above is provided for illustrative purposes only, and in some examples, the second DSCP value may indicate a higher priority for PDU 310b than the priority indicated by the first DSCP value for PDU 310a.

[0092] In box 530, the transmission of a PDU can be prioritized based on the DSCP value for the PDU set to which the PDU belongs. For example, as described above, if the first DSCP value indicates a higher priority for PDU 310a than the priority indicated by the second DSCP value for PDU 310b in PDU set 310b, PDU 310a can receive a higher transmission priority than PDU 310b (e.g., at the transport layer). Furthermore, the drop priority for PDU 310a can be lower than the drop priority for PDU 310b. Therefore, PDU 310b may experience a higher probability of being dropped during transmission than PDU 310a.

[0093] Figure 5 The operations described are merely illustrative, and variations are contemplated within the scope of this disclosure. In embodiments, the operations may include... Figure 5 Other boxes not shown in the diagram. In embodiments, the operation may not include... Figure 5 Each box is shown. In an embodiment, the operation can be in conjunction with... Figure 5The different sequences shown are used to implement the same functionality. These and other embodiments are contemplated within the scope of this disclosure. Those skilled in the art will understand that although the various example components are described as performing various functions, other components may perform the functions described in method 500.

[0094] Therefore, using methods 400 and / or 500, transport level marking can operate as a function of PDU set importance within a QoS flow, and is performed based on PDU sets within the QoS flow. Different importance values ​​can be extended to backhaul transport levels with different guaranteed forwarding (AF) drop priorities (e.g., N3 / N9). Furthermore, different PDU sets can be assigned different DSCP tag values, and are thus prioritized differently within the transport level based on PDU set importance. Appropriate processing for a given application PDU belonging to a PDU set can be performed dynamically, rather than based on a static configuration that may not be suitable for all applications (e.g., in UPF). Individual PDUs can be mapped to separate QoS flows or the same QoS flow.

[0095] Now refer to Figure 6 This diagram illustrates a block diagram of example components of a UE or (e.g., RAN or core network) network device. The device includes electronic memory 610, a processor 620, a network interface 640, and memory 650. The various components can be communicatively coupled to each other. The processor 620 can be and may include any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a system-on-a-chip (SoC), or any other type of processor. The memory 650 can be a volatile type of memory, such as RAM, or a non-volatile type of memory, such as NAND flash memory. The memory 650 includes processor-readable instructions that can be executed by the processor 620 to cause the device to perform various operations, including those mentioned herein, such as... Figure 4 to Figure 5 The operation.

[0096] Electronic storage device 610 can be and includes any type of electronic storage device for storing data, such as hard disk drives, solid-state drives, optical disks and / or other non-transitory computer-readable media, as well as other types of electronic storage devices. Electronic storage device 1010 stores processor-readable instructions for causing or being configured to perform its operations and also stores data associated with such operations (such as data related to the 5G NR standard and other data). Network interface 640 can implement wireless networking technologies, such as 5G NR and / or other wireless networking technologies.

[0097] Figure 6The components shown are merely examples, and those skilled in the art will understand that the apparatus includes other components not shown, and may include multiples of any of the components shown. These and other embodiments are contemplated within the scope of this disclosure.

[0098] Other embodiments of this disclosure include the following examples.

[0099] Example 1.1. An apparatus comprising: A component used to obtain the importance value of the first set of Packet Data Units (PDUs) within the first set of Quality of Service (QoS) data units; A component for assigning a first Differentiated Service Code Point (DSCP) value to a first PDU set based on the importance value of the first PDU set; A component for marking the header of each transport network packet carrying PDUs in the first PDU set using the assigned first DSCP value; and A component used to prioritize the transmission of PDUs in the first PDU set based on the assigned first DSCP value.

[0100] Example 1.2. The apparatus according to Example 1.1, wherein the second PDU set within the QoS flow includes a second PDU set importance value.

[0101] Example 1.3. The apparatus according to Example 1.2, wherein the importance value of the first PDU set indicates a discard qualification that is lower than the importance value of the second PDU set.

[0102] Example 1.4. The apparatus according to Examples 1.2 to 1.3 further includes: a component for assigning a second DSCP value to a second PDU set.

[0103] Example 1.5. The apparatus according to Example 1.4, wherein the first DSCP value includes a lower drop priority for the PDU than the second DSCP value.

[0104] Example 1.6. The apparatus according to Examples 1.4-1.5, wherein the header of each transport network packet carrying PDUs in the first PDU set includes: marking the IP header of each transport network packet with a first DSCP value.

[0105] Example 1.7. The apparatus according to Examples 1.4-1.6 further includes: a component for marking the header of each transport network packet carrying PDUs in the second PDU set using a second DSCP value.

[0106] Example 1.8. The apparatus according to Examples 1.4-1.7, wherein priority transmission includes: prioritizing the transmission of PDUs in a first PDU set over PDUs in a second PDU set at the transmission level.

[0107] Example 1.9. The apparatus according to Example 1.8, wherein the transmission level includes an N3 transmission layer or an N9 transmission layer.

[0108] Example 1.10. The apparatus according to any of the foregoing examples, wherein the assignment of the first DSCP value is based on the Forwarding Action Rule (FAR).

[0109] Example 1.11. The apparatus according to Example 1.10, wherein the header marking of each transport network packet is performed by the User Plane Function (UPF), and wherein the FAR is received from the Session Management Function (SMF).

[0110] Example 1.12. The apparatus according to Example 1.11, wherein the FAR instruction to assign a first DSCP value based on a first PDU set importance value is performed based on the determination of UPF.

[0111] Example 1.13. The apparatus according to Example 1.12, wherein the FAR indicates: the allocation of a first DSCP value based on the importance value of a first PDU set shall be performed using the guaranteed forwarding (AF) service class determined based on the UPF.

[0112] Example 1.14. According to the apparatus described in Example 1.11, the allocation of a first DSCP value based on a first PDU set importance value is performed using a mapping between the PDU set importance value and the DSCP value based on the determination of the UPF, wherein the PDU set importance value includes the first PDU set importance value.

[0113] Example 1.15. The apparatus according to Example 1.14, wherein the mapping is included in the QoS Enforcement Rule (QER).

[0114] Example 1.16. According to the apparatus described in Examples 1.1-1.15, obtaining a first PDU set importance value in a first PDU set within a Quality of Service (QoS) flow includes: a component for determining the PDU set importance value based on the value of the PDU set importance header field in the PDU set.

[0115] Example 1.17. The apparatus according to Example 1.16, wherein the PDU set importance header field in the PDU set is a field in the Real-Time Transport Protocol (RTP) header extension.

[0116] The embodiments and aspects disclosed herein are examples of this disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. The specific structural and functional details disclosed herein should not be construed as limiting, but rather serve as the basis for the claims and as a representative basis for teaching those skilled in the art to adopt this disclosure broadly in virtually any suitable detailed structure. Throughout the description of the accompanying drawings, the same reference numerals may refer to similar or identical elements.

[0117] The phrases “in one aspect,” “in all aspects,” “in all dimensions,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects under this disclosure. The phrase “multiple” may refer to two or more.

[0118] The phrases “in one embodiment,” “in an embodiment,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments according to this disclosure. A phrase of the form “A or B” means “(A), (B), or (A and B)”, and a phrase of the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C)”. Any method, program, algorithm, or code described herein can be translated into or expressed in a programming language or computer program. As used herein, the terms "programming language" and "computer program" each include any language used to specify instructions to a computer, and include (but are not limited to) the following languages ​​and their derivatives: assembler, Basic, batch file, BCPL, C, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, meta-languages ​​used to specify the program itself, and all first-, second-, third-, fourth-, fifth-, or other generative computer languages. Databases and other data schemas, and any other meta-languages, are also included. No distinction is made between interpreted languages, compiled languages, or languages ​​that use both compilation and interpretation. No distinction is made between compiled versions and source code versions of a program. Therefore, when referring to a program, where a programming language may exist in multiple states (e.g., source code, compiled, object code, or linked), the reference refers to any and all such states. References to procedures may cover the actual instructions and / or the intent of those instructions.

[0119] While various aspects of this disclosure have been shown in the accompanying drawings, it is not intended to limit the disclosure thereto, as the disclosure is intended to have the broadest possible scope permitted by the art, and the specification should be understood in the same manner. Therefore, the foregoing description should not be construed as limiting, but merely as examples of particular aspects. Other modifications falling within the scope and spirit of the appended claims will be contemplated by those skilled in the art.

Claims

1. A method comprising: obtaining a first packet data unit (PDU) set importance value for a first set of PDUs within a quality of service (QoS) flow; allocating a first differentiated services code point (DSCP) value for the first set of PDUs based on the first PDU set importance value; marking a header of each transport network packet carrying a PDU in the first set of PDUs with the allocated first DSCP value; and prioritizing transmission of PDUs in the first set of PDUs based on the allocated first DSCP value.

2. The method of claim 1, wherein a second set of PDUs within the QoS flow comprises a second PDU set importance value.

3. The method of claim 2, wherein the first PDU set importance value indicates a lower drop eligibility than the second PDU set importance value.

4. The method of claim 2 or 3, further comprising allocating a second DSCP value for the second set of PDUs.

5. The method of claim 4, wherein the first DSCP value comprises a lower drop priority for PDUs than the second DSCP value. marking an IP header of the each transport network packet with the first DSCP value.

6. The method of claim 4 or 5, wherein marking the header of each transport network packet carrying a PDU of the first set of PDUs comprises: marking a header of each transport network packet carrying a PDU in the second set of PDUs with the second DSCP value.

7. The method of any of claims 4-6, further comprising: prioritizing transmission of PDUs in the first set of PDUs over PDUs in the second set of PDUs at a transport level.

8. The method of any of claims 4-7, wherein prioritizing the transmissions comprises:

9. The method of claim 8, wherein the transport level comprises an N3 or N9 transport layer.

10. The method of any preceding claim, wherein allocating the first DSCP value is based on a forwarding action rule (FAR).

11. The method of claim 10, wherein marking the header of each transport network packet is performed by a user plane function (UPF), and wherein the FAR is received from a session management function (SMF).

12. The method of claim 11, wherein the FAR indicates that allocating the first DSCP value based on the first PDU set importance value is performed based on a determination by the UPF.

13. The method of claim 12, wherein the FAR indicates that allocating the first DSCP value based on the first PDU set importance value is to be performed using an assured forwarding (AF) traffic class based on a determination by the UPF.

14. The method of claim 11, wherein the FAR indicates that allocating the first DSCP value based on the first PDU set importance value is to be performed using a mapping between PDU set importance and DSCP value based on a determination by the UPF.

15. The method of claim 14, wherein the mapping is contained in a QoS enforcement rule (QER). determining the first PDU set importance value based on a value of a PDU set importance header field of a PDU in the PDU set.

16. The method of any of claims 1 to 15, wherein obtaining a first PDU set significance value for the first PDU set within a quality of service (QoS) flow comprises: ​ 17. The method of claim 16, wherein the PDU set significance header field in a PDU set is a field in a Real-time Transport Protocol (RTP) header extension.

18. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform the method of any of claims 1 to 17.

19. A processor-readable medium storing instructions that, when executed by at least one processor of an apparatus, cause the apparatus at least to perform the method of any of claims 1 to 17.

Images