WO2025034822A1

WO2025034822A1 - A method for reliable and resource efficient transmission of extended reality (xr) traffic and a system thereof

Info

Publication number: WO2025034822A1
Application number: PCT/US2024/041235
Authority: WO
Inventors: Senay NEGUSSE; Jaya Rao; Tejaswinee LUTCHOOMUN; Oumer Teyeb; Ognen OGNENOSKI; Paul Marinier; Ahmed Mostafa; Ananth KINI
Original assignee: Interdigital Patent Holdings, Inc.
Priority date: 2023-08-07
Filing date: 2024-08-07
Publication date: 2025-02-13

Abstract

A determination and/or indication of one or more transmission parameters for transmitting one or more protocol data units (PDUs) in a PDU set is described. A wireless transmit/receive unit (WTRU) receives a set of configurations associated with one or more PDU set profile. The WTRU receives the one or more PDUs of the PDU set and an information associated with a PDU set profile. If one or more conditions associated with the PDU set profile are met, the WTRU determines a number of unused transmission occasions that may be used for repetition of the one or more PDUs, and thereby selects a repetition pattern that allows repeating at least a subset of PDUs of the PDU set. The WTRU transmits, to a network, an indication associated with the selected repetition pattern. The WTRU transmits the one or more PDUs of the PDU set based on the selected repetition pattern.

Description

IDC-2023P00722WQ

A METHOD FOR RELIABLE AND RESOURCE EFFICIENT TRANSMISSION OF EXTENDED REALITY (XR) TRAFFIC AND A SYSTEM THEREOF

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63/531 ,196, filed August 7, 2023, the contents of which are incorporated herein by reference.

BACKGROUND

[0002] Extended reality (XR) is an umbrella term for different types of immersive experiences including virtual reality (VR), augmented reality (AR), mixed reality (MR) and a combination of other such realities. In XR applications, an XR data traffic may be generated aperiod ically and/or in form of multiple data bursts. Different data bursts may have different quality of service (QoS) requirements. Moreover, within a data burst, different data units may also have different QoS requirements. Conventional data transmission techniques fail to satisfy the QoS requirements of the XR data traffic, which results in inefficient use of resources such as wireless medium and hardware. Moreover, the conventional data transmission techniques cause delays and latency that degrades a user experience of the XR applications. Therefore, there is a need for an efficient data transmission and/or reception technique that can meet the QoS requirements of the XR data traffic and effectively utilize the resources.

SUMMARY

[0003] Determination and indication of one or more transmission parameters for transmitting one or more protocol data units (PDUs) in a PDU set based on a PDU set profile is described. This includes a wireless transmit/receive unit (WTRU) that receives, from a network, a set of configurations, including but not limited to a multi physical uplink shared channel (multi-PUSCH) configuration, a set of repetition patterns that the WTRU may use, a set of logical channels (LCHs) associated with one or more PDU set profiles, an association information between a PDU set error rate (PSER) and a maximum number of repetitions, and/or one or more threshold values associated with a PDU set profile. The WTRU receives, from one or more higher layers, the one or more PDUs of the PDU set and information on the PDU set profile (e.g., a PDU set size, the PSER, etc.) and determines a mapping of the one or more PDUs of the PDU set to one or more LCHs based on the PDU set profile. If one or more conditions associated with PDU set profile are met (e.g., whether the PDU set size is greater than a first threshold indicative of a threshold PDU set size, and/or whether the PSER is greater than a second threshold indicative of a threshold PSER etc.), the WTRU determines a number of unused transmission occasions (UTOs) (i.e. one or more unused PUSCHs) that may be used for repetition of the one IDC-2023P00722WC or more PDUs and/or one or more transport blocks (TBs) based on the PDU set profile (e.g., a payload size, the PSER) and selects a repetition pattern that allows repeating at least a subset of PDUs of the PDU set based on a priority of the repetition pattern, the PSER, and/or the number of UTOs. The WTRU transmits an indication to the network (e.g., in an uplink control information (UCI)) on the selected repetition pattern (e.g., index and/or identifier (ID) of the selected repetition pattern) in one or more CG PUSCH transmission occasions (TOs). The WTRU transmits the one or more PDUs of the PDU set using one or more CG PUSCHs based on the selected repetition pattern.

[0004] In an embodiment, a method performed by a WTRU is provided. The method includes receiving configuration information comprising a plurality CG PUSCH occasions and transmitting an indication of one or more transmission parameters associated with one or more PDUs of at least one PDU set. The method further includes determining the one or more transmission parameters based on the configuration information and a plurality of PDU set attributes associated with the at least one PDU set. The method further includes transmitting the one or more PDUs in one or more CG PUSCH occasions of the plurality of CG PUSCH occasions based on the one or more transmission parameters.

[0005] In an embodiment, a WTRU comprising a memory, a transceiver, and a processor is provided. The memory is configured to store one or more PDUs of at least one PDU set. The transceiver is configured to receive configuration information comprising a plurality of CG PUSCH occasions. The transceiver is configured to transmit an indication of one or more transmission parameters associated with the one or more PDUs. The processor is configured to determine the one or more transmission parameters based on the configuration information and a plurality of PDU set attributes associated with the at least one PDU set. The transceiver is further configured to transmit the one or more PDUs in one or more CG PUSCH occasions of the plurality of CG PUSCH occasions based on the one or more transmission parameters.

[0006] In an embodiment, the one or more transmission parameters include at least one repetition pattern. [0007] In an embodiment, the configuration information further comprises one or more of: (1) a threshold PDU Set Error Rate (PSER), (2) a threshold PDU set size, (3) a set of repetition patterns, or (3) a maximum number of repetitions. Each repetition pattern in the set of repetition patterns is associated with a priority.

[0008] In an embodiment, the WTRU determines one or more used CG PUSCH occasions and one or more unused CG PUSCH occasions from the plurality of CG PUSCH occasions.

[0009] In an embodiment, the WTRU selects a repetition pattern from the set of repetition patterns based on the plurality of PDU set attributes, a number of the one or more unused CG PUSCH occasions, and at least one threshold. The WTRU determines a number of repetitions based on the maximum number of repetitions and the plurality of PDU set attributes.

[0010] In an embodiment, the one or more transmission parameters are indicative of at least one of: the selected repetition pattern or the determined number of repetitions. IDC-2023P00722WG

[0011] In an embodiment, the WTRU retransmits the one or more PDUs in the one or more unused CG PUSCH occasions based on at least one of: the selected repetition pattern or the determined number of repetitions.

[0012] In an embodiment, the WTRU determines a PDU set size associated with the at least one PDU set. The WTRU determines the one or more transmission parameters based on a comparison of the threshold PDU set size with the PDU set size.

[0013] In an embodiment, the WTRU determines a PSER associated with the at least one PDU set. The WTRU determines the one or more transmission parameters based on a comparison of the threshold PSER with the determined PSER.

[0014] In an embodiment, the indication is transmitted in an Uplink Control Information (UCI).

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein:

[0016] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;

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

[0018] 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 according to an embodiment;

[0019] FIG. 1 D is a system diagram illustrating a further example RAN and a further example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0020] FIG. 2 is a diagram illustrating an example transmission of an indication by the WTRU to a network according to an embodiment; and

[0021] FIG. 3 is a flowchart illustrating an example method performed by the WTRU for transmitting the indication to the network according to an embodiment.

DETAILED DESCRIPTION

[0022] A wireless transmit/receive unit (WTRU) may correspond to any extended Reality (XR) device and/or node which may have various form factors. Typical WTRUs (e.g., an XR WTRUs) may include, but are not limited to the following: a head mounted display (HMDs), optical see-through glasses or a camera see- through HMD for augmented reality (AR) and/or mixed reality (MR), a mobile device with a positional tracking unit and a camera, a wearable device, haptic gloves, a haptic body suit, haptic shoes, etc. In addition, several IDC-2023P00722WQ different types of the XR WTRUs may be envisioned based on various XR device functions, for example, the XR device functions associated with display, camera, sensors, sensor processing, wireless connectivity, XR and/or media processing, power supply, to be provided by one or more devices, such as but not limited to wearable devices, actuators, controllers and/or accessories. One or more device, nodes, and/or WTRUs may be grouped into a collaborative XR group for supporting any of the XR applications, experiences, and/or services.

