WO2025019417A1

WO2025019417A1 - Methods, architectures, apparatuses and systems for managing extended reality traffic transmissions

Info

Publication number: WO2025019417A1
Application number: PCT/US2024/038029
Authority: WO
Inventors: Ognen OGNENOSKI; Jaya Rao; Paul Marinier; Senay NEGUSSE; Oumer Teyeb; Tejaswinee LUTCHOOMUN; Ahmed Mostafa
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2023-07-14
Filing date: 2024-07-15
Publication date: 2025-01-23
Anticipated expiration: 2026-01-14

Abstract

Procedures, methods, architectures, apparatuses, systems, devices, and computer program products for managing processing delays of protocol data unit (PDU) sets in the uplink and/or the downlink directions. For example, a wireless transmit/receive unit (WTRU) may send, using a first set of resources, information indicating one or more TBs of a PDU set associated with hybrid automatic repeat request (HARQ) information. The WTRU may receive HARQ feedback information associated with the HARQ information indicating retransmission of the one or more TBs of the PDU set. The WTRU may receive information indicating a second set of granted resources associated with the retransmission of the one or more TBs of the PDU set. The WTRU may send, using the second set of granted resources, one or more TBs of another PDU set associated with the first HARQ information based on an importance and/or priority information.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR MANAGING EXTENDED REALITY TRAFFIC TRANSMISSIONS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63/526,691 filed 14-Jul-2023 which is incorporated herein by reference.

TECHNICAL FIELD

[0002] The present disclosure is generally directed to the fields of communications, software and encoding, including, for example, to methods, architectures, apparatuses, systems directed to the management of extended reality (XR) traffic. More specifically, XR traffic transmissions may be managed based on traffic processing delays (TPD) and Quality of Experience (QoE)-related measurements.

BACKGROUND

[0003] XR traffic may sent and/or received in the uplink and downlink directions. Processing delays may occur at different layers of the protocol stack. It would be desirable to provide solutions to address varying requirements of PDU sets (e.g., the XR traffic) to manage the transmissions based on processing delays.

SUMMARY

[0004] In a representative embodiment, a wireless transmit/receive unit (WTRU) may be configured to implement a procedure for transport block (TB) transmission from a protocol data unit (PDU) set based on importance and/or priority information. For example, a WTRU may include a processor, a memory, and a transceiver which are configured to implement the procedure. The WTRU may send, using a first set of resources, information indicating one or more transport blocks (TBs) of a first PDU set associated with first hybrid automatic repeat request (HARQ) information. The WTRU may receive HARQ feedback information associated with the first HARQ information indicating retransmission of the one or more TBs of the first PDU set. The WTRU may receive information indicating a second set of granted resources associated with the retransmission of the one or more TBs of the first PDU set. The WTRU may send, using the second set of granted resources, one or more TBs of a second PDU set associated with the first HARQ information based on an importance of the second PDU set being higher than an importance of the first PDU set.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein: [0006] FIG. 1 A is a system diagram illustrating an example communications system;

[0007] FIG. IB is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;

[0008] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A;

[0009] FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;

[0010] FIG. 2 is a flow diagram illustrating an example communications sequence for transport block (TB) transmission of a protocol data unit (PDU) set based on importance and/or priority;

[0011] FIG. 3 is a flow diagram illustrating an example communications sequence for reporting traffic processing delay and/or Quality of Experience (QoE) related information;

[0012] FIG. 4 is a procedural diagram illustrating an example procedure for TB transmission of PDU sets;

[0013] FIG. 5 is a procedural diagram illustrating an example procedure for reporting traffic processing delay and/or QoE related information;

[0014] FIG. 6 is a procedural diagram illustrating another example procedure for TB transmission of PDU sets;

[0015] FIG. 7 is a procedural diagram illustrating another example procedure for reporting traffic processing delay and/or QoE related information;

[0016] FIG. 8 is a procedural diagram illustrating another example procedure for TB transmission of PDU sets; and

[0017] FIG. 9 is a procedural diagram illustrating another example procedure for reporting traffic processing delay and/or QoE related information.

DETAILED DESCRIPTION

[0018] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. Although various embodiments are described and/or claimed herein in which an apparatus, system, device, etc. and/or any element thereof carries out an operation, process, algorithm, function, etc. and/or any portion thereof, it is to be understood that any embodiments described and/or claimed herein assume that any apparatus, system, device, etc. and/or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and/or any portion thereof.

[0019] Example Communications System

[0020] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.

[0021] FIG. 1A is a system diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0022] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104/113, a core network (CN) 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a "station" and/or a "STA", may be configured to transmit and/or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0023] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d, e.g., to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

[0024] The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

[0025] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0026] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

[0027] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE- Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).

[0028] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0031] The base station 114b in FIG. 1 A may be a wireless router, Home Node-B, Home eNode- B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a small cell, picocell or femtocell. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106/115.

[0032] The RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT. For example, in addition to being connected to the RAN 104/113, which may be utilizing an NR radio technology, the CN 106/115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0033] The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/114 or a different RAT.

[0034] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0035] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other elements/peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0036] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.

[0037] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in an embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/ detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In an embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

[0038] Although the transmit/receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit/receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0039] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example. [0040] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), readonly memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0041] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0042] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0043] The processor 118 may further be coupled to other elements/peripherals 138, which may include one or more software and/or hardware modules/units that provide additional features, functionality and/or wired or wireless connectivity. For example, the elements/peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and/or augmented reality (VR/AR) device, an activity tracker, and the like. The elements/peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.

[0044] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

[0045] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0046] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0047] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0048] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the CN operator.

[0049] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.

[0050] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0051] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0052] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.

[0053] Although the WTRU is described in FIGs. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network. [0054] In representative embodiments, the other network 112 may be a WLAN.

[0055] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a distribution system (DS) or another type of wired/wireless network that carries traffic into and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802. l ie DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.

[0056] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0057] High throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0058] Very high throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse fast fourier transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.

[0059] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in

802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment,

802.1 lah may support meter type control/machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0060] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.1 In, 802.1 lac, 802.11af, and 802.1 lah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.1 lah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0061] In the United States, the available frequency bands, which may be used by 802.1 lah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 lah is 6 MHz to 26 MHz depending on the country code.

[0062] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0063] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).

[0064] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

[0065] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.

[0066] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0067] The CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0068] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and/or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

[0069] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP -based, non-IP based, Ethernet-based, and the like.

[0070] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, e.g., to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0071] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0072] In view of FIGs. 1 A-1D, and the corresponding description of FIGs. 1 A-1D, one or more, or all, of the functions described herein with regard to any of WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

[0073] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.

[0074] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.

[0075] The following abbreviations and acronyms may be used for the following terms:

ADU Application Data Unit

AR Augmented Reality

AS Access stratum

BWP Bandwidth Part

CE Control Element

CG Configured grant CSI Channel State Information

DCI Downlink Control Information

DG Dynamic Grant

DL Downlink

DRB Data Radio Bearer

DSR Delay Status Report

HARQ Hybrid Automatic Repeat Request HMD Head Mounted Displays

LCH Logical Channel

LCP Logical control prioritization

MAC Medium Access Control

MCS Modulation and Coding Scheme

MR Mixed Reality

NDI New Data Indicator

PDB Packet Delay Budget

PDU Protocol Data Unit

PSDB PDU Set Delay Budget

PSER PDU Set Error Rate

PSI PDU Set Importance

PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel

QoE Quality of Experience

QoS Quality of Service

RBG Resource Block Group

RLC Radio link control

RRC Radio Resource Control

RV Redundancy Version

SDAP Service data adaptation protocol

SDU Service Data Unit

SLIV Start and Length Indicator value

SR Scheduling Request

SRB Signaling Radio Bearer

TB Transport Block

TDD Time Division Duplex

TPD Traffic Processing Delays TRP Transmission / Reception Point

TTL Time to Live

UCI Uplink Control Information

UL Uplink

UTO Unused Transmission Occasion

VR Virtual Reality Repeat reQuest

XR extended Reality

[0076] Introduction

