Uplink transmission enhancement for radio link control data in extended reality

Abstract

Systems, methods, and instrumentalities are disclosed herein for an uplink enhancement procedure. A device, such as a wireless transmit / receive unit (WTRU) may receive configuration information from a network. The configuration information may indicate a condition to trigger an uplink enhancement. In some examples, the uplink enhancement may be associated with a radio link control (RLC) enhancement. In some examples, the uplink enhancement may be associated with (e.g., may be further associated with) a medium access control (MAC) enhancement. The device may receive a data set associated with an uplink transmission. The device may determine whether to perform the uplink enhancement based on the configuration information. Based on a determination to perform the uplink enhancement, the device may perform the uplink transmission using the uplink enhancement.

Description

UPLINK TRANSMISSION ENHANCEMENT FOR RADIO LINK CONTROL DATA IN EXTENDED REALITYCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 572,469, filed on April 1 , 2024, the contents of which are incorporated by reference herein.BACKGROUND

[0002] Mobile communications using wireless communication continue to evolve. A fifth generation of mobile communication radio access technology (RAT) may be referred to as 5G new radio (NR). A previous (legacy) generation of mobile communication RAT may be, for example, fourth generation (4G) long term evolution (LTE).SUMMARY

[0003] Systems, methods, and instrumentalities are disclosed herein for an uplink enhancement procedure. For example, a device, such as a wireless transmit / receive unit (WTRU), may include a processor that is configured to perform one or more of the following.

[0004] The device may receive configuration information from a network. The network described herein may be, or may include, one or more of the following: a base station, a gNB, a transmission / reception point, a radio access network node, an access node, a core network function, or an application function. The configuration information may indicate a condition to trigger an uplink enhancement. In some examples, the uplink enhancement may be associated with a radio link control (RLC) enhancement. In some examples, the uplink enhancement may be associated with (e.g., may be further associated with) a medium access control (MAC) enhancement.

[0005] In some examples, the configuration information may include one or more of the following: a timer, a threshold value associated with the importance of at least one of an RLC PDU or a PDU segment, a threshold value associated with a quality of service (QoS) parameter for the data set, a threshold value associated with aparameter for a resource block (RB), a threshold value associated with a parameter for a logical channel (LCH), or a triggering condition associated with the performance of the uplink enhancement. The threshold value associated with the QoS parameter may be, or may include, one or more of the following: a packet delay budget (PDB) parameter, a PDU set delay budget (PSDB) parameter, a PDU Set Delay Deadline (PSDD) parameter, an importance parameter, or a priority parameter. The threshold value associated with the parameter for at least one of the RB or the LCH may be, or may include, one or more of the following: a priority parameter, a parameter associated with a prioritized bit rate (PBR), or a discard timer. The triggering condition described herein may be associated with receiving a number of Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgements (NACKs) for an RLC PDU or a PDU segment.

[0006] The device may receive a data set associated with an uplink transmission. The data set may be, or may include, one or more of the following: an RLC protocol data unit (PDU) or a PDU segment. Performing the uplink transmission using the uplink enhancement as described herein may include the device being configured to perform retransmission of at least one of the RLC PDU or the PDU segment.

[0007] The device may determine whether to perform the uplink enhancement based on the configuration information. The determination of whether to perform the uplink enhancement may be based on whether the condition is satisfied.

[0008] Based on a determination to perform the uplink enhancement, the device may perform the uplink transmission using the uplink enhancement.

[0009] In some examples, the configuration information may include a timer. The device may initiate the timer based on one or more of the following: the reception of an RLC service data unit (SDU), the transmission of at least one of an RLC PDU or a PDU segment to a MAC layer, or the transmission of a MAC PDU that is associated with at least one of the RLC PDU or the PDU segment. The device may determine whether the timer has expired. The condition may be satisfied based on a determination that the timer has expired.

[0010] In some examples, the configuration information may include a threshold value associated with the importance of at least one of an RLC PDU or a PDU segment. The device may determine that the threshold value associated with the importance of at least one of the RLC PDU or the PDU segment is above a configured threshold value. Based on the determination that the threshold value is above the configured threshold value, the device may enable polling of at least one of the RLC PDU or the PDU segment.

[0011] In some examples, determining whether to perform the uplink enhancement may include the device being configured to perform one or more of the following. The device may determine whether a QoSassociated with the data set is above a threshold value. The threshold value may be associated with a QoS parameter. The condition may be satisfied based on a determination that the QoS associated with the data set is above the threshold value. The device may determine whether a parameter associated with an RB is above the threshold value. The threshold value may be associated with the parameter for the RB. The condition may be satisfied based on a determination that the parameter associated with the RB is above the threshold value. The device may determine whether a parameter associated with an LCH is above the threshold value. The threshold value may be associated with the parameter for the LCH. The condition may be satisfied based on a determination that the parameter associated with the LCH is above the threshold value. The device may determine whether a triggering condition has been satisfied.

[0012] Systems, methods, and instrumentalities are disclosed herein for extended reality (XR). For example, a device, such as a wireless transmit / receive unit (WTRU) may be configured for an uplink (UL) transmission (e.g., UL transmission enhancement) for radio link control (RLC) data in XR.

[0013] In some examples, a WTRU may perform RLC enhancement for a data set by performing one or more additional RLC procedures and / or adapting / overriding one or more RLC parameters. The WTRU may inform a base station and / or a network regarding adapting one or more RLC parameters for the RLC enhancement.

[0014] In some examples, the WTRU may perform MAC enhancement for a data set by performing additional MAC procedure and / or by adapting / overriding one or more MAC parameters. The WTRU may inform the base station and / or the network regarding adapting one or more MAC parameters for the MAC enhancement.

[0015] The WTRU may perform a UL enhancement based on quality of service (QoS) of the data set and / or may perform a UL enhancement procedure based on a parameter of a resource block (RB) and / or a logical channel (LCH) of the data set.

[0016] The WTRU may perform the UL enhancement for a data set based on an indication, e.g., from the network and / or based on a triggering event.

[0017] The WTRU may determine which data set to perform uplink enhancement. The WTRU may send an indication regarding a UL enhancement transmission. In some examples, the WTRU may be prohibited from performing the UL enhancement.

[0018] In some examples, the WTRU may receive a configuration from a network, such as a gNB. The configuration is associated with triggering uplink enhancement. The configuration may be, or may include, atleast one of a threshold value associated with a QoS parameter for the data set, a threshold value associated with a parameter for an RB, a threshold value associated with a parameter for a LCH, or a triggering condition associated with the performance of uplink enhancement.

[0019] The threshold value associated with the QoS parameter may be, or may include, at least one of a packet delay budget (PDB) parameter, a protocol data unit (PDU) set delay budget (PSDB) parameter, a PDU Set Delay Deadline (PSDD) parameter, an importance parameter, or a priority parameter.

[0020] The threshold value associated with the parameter for at least one of the RB or the LCH may be, or may include, at least one of a priority parameter, a parameter associated with prioritized bit rate (PBR), or a discard timer.

[0021] The triggering condition may be associated with receiving a number of Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgements (NACKs) for a radio link control (RLC) PDU or PDU segment.

[0022] The WTRU may receive a data set associated with an uplink transmission. The data set may be, or may include, at least one of a PDU segment, an RLC PDU segment, a PDU, a subset of a PDU set, a PDU set, or a data burst.

[0023] The WTRU may determine whether to perform uplink enhancement. In some examples, the WTRU may determine whether a QoS associated with the data set satisfies the threshold value associated with the QoS parameter. In some examples, the WTRU may determine whether the parameter for the RB satisfies the threshold value associated with the parameter for the RB. In some examples, the WTRU may determine whether the parameter for the LCH satisfies the threshold value associated with the parameter for the LCH. In some examples, the WTRU may determine whether the triggering condition has been satisfied.

[0024] Based on a determination, the WTRU may perform the uplink transmission of the data set using uplink enhancement. Uplink enhancement may be associated with at least one of an RLC enhancement or a medium access control (MAC) enhancement.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0026] 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. 1 A according to an embodiment.

[0027] FIG. 1 C 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. 1 A according to an embodiment.

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

[0029] FIG. 2 illustrates an example of performing an uplink enhancement procedure.DETAILED DESCRIPTION

[0030] 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), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0031] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include 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 commercialand / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0032] 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 / 115, the I nternet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a 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.

[0033] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in 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.

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

[0035] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC- FDMA, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 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 UL Packet Access (HSUPA).

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

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

[0038] 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., a eNB and a gNB).

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

[0040] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In 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 / 115.

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

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

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

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

[0045] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 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.

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

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

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

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

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

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

[0052] 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 hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0053] 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 downlink(e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 1 18). In an embodiment, the WRTU 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 downlink (e.g., for reception)).

[0054] FIG. 1 C 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 CN 106.

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

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

[0057] The CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of 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.

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

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

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

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

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

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

[0064] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic 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.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (e.g., all ofthe STAs) within or using the I BSS may communicate directly with each other. The I BSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0065] 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 via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example, in 802.11 systems. For CSMA / CA, the STAs (e.g., every ST A), 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.

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

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

[0068] Sub 1 GHz modes of operation are supported by 802.11af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac. 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, 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 limitedbandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0069] WLAN systems, which may support multiple channels and channel bandwidths, such as 802.11 n, 802.11 ac, 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 ST As in the BSS. The bandwidth of the primary channel may be set and / or limited by a ST A, 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 a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0070] 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.11 ah is 6 MHz to 26 MHz depending on the country code.

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

[0072] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In 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).

[0073] 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 varying number of OFDM symbols and / or lasting varying lengths of absolute time).

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

[0075] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane 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. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

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

[0077] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b 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 machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

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

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

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

[0081] In view of Figures 1A-1D, and the corresponding description of Figures 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.

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

[0083] 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 testing 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.

[0084] Systems, methods, and instrumentalities are disclosed herein for an uplink enhancement procedure. For example, a device, such as a wireless transmit / receive unit (WTRU), may include a processor that is configured to perform one or more of the following.

[0085] The device may receive configuration information from a network. The network described herein may be, or may include, one or more of the following: a base station, a gNB, a transmission / reception point, a radio access network node, an access node, a core network function, or an application function. The configuration information may indicate a condition to trigger an uplink enhancement. In some examples, the uplink enhancement may be associated with a radio link control (RLC) enhancement. In some examples, the uplinkenhancement may be associated with (e.g., may be further associated with) a medium access control (MAC) enhancement.

[0086] In some examples, the configuration information may include one or more of the following: a timer, a threshold value associated with the importance of at least one of an RLC PDU or a PDU segment, a threshold value associated with a quality of service (QoS) parameter for the data set, a threshold value associated with a parameter for a resource block (RB), a threshold value associated with a parameter for a logical channel (LCH), or a triggering condition associated with the performance of the uplink enhancement. The threshold value associated with the QoS parameter may be, or may include, one or more of the following: a packet delay budget (PDB) parameter, a PDU set delay budget (PSDB) parameter, a PDU Set Delay Deadline (PSDD) parameter, an importance parameter, or a priority parameter. The threshold value associated with the parameter for at least one of the RB or the LCH may be, or may include, one or more of the following: a priority parameter, a parameter associated with a prioritized bit rate (PBR), or a discard timer. The triggering condition described herein may be associated with receiving a number of Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgements (NACKs) for an RLC PDU or a PDU segment.

[0087] The device may receive a data set associated with an uplink transmission. The data set may be, or may include, one or more of the following: an RLC protocol data unit (PDU) or a PDU segment. Performing the uplink transmission using the uplink enhancement as described herein may include the device being configured to perform retransmission of at least one of the RLC PDU or the PDU segment.

[0088] The device may determine whether to perform the uplink enhancement based on the configuration information. The determination of whether to perform the uplink enhancement may be based on whether the condition is satisfied.

[0089] Based on a determination to perform the uplink enhancement, the device may perform the uplink transmission using the uplink enhancement.

[0090] In some examples, the configuration information may include a timer. The device may initiate the timer based on one or more of the following: the reception of an RLC service data unit (SDU), the transmission of at least one of an RLC PDU or a PDU segment to a MAC layer, or the transmission of a MAC PDU that is associated with at least one of the RLC PDU or the PDU segment. The device may determine whether the timer has expired. The condition may be satisfied based on a determination that the timer has expired.

[0091] In some examples, the configuration information may include a threshold value associated with the importance of at least one of an RLC PDU or a PDU segment. The device may determine that the thresholdvalue associated with the importance of at least one of the RLC PDU or the PDU segment is above a configured threshold value. Based on the determination that the threshold value is above the configured threshold value, the device may enable polling of at least one of the RLC PDU or the PDU segment.In some examples, determining whether to perform the uplink enhancement may include the device being configured to perform one or more of the following. The device may determine whether a QoS associated with the data set is above a threshold value. The threshold value may be associated with a QoS parameter. The condition may be satisfied based on a determination that the QoS associated with the data set is above the threshold value. The device may determine whether a parameter associated with an RB is above the threshold value. The threshold value may be associated with the parameter for the RB. The condition may be satisfied based on a determination that the parameter associated with the RB is above the threshold value. The device may determine whether a parameter associated with an LCH is above the threshold value. The threshold value may be associated with the parameter for the LCH. The condition may be satisfied based on a determination that the parameter associated with the LCH is above the threshold value. The device may determine whether a triggering condition has been satisfied. A device, such as a WTRU, may configure radio link control (RLC) acknowledgement mode (AM) operation, e.g., in a new radio (NR) system.