[0023] In the XR services and/or applications, XR traffic may include data which may be associated with an application data unit (ADU), a protocol data unit (PDU) set or a data burst. In an example, one or more PDUs of a PDU set may be associated with different segments and/or components of a video frame or a video slice. The data burst may include one or more PDU sets that may be transmitted and/or received over a time window. For example, a number of PDUs in the PDU set or the data burst transmitted in uplink (UL) and/or received in downlink (DL) may be dependent on a type of a media frame (e.g., three-dimensional (3D) video frame, audio frame etc.).

[0024] In typical XR applications, the WTRU transmits the XR traffic including the one or more PDUs and/or the one or more PDU sets in UL communication (e.g., pose, gesture, video data) and/or receives the XR traffic in DL communication (e.g video, audio, haptics). The XR traffic may be transmitted and/or received periodically or aperiodically in one or more data flows (e.g., quality of service (QoS) flows). During UL transmission, the XR traffic may arrive from an application layer at the WTRU and/or from different devices, terminals, or WTRUs (for e.g. via sidelink (S L)) at different time instances The XR traffic may be characterized by different attributes such as but not limited to variable payload sizes per PDU set, variable number of PDUs per PDU set, variable per PDU and/or per PDU set level importance and/or different levels of inter-dependencies between the one or more PDUs and/or the one or more PDU sets. The XR traffic (e.g. the one or more PDU and/or the one or more PDU sets) received by the WTRU may experience different delays, jitter, data rate and/or loss rate. For ensuring the QoS and high user experience, for e.g. quality of experience (QoE), it is important that data transmission and/or reception and other associated functions (e.g., prioritization, multiplexing, or scheduling etc.) are done on timely basis with an XR awareness (e.g., awareness of one or more PDU set attributes).

[0025] In many embodiments, determination and/or indication of the one or more transmission parameters for transmitting the one or more PDUs in the PDU set based on a PDU set profile is provided. In many examples, the WTRU receives, from a network, a set of configurations, including but not limited to a multi physical uplink shared channel (PUSCH) configuration, a set of repetition patterns that the WTRU may use, a set of logical channels (LCHs) associated with one or more PDU set profiles, an association information between a PDU set error rate (PSER) and/or a maximum number of repetitions, and/or one or more threshold values associated with the PDU set profile. The WTRU receives, from one or more higher layers, one or more PDUs of the PDU set and information on the PDU set profile (e.g., a PDU set size, a PDU set error rate (PSER) etc.) and determines a mapping of the one or more PDUs of the PDU set to one or more LCHs based on the PDU set profile. If any conditions associated with the PDU set profile are met (e.g., whether a size of PDU set IDC-2023P00722WG is greater than a first threshold indicative of a threshold PDU set size, and/or whether the PSER is greater than a second threshold indicative of a threshold PSER), the WTRU determines a number of unused transmission occasions (UTOs), i.e. unused PUSCHs that may be used for repetition of the one or more PDUs and/or transport blocks (TBs) based on the PDU set profile (e.g., a payload size, the PSER) and selects a repetition pattern that allows repeating at least a subset of PDUs of the PDU set based on a priority of the repetition pattern, the PSER and/or the number of UTOs The WTRU sends the indication to the network (e g., in uplink control information (UCI )) on the selected repetition pattern (e.g., index/ID of pattern) in one or more configured grant (CG) PUSCH transmission occasions (TOs). The WTRU transmits the one or more PDUs of the PDU set using one or more CG PUSCHs based on the selected repetition pattern.

[0026] FIG. 1A is a 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 unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0027] 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, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though itwill 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 (STA), may be configured to transmit and/or receive wireless signals and may include 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.

[0028] 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 to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, 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.

[0029] The base station 114a may be part of the RAN 104, 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, and the like. 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 one 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 sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

[0030] 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).

[0031] 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 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 (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).

[0032] 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). [0033] 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 NR. IDC-2023P00722WC

[0034] 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).

[0035] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e , Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, 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. [0036] The base station 114b in FIG 1A 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 one 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 yet another 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 a picocell or femtocell. As shown in FIG. 1A, 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.

[0037] The RAN 104 may be in communication with the CN 106, 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 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 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0038] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the 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 or a different RAT.

[0039] 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. 1 A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0040] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1B, 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 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.

[0041] 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), 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. 1 B 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 in an electronic package or chip.

[0042] 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 one 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 yet another 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.

[0043] Although the transmit/receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ IDC-2023P00722WG

MIMO technology. Thus, in one 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. [0044] 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.

[0045] 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), read-only 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).

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

[0047] 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

[0048] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a handsfree 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 IDC-2023P00722WG and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The 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, a humidity sensor and the like.

[0049] 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 UL (e.g., for transmission) and DL (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 UL (e g., for transmission) or the DL (e g., for reception)).

[0050] 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, 102c over the air interface 116. The RAN 104 may also be in communication with the GN 106.

[0051] 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 one 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/or receive wireless signals from, the WTRU 102a.

[0052] Each of the eNode-Bs 160a, 160b, 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 UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0053] 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 the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0054] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 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 IDC-2023P00722WG

[0055] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 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.

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

[0057] 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. [0058] Although the WTRU is described in FIGS. 1A-1 D 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.

[0059] In representative embodiments, the other network 112 may be a WLAN.

[0060] 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 access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to 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.11e DLS or an 802.11z 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.

[0061] When using the 802.11ac 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. 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 IDC-2023P00722WG representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example 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.

[0062] 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 nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0063] Very High Throughput (VHT) STAs may support 20MHz, 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 noncontiguous 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 the Medium Access Control (MAC).

[0064] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah 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).

[0065] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802 11 n, 802.11ac, 802.11 af, and 802.11 ah, 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.11 ah, 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 IDC-2023P00722WG a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.

[0066] In the United States, the available frequency bands, which may be used by 802.11 ah, 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.11ah is 6 MHz to 26 MHz depending on the country code.

[0067] FIG. 1 D 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 NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0068] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 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 one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c. 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).

[0069] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the 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., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

[0070] 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 IDC-2023P00722WG

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.

[0071] 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, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0072] The CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0073] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 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 non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order 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 the like The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 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.

[0074] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 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 DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

[0075] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, 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. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, IDC-2023P00722WQ enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.

[0076] The ON 106 may facilitate communications with other networks 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 In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local 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.

[0077] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation 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.

[0078] 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 performing testing using over-the-air wireless communications.

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

[0080] The WTRU supporting an XR experience i.e. the XR services and/or applications may receive the one or more data units (e.g , the one or more PDUs, PDU sets, data bursts, and/or bitstreams etc.) from the one or more higher layers or from different devices, such as but not limited to the AR glasses and haptics gloves (e.g., via sidelink (SL)). The data units, which may have variable payload sizes, different periodicity, jitter and different inter-dependencies may be further processed and transmitted by the WTRU in the UL. IDC-2023P00722WQ

[0081] In typical scenarios, the WTRU transmits the XR traffic including the one or more PDUs and/or the one or more PDU sets in the UL (e.g., pose, gesture, and/or video data etc.) and/or receives the XR traffic in the DL (e.g video, audio, and/or haptics etc.). The XR traffic may be transmitted and/or received periodically or aperiodically in one or more data flows (e.g., the QoS flows). During the UL transmissions, the XR traffic may arrive from an application layer at the WTRU and/or from different devices, terminals, or WTRUs (e.g. via SL) at different time instances. The XR traffic may be characterized by one or more traffic attributes such as but not limited to variable payload sizes per PDU set, variable number of PDUs per PDU set, variable per PDU priority and/or importance values, variable per PDU set level priority and/or importance values and/or different levels of inter-dependencies between the one or more PDUs and/or the one or more PDUs sets. The XR traffic (e g., the one or more PDUs and/or the one or more PDU sets) received by the WTRU from the one or more higher layers or other devices and/or terminals may also experience different delays, jitter, data rate and/or loss rate. For ensuring that one or more QoS requirements and/or conditions (e.g., a PDU set delay bound (PSDB), a PDU set error rate (PSER), and/or a PDU set integrated handling indication (PSIHI) etc.) are met, the WTRU may prioritize, multiplex, schedule and/or allocate resources on timely basis based on one or more PDU set attributes. For ensuring quality of experience (QoE), the one or more PDUs within the PDU set or within different PDU sets generated at a transmitting side of the XR application are expected to be delivered to a receiving side of the application within the QoS requirements and/or conditions (e.g. the PSDB, the PSER, and/or the PSIHI etc.). In an example, the PDU set attributes may include one or more XR traffic attributes such as but not limited to the payload sizes per PDU set, the number of PDUs per PDU set, the priorities and/or importance values of the PDUs in the PDU set, the priorities and/or importance values of the PDU set, and/or the inter-dependencies between the one or more PDUs and/or the one or more PDUs sets. In an example, the PDU set attributes may include one or more of: the PSDB, the PSER, and/or the PSIHI etc. In an example, the PDU set attributes may include the one or more QoS parameters and/or the one or more QoE parameters.