[0077] As used herein, “extended Reality (XR)” may be used as a broad umbrella term which may include all real-and-virtual combined environments and/or human-machine interactions generated by computer technology and/or wearables. For example, XR may be used interchangeably with Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), and interpolations and/or combinations thereof.

[0078] For example, VR may refer to environments where a rendered version of a visual and audio scene, such as scenes delivered to a WTRU. A rendering may be designed to mimic the visual (e.g., stereoscopic 3D) and/or audio sensory stimuli of the real world (e.g., as naturally as possible) to an observer or user as they move, such as within the limits defined by an application executed by a WTRU.

[0079] For example, AR may refer to environments where a user is provided with additional information and/or artificially generated objects, items, and/or content which may be overlaid upon their current environment.

[0080] For example, MR may refer to an advanced form of AR where some virtual elements are inserted into a physical scene, such as with the intent to provide the illusion that these elements are part of the real scene and/or environment.

[0081] For example, the notion of immersion in the context of XR applications and/or services may refer to a user’ s sense of being surrounded by the virtual environment. A user may be provided with the feeling of being physically and/or spatially located in a virtual environment. For example, the levels of virtuality may range from partial sensory inputs to fully immersive multi-sensory inputs leading to a virtual reality practically indiscernible from actual reality.

[0082] In certain representative embodiments, a WTRU 102 may refer to any XR device and/or node. XR devices and/or nodes may come in a variety of form factors. For example, a WTRU 102 (e.g., XR WTRU) may include, but is not limited to the following: Head Mounted Displays (HMD), optical see-through glasses and camera see-through HMDs (e.g., for AR and MR), mobile devices with positional tracking and camera, wearables, haptic gloves, haptic body suits, haptic shoes, etc. In addition to the above, several different types of XR WTRUs may be envisioned based on XR device functions (e.g., as display, camera, sensors, sensor processing, wireless connectivity, XR/Media processing and power supply) to be provided by one or more devices, wearables, actuators, controllers and/or accessories. One or more devices, nodes, and/or WTRUs may be grouped into a collaborative XR group for supporting any of XR applications, experience, and/or services.

[0083] For example, in XR services and applications, traffic (e.g., wireless traffic) may comprise first data units (e.g., data such as PDUs) which may be associated with second date units (e.g., an Application Data Unit (ADU), PDU set, and/or data burst). For example, one or more PDUs belonging to a PDU set may be associated with different segments and/or components of a video frame or a video slice. For example, a data burst may comprise one or more PDU sets. For example, a number of PDUs in an PDU set or data burst of a total payload size (e.g., units of bits/bytes) transmitted in the UL and/or received in the DL may be dependent on a type of media frame (e.g. 3D video frame, audio frame).

[0084] In certain representative embodiments, a WTRU 102 may perform transmissions/receptions of XR traffic in uplink and downlink. For example, different traffic processing delays (e.g. at the WTRU 102 and at the network side) may occur, such as at different layers of the protocol stack. XR traffic may be characterized by variable load size carrying a set of PDUs (e.g., a PDU Set) which may have varying requirement in terms of PDU Set reliability, PDU Set delay bound, etc. The notion of Quality of Experience (QoE) for XR has yet to be adopted by the 3 GPP to its full extent. For example, QoE may depend implicitly on the Quality of Service (QoS), and in current 3 GPP systems, there are several descriptors related to aspects such as QoS flow ID in the headers or depending on the mapping of the PDU set to a particular DRB.

[0085] In certain representative embodiments, procedures to manage XR transmissions, such as lower layer (e.g., MAC and/or PHY) procedures, may be based on traffic processing delays (TPD) and QoE-related measurements.

[0086] In certain representative embodiments, procedures may use information related to and/or associated with any of TPD and/or QoE, which may be available at the WTRU 102 (e.g., which is not available at the network side). Indications, based on the available information, may be sent to the NETWORK 113, 115 for efficient handling of XR traffic, such as by lower layer (e.g., MAC and/or PHY) mechanisms.

[0087] In certain representative embodiments, the information available at the WTRU 102 may include any of processing time, application consumption and/or transmission time, DL and UL correlation, transmission configuration, transmission occasions, buffer level, and/or remaining time. For example, the information available at the WTRU 102 may be obtained based on measurements (e.g., by the WTRU 102). [0088] In certain representative embodiments, the processing time of XR data (e.g., PDUs/PDU sets/data bursts) may be associated with any of, but not limited to compression, concatenation, segmentation, security and/or integrity protection, and/or multiplexing. For example, a measurement of processing time may refer to the time taken to process a unit of XR data, such as measured from entering until leaving one or more applications and/or AS layers. The processing time may be specified as a minimum or maximum requirement, such as X seconds.

[0089] In certain representative embodiments, the application consumption time and/or application transmission time may be variable. This time may be dependent on the encoding and/or decoding employed and as such may be device specific. The application consumption and/or transmission time may refer to the time taken for the XR application to transmit or to receive XR data to/from the layers below the application layer. The application consumption and/or transmission time may be specified as minimum or maximum requirement, such as X seconds.

[0090] In certain representative embodiments, a correlation may be made between DL and UL XR traffic and/or between flows in either the UL or DL direction. For example, the correlation may refer to a time dependency of the XR traffic in the DL and the XR traffic in the UL. In case UL and DL traffics are not correlated, a WTRU 102 may transmit (e.g., in the UL) without prerequisites for receiving DL data. In cases where UL and DL traffics are correlated, a WTRU 102 may (e.g., need to) wait X seconds after receiving a PDU set in the DL before transmitting a PDU set in the UL. Estimation of correlation at the Network side may be challenging, such as due to the potential large number of WTRUs. For example, a correlation (e.g., Corr) equal to 0, may indicate no dependency between the UL and DL XR transmission, whereas a correlation greater than 0 may indicate that there should be a certain time dependency between transmitting in the UL and receiving in the DL.

[0091] In certain representative embodiments, a WTRU may obtain information associated with a (e.g., UL) transmission configuration, such as a multi-PUSCH CG. For example, a multi- PUSCH CG may refer to a transmission configuration in the UL which may include one or more CG periods. A single CG period may include multiple DL and UL slots. A DL and UL slot configuration (or pattern) may or may not be consecutive (e.g., in time). For example, a single UL slot may carry one or more PUSCH occasions. A transmission occasion (TO) of the multiple PUSCHs in a slot may occupy consecutive (or non-consecutive) symbols.

[0092] In certain representative embodiments, a WTRU may obtain information associated with Unused Transmission Occasions (UTOs). For example, UTOs may be UL transmission occasions that have been allocated to the WTRU 102 (e.g., in a multi-PUSCH CG). A WTRU may not have XR traffic to transmit in certain transmission occasions, the WTRU may signal UTOs to the NETWORK 113, 115 which may reuse them for other WTRUs being served. [0093] In certain representative embodiments, a WTRU may obtain buffer information. For example, a buffer level threshold may be used, such as buffer level threshold based RVQoE (RAN Visible QoE) reporting. This reporting may carry QoE information describing a perceptual quality of a service by a user, and may be relevant for modifying, changing, and/or adapting MAC procedures.

[0094] In certain representative embodiments, a WTRU may obtain other time related information. For example, a WTRU may determine a remaining time. Remaining time may refer to the time remaining (e.g., expressed in X ms) for receiving the last PDUs of a PDU set before exceeding a PDU set delay budget (PSDB).

[0095] Overview

[0096] In certain representative embodiments, a WTRU may perform transmission of a TB from a PDU set based on importance information and/or priority information. For example, a TB from a PDU set may be transmitted with a higher importance and/or priority.

[0097] For example, a WTRU may receive (e.g., from an application) a first PDU set that is associated with PDU set importance information (e.g., importance ‘X’). The WTRU may receive (e.g., from a network entity) a first set of UL DG resources (e.g., in DCI) for transmission of a TB from the first PDU set. The WTRU may transmit one or more TBs from the first PDU set, such as by using one or more HARQ processes (e.g., HARQ_process_ID =1, 2 , etc.) and/or using the first set of UL DG resources. The WTRU may receive HARQ feedback (e.g., with NDI not toggled) that is associated with the one or more HARQ processes (e.g., IDs). The WTRU may receive (e.g., from the network entity) a second set of UL DG resources for retransmission of the one or more TBs from the first PDU set (e.g., associated with the HARQ processes). The WTRU may receive (e.g., from an application) a second PDU set associated with different PDU set importance information (e.g., importance ‘ Y’).