[0092] For example, an RLC AM may work according to (e.g., based on) a transmitting / receiving windowbased operation, in which one or more (e.g., all) protocol data units (PDUs) transmitted from the transmission (Tx) to the reception (Rx) may be guaranteed to be received successfully and acknowledged by the Rx RLC entity. An RLC PDU may have an associated sequence number (SN), and Tx and Rx may maintain their own transmission and reception window with a size of AM_Window_Size. The Tx WTRU may not be allowed to transmit more data if the gap between the acknowledged SN and the current SN is greater than the window size.

[0093] The acknowledgement procedure may be implemented according to (e.g., based on) the pollingresponse procedure, in which the RLC AM transmission entity may poll the status of the transmitted PDU after a configured number of transmitted PDUs (e.g, pollPDUs) and / or transmitted bytes (e.g, pollBytes).

[0094] An RLC AM transmission entity may be allowed to poll the RLC AM reception entity if one or more of the following conditions are satisfied (e.g, are met): the amount of data without polling is larger than a threshold (e.g, PDU_WITHOUT_POLL >= pollPDU; or BYTE_WITHOUT_POLL >= pollByte); the buffer (e.g, initial and / or retransmission buffer) may be empty after the current PDU; and / or a window may be stalling (e.g, if the gap between the current SN and the acknowledged (ACKED) SN is greater than the window size).

[0095] Upon reception of a negative acknowledgement (NACK) feedback in the STATUS PDU of an RLC PDU, the WTRU may consider the RLC PDU for retransmission. The WTRU may retransmit the PDU along with a polling request, e.g., if the t-Pollretransmit timer expires and the WTRU has not received a positive acknowledgement (ACK) from the receiver. If the number of retransmissions reaches a threshold, e.g., a maximumThreshold, the RLC entity may indicate this (e.g., the number of retransmissions reaching the maximumThreshold) to an upper layer and may declare radio link failure (RLF).

[0096] At the RLC AM reception, the entity may send a control RLC PDU (e.g., STATUS PDU) to the RLC AM transmission entity. The control RLC PDU (e.g., STATUS PDU ) may be configured to indicate until which PDU (e.g., segment) has received an ACK and / or which PDU (e.g., segment) has not received correctly (e.g., NACK) if the RLC AM reception entity receives the poll request from Tx and / or if the timer to assemble a PDU segment (e.g., t-Reassembly) expires. To control the frequency of STATUS report transmission, the WTRU may transmit (e.g., may be allowed to transmit) the STATUS report if the StatusProhibit (e.g., a timer associated with the status report transmission) has expired.

[0097] The term extended Reality (XR) may be an umbrella term for different types of immersive experiences including Virtual Reality (VR), Augmented Reality (AR) and Mixed Reality (MR), and / or the realities interpolated among them. VR may be a rendered version of a delivered visual and audio scene. The rendering may be designed to mimic the visual (e.g., stereoscopic 3D) and audio sensory stimuli of the real world as naturally as possible for an observer or a user as the observer / user moves within the limits defined by the application. AR may be when a user is provided with additional information or artificially generated objects / items or content overlaid upon the current environment. MR may be an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that the elements are part of the real scene. XR may include to one or more (e.g., all) real-and-virtual combined environments and human-machine interactions generated, e.g., by computer technology and / or wearables.

[0098] The notion of immersion in the context of XR ap plicatio ns / services may refer to the sense of being surrounded by the virtual environment as well as providing the feeling of being physically and / or spatially located in the virtual environment. The levels of virtuality may range from partial sensory inputs to fully immersive multi-sensory inputs, leading to a virtual reality practically indiscernible from actual reality.

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

[0100] In an XR application, the WTRU may transmit XR traffic, including one or more PDUs / PDU sets in UL (e.g, pose, gesture, video data, and / or the like) and / or receive XR traffic in DL (video, audio, haptics, and / or the like). Such traffic may be transmitted and / or received periodically or aperiodically in one or more data flows (e.g, quality of service (QoS) flows). During one or more UL transmissions, XR traffic may arrive from an application layer at the WTRU and / or from different devices / terminals / WTRUs (e.g, via sidelink) at different time instances. Such XR traffic may be characterized by different attributes, such as: variable payload sizes per PDU set, a variable number of PDUs per PDU set, variable per-PDU / PDU set level importance, and / or different levels of inter-dependencies between PDUs / PDU sets. Such XR traffic (e.g, PDU / PDU sets) received by the WTRU may also experience different delays, jitter, data rate, and / or loss rate. To ensure QoS and / or a high user experience (e.g, quality of experience (QoE)), data transmission / reception and / or other associated functions (e.g, prioritization, multiplexing, scheduling, and / or the like) may be done on a timely basis with XR awareness (e.g, awareness of PDU set attributes).

[0101] One or more characteristics of XR for decoding operation may be configured.

[0102] For example, in XR, a PDU set, which may be, or may include, one or more inter-dependent PDUs, may be introduced. One or more XR applications may support the following types of PDU sets: reliable delivery of one or more (e.g, all) PDUs in the set; conditional delivery, e.g, the transmission of a PDU set is unsuccessful if at least one (e.g, possibly specific) PDU fails transmission; and / or X out of Y, such as the transmission of a PDU set is successful if X PDUs of the PDU set out of Y PDUs are received. For example, if Forward Error Correction (FEC) is used and / or if additional layered encoding is used and assigned to the same PDU set, the XR application (s) may support X out of Y types of PDU sets described herein.

[0103] An example RLC AM process may be configured. For example, in an NR RLC AM system, the acknowledgement process may be implemented, e.g, according to the polling-response procedure described herein. For example, the RLC AM transmission entity may poll the status of the RLC PDU and / or RLC PDU segment after a configured number of transmitted PDUs and / or bytes. Upon reception of a poll request, the RLC AM reception entity may generate a status report to indicate the reception status of the RLC AM reception entity. Such polling-response process may result in large latency overhead, which may not be suitable for low latency data sets (e.g, PDU segment, PDU, a subset of a PDU set, a PDU set, and / or a data Burst).

[0104] A UL procedure (e.g., RLC, MAC, and / or the like) for transmission of a data set (e.g, a PDU segment, PDU, a subset of a PDU set, a PDU set, and / or the like) associated with an RLC (e.g., an AM RLC) may be configured (e.g., enhanced), e.g, to reduce latency.

[0105] In some examples, a WTRU may perform a UL enhancement procedure (e.g, RLC enhancement, MAC enhancement, and / or the like) for a data set (e.g, a PDU segment, PDU, a subset of a PDU set, a PDU set, and / or a data burst), e.g, as a function of the QoS of the data set, one or more configured parameters of the resource block (RB) and / or logical channel (LCH) associated with the data set, and / or a configured triggering condition.

[0106] The WTRU may receive one or more of the following configurations (e.g, configuration information) from a base station (e.g, gNB) and / or a network (e.g, in a radio resource control (RRC) message): a threshold associated with a QoS parameter of a data set to trigger uplink enhancement; a threshold associated with a parameter for the RB / LCH to trigger uplink enhancement; and / or a triggering condition to perform UL enhancement. In some examples, the base station and / or the network may be, or may include, one or more of the following: a base station, a gNB, a transmission / reception point, a radio access network node, an access node, a core network function, or an application function.

[0107] In some example, the WTRU may receive a threshold associated with a QoS parameter of a data set (e.g, packet delay budget (PDB) parameter, PDU set delay budget (PSDB) parameter, PDU set delay deadline (PSDD) parameter, importance parameter, priority parameter, etc.) to trigger UL enhancement (e.g, RLC, MAC enhancement, and / or the like). For example, the WTRU may receive a configuration of a remaining PSDB threshold.

[0108] In some examples, the WTRU may receive a threshold associated with a parameter for the RB / LCH (e.g, priority parameter, prioritized bit rate (PBR) parameter, DiscardTimer, and / or the like) to trigger uplink enhancement. For example, the WTRU may receive a configuration of which RB / LCH is enabled for (e.g, to enable) uplink enhancement.

[0109] In some examples, the WTRU may receive a triggering condition to perform uplink enhancement (e.g, RLC, MAC enhancement, and / or the like) for transmission of the data set. For example, the WTRU may receive a configuration (e.g, configuration information) of a timer, a threshold value associated with an importance of the data set (e.g, the importance of at least one of an RLC PDU or a PDU segment), the number of Hybrid Automatic Repeat Request (HARQ) NACKs for the RLC PDU or PDU segment to trigger the retransmission of the RLC PDU.

[0110] In some examples, the device, such as the WTRU, may receive configuration information. The configuration information may include one or more of the following: a timer, a threshold value associated with the importance of at least one of an RLC PDU or a PDU segment, a threshold value associated with a quality of service (QoS) parameter for the data set, a threshold value associated with a parameter for a resource block (RB), a threshold value associated with a parameter for a logical channel (LCH), or a triggering condition associated with the performance of the uplink enhancement. The threshold value associated with the QoS parameter may be, or may include, one or more of the following: a packet delay budget (PDB) parameter, a PDU set delay budget (PSDB) parameter, a PDU Set Delay Deadline (PSDD) parameter, an importance parameter, or a priority parameter. The threshold value associated with the parameter for at least one of the RB or the LCH may be, or may include, one or more of the following: a priority parameter, a parameter associated with a prioritized bit rate (PBR), or a discard timer. The triggering condition described herein may be associated with receiving a number of Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgements (NACKs) for an RLC PDU or a PDU segment.

[0111] The WTRU may receive a data set, e.g., from an upper layer. As described herein, the data set may be, or may include, one or more of the following: an RLC PDU or a PDU segment. Performing the uplink transmission using the uplink enhancement as described herein may include the device being configured to perform retransmission of at least one of the RLC PDU or the PDU segment.

[0112] The WTRU may determine whether to perform an uplink enhancement procedure for the data set. For example, the WTRU ay determine whether to perform the uplink enhancement based on the configuration information (e.g., one or more configurations). The determination of whether to perform the uplink enhancement may be based on whether the condition is satisfied.

[0113] In some examples, the WTRU may determine whether to perform an uplink enhancement procedure for the data set if the QoS of the data set satisfies the configured threshold, a parameter of the RB / LCH associated with the data set satisfies the configured threshold, and / or the triggering condition is satisfied.

[0114] For RLC enhancement, the WTRU may perform WTRU autonomous RLC retransmission (e.g., without waiting for a report, such as a PDU STATUS report) of an RLC PDU if the PSDB of the PDU is smaller than a threshold. The WTRU may perform an RLC retransmission if the WTRU receives a configured number of HARQ NACK associated with the RLC PDU.

[0115] For the MAC enhancement, the WTRU may override logical control prioritization (LCP) restriction. The LCP restriction may prohibit data from an RB / LCH from using the grant. By overriding the LCP restriction, an RLC PDU may be configured (e.g., allowed) to be transmitted in a restricted grant.

[0116] Based on a determination to perform the uplink enhancement, the device may perform the uplink transmission using the uplink enhancement. The WTRU may perform one or more UL transmissions of the data set.

[0117] In some examples, the configuration information may include a timer. The device may initiate the timer based on one or more of the following: the reception of an RLC service data unit (SDU), the transmission of at least one of an RLC PDU or a PDU segment to a MAC layer, or the transmission of a MAC PDU that is associated with at least one of the RLC PDU or the PDU segment. The device may determine whether the timer has expired. The condition may be satisfied based on a determination that the timer has expired.

[0118] In some examples, the configuration information may include a threshold value associated with the importance of at least one of an RLC PDU or a PDU segment. The device may determine that the threshold value associated with the importance of at least one of the RLC PDU or the PDU segment is above a configured threshold value. Based on the determination that the threshold value is above the configured threshold value, the device may enable polling of at least one of the RLC PDU or the PDU segment.

[0119] In some examples, determining whether to perform the uplink enhancement may include the device being configured to perform one or more of the following. The device may determine whether a QoS associated with the data set is above a threshold value. The threshold value may be associated with a QoS parameter. The condition may be satisfied based on a determination that the QoS associated with the data set is above the threshold value. The device may determine whether a parameter associated with an RB is above the threshold value. The threshold value may be associated with the parameter for the RB. The condition may be satisfied based on a determination that the parameter associated with the RB is above the threshold value. The device may determine whether a parameter associated with an LCH is above the threshold value. The threshold value may be associated with the parameter for the LCH. The condition may be satisfied based on a determination that the parameter associated with the LCH is above the threshold value. The device may determine whether a triggering condition has been satisfied.

[0120] The one or more processes described herein may allow the WTRU to perform (e.g., proactively perform) uplink enhancement for a data set, e.g., to improve the successful reception probability at the receiver within the delay budget of the data set. For example, the one or more processes described herein may allow the WTRU to retransmit (e.g., dynamically retransmit) a high-importance RLC PDU instead of and / or in addition to waiting for NACK feedback from the base station and / or the network.

