Quality of service for augmented reality media over wireless communication network

Abstract

A method in a user equipment of a wireless communication network is provided. The method includes transmitting a protocol data unit (PDU) of a first set of PDUs using a first quality of service (QoS) mapping rule via a first data radio bearer. The method further comprises receiving a downlink packet for the data radio bearer, the downlink packet comprising header information, the header information comprising at least one QoS parameter indicating a second QoS mapping rule; applying a first QoS mapping rule to an uplink transmission on the data radio bearer until a transmission of a last PDU in the first set of PDUs; and transmitting the PDUs in the second PDU set by using the second QoS mapping rule.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to the field of applying quality of service requirements to extended reality media carried over a wireless communication network.This document defines a method in a user equipment of a wireless communication network and a user equipment of a wireless communication network. Background Art

[0002] In this article, Extended Reality (XR) is used as a general term for different types of reality (of which Virtual Reality, Augmented Reality, and Mixed Reality are examples). XR application services are subject to strict bandwidth and latency constraints in order to deliver appropriate quality of service and quality of experience to the end users of XR services. Bandwidth and latency constraints are examples of quality of service requirements. Such quality of service (QoS) requirements may make the delivery of XR application services over wireless communication networks challenging.

[0003] In the context of XR media services, SA2 recently introduced the concept of protocol data unit (PDU) sets. A PDU set groups a series of PDUs that carry information units at the application level. An information unit can be an application data unit (ADU) or a service data unit (SDU). The PDUs in a PDU set should and usually are processed according to the same QoS requirements with associated constraints on delay budget and error rate. This improves the granularity of the traditional 5G QoS flow framework, allowing the RAN to optimize the mapping between QoS flows and data radio bearers (DRBs) to meet strict XR media requirements. Typically, XR media requires high-rate transmission with a short delay budget. The implementation of PDU sets in XR media communications requires, on the one hand, determining the PDU set and its constituent PDUs (i.e., identifying the PDU set boundaries), and on the other hand, applying different QoS to different PDU sets within a specific QoS flow. In traditional communication systems, all packets of a QoS flow are processed with the same QoS requirements. Summary of the invention

[0004] For XR media, the same QoS needs to be applied to the PDUs in a PDU set. However, the inventors have recognised a problem when reflective QoS mapping is used with PDU sets. The Reflective QoS Attribute (RQA) is an optional parameter that indicates that certain services (not necessarily all) carried on a particular QoS flow are subject to reflective QoS. The (Radio) Access Network ((R)AN) enables transmission of the RQI for AN resources corresponding to a QoS flow only when the RQA is signalled for that QoS flow. The RQA can be signalled to the NG-RAN via the N2 reference point at UE context establishment in the NG-RAN and when a QoS flow is established or modified.

[0005] Disclosed herein is a process for applying quality of service requirements to augmented reality media carried on a wireless communication network. The process may be implemented by a method in a user equipment of a wireless communication network and a user equipment of a wireless communication network.

[0006] A method in a user equipment of a wireless communication network is provided. The method includes sending a first protocol data unit (PDU) set of PDUs via a first data radio bearer using a first quality of service (QoS) mapping rule. The method also includes: receiving a downlink packet for the data radio bearer, the downlink packet containing header information, the header information including at least one QoS parameter indicating a second QoS mapping rule; applying the first QoS mapping rule to uplink transmissions on the data radio bearer until transmission of the last PDU in the first PDU set; and sending the PDUs in a second PDU set using the second QoS mapping rule.

[0007] A user equipment of a wireless communication network is also provided, the user equipment comprising a transmitter, a receiver and a processor. The transmitter is arranged to send a PDU in a first protocol data unit (PDU) set via a data radio bearer using a first quality of service (QoS) mapping rule. The receiver is arranged to receive a downlink packet for the data radio bearer, the downlink packet containing header information, the header information including at least one QoS parameter indicating a second QoS mapping rule. The processor is arranged to apply the first QoS mapping rule to an uplink transmission on the data radio bearer until the transmission of the last PDU in the first PDU set. The transmitter is also arranged to send the PDU in the second PDU set using the second QoS mapping rule.

[0008] Even when reflective QoS is implemented, the method and corresponding user equipment tend to ensure that the PDUs in a PDU set are processed according to the same set of QoS requirements. It is important for the timely delivery of the data contained in the PDU set that the PDUs in the PDU set are subject to the same QoS requirements and the associated constraints of delay budget and error rate. This tends to improve the granularity of the traditional 5G QoS flow framework, allowing the RAN to optimize the mapping between QoS flows and DRBs to meet, for example, stringent XR media requirements such as high-rate transmission with a short delay budget. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented by reference to certain devices and methods illustrated in the accompanying drawings. Each of these drawings depicts only certain aspects of the present disclosure and therefore should not be considered as limiting the scope thereof. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

[0010] A method and apparatus for applying quality of service requirements to augmented reality media carried on a wireless communication network will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0011] Figure 1 Embodiments of a wireless communication system for applying quality of service requirements to extended reality media carried over a wireless communication network are described;

[0012] Figure 2 depicting a user equipment device;

[0013] Figure 3 further details of the network nodes are depicted;