[0082] In the XR traffic, different PDUs and/or PDU sets may contribute to different user experiences (e.g., the QoE). As such, the different PDUs and/or PDU sets may also be associated with different importance and/or priority values from an application layer perspective In that, the one or more PDU sets transmitted sequentially in a time domain may be inter-dependent with each other in different ways. In other words, unlike an existing QoS framework where all the PDUs and/or all the PDU sets in the data flow and/or the QoS flow are provided with same forwarding treatment by assuming equal importance and/or priority, the one or more PDUs and/or the one or more PDU sets in the data burst for the XR traffic may need to be differentiated and handled differently based on different QoS requirements and/or conditions at one or more lower layers, irrespective of whether the one or more PDUs and/or the one or more PDU sets are in the one or more QoS flows, during scheduling and transmissions in the UL and/or the DL.

[0083] The inter-dependencies between the one or more PDUs and/or the one or more PDU sets in a single QoS flow and/or multiple QoS flows may result in different challenges for meeting the QoS conditions and/or requirements at a PDU set level during transmission in the UL and/or the DL. For example, when the one or more PDUs from the different PDU sets may be multiplexed into a same radio bearer and/or same logical IDC-2023P00722WQ channels and subsequently mapped to different occasions, slots, and/or periods in one or more resources (e.g, configured grants (CGs)), tracking an association between the one or more PDUs for meeting one or more PDU set level QoS conditions and/or requirements may be challenging, especially when there may be delays and/or jitter during reception and/or processing. Examples that ensure proper mapping and/or multiplexing of the one or more PDUs and/or the one or more PDU sets to one or more configured resources (e.g. CGs) over time and/or frequency domain such as one or more PUSCH occasions (e.g. PUSCHs) or resource block groups (RBGs) considering traffic characteristics (e g, delays and/or jitter during reception of the one or more PDUs and/or the one or more PDU sets over the SL or from the one or more higher layers, the variable payload sizes and/or the variable priority and/or importance values) for meeting the PDU set level QoS conditions and/or requirements during the UL transmissions may be beneficial.

[0084] Enhancements for the XR include support for multi-PUSCH TOs within a slot over one or more slots to accommodate transmission of the one or more PDUs of the one or more PDU sets with a large pay load size. Moreover, the multi-PUSCH TOs per slot may be statically configured across one or more CG periods or may be provided to the WTRU, using the DCI, such but not limited to a default grant (DG). In multiple CG PUSCH TOs, the WTRU may be configured with one or more parameters, e g, RepK value, which may indicate the number of TOs within the CG period, wherein the RepK value might indicate a number of repetitions for a single PUSCH occasion. Multi-PUSCH CG configuration, the TOs as well as one or more frequency domain resources in additional to the one or more transmission parameters, such as modulation and coding scheme (MCS) indices, may be semi-statically configured over multiple periods of the CG. Moreover, each PUSCH occasion in the slot may be associated with a hybrid automatic repeat request (HARQ) process identifier (ID).

[0085] In current systems, adaptation of the one or more transmission parameters (e.g, link adaptation) and one or more retransmission schemes are configured based on an achievable target error rate (e.g, a block error rate (BLER) and/or a packet error rate (PER)) for a packet or a TB to ensure reliable reception of the packet within a packet delay budget (PDB). Such an approach treats each TB independently and with identical importance, such that all the QoS requirements and/or conditions, e.g, reliability and/or latency requirements, are met for each TB. In multi-PUSCH transmission of the TBs including the one or more PDUs from the one or more PDU sets, ensuring that the one or more QoS requirements and/or conditions for each PUSCH transmission is met may not guarantee that the PDU set level QoS requirements (e.g. the data rate, the latency, the error rate (e.g. BLER and/or PER), and/or the reliability etc.) are fulfilled.

[0086] In multi-PUSCH transmission of the one or more PDU sets, retransmission of the one or more TBs is based on the network (NW) sending an indication to the WTRU including a new resource grant (e.g, the DG and/or the CG) allocated for retransmission of the one or more TBs. The allocated resource grant is associated with the one or more HARQ process IDs which are associated with the one or more TBs and/or the one or more PUSCH occasions which are to be retransmitted. The network may send the indication (e.g, allocate the DG and/or the CG) for retransmission of the TB multiple times until the TB is received successfully. IDC-2023P00722WQ

[0087] Even though the network ensures that all the PDUs in the multi-PUSCH transmission of the PDU set are received successfully within the PDB, the network may not be able to guarantee that all the PDU set level QoS requirements and/or conditions (e g., the PSER and/or the PSDB) are met. Since, for the UL transmissions, the network may not have knowledge and/or information related to the PDU set profile (e.g , the PDU set level QoS, the payload size, .... etc.), the network consequently, may not allocate resource grants for the retransmission of the one or more PDUs within the PSDB.

[0088] In an embodiment, the present systems and method address providing efficient resource utilization and high reliability in the XR services transmitting multiple TBs. Throughout the embodiments described herein, the network may include any of a base station (e.g., a gNB, a transmission and reception point (TRP), a RAN node and/or an access node etc.), a core network function (e g., an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), and/or a network exposure function (NEF) etc.) and/or an application function (e.g , an edge server function and/or a remote server function etc.), for example. Throughout the embodiments herein, the one or more flows may correspond to any of: the one or more QoS flows and/or the one or more data flows (e.g., a flow of data including the one or more PDUs, the one or more PDU sets and/or the one or more data bursts, which may be inter-dependent with one and another and/or associated with the one or more QoS requirements and/or conditions, such as but not limited to the latency, the data rate, the reliability, an/or a round-trip time RTT latency etc., for example). Different flows, possibly originating from a common application and/or a common experience source and/or intended to a common destination device and/or a destination WTRU or a group of associated devices and/or a group of WTRUs may be referred to as associated flows or correlated flows. Throughout the embodiments herein, the data unit may refer to any of: one or more frames (e.g., media frames, video frames, and/or audio frames and/or slices and/or segments associated with the frames), the one or more PDUs, the one or more PDU sets, the one or more data bursts, a group of frames, a group of PDUs, a group of PDU sets, a group of data bursts, and/or one or more bitstreams etc The data units, which may be transmitted and/or received by the WTRU sequentially (e.g., one after the other) or in parallel (e.g., over different channels, links, and/or resources etc.), may or may not be inter-dependent with each other.

[0089] Throughout the embodiments herein, a forwarding configuration may be associated with any one or more of radio bearers (e g., a data radio bearer (DRB), a signaling radio bearers (SRB), a transport radio bearer, and/or a PDU set bearer etc.), one or more logical channels (LCHs), one or more logical channel groups (LCGs), one or more configuration parameters (e.g configuration information) in one or more individual layers within an AS protocol stack (e g., service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), media access control (MAC), physical (PHY), and/or other protocol layers etc.), one or more parameters associated with logical channel prioritization (LCP) (e.g., one or more priority and/or importance values and/or levels, prioritized bit rate (PBR), and/or bucket size duration (BSD) etc.), one or more bandwidth parts (BWPs), one or more carriers, one or more radio links and/or interfaces (e.g. Uu links and/or SLs etc.), and/or one or more radio resources (e.g., one or more frequency, time, and/or spatial resources such as but not limited to symbols, slots, subcarriers, resource elements and/or beams). For IDC-2023P00722WQ example, radio resources may be associated with, but not limited to, one or more CGs, dynamic grants, one or more default grants, any other resource grants, and/or grant free resources etc..