[0098] For example, the importance of the second PDU set (e.g., Y) may be greater than or higher than the importance of the first PDU set (e.g., X), and the WTRU may determine to transmit one or more TBs from the second PDU set using the second set of UL DG resources (e.g., which were made available for retransmission of the TBs from the first PDU set). For example, the WTRU may select one or more HARQ process IDs, from the set of HARQ processes intended for sending the TB from the first PDU set, for transmission of (e.g., any of) the TBs from the second PDU set. For example, the WTRU may transmit the TB from the second PDU using the selected HARQ process and information indicating (e.g., in UCI) that that this transmission is associated with new data.

[0099] In certain representative embodiments, a WTRU may send (e.g., report) information indicating a traffic processing delay and/or QoE related information. For example, traffic processing delay and/or QoE related information may be used for adjustment of a received resource set.

[0100] For example, a WTRU may receive (e.g., from a network entity) information indicating a first resource set. The first resource set may include any of a TDD configuration (e.g., number of UL and DL slots/resources in a time duration), a (e.g., dynamic or configured) grant, and/or a number of time/frequency resources (e.g., resource elements). For example, a WTRU may receive (e.g., from a network entity) information indicating one or more thresholds for when to report regarding adjustments of the resource set. For example, one threshold may be relevant for DL (e.g., Thresholdl) and one threshold may be relevant for UL (e.g., Threshold2). For example, a threshold may be provided for correlation between DL and UL (e.g., Thresholds). The WTRU may receive data in the DL and/or transmit data in the UL according to the received first resource set. The WTRU may perform measurements on the data received in the DL and/or transmitted in the UL, such as to determine that transmission of the DL traffic is very slow (e.g., DL processing time is above Thresholdl), transmitted UL traffic is very fast (e.g., UL processing time is below Threshold2), and/or a correlation between DL and UL (e.g., a ratio of the UL and DL processing times is below Thresholds).

[0101] For example, the WTRU may determine that one or more of the thresholds (and/or other criteria) are met, and may transmit measurements according to the configured criteria (e.g., via MAC CE).

[0102] For example, the WTRU may receive information indicating a second resource set. The second resource set may include any of a TDD configuration (e.g., number of UL and DL slots/resources in a time duration), a (e.g., dynamic or configured) grant, and/or a (e.g., different) number of time/frequency resources (e.g., resource elements).

[0103] Common Terminology

[0104] As described herein, the terms “network” and/or “network entity” may be used interchangeably to refer to any of a base station (e.g., gNB, TRP, RAN node, access node), a core network function (e.g., AMF, SMF, PCF, NEF), and/or an application function (e.g., edge server function, remote server function), for example.

[0105] As described herein, the terms “flow” and/or “flows” may be used to refer to any of QoS flows and/or data flows (e.g., a flow of data comprising one or more PDUs, PDU sets or data bursts), such as may be inter-dependent with one another and/or associated with one or more QoS requirements (e.g., latency, data rate, reliability, RTT latency). Different flows, possibly originating from a common application and/or experience source and/or intended to a common destination device (or WTRU 102) or group of associated devices (or WTRUs) may be referred to as associated flows or correlated flows. [0106] As described herein, the term “data unit” may be used to refer to any of one or more frames (e.g., media/video/audio frames or slices/ segments), PDUs, PDU sets, data bursts, or group thereof (e.g., frames, PDUs, PDU-sets, data bursts). For example, data units, which may be transmitted or received by the WTRU 102 sequentially (e.g. one after the other) or in parallel (e.g. over different channels/links/resources), may or may not be inter-dependent with each other.

[0107] As described herein, the term “QoE” may be used to refer to any of an application and/or higher layer metrics and/or measurements, such which may be directly and/or indirectly detectable and/or visible at the WTRU 102 and/or an application function. For example, QoE metrics and/or measurements may or may not be directly visible and/or detectable at a base station. QoE metrics and/or measurements may be determined and/or performed as a function of QoS metrics and/or parameters (e.g. latency, data rate, reliability, RTT/MTP latency)