[0121] As described herein, the term “a network” may be, or may include, at least one of the following: a base station (e.g., a gNB, a Transmission / Reception Point (TRP), a RAN node, an access node, and / or thelike), a core network function (e.g., an Access Management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), a Network Exposure Function (NEF), and / or the like) and / or an application function (e.g., an edge server function, a remote server function, and / or the like), for example.

[0122] As described herein, a WTRU may correspond to an XR device and / or an XR node, which may come in a variety of form factors. A typical WTRU (e.g., an XR WTRU) may be, or may include, one or more of the following: Head Mounted Displays (HMDs), optical see-through glasses and / or camera see-through HMDs for AR and MR, mobile devices with positional tracking and a camera, wearables, haptic gloves, a haptic body suit, haptic shoes, etc. In addition to the above, one or more different types of XR WTRUs may be envisioned based on XR device functions, e.g., as a display, a camera, one or more sensors, sensor processing, wireless connectivity, XR / Media processing, and / or power supply, to be provided by one or more devices, wearables, actuators, controllers and / or accessories. One or more devices, nodes, and / or WTRUs may be grouped into a collaborative XR group for supporting one or more of XR applications, experiences, and / or services.

[0123] As described herein, an uplink enhancement process may enhance a UL transmission of the WTRU. Uplink enhancement process described herein (e.g., for a UL transmission associated with the WTRU) may be applicable to sidelink (SL) operation, such as SL enhancement. For example, the network may be replaced by another WTRU. The WTRU, e.g., instead of transmitting / receiving to / from the network, may transmit / receive to / from another WTRU, e.g., for SL operation.

[0124] As described herein, the term “the WTRU may be configured with something” may be used to indicate that the WTRU is preconfigured with something and / or that the WTRU may receive a network configuration of something. The network configuration may be received via at least one of the following: a System Information Block (SIB), a dedicated RRC message, a medium access control (MAC) control element (CE), and / or downlink control information (DCI). For example, the WTRU is configured with a threshold is equivalent to the WTRU is preconfigured (e.g., the WTRU stores the configuration) with the threshold or the WTRU receives the threshold, from the network, via a SIB, an RRC, a MAC CE, and / or DCI.

[0125] As described herein, a PDU set may refer to a PDU set in its integrity and / or one or more PDUs that make up the PDU set. For example, a PDU set may be, or may include, one or more PDUs that make up the PDU set. At an application, a PDU set (e.g., one or more (e.g., all) PDUs making up the PDU set) may be considered as one frame. A PDU set may be, or may include, one or more PDUs. One or more PDU sets may be of the PDU Set Integrated Handling Indication (PSIHI) type, e.g., one or more (e.g., all) PDUs of the PDU set may be needed at the application by the PSDB and / or PSDD for the application to be able to decode the PDU set. Other PDU sets may not be of the PSIHI type, e.g., the application may still be able to decode thePDU set if some PDUs of the PDU set (e.g., within the PDU set) are lost and / or delayed beyond the PSDB and / or PSDD. In some examples, successful reception of, for example, 80% of the PDUs of the PDU set may be sufficient for successful decoding of the PDU set at the application. In other examples, successful reception of, for example, 70% of the PDUs of the PDU set may be sufficient for successful decoding of the PDU set at the application.

[0126] A data burst may refer to data produced by an application, e.g., in a short period of time. The data burst may be, or may include one or more PDUs from one or more PDU sets. Such attributes, associations, and / or inter-dependencies (e.g., intra-PDU set and / or inter-PDU set), including the start / end indication of a PDU set / data burst (e.g., via sequence number, start / end indication, timestamp, and / or the like), start / end time, duration, payload sizes, periodicity, importance / priority and QoS (e.g., PSDB) may be visible to the AS layers (e.g., with associated IDs) and / or handled at the AS layers with awareness of the association during data transmission in UL and reception in DL.

[0127] As described herein, a data set may be used to represent a PDU segment (e.g., an RLC PDU segment), one or more PDUs, a subset of a PDU set, a PDU set, a data burst, and / or the like.

[0128] As described herein, QoS associated with a data set may be used to indicate one or more of the following: one or more parameters (e.g., QoS parameters) of a PDU or PDU segment associated with the data set; one or more parameters of a PDU set (e.g., QoS parameters) associated with the data set; and / or one or more parameters of a data burst associated with the data set.

[0129] In some examples, in one or more parameters (e.g., QoS parameters) of a PDU and / or PDU segment associated with the data set, the parameters of the PDU and / or PDU segment may include one or more of the following: PDU importance; priority; latency parameter (e.g., latency requirement) of the PDU and / or PDU segment; reliability parameter (e.g., reliability requirement) of the PDU (e.g., packet error rate (PER)); maximum data burst volume (MDBV); the type of PDU and / or the type of PDU segment (e.g., periodic vs. aperiodic); the periodicity of the PDU and / or PDU segment; and / or the size of the PDU or PDU segment.

[0130] PDU importance may be used to indicate the importance of the PDU set associated with the PDU, the relative importance of the PDU in the PDU set, the relative importance of the PDU in a data burst, and / or the relative importance of the in the QoS flow.

[0131] A latency parameter (e.g., latency requirement) of the PDU and / or PDU segment may include the packet delay budget (PDB) and / or the remaining PDB.

[0132] In some examples, in one or more parameters of a PDU set (e.g, QoS parameters) associated with the data set, the parameters of the PDU set may include one or more of the following: PDU set importance; PDU set priority; latency parameter (e.g., latency requirement) associated with the PDU set; PDU set integrated handling indication (PSI HI); the type of the PDU set; reliability parameter (e.g., reliability requirement) of a PDU set such as PDU Set Error Rate (PSER); the volume of the PDU set; the type of PDU (e.g, periodic vs. aperiodic); the periodicity of the PDU set; and / or the type of frame that the PDU set may correspond to (e.g, whether the PDU set may correspond to a first l-frame or a differential P- / B / -frame).

[0133] PDU set importance may be used to indicate the relative importance of a PDU set compared to other PDU sets within a QoS Flow.

[0134] A latency parameter (e.g, latency requirement) associated with the PDU set may be, or may include, the PDU set delay budget (PSDB); the remaining PSDB; and / or the PDU set delivery deadline (PSDD).

[0135] In some examples, the PSDB may be used to indicate the maximum time between the reception of the first PDU (e.g, at the User Plane Function (UPF) in DL and / or at the WTRU in UL) and the successful delivery of the last arrived (e.g, received) PDU of a PDU set (e.g, at the WTRU in DL and / or at the UPF in UL). The PSDB may be an optional parameter and if provided, the PSDB may supersede the PDB.

[0136] In some examples, the PSDD may be a deadline (e.g, the absolute deadline) where the last PDU of a PDU set may need to be received at the application, e.g, so that the application may make use of the PDU set.

[0137] The PSIHI may indicate whether one or more (e.g, all) PDUs of the PDU set may be needed for the usage of the PDU set by an application layer.

[0138] The type of the PDU set may include one or more of the following: a first type of PDU set, which may need (e.g, require) reliable delivery of one or more (e.g, all) PDUs in the set; a second type of PDU set, in which the transmission of a PDU set may be unsuccessful if at least one (e.g, possibly specific) PDU fails to be transmitted; and / or the third type of PDU set, in which the transmission of a PDU set may be successful if X PDUs (e.g, at least X PDUs) out of the PDU set of Y PDUs are received. For example, if FEC is used and / or if additional layered encoding is used and assigned to the same PDU set, the transmission of a PDU set may be successful if X PDUs (e.g, at leastX PDUs) out of the PDU set of Y PDUs are received.

[0139] A reliability parameter (e.g, reliability requirement) of a PDU set, such as the PSER, may be used to indicate one or more of the following: an upper bound for the rate of PDU sets that may have been processed by the sender of a link layer protocol (e.g, the RLC in the RAN of a 3GPP access) that may not have beensuccessfully delivered by the corresponding receiver to the upper layer (e.g., the Packet Data Convergence Protocol (PDCP) in the RAN of a 3GPP access); an upper bound for the rate of PDUs per PDU set that may have been processed by the sender of a link layer protocol (e.g., the RLC in the RAN of a 3GPP access) but may not have been successfully delivered by the corresponding receiver to the upper layer (e.g., the PDCP in the RAN of a 3GPP access); and / or an upper bound for the rate of PDUs per PDU set that may not have been successfully received by the receiver of (e.g., at) the upper layer (e.g., the PDCP in the RAN of a 3GPP access).

[0140] The volume of the PDU set may include one or more of the following: the size of a PDU; and / or the number of PDUs in the PDU set.

[0141] One or more parameters of a data burst associated with a data set may include the volume of the data burst. The volume of the data burst may include one or more of the following: the size of a PDU in the data burst; the number of PDU sets in the data burst; and / or the volume of a PDU set in the data burst.

[0142] The WTRU may perform uplink enhancement procedure for a data set.

[0143] In some examples, the WTRU may receive a data set (e.g., a PDU segment, a subset of PDU segments, a PDU, a subset of a PDU set, a PDU set, a data burst, and / or the like). The WTRU may perform uplink enhancement for the data set, which may help the WTRU to successfully transmit a data set with reduced latency. For example, uplink enhancement may include one or more of the following layer enhancements: an RLC enhancement; and / or a MAC enhancement.

[0144] The WTRU may perform RLC enhancement for a data set by performing one or more RLC procedures (e.g., additional RLC procedures).

[0145] In some examples, the WTRU may perform RLC enhancement for a data set by performing one or more features, functions, and / or procedures, that may help to enhance the reliability of the transmission for the data set and / or to reduce the latency associated with the transmission of the data set. For example, the WTRU may perform one or any combination of the following RLC enhancements: performing a WTRU autonomous RLC PDU or PDU segment retransmission; performing a HARQ NACK feedback-based RLC retransmission; and / or performing multi-carrier duplication for an RLC PDU or PDU segment.

[0146] The WTRU may perform a WTRU autonomous RLC PDU or PDU segment retransmission. For example, the WTRU may generate (e.g., first generate) an RLC PDU or PDU segment. The WTRU may perform transmission of (e.g., transmit) the RLC PDU or PDU segment. The WTRU may retransmit (e.g., subsequently retransmit) the RLC PDU or PDU segment. The WTRU may determine whether to retransmit theRLC PDU or PDU segment based on one or more of the following: after a duration (e.g., a minimum duration); upon expiry of a timer; and / or a QoS parameter (e.g., QoS requirement).

[0147] In some examples, the WTRU may determine whether to retransmit the RLC PDU or PDU segment after a duration (e.g., a minimum duration). For example, the WTRU may retransmit an RLC PDU or PDU segment after the initial transmission of the RLC PDU or PDU segment for at least a minimum duration. The minimum duration between the initial retransmission and the retransmission of an RLC PDU or PDU segment may be fixed or configured by the network.

[0148] In some examples, the WTRU may determine whether to retransmit the RLC PDU or PDU segment upon expiry of a timer. For example, the WTRU may be configured with an RLC retransmission timer to retransmit an RLC PDU or PDU segment. The WTRU may trigger RLC retransmission of an RLC PDU or PDU segment upon the expiry of the RLC retransmission timer. The WTRU may initiate the timer based on one or more of the following: the arrival of an RLC Service Data Unit (SDU); upon submitting an RLC PDU or PDU segment to the MAC layer (e.g., for MAC PDU construction); and / or the initial transmission of the MAC PDU associated with the RLC PDU or PDU segment.

[0149] In some examples, the WTRU may determine whether to retransmit the RLC PDU or PDU segment based on one or more QoS parameters, such as one or more QoS requirements (e.g., a latency parameter, (e.g., the latency requirement), such as the PSDB, PSDD, remaining PSDB of an RLC PDU or PDU segment, the PDU set importance of the PDU set to which the RLC PDU or PDU segment) of the PDU or PDU segment.

[0150] For example, the WTRU may retransmit an RLC PDU or PDU segment if the WTRU has not receivedACK feedback (e.g., ACK feedback in a STATUS report) from the network and / or the remaining PDB, PSDB, and / or PSDD of the RLC PDU or PDU segment is smaller than a configured threshold.

[0151] For example, the WTRU may retransmit the RLC PDU or PDU segment if (e.g., only if) the RLC PDU or PDU segment belongs to a high-importance PDU set (e.g, a PDU set of PDU set importance (PSI) level 0, 1, or 2)

[0152] The WTRU may perform HARQ NACK feedback-based RLC retransmission. For example, the WTRU may retransmit an RLC PDU or PDU segment if the WTRU receives one or more HARQ NACK feedback (e.g, messages) for a MAC PDU containing the RLC PDU or the RLC PDU segment. The number of HARQ NACK feedback (messages) need to trigger RLC retransmission of the RLC PDU or PDU segment may be fixed (e.g, fixed as one or set to one) or configured by the network. As described herein, the WTRU may retransmit an RLC PDU or PDU segment with reduced latency. The WTRU may configure a cross-layerinteraction between the MAC and the RLC (e.g., RLC layer) in the WTRU. For example, upon reception of HARQ NACK feedback from the network, the MAC layer in the WTRU may inform (e.g., need to inform) the RLC (e.g. ,RLC layer) regarding which RLC PDU was received incorrectly.