[0014] Figure 4 The method presented in this article is illustrated;

[0015] Figure 5 The figure illustrates the format of the SDAP data PDU of a downlink packet configured with an SDAP header;

[0016] Figure 6 The figure illustrates the format of the SDAP data PDU of an uplink packet configured with an SDAP header;

[0017] Figure 7 Three different possibilities for the required QoS for each PDU and each PDU set applicable to a QoS flow are shown;

[0018] Figure 8 shows that the UE applies the latest update of the mapping rules only at the start of transmission for the next UL PDU set; and

[0019] Fig. 9 An arrangement is shown in which the RDI bit set to 1 indicates immediate QoS reflection. DETAILED DESCRIPTION

[0020] As will be appreciated by those skilled in the art, aspects of the present disclosure may be embodied as systems, devices, methods or program products. Therefore, the arrangements described herein may be implemented in full hardware form, full software form (including firmware, resident software, microcode, etc.), or in a combination of software and hardware aspects.

[0021] For example, the disclosed methods and apparatus may be implemented as hardware circuits, including custom very large scale integrated (VLSI) circuits or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors, or other discrete components). The disclosed methods and apparatus may also be implemented in programmable hardware devices, such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0022] In addition, the method and apparatus may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code (hereinafter referred to as code). The storage device may be tangible, non-transitory, and / or non-transmitting. The storage device may not embody a signal. In some arrangements, the storage device employs only a signal for accessing a code.

[0023] 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 storing code. For example, the storage device may be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0024] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more conductors, 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 document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0025] Throughout this specification, references to examples or similar language of a particular method or device mean that the specific features, structures, or characteristics described in conjunction with the example are included in at least one implementation of the methods and devices described herein. Therefore, unless otherwise expressly specified, references to features or similar language of examples of a particular method or device may, but do not necessarily, all refer to the same example, but rather mean "one or more but not all examples". The terms "including", "comprising", "having" and their variations mean "including but not limited to", unless otherwise expressly specified. An enumerated list of items does not imply that any or all items are mutually exclusive, unless otherwise expressly specified. The terms "a", "an", and "the" also refer to "one or more", unless otherwise expressly specified.

[0026] As used herein, a list with the conjunction "and / or" includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one or more of..." includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one of..." includes one and only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and does not include a combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C" includes one and only one of A, B, or C, and does not include a combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B and C and combinations thereof” includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B and C.

[0027] In addition, the described features, structures or characteristics described herein may be combined in any suitable manner. In the following description, many 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, etc., to provide a comprehensive understanding of the present disclosure. However, those skilled in the relevant art will recognize that the disclosed methods and apparatus can be practiced without one or more of the specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid confusing aspects of the present disclosure.

[0028] Aspects of the disclosed methods and apparatus are described below with reference to schematic flow charts and / or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flow charts and / or schematic block diagrams, and the combination of blocks in the schematic flow charts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / actions specified in the schematic flow charts and / or schematic block diagrams.

[0029] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other device to work in a specific manner, so that the instructions stored in the storage device produce an article of manufacture that includes instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0030] The code can also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operating steps to be executed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0031] The schematic flow charts and / or schematic block diagrams in the figures illustrate the architecture, functionality and operation of possible implementations of devices, systems, methods and program products. In this regard, each box in the schematic flow charts and / or schematic block diagrams may represent a module, segment or portion of code, which includes one or more executable instructions of the code for implementing (multiple) specified logical functions.

[0032] It should also be noted that in some alternative implementations, the functions mentioned in the blocks may not appear in the order mentioned in the drawings. For example, in fact, two blocks shown in succession may be substantially executed concurrently, or the two blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods that are equivalent in function, logic or effect to one or more blocks or portions thereof of the illustrated drawings can be envisioned.

[0033] The description of an element in each figure may refer to elements of subsequent figures. Like reference numerals refer to like elements throughout the figures.

[0034] Figure 1 An embodiment of a wireless communication system 100 for implementing quality of service for augmented reality media over a wireless communication network is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Figure 1 A specific number of remote units 102 and network units 104 are depicted in FIG. 1 , but those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0035] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, a modem), an aircraft, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness bracelet, an optical head-mounted display, etc. In addition, the remote unit 102 may be referred to as a subscriber unit, a mobile station, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, the remote unit 102 may communicate directly with other remote units 102 via side link communications.

[0036] The network elements 104 may be distributed over geographical intervals. In some embodiments, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, node Bs, eNBs, gNBs, home node Bs, relay nodes, devices, core networks, air servers, radio access nodes, APs, NRs, network entities, access and mobility management functions (AMFs), unified data management functions (UDMs), unified data repositories (UDRs), UDM / UDRs, policy control functions (PCFs), radio access networks (RANs), network slice selection functions (NSSFs), operations, maintenance, and management (OAMs), session management functions (SMFs), user plane functions (UPFs), application functions, authentication server functions (AUSFs), security anchor functionality (SEAFs), trusted non-3GPP gateway functions (TNGFs), application functions, service enablement architecture layer (SEAL) functions, vertical application enablement servers, edge enablement servers, edge configuration servers, mobile edge computing platform functions, mobile edge computing applications, application data analysis enablement servers, SEAL data delivery servers, middleware entities, network slice capability management servers, or any other term used in the art. The network elements 104 are generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is generally communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and a public switched telephone network. These and other elements of the radio access network and core network are not shown, but are generally known by those of ordinary skill in the art.