[0108] As described herein, the term “forwarding configuration” may be used to refer to any of radio bearers (e.g. data radio bearers (DRBs) and/or signaling radio bearers (SRBs), logical channels (LCHs), logical channel groups (LCGs), configuration parameters (e.g., in the individual layer) within the AS protocol stack (e.g., SDAP, PDCP, RLC, MAC, PHY, other new protocol layers), a configuration to be applied for assigning COUNT/SNs (e.g., for PDUs, PDU sets and/or data bursts), parameters associated with logical channel prioritization (LCP) (e.g., priority, PBR, BSD), BWPs, carriers, radio links and/or interfaces (Uu links, sidelinks), and/or radio resources (e.g., a set of one or more frequency/time/spatial resources, such as symbols, slots, subcarriers, resource elements, and/or beams). For example, radio resources may be associated with or refer to configurated grants (CG), dynamic grants (DG) and/or any other resource grants or grant free resources.

[0109] As used herein, the term “PDU set delay budget” (PSDB) may refer to a time between reception of a first PDU (e.g., at the network in the UL direction) and the successful delivery of a last arrived PDU of a PDU Set (e.g., at the network in the UL direction).

[0110] As used herein, the term “PDU set integrated handling indication” (PSIHI) may refer to an indication as to whether all PDUs of a PDU Set are needed for the usage of PDU Set (e.g., by an application layer).

[OHl] As used herein, the term PDU set error rate (PSER) may refer to an upper bound for a rate of non-congestion related PDU set losses (e.g., between the RAN and the WTRU 102).

[0112] As used herein, the term “jitter” may refer to variations with respect to an expected time instance during which one or more data units may be received or transmitted. For example, for a set of data units that may be expected to be received periodically at different periodic time instances, jitter may refer to the variation with respect to the periodic time instances (e.g., for a data unit that may be received T1 ms in advance or T2 ms later than an expected time instance at T, the jitter range may be determined as T2 - Tl). Jitter may refer to an instantaneous value or a statistical value (e.g., average, variance, standard deviation, max/min).

[0113] As used herein, the term PDU set importance (PSI) may refer to an indication of an application/higher layer priority of the PDU set. For example, PSI may be defined as in 3GPP Release 18.

[0114] As used herein, the terms “remaining time” and “remaining delay” may be used refer to the time duration remaining for receiving or transmitting one or more PDUs of a PDU set before the PSDB. Remaining delay may also be referred to as a time to live (TTL) associated with a PDU set.

[0115] TB Transmission from a PDU Set With Higher Importance/Priority

[0116] In certain representative embodiments, a WTRU 102 may perform transmission of a TB from a PDU set with a higher importance and/or priority (e.g., instead of retransmission of a TB from a PDU set with a lower importance and/or priority).

[0117] In certain representative embodiments, a WTRU 102 may receive (e.g., from an XR application running on the WTRU 102, or an XR application running at a network XR server (e.g., at the RAN 113 or core network 115) with which the WTRU 102 may transmit and/or receive XR data) a burst of one or more PDUs organized in a first PDU set. The first PDU set may be associated with an importance of ‘X’ . For example, the importance and/or the association of PDUs within a PDU set may be defined as described above. For example, a PSI for the first PDU set may indicate a first importance level/value. The WTRU 102 may receive the first PDU set from an application (or higher layers), and the WTRU 102 (e.g., at the MAC layer) may associate the PDUs from the first PDU set with at least one TB that the WTRU 102 transmits (e.g., in the UL to the network 113, 115). For example, the WTRU 102 may transmit a scheduling request (SR) and/or a buffer status report (BSR) to the network 113, 115, such as upon receiving the PDUs of the first PDU set from the application/higher layers. The WTRU 102 may receive, from the RAN 113, information indicating a set of UL grant resources, such as time/frequency resources, and/or information indicating transmission parameters including any of BWP, MCS, and/or a set of HARQ processes (e.g., HARQ process IDs = n, n+1, n+2, . . .) that the WTRU 102 may use for the transmission of one or more TBs from the first PDU set.

[0118] The WTRU 102 may use the resources from the received UL grant to transmit the TBs from the first PDU set, such as using the HARQ process information. For example, if the transmission is not successful, the WTRU 102 may retransmit a subset or all of the TBs from the first PDU set.

[0119] The WTRU 102 may, receive from the RAN 113, HARQ feedback information associated with the transmitted TBs from the first PDU set. For example, the HARQ feedback may include information indicating any of the following: (1) a set HARQ processes (e.g., HARQ process IDs) associated with the feedback, (2) a state of NDI flags (e.g., toggled/not toggled) associated with the feedback, and/or (3) transmission parameters to apply when retransmitting the TB. For example, where a NDI flag for a HARQ process is not toggled, the WTRU 102 may assume a NACK and/or that the RAN 113 expects a retransmission of the TB from the first PDU set. For example, where the NDI flag for a HARQ process is toggled, the WTRU 102 may assume an ACK and/or successful transmission of the TB from the first PDU set. The WTRU 102 may assume a HARQ process ID for a TB (with a NDI toggled) is released and is available for other transmissions (e.g., of a new TB). For example, the transmission parameters to apply for TB retransmission may include any of UL grant resources (e.g., time/frequency resources), MCS, redundancy version (RV) associated with the TB, and/or an (e.g., K2) offset value (e.g., of the slot of the UL grant resource).

[0120] The WTRU 102 may receive the HARQ feedback information as part of DCI. For example, a DCI format the DCI may include, but is not limited to, DCI formats 0-0 and 0-1.

[0121] In certain representative embodiments, the WTRU 102 may receive one or more PDUs of a second PDU set with an importance ‘Y’ . For example, the importance and/or the association of PDUs within a PDU set may be defined as described above. For example, a PSI for the second PDU set may indicate a second importance level/value. One or more PDUs of the second PDU set may be received prior to performing the retransmission of the TB from the first PDU set with importance X. The WTRU 102 may perform an importance comparison between the TB from the second PDU set and the TB from the first PDU set to be retransmitted.

[0122] In certain representative embodiments, the WTRU 102 may perform a comparison associated with the properties of the first and the second PDU set. For example, the properties may include one or more static properties, one or more dynamic properties, or a combination thereof.

[0123] For example, static properties of a PDU set may include, but are not limited to, PDU set importance, PSDB, payload size, and/or PDU set version. For example, a WTRU 102 may check the PDU set importance (PSI) of the first PDU set and of the second PDU set and determine an outcome (e.g., as described herein) based thereon. For example, a WTRU 102 may perform a check based on PSDB (e.g., as a fixed time duration/window) for which the PDUs of the PDU set are expected to be transmitted/received. For example, a WTRU 102 may perform a check based on payload size, where the PDU set with a higher value for the payload size may have higher priority to be transmitted as compared to the PDU set with a lower value for the payload size. For example, a WTRU 102 may perform a check based on PDU set version, where a PDU set of a more recent (or later) version (e.g., indicated by a version ID or timestamp) may be transmitted with a higher priority compared to an ongoing PDU set of an older (or earlier) version.

[0124] For example, dynamic properties may include, but are not limited to, remaining time and/or arrival time. For example, the remaining time may be defined as described above. For example, a WTRU 102 may check the remaining time of the first PDU set and of the second PDU set and determine an outcome (e.g., as described herein) based thereon. For example, the arrival time may correspond to a time within a window predefined by a set of parameters (e.g., start/end time, duration). For example, the WTRU 102 may check the arrival time for the PDUs of PDU set A and PDU set B (e.g., the arrival time of Nth PDU of PDU set A vs. arrival time of Nth PDU of PDU set B), and determine an outcome (e.g., as described herein) based thereon.

[0125] For example, the WTRU 102 may compare a combination of the static and/or dynamic properties as listed above and determine an outcome based thereon.

[0126] For example, a result of the comparison of PDU set properties may be that the TB from the second PDU set (Y) is to be transmitted prior to the retransmission of the TB from the first PDU set (X). Another result of the comparison may be that the TB from the second PDU set (Y) is to be transmitted with a lower or with the same priority as the retransmission TB from the first PDU set (X). For example, the comparison may indicate that the TB from the second PDU set (Y) to be transmitted prior to the retransmission of the TB from the first PDU set (X) (e.g., at the MAC layer of the WTRU 102) when the TB from the second PDU set has a higher transmission priority than the TB from the first PDU set. Hence, the TB from the second PDU set may be pre-empted before retransmitting the TB from the first PDU set. For example, the comparison may indicate that the TB from the second PDU set (Y) is to be transmitted with a lower or with the same priority as the retransmission TB from the first PDU set (X) (e.g., at the MAC layer of the WTRU 102) when the TB from the second PDU set has a lower or equal priority to the TB from the first PDU set.

[0127] In certain representative embodiments, the comparison of the PDU set properties may be that the TB from the second PDU set (Y) is to be transmitted prior to the retransmission of the TB from the first PDU set (X). In such cases, the WTRU 102 may determine to transmit the TB from the second PDU set using the resources received from the RAN 113 for the (e.g., retransmission of the) TB from the first PDU set. To achieve this, the WTRU 102 may perform any of the following. The WTRU 102 may select the HARQ process associated with the retransmission of the TB from the first PDU set. The WTRU 102 may use the selected HARQ process intended for sending the TB from the first PDU set for the transmission of the TB from the second PDU set. The WTRU 102 may transmit the TB using the selected HARQ process. The WTRU 102 may send information (e.g., implicit or explicit indication) indicating that the transmitted TB is associated with new data. For example, an indication may contain any of the following: a HARQ process ID associated with TB/new data, a state of the NDI flag associated with the HARQ process (e.g., toggled or not toggled), RV of the TB/new data, and/or resource information (e.g., SLIV and RBGs associated with the TB/new data). For example, the indication may be sent in PUCCH (e g., UCI), and/or PUSCH (e.g, UCI, MAC CE).

[0128] In certain representative embodiments, the comparison of the PDU set properties may be that the TB from the second PDU set (Y) is to be transmitted with a lower or with the same priority as the retransmission TB from the first PDU set (X). In such cases, the WTRU 102 may decide to retransmit as per legacy procedures or to perform additional checks related to the comparison of the PDU sets associated to the TBs. Based on the comparison of the PDU set properties, the WTRU 102 may perform any of the following embodiments.

[0129] In certain representative embodiments, a WTRU 102 may perform transmission of the TB from a PDU set with higher priority and the WTRU 102 discards the TB from the PDU set with a lower importance. For example, the TB from the second PDU set with higher importance (e.g., as determined from the comparison above) may be transmitted on a resource grant received for a retransmission of the TB from the first PDU set with lower importance using the same HARQ process. The TB from the first PDU set with the lower importance may be discarded prior to the transmission of the TB from a second PDU set with higher importance. For example, any (e.g, all) states and/or buffers related to the HARQ process may be cleared and/or reset as the HARQ process may be used to transmit new data. For example, the WTRU 102 may send, to the network, information indicating or stating that the retransmission of the TB from the first PDU set is discarded at the WTRU 102.

[0130] In certain representative embodiments, a WTRU 102 may perform transmission of the TB from a PDU set with higher priority and the WTRU 102 may attempt to transmit the TB from the PDU set with a lower importance. For example, the TB from the second PDU set with higher importance may have priority to be transmitted beforehand. However, the WTRU 102 may evaluate whether the received UL grant resources may be suited to transmit the TB from the second PDU set and to perform retransmission of the TB from the first PDU set. The WTRU 102 may use two HARQ processes to achieve this. For example, the WTRU 102 may send, to the network, information indicating that the TB from the second PDU set is transmitted and the TB from the first PDU set is transmitted, such as by indicating information for the two HARQ processes (e.g, HARQ process IDs) associated with the transmission of both TBs.

[0131] For example, the WTRU 102 may transmit all or a subset of the TBs from one or more of the PDU sets with higher importance and, after completing the transmissions, the WTRU 102 may additionally send information indicating (e.g, SR and/or BSR) a request for resources for the TBs from the PDU sets with lower priority. Such an indication may be transmitted if the WTRU 102 evaluates that the TBs from the PDU sets with lower priority have not been sufficiently delayed (e.g., according to a timer value) such that transmission of the PDU sets with lower priority becomes unnecessary.

[0132] In certain representative embodiments, the WTRU 102 may send, to the network, information indicating to suspend the HARQ process associated with the retransmission of the TB from the PDU set with lower importance (e.g., as defined by the comparison of properties of PDU sets). For example, the WTRU 102 may (e.g., also) send information indicating the WTRU 102 will use a new HARQ process (e.g., with a different ID compared to the HARQ process associated with retransmission of the TB) to transmit the TB from the PDU set with higher importance. Such indications may be sent (e.g., in UCI) before and/or during the transmission of the TB from the PDU set with higher importance. In an example, the WTRU 102 may send in an indication to suspend the HARQ process used for retransmission and information on the duration or time interval of the suspension (e.g., in units of symbols, slots, ms or other transmission time intervals). The WTRU 102 may resume retransmission of the TB from the PDU set with lower importance using the suspended HARQ process, such as upon transmitting the TB from the PDU set with higher importance.

[0133] In certain representative embodiments, a WTRU 102 may receive (e.g., from an application) a first PDU set that is associated with PDU set importance information (e.g., importance ‘X’). The WTRU may receive (e.g., from a network entity) a first set of UL DG resources (e.g., in DCI) for transmission of a TB from the first PDU set. The WTRU may transmit one or more TBs from the first PDU set, such as by using one or more HARQ processes (e.g., HARQ_process_ID =1, 2 , etc.) and/or using the first set of UL DG resources. The WTRU may receive HARQ feedback (e.g., with NDI not toggled) that is associated with the one or more HARQ processes (e.g., IDs). The WTRU may receive (e.g., from the network entity) a second set of UL DG resources for retransmission of the one or more TBs from the first PDU set (e.g., associated with the HARQ processes). The WTRU may receive (e.g., from an application) a second PDU set associated with different PDU set importance information (e.g., importance ‘ Y’). [0134] For example, the importance of the second PDU set (e.g., Y) may be determined to be greater than or higher than the importance of the first PDU set (e.g., X). The WTRU may determine to transmit one or more TBs from the second PDU set using the second set of UL DG resources (e.g., which were made or are available for retransmission of the TBs from the first PDU set) based on the importance information. For example, the WTRU may select one or more HARQ process IDs, from the set of HARQ processes intended for sending the TB from the first PDU set, for transmission of (e.g., any of) the TBs from the second PDU set. For example, the WTRU may transmit the TB from the second PDU using the selected HARQ process and information indicating (e.g., in UCI) that that this transmission is associated with new data.

[0135] Reporting Traffic Processing Delay and/or QoE Related Information for Adjustment of Resources

[0136] In certain representative embodiments, a WTRU 102 may perform reporting of traffic processing delay and/or QoE related information relevant for network-based adjustment of a resource set received by the WTRU 102.

[0137] In certain representative embodiments, a WTRU 102 may receive, from a network entity, configuration information indicating a first resource set. For example, the first resource set may include or be associated with any of a TDD configuration and/or dynamic/configured grant resources. A TDD configuration may include information indicating a DL and/or UL slot pattern used by the WTRU 102 and the network for the DL/UL transmissions of XR data. Dynamic/configured grant resources may include any of time/frequency resources, BWP, MCS, and/or periodicity, among others. The WTRU 102 may receive, from the network entity, information indicating a set of threshold values associated with reporting of traffic processing delays and QoE related parameters as described herein. Examples of thresholds include thresholds for UL measurement, thresholds for DL measurement, thresholds for correlation between UL and DL transmissions.

[0138] For example, a threshold may be associated with or relevant for UL measurements. Examples of UL measurement definitions include: (1) a processing time of the transmitted XR data should be less than X ms; (2) a processing time of the transmitted XR data should be kept within a specified interval [Xmin, Xmax]; (3) an application transmission time of the XR data should be less than X ms; (4) an application transmission time of the XR data should be kept within specified interval [Xmin, Xmax]; (5) a number of Unused Transmission Occasions is above N; (6) a number of Unused Transmission Occasions should be kept within specified interval [Nmin, Nmax]; (7) elements of the RAN Visible QoE reporting, such as experiencing initial buffering, or rebuffering while rendering the service, and/or the user video quality metric is below/above and/or within an interval (e.g., a predefined Mean Opinion Score interval); (8) a remaining time for transmission of the PDU set should be less than X ms; and/or (9) a remaining time for transmission of the PDU set should be kept within specified interval [Xmin, Xmax],

[0139] For example, a threshold may be associated with or relevant for DL measurements. Examples of DL measurement definitions include: (1) a processing time of the received XR data should be less than X ms; (2) a processing time of the received XR data should be kept within specified interval [Xmin, Xmax]; (3) an application decoding/rendering time of the XR data should be less than X ms; (4) an application decoding/rendering time of the XR data should be kept within specified interval [Xmin, Xmax]; (5) elements of the RAN Visible QoE reporting such as a user is experiencing initial buffering, or rebuffering while rendering the service, and/or the user video quality metric is below/above and/or within an interval (e.g., predefined Mean Opinion Score interval); (6) a remaining time for reception of the PDU set should be less than X ms; and/or (7) a remaining time for reception of the PDU set should be kept within specified interval [Xmin, Xmax],

[0140] For example, a threshold may be associated with or relevant for correlation between UL and DL transmissions. Examples for thresholds relevant for correlation include: (1) wait X ms after receiving a PDU set in the DL before transmitting a PDU set in the UL due to time correlation of the DL and UL PDU sets; (2) no correlation between UL and DL PDU sets; and/or (3) a minimum time difference between two events associated with UL and DL transmissions (e.g., a time between the transmission of a PDU set in UL and the reception of a dependent PDU set in DL). Two events may be considered as correlated between one another when they occur within a correlation time window. When the two events occur at time instances beyond the correlation time window, they may be considered as independent.

[0141] The WTRU 102 may receive and transmit data in both DL and UL according to the first received resource set. The WTRU 102 may (e.g., start to) perform measurements on data for both DL and UL. In addition, the WTRU 102 may compare the measurements with the configured thresholds. The comparison of result in the criteria defined for the thresholds not being met, or the criteria defined for the thresholds being met.

[0142] In cases where the criteria are not met, the WTRU 102 may continue to perform DL and/or UL transmissions according to the first received resource set.

[0143] In cases where the criteria are met, the WTRU 102 transmit (e.g., report) the measurements according to the configured criteria to the network, and/or transmit an indication requesting a change of the first resource set.

[0144] For example, the measurements may be sent (e.g., reported) by the WTRU 102 in any of the following methods. The WTRU 102 may send a report periodically (e.g., using one or more configured periodicity values). The WTRU 102 may send a report aperiodically (e.g., when detecting triggering events/conditions described by the criteria/thresholds above or as an update indication when detecting a change in a measurement sent previously). The WTRU 102 may send a report in a semi-persistent manner (e.g., sent periodically with a periodicity value or in a burst manner over a predefined time window or duration).

[0145] For example, the WTRU 102 may switch between a first periodicity value and a second periodicity value for sending the measurements, such as based on a type of event detected (e.g., a change in the type of PDU set to be transmitted in UL, and/or a remaining delay for a PDU set is less than a threshold value). In another example, the WTRU 102 may change between methods used for sending measurements. The WTRU 102 may switch between reporting periodically and aperiodically, such as based on whether any change and/or amount of change is determined in the measurements to be reported.

[0146] For example, the WTRU 102 may report the measurements to network via any of the following message types: (1) RRC signalling and/or messages (e.g., via SRBO, SRB1, SRB2, SRB3, SRB4); (2) control PDUs associated with any of the AS layers (e.g., SDAP control PDU, PDCP control PDU, RLC control PDU); (3) UL MAC CE (e.g, new MAC CE, BSR, delay status report (DSR)); (4) PUSCH UCI (e.g., single bit SR, multi-bit SR, HARQ feedback, CSI report); (5) PUSCH UCI (e.g, UTO-UCI, CG-UCI, new UCI); and/or (6) non-AS (NAS) layer signalling (e.g, PDU session related messages).

[0147] In certain representative embodiments, the WTRU 102 may receive information indicating a second resource set. For example, the second resource set may include or be associated with any of a TDD configuration and/or dynamic/configured grant resources. A TDD configuration may include information indicating a DL and/or UL slot pattern used by the WTRU 102 and the network for the DL/UL transmissions of XR data. Dynamic/configured grant resources may include any of time/frequency resources, BWP, MCS, and/or periodicity, among others.

[0148] In certain representative embodiments, the network may change (e.g, periodically adjust) one or more thresholds, a type(s) of traffic processing delay measurements, and/or QoE related measurements a WTRU 102 is (e.g, needed) to perform.

[0149] In certain representative embodiments, the network may change (e.g, periodically adjust) the configuration of one or more thresholds and/or may indicate a subset of parameters for reporting such that the network obtains information relevant for changing the resource set (e.g, for XR traffic) sent to a WTRU 102.

[0150] In certain representative embodiments, a WTRU may receive (e.g, from a network entity) information indicating a first resource set. The first resource set may include any of a TDD configuration (e.g, number of UL and DL slots/resources in a time duration), a (e.g, dynamic or configured) grant, and/or a first number of time/frequency resources (e.g, resource elements). For example, a WTRU may receive (e.g, from a network entity) information indicating one or more thresholds for when to report regarding adjustments of the resource set. For example, one threshold may be relevant for DL (e.g. Threshold 1) and one threshold may be relevant for UL (e.g, Threshold2). For example, a threshold may be provided for correlation between DL and UL (e.g. Thresholds). The WTRU may receive data in the DL and/or transmit data in the UL according to the received first resource set. The WTRU may perform measurements on the data received in the DL and/or transmitted in the UL, such as to determine that delivered DL traffic is very slow (e.g., DL processing time is above Thresholdl), transmitted UL traffic is very fast (e.g., UL processing time is below Threshold2), and/or a correlation between DL and UL (e.g., a ratio of the UL and DL processing times is below Thresholds).

[0151] For example, the WTRU may determine that one or more of the thresholds (and/or other criteria) are met, and may transmit measurements according to the configured criteria (e.g., via MAC CE).

[0152] For example, the WTRU may receive information indicating a second resource set. The second resource set may include any of a TDD configuration (e.g., number of UL and DL slots/resources in a time duration), a (e.g., dynamic or configured) grant, and/or a (e.g., different) second number of time/frequency resources (e.g., resource elements).

[0153] FIG. 2 is a flow diagram illustrating an example communications sequence for transport block (TB) transmission of a protocol data unit (PDU) set based on importance and/or priority. As shown in FIG. 2, an application (APP) 202, such as an XR application, may reside at (e.g., be executed by) a WTRU 102 (e.g., a XR WTRU). The application may generate a plurality of PDU sets with different importance and/or priority levels which are to be transmitted by the WTRU to the network 204 (e.g., a gNB 180). For example, the application 202 at the WTRU 102 may generate a PDU set ‘A’ with importance information of ‘X’ at 206. The WTRU 102 may receive information indicating a UL DG ‘ 1’ in DCI (e.g., upon sending a SR) for the transmission of the PDU set A at 208. The WTRU 102 may send a TB from the PDU set A using a HARQ process with ID=2 at 210. In the HARQ feedback, the WTRU 102 may receive information indicating a UL DG ‘2’ with a NDI flag indicating that the WTRU 102 needs to retransmit the TB from the PDU set A (e.g., the NDI flag not toggled) at 212. A PDU set ‘B’ with importance information of ‘ Y’ may arrive at (e.g., be generated at that time instance the by) the WTRU at 216. The WTRU 102 may determine that the importance level of the PDU set B has a higher importance compared to the importance level of the PDU set A at 218. The WTRU may use the HARQ process intended for the retransmission to send a new transmission (e.g., TB) from the PDU set B at 220. For example, the WTRU may transmit the TB from PDU set B and information indicating the transmission (e.g., of the TB from PDU set B) is for new data at 222.

[0154] FIG. 3 is a flow diagram illustrating an example communications sequence for reporting traffic processing delay and/or Quality of Experience (QoE) related information. As shown in FIG. 2, an application (APP) 202, such as an XR application, may reside at (e.g., be executed by) a WTRU 102 (e.g., XR WTRU) and the WTRU 102 may communicate with a network 204. For example, the WTRU 102 may receive information indicating a first resource set and/or information indicating a reporting threshold configuration related to processing time at 302. For example, the reporting threshold configuration may include that a DL processing time should be less than X[DL] ms, and/or a UL processing time should be less than X[UL] ms. The WTRU 102 may perform transmission both in the UL and the DL direction (e.g., of PDU sets for the XR application). In the DL, a PDU set ‘A’ may delivered to the application at 304. The same application may generate a PDU set ‘B’ for transmission to the network at 306. The WTRU 102 may perform one or more measurements of processing time (e.g., for DL and UL transmissions) at 308. For example, the WTRU 102 may measure that the processing time in the DL is Y ms, where Y > X[DL] time, and/or that the processing time in the UL is Z ms, where Z < X[UL] ms. At 310, the WTRU 102 may compare the processing time in the DL and the processing time the UL with respect to the reporting thresholds at 310. At 312, the WTRU 102 may determine reporting information based on the reporting criteria (e.g., the processing times and/or correlation thereof satisfy the reporting thresholds). After determining the reporting criteria is satisfied, the WTRU 102 may report to the network 204 that the reporting criteria is satisfied (e.g., the DL processing time is above the associated threshold), and/or transmit to the network information indicating adjustment of the first resource set at 314.

[0155] In certain representative embodiments, a WTRU 102 may be configured to implement a procedure for reporting traffic processing delay and/or QoE related information. For example, a WTRU 102 may include a processor, a memory, and a transceiver which are configured to implement the procedure. The WTRU 102 may receive information indicating threshold information associated with a first set of resources. The WTRU 102 may send and/or receive TBs for one or more PDU sets using the first set of resources. The WTRU 102 may perform one or more measurements on the sending and/or the receiving of the one or more PDU sets. The WTRU 102 may send reporting information associated with the one or more measurements based on the one or more measurements satisfying at least a portion of the threshold information.

[0156] FIG. 4 is a procedural diagram illustrating an example procedure for TB transmission of PDU sets. For example, the procedure in FIG. 4 may be implemented by a WTRU 102 (e.g., a XR WTRU). At 402, the WTRU 102 may send, using a first set of resources, information indicating one or more TBs of a first PDU set associated with first HARQ information. For example, the first set of resources may be provided as a configured grant. For example, the first set of resources may be provided as a dynamic grant. The WTRU 102 may receive HARQ feedback information associated with the first HARQ information indicating retransmission of the one or more TBs of the first PDU set at 404. For example, the HARQ feedback may be received in DCI and/or may include a NDI as described herein. At 406, the WTRU 102 may receive information indicating a second set of granted resources (e.g., a configured or dynamic grant) associated with the retransmission of the one or more TBs of the first PDU set. At 408, the WTRU 102 may send, using the second set of granted resources, one or more TBs of a second PDU set. For example, the TBs of the second PDU set may be (e.g., indicated to be) associated with the first HARQ information based on an importance and/or priority information, such as where the importance of the second PDU set is higher than an importance of the first PDU set.

[0157] FIG. 5 is a procedural diagram illustrating an example procedure for reporting traffic processing delay and/or QoE related information. For example, the procedure in FIG. 5 may be implemented by a WTRU 102 (e.g., a XR WTRU). At 502, the WTRU 102 may receive (e.g., via MAC CE) information indicating threshold information associated with a first set of resources. For example, the threshold information may include any of thresholds for PDU set transmission in the UL, DL, or combinations thereof. At 504, the WTRU 102 may send and/or receive TBs for one or more PDU sets using the first set of resources. At 506, the WTRU 102 may perform one or more measurements on the sending and/or the receiving of the one or more PDU sets. At 508, the WTRU 102 may send reporting information associated with the one or more measurements based on the one or more measurements satisfying at least a portion of the threshold information. Examples of measurements satisfying (e.g., exceeding) a threshold are described above.

[0158] FIG. 6 is a procedural diagram illustrating another example procedure for TB transmission of PDU sets. For example, the procedure in FIG. 5 may be implemented by a WTRU 102 (e.g., a XR WTRU). At 602, the WTRU 102 may send, using a first set of resources, one or more TBs of a first PDU set which are associated with first HARQ information. At 604, the WTRU 102 may receive HARQ feedback information, associated with the first HARQ information, indicating retransmission of at least one TB of the first PDU set. At 606, the WTRU 102 may receive information indicating a second set of resources associated with the retransmission of the at least one TB of the first PDU set. At 608, the WTRU 102 may send, using the second set of resources, one or more TBs of a second PDU set which are associated with the first HARQ information based on an importance of the second PDU set being higher than an importance of the first PDU set.

[0159] For example, the WTRU 102 may receive information indicating the first set of resources via first downlink control information.

[0160] For example, the WTRU 012 may receive the HARQ feedback information and the information indicating the second set of resources via second downlink control information.

[0161] For example, the first HARQ information may include one or more HARQ process identifiers associated with the one or more TBs of the first PDU set.

[0162] For example, the HARQ feedback information may include (i) at least one HARQ process identifier associated with at least one TB of the first PDU set, and (ii) at least one new data indicator, associated with the least one HARQ process identifier, which is not toggled. [0163] For example, the WTRU 102 may send information indicating that the one or more TBs of the second PDU set are associated with new data.

[0164] For example, the WTRU 102 may select one or more HARQ process identifiers from the first HARQ information associated with the one or more TBs of the first PDU set. The WTRU 102 may send the one or more TBs of the second PDU set which are associated with the selected one or more HARQ process identifiers.

[0165] For example, the information indicating that the one or more TBs of the second PDU set are associated with new data may be sent via uplink control information.

[0166] For example, the first PDU set and the second PDU set may be generated by an application at (e.g., executed by) the WTRU 102.

[0167] For example, the WTRU 102 may determine the importance of the first PDU set and/or the importance of the second PDU set based on any of a static property and/or a dynamic property associated with the first PDU set and/or the second PDU set.

[0168] FIG. 7 is a procedural diagram illustrating another example procedure for reporting traffic processing delay and/or QoE related information. For example, the procedure in FIG. 5 may be implemented by a WTRU 102 (e.g., a XR WTRU). At 702, the WTRU 102 may receive information indicating threshold information associated with a first set of resources. At 704, the WTRU 102 may communicate (e.g., send and/or receive) TBs for one or more PDU sets using the first set of resources. At 706, the WTRU 102 may perform one or more measurements on the communication of the one or more PDU sets. At 708, the WTRU 102 may send reporting information associated with the one or more measurements based on the one or more measurements satisfying at least a portion (e.g., a first, second, and/or third threshold) of the threshold information.

[0169] For example, the WTRU 102 may communicate the TBs for the one or more PDU sets using the first set of resources which includes to send the TBs for the one or more PDU sets using the first set of resources.

[0170] For example, the WTRU 102 may communicate the TBs for the one or more PDU sets using the first set of resources which includes to receive the TBs for the one or more PDU sets using the first set of resources.

[0171] For example, the WTRU 102 may, after sending the reporting information, receive information indicating a second set of resources. The WTRU 102 may communicate (e.g., send and/or receive) TBs for (e.g., other) PDU sets using the second set of resources.

[0172] For example, the threshold information may include a first threshold. The WTRU 102 may compare measurement information associated with the one or more PDU sets sent using the first set of resources and the first threshold. [0173] For example, the threshold information may include a second threshold. The WTRU 102 may compare measurement information associated with the one or more PDU sets received using the first set of resources and the first threshold.

[0174] For example, the threshold information may include a third threshold. The WTRU 102 may compare a correlation of measurement information associated with the one or more PDU sets sent using the first set of resources and the one or more PDU sets received using the first set of resources with the third threshold.

[0175] For example, the one or more PDU sets may be associated with an application (e.g., executed) at the WTRU 102.

[0176] For example, the WTRU 102 may perform the one or more measurements on the communicating of the one or more PDU sets which includes to determine a processing time (e.g., as measurement information) associated with receiving of the one or more PDU sets.

[0177] For example, the WTRU 102 may perform the one or more measurements on the communicating of the one or more PDU sets which includes to determine a processing time (e.g., as the measurement information) associated with sending of the one or more PDU sets.

[0178] FIG. 8 is a procedural diagram illustrating another example procedure for TB transmission of PDU sets. For example, the procedure in FIG. 5 may be implemented by a WTRU 102 (e.g., a XR WTRU). At 802, the WTRU 102 may send, using a first set of resources and first HARQ information, one or more TBs of a first PDU set. At 804, the WTRU 102 may receive HARQ feedback information associated with the sent TBs of the first PDU set. At 806, the WTRU may receive information indicating a second set of resources associated with the HARQ feedback information. At 808, the WTRU 102 may send, using the second set of resources and at least a portion of the first HARQ information (e.g., indicated by the HARQ feedback information), one or more TBs of a second PDU set based on the second PDU set being higher importance than the first PDU set.

[0179] For example, the WTRU 102 may receive information indicating the first set of resources via first downlink control information.

[0180] For example, the WTRU 102 may receive the HARQ feedback information and the information indicating the second set of resources via second downlink control information.

[0181] For example, the first HARQ information may include one or more HARQ process identifiers respectively associated with the one or more TBs of the first PDU set.

[0182] For example, the HARQ feedback information may indicate that at least one TB of the first PDU set is to be retransmitted.

[0183] For example, the WTRU 102 may send information indicating that the one or more TBs of the second PDU set are new data. [0184] For example, the information indicating that the one or more TBs of the second PDU set are associated with new data may be sent via uplink control information.

[0185] For example, the WTRU 102 may select one or more HARQ process identifiers from the first HARQ information based on the HARQ feedback information. The WTRU 102 may send, using the selected one or more HARQ process identifiers, the one or more TBs of the second PDU set.

[0186] For example, the first PDU set and the second PDU set may be generated by an application at (e.g., executed by) the WTRU 102.

[0187] For example, the WTRU 102 may determine the importance of the first PDU set and/or the importance of the second PDU set based on one or more properties associated with the first PDU set and/or the second PDU set.

[0188] FIG. 9 is a procedural diagram illustrating another example procedure for reporting traffic processing delay and/or QoE related information. For example, the procedure in FIG. 5 may be implemented by a WTRU 102 (e.g., a XR WTRU). At 902, the WTRU 102 may receive information indicating a set of thresholds associated with a first set of resources. At 904, the WTRU 102 may communicate TBs one or more PDU sets using the first set of resources. At 906, the WTRU 102 may perform one or more measurements on the communication of the one or more PDU sets. At 908, the WTRU 102 may send reporting information associated with the one or more measurements based on the one or more measurements satisfying at least one of the set of thresholds.

[0189] For example, the WTRU 102 may communicate the TBs for the one or more PDU sets using the first set of resources which includes to send the TBs for the one or more PDU sets using the first set of resources.

[0190] For example, the WTRU 102 may perform the one or more measurements on the communicating of the one or more PDU sets which includes to measure a processing time associated with the sending of the one or more PDU sets.

[0191] For example, the WTRU 102 may communicate the TBs for the one or more PDU sets using the first set of resources which includes to receive the TBs for the one or more PDU sets using the first set of resources.

[0192] For example, the WTRU 102 may perform the one or more measurements on the communicating of the one or more PDU sets which includes to measure a processing time associated with the receiving of the one or more PDU sets.

[0193] For example, the WTRU 102 may, after sending the reporting information, receive information indicating a second set of resources. The WTRU 102 may communicate TBs for (e.g., subsequent) PDU sets using the second set of resources. [0194] For example, the set of thresholds may include a first threshold for the one or more PDU sets sent using the first set of resources.

[0195] For example, the set of thresholds may include a second threshold for the one or more PDU sets received using the first set of resources.

[0196] For example, the set of thresholds may include a third threshold for a correlation between the one or more PDU sets sent using the first set of resources and the one or more PDU sets received using the first set of resources.

[0197] For example, the one or more PDU sets may be associated with an application at (e.g., executed by) the WTRU 102.

[0198] In certain representative embodiments, features shown in any of FIGs. 2, 3, 4, 5, 6, 7, 8 and/or 9 may be modified and/or combined, whether in whole or in part.

[0199] In certain representative embodiments, a WTRU 102 (e.g., a XR WTRU) may send, using a first set of resources, information indicating one or more TBs of a first PDU set associated with first HARQ information. The WTRU 102 may receive HARQ feedback information associated with the first HARQ information. The HARQ feedback information may include information indicating (e.g., to the WTRU 102 to perform) retransmission of the one or more TBs of the first PDU set. The WTRU 102 may receive information indicating a second set of (e.g., dynamically) granted resources associated with the retransmission of the one or more TBs of the first PDU set. The WTRU 102 may send, using the second set of resources, one or more TBs of a second PDU set associated with the first HARQ information based on an importance of the second PDU set being higher than an importance of the first PDU set.

[0200] For example, the information indicating the first set of granted resources or the information indicating the second set of granted resources may be received in downlink control information.

[0201] For example, the first HARQ information may be a HARQ process identifier associated with the retransmission of the one or more TBs of the first PDU set.

[0202] For example, the WTRU 102 may determine the importance of the first PDU set and/or the importance of the second PDU set based on any of a static property and/or a dynamic property associated with the first PDU set and/or the second PDU set.

[0203] For example, the first PDU set and the second PDU set may be generated by an application (e.g., executed) at the WTRU 102.

[0204] For example, the HARQ feedback information and the information indicating the second set of granted resources may be received in downlink control information. [0205] References

[0206] The content of each of the following references is incorporated by reference herein in its entirety:

[1] 3GPP TR 38.835 -Technical Specification Group Radio Access Network; NR; Study on XR enhancements for NR (Release 18) (v 18.0.1);

[2] 3GPP TR 23.700-60 - Study on XR (Extended Reality) and media services (Release 18) (v 18.0.0); and

[3] 3GPP TS 38.300 - NR and NG-RAN Overall Description Stage 2 (v 17.5.0).

[0207] Conclusion

[0208] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0209] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of wireless communication capable devices, (e.g., radio wave emitters and receivers). However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