[0153] The WTRU may perform multi-carrier duplication for an RLC PDU or PDU segment. For example, the WTRU may transmit an RLC PDU or PDU segment on two or more carriers, e.g., to enhance the reliability of the RLC PDU or PDU segment. In an example, the WTRU may perform multi-carrier duplication in the PDCP (e.g., at the PDCP layer), e.g., in which the WTRU may transmit a MAC PDU on two or more carriers.

[0154] The WTRU may perform RLC enhancement for a data set by adapting / overriding one or more RLC parameters.

[0155] In some examples, the WTRU may perform RLC enhancement for a data set by adapting one or more RLC configuration parameters. In an example, the WTRU may be configured with two or more (e.g., two) sets of RLC parameters. The first set of RLC parameters may be used as a set of RLC parameters (e.g., the default RLC parameters) for an RLC operation (e.g., a normal RLC operation, a default RLC operation, or a regular RLC operation). The second set of RLC parameters may be used as a set of RLC parameters for RLC enhancement operation. The WTRU may use (e.g., first use or initially use) the first set of RLC parameters for an RLC operation (e.g., a normal RLC operation). The WTRU may switch (e.g., then switch) to the second set of RLC parameters for an RLC enhancement operation. In some examples, the WTRU may be allowed (e.g., only be allowed) to switch to the second set of RLC parameters for a time duration (e.g., for a specified or configured time duration), which the WTRU may receive as part of the RLC enhancement configuration that the WTRU receives from the network. In some examples, the WTRU may be configured with an RLC parameter and / or a timer (e.g., prohi bit-timer) to restrict the WTRU from performing a function (e.g., a certain function). For example, the WTRU may be prohibited to (e.g., restricted from) retransmit an RLC PDU if the t- PollRetransmit timer is running. The WTRU may perform (e.g., then perform) RLC enhancement by overriding the restricted rule. For example, the WTRU may adapt and / or override one or more of the following parameters for RLC enhancement: WTRU autonomous RLC retransmission enabled / disabled parameters; HARQ NACK- based RLC retransmission enabled / disabled parameters; override RLC window size (e.g., AM_Window_Size) parameters; SN-FieldLength parameters; PollPDU and / or PollByte parameters; PollTime parameters; and / or T- PollRetransmit parameters.

[0156] The WTRU may adapt and / or override WTRU autonomous RLC retransmission enabled / disabled parameters. For example, the WTRU may disable WTRU autonomous RLC retransmission for an RLCprocedure (e.g., a default, normal, and / or standard RLC procedure). The WTRU may enable WTRU autonomous RLC retransmission for RLC enhancement.

[0157] The WTRU may adapt and / or override HARQ NACK-based RLC retransmission enabled / disabled parameters. For example, the WTRU may disable HARQ NACK-based WTRU autonomous RLC retransmission for an RLC procedure (e.g., a default, normal, and / or standard RLC procedure). The WTRU may enable HARQ NACK based RLC retransmission for RLC enhancement.

[0158] The WTRU may adapt and / or override RLC window size (e.g., AM_Window_Size) parameters. The RLC window size parameter may be used to control the sliding window for the RLC transmitting and / or receiving entities.

[0159] In some examples, the WTRU may be configured with multiple possible values of RLC window size. The WTRU may use an RLC window size (e.g., the default RLC window size) for the RLC procedure. The WTRU may use (e.g., then use) another configured window size (e.g., a larger window size) for RLC enhancement. The WTRU may transmit an indication to the network. For example, the WTRU may transmit an indication to the network if the WTRU activates a non-default RLC window size. The indication may include the duration for using the new window.

[0160] In some examples, the WTRU may override the restriction of not performing (e.g., preventing and / or restricting) RLC transmission if the transmission window is stalled. For example, the WTRU may perform RLC enhancement by continuing to transmit one or more RLC PDUs if the transmission window is stalled. The WTRU may determine whether to increase the window size to continue transmitting one or more RLC PDUs. The WTRU may indicate to the network (e.g., by sending an indication) regarding the new RLC window size. The indication may be sent via a RRC message (e.g., WTRU Assistant Information), an RLC control PDU, and / or an RLC header associated with the RLC PDU using the new RLC Window size.

[0161] The SN-FieldLength parameter may be used to indicate the RLC Sequence Number field size. For example, the WTRU may be configured with multiple possible values SN-FieldLength for an RLC channel. The WTRU may use a SN-FieldLength (e.g., the default SN-FieldLength) for the RLC procedure. The WTRU may use (e.g., then use) another configured SN-FieldLength (e.g., a larger SN-FieldLength) for RLC enhancement.

[0162] PollPDU and / or Poll Byte parameters may be used to control the polling request of the WTRU. For example, the WTRU may poll the network regarding the transmitted RLC PDU if the amount of data without polling is larger than a threshold (e.g., PDU_WITHOUT_POLL >= pollPDU; or BYTE_WITHOUT_POLL >= poll Byte).

[0163] In some examples, the WTRU may be configured with two sets of PollPDU / PollByte. The WTRU may use the first set of PollPDU / PollByte (e. g. , the default PollPDU / PollByte) for an RLC procedure (e.g., a normal RLC procedure). The WTRU may use another set of PollPDU / PollByte (e.g., the second set of PollPDU / PollByte) for an RLC enhancement procedure. For example, the WTRU may be configured with two set of PollPDU / PollByte. The first set of PollPDU / PollByte may be used for data set with importance being smaller than a configured threshold. The second set of PollPDU / PollByte may be used for data set with Importance being larger than a configured threshold. For example, the WTRU may be configured with two or more (e.g., two) sets of PollPDU / PollByte. The first set of PollPDU / PollByte may be used for an RLC PDU or PDU segment with PSDB being smaller than a configured threshold. The second set of PollPDU / PollByte may be used for an RLC PDU or PDU segment with Importance being larger than a configured threshold.

[0164] In some examples, the WTRU may perform RLC enhancement by overriding the PollPDU / PollByte restriction. For example, the WTRU may determine (e.g., dynamically determine) the exception for polling an RLC PDU or PDU segment, e.g, for RLC enhancement even the amount of data without polling is smaller than the configured threshold. For example, the WTRU may enable polling for an RLC PDU or PDU segment if the importance of the associated RLC PDU is larger than a configured threshold. For example, the WTRU may enable polling for the RLC PDU or PDU segment if the PSDB and / or the remaining PSDB of the RLC PDU or PDU segment is smaller than a configured threshold. For example, the WTRU may perform RLC enhancement by determining (e.g, dynamically determining) the exception for polling an RLC PDU or PDU segment. For example, the WTRU may enable polling for the RLC PDU or PDU segment if the PDU and / or the PDU segment is the last PDU or the last PDU segment of one or more PDU sets and / or one or more data bursts. The number of PDU sets and / or the data burst may be fixed (e.g, fixed as one) or configured by the network. After polling the RLC PDU or PDU segment for RLC enhancement, in some examples, the WTRU may reset the amount of data without polling (e.g, reset PDU_WITHOUT_POLL and / or BYTE_WITHOUT_POLL). In some examples, the WTRU may resume the amount of data without polling (e.g, resume PDU_WITHOUT_POLL and / or BYTE_WITHOUT_POLL as the value before performing polling enhancement for RLC enhancement).

[0165] The PollTime parameter may be used to allow the WTRU to enable polling for an RLC PDU or PDU segment. For example, if PollTime is enabled, the WTRU may be (e.g, shall be) allowed to enable polling in (e.g, for) an RLC PDU or PDU segment, e.g, after an interval of PollTime.

[0166] In some examples, the WTRU may disable Polltime for an RLC operation (e.g, a default, normal, or standard RLC operation). The WTRU may enable the PollTime for RLC enhancement of an RLC PDU. TheWTRU may be allowed to transmit a poll request in an RLC PDU, e.g., to accelerate the reception of a STATUS PDU report.

[0167] In some examples, the WTRU may be configured with values (e.g., two values) of the PollTime parameter. The WTRU may use the first value of PollTime (e.g., the default PollTime) for an RLC procedure (e.g., a normal, default, or standard RLC procedure). The WTRU may use the second value of PollTime for an RLC enhancement procedure.

[0168] The T-PollRetransmit parameter may be used for the WTRU to retransmit an RLC PDU or PDU segment and poll the reception status of the RLC channel. For example, the WTRU may initiate the T- PollRetransmit timer upon polling the reception status of the RLC channel. Upon expiry of the T-PollRetransmit timer, the WTRU may poll the reception status of the RLC channel (e.g., again). If the WTRU has not received ACK associated with the RLC PDU or PDU segment, the WTRU may trigger retransmission of the RLC PDU or PDU segment.

[0169] In some examples, the WTRU may be configured with values (e.g., two values) of T-PollRetransmit parameter. The WTRU may use the first value of T-PollRetransmit parameter (e.g., the default T- PollRetransmit parameter) for an RLC procedure (e.g., a normal, default, or standard RLC procedure). The WTRU may use the second value of T-PollRetransmit parameter for an RLC enhancement procedure.

[0170] In some examples, the WTRU may be configured with multiple values of T-PollRetransmit parameters. A value of T-PollRetransmit parameter may be associated with the delay requirement of the transmitted RLC PDU or the transmitted PDU segment (e.g., the PSDB, the remaining PSDB, and / or the like). The WTRU may determine which T-PollRetransmit value to use based on the delay requirement (e.g., the PSDB, the remaining PSDB, and / or the like) of the transmitted RLC PDU or the transmitted PDU segment. For example, the WTRU may use a shorter T-PollRetransmit value if the remaining PSDB of the transmitted RLC PDU waiting for ACK feedback is smaller than a configured threshold. The WTRU may use a longer T- Poll Retransmit value if the remaining PSDB of the transmitted RLC PDU waiting for ACK feedback is larger than a configured threshold.

[0171] In some examples, the WTRU may be configured with multiple values of T-PollRetransmit parameters. A value of T-PollRetransmit may be associated with a transmission (e.g., a corresponding retransmission) order of the RLC PDU or PDU segment. For example, the WTRU may use the first value of the T-Poll Retransmit parameter if the WTRU has not received ACK feedback for the initial transmission of the transmitted RLC PDU or the transmitted PDU segment. The WTRU may use the Nth value of T-PollRetransmitparameter if the WTRU has not received ACK feedback for the Nth transmission of an RLC PDU or PDU segment.

[0172] In some examples, the WTRU may override the T-PollRetransmit timer to trigger transmission of polling indication and retransmission of an RLC PDU for RLC enhancement. For example, if the T- PollRetransmit timer is running and the WTRU has not received STATUS feedback from the network, the WTRU may trigger transmission of polling indication and retransmission of an RLC PDU for RLC enhancement. For example, the WTRU may override T-PollRetransmit restriction if the configured triggering condition for RLC enhancement is satisfied (e.g., the remaining PSDB of the PDU is smaller than (e.g., is below) a configured threshold and / or the importance of the PDU is larger than (e.g., exceeds) a configured threshold).

[0173] The WTRU may inform the network regarding adapting one or more RLC parameters for RLC enhancement. For example, upon adapting one or more RLC parameters, the WTRU may inform the network (e.g., the gNB) regarding one or more new RLC parameters associated with the WTRU. The one or more new RLC parameters may help the WTRU to align transmission and reception behavior of the two RLC entities. For example, the WTRU may indicate to the network that the WTRU may be using a value (e.g., a new value) of Window Size, Poll Byte, PollPDU, and / or the like. For example, the WTRU may indicate to the network that the WTRU has enabled PollTime, UE-autonomous RLC retransmission, HARQ NACK-based RLC retransmission, and / or the like.

[0174] The WTRU may perform MAC enhancement for a data set by performing one or more MAC procedures (e.g., one or more additional MAC procedures).

[0175] In some examples, the WTRU may perform MAC enhancement for a data set by performing one or more features, functions, and / or procedures. The one or more features, functions, and / or procedures may help to enhance the reliability of the transmission for the data set and / or to reduce the latency associated with the transmission of the data set. For example, the WTRU may perform one or more of the following MAC enhancements: performing dynamic LCP restrictions / adaptation; performing dynamic grant / resource selection for a data set; performing multi-carrier duplication for a MAC PDU; performing transmission repetition; and / or performing adaptation of one or more transmission parameters.

[0176] The WTRU may perform dynamic LCP restrictions / adaptation. For example, the WTRU may perform MAC enhancement for a data set by determining (e.g., dynamically determining) whether to multiplex an RLC PDU or PDU segment of a data set to a scheduled grant. The WTRU may determine whether to multiplex an RLC PDU associated with the data set for MAC enhancement operation in a scheduled grant based on one ormore of the following: the properties associated with the data set; and / or the properties associated with the scheduled grant.

[0177] The properties associated with the data set may include one or more of the QoS associated with the data set. In some examples, the WTRU may multiplex the RLC PDU or PDU segment in the grant if the importance of the PDU or PDU segment is greater than (e.g., above) a configured threshold and / or if the PDU Set Importance (PSI) level of the PDU set, to which the RLC PDU and / or PDU segment belongs, is lower than (e.g., below) a preconfigured threshold. In some examples, the WTRU may multiplex the RLC PDU or PDU segment in the grant if the remaining PSDB of the PDU or PDU segment is smaller (e.g., below) than a configured threshold.