[0037] In one implementation, the wireless communication system 100 complies with the New Radio (NR) protocol standardized in 3GPP, wherein the network unit 104 transmits on the downlink (DL) using an orthogonal frequency division multiplexing (OFDM) modulation scheme, and the remote unit 102 transmits on the uplink (UL) using a single carrier frequency division multiple access (SC-FDMA) scheme or an OFDM scheme. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfox, etc. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0038] The network unit 104 can serve multiple remote units 102 within a service area, for example, serving a cell or cell sector via wireless communication links. The network unit 104 sends DL communication signals to serve the remote units 102 in the time domain, frequency domain, and / or spatial domain.

[0039] Figure 2 A user equipment device 200 that can be used to implement the methods described herein is depicted. The user equipment device 200 is used to implement one or more solutions described herein. The user equipment device 200 is in accordance with one or more user equipment devices described in the embodiments herein. The user equipment device 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0040] The input device 215 and the output device 220 may be combined into a single device, such as a touch screen. In some implementations, the user equipment apparatus 200 does not include any input device 215 and / or output device 220. The user equipment apparatus 200 may include one or more of the following: a processor 205, a memory 210, and a transceiver 225, and may not include an input device 215 and / or an output device 220.

[0041] As depicted, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 can communicate with one or more cells (or wireless coverage areas) supported by one or more base station units. The transceiver 225 can be operable on an unlicensed spectrum. In addition, the transceiver 225 can include multiple UE panels supporting one or more beams. Additionally, the transceiver 225 can support at least one network interface 240 and / or application interface 245. (Multiple) application interface 245 can support one or more APIs. (Multiple) network interface 240 can support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 240 can be supported, as understood by those of ordinary skill in the art.

[0042] The processor 205 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 205 may be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, a field programmable gate array (FPGA), or a similar programmable controller. The processor 205 may execute instructions stored in the memory 210 to perform the methods and routines described herein. The processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225.

[0043] Processor 205 may control user equipment device 200 to implement the user equipment device behaviors described herein. Processor 205 may include an application processor (also referred to as a "main processor") that manages application domain and operating system (OS) functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0044] The memory 210 may be a computer-readable storage medium. The memory 210 may include a volatile computer storage medium. For example, the memory 210 may include a RAM including a dynamic RAM (DRAM), a synchronous dynamic RAM (SDRAM), and / or a static RAM (SRAM). The memory 210 may include a non-volatile computer storage medium. For example, the memory 210 may include a hard drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 210 may include both a volatile computer storage medium and a non-volatile computer storage medium.

[0045] The memory 210 may store data related to implementing the traffic class fields described herein. The memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on the device 200.

[0046] Input device 215 may include any known computer input device, including a touchpad, buttons, keyboard, stylus, microphone, etc. Input device 215 may be integrated with output device 220, for example, as a touch screen or similar touch-sensitive display. Input device 215 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 215 may include two or more different devices, such as a keyboard and a touchpad.

[0047] The output device 220 may be designed to output visual signals, audible signals, and / or tactile signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 220 may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display, an organic LED (OLED) display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 220 may include a wearable display that is separate from the rest of the user device apparatus 200 but communicatively coupled to the rest, such as a smart watch, smart glasses, a head-up display, etc. In addition, the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0048] Output device 220 may include one or more speakers for producing sound. For example, output device 220 may produce an audible alarm or notification (e.g., a beep or chime). Output device 220 may include one or more tactile devices for producing vibration, motion, or other tactile feedback. All or part of output device 220 may be integrated with input device 215. For example, input device 215 and output device 220 may form a touch screen or similar touch-sensitive display. Output device 220 may be located near input device 215.

[0049] The transceiver 225 communicates with one or more network functions of the mobile communication network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to send messages, data and other signals, and also receive messages, data and other signals. For example, the processor 205 can selectively activate the transceiver 225 (or part thereof) at a specific time to send messages and receive messages.

[0050] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. One or more transmitters 230 can be used to provide uplink communication signals to the base station unit of the wireless communication network. Similarly, one or more receivers 235 can be used to receive downlink communication signals from the base station unit. Although only one transmitter 230 and one receiver 235 are illustrated, the user equipment device 200 can have any suitable number of transmitters 230 and receivers 235. In addition, (multiple) transmitters 230 and (multiple) receivers 235 can be any suitable type of transmitter and receiver. The transceiver 225 may include a first transmitter / receiver pair for communicating with a mobile communication network through a licensed radio spectrum, and a second transmitter / receiver pair for communicating with a mobile communication network through an unlicensed radio spectrum.

[0051] A first transmitter / receiver pair that can be used to communicate with a mobile communication network via a licensed radio spectrum, and a second transmitter / receiver pair for communicating with a mobile communication network via an unlicensed radio spectrum can be combined into a single transceiver unit, for example, a single chip that performs functions for use with both the licensed radio spectrum and the unlicensed radio spectrum. The first transmitter / receiver pair and the second transmitter / receiver pair can share one or more hardware components. For example, some of the transceivers 225, transmitter 230, and receiver 235 can be implemented as physically separate components that access shared hardware resources and / or software resources (such as, for example, network interface 240).