[0210] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term “video” or the term “imagery” may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms “user equipment” and its abbreviation “UE”, the term “remote” and/or the terms “head mounted display” or its abbreviation “HMD” may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0211] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0212] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0213] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit (“CPU”) and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being “executed,” “computer executed” or “CPU executed.” [0214] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU’s operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0215] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0216] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device.

[0217] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be effected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.

[0218] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples include one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and/or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0219] Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems. [0220] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being “operably couplable” to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0221] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

[0222] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a s“ecific number of an introduced ”laim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term “single” or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may include usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should be interpreted to mean “at least one” or “one or more”). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.” Further, the terms “any of’ followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include “any of,” “any combination of,” “any multiple of,” and/or “any combination of multiples of’ the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, as used herein, the term “set” is intended to include any number of items, including zero. Additionally, as used herein, the term “number” is intended to include any number, including zero. And the term “multiple”, as used herein, is intended to be synonymous with “a plurality”.

[0223] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0224] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as “up to,” “at least,” “greater than,” “less than,” and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0225] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms “means for” in any claim is intended to invoke 35 U.S.C. §112, 6 or means-plus-function claim format, and any claim without the terms “means for” is not so intended.

Claims

CLAIMS What is claimed is:

1. A wireless transmit/receive unit (WTRU) comprising: a processor, a memory, and a transceiver which are configured to: send, using a first set of resources, one or more transport blocks (TBs) of a first protocol data unit (PDU) set which are associated with first hybrid automatic repeat request (HARQ) information, receive HARQ feedback information, associated with the first HARQ information, indicating retransmission of at least one TB of the first PDU set, receive information indicating a second set of resources associated with the retransmission of the at least one TB of the first PDU set, and send, using the second set of resources, one or more TBs of a second PDU set which are associated with the first HARQ information based on an importance of the second PDU set being higher than an importance of the first PDU set.