[0090] Throughout the embodiments herein, the one or more PDU sets and the corresponding one or more characteristics and/or one or more properties, may refer to any one or more PDU sets may include, but are not limited to the one or more data units (e g., the one or more PDUs) associated with a media unit, or the video frame and/or slice etc., for example. The data units within the PDU set and/or the data burst may be interdependent with each other at the application layer and/or at the one or more lower layers (e.g , AS layers), the attributes and/or properties of the PDU set may be different from each other in terms of, for example, the number of PDUs in the PDU set, the payload sizes, an intra-PDU set correlation, the importance and/or priority values and/or levels of the data units, a status of transmission (e.g., a percentage of PDUs of the one or more data units transmitted and/or received successfully etc ), an effective data rate and/or an effective reliability associated with the transmission etc., for example. In an example, the attributes and/or properties associated with the one or more PDU sets may be visible at the one or more lower layers (e.g., at the PDCP, RLC, MAC, and/or PHY sub-layers and/or layers etc.), possibly for supporting one or more additional actions and/or functions (e.g., prioritizing, mapping to the LCH, multiplexing into the one or more TBs, and/or scheduling etc.). This may be based on one or more of markings in the one or more data units (e.g. markings in the one or more frames, the one or more slices and/or subframes, the one or more PDUs and/or the one or more PDU sets etc.), reception of the indication, mapping of the one or more data units, tracking of the attributes and/or the parameters, and one or more restrictions associated with the corresponding layer and/or sublayer. For example, the markings may include, but are not limited to, one or more sequence numbers, IDs, indexes, timestamps, and/or time offset values (e.g., with respect to a reference time) in a header of the one or more data units etc. The markings may be made by the one or more higher layers, any preceding sub-layer and/or layer, another device and/or another WTRU Reception of the indication such as a control PDU (e.g., an application, higher, and/or NAS layer indication, a PDCP control PDU, an RLC control PDU, a MAC control element (CE), the DCI, and/or the UCI etc.). The indication may be received by the WTRU from a higher and/or preceding layer, from another device and/or WTRU (e.g , over the SL) and/or from the network, for example.

[0091] Mapping of the one or more data units from the higher layer to a configuration associated with the one or more lower layers. For example, the WTRU may have visibility of one or more higher layer attributes at the one or more lower layers when mapping the one or more PDUs to one or more radio bearers, the one or more LCHs, the one or more TBs and/or one or more HARQ processes that may be configured to provide similar forwarding treatment.

[0092] Tracking of the one or more attributes of the one or more PDUs at any buffer associated with the one or more sublayers, the one or more radio bearers, the one or more LCHs and/or the one or more HARQ processes. For example, the WTRU may track the one or more attributes associated with the one or more PDU sets based at least on any of a time elapsed since the reception of a first PDU of the PDU set, a remaining time for the one or more PDUs of the PDU set for meeting the PSDB, the jitter between an arrival the one or more IDC-2023P00722WQ

PDUs within and/or across the one or more PDU sets, the percentage and/or the payload size of one or more remaining PDUs of the PDU set expected to be received.

[0093] Restrictions associated with the one or more sublayers, the one or more radio bearers, the one or more LCHs and/or the one or more HARD processes to which the one or more data units of the one or more PDU sets may be mapped to. For example, the WTRU may have visibility of the one or more data units and determine corresponding actions and/or functions (e.g., perform prioritization per LCP, perform mapping to one or more restricted CG configurations, the one or more TBs, one or more HPIs) based on one or more configured restrictions associated with the one or more sublayers, the one or more radio bearers and/or the one or more LCHs to which the one or more data units may be mapped to.

[0094] The one or more PDU sets and the corresponding characteristics and/or properties may refer to the data burst and/or may refer to the data produced by the application in a short period of time, comprising the one or more PDUs from the one or more PDU sets. The attributes (i e. characteristics and/or properties), associations and inter-dependencies (e g., intra-PDU set and/or inter-PDU set), include but are not limited to a start and/or end indication of the PDU set and/or the data burst (e.g., via a sequence number (SN), the start and/or end indication, and/or the timestamp etc.), a start and/or end time, a duration, corresponding payload sizes, a periodicity, the importance and/or priority values and the QoS (e.g., the PSDB) and may be visible to the one or more AS layers (e.g., with associated IDs) and/or handled at the one or more AS layers with the awareness of the association during data transmission in the UL and/or reception in the DL.

[0095] The one or more PDU sets and the associated characteristics and/or properties may refer to application and/or high layer importance and/or priority values. In that, the different PDUs in the PDU set and/or all PDUs in the PDU set may be associated with different importance and/or priority values. The importance and/or priority values may correspond to spatial importance (e.g., spatial position of the video frame whose data is carried by the one or more PDUs and/or the PDU set, where the one or more PDUs and/or the PDU set carrying field of view (FoV) spatial positions may be associated with higher spatial importance than non-FoV spatial positions) and/or temporal importance (e.g., time sequence of the video frame and/or application frame whose data is carried by the one or more PDUs and/or the PDU set, where the one or more PDUs and/or the PDU sets carrying base video frames such as l-frames may be associated with higher temporal importance than differential video frames such as P-frames and/or B-frames). The importance and/or priority values may be visible to the AS layers during data transmission and/or reception.

[0096] The one or more PDU sets and the associated characteristics and/or properties may refer to the one or more QoS flows and/or the one or more data flows: The one or more PDUs and/or the one or more PDU sets of the application may be encoded and delivered by the application to the WTRU (in the UL) and/or network (in the DL) via the one or more QoS flows and/or the one or more data flows In this regard, the different QoS flows and/or the different data flows carrying the one or more PDUs and/or the one or more PDU sets associated to the XR application and/or the experience may be visible to the AS layers and/or handled at the AS layers with the awareness of such association during data transmission and/or reception. IDC-2023P00722WC

[0097] Throughout the embodiments herein, the PDU set profile may include but is not limited to the traffic characteristics and one or more PDU set level QoS requirements and/or conditions referring to one or more of: the PSDB, the PSI HI, the PSER, the jitter, and/or a remaining delay. The PSDB refers to a time between reception of the first PDU (at the UPF in the DL, at the WTRU in the UL) and the successful delivery of a last arrived PDU of the PDU set (at the WTRU in the DL, at the UPF in the UL). The PSDB is an optional parameter and when provided, the PSDB may supersede the PDB. The PSIHI indicates whether all the PDUs of the PDU set are needed for the usage of the PDU set by the application layer. The PSER defines an upper bound for a rate of non-congestion related PDU set losses between the RAN and the WTRU. The jitter may refer to a variation with respect to an expected time instance during which the one or more data units may be received and/or transmitted For example, for a set of data units that may be expected to be received periodically at different periodic time instances, the jitter may refer to the variation with respect to the periodic time instances (e g, for the data unit that may be received T1 ms in advance and/or T2 ms later than the expected time instance at T, the jitter range is T2 - T1). The jitter may refer to an instantaneous value or a statistical value (e g., an average, a variance, a standard deviation, a maximum and/or a minimum etc.). The remaining delay may refer to the time duration remaining for receiving and/or transmitting the one or more PDUs of the PDU set before the PSDB The remaining delay may also be referred to as a time to live (TTL) associated with the PDU set.

[0098] Throughout the embodiments herein, the multi-PUSCH CG may correspond to the one or more configured resources or one or more CG configurations, wherein each CG configuration may include a set of consecutive and/or non-consecutive PUSCH occasions per slot and/or per CG period. In an example, the multi- PUSCH CG may include the one or more CG periods (e g, each CG period may repeat periodically with a certain periodicity value), the CG period in the multi-PUSCH CG may include one or more consecutive or non- consecutive slots, the slot in the CG period of the multi-PUSCH CG may include the one or more consecutive and/or non-consecutive PUSCH occasions, and/or the PUSCH occasion in the slot and/or the CG period of the multi-PUSCH CG may include one or more consecutive and/or non-consecutive symbols with a certain symbol length (e.g, one or more time domain resources). The PUSCH occasion may include one or more resource blocks or one or more resource block groups in the frequency domain. Throughout the embodiments herein, a PUSCH usage may refer to any of the number, location, position, and/or timing of the one or more PUSCH occasions in the one or more slots and/or the one or more CG periods, which may be associated with one or more multi-PUSCH CG configurations.