[0052] One or more transmitters 230 and / or one or more receivers 235 can be implemented as a single hardware component and / or integrated into a single hardware component, such as a multi-transceiver chip, a system on chip, an application specific integrated circuit (ASIC), or other types of hardware components. One or more transmitters 230 and / or one or more receivers 235 can be implemented as a multi-chip module and / or integrated into a multi-chip module. Other components (such as a network interface 240 or other hardware components / circuits) can be integrated into a single chip with any number of transmitters 230 and / or receivers 235. Transmitters 230 and receivers 235 can be logically configured as transceivers 225 using one or more common control signals, or can be logically configured as modular transmitters 230 and receivers 235 implemented in the same hardware chip or multi-chip module.

[0053] Figure 3 Further details of a network node 300 are depicted which may be used to implement the methods described herein. The network node 300 comprises a processor 305, a memory 310, an input device 315, an output device 320 and a transceiver 325.

[0054] The input device 315 and the output device 320 may be combined into a single device, such as a touch screen. In some implementations, the network node 300 does not include any input device 315 and / or output device 320. The network node 300 may include one or more of the following: a processor 305, a memory 310, and a transceiver 325, and may not include an input device 315 and / or an output device 320.

[0055] As depicted, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more remote units 200. Additionally, the transceiver 325 can support at least one network interface 340 and / or an application interface 345. The (multiple) application interface 345 can support one or more APIs. The (multiple) network interface 340 can support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 340 can be supported, as understood by those of ordinary skill in the art.

[0056] The processor 305 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 305 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or a similar programmable controller. The processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.

[0057] The memory 310 may be a computer-readable storage medium. The memory 310 may include a volatile computer storage medium. For example, the memory 310 may include a RAM including a dynamic RAM (DRAM), a synchronous dynamic RAM (SDRAM), and / or a static RAM (SRAM). The memory 310 may include a non-volatile computer storage medium. For example, the memory 310 may include a hard drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 310 may include both a volatile computer storage medium and a non-volatile computer storage medium.

[0058] The memory 310 may store data related to establishing a multipath unicast link and / or mobile operation. For example, the memory 310 may store parameters, configurations, resource assignments, policies, etc., as described herein. The memory 310 may also store program code and related data, such as an operating system or other controller algorithm operating on the network node 300.

[0059] Input device 315 may include any known computer input device, including a touch pad, buttons, keyboard, stylus, microphone, etc. Input device 315 may be integrated with output device 320, for example, as a touch screen or similar touch-sensitive display. Input device 315 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 315 may include two or more different devices, such as a keyboard and a touch pad.

[0060] Output device 320 may be designed to output visual signals, audible signals, and / or tactile signals. Output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device 320 may include a wearable display that is separate from the rest of network node 300 but communicatively coupled to the rest, such as a smart watch, smart glasses, a head-up display, etc. In addition, output device 320 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0061] Output device 320 may include one or more speakers for producing sound. For example, output device 320 may produce an audible alarm or notification (e.g., a beep or chime). Output device 320 may include one or more tactile devices for producing vibration, motion, or other tactile feedback. All or part of output device 320 may be integrated with input device 315. For example, input device 315 and output device 320 may form a touch screen or similar touch-sensitive display. Output device 320 may be located near input device 315.

[0062] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. One or more transmitters 330 can be used to communicate with the UE, as described herein. Similarly, one or more receivers 335 can be used to communicate with network functions in the PLMN and / or RAN, as described herein. Although only one transmitter 330 and one receiver 335 are illustrated, the network node 300 can have any suitable number of transmitters 330 and receivers 335. In addition, the (multiple) transmitters 330 and (multiple) receivers 335 can be any suitable type of transmitter and receiver.

[0063] Figure 4 A method 400 in a user equipment of a wireless communication network is illustrated. The method 400 includes sending 410 a first set of protocol data units (PDUs) via a first data radio bearer using a first quality of service (QoS) mapping rule. The method 400 also includes: receiving 420 a downlink packet for the data radio bearer, the downlink packet including header information including at least one QoS parameter indicating a second QoS mapping rule; applying 430 the first QoS mapping rule to uplink transmissions on the data radio bearer until transmission of a last PDU in the first set of PDUs; and sending 440 the PDUs in a second set of PDUs using the second QoS mapping rule.

[0064] Even when reflective QoS is implemented, such an approach tends to ensure that the PDUs in a PDU Set are processed according to the same set of QoS requirements. It is important for the timely delivery of the data contained within the PDU Set that the PDUs in a PDU Set are subject to the same QoS requirements and the associated constraints of delay budget and error rate. This tends to improve the granularity of the traditional 5G QoS flow framework, allowing the RAN to optimize the mapping between QoS flows and DRBs to meet, for example, stringent XR media requirements such as high-rate transmissions with short delay budgets.