[0178] The properties associated with the scheduled grant may include one or more of the following: the types of the grant (e.g., whether the grant is a dynamic grant, a type 1 configured grant, and / or a type 2 configured grant); the size of the grant; the MCS associated with the grant; the number of repetitions associated with the grant; the component carrier associated with the grant (e.g., whether the grant is in a licensed or unlicensed carrier); the duration of the grant; the priority associated with the grant; the serving cell associated with the grant; the sub carrier spacing (SCS) associated with the grant; and / or the Channel access priority class (CAPC) associated with the grant.

[0179] In some examples, the WTRU may perform MAC enhancement for an RLC PDU or PDU segment retransmission. The WTRU may determine whether to multiplex the RLC PDU or PDU segment in a MAC PDU to transmit in the scheduled grant, e.g., based on various factors, such as the MCS associated with the grant. For example, the WTRU may multiplex the RLC PDU or PDU segment in a MAC PDU for transmission in the scheduled grant if the MCS associated with the scheduled grant is smaller than the MCS associated with the initial transmission of the RLC PDU or PDU segment. For example, the WTRU may multiplex the RLC PDU or PDU segment in the MAC PDU for transmission in the scheduled grant if the MCS associated with the scheduled grant is smaller than a configured threshold. The probability of successful reception for the RLC PDU or PDU segment retransmission may be increased.

[0180] In some examples, the WTRU may determine whether to multiplex the RLC PDU or PDU segment in a MAC PDU to transmit in the scheduled grant, e.g., based on the size of the grant. If the size of the grant is larger than a configured threshold, the WTRU may multiplex the RLC PDU or PDU segment in a MAC PDU to transmit in the scheduled grant. If the size of the grant is sufficient for the WTRU to transmit the RLC PDU or PDU segment, the WTRU may multiplex the RLC PDU or PDU segment in a MAC PDU and transmit in the scheduled grant. The segmentation of an RLC PDU or PDU segment may be minimized.

[0181] In some examples, the WTRU may determine whether to multiplex the RLC PDU or PDU segment in a MAC PDU to transmit in the scheduled grant, e.g., based on the number of repetitions associated with the scheduled grant. If the number of repetitions associated with the grant is larger than a configured threshold, the WTRU may multiplex the RLC PDU or PDU segment in a MAC PDU to transmit in the scheduled grant. The WTRU may perform MAC enhancement for RLC PDU retransmission. The WTRU may multiplex the RLC PDU or PDU segment in a MAC PDU and transmit in the scheduled grant if the number of repetitions associated with the grant is larger than the number of repetitions associated with the grant for retransmission of the RLC PDU or PDU segment. The transmission success probability of the RLC PDU or PDU segment retransmission may be increased.

[0182] In some examples, the WTRU may determine whether to multiplex the RLC PDU or PDU segment in a MAC PDU to transmit in the scheduled grant, e.g., based on the carrier component associated with the grant. For example, the WTRU may multiplex the RLC PDU or PDU segment to a MAC PDU and transmit in the scheduled grant if the grant is associated with a licensed carrier. If the grant is associated with an unlicensed carrier, the WTRU may skip transmitting (e.g., not transmit) the RLC PDU or PDU segment in the grant.

[0183] The WTRU may perform dynamic grant / resource selection for the data set. For example, the WTRU may perform MAC enhancement for a data set by determining (e.g., dynamically determining) which grant to transmit a MAC PDU associated with the data set. For example, the WTRU may determine (e.g., dynamically determine) which scheduled grant to transmit a MAC PDU associated with the data set for MAC enhancement, e.g., based on the properties associated with the scheduled grants. The properties associated with the scheduled grants may include one or more of the following: the types of the grant (e.g., whether the grant is a dynamic grant, a type 1 configured grant, and / or a type 2 configured grant); the size of the grant, the MCS associated with the grant; the number of repetitions associated with the grant; the component carrier associated with the grant (e.g., whether the grant is in a licensed or unlicensed carrier); the duration of the grant; the priority associated with the grant; the serving cell associated with the grant; the SCS associated with the grant; and / or the CAPC associated with the grant.

[0184] In some examples, the WTRU may select a grant to transmit a MAC PDU associated with the data set based on the timing of the grant. For example, the WTRU may select the grant within a configured duration.

[0185] In some examples, the WTRU may select a grant to transmit a PDU associated with the data set based on the size of the grant. For example, the WTRU may select a grant within a period (e.g., the earliest grant) having the size being greater than a configured threshold. For example, the WTRU may select a grant within a period having the largest size.

[0186] The WTRU may perform multi-carrier duplication for a MAC PDU. For example, the WTRU may transmit a MAC PDU to (e.g., on) two or more carriers, e.g., to enhance the reliability of the MAC PDU.

[0187] The WTRU may perform transmission repetition. For example, the WTRU may retransmit (e.g., blindly retransmit) the MAC PDU one or more times if the criteria for uplink enhancement are satisfied (e.g., are met). For example, the WTRU may perform blind retransmission of the MAC PDU if one or more latency requirements associated with the MAC PDU (e.g., PSDB) is smaller than a configured threshold. The WTRU may indicate the number of repetitions (e.g., via Uplink Control Information (UCI) associated with one or more transmissions of the MAC PDU) the WTRU plans to transmit for the MAC PDU.

[0188] The WTRU may perform adaptation of one or more transmission parameters. The one or more transmission parameters to adapt may be, or may include, one or more of the following: Modulation and Coding Scheme (MCS); transmission power; transmission beam; the number of repetitions for a Transport Block (TB); HARQ pattern; and / or the like. For example, the WTRU may adapt one or more transmission parameters if the uplink transmission enhancement condition is met (e.g., is satisfied). For example, the WTRU may be scheduled with a configured grant. The configured grant may allow the WTRU to adapt its MCS. The WTRU may indicate the MCS of the Physical Uplink Shared Channel (PUSCH) in the associated UCI. The WTRU may adapt (e.g., then adapt) its MCS (e.g., reduce MCS) if the uplink transmission enhancement condition is satisfied.

[0189] The WTRU may perform MAC enhancement for a data set by adapting / overriding one or more MAC parameters.

[0190] In some examples, the WTRU may perform MAC enhancement for a data set by adapting and / or overriding one or more MAC configuration parameters. In some examples, the WTRU may be configured with two or more (e.g., two) sets of MAC parameters. The first set of MAC parameters may be used as a set of MAC parameters (e.g., default MAC parameters). The second set of MAC parameters may be used as a set of MAC parameters for MAC enhancement operation. The WTRU may first use (e.g., initially use) the first set of MAC parameters for a MAC operation (e.g., a normal, standard, or default MAC operation). The WTRU may switch to the second set of MAC parameters for MAC enhancement operation. In some examples, the WTRU may be configured with a MAC parameter and / or a timer (e.g., Prohibit-timer) to restrict the WTRU in performing a function. For example, the WTRU may not be allowed to use a Type 1 configured grant for a data set in a MAC operation (e.g., a normal, default, or standard MAC operation). The WTRU may perform MAC enhancement by overriding the restricted rule. The WTRU may be allowed to use a Type 1 configured grant for the data for MAC enhancement operation. For example, the WTRU may adapt and / or override one or more ofthe following parameters for MAC enhancement: priority; PBR; set of allowed serving cells from the cell group; set of allowed carriers; set of allowed SCSs; maximum / minimum PUSCH duration; minimum / maximum grant size; maximum / minimum MCS; minimum number of repetitions associated with the grant; allowed CG types (e.g., Type 1 CG and / or Type 2 CG); list of allowed CGs; list of allowed PHY priorities; and / or the CAPC.

[0191] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on priority. For example, the WTRU may be configured with two or more (e.g., two) priorities for the LCH associated with the data set. The WTRU may use the first priority (e.g., a lower priority) for a MAC procedure (e.g., a normal, standard, or default MAC procedure). The WTRU may use the second priority (e.g., a higher priority) for MAC enhancement operation for the data set.

[0192] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on PBR. For example, the WTRU may be configured with two or more (e.g., two) values of PBR for the LCH associated with the data set. The WTRU may use a first PBR (e.g., the lower PBR) for a MAC procedure (e.g, a normal, standard, or default MAC procedure). The WTRU may use a second PBR (e.g, the higher PBR) for MAC enhancement operation for the data set.

[0193] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the set of allowed serving cells from the cell group. For example, the WTRU may be configured with two or more (e.g, two) sets of allowed serving cells for the LCH associated with the data set. The WTRU may use one set (e.g, the first set) of allowed serving cells for a MAC procedure (e.g, a normal, standard, or default MAC procedure). The WTRU may use another set (e.g, the second set) of allowed serving cells for MAC enhancement operation for the data set.

[0194] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the set of allowed carriers. For example, the WTRU may be configured with two or more (e.g, two) sets of carriers for the LCH associated with the data set. The WTRU may use a set (e.g, the first set) of carriers for a MAC procedure (e.g, a normal, standard, or default MAC procedure). The WTRU may use another set (e.g, the second set) of allowed carriers for MAC enhancement operation for the data set. For example, the WTRU may select either licensed carriers or unlicensed carriers to transmit the data set for the MAC procedure (e.g, the normal MAC procedure). The WTRU may select the licensed carrier to transmit (e.g, only to transmit) the data set for a MAC enhancement operation.

[0195] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the set of allowed SCSs. For example, the WTRU may be configured with two or more (e.g, two) sets of allowed SCSs for the LCH associated with the data set. The WTRU may use a set (e.g, the first set) of allowed SCSsfor a MAC procedure (e.g., a normal, standard, or default MAC procedure). The WTRU may another set (e.g., the second set) of allowed SCSs for MAC enhancement operation for the data set. In some examples, the WTRU may be configured with a list of allowed SCSs for the MAC procedure (e.g., the normal, standard, or default MAC procedure) of a data set. The WTRU may use one or more (e.g., all) SCSs for MAC enhancement of the data set.

[0196] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the maximum / minimum PUSCH duration. For example, the WTRU may be configured with two or more (e.g., two) value of the maximum PUSCH duration for the LCH associated with the data set. The WTRU may use a value (e.g., the shorter value) of the maximum PUSCH for a MAC procedure (e.g., a normal, standard, or default MAC procedure). The WTRU may another value (e.g., longer value) of the maximum PUSCH for MAC enhancement operation for the data set. In some examples, the WTRU may be configured a maximum PUSCH duration for the MAC procedure (e.g., the normal MAC procedure) of a data set. The WTRU may use one or more (e.g., all) PUSCH durations for MAC enhancement of the data set.

[0197] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the minimum / maximum grant size. For example, the WTRU may be configured with a minimum / maximum grant size for MAC enhancement of the data set. The WTRU may select (e.g., only select) the grant having the size satisfying the minimum / maximum configured grant size to transmit the MAC PDU associated with the data set for a MAC enhancement operation.

[0198] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the maximum / minimum MCS. For example, the WTRU may be configured with a maximum / minimum MCS for MAC enhancement of the data set. The WTRU may select (e.g., only select) the grant having the associated MCS satisfying the configured maximum / minimum MCS to transmit the MAC PDU associated with the data set for a MAC enhancement operation.

[0199] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the minimum number of repetitions associated with the grant. For example, the WTRU may be configured with a maximum MCS for MAC enhancement of the data set. The WTRU may select (e.g., only select) the grant having the associated MCS being smaller than the configured maximum MCS to transmit the MAC PDU associated with the data set for the MAC enhancement operation.

[0200] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the allowed CG types (e.g., Type 1 CG and / or Type 2 CG). In some examples, the WTRU may be configured with two or more (e.g., two) list of allowed CG types for a LCH associated with a data set. In one list (e.g., the firstlist) of allowed CG types, the list may be used for a MAC procedure (e.g., a normal, standard, or default MAC procedure). In another list (e.g., the second list) of allowed CG types, the list may be used for a MAC enhancement operation. The WTRU may perform MAC enhancement for the data set by selecting the second list of allowed CG types. In some examples, the WTRU may be configured with a list of allowed CG types for a normal MAC procedure (e.g., a standard or default MAC procedure) of a data set. The WTRU may use one or more (e.g., all) CG types for MAC enhancement for the data set.

[0201] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the list of allowed CGs. In some examples, the WTRU may be configured with two or more (e.g., two) list of allowed CGs for a LCH associated with a data set. In one list (e.g., the first list) of allowed CGs, the list may be used for a MAC procedure (e.g., a normal, standard, or default MAC procedure). In another list (e.g., the second list) of allowed CGs, the list may be used for a MAC enhancement operation. The WTRU may perform MAC enhancement for the data set by selecting the second list of allowed CGs. In some examples, the WTRU may be configured with a list of allowed CG types for the normal MAC procedure (e.g., a standard or default MAC procedure) of a data set. The WTRU may use one or more (e.g., all) CG types for MAC enhancement for the data set.