[0099] FIG. 2 is a diagram illustrating an example transmission of an indication by a WTRU 202 to a base station 204 in a network 200 according to an embodiment. In an example, the WTRU 202 determines and/or indicates changes to the one or more transmission parameters in the multi-PUSCH configuration. For example, at 206, the WTRU 202 receives, from the base station 204, the configuration information indicative of adjusting the one or more transmission parameters when transmitting the one or more PDUs of the PDU set. The WTRU 202 multiplexes the one or more PDUs of the PDU set into the one or more TBs and/or the one or more HARQ processes, for example. At 208, the WTRU 202 determines and/or generates the one or more transmission IDC-2023P00722WC parameters associated with the PDU set. In that, the WTRU 202 selects the repetition pattern based on the PDU set profile for repeating the one or more PDUs using the one or more resources in the multi-PUSCH configuration. At 210, the WTRU 202 transmits the indication to the base station 204. The WTRU 202 also dynamically selects the number of repetitions for a remaining subset of PDUs in the PDU set based on the remaining delay and a downlink feedback information after an initial transmission of a first subset of PDUs at 212. At 214, the WTRU 202 receives, from the base station 204, one or more indications (e.g. a feedback) from the network 200 associated with the first subset of PDUs and/or a first subset of TBs associated with the PDU set transmitted to the base station 204. The WTRU 202 determines the repetition pattern to apply on a second subset of PDUs of the PDU set based on a remaining error budget and/or the remaining delay, and/or the WTRU 202 may determine one or more increments and/or one or more decrements for adjusting an MCS index in the multi-PUSCH CG based on the PDU set profile. At 216, the WTRU 202 transmits the second subset of PDUs to the base station 204.

[0100] FIG. 3 is a flowchart illustrating an example method 300 performed by the WTRU for transmitting the indication according to an embodiment. At 305, the WTRU receives the set of configurations, including but not limited to the multi-PUSCH configuration, the set of repetition patterns that the WTRU may use, a set of LCHs associated with the one or more PDU set profiles, information of association between the PSER and the maximum number of repetitions, and/or the one or more threshold values associated with the one or more PDU set profiles. At 310, the WTRU receives, from the one or more higher layers, the one or more PDUs of the one or more PDU sets and/or information on the PDU set profile, i.e., the one or more PDU set attributes (e.g , the PDU set size and/or the PSER, etc.). The WTRU determines the mapping of the one or more PDUs of the one or more PDU sets to the one or more LCHs based on the corresponding one or more PDU set profiles. At 315, the WTRU identifies one or more used and/or unused CG PUSCH occasions (i.e. one or more used and/or unused CG PUSCH TOs) In an example, the WTRU determines that the PUSCH occasion in the multi-PUSCH configuration is not used. In an example, the PUSCH occasion is unused if no PDU is scheduled for transmission during the PUSCH occasion and/or if the payload size of the one or more PDUs of the PDU set multiplexed into the PUSCH occasion is below a threshold value, as discussed below. In more examples, the one or more unused PUSCH occasions (i.e. the one or more unused CG PUSCH TOs) may be the one or more PUSCH occasions not expected to be used for data transmission by the WTRU. In an example, the one or more unused PUSCH occasions may include consecutive PUSCH occasions and/or may occur in a gap in between the one or more used PUSCH occasions.

[0101] At 320, the WTRU determines one or more conditions associated with the one or more PDU sets. The one or more conditions may include one or more thresholds (e.g. thresholdl, threshold2, etc.) associated with the one or more PDU set attributes. At 325, the WTRU checks if any condition of the one or more conditions is met. In that, the WTRU compares the one or more thresholds with corresponding PDU set attributes to check whether the PDU set attributes exceed the threshold. For example, the WTRU checks whether the size of the PDU set exceeds a threshold PDU set size indicated by a first threshold (i.e. thresholdl). In more examples, the WTRU checks whether the PSER associated with the one or more PDUs and/or the one or more PDU sets exceeds a threshold PSER indicated by a second threshold (i.e. threshold ).

[0102] If at 325, the WTRU determines that any conditions associated with the PDU set profile are met (e g., the size of PDU set exceeds the first threshold and/or the PSER associated with the PDU set exceeds the second threshold), then at 330, the WTRU determines the number of UTOs (i.e. unused CG PUSCH occasions) that may be used for repetition of the one or more PDUs and/or the one or more TBs based on the PDU set profile (e.g., the payload size and/or the PSER etc.). At 335, the WTRU selects the repetition pattern that allows repeating at least a subset of the PDUs of the one or more PDU sets based on the priority of the repetition pattern, the PSER and/or the number of UTOs. The WTRU generates the one or more transmission parameters and/or one or more retransmission parameters which may include the selected repetition pattern, the UTOs, and/or the number of repetitions etc. At 340, the WTRU generates the indication associated with the one or more transmission and/or retransmission parameters.

[0103] If at 325, the WTRU determines that the one or more conditions associated with the PDU set profile are not met, at 345, the WTRU determines the one or more used CG PUSCH TOs for transmission of the one or more PDU sets. Further, the WTRU generates, at 350, the indication associated with the one or more transmission parameters indicative of the one or more used CG PUSCH TOs used for transmission of the one or more PDU sets.

[0104] At 355, the WTRU transmits the indication to the network (e.g., in the UCI). In some examples, the WTRU transmits the indication in the one or more CG PUSCH occasions. Further, at 360, the WTRU transmits and/or retransmits the one or more PDUs of the one or more PDU sets using the one or more CG PUSCH occasions based on the one or more transmission and/or retransmission parameters respectively.

[0105] In many more example embodiments, the WTRU may receive the configuration information indicative of adjusting the one or more transmission parameters when transmitting the one or more PDUs of the one or more PDU sets. In an example, the WTRU determines to change the one or more transmission parameters (e.g., the number of repetitions, the repetition pattern, and/or the MCS values etc.) when transmitting the one or more PDUs of the one or more PDU sets using the one or more resources in the multi- PUSCH configuration based on one or more of: the one or more PDU set profiles, the payload size of the one or more PDUs of the one or more PDU sets and the number of PUSCH occasions expected to be used and/or not used (e g., the PUSCH usage). The multi-PUSCH CG configuration may be associated with one or more CG resources (e.g., in the multi-PUSCH CG config) or DG resources (e.g., single DCI or multiple DCIs scheduling multiple PUSCHs), for example.

[0106] In an example, for the multi-PUSCH configuration, the WTRU may determine the UTOs, corresponding to any of the PUSCH occasions not used for the UL transmission, based on the payload size and/or arrival of the one or more PDUs in an LCH buffer. The WTRU may then utilize one or more available resources in the UTOs and determine the one or more transmission parameters (e g., the number of repetitions for the one or more TBs, the selected repetition pattern, the adjustment to the MCS values) which may provide IDC-2023P00722WC improved reliability and ensure successful transmission of the one or more PDUs within the PSDB. The WTRU may consider the one or more available resources associated with the multi-PUSCH configuration when determining the one or more transmission parameters to enable meeting the reliability and/or the latency requirements during transmission of the one or more PDU sets