[0065] The header information may be a Service Data Adaptation Protocol (SDAP) header. A data radio bearer (DRB) may carry packets from multiple QoS flows. The QoS mapping rules specify which QoS flows' PDUs will be carried in a certain DRB. The PDUs in the second PDU set may be sent via a second data radio bearer. The PDUs in the second PDU set may be sent via the same data radio bearer as the PDUs in the first PDU set or via a different data radio bearer. A change in QoS mapping rules may mean that packets from a certain QoS flow may be mapped to a different second DRB instead of the first DRB. The second DRB may exist in parallel with the first DRB.

[0066] The method may further include saving the second QoS mapping rule to the packet filter.The packet filter may be applied to the QoS flow indicated by the new QoS mapping rule for the data radio bearer received in the downlink.

[0067] The QoS parameters may include a QoS flow identifier (QFI) value. Each PDU set includes one or more PDUs that carry a payload of an information unit generated at the application level. The information unit may include an application data unit. The information unit may include a frame or a video slice. The information unit may be used for an XRM service.

[0068] A reflective QoS flow to data radio bearer mapping indication (RDI) bit received in a DL data PDU with an SDAP header may be used to indicate to the user equipment a change of the QoS mapping rule from the first QoS mapping rule to the second QoS mapping rule.

[0069] The method may further include: sending an end marker on the data radio bearer when the applied QoS mapping rule is changed.The QoS mapping rule may be changed from a first QoS mapping rule to a second QoS mapping rule.

[0070] A user equipment of a wireless communication network is also provided, the user equipment comprising a transmitter, a receiver and a processor. The transmitter is arranged to send a PDU in a first protocol data unit (PDU) set via a data radio bearer using a first quality of service (QoS) mapping rule. The receiver is arranged to receive a downlink packet for the data radio bearer, the downlink packet containing header information, the header information including at least one QoS parameter indicating a second QoS mapping rule. The processor is arranged to apply the first QoS mapping rule to an uplink transmission on the data radio bearer until the transmission of the last PDU in the first PDU set. The transmitter is also arranged to send the PDU in the second PDU set using the second QoS mapping rule.

[0071] Even when implementing reflective QoS, such user equipment tends to ensure that the PDUs in a PDU Set are processed according to the same set of QoS requirements. It is important for the timely delivery of the data contained within the PDU Set that the PDUs in a PDU Set are subject to the same QoS requirements and the associated constraints of delay budget and error rate. This tends to improve the granularity of the traditional 5G QoS flow framework, allowing the RAN to optimize the mapping between QoS flows and DRBs to meet, for example, stringent XR media requirements such as high-rate transmission with a short delay budget.

[0072] The header information may be a Service Data Adaptation Protocol (SDAP) header. A data radio bearer (DRB) may carry packets from multiple QoS flows. The QoS mapping rules specify which QoS flows' PDUs will be carried in a certain DRB. The PDUs in the second PDU set may be sent via the same data radio bearer as the PDUs in the first PDU set or via a different data radio bearer. A change in QoS mapping rules may mean that packets from a certain QoS flow may be mapped to a different second DRB instead of the first DRB. The second DRB may exist in parallel with the first DRB.

[0073] The user equipment may further comprise a storage element arranged to save the second QoS mapping rule to the packet filter. The packet filter may be applied to the QoS flow indicated by the new QoS mapping rule for the data radio bearer received in the downlink. The QoS parameters may comprise a QoS flow identifier (QFI) value.

[0074] Each PDU set may include one or more PDUs carrying a payload of an information unit generated at the application level. The information unit may include an application data unit. The information unit may include a frame or a video slice. The information unit may be used for an XRM service.

[0075] A reflective QoS flow to data radio bearer mapping indication (RDI) bit received in a DL data PDU with an SDAP header may be used to indicate to the user equipment a change of the QoS mapping rule from the first QoS mapping rule to the second QoS mapping rule.

[0076] The sender may further be arranged to send an end marker on the data radio bearer when the applied QoS mapping rule is changed.The QoS mapping rule may be changed from a first QoS mapping rule to a second QoS mapping rule.

[0077] Reflective QoS is controlled on a per-packet basis by using a Reflective QoS Indication (RQI) in the encapsulation header over the N3 (and N9) reference point together with the QFI and together with a Reflective QoS Timer (RQ Timer) value which is signaled to the UE or set to a default value at PDU Session Establishment (or at PDU Session Modification as described in 3GPP TS 23.501 v17.5.0 clause 5.17.2.2.2). The RQ Timer value provided by the core network is at the granularity of the PDU Session (details are specified in 3GPP TS 24.501 v17.7.1).

[0078] When the 5GC determines that Reflective QoS must be used for a specific SDF belonging to a QoS Flow, the Session Management Function (SMF) shall provide the RQA (Reflective QoS Attribute) within the QoS Profile of the QoS Flow to the NG-RAN over the N2 reference point, unless the SMF has previously done so. When the RQA has already been provided to the NG-RAN for a QoS Flow and the 5GC determines that the QoS Flow no longer carries a Service Data Flow (SDF) for which Reflective QoS must be used, the SMF shall signal to the NG-RAN over the N2 reference point to remove the RQA (Reflective QoS Attribute) from the QoS Profile of the QoS Flow.