[0202] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the list of allowed PHY priorities. The list of allowed PHY priorities may be used to indicate the set of PHY priorities, in which the WTRU is allowed to transmit the data set associated with the LCH. For example, the WTRU may be scheduled with a transmission grant (e.g., dynamic grant or Configured Grant), in which the WTRU may be indicated which PHY priority to use the scheduled grant. The PHY priority information may be indicated (e.g., via DCI) for a dynamic grant and / or via RRC, MAC CE, or DCI for a configured grant. The WTRU may transmit the data set in (e.g., using) the scheduled grant if the indicated PHY priority belongs to the configured list of allowed PHY priorities associated with the LCH. If the indicated PHY priority does not belong to the configured list of allowed PHY priorities associated with the LCH, the WTRU may skip transmitting (e.g., may not transmit) the data set in (e.g., using) the scheduled grant.

[0203] In some examples, the WTRU may be configured with two or more (e.g., two) lists of allowed PHY priorities for the LCH associated with a data set. In one list (e.g., the first list) of allowed PHY priorities, the list may be used for a MAC procedure (e.g., a normal, standard, or default MAC procedure). In another list (e.g., the second list) of allowed PHY priorities, the list may be used for a MAC enhancement operation for the data set. The WTRU may perform MAC enhancement for the data set by selecting the second list of allowed PHY priorities.

[0204] In some examples, the WTRU may be configured with a list of allowed PHY priorities for the MAC procedure (e.g., the normal MAC procedure) of a data set. The WTRU may use one or more (e.g., all) PHY priorities for MAC enhancement for the data set. The allowed data set may be configured to be transmitted in one or more (e.g., all) possible scheduled grants and may help the WTRU to deliver the data set sooner to the network.

[0205] In some examples, for MAC enhancement of the data set, the WTRU may use the scheduled grant for the data set if the PHY priority associated with the scheduled grant is greater than a configured threshold. If the associated PHY priority associated with the scheduled grant is smaller than the configured threshold, the WTRU may skip using (e.g., may not use) the scheduled grant to transmit the data set. The WTRU may be allowed to select the grant (e.g., the best grant) to transmit the data set for MAC enhancement.

[0206] The WTRU may adapt and / or override one or more parameters for MAC enhancement based on the CAPC. The CAPC may be used by the WTRU to determine one or more parameters associated with the channel access procedure for shared spectrum, such as LBT parameters, maximum COT duration, and / or the like. For example, the WTRU may be configured with two or more (e.g., two) CAPCs associated with the LCH of the data set. The WTRU may use the first CAPC (e.g., a low CAPC) for a MAC procedure (e.g., a normal, standard, or default MAC procedure) of the data set. The WTRU may use the second CAPC (e.g., a high CAPC) for MAC enhancement operation for the data set.

[0207] The WTRU may inform the network regarding adapting one or more MAC parameters for MAC enhancement. For example, upon adapting / overriding one or more MAC parameters, the WTRU may inform the network (e.g., the gNB) regarding one or more new MAC parameters associated with the WTRU. The WTRU informing the network may help to align transmission and reception behavior between the network and the WTRU.

[0208] The WTRU may be configured to trigger uplink enhancement.

[0209] The WTRU may determine whether to perform uplink enhancement procedure for a data set. For example, the WTRU may determine whether to perform uplink enhancement procedure for a data set based on one or more of the following: one or more QoS parameters associated with the data set; one or more parameters associated with the RB / LCH of the data set; an indication from the network; and / or a configured triggering event.

[0210] The WTRU may perform uplink enhancement based on the QoS of the data set. In some examples, the WTRU may perform uplink enhancement (e.g., RLC enhancement, MAC enhancement, and / or the like) fora data set based on QoS of the data set. For example, the WTRU may be configured with a QoS threshold to perform uplink enhancement for a data set. The WTRU may determine whether to perform uplink enhancement for the data set, e.g., based on if the QoS of the data set satisfies the configured threshold.

[0211] In some examples, the WTRU may determine whether to perform uplink enhancement for a data set based on the importance of the data set. For example, the WTRU may be configured with an importance threshold to perform uplink enhancement for the data set. The WTRU may perform uplink enhancement for the data set if the importance of the data set is greater than the configured threshold. If the importance of the data set is less than the configured threshold, the WTRU may skip performing (e.g., may not perform) uplink enhancement for the data set. For example, the WTRU may perform autonomous RLC PDU retransmission for the RLC PDU if the importance of the PDU is larger than the configured threshold.

[0212] In some examples, the WTRU may determine whether to perform uplink enhancement for a data set based on the latency requirement of the data set (e.g., PDB, remaining PDB, PSDB, remaining PSDB, PSDD, and / or the like). The WTRU may be configured with a time threshold (e.g., PDB threshold, PSDB threshold, remaining PSDB threshold, and / or the like) to perform uplink enhancement for the data set. The WTRU may determine whether to perform uplink enhancement for the data set if the latency requirement associated with the data set satisfies the threshold. In some examples, the WTRU may perform WTRU autonomous RLC retransmission for a PDU set if the PSDB of the PDU set is smaller than a configured threshold. In some examples, the WTRU may perform WTRU autonomous RLC retransmission for one or more PDUs (e.g., the remaining PDUs, which has not been transmitted) of a PDU set if the remaining PSDB of the PDU set is smaller than the configured threshold. In some examples, the WTRU may perform HARQ-based RLC PDU retransmission for a PDUs of a PDU set if the remaining PSDB of the PDU is smaller than a configured threshold. In some examples, the WTRU may perform multicarrier duplication for a PDU in a PDU set if the remaining PSDB of the PDU is smaller than a configured threshold.

[0213] In some examples, the WTRU may determine whether to perform uplink enhancement for a data set based on the reliability requirement of the data set (e.g., PER, PSER, and / or the like). For example, the WTRU may be configured with a reliability threshold for a data set (e.g., PER threshold, PSER threshold, and / or the like). The WTRU may determine whether to perform uplink enhancement for a data set, e.g., based on if the PER and / or the PSER associated with the data set is larger than the configured threshold. In some examples, the WTRU may perform multicarrier duplication for a PDU if the PER of the PDU is larger than a configured threshold. In some examples, the WTRU may perform PHY repetition for PDUs in a PDU set if the PSER of thePDU set is greater than a configured threshold. In some examples, the WTRU may perform multicarrier duplication for a PDU set if PSER of the PDU set is greater than a configured threshold.

[0214] In some examples, the WTRU may determine whether to perform uplink enhancement for a data set based on the volume of the data set. For example, the volume of a PDU or PDU segment may be determined based on the size of the PDU or PDU segment. For example, the volume of a PDU set may be determined based on the size of each PDU and / or the number of PDUs in the PDU set. The WTRU may perform uplink enhancement for a data set if the volume of the data set is smaller than a configured threshold. For example, the WTRU may perform WTRU autonomous RLC retransmission for PDUs in a PDU set if the number of PDUs in the PDU set is smaller than a configured threshold. The network may be configured and / or allowed to control the resource usage, e.g., to avoid excessive usage of the resources.

[0215] In some examples, the WTRU may determine whether to perform uplink enhancement for a data set based on whether PSIHI is enabled / disabled for one or more PDU sets of the data set. For example, the WTRU may perform uplink enhancement for the data set if PSIHI is enabled. If PSIHI is disabled, the WTRU may skip performing (e.g., not perform) uplink enhancement for the data set.

[0216] In some examples, the WTRU may determine whether to perform uplink enhancement for a data set based on the type of PDU set in the data set. For example, the WTRU may perform uplink enhancement for the first or the second type of PDU set. The WTRU may skip performing (e.g., not perform) uplink enhancement for the third type of PDU set.

[0217] The WTRU may perform uplink enhancement procedure based on a parameter of the RB / LCH of the data set.

[0218] In some examples, the WTRU may perform uplink enhancement (e.g., RLC enhancement, MAC enhancement, and / or the like) for a data set based on one or more parameters associated with the RB / LCH of the data set. The parameters associated with the RB / LCH of the data set may include one or more of the following: whether uplink enhancement is enabled / disabled; priority associated with the RB / LCH; the set of allowed carriers; the set of allowed SCSs; the list of allowed CGs; the list of allowed PHY priorities; and / or CAPC.

[0219] The WTRU may perform uplink enhancement based on whether uplink enhancement is enabled / disabled. In some examples, the WTRU may perform WTRU autonomous RLC retransmission for a PDU if the PDU is associated with an RB / LCH where uplink enhancement enabled (e.g., WTRU autonomous RLC retransmission enabled RB / LCH, and / or the like).

[0220] In some examples, the WTRU may perform WTRU autonomous RLC retransmission for a PDU in a PDU set if the PDU set is associated with uplink enhancement enabled (e.g., WTRU autonomous RLC retransmission enabled RB / LCH).

[0221] The WTRU may perform uplink enhancement based on priority associated with the RB / LCH.

[0222] For example, the WTRU may be configured with a priority threshold to enable uplink enhancement. If the priority of the RB / LCH is higher than the configured threshold, the WTRU may perform uplink enhancement for a data set in the RB / LCH. If the priority of the RB / LCH is smaller (e.g., lower) than the configured threshold, the WTRU may skip performing (e.g., not perform) uplink enhancement for the data set from the RB / LCH.

[0223] The WTRU may perform uplink enhancement based on PBR of the RB / LCH. For example, the WTRU may be configured with a priority threshold to enable uplink enhancement. If the priority of the RB / LCH is higher than the configured threshold, the WTRU may perform uplink enhancement for a data set in the RB / LCH. If the priority of the RB / LCH is smaller (e.g., lower) than the configured threshold, the WTRU may skip performing (e.g., not perform) uplink enhancement for the data set from the RB / LCH.

[0224] The WTRU may perform uplink enhancement based on the set of allowed carriers. For example, the WTRU may perform uplink enhancement for a data set in the RB / LCH, such as multi-carrier duplication if the set of allowed carriers includes at least two carriers or two licensed carriers.

[0225] The WTRU may perform uplink enhancement based on the set of allowed SCSs. For example, the WTRU may perform uplink enhancement for a data set in the RB / LCH if the set of allowed SCSs includes at least two SCSs.

[0226] The WTRU may perform uplink enhancement based on the list of allowed CGs. For example, the WTRU may perform uplink enhancement for a data set in the RB / LCH such as dynamic LCP restriction / adaptation or dynamic grant / resource selection if the list of CGs associated with the RB / LCH is greater than a threshold. The list of CGs may be fixed (e.g., set to two) or configured by the network.

[0227] The WTRU may perform uplink enhancement based on the list of allowed PHY priorities. For example, the WTRU may perform uplink enhancement for a data set in the RB / LCH if the list of allowed PHY priorities includes a specific priority and / or the highest allowed priority is larger than or equal to a threshold. The list of allowed PHY priorities may be fixed (e.g., set to the highest PHY priority) or configured by the network.

[0228] The WTRU may perform uplink enhancement based on CAPC. For example, the WTRU may perform uplink enhancement for a data set in the RB / LCH if the CAPC associated with the RB / LCH is smaller than a threshold. The CAPC may be fixed or configured by the network.

[0229] The WTRU may perform uplink enhancement for a data set based on an indication from the network. For example, the WTRU may perform uplink enhancement for the data set based on one or more of the following indications from the network: an indication enabling / disabli ng uplink enhancement; an indication on a configured grant; an indication on a dynamic grant; and / or an indication on congestion conditions.

[0230] The WTRU may perform uplink enhancement for a data set based on an indication enabling / disabling uplink enhancement. For example, the WTRU may receive the indication from the network to enable / disable uplink enhancement. The indication may be sent by the network, e.g. , via an RRC, MAC CE, or DCI.

[0231] The WTRU may perform uplink enhancement for a data set based on an indication of a configured grant. For example, the WTRU may be scheduled with a CG by the network. The WTRU may be indicated which RB / LCH is allowed to use the CG. The WTRU may also be indicated whether an RB / LCH may use the grant in case of uplink enhancement operation. The WTRU may perform uplink enhancement for the data set in the RB / LCH by allowing the data set to use the grant.

[0232] The WTRU may perform uplink enhancement for a data set based on an indication of a dynamic grant. For example, the WTRU may receive a dynamic grant from the network, e.g., via DCI. The WTRU may be indicated whether to allow the data set in one or more LCHs / RBs to use the grant as uplink enhancement is triggered. The WTRU may not be allowed to use the grant for the data set in the LCH / RB for MAC operation (e.g., normal, default, or standard MAC operation). If the network allows the WTRU to use the grant, the WTRU may override the restriction during MAC operation (e.g., normal, default, or standard MAC operation) and use the grant for the RB / LCH if uplink enhancement is triggered. For example, the WTRU may be configured with an RB / LCH, which allow to use a grant, if the PHY priority associated with the grant is lower than a threshold. The WTRU may receive a dynamic grant having PHY priority being greater than the threshold. The WTRU may be indicated to use the grant if uplink enhancement for the data set in the RB / LCH is triggered (e.g., via DCI indication). The WTRU may perform uplink enhancement for the data set in the RB / LCH and use the scheduled dynamic grant.

[0233] The WTRU may perform uplink enhancement for a data set based on an indication of congestion conditions. For example, the WTRU may perform one or more actions associated with UL enhancements (e.g., flow control of data sets) if the WTRU receives a congestion indication from the network. Such congestionindication may include timing information (e.g., start / end time, duration, and / or the like) for which the congestion conditions or any associated UL enhancement actions may apply, for example. Such congestion indication may include the information on data types / properties (e.g., importance of data set) or restrictions / exemptions (e.g., restrictions on using CG resources associated with one or more LCHs) for which the UL enhancements may apply during congestion, for example.