2. The WTRU of claim 1, wherein the processor, the memory, and the transceiver are configured to receive information indicating the first set of resources via first downlink control information.

3. The WTRU of any one of claims 1-2, wherein the processor, the memory, and the transceiver are configured to receive the HARQ feedback information and the information indicating the second set of resources via second downlink control information.

4. The WTRU of any one of claims 1-3, wherein the first HARQ information includes one or more HARQ process identifiers associated with the one or more TBs of the first PDU set.

5. The WTRU of any one of claims 1-4, wherein the HARQ feedback information includes (i) at least one HARQ process identifier associated with at least one TB of the first PDU set, and (ii) at least one new data indicator, associated with the least one HARQ process identifier, which is not toggled.

6. The WTRU of any one of claims 1-5, wherein the processor, the memory, and the transceiver are configured to send information indicating that the one or more TBs of the second PDU set are associated with new data.

7. The WTRU of any one of claims 1-5, wherein information indicating that the one or more TBs of the second PDU set are associated with new data is sent via uplink control information.

8. The WTRU of any one of claims 1-7, wherein the processor, and the memory are configured to: select one or more HARQ process identifiers from the first HARQ information associated with the one or more TBs of the first PDU set, and send the one or more TBs of the second PDU set which are associated with the selected one or more HARQ process identifiers.