[0079] In some arrangements, the SMF may have a timer to delay sending of the RQA removal. This avoids signaling to the RAN if a new SDF subject to reflective QoS is simultaneously bound to the QoS flow.

[0080] When the 5GC determines to use reflective QoS for a specific SDF, the SMF shall ensure that the user plane function (UPF) applies an RQI marking for the SDF. The RQI marking may include an indication to use reflective QoS set in the QER associated with the DL packet detection rule (PDR), if not already set. The SMF shall also ensure that uplink packets for the SDF can be received by the UPF from the QoS flow whose DL PDR is associated with the QoS flow, as specified in 3GPP TS29.244v17.5.0. For example, the SMF may generate a new UL PDR for the SDF for the QoS flow and provide the UL PDR to the UPF.

[0081] When the UPF is instructed by the SMF to apply the RQI marking, the UPF shall set the RQI for each DL packet corresponding to the SDF in the encapsulation header on the N3 (or N9) reference point.

[0082] When an RQI is received by the (R)AN in a DL packet over the N3 reference point, the (R)AN shall indicate the QFI and RQI of the DL packet to the UE.

[0083] Upon receiving a DL packet with an RQI: if there is no UE-derived QoS rule with a packet filter corresponding to the DL packet, then: the UE shall create a new UE-derived QoS rule with a packet filter corresponding to the DL packet; and for the UE-derived QoS rule, the UE shall start a timer set to the RQ timer value.

[0084] If a UE-derived QoS rule with a packet filter corresponding to the DL packet does already exist, then: the UE shall restart the timer associated with the UE-derived QoS rule; and if the QFI associated with the downlink packet is different from the QFI associated with the UE-derived QoS rule, the UE shall update the UE-derived QoS rule with the newly received QFI.

[0085] In some arrangements, non-3GPP access networks (ANs) do not require N2 signaling to enable reflective QoS. Non-3GPP accesses are expected to send QFI and RQI transparently to the UE. If the UPF does not include RQI, UE-derived QoS rules will not be generated. If RQI is included to help the UE trigger an update to the UE-derived QoS rules, the reception of the PDU for the QFI restarts the RQ timer.

[0086] Figure 5 The format of the SDAP data PDU of a downlink packet 500 configured with an SDAP header is illustrated. The downlink packet 500 includes a plurality of octets 508. The first octet includes a reflective QoS flow to DRB mapping indication (RDI) 510, a reflective QoS indication (RQI) 520, and a QoS flow identifier (QFI) 530. The remaining octets include data 550.

[0087] The RDI field 510 has a length of 1 bit and indicates whether the QoS flow to DRB mapping rule should be updated.

[0088] Bit describe 0 No Action 1 Stores QoS flow to DRB mapping rules.

[0089] Table 1: RDI fields

[0090] The RQI field 520 has a length of 1 bit and indicates whether the NAS should be informed of the update of the SDF to QoS flow mapping rule (3GPP TS 23.501 v17.5.0).

[0091] Bit describe 0 No Action 1 The RQI bit is set to 1 to inform NAS.

[0092] Table 2: RQI fields

[0093] Figure 6 The format of the SDAP data PDU of an uplink packet 600 configured with an SDAP header is illustrated. The downlink packet 600 includes a plurality of octets 608. The first octet includes a 1-bit D / C field 615, a reserved field R 625, and a QoS flow identifier (QFI) 630. The 1-bit D / C field 615 is set to zero to indicate a control PDU. The remaining octets include data 650.

[0094] Figure 7 Three different possibilities 710, 720 and 730 are shown for the required QoS for each PDU and each PDU set applicable to the QoS flow. Each illustrated possibility includes four PDU sets, each PDU set includes 1 to 4 PDUs, each PDU consists of Figure 7 As shown in the legend, there are four possible classifications of PDUs in this example: packets of PDU sets using QoS-1, 701; packets of PDU sets using QoS-2, 702; packets of PDU sets using QoS-3, 703; and individual packets that do not belong to any PDU set, 705.

[0095] In the first possibility (Possibility-1) 710, all PDU sets will be processed with the same QoS and therefore each PDU undergoes the same QoS treatment, in this case, QoS-1 701 is applied to each packet.

[0096] In the second possibility (Possibility-2) 720, the first PDU set having PDU 1 to PDU 3 and the third PDU set having PDU 8 to PDU 9 will be processed using QoS-1 701, and therefore each of these 5 PDUs will undergo the same QoS processing, unlike the PDUs in the second (4 to 7) PDU set and the fourth (10 to 12) PDU set which are processed using QoS-2 702 and QoS-3 703, respectively.

[0097] In the third possibility (Possibility-3) 730, all PDU sets will be processed with QoS-1 701, and thus each PDU belonging to a PDU set will undergo the same QoS treatment QoS-1 701. However, PDUs that do not belong to any PDU set (e.g., PDU 4 and PDU 8) are considered to have no specific QoS, 705. For practical purposes, in the solution disclosed herein, it is assumed that a PDU that is not part of any PDU set is part of its own PDU set (i.e., its PDU set contains only one PDU).

[0098] Figure 7 Indicates a downlink packet. In the corresponding uplink direction, the mapping of QoS flows to DRBs can also be controlled by using reflective QoS mapping.