[0234] In some examples, the WTRU may perform uplink enhancement (e.g., RLC enhancement, MAC enhancement, and / or the like) for a data set based on one or more triggering events. For example, the WTRU may be configured with one or more triggering events for uplink enhancement of a data set. The WTRU may determine whether to perform the uplink enhancement procedure for a data set if the triggering event is satisfied. For example, the WTRU may trigger uplink enhancement procedure based on one or more of the following: the expiry of a timer (e.g., uplink enhancement Timer); the duration that the data set stay in the buffer; reception status of a data set (e.g., the same data set or an associated data set with the one applying uplink enhancement procedure; and / or transmission status of a data set.

[0235] The WTRU may trigger uplink enhancement procedure for a data set based on the expiry of a timer. In some examples, the WTRU may be configured with a timer to trigger an uplink enhancement procedure. The WTRU may perform an uplink enhancement procedure upon expiry of the timer. The value (e.g., the initial value) of the timer may be configured by the network. The value of the timer may be (e.g., may be based on) a function of one or more of the QoS parameters of the data set, such as the importance of the data set, PDB, PSDB, and / or PSDD. The WTRU may stop the timer if the data set is delivered successfully at the receiver and / or if the data set is discarded. The WTRU may start the timer based on one or more of the following: the arrival of the data set; the transmission (e.g., the initial transmission of the data set); and / or if the RLC PDU or PDU segment is submitted to a lower layer (e.g., MAC).

[0236] The WTRU may start the timer based on the arrival of the data set. For example, the WTRU may start uplink enhancement timer for a PDU set upon arrival of the PDU set (e.g., upon the arrival of the first PDU, each PDU, a specific PDU, or the last PDU of the PDU set). The WTRU may trigger uplink enhancement for a data set if the data set stays in the buffer for a long time and has not been served (e.g., transmitted).

[0237] The WTRU may start the timer based on the transmission (e.g., the initial transmission of the data set). For example, the WTRU may trigger uplink enhancement for retransmission of a PDU or PDU segment.

[0238] In some examples, the WTRU may trigger an uplink enhancement procedure for a data set based on the duration of that the data set in the buffer. For example, the WTRU may trigger uplink enhancement for aPDU or PDU segment if the duration the PDU or PDU segment stays in the buffer is greater than a configured threshold.

[0239] In some examples, the WTRU may perform an uplink enhancement procedure for a data set based on the reception status of a data set (e.g, the same data set or an associated data set with the one applying uplink enhancement procedure). The reception status of a data set may be derived from HARQ feedback and / or RLC status reporting.

[0240] In some examples, the WTRU may trigger an HARQ NACK feedback based RLC retransmission for an RLC PDU and / or RLC PDU segment. For example, the WTRU may retransmit an RLC PDU or PDU segment if the WTRU receives one or more HARQ NACK feedbacks (e.g., messages) for a MAC PDU including the RLC PDU or the RLC PDU segment. In some examples, the WTRU may trigger WTRU autonomous RLC retransmission for one or more PDUs (e.g., subsequent PDUs) of a PDU set if the WTRU receives one or more HARQ NACK feedbacks (e.g., messages) for one or more PDUs (e.g., one or more first PDUs) of the PDU set. In some examples, the WTRU may trigger WTRU autonomous RLC retransmission for one or more PDUs (e.g., subsequent PDUs) of a PDU set if the WTRU receives NACK feedbacks (e.g., messages) from a report, such as an RLC STATUS report, for one or more PDUs from the PDU set. In some examples, the WTRU may trigger WTRU autonomous RLC retransmission for a PDU set if the WTRU receives a NACK feedback (e.g., message) for one or more PDU sets (e.g., the PDU sets arrived before the current PDU set).

[0241] In some examples, the WTRU may perform an uplink enhancement procedure for a data set based on the transmission status of the data set. The transmission status of a data set may be based on the number of transmissions the WTRU has made for one or more PDUs and / or PDU segments of the data set.

[0242] In some examples, the WTRU may perform uplink enhancement for an RLC PDU if the RLC PDU has been transmitted one or more times. The number of transmissions made for the RLC PDU to trigger uplink enhancement procedure may be fixed (e.g, fixed as one or set to one) or configured by the network. For example, the WTRU may trigger uplink enhancement for an RLC PDU retransmission. For example, the WTRU may perform multicarrier duplication for an RLC PDU retransmission. For example, the WTRU may perform PHY repetition for an RLC PDU retransmission. The WTRU may increase the reliability of in RLC PDU retransmission and may help to increase the successful reception probability of the RLC PDU retransmission.

[0243] The WTRU may determine which data set to perform uplink enhancement. In some examples, the WTRU may trigger uplink enhancement for a PDU or PDU segment. The WTRU may determine which additional PDU or PDU segment to perform uplink enhancement based on one or more of the following:whether the WTRU performs uplink enhancement for PDU segment; the type of PDU set associated with the PDU; and / or the reliability parameter (e.g, reliability requirement) associated with the PDU set.

[0244] The WTRU may determine which additional PDU or PDU segment to perform uplink enhancement based on whether the WTRU performs uplink enhancement for PDU segment. For example, upon triggering uplink enhancement for a PDU segment, the WTRU may trigger uplink enhancement for a PDU segment of the PDU. The WTRU may increase the reliability of the PDU associated with the PDU segments.

[0245] The WTRU may determine which additional PDU or PDU segment to perform uplink enhancement based on the type of PDU set associated with the PDU. For example, for the first type of PDU set (e.g., reliable delivery of one or more (e.g., all) PDUs in the set), the WTRU may trigger uplink enhancement for one or more (e.g., all) PDUs in the PDU set. For example, for the second type of PDU set (e.g., conditional delivery), the WTRU may trigger uplink enhancement for the PDUs with the importance being equal or greater than a configured threshold. For example, for the third type of PDU set (e.g, X out of Y), the WTRU may trigger uplink enhancement for a configured number of PDU in the PDU set.

[0246] The WTRU may determine which additional PDU or PDU segment to perform uplink enhancement based on whether PSIHI is enabled / disabled for the PDU set associated with the PDU. For example, if PSIHI for the PDU set is enabled, the WTRU may trigger uplink enhancement for one or more (e.g, all) PDUs in the PDU set or one or more (e.g, all) the remaining PDU in the PDU set (e.g, which has not been transmitted successfully). For example, if PSIHI is disabled, the WTRU may trigger uplink enhancement on a per PDU basis.

[0247] The WTRU may determine which additional PDU or PDU segment to perform uplink enhancement based on the reliability parameter (e.g, reliability requirement, such as PSER) associated with the PDU set. In some examples, the WTRU may determine the number of PDU to perform uplink enhancement to satisfy the PSER parameter (e.g, the PSER requirement) of the PDU set. For example, the WTRU may select a configured number of PDUs to trigger uplink enhancement.

[0248] The WTRU may send an indication regarding uplink enhancement transmission. In some examples, the WTRU may trigger sending (e.g, transmitting) an indication to a network, e.g, using UCI, MAC CE, and / or RRC, upon uplink enhancement triggered is satisfied. In some examples, the WTRU may trigger a MAC CE (e.g, buffer status report (BSR), delay status report (DSR), and / or the like) to inform the network the information associated with uplink enhancement triggering event. The WTRU may trigger a UCI (e.g, scheduling request (SR)) upon triggering MAC CE if the WTRU does not have a sufficient grant within a period to transmit the triggered MAC CE. The WTRU may send one or more of the following indications to thenetwork: which triggering condition is satisfied; and / or the properties of the data set satisfying the triggering conditions.

[0249] The WTRU may send an indication to the network indicating which triggering condition has been satisfied (e.g., met) and the associated value of the parameters which triggers uplink enhancement. For example, the WTRU may be configured with multiple triggering conditions for uplink enhancement. The WTRU may indicate (e.g., implicitly indicate) which triggering condition has been satisfied (e.g., met). For example, the WTRU may be configured to perform uplink enhancement if the importance of the PDU set is greater than a configured threshold. The WTRU may trigger (e.g., then trigger) uplink enhancement upon the importance of one or more PDU sets is satisfied. The WTRU may indicate (e.g., then indicate) the information regarding the amount of data (e.g., number of PDU sets) satisfying uplink enhancement condition and / or the associated importance of the PDU set.

[0250] The WTRU may send an indication to the network indicating the properties of the data set (e.g., QoS, the amount of data, etc.) satisfy the triggering condition. For example, the WTRU may indicate the remaining PSDB of the data set, the priority, and / or the importance of the data set. For example, the WTRU may indicate the amount of data (e.g., via MAC CE) having importance being greater than a configured threshold. For example, the WTRU may indicate the amount of data (e.g., via MAC CE) having the remaining PSDB being greater than a configured threshold. For example, for WTRU autonomous RLC retransmission, the WTRU may indicate the amount of data associated with such uplink enhancement.

[0251] The WTRU may be prohibited from performing uplink enhancement. For example, the WTRU may be prohibited from performing uplink enhancement, such as an RLC enhancement, a MAC enhancement, and / or the like. The network may be allowed to limit the WTRU in using excessive resource. In some examples, the WTRU may be configured with a timer (e.g., a prohibit timer, such as uplink enhancement prohibit timer) to prohibit the WTRU from performing uplink enhancement. The WTRU may not be allowed to perform uplink enhancement if the prohibit timer is running. In some examples, the WTRU may be configured with another timer (e.g., a second timer, such as uplink enhancement allowance timer) to allow the WTRU to perform uplink enhancement. The WTRU may perform uplink enhancement if the timer (e.g., the second timer, such as uplink enhancement allowance timer) is running. The WTRU may not be allowed to perform uplink enhancement if the timer (e.g., the second timer, such as uplink enhancement allowance timer) has expired. The network may configure the WTRU to control the amount of data to perform an uplink enhancement function.

[0252] In some examples, the WTRU may be configured with one or more prohibit / allow timers. The timers (e.g., the prohibit timers and / or the allow timers) may be associated with uplink enhancement in a layer. Forexample, the WTRU may be configured with a timer (e.g., a first timer) for RLC enhancement and / or another timer (e.g., a second timer) for MAC enhancement.

[0253] In some examples, the WTRU may be configured with one or more prohibit / allow timers. The timers (e.g., the prohibit timers and / or the allow timers) may be associated with uplink enhancement function. For example, the WTRU may be configured with a WTRU autonomous RLC retransmission enhancement timer to allow / prohibit the WTRU from autonomously retransmitting an RLC PDU or PDU segment, e.g., without waiting for STATUS feedback. For example, the WTRU may be configured with a timer to allow / prohibit the WTRU from overriding / adapting one or more MAC parameters. The WTRU may initiate uplink enhancement allowance timer for uplink enhancement upon triggering uplink enhancement function. Regarding a prohibit timer, the WTRU may initiate a prohibit timer for uplink enhancement based on one or more of the following: the amount of data or resources following uplink enhancement procedure; the duration from the time uplink enhancement that was enabled for a data set; an indication from the network; and / or one or more properties associated with data.

[0254] The WTRU may initiate a prohibit timer for uplink enhancement based on the amount of data or resources (e.g., number of PDUs, number of transmission resources, and / or the like) following the uplink enhancement procedure. In some examples, for a WTRU autonomous RLC retransmission prohibit timer, the WTRU may initiate the timer if the WTRU has autonomously retransmitted a configured number of PDUs or bytes. In some examples, for a WTRU overriding / adapting MAC parameters prohibit timer, the WTRU may initiate the timer if the amount of data needed (e.g., required) for overriding / adapting a MAC parameter is greater than (e.g., exceeds) a configured threshold.

[0255] The WTRU may initiate a prohibit timer for uplink enhancement based on the duration from the time uplink enhancement that was enabled for a data set. For example, the WTRU may initiate a prohibit timer after a configured duration from the time the WTRU enables an uplink enhancement function.

[0256] The WTRU may initiate a prohibit timer for uplink enhancement based on an indication from the network. For example, the WTRU may initiate a timer upon reception of an implicit or explicit indication from the network, e.g., to prohibit the WTRU from performing an uplink enhancement function. The network may prohibit (e.g., temporarily prohibit) the WTRU from performing an uplink enhancement function.

[0257] The WTRU may initiate a prohibit timer for uplink enhancement based on one or more properties associated with data (e.g., importance of data set, priority level of any PDU / segment of a data set, presence of PSI HI flag / indication, and / or the like). For example, the WTRU may initiate a prohibit timer if the importance values of previously transmitted one or more data sets are greater than a configured threshold.

[0258] FIG. 2 illustrates an example of performing an uplink enhancement procedure. As illustrated in FIG.2, the WTRU may perform an uplink enhancement procedure 200 (e.g, RLC enhancement, MAC enhancement, and / or the like) for a data set (e.g., a PDU segment, PDU, a subset of a PDU set, a PDU set, data burst, an RLC PDU or a PDU segment, and / or the like), e.g., as a function of the QoS of the data set, one or more configured parameters of the RB / LCH associated with the data set, and / or a configured triggering condition.

[0259] As illustrated in FIG. 2 (e.g., 202), the WTRU may receive an indication of one or more of the following configurations from the network (e.g., via an RRC message): a threshold associated with a QoS parameter of a data set (e.g., PDB, PSDB, PSDD, importance, priority, etc.) to trigger uplink enhancement (e.g., RLC, MAC enhancement); a threshold associated with a parameter for the RB / LCH (e.g., priority, PBR, DiscardTimer, and / or the like) to trigger uplink enhancement; and / or a condition (e.g., a triggering condition) to perform uplink enhancement (e.g., RLC enhancement, MAC enhancement, and / or the like) for transmission of the data set.

[0260] In some examples, the WTRU may receive a configuration for a threshold associated with a QoS parameter of a data set (e.g, PDB parameter, PSDB parameter, PSDD parameter, importance parameter, priority parameter, etc.) to trigger uplink enhancement (e.g, RLC, MAC enhancement, and / or the like). For example, the WTRU may receive configuration of a remaining PSDB threshold.

[0261] In some examples, the WTRU may receive a configuration for a threshold associated with a parameter for the RB / LCH (e.g, priority parameter, PBR parameter, DiscardTimer, and / or the like) to trigger uplink enhancement. For example, the WTRU may receive configuration of which RB / LCH to enable uplink enhancement.

[0262] In some examples, the WTRU may receive a configuration (e.g, configuration information) for a condition (e.g, a triggering condition) to perform uplink enhancement (e.g, RLC enhancement, MAC enhancement, and / or the like) for transmission of the data set. For example, the WTRU may receive configuration of number of HARQ NACKs for the RLC PDU or PDU segment to trigger retransmission of the RLC PDU.

[0263] In some examples, the WTRU may receive configuration information from a network. The network described herein may be, or may include, one or more of the following: a base station, a gNB, a transmission / reception point, a radio access network node, an access node, a core network function, or an application function. The configuration information may indicate a condition to trigger an uplink enhancement. In an example, the uplink enhancement may be associated with a radio link control (RLC) enhancement. Inanother example, the uplink enhancement may be associated with (e.g., may be further associated with) a medium access control (MAC) enhancement.

[0264] As described herein, the configuration information may include one or more of the following: a timer, a threshold value associated with the importance of at least one of an RLC PDU or a PDU segment, a threshold value associated with a quality of service (QoS) parameter for the data set, a threshold value associated with a parameter for a resource block (RB), a threshold value associated with a parameter for a logical channel (LCH), or a triggering condition associated with the performance of the uplink enhancement. The threshold value associated with the QoS parameter may be, or may include, one or more of the following: a packet delay budget (PDB) parameter, a PDU set delay budget (PSDB) parameter, a PDU Set Delay Deadline (PSDD) parameter, an importance parameter, or a priority parameter. The threshold value associated with the parameter for at least one of the RB or the LCH may be, or may include, one or more of the following: a priority parameter, a parameter associated with a prioritized bit rate (PBR), or a discard timer. The triggering condition described herein may be associated with receiving a number of Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgements (NACKs) for an RLC PDU or a PDU segment.

[0265] As illustrated in FIG. 2 (e.g., 204), the WTRU may receive a data set from an upper layer. The data set may be, or may include, one or more of the following: an RLC protocol data unit (PDU) or a PDU segment. Performing the uplink transmission using the uplink enhancement as described herein may include the device being configured to perform retransmission of at least one of the RLC PDU or the PDU segment.

[0266] As illustrated in FIG. 2 (e.g., 206), the WTRU may determine whether to perform an uplink enhancement procedure for the data set. For example, if the QoS of the data set satisfies the configured threshold, if a parameter of the RB / LCH associated with the data set satisfies the configured threshold, and / or if the triggering condition is satisfied, the WTRU may perform the uplink enhancement procedure for the data set. For RLC enhancement, the WTRU may perform WTRU autonomous RLC retransmission (e.g., without waiting for a PDU STATUS report) of an RLC PDU if the PSDB of the PDU is smaller than a threshold. The WTRU may perform RLC retransmission if the WTRU receives a configured number of HARQ NACK associated with the RLC PDU. For MAC enhancement, the WTRU may override an LCP restriction. The LCP restriction may prohibit the data from an RB / LCH to use the grant. By overriding the LCP restriction, the WTRU may allow an RLC PDU to transmit in a restricted grant.

[0267] In some examples, the device may determine whether to perform the uplink enhancement based on the configuration information. The determination of whether to perform the uplink enhancement may be based on whether the condition is satisfied.

[0268] As illustrated in FIG. 2 (e.g., 208), the WTRU may perform uplink transmission of the data set. For example, based on a determination to perform the uplink enhancement, the device may perform the uplink transmission using the uplink enhancement.

[0269] In some examples, the configuration information may include a timer. The device may initiate the timer based on one or more of the following: the reception of an RLC service data unit (SDU), the transmission of at least one of an RLC PDU or a PDU segment to a MAC layer, or the transmission of a MAC PDU that is associated with at least one of the RLC PDU or the PDU segment. The device may determine whether the timer has expired. The condition may be satisfied based on a determination that the timer has expired.

[0270] In some examples, the configuration information may include a threshold value associated with the importance of at least one of an RLC PDU or a PDU segment. The device may determine that the threshold value associated with the importance of at least one of the RLC PDU or the PDU segment is above a configured threshold value. Based on the determination that the threshold value is above the configured threshold value, the device may enable polling of at least one of the RLC PDU or the PDU segment.

[0271] In some examples, determining whether to perform the uplink enhancement may include the device being configured to perform one or more of the following. The device may determine whether a QoS associated with the data set is above a threshold value. The threshold value may be associated with a QoS parameter. The condition may be satisfied based on a determination that the QoS associated with the data set is above the threshold value. The device may determine whether a parameter associated with an RB is above the threshold value. The threshold value may be associated with the parameter for the RB. The condition may be satisfied based on a determination that the parameter associated with the RB is above the threshold value. The device may determine whether a parameter associated with an LCH is above the threshold value. The threshold value may be associated with the parameter for the LCH. The condition may be satisfied based on a determination that the parameter associated with the LCH is above the threshold value. The device may determine whether a triggering condition has been satisfied.

[0272] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and / or wireless connections) and / or 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, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as CD-ROM disks, and / ordigital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