[0107] In an example, the WTRU may receive, from the network, the configuration information and/or the one or more configuration parameters associated with the one or more multi-PUSCH configurations (e.g , the number of PUSCH occasions per slot, the number of slots per CG period etc.) for transmitting the one or more TBs including the one or more PDUs of the one or more PDU sets. The WTRU may receive the set of configurations from a variety of sources. The WTRU may receive the set of configurations indicative of the set of repetition patterns that may be used with the multi-PUSCH configuration for repeating the transmission of one or more TBs including the one or more PDUs of the one or more PDU sets. For example, the set of repetition patterns may indicate the TOs or the locations in the multi-PUSCH configuration that may be used for repetition of the one or more TBs and the RVs associated with such repetitions. The WTRU may additionally receive the priorities associated with the set of repetition patterns which may be associated with the one or more PDU set profiles associated with the one or more PDU sets. Different repetition patterns may be associated with different set of parameters, including but not limited to any of the following: a length, the number of repetitions, the locations to carry repetitions, the index and/or the ID etc., for example. The WTRU may receive the set of configurations from the configuration information related to the association between the one or more PDU set profiles (e g., the PSER) and the maximum number of repetitions allowed. For example, the WTRU may receive a mapping relation and/or a table including but not limited to the association between the maximum number of repetitions to use for a given PSER, e.g., maximum of X repetitions allowed for the PDU set requiring a Y% PSER. The WTRU may receive the set of configurations including the one or more threshold values associated with the one or more PDU set profiles. For example, the one or more threshold values relate to the payload size of the one or more PDU sets. The payload size may indirectly indicate the number of PUSCH occasions in the multi-PUSCH configuration that may or may not be used. The WTRU may additionally receive the one or more threshold values related to the PSER which may indicate the priority and/or importance level of the PDU set. The WTRU may receive the set of configurations including information associating the set of LCHs with the one or more PDU set profiles For example, the one or more PDU sets with similar profiles that are mapped to the same LCH. The WTRU may receive the set of configurations including but not limited to an association information between a percentage of allowed UTOs and the one or more PDU set profiles. In an example, the network may provide one or more restrictions on how the WTRU uses the UTOs, possibly to limit excess usage resources. The WTRU may receive the configuration information, via AS layer signaling (e.g., RRC signaling and/or messages, MAC CE or the DCI) or Non-AS (NAS) layer signaling (e.g., one or more PDU session related messages), for example.

[0108] The WTRU may receive, from the one or more higher layers, the one or more PDUs of the one or more PDU sets and the information related to the corresponding one or more PDU set profiles (e.g., the PSER, the PSDB, and/or the payload size, etc.). The WTRU may select and/or forward the one or more PDUs of the IDC-2023P00722WQ one or more PDU sets to the one or more radio bearers and/or the one or more LCHs based on the set of parameters associated with the one or more PDUs and/or the one or more PDU sets including but not limited to the importance and/or priority values, the arrival time window of the one or more PDUs, the payload size of the one or more PDUs, the QoS of the one or more PDUs and/or the one or more PDU sets (e g., the PSDB, the PSI HI, and/or the PSER), etc. The WTRU may determine the mapping of the one or more PDUs of the one or more PDU set to the one or more LCHs based on the corresponding one or more PDU set profiles (e.g , the PSER and/or the PSDB etc.). Mapping of the one or more PDUs of the one or more PDU sets to the one or more LCHs may ensure that the one or more PDUs of the one or more PDU sets are grouped within the same TB and/or successive TBs. The WTRU may multiplex the one or more PDUs of the one or more PDU sets into multiple TBs and/or multiple HARQ processes. In an example, for the PDU set including N PDUs mapped to M LCHs, a subset of the N PDUs may be multiplexed into one TB, as per an LCP procedure, according to a size of a resource grant associated with the TB and the priority of the M LCHs. The remaining subset of the PDUs may be multiplexed into other one or more TBs. Since the M LCHs may also contain other PDUs which may not be associated with the PDU set, the one or more TBs may contain a combination of N PDUs from the PDU set and non-PDU set. In an example, the WTRU may be configured with the one or more restrictions such that the N PDUs of the PDU set are prioritized over other non-PDU set related PDUs when multiplexing the PDUs into the one or more LCHs to one or more TBs. The different TBs including the different subsets of the PDUs of the PDU set may be associated with the one or more HARQ processes, where each HARQ process may be associated with the HARQ process ID. The one or more TBs may be transmitted by the WTRU in the UL in different PUSCH occasions of the multi-PUSCH configuration.

[0109] The WTRU (e.g., at the MAC sublayer) may be aware of which PDUs of the PDU set in the one or more LCHs that are mapped to the one or more TBs and/or the one or more HARQ processes based on the association and/or restriction information between the PDU set, the one or more LCHs and the one more HARQ processes, for example. The WTRU may transmit the indication to NW with the information on which of the TBs contain PDUs associated with the PDU set. The indication may be transmitted along with the one or more TBs (e g., in the UCI and/or the MAC CE multiplexed with the one or more PUSCHs) or in a separate indication (e g., the UCI in a physical uplink control channel (PUCCH) etc.). For example, the one or more TBs containing the one or more PDUs of the PDU set may include a flag or an ID (e.g , ID and/or index of the PDU set) indicating that the one or more TBs contain inter-dependent data. In another example, the WTRU may select a subset of HARQ process IDs from a configured set of IDs and indicate the selected IDs in the one or more TBs for implicitly indicating to the NW that the TBs contain inter-dependent data.

[01 10] The WTRU may select the repetition pattern to use based on the PDU set profile for repeating the one or more PDUs using resources in the multi-PUSCH configuration In an example, the WTRU may select the repetition pattern, from a preconfigured set of repetition patterns, to use over a configured multi-PUSCH transmission period based on the one or more PDU set profiles. For example, if the size of the PDU set scheduled for transmission during the multi-PUSCH transmission occasions is greater than the payload size threshold and/or if the PSER of the one or more PDU sets is greater than an error threshold (for e.g. the IDC-2023P00722WC threshold PS ER) , the WTRU may determine the number of available PUSCH occasions, including one or more unused occasions not used for carrying any PDUs and/or TBs, within the configured multi-PUSCH that may be used for repetition of the PDUs and/or TBs belonging to the one or more PDU sets. In an example, the WTRU may determine the PUSCH occasion in the multi-PUSCH configuration is not used i.e. is unused if no PDU is scheduled for transmission during the PUSCH occasion and/or if the payload size of one or more PDUs of the one or more PDU sets multiplexed into the PUSCH occasion is below the threshold value. The WTRU may select the repetition pattern to use within the available set of PUSCH occasions which are not used for repeating the transmission of the one or more PDUs in the one or more PDU sets. In an example, the WTRU may select the repetition pattern based on the mapping of the priority of available patterns to the PSER of the PDU set and/or the number of PUSCHs which are not used.

[01 11] In an example, the WTRU may transmit to the network (e.g., in the UCI), one or more indications indicative of the repetition pattern selected and/or used for transmitting the one or more PDUs of the one or more PDU sets. The indication transmitted by the WTRU may include the index or the ID which refers to the repetition pattern from the set of repetition patterns available for the WTRU for retransmission. The indication may also, implicitly or explicitly, include information on the set of used and/or not used and/or used PUSCH occasions in the multi-PUSCH configuration, a subset of which are used for repetition of the one or more PDUs. The indication may also include the one or more HARQ process IDs corresponding to the one or more TBs including the one or more PDUs of the one or more PDU sets which are repeated. The WTRU may multiplex (e g., in the UCI) the indication in the one or more PUSCH occasions during the transmission of the PDUs and/or the one or more TBs

[01 12] The WTRU may dynamically select the number of repetitions for the remaining subset of PDUs in the one or more PDU sets based on the remaining delay and/or the downlink feedback information after initial transmission. In an example, the WTRU may dynamically determine the number of repetitions and/or the repetition repetitions to apply when repeating the transmission of the one or more PDUs in the subset of PDUs based on the indication received from the network (e.g., in the DCI) after initial transmission of the first subset of PDUs of the PDU set. The WTRU may apply repetitions when transmitting the second subset of PDUs and/or subset of PDUs scheduled for transmission in a later period of the multi-PUSCH configuration period.