[0099] In operation, for each DRB, the UE monitors the QFI(s) of the downlink packets and applies the same mapping in the uplink; i.e., for a DRB, the UE maps the uplink packets belonging to the QoS flows(s) corresponding to the QFI(s) and PDU sessions observed in the downlink packets for that DRB. Once QoS mapping starts, the same QoS mapping rules are saved and used based on the most recently available QFI(s) received in the DL until the transmission of the currently ongoing UL PDU set is completed, i.e., all PDUs in the PDU set will use the same QoS mapping rules as the QoS mapping rules used for the first PDU in the corresponding PDU set. In other words, the UE maps the uplink PDUs in the PDU sets belonging to the QoS flows(s) corresponding to the QFI(s) and PDU sessions observed in the downlink packets for that DRB, and applies the most recent update of the mapping rules only at the start of transmission for the next UL PDU set; the PDUs in the current PDU set in transmission may use only the stored / current QoS mapping rules. To achieve this reflective mapping, NG-RAN marks the downlink packets on Uu with QFI.

[0100] Figure 8 It is shown that the UE applies the most recent update of the mapping rules only at the start of transmission for the next UL PDU set. The legend shows four possible classifications of packets: packets of PDU sets utilizing QoS-1, 801; packets of PDU sets utilizing QoS-2, 802; packets of PDU sets utilizing QoS-3, 803; and individual packets that do not belong to any PDU set, 805. For example, PDU-set 1 in UL 850 uses the most recent QoS mapping (QFI(s)) available at the time, i.e., QoS-1 801 from PDU-set 1 received in DL 840; while PDU-set 2 in UL 850 uses the most recent QoS mapping (QFI(s)) available at the time, i.e., QoS-1 801 from PDU-set 3 received in DL 840 (and not QoS-2 802 from PDU-set 2 in DL 840). Upon transmission of PDU-set 3 in UL 850 , the QoS attribute of QoS-3 803 (5QI-c) will be used, which corresponds to the QFI(s) of QoS-3 803 received upon reception of PDU-set 4 in DL 840 .

[0101] In some arrangements, when updating the QoS flow to DRB mapping rules, the UE sends an end marker on the old bearer. The UE sends an end marker from the DL reception, such as when the transmission of the currently ongoing PDU set ends, or at least when the last PDU in the PDU set is sent or is being sent. Figure 5 The received RQI bit (set to 1) received in the DL data PDU with the SDAP header shown in is indicated to the NAS, informing it of the update of the SDF to QoS flow mapping rules.

[0102] In an alternative mode of operation, the RDI bit received in a DL data PDU with an SDAP header (eg Figure 5 ) indicates whether the QoS flow to DRB mapping rules should be updated. When a UE receives the RDI bit set to 1, the UE immediately starts mapping uplink PDUs belonging to (multiple) QoS flows corresponding to (multiple) QFIs and PDU sessions observed in the downlink packets for this DRB, without waiting for the start of the next PDU set. Such an operation mode may not be covered by the attached claims. Fig. 9 An arrangement is shown in which the RDI bit set to 1 indicates immediate QoS reflection. Fig. 9 The legend shows four possible classifications of packets: packets utilizing PDU set QoS-1, 901; packets utilizing PDU set QoS-2, 902; packets utilizing PDU set QoS-3, 903; and individual packets that do not belong to any PDU set, 905. The uplink 950 PDUs (PDU-1 and PDU-2) belong to PDU set-1, but the UE begins mapping PDU-2 corresponding to the (multiple) QFIs and PDU sessions observed in downlink PDU set 2 for this DRB. PDU-1 in uplink 950 uses QoS-1 901, reflecting PDU set-1 in downlink 940. PDU-2 in uplink 950 uses QoS-2 902, reflecting PDU set 2 in downlink 940.

[0103] Thus, the UE may map uplink PDUs in a PDU set belonging to (multiple) QoS flows corresponding to the (multiple) QFIs and PDU sessions observed in the downlink packets for that DRB and apply the most recent update of the mapping rules only at the start of transmission for the next UL PDU set; the PDUs in the current PDU set in transmission may only use the stored / current QoS mapping rules.

[0104] The RQI bit received (set to 1) in a DL data PDU with an SDAP header may be indicated to the NAS only after the transmission of the currently ongoing PDU set ends, or at least until the last PDU in the PDU set is sent or is being sent.

[0105] An alternative operating mode is provided such that when a UE receives the RDI bit set to 1, the UE immediately starts mapping uplink PDUs belonging to (multiple) QoS flows corresponding to the (multiple) QFIs and PDU sessions observed in the downlink packets for that DRB, without waiting for the start of the next PDU set.

[0106] Therefore, a method is provided, which includes: receiving a downlink packet for a DRB, the downlink packet containing SDAP header information, the SDAP header information including at least a QFI value; applying the current QoS mapping rule to the UL transmission on the bearer until the transmission of the last PDU in the corresponding PDU set in the transmission has begun; saving the received QoS mapping rule configuration to a packet filter based on the received QFI for the bearer; once the last PDU in the corresponding PDU set in the transmission is sent, treating the saved QoS mapping rule as the current QoS mapping rule for the bearer; and applying the current QoS mapping rule to the UL transmission on the bearer.