9. The WTRU of any one of claims 1-8, wherein the first PDU set and the second PDU set are generated by an application executed by the WTRU.

10. The WTRU of any one of claims 1-9, wherein the processor, and the memory are configured to determine the importance of the first PDU set and/or the importance of the second PDU set based on any of a static property and/or a dynamic property associated with the first PDU set and/or the second PDU set.

11. A method implemented by a wireless transmit/receive unit (WTRU), the method comprising: sending, using a first set of resources, one or more transport blocks (TBs) of a first protocol data unit (PDU) set which are associated with first hybrid automatic repeat request (HARQ) information; receiving HARQ feedback information, associated with the first HARQ information, indicating retransmission of at least one TB of the first PDU set; receiving information indicating a second set of resources associated with the retransmission of the at least one TB of the first PDU set; and sending, using the second set of resources, one or more TBs of a second PDU set which are associated with the first HARQ information based on an importance of the second PDU set being higher than an importance of the first PDU set.

12. The method of claim 11, further comprising: receiving information indicating the first set of resources via first downlink control information.

13. The method of any one of claims 11-12, wherein the HARQ feedback information and the information indicating the second set of resources are received via second downlink control information.

14. The method of any one of claims 11-13, wherein the first HARQ information includes one or more HARQ process identifiers associated with the one or more TBs of the first PDU set.

15. The method of any one of claims 11-14, wherein the HARQ feedback information includes

(i) at least one HARQ process identifier associated with at least one TB of the first PDU set, and

(ii) at least one new data indicator, associated with the least one HARQ process identifier, which is not toggled.

16. The method of any one of claims 11-15, further comprising: sending information indicating that the one or more TBs of the second PDU set are associated with new data.

17. The method of any one of claims 11-16, wherein information indicating that the one or more TBs of the second PDU set are associated with new data is sent via uplink control information.

18. The method of any one of claims 11-17, further comprising: selecting one or more HARQ process identifiers from the first HARQ information associated with the one or more TBs of the first PDU set; and sending the one or more TBs of the second PDU set which are associated with the selected one or more HARQ process identifiers.

19. The method of any one of claims 11-18, wherein the first PDU set and the second PDU set are generated by an application executed by the WTRU.

20. The method of any one of claims 11-19, wherein the processor, and the memory are configured to determine the importance of the first PDU set and/or the importance of the second PDU set based on any of a static property and/or a dynamic property associated with the first PDU set and/or the second PDU set.