[01 13] In an example, the WTRU may receive, from the network, the configuration information and/or the one or more parameters associated with the one or more multi-PUSCH configurations (e.g., the number of PUSCH occasions per slot and/or the number of slots per CG period etc.) for transmitting the one or more TBs including the one or more PDUs of the one or more PDU sets. The WTRU may also receive a set of threshold values associated with one or more remaining error budgets for the one or more PDU sets. The WTRU may receive the threshold value related to the remaining delay relative to the PSDB of the corresponding PDU set. [01 14] The WTRU may receive the first subset of PDUs including the one or more PDUs of the one or more PDU sets from the one or more application and/or higher layers and the information associated with the one or more PDU set profiles corresponding to the one or more PDU sets. For example, the first subset of PDUs IDC-2023P00722WQ including the one or more PDUs of the one or more PDU sets may include information (e g., in one or more PDU headers) including but not limited to a PDU set payload size, a total number of PDUs in the PDU set, the PSER and the PSDB. The WTRU may also receive the information including but not limited to a minimum percentage and/or a number of the PDUs in the PDU set which may be received successfully for the PDU set to be successful. The WTRU may use the one or more available resources available in the multi-PUSCH configuration to transmit the first subset of PDUs and/or the one or more TBs belonging to the PDU set.

[01 15] The WTRU may receive the one or more indications from the NW on the first subset of PDUs and/or the one or more TBs of the one or more PDU set. In an example, the WTRU may receive the indication from the NW upon performing transmissions of the first subset of PDUs of the PDU set The indication may provide the feedback information and/or the status of transmission associated with the transmission of the one or more TBs, for example. The indication may be received by the WTRU in the DCI, the DL MAC CE, and/or the RRC signaling, for example. The indication may be received in a single indication (e g., in single DCI) with information associated with the transmission of the one or more TB or in multiple indications where each indication may be associated with the transmission of one TB. The indication received by the WTRU may include but is not limited to one or more HARQ process IDs, NDI information on the associated HARQ process IDs, the one or more resources for retransmission, and/or timing information of the one or more resources for retransmission.

[01 16] For the one or more HARQ process IDs, for example, the information on the one or more HARQ processes (e.g., the IDs) may be provided the single indication or in multiple indications, where each indication may be associated with a HARQ process ID. When providing information on multiple HARQ processes associated with transmissions of multiple TBs, a bitmap format may be used For example, each bit in the bitmap may be associated with a HARQ process ID and may indicate an acknowledgement (ACK) and/or a negative acknowledgement (NACK) status of the transmission of the corresponding TB. The bitmap format may be related to the downlink feedback indication (DFI), for example. For the NDI information on the corresponding HARQ process IDs, for example, if the NDI flag for the HARQ process ID is flipped and/or reset, the WTRU may assume the transmission of the TB associated with the HARQ process ID was successful. The WTRU may release the data in a buffer associated with the HARQ process.

[01 17] For resources for retransmission, the resources for retransmissions may be associated with the one or more HARQ process IDs, wherein the WTRU may use the resources for retransmitting the TBs associated with the HARQ processes. The resources for retransmissions may be the DGs, the CGs or a combination of the DGs and the CGs, for example. In case when the resources are the DGs, the resource information may include but is not limited to any of time domain resource allocation (TDRA) (e g. the PUSCH occasions, a start and length indicator value (SLIV) etc.), frequency domain resource allocation (FDRA) (e.g., number of RBs and/or RBGs etc.) and the one or more transmission parameters (e.g., the MCS, the RV, etc.). In case when the resources are the CGs, the information may include an activation indication of the one or more CG configurations (e.g., the IDs and/or the indexes of the CG configurations), in addition to the TDRA and/or the FDRA. IDC-2023P00722WC

[01 18] For timing information of the resources for retransmission, for example, the one or more PUSCH occasions may be associated with at least one K2 value, where the K2 may indicate the occasion, slot, and/or symbol etc. for performing retransmission of the TB. The timing information may be indicated with respect to a reference occasion, slot, and/or symbol (e.g. SFN) etc., for example.

[01 19] The WTRU determines the repetition pattern to apply on the second subset of PDUs of the PDU set based on the remaining error budget and/or the remaining delay. In an example, the WTRU may receive the second subset of PDUs including the one or more PDUs from the one or more application and/or higher layers. The WTRU may determine the remaining error budget for the PDU set based on the information received from the NW on the status of transmission (e.g the ACK and/or NACK information in the bitmap) of the first subset of PDUs of the PDU set. The remaining error budget may also be determined based on the remaining PDUs to be transmitted in the second subset of the PDU set as well as the one or more PDUs from the first subset of the PDU set scheduled for retransmission. The WTRU may be provided with resources (e.g., the DGs) for retransmission of the one or more PDUs of the first subset of PDUs which may be indicated in a single DCI or in multiple (corresponding to the number of TBs to be retransmitted) DCIs. The resource indication for retransmission may also include timing information for indicating the location when the resource for retransmission is made available. For example, the remaining error budget for the PDU set may be the maximum number of PDUs of the PDUs scheduled for initial transmission and/or retransmission, for which successful reception is not required. The WTRU may determine the delay budget relative to the PDU set based on the remaining TBs and/or the remaining PDUs scheduled for transmission and/or retransmission.

[0120] In an example, the WTRU may dynamically determine a repetition (e.g. the number of repetitions and/or the repetition pattern etc.) to apply when transmitting and/or retransmitting the remaining subset of PDUs using the available DGs allocated for retransmission of the one or more PDUs from the first subset of PDUs and the multi-PUSCH resources based on the configured conditions. For example, if the remaining error budget for the remaining and/or second subset of PDUs of the PDU set is less than the error threshold and/or if the remaining delay relative to the PSDB is below the delay threshold, the WTRU may determine the number of PUSCH occasions which are not used within the resources available in the multi-PUSCH configuration and the DGs allocated for retransmission of the one or more PDUs and/or the one or more TBs corresponding to the first subset of PDUs. Such determination may be done based on the remaining payload size of the one or more PDUs of the PDU set scheduled for initial transmission and/or retransmission. The WTRU may determine the number of repetitions and/or the repetition pattern to use when repeating the transmission of the one or more PDUs from the remaining set of PDUs and/or the second subset of PDUs based on the available PUSCH occasions in the multi-PUSCH configuration, the DG resources, and/or the PSER. In an example, the WTRU may determine the repetition pattern based on a mapping relation preconfigured in a set of tables providing association between the number of available PUSCH occasions and the PSER.

[0121] The WTRU may transmit to network (e.g., in the UCI), the one or more indications associated with the repetition pattern applied for repeating the remaining subset of PDUs of the PDU set. The indication IDC-2023P00722WC transmitted by the WTRU may include the index and/or the ID which refers to the repetition pattern from the set of repetition patterns. The indication may also, implicitly or explicitly, include information on the PUSCH occasions in the multi-PUSCH configuration and the DG resources which are used for repetition of the one or more PDUs and/or the one or more TBs associated with the subset of remaining PDUs and/or the TBs. The indication may also include the one or more HARQ process IDs corresponding to the TBs including the one or more PDUs of the PDU set which are repeated. The WTRU may multiplex (e. g. , in the UCI) the indication in the one or more of the PUSCHs during transmission. If, on the other hand, the remaining error budget is above the error threshold and/or if the remaining delay relative to the PSDB is above the delay threshold, the WTRU may use one or more default transmission parameters with or without repetition when transmitting the remaining PDUs of the PDU set. In an example, the remaining error budget larger than the error threshold may imply that most of the PDUs of the PDU set may have already been successfully received and the WTRU may afford transmitting and/or retransmitting the remaining PDUs with a lower reliability, such as a higher error margin and/or budget, for example. The remaining delay larger than the delay threshold may indicate that the WTRU may afford to wait for receiving the indication from the NW for retransmitting the one or PDUs in the remaining subset of PDUs to achieve the PSER requirement for the PDU set without repetition of the one or more PDUs. [0122] The WTRU may determine the increments and/or decrements for adjusting the MCS index in the multi-PUSCH CG based on the PDU set profile In an example, the WTRU may determine an increment and/or decrement value for adjusting the MCS index for improving the reliability and resource efficiency during transmission of the one or more PDU sets using the multi-PUSCH CG based on the one or more PDU set profiles.