[0107] A PDU set may consist of one or more PDUs carrying the payload of one information unit generated at the application level (eg, a frame or video slice for an XRM service).

[0108] The RDI bit received in a DL data PDU with an SDAP header may be used to indicate changes regarding QoS mapping rules to the UE.

[0109] It should be noted that the methods and devices mentioned above illustrate rather than limit the present invention, and that those skilled in the art will be able to design many alternative arrangements without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps other than those listed in the claims, "a" or "an" does not exclude a plurality, and a single processor or other unit may perform the functions of multiple units listed in the claims. Any reference signs in the claims should not be construed as limiting their scope.

[0110] In addition, although examples are given in the context of specific communication standards, these examples are not intended to limit the communication standards to which the disclosed methods and apparatus may be applied. For example, although specific examples are given in the context of 3GPP, the principles disclosed herein may also be applied to another wireless communication system, and in fact may be applied to any communication system that uses routing rules.

[0111] The method may also be embodied in an instruction set stored on a computer-readable medium, which, when loaded into a computer processor, a digital signal processor (DSP) or the like, causes the processor to perform the method described above.

[0112] The described methods and devices may be practiced in other specific forms. The described methods and devices are considered in all respects to be illustrative only and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes that fall within the equivalent meaning and range of the claims are included within the scope of the claims.

[0113] The following abbreviations are relevant in the field of the present disclosure: 3GPP, 3rd Generation Partnership Project; 5G, fifth generation; 5GS, 5G System; 5QI, 5G QoS identifier; AF, application function; AMF, access and mobility function; AR, augmented reality; DL, downlink; DRB, data radio bearer; NAL, network abstraction layer; PCF, policy control function; PDU, packet data unit; PPS, picture parameter set; QFI, QoS flow identifier; QoE, quality of experience; QoS, quality of service; PDR, packet detection rule; RAN, radio access network; RTCP, real-time control protocol; RTP, real-time protocol; RDI, reflective QoS flow to DRB mapping indication; RQI, reflective QoS indication; SDAP, service data adaptation protocol; SDF, service data flow; SMF, session management function; SRTCP, secure real-time control protocol; SRTP, secure real-time protocol; UE, user equipment; UL, uplink; UPF, user plane function; VCL, video coding layer; VMAF, video multi-method assessment function; VPS, video parameter set; VR, virtual reality; XR, extended reality; XR AS, XR application server; and XRM, XR media.

Claims

1. A method in a user equipment of a wireless communication network, the method comprising: sending, via a first data radio bearer, a first quality of service (QoS) mapping rule, a first protocol data unit (PDU) in a first set of PDUs; receiving a downlink packet for the data radio bearer, the downlink packet comprising header information, the header information including at least one QoS parameter indicating a second QoS mapping rule; applying the first QoS mapping rule to uplink transmissions on the data radio bearer until the transmission of a last PDU in the first PDU set; as well as The PDUs in the second PDU set are sent using the second QoS mapping rule.

2. The method according to claim 1, further comprising: The second QoS mapping rule is saved in the packet filter.

3. The method of claim 1 or 2, wherein the QoS parameter comprises a QoS Flow Identifier (QFI) value.

4. The method according to any one of claims 1, 2 or 3, wherein each PDU set comprises one or more PDUs, the one or more PDUs carrying the payload of the information unit generated at the application level.

5. A method according to any preceding claim, wherein a reflective QoS flow to data radio bearer mapping indication (RDI) bit received in a DL data PDU with an SDAP header is used to indicate to the user equipment the change of QoS mapping rules from the first QoS mapping rules to the second QoS mapping rules.

6. The method according to any preceding claim, further comprising: When the applied QoS mapping rule is changed, an end marker is sent on the data radio bearer.

7. A user equipment of a wireless communication network, the user equipment comprising: a transmitter arranged to transmit, via a data radio bearer, a first quality of service (QoS) mapping rule, a first set of protocol data units (PDUs); a receiver arranged to receive a downlink packet for the data radio bearer, the downlink packet comprising header information including at least one QoS parameter indicating a second QoS mapping rule; a processor arranged to apply the first QoS mapping rule to uplink transmissions on the data radio bearer until the transmission of a last PDU in the first PDU set; The transmitter is further arranged to transmit the PDUs in the second PDU set using the second QoS mapping rule.

8. The user equipment according to claim 7, further comprising: A storage element is arranged to save the second QoS mapping rule to a packet filter.

9. The user equipment according to claim 7 or 8, wherein the QoS parameter comprises a QoS Flow Identifier (QFI) value.

10. The user equipment according to any one of claims 7, 8 or 9, wherein each PDU set comprises one or more PDUs, the one or more PDUs carrying the payload of the information unit generated at the application level.

11. A user equipment according to any one of claims 7 to 10, wherein a reflective QoS flow to data radio bearer mapping indication (RDI) bit received in a DL data PDU with an SDAP header is used to indicate to the user equipment the change of QoS mapping rules from the first QoS mapping rules to the second QoS mapping rules.

12. The user equipment according to any one of claims 7 to 11, wherein the transmitter is further arranged to transmit an end marker on the data radio bearer when the applied QoS mapping rule is changed.

Images