CLAIMSWhat is Claimed:1 . A wireless transmit / receive unit (WTRU) comprising: a processor configured to: receive configuration information from a network, wherein the configuration information indicates a condition to trigger an uplink enhancement, wherein the uplink enhancement is associated with a radio link channel (RLC) enhancement; receive a data set associated with an uplink transmission; determine whether to perform the uplink enhancement based on the configuration information, wherein the determination of whether to perform the uplink enhancement is based on whether the condition is satisfied; and based on a determination to perform the uplink enhancement, perform the uplink transmission using the uplink enhancement.

2. The WTRU of claim 1 , wherein the data set comprises at least one of an RLC protocol data unit (PDU) or a PDU segment, and wherein to perform the uplink transmission using the uplink enhancement comprises the processor being configured to perform retransmission of the at least one of the RLC PDU or the PDU segment.

3. The WTRU of claim 1 , wherein the configuration information comprises a timer, and wherein the processor is configured to: initiate the timer based on at least one of a reception of an RLC service data unit (SDU), a transmission of at least one of an RLC PDU or a PDU segment to a medium access control (MAC) layer, or a transmission of a MAC PDU that is associated with at least one of the RLC PDU or the PDU segment; and determine whether the timer has expired, wherein the condition is satisfied based on a determination that the timer has expired.

4. The WTRU claim 1 , wherein the configuration information comprises a threshold value associated with an importance of at least one of an RLC PDU or a PDU segment, and wherein the processor is configured to:determine that the threshold value associated with the importance of at least one of the RLC PDU or the PDU segment is above a configured threshold value; and based on the determination that the threshold value is above the configured threshold value, enable polling of the at least one of the RLC PDU or the PDU segment.

5. The WTRU claim 1 , wherein the configuration information further comprises at least one of a threshold value associated with a quality of service (QoS) parameter for the data set, a threshold value associated with a parameter for a resource block (RB), a threshold value associated with a parameter for a logical channel (LCH), or a triggering condition associated with the performance of the uplink enhancement.

6. The WTRU of claim 5, wherein the threshold value associated with the QoS parameter comprises at least one of a packet delay budget (PDB) parameter, a PDU set delay budget (PSDB) parameter, a PDU Set Delay Deadline (PSDD) parameter, an importance parameter, or a priority parameter, wherein the threshold value associated with the parameter for at least one of the RB or the LCH comprises at least one of a priority parameter, a parameter associated with prioritized bit rate (PBR), or a discard timer, and wherein the triggering condition is associated with receiving a number of Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgements (NACKs) for an RLC PDU or a PDU segment.

7. The WTRU of claim 1 , wherein to determine whether to perform the uplink enhancement comprises the processor being further configured to at least: determine whether a QoS associated with the data set is above a threshold value, wherein the threshold value is associated with a QoS parameter, and wherein the condition is satisfied based on a determination that the QoS associated with the data set is above the threshold value; determine whether a parameter associated with an RB is above the threshold value, wherein the threshold value is associated with the parameter for the RB, wherein the condition is satisfied based on a determination that the parameter associated with the RB is above the threshold value; determine whether a parameter associated with an LCH is above the threshold value, wherein the threshold value is associated with the parameter for the LCH, wherein the condition is satisfied based on a determination that the parameter associated with the LCH is above the threshold value; or determine whether a triggering condition has been satisfied.

8. The WTRU of claim 1 , wherein the uplink enhancement is further associated with a MAC enhancement.

9. The WTRU of claim 1 , wherein the network comprises at least one of a base station, a gNB, a transmission / reception point, a radio access network node, an access node, a core network function, or an application function.

10. A method comprising: receiving configuration information from a network, wherein the configuration information indicates a condition to trigger an uplink enhancement, wherein the uplink enhancement is associated with a radio link channel (RLC) enhancement; receiving a data set associated with an uplink transmission; determining whether to perform the uplink enhancement based on the configuration information, wherein the determination of whether to perform the uplink enhancement is based on whether the condition is satisfied; and based on a determination to perform the uplink enhancement, performing the uplink transmission using the uplink enhancement.

11. The method of claim 10, wherein the data set comprises at least one of an RLC protocol data unit (PDU) or a PDU segment, and wherein performing the uplink transmission using the uplink enhancement comprises performing retransmission of the at least one of the RLC PDU or the PDU segment.

12. The method of claim 10, wherein the configuration information comprises a timer, and wherein the method comprises: initiating the timer based on at least one of a reception of an RLC service data unit (SDU), a transmission of at least one of an RLC PDU or a PDU segment to a medium access control (MAC) layer, or a transmission of a MAC PDU that is associated with at least one of the RLC PDU or the PDU segment; and determining whether the timer has expired, wherein the condition is satisfied based on a determination that the timer has expired.

13. The method of claim 10, wherein the configuration information comprises a threshold value associated with an importance of at least one of an RLC PDU or a PDU segment, and wherein the method comprises: determining that the threshold value associated with the importance of at least one of the RLC PDU or the PDU segment is above a configured threshold value; and based on the determination that the threshold value is above the configured threshold value, enabling polling of the at least one of the RLC PDU or the PDU segment.

14. The method of claim 10, wherein the configuration information further comprises at least one of a threshold value associated with a quality of service (QoS) parameter for the data set, a threshold value associated with a parameter for a resource block (RB), a threshold value associated with a parameter for a logical channel (LCH), or a triggering condition associated with the performance of the uplink enhancement.

15. The method of claim 14, wherein the threshold value associated with the QoS parameter comprises at least one of a packet delay budget (PDB) parameter, a PDU set delay budget (PSDB) parameter, a PDU Set Delay Deadline (PSDD) parameter, an importance parameter, or a priority parameter, wherein the threshold value associated with the parameter for at least one of the RB or the LCH comprises at least one of a priority parameter, a parameter associated with prioritized bit rate (PBR), or a discard timer, and wherein the triggering condition is associated with receiving a number of Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgements (NACKs) for an RLC PDU or a PDU segment.

16. The method of claim 10, wherein determining whether to perform the uplink enhancement further comprises at least: determining whether a QoS associated with the data set is above a threshold value, wherein the threshold value is associated with a QoS parameter, wherein the condition is satisfied based on a determination that the QoS associated with the data set is above the threshold value; determining whether a parameter associated with an RB is above a threshold value, wherein the threshold value is associated with the parameter for the RB, wherein the condition is satisfied based on a determination that the parameter associated with the RB is above the threshold value;determining whether a parameter associated with an LCH is above a threshold value, wherein the threshold value is associated with the parameter for the LCH, wherein the condition is satisfied based on a determination that the parameter for the LCH is above the threshold value; or determining whether a triggering condition has been satisfied.

17. The method of claim 10, wherein the uplink enhancement is further associated with a MAC enhancement.

18. The method of claim 10, wherein the network comprises at least one of a base station, a gNB, a transmission / reception point, a radio access network node, an access node, a core network function, or an application function.

Images