[0123] In an example, the WTRU may receive, from the network, the configuration information and/or the one or more parameters associated with the one or more multi-PUSCH configurations (e.g., the number of PUSCH occasions per slot, the number of slots per CG period etc.) for transmitting the one or more TBs including the one or more PDUs of the one or more PDU sets. The WTRU may receive the set of LCHs associated with the set of PDU set profiles for mapping the one or more PDUs belonging to the same PDU set in one or successive TBs. The WTRU may also receive a set of possible values related to the maximum incremental and/or decremental values to apply for adjusting the MCS index. The WTRU may also receive configuration information including the set of tables and/or mapping relationships relating the PDU set profile, the unused PUSCH occasions (e.g., PUSCH occasions not expected to be used for data transmission) and/or the MCS adjustment to apply.

[0124] The WTRU may receive, from the one or more higher layers, the one or more PDUs of the PDU set and information related to the PDU set profile (e.g., the PSER, the PSDB, the payload size, etc.). The WTRU may determine the mapping of the one or more PDUs in the PDU set to the one or more LCHs based on the corresponding one or more PDU set profiles (e.g., the PSER, the PSDB etc.) to ensure that the one or more PDUs of the PDU set are grouped within the same TB and/or within successive TBs. IDC-2023P00722WC

[0125] In an example, the WTRU may determine the unused PUSCH occasions in the multi-PUSCH CG based on the number of TBs scheduled for transmission and/or the multiplexing the one or more TBs to the one or more PUSCH occasions. For example, depending on arrival for the one or more PDUs from the one or more higher layers (e.g., the application layer etc.) and/or the jitter, the one or more TBs including the one or more PDUs of the one or more PDU sets may be mapped to consecutive PUSCH occasions and/or with the gap of the one or more TOs between the PUSCH occasions Consequently, the one or more unused PUSCH occasions may be in consecutive PUSCH occasions and/or with the gap in between where the one or more used PUSCH occasions occur.

[0126] In an example, the WTRU may use the mapping table for selecting the adjustment (e.g., an index of delta on the MCS index) to apply on a default MCS index based on the one or more PDU set profiles (e.g , the PSER etc.) and/or the one or more unused PUSCH occasions. For example, for the PDU set with the PSER of X% and with Z number of the unused PUSCH occasions in the multi-PUSCH CG, the WTRU may refer to the mapping table to obtain the maximum increment and/or decrement values to apply on the default MCS index to improve reliability and/or efficiency of resource utilization during the transmission of the one or more PDU sets. The WTRU may reevaluate the unused PUSCH occasions based on the updated MCS index which may consequently change the number and/or size of the one or more TBs scheduled within the multi-PUSCH CG. Based on the newly reevaluated unused PUSCH occasions and/or the updated applied to the MCS index, the WTRU may determine the repetition pattern to apply for repeating the one or more PDUs of the PDU set. Such approach may aim to improve reliability and/or improve resource utilization during transmission of the one or more PDUs and/or the one or more TBs using higher MCS values by using the repetition pattern that may ensure higher number of repetitions, while during transmissions employing lower MCS values may use the repetition pattern with lower number of repetitions, for example

[0127] The WTRU may transmit to the network (e.g., in the UCI), the one or more indications associated with the update applied to the MCS index and/or the repetition pattern used for transmitting the one or more PDUs of the one or more PDU sets. The indication may also, implicitly or explicitly, include the set of unused PUSCH occasions in the multi-PUSCH configuration, the subset of which are used for repetition of the one or more PDUs. The indication may also include the one or more HARQ process IDs corresponding to the one or more TBs containing the one or more PDUs of the one or more PDU sets which are repeated. The WTRU may multiplex (e.g., in the UCI) the indication regarding the MCS adjustment and/or repetition of the one or more PDUs during the transmission of the first PUSCH occasion.

[0128] Although features and elements are described 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. In addition, the methods described 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, magnetooptical 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.

Claims

IDC-2023P00722WC CLAIMS What is Claimed:

1. A method performed by a wireless transmit/receive unit (WTRU), the method comprising: receiving configuration information comprising a plurality of Configured Grant (CG) Physical Uplink Shared Channel (PUSCH) occasions; transmitting an indication of one or more transmission parameters associated with one or more Protocol Data Units (PDUs) of at least one PDU set, wherein the one or more transmission parameters are determined based on the configuration information and a plurality of PDU set attributes associated with the at least one PDU set; and transmitting the one or more PDUs in one or more CG PUSCH occasions of the plurality of CG PUSCH occasions based on the one or more transmission parameters.

2. The method of claim 1 , wherein the one or more transmission parameters include at least one repetition pattern.

3. The method of claim 1 , wherein the configuration information further comprises one or more of: a threshold PDU Set Error Rate (PSER), a threshold PDU set size, a set of repetition patterns, wherein each repetition pattern in the set of repetition patterns is associated with a priority, or a maximum number of repetitions.

4. The method of claim 3, the method further comprising: determining one or more used CG PUSCH occasions and one or more unused CG PUSCH occasions from the plurality of CG PUSCH occasions.

5. The method of claim 4, the method further comprising: selecting a repetition pattern from the set of repetition patterns based on the plurality of PDU set attributes, a number of the one or more unused CG PUSCH occasions, and at least one threshold; and determining a number of repetitions based on the maximum number of repetitions and the plurality of PDU set attributes.

6. The method of claim 5, wherein the one or more transmission parameters are indicative of at least one of: the selected repetition pattern or the determined number of repetitions.

7. The method of claim 5, the method further comprising: retransmitting the one or more PDUs in the one or more unused CG PUSCH occasions based on at least one of: the selected repetition pattern or the determined number of repetitions.

8. The method of claim 3, the method further comprising: determining a PDU set size associated with the at least one PDU set; and determining the one or more transmission parameters based on a comparison of the threshold PDU set size with the PDU set size. IDC-2023P00722WC

9. The method of claim 3, the method further comprising: determining a PSER associated with the at least one PDU set; and determining the one or more transmission parameters based on a comparison of the threshold PSER with the determined PSER.

10. The method of claim 1, wherein the indication is transmitted in an Uplink Control Information (UCI).

11. A wireless transmit/receive unit (WTRU), comprising: a memory configured to store one or more Protocol Data Units (PDUs) of at least one PDU set; a transceiver configured to: receive configuration information comprising a plurality of Configured Grant (CG) Physical

Uplink Shared Channel (PUSCH) occasions, and transmit an indication of one or more transmission parameters associated with the one or more PDUs; and a processor configured to: determine the one or more transmission parameters based on the configuration information and a plurality of PDU set attributes associated with the at least one PDU set, wherein the one or more PDUs are transmitted in one or more CG PUSCH occasions of the plurality of CG PUSCH occasions based on the one or more transmission parameters.

12. The WTRU of claim 11 , wherein the one or more transmission parameters include at least one repetition pattern.

13. The WTRU of claim 11 , wherein the configuration information further comprises one or more of: a threshold PDU Set Error Rate (PSER), a threshold PDU set size, a set of repetition patterns, wherein each repetition pattern in the set of repetition patterns is associated with a priority, or a maximum number of repetitions.

14. The WTRU of claim 13, wherein the processor is configured to: determine one or more used CG PUSCH occasions and one or more unused CG PUSCH occasions from the plurality of CG PUSCH occasions.

15. The WTRU of claim 14, wherein the processor is further configured to: select a repetition pattern from the set of repetition patterns based on the plurality of PDU set attributes, a number of the one or more unused CG PUSCH occasions, and at least one threshold, and determine a number of repetitions based on the maximum number of repetitions and the plurality of PDU set attributes.

16. The WTRU of claim 15, wherein the one or more transmission parameters are indicative of at least one of: the selected repetition pattern or the determined number of repetitions.

17. The WTRU of claim 15, wherein the transceiver is configured to: IDC-2023P00722WC retransmit the one or more PDUs in the one or more unused CG PUSCH occasions based on at least one of: the selected repetition pattern or the determined number of repetitions.

18. The WTRU of claim 13, wherein the processor is further configured to: determine a PDU set size associated with the at least one PDU set, and determine the one or more transmission parameters based on a comparison of the threshold PDU set size with the PDU set size.

19. The WTRU of claim 13, wherein the processor is further configured to: determine a PSER associated with the at least one PDU set, and determine the one or more transmission parameters based on a comparison of the threshold PSER with the determined PSER.

20. The WTRU of claim 11 , wherein the indication is transmitted in an Uplink Control Information (UCI).