Configured grant transmission in controlled environment

Abstract

To provide a technique of configured grant transmission in a controlled environment.SOLUTION: A device (WTRU)) may determine which information (e.g., among multiple transport blocks (TBs)) is to be transmitted on (one or more) resources of a physical uplink channel (PUCCH) transmission occasion of a configured grant (CG). The device may receive configuration information. The configuration information may indicate a resource associated with the CG. The device may determine whether first information of a first TB or second information of a second TB is to be transmitted (e.g., on the resource associated with the CG) based on one or more of downlink feedback information (DFI) reception, a cause for which information of a TB (e.g., the first TB or the second TB) has not been transmitted in a previous transmission, and a property of content in the TB (e.g., control information or data).SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 060,850, filed August 4, 2020, and U.S. Provisional Patent Application No. 63 / 136,273, filed January 12, 2021, the disclosures of which are incorporated herein by reference in their entireties. [Background technology]

[0002] Mobile communications using wireless communications continues to evolve. The fifth generation of mobile communications radio access technology (RAT) is sometimes referred to as 5G new radio (NR). The previous generation (legacy) mobile communications RAT may be, for example, fourth generation (4G) long term evolution (LTE). Summary of the Invention

[0003] Information in a TB of multiple transport blocks (TBs) may be transmitted using resource(s) of a physical uplink channel (PUCCH) transmission opportunity of a configured grant (CG). The CG may indicate a PUCCH transmission opportunity. A device (e.g., a wireless transmit / receive unit (WTRU)) may determine information to be transmitted on resource(s) of a PUCCH transmission opportunity of a CG (e.g., of multiple TBs). In one example, the device may receive configuration information. The configuration information may indicate resources associated with the CG. The device may determine whether to transmit first information of a first TB or second information of a second TB (e.g., on resources associated with the CG). The first TB may include the first information, and the second TB may include the second information. The device may determine the first TB and the second TB. The device may decide whether to transmit first information of a first TB or second information of a second TB (e.g., on resources associated with a CG) based on one or more of the following: receipt of downlink feedback information (DFI), the reason why the information of the TB (e.g., the first TB or the second TB) was not transmitted in a previous transmission, and the nature of the content in the TB (e.g., control information or data).

[0004] The device may determine whether to transmit the first information or the second information on resources associated with the CG based on receipt of a DFI. For example, if the device receives first feedback for a first preceding transmission including the first information, the first feedback indicating that the first information has not been received, and the device has not received a DFI for a second preceding transmission including the second information, the device may determine to transmit the first information for the first TB using resources associated with the CG. The device may transmit the first information for the first TB using resources associated with the CG. In an example, the first information may be associated with a first logical channel priority, and the second information may be associated with a second logical channel priority. The first logical channel priority may be equal to or higher than the second logical channel priority.

[0005] The device may determine whether to transmit the first information or the second information on a resource associated with the CG based on the reason why the first information of the first TB has not been transmitted and / or the reason why the second information of the second TB has not been transmitted. For example, if the first information has not been transmitted on the first preceding resource due to priority deprioritization of the first TB and the second information has not been transmitted on the second preceding resource due to a listen before talk (LBT) failure, the device may determine to transmit the first information of the first TB using a resource associated with the CG. The device may transmit the first information of the first TB using a resource associated with the CG. In an example, the first logical channel priority may be equal to or higher than the second logical channel priority.

[0006] The device may determine whether to transmit the first information or the second information on a resource associated with a CG based on the nature of the content of the first TB and / or the nature of the content of the second TB. For example, if the first information includes control information and has not been transmitted on the first preceding resource, and the second information includes data (e.g., data only) and has been transmitted in the second preceding transmission, the device may determine to transmit the first information of the first TB using a resource associated with a CG. If the first information includes a medium access control (MAC)-control element (CE) and has not been transmitted on the first preceding resource, and the second information includes data (e.g., data only) and has been transmitted in the second preceding transmission, the device may determine to transmit the first information of the first TB using a resource associated with a CG.

[0007] In some examples, the first preceding transmission may be a most recent transmission of the first information, and the second transmission may be a most recent transmission of the second information. The first feedback may include a DFI for the first preceding transmission. The first preceding transmission may be a PUCCH transmission opportunity indicated by a CG or a PUCCH transmission opportunity indicated by another uplink grant. The configuration information may indicate which resources are associated with the PUCCH transmission opportunity. The first preceding resource and the second preceding resource may differ in the time domain and / or the frequency domain.

[0008] The transmission may be sent using resources associated with the CG. For example, the WTRU may send the transmission based on a decision whether to transmit the first information or the second information on resources associated with the CG. [Brief explanation of the drawings]

[0009] [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1B is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1C] 1A is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1D] 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 2] 1 illustrates an example in which the WTRU receives downlink control information (DCI) scheduling a dynamic grant (DG) at a hybrid automatic repeat request process ID (HARQ PID) before transmission of a transport block (TB) and after the WTRU constructs a protocol data unit (PDU) for a HARQ PID, where the start time of the DG is earlier than the start time of the configured grant and the DG overlaps with a CG in the time domain. [Figure 3] 10 illustrates an example in which the WTRU receives a DCI scheduling a DG on the HARQ PID during a TB transmission on a CG opportunity and after the WTRU constructs a PDU for the HARQ PID, and the start time of the DG is after the start time of the CG. [Figure 4] For example, an example of prioritization used to determine which information of multiple TBs to transmit on resources associated with a CG opportunity is shown. DETAILED DESCRIPTION OF THE INVENTION

[0010] 1A illustrates an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. Communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messaging, broadcasts, etc., to multiple wireless users. Communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 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), etc.

[0011] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RANs 104 / 113, CNs 106 / 115, public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of 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 “STA,” may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

[0012] The communications system 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 communications networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNodeB, a Home Node B, a Home eNodeB, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each shown as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0013] 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), a relay node, etc. The base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a particular geographic area, which may be relatively fixed or may change over time. A cell may be further 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 transceiver for each sector of the cell. In one 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, using beamforming to transmit and / or receive signals in desired spatial directions.

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

[0015] More specifically, as noted above, the communications system 100 may be a multiple-access system and may use one or more channel access schemes, such as, for example, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114 a and the WTRUs 102 a, 102 b, 102 c in the RAN 104 / 113 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 communications protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

[0016] In one 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).

[0017] In one 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).

[0018] In one 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 jointly implement LTE radio access and NR radio access, e.g., using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

[0019] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology 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), or the like.

[0020] 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point and may utilize any suitable RAT to facilitate wireless connectivity in a local area such as a location such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. 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 one 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 establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). 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 need to access the Internet 110 through the CN 106 / 115.

[0021] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, such as different throughput, latency, error tolerance, reliability, data throughput, and mobility requirements. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A , it will be understood that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs employing 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 utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0022] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a public switched telephone network providing 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) of the TCP / IP Internet protocol suite. The network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the network 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.

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

[0024] 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include, among other things, 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. It will be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0025] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. 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. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0026] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., 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 one 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 understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0027] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may use 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.

[0028] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0029] The processor 118 of the WTRU 102 may be coupled to and may receive user-entered data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an 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. Furthermore, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or 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, etc. In other embodiments, the processor 118 may access information and store data in memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown).

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

[0031] The processor 118 may also be coupled to a 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 instead of information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0032] 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 electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), 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, etc. The peripheral device 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, a direction 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.

[0033] The WTRU 102 may include a full-duplex radio where transmission and reception of some or all of the signals (e.g., associated with a particular subframe for both the UL (e.g., for transmission) and downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference through hardware (e.g., chokes) or processor-based signal processing (e.g., via a separate processor (not shown) or processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for transmission and reception of either some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or downlink (e.g., for reception)).

[0034] 1C is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.

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

[0036] Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling, etc. in the UL and / or DL. As shown in FIG. 1C, the eNodeBs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0037] 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the foregoing elements is illustrated as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0038] The MME 162 may be connected to each of the eNodeBs 162a, 162b, 162c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, etc. 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.

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

[0040] The SGW 164 may be connected to a 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.

[0041] 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 landline communications devices. For example, the CN 106 may include or 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. Furthermore, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0042] Although the WTRU is depicted in FIGS. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments, such a terminal may use a wired communication interface (e.g., temporarily or permanently) with the communication network.

[0043] In a representative embodiment, the other network 112 may be a WLAN.

[0044] A WLAN in infrastructure Basic Service Set (BSS) mode may have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating from outside the BSS to a STA may arrive through the AP and be delivered to the STA. Traffic originating from a STA to a destination outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs within the BSS may be transmitted, for example, through the AP; the source STA may send traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between a source STA and a destination STA (e.g., directly between them) in a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (e.g., all of the STAs) may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad hoc" communication mode.

[0045] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel may be the operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, for example, in an 802.11 system, Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA) with collision avoidance may be implemented. With CSMA / CA, STAs (e.g., all STAs), 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.

[0046] High Throughput (HT) STAs may use 40 MHz wide channels for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

[0047] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz and / or 80 MHz wide channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data may pass through a segment parser that may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed and the combined data may be transmitted to the Medium Access Control (MAC).

[0048] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter-type control / machine-type communications, such as MTC devices within macro coverage areas. MTC devices may have specific capabilities, including, for example, support for (e.g., only for) specific and / or limited bandwidths. MTC devices may include batteries with above-threshold battery life (e.g., to maintain very long battery life).

[0049] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as a primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be configured and / or limited by the STAs among all STAs operating in the BSS that support the minimum bandwidth operating mode. In an 802.11ah example, the primary channel can be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) the 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) configuration can depend on the condition of the primary channel. For example, if the primary channel is busy due to a STA (that only supports 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered busy, even though most of the frequency band may remain idle and be available for use.

[0050] In the United States, the available frequency band that can be used by 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz depending on the country code.

[0051] 1D is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As mentioned above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using NR radio technology. The RAN 113 may also communicate with the CN 115.

[0052] The RAN 113 may include gNBs 180a, 180b, and 180c, although it will be understood that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, and 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit and / or receive signals to the gNBs 180a, 180b, and 180c. Thus, the gNB 180a may, for example, transmit wireless signals to and / or receive wireless signals from the WTRU 102a using multiple antennas. In one embodiment, the gNBs 180a, 180b, and 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 an unlicensed spectrum, and the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, and 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or 180c).

[0053] The WTRUs 102a, 102b, 102c may communicate with the 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 the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0054] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., eNodeBs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to gNBs 180a, 180b, 180c while also communicating with and connecting to another RAN, such as eNodeBs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, while the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0055] 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 for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a, 184b, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D , the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.

[0056] 1D 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 is shown as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0057] 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 function as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the 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.

[0058] The SMFs 183a and 183b may be connected to the AMFs 182a and 182b in the CN 115 via an N11 interface. The SMFs 183a and 183b may also be connected to the UPFs 184a and 184b in the CN 115 via an N4 interface. The SMFs 183a and 183b may select and control the UPFs 184a and 184b and configure the routing of traffic through the UPFs 184a and 184b. The SMFs 183a and 183b may perform other functions, such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0059] The UPFs 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 UPFs 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, etc.

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

[0061] 1A-1D and their corresponding descriptions, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices 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 simulate network and / or WTRU functions.

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

[0063] One or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, e.g., one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0064] Described herein are systems, methods, and apparatus for transmission with configured grants in a controlled environment. A wireless transmit / receive unit (WTRU) can flush HARQ process buffers of transport blocks (TBs) generated for transmission with configured grant (CG) opportunities, for example, when a higher priority dynamic grant (DG) is signaled for the same hybrid automatic retransmission request (HARQ) process and overlaps with the CG in the time domain (and, for example, the CG transmission has not started). The flushed protocol data units (PDUs) can be mapped to different HARQ process identifiers (PIDs). The WTRU can map the flushed PDUs to different applicable HARQ PIDs.

[0065] A TB may be transmitted in an overlapping DG if it has the same or higher priority. The WTRU may discard a DG if it has the same transport block size (TBS) and / or the same or lower priority as a TB generated for a CG. The WTRU may prioritize (e.g., as a function) between initial transmission and retransmissions in the CG. The WTRU may adjust (e.g., as a function) the reference time delivered by the gNodeB.

[0066] Information in a TB of multiple transport blocks (TBs) may be transmitted using resource(s) of a physical uplink channel (PUCCH) transmission opportunity of a configured grant (CG). The CG may indicate a PUCCH transmission opportunity. A device (e.g., a wireless transmit / receive unit (WTRU)) may determine information to be transmitted on resource(s) of a PUCCH transmission opportunity of a CG (e.g., of multiple TBs). In one example, the device may receive configuration information. The configuration information may indicate resources associated with the CG. The device may determine whether to transmit first information of a first TB or second information of a second TB (e.g., on resources associated with the CG). The first TB may include the first information, and the second TB may include the second information. The device may determine the first TB and the second TB. The device may decide whether to transmit first information of a first TB or second information of a second TB (e.g., on resources associated with a CG) based on one or more of the following: receipt of downlink feedback information (DFI), the reason why the information of the TB (e.g., the first TB or the second TB) was not transmitted in a previous transmission, and the nature of the content in the TB (e.g., control information or data).

[0067] The device may determine whether to transmit the first information or the second information on resources associated with the CG based on receipt of a DFI. For example, if the device receives first feedback for a first preceding transmission including the first information, the first feedback indicating that the first information has not been received, and the device has not received a DFI for a second preceding transmission including the second information, the device may determine to transmit the first information for the first TB using resources associated with the CG. The device may transmit the first information for the first TB using resources associated with the CG. In an example, the first information may be associated with a first logical channel priority, and the second information may be associated with a second logical channel priority. The first logical channel priority may be equal to or higher than the second logical channel priority.

[0068] The device may determine whether to transmit the first information or the second information on a resource associated with the CG based on the reason why the first information of the first TB has not been transmitted and / or the reason why the second information of the second TB has not been transmitted. For example, if the first information has not been transmitted on the first preceding resource due to priority deprioritization of the first TB and the second information has not been transmitted on the second preceding resource due to a listen before talk (LBT) failure, the device may determine to transmit the first information of the first TB using a resource associated with the CG. The device may transmit the first information of the first TB using a resource associated with the CG. In an example, the first logical channel priority may be equal to or higher than the second logical channel priority.

[0069] The device may determine whether to transmit the first information or the second information on a resource associated with a CG based on the nature of the content of the first TB and / or the nature of the content of the second TB. For example, if the first information includes control information and has not been transmitted on the first preceding resource, and the second information includes data (e.g., data only) and has been transmitted in the second preceding transmission, the device may determine to transmit the first information of the first TB using a resource associated with a CG. If the first information includes a medium access control (MAC)-control element (CE) and has not been transmitted on the first preceding resource, and the second information includes data (e.g., data only) and has been transmitted in the second preceding transmission, the device may determine to transmit the first information of the first TB using a resource associated with a CG.

[0070] In some examples, the first preceding transmission may be a most recent transmission of the first information, and the second transmission may be a most recent transmission of the second information. The first feedback may include a DFI for the first preceding transmission. The first preceding transmission may be a PUCCH transmission opportunity indicated by a CG or a PUCCH transmission opportunity indicated by another uplink grant. The configuration information may indicate which resources are associated with the PUCCH transmission opportunity. The first preceding resource and the second preceding resource may differ in the time domain and / or the frequency domain.

[0071] The transmission may be sent using resources associated with the CG. For example, the WTRU may send the transmission based on a decision whether to transmit the first information or the second information on resources associated with the CG.

[0072] For example, if a TB contains the same or higher priority (and, for example, the same transport block size (TBS)), the WTRU may take that TB already generated and transmit it on an overlapping DG.

[0073] For example, if a DG contains the same TBS and / or the same or lower priority as a TB generated for transmission on a CG, the WTRU may discard the DG.

[0074] The WTRU may prioritize between the initial transmission and the retransmission(s) as a function of one or more of the following: the priority of the initial transmission compared to the priority of the retransmission; whether the retransmission is due to an uplink (UL) listen-before-talk (LBT); whether the retransmission is due to expiration of a CG retransmission timer (CGRT) (e.g., due to failure to receive a downlink feedback information (DFI) due to a downlink (DL) LBT failure); whether the retransmission is due to receipt of a HARQ acknowledgement (ACK) indication or a negative acknowledgement (NACK) in the DFI; whether the retransmission is due to priority de-prioritization within the WTRU; and / or whether the PDU contains a high priority MAC CE (e.g., a CG acknowledgement medium access control (MAC) control element (CE), a power headroom report (PHR), etc.).

[0075] The WTRU may adjust the reference time distributed by the gNodeB (gNB) depending on, for example, the estimated distance to the target device / node, the subcarrier spacing used, the service type, and / or the propagation delay to the target device and / or node.

[0076] The WTRU may adjust the reference time provided by the source cell (e.g., based on mobility) to meet synchronization at the target cell. The WTRU may use a timing advance (TA) command provided by the target cell to adjust the reference time provided by the source cell.

[0077] Timing compensation may be performed by the network and / or the WTRU.

[0078] The WTRU may enable or disable WTRU-based timing compensation based on, for example, explicit or implicit indication information from the network.

[0079] A wireless (e.g., mobile) communication system / network (e.g., New Radio (NR)) can support ultra-reliable and low latency communications (URLLC) applications and / or internet of things (IoT) applications. The transmission duration within a slot may be flexible. There may be multiple types of configured grants. In one example (e.g., configured grant (CG) type 1 for uplink transmission), the network may configure (e.g., semi-statically configure) the uplink (UL) grant. The WTRU may use (e.g., autonomously use) the UL grant, e.g., without L1 indication / activation. In CG type 2 (e.g., similar to type 1), L1 indication / activation may be considered. Downlink (DL) semi-persistent scheduling (SPS) resources and / or DL ​​CG may be supported. The WTRU may receive DL data on an active DL CG without scheduling for the DL TB (e.g., each DL TB).

[0080] UL and DL services may have different QoS requirements (e.g., traffic with various latency and / or reliability requirements). Communications may be time-sensitive (TSN). Networking may include deterministic or non-deterministic TSN traffic patterns and / or flows, for example, using licensed or unlicensed spectrum.

[0081] The WTRU may be configured with enhanced intra-WTRU overlapping resource prioritization. A configured uplink grant transmission may overlap in time with a dynamically assigned uplink transmission or another configured uplink grant transmission in the same serving cell. The WTRU may prioritize the transmission, for example, based on a comparison between the highest priority of a logical channel having data to be transmitted and that may be multiplexed into a Medium Access Control (MAC) Protocol Data Unit (PDU) associated with the overlapping resource. The configured uplink grant transmission and / or the dynamically assigned uplink transmission may overlap in time with a scheduling request transmission. The WTRU may prioritize the transmission, for example, based on a comparison between the priority of the logical channel that triggered the scheduling request and the highest priority of a logical channel having data to be transmitted (that may be multiplexed into a MAC PDU associated with the overlapping resource). In one example, the WTRU may retain a MAC PDU associated with an already generated deprioritized transmission, for example, to allow a gNodeB (gNB) to schedule a retransmission. The WTRU may be configured by the gNB to transmit the stored MAC PDU as a new transmission using subsequent resources of the same configured uplink grant configuration, for example, if no explicit retransmission grant is provided by the gNB.

[0082] The WTRU may determine that transmissions (e.g., two or more of control data, data, and / or physical layer signals) overlap, e.g., in the time domain and / or frequency domain. The WTRU may, e.g., based on or after determining that the transmissions overlap, determine (e.g., follow a procedure for determining) which of the overlapping transmissions to transmit and / or multiplex together. The WTRU may decide which transmissions to prioritize or demote. The WTRU may drop the demoted priority transmission (e.g., discard the grant and / or store the associated PDU if generated for a later time in the HARQ process (re)transmission) and / or multiplex the demoted priority transmission with other selected transmissions. The WTRU may select which of the overlapping transmissions to transmit based on a determination (e.g., designation) of prioritized and de-prioritized transmissions. A transmission may include one or more of a PUSCH transmission, a physical uplink control channel (PUCCH) transmission, a sounding reference signal (SRS), an uplink control information (UCI), a scheduling request (SR), or other control information transmission and / or signaling. A grant in one or more examples herein may refer to a PUSCH resource applicable for transmission of data and / or control information / elements, e.g., a dynamic grant (DG) or a configured grant (CG). A grant (e.g., a first grant) may be demoted in priority in the MAC, for example, if another grant (e.g., a second grant) has higher priority LCH(s) that overlap with the grant and onto which data may be multiplexed. A grant (e.g., a first grant) may be demoted in priority at the physical layer (PHY), for example, if another grant (e.g., a second grant) or PUCCH transmission overlaps with that grant and has a higher priority.

[0083] The time synchronization accuracy (e.g., in TSN) may depend on the maximum distance between the gNB and the WTRU, for example, if compensation for radio propagation delay between the gNB and the WTRU is not provided (e.g., by the WTRU). The maximum error in timing synchronization may depend on the inter-site / inter-WTRU distance, the subcarrier spacing, and / or whether WTRU propagation delay compensation is applied. The clock synchronization requirement can be achieved by accurate reference timing distribution from the gNB to the WTRU (e.g., performed using broadcast or unicast RRC signaling).

[0084] Wireless communications (e.g., NR RAT and LTE RAT) can use unlicensed spectrum. Channel access in unlicensed frequency bands can use a listen-before-talk (LBT) procedure. LBT can be used regardless of whether the channel is occupied or not. The WTRU can, for example, perform a transmission (e.g., an immediate transmission) after a short switching gap.

[0085] LBT may be characterized (e.g., in a frame-based system) by, for example, one or more of the following: clear channel assessment (CCA) time (e.g., approximately 20 μs), channel occupation time (e.g., minimum 1 ms and / or maximum 10 ms), idle period (e.g., minimum 5% of channel occupation time), fixed frame period (e.g., equal to channel occupation time + idle period), short control signaling transmission time (e.g., maximum duty cycle of 5% within a 50 ms observation period), and / or CAA energy detection threshold.

[0086] The LBT may be characterized, for example, by a number N corresponding to the number of clear idle slots in the extended CCA (e.g., instead of a fixed frame period) (e.g., in the case of a load-based system where the transmit or receive structure cannot be fixed in time). In an example, N may be randomly selected within a range.

[0087] Wireless communication in the unlicensed spectrum may vary depending on the RAT (e.g., NR and LTE). For example, unlicensed spectrum operation in a first RAT (e.g., LTE) may implement multiple categories (e.g., two categories) of CCA for UL and DL communications. In the first category, a node may sense the channel, for example, for a duration of N slots, where N may be a random value selected from a range of allowed values ​​(e.g., referred to as a contention window). The size and / or adjustment of the contention window may depend on the priority of channel access. In a license assisted access (LAA) mode, a WTRU may operate with carrier aggregation (CA) with at least one carrier on the licensed spectrum. A further enhanced LAA (FeLAA) mode may support autonomous uplink transmissions (AUL), e.g., a WTRU may transmit autonomously on pre-configured active UL SPS resources, for which explicit HARQ feedback may be provided, e.g., via downlink feedback information (DFI).

[0088] Unlicensed spectrum operation in a second RAT (e.g., NR unlicensed operation (NR-U)) can support standalone operation, licensed-assisted operation, dual connectivity (DC) operation, CA operation, initial access, scheduling / HARQ, mobility, and / or coexistence procedures (e.g., with LTE-LAA and other RATs). Operational and / or deployment scenarios (e.g., for NR-U) can include, for example, variations of standalone NR operation (e.g., NR-based operation), DC operation (e.g., E-UTRAN NR(EN)-DC with at least one carrier operating according to LTE(RAT) or NR DC with at least two sets of one or more carriers operating according to the NR RAT), and / or CA operation (e.g., including different combinations of zero or more carriers of the LTE RAT and the NR RAT).

[0089] NR-U may support CG transmission and / or block group (CBG)-based transmission for CG. In one example (e.g., in an LTE FeLAA system), the WTRU may not generate a retransmission, e.g., until the AUL timer expires and no HARQ feedback is received, or until it receives a negative acknowledgement (NACK) indication (e.g., in a DFI). In one example (e.g., in an NR-U system), the WTRU may maintain a CG retransmission timer (CGRT) to control retransmissions on an active CG(s), e.g., in addition to the CG timer. The CGRT may start, for example, when a transport block (TB) transmitted on a CG stops (e.g., based on receiving HARQ feedback in a DFI and / or receiving a DG for the same HARQ process). The WTRU may determine a NACK for a TB previously transmitted on the CG (e.g., based on expiration of the CGRT). The WTRU may attempt (e.g., be granted) another (re)transmission, e.g., on an active configured grant with the same HARQ process identifier (PID).

[0090] The operation of the CG can be harmonized between NR-U and URLLC, for example. Uplink enhancements for URLLC and / or IoT (e.g., industrial IoT (IIoT)) (e.g., in unlicensed controlled environments) can include, for example, support for WTRU-initiated COT for frame-based equipment (FBE) and / or harmonization of UL configured grant enhancements in NR-U and URLLC for unlicensed spectrum.

[0091] A WTRU can be configured with multiple CGs on a given bandwidth part (BWP). Multiple CGs (e.g., a subset of CGs) can be active simultaneously. CGs can be configured using both harq-ProcID-Offset and cg-RetransmissionTimer (e.g., for NR-U). CGs can be configured using, for example, harq-ProcID-Offset2 (e.g., only harq-ProcID-Offset2) (e.g., for IIoT), where this offset can distinguish between CGs that overlap in time (e.g., when a WTRU configures and / or enables multiple active CGs in a BWP).

[0092] The WTRU may select a HARQ PID for the first transmission in a CG configured for NR-U. The WTRU may configure a HARQ PID pool for each CG (e.g., multiple CGs in the same BWP are configured), e.g., using the parameter harq-ProcID-Offset. The WTRU may select a HARQ PID according to an equation such as Equation 1 (e.g., for a CG configured for IIoT). HARQ Process ID = [floor(CURRENT_symbol / period)] modulo nrofHARQ-Processes+harq-ProcID-Offset2

[0093] For example, HARQ feedback (e.g., in NR-U) for an UL PDU transmitted on a CG may be based on receiving (e.g., explicit) an ACK / NACK (e.g., in DFI). Feedback (e.g., in IIoT) may be based on, for example, a CG timer expiring without receiving a retransmission grant. The WTRU (e.g., for a transmission on a CG configured for IIoT) may select a redundancy version (RV) according to a configured sequence (e.g., including repetitions). The RV selection (e.g., for a CG configured for NR-U) may be based on the WTRU implementation. The WTRU may include the selected RV and the selected HARQ PID in the CG uplink control information (UCI) for the PUSCH transmission.

[0094] The WTRU (e.g., in the case of NR-U and IIoT) may retransmit (e.g., autonomously retransmit) the PDU in a subsequent CG opportunity and HARQ process (e.g., the same HARQ process) for a CG (e.g., the same CG), for example, if the TB fails the LBT (e.g., in NR-U) or if the TB is demoted due to prioritization within the WTRU (e.g., in IIoT). The WTRU may prioritize retransmissions before the first transmission (e.g., in the case of CGs configured for NR-U).

[0095] The channel state information (CSI) may include, for example, at least one of the following: a channel quality index (CQI), a rank indicator (RI), a precoding matrix index (PMI), an L1 channel measurement (e.g., a reference signal received power (RSRP) such as L1-RSRP or a signal-to-interference-plus-noise ratio (SINR)), a CSI-RS resource indicator (CRI), a synchronization signal (SS) / physical broadcast channel (PBCH) block resource indicator (SSBRI), a layer indicator (LI), and / or measurements (e.g., measurements measured by the WTRU from configured CSI-RS or SS / PBCH blocks).

[0096] The UCI may include, for example, one or more of the following: CSI, HARQ feedback for one or more HARQ processes, SR, link recovery request (LRR), CG-UCI (e.g., CG may indicate a PUCCH transmission), and / or control information bits (e.g., transmitted on the PUCCH or PUSCH).

[0097] The channel conditions may include one or more conditions related to radio / channel conditions, which may be determined by the WTRU from one or more of the following: WTRU measurements (e.g., L1 / SINR / RSRP, CQI / modulation and coding scheme (MCS), channel occupancy, received signal strength indicator (RSSI), power headroom, and / or exposure headroom), L3 / mobility-based measurements (e.g., RSRP and / or reference signal received quality (RSRQ)), RLM status, and / or channel availability in unlicensed spectrum (e.g., whether the channel is considered occupied based on the LBT procedure determination or whether consistent LBT failures have occurred on the channel).

[0098] Characteristics of the scheduling information (e.g., uplink grant or downlink allocation) may include, for example, at least one of: frequency allocation, time allocation aspect (e.g., duration), priority, MCS, TB size, number of spatial layers, number of TBs transmitted, transmission configuration indicator (TCI) state (e.g., configuration information that may indicate that a CG is associated with a PUCCH transmission) or SRS resource indicator (SRI), number of repetitions, and / or whether the grant is a CG type 1, CG type 2, or dynamic grant.

[0099] The DCI indication may include explicit or implicit indication. In an example, the DCI field indication (e.g., explicit indication) or the radio network identifier (RNTI) indication may be used to mask the cyclic redundancy check (CRC) of the PDCCH. The implicit indication may include indication of properties such as the DCI format, DCI size, control resource set (CORESET) or search space, aggregation level, and identity of the first control channel resource for the DCI (e.g., the index of the first control channel element (CCE)). The mapping between the property and the value may be signaled (e.g., by RRC or MAC).

[0100] A WTRU can be configured with multiple CGs on a given BWP. A subset of CGs can be active simultaneously. A CG (e.g., in NR-U) can be used to autonomously (re)transmit a TB after an LBT failure, e.g., to increase the probability of channel acquisition. A CG (e.g., in URLLC and / or IIoT) can be overridden by a higher priority DG. The WTRU can autonomously (re)transmit a PDU with demoted priority, e.g., on a subsequent CG opportunity in the same CG and the same HARQ process. The WTRU can select a HARQ process ID for CG transmission (e.g., in NR-U) from a pool of configured PIDs. The WTRU can select a PID for CG transmission (e.g., in IIoT) according to a time-based formula.

[0101] CG operation can support (e.g., be combined to support) NR-U and / or IIoT operations and / or features, e.g., when CG is not configured in both modes. CG operation in IIoT can be enabled using a CG retransmission timer. The WTRU can select a HARQ PID. The network can know which PID the WTRU selected (e.g., based on indication information). The network can disable CG by dynamic grant (DG). For example, when disabling CG using the same HARQ process, the HARQ buffer may become occupied before the DG is issued.

[0102] The WTRU may, for example, prioritize between data-only retransmissions, retransmissions due to UL LBT failure, retransmissions due to CGRT expiration (e.g., due to failure to receive a DFI due to DL LBT), (re)transmissions due to priority demotion within the WTRU, and / or (re)transmissions of PDUs containing higher priority MAC CEs (e.g., CG Acknowledgment MAC Control Element (CE), Power Headroom Report (PHR), etc.) and initial transmissions (e.g., new transmissions that may contain higher priority data or control data). The WTRU may handle prioritized transmissions on CGs that have failed the LBT (e.g., in the context of prioritization within the WTRU).

[0103] In time-sensitive communication networks (TSN), timing pre-compensation and / or synchronization may be performed. TSN may use (e.g., require strict timing synchronization) timing synchronization between end node devices and, for example, a grandmaster clock to which devices (e.g., all devices) in the TSN are synchronized. As information is transmitted (e.g., through a 5G RAN network), propagation delays may cause drift in the synchronization between the WTRU and the grandmaster clock.

[0104] Synchronization requirements may vary based on the scenario (e.g., industrial environment or smart grid) and / or the location of the grandmaster clock (e.g., in the WTRU or in the AMF). For example, synchronization may use a granularity that cannot be met by means such as timing advance. In examples, timing requirements may be met using, for example, a network-based pre-compensation technique (e.g., additional network-based pre-compensation technique) or a WTRU-based pre-compensation technique.

[0105] In examples, the granularity of the timing advance can meet timing requirements (e.g., without the need for WTRU-based pre-compensation), e.g., depending on the TSN deployment scenario. For example, techniques can be used to enable or disable WTRU timing pre-compensation to avoid double correction of timing advance (e.g., WTRU applying pre-compensation in addition to network-based TA), which would lead to inaccurate timing correction.

[0106] HARQ management may include, for example, HARQ process buffer management and one or more procedures for grant selection and / or prioritization for overlapping grants with the same HARQ PID. The priority of a grant may be determined (e.g., by the WTRU) based on, for example, one or more of the following: a priority index indicated by the DCI, scheduling characteristics, DCI indication information, and / or the highest priority logical channel (LCH) that may be or is already multiplexed for transmission on the grant. A grant may refer to a set of PUSCH resources (e.g., dynamically scheduled by the DCI or semi-statically configured by higher layers).

[0107] The WTRU may be configured to flush the HARQ process buffer of the transport block generated for the first grant, e.g., if the second grant indicates or requests the same HARQ process ID (and, e.g., if the second grant has a higher priority and / or if the two grants overlap in time). In one example, the WTRU may flush (e.g., be configured to flush and / or predefined) the HARQ process buffer of the TB generated for the first grant, e.g., if the start time of the second grant is scheduled within a window of x milliseconds (ms) before the start of the first grant. The value of x may be predefined and / or set by the gNB, e.g., based on the capabilities of the WTRU. In one example, the WTRU may be configured to flush the HARQ process buffer of the TB generated for the first grant, e.g., if the start time of the second grant is scheduled within a window of y ms after the start of transmission of the first grant. The value of y may be pre-defined and / or configured by the gNB, e.g., based on the capabilities of one or more WTRUs. In one example, the WTRU may flush a common HARQ process buffer of a TB generated for a first grant, e.g., if a second grant is for the same HARQ process, a different transport block size (TBS), and / or a different priority (e.g., higher priority). The WTRU may map a PDU previously stored in the flushed HARQ PID buffer to another HARQ process ID, e.g., based on one or more of the following: the PDU was originally generated to be transmitted in a configured grant; the mapped HARQ PID is applicable for autonomous (re)transmissions in the same or a different configured grant; and / or the configured grant can support a PDU (e.g., with the same or larger TBS).

[0108] The WTRU may transmit a PDU already stored in the HARQ PID buffer (e.g., the same PDU) on one of the grants (and, e.g., discard the other), or may transmit the same PDU on both grants (e.g., if the second grant is of the same or lower priority than the first grant). The WTRU may transmit a PDU already stored in the HARQ PID buffer (e.g., the same PDU) on one of the grants (and, e.g., discard the other), or may transmit the same PDU on both grants (e.g., if the second grant is of a higher priority than the first grant). Transmitting an already generated PDU on the second grant may be based, for example, on the ability to transmit a PDU on the second grant subject to configured logical channel prioritization (LCP) and / or LCH mapping restrictions (e.g., if all or fewer LCHs included in the PDU satisfy the LCP and / or LCH selection restrictions associated with the second grant). Transmitting an already generated PDU on the second grant may be based, for example, on whether the TBS of the second grant is greater than or equal to the PDU size and / or TBS of the first grant. The WTRU may, for example, add padding bits to the second grant to fill the TBS, reconstruct the PDU (e.g., without reconstructing the data sub-PDUs), and / or include additional MAC CEs (e.g., if the TBS of the second grant is larger than the PDU size and / or TBS of the first grant). The WTRU may, for example, transmit a PDU already generated for the first grant on both grants if the grants do not overlap in the time domain.

[0109] The WTRU may be configured to prioritize the first grant and discard the second grant (e.g., not transmit the second grant), e.g., if both grants have the same HARQ process ID and / or if a DCI scheduling the second grant is received within z ms before the start time of the first grant. The WTRU may be configured to prioritize the first grant, e.g., even if the first grant has a lower priority than the second grant. In one example, the WTRU may be configured to prioritize the first grant, e.g., if the start time of the second grant is scheduled within an x ​​ms window before the start of the first grant. The value of x may be set by the gNB, e.g., based on the capabilities of the WTRU. The WTRU may be configured to prioritize the first grant, e.g., if the start time of the second grant is scheduled within a y ms window after the start of transmission of the first grant. The value of y may be set (e.g., by the gNB), e.g., based on the capabilities of the WTRU.

[0110] The WTRU may be configured to prioritize the first grant and discard the second grant (e.g., not transmit the second grant), e.g., if both grants have the same HARQ process ID and / or if the priority of the first grant is higher than the priority of the second grant. The WTRU may be configured to prioritize the first grant, e.g., if the start time of the second grant is scheduled within an x ​​ms window before the start of the first grant. The value of x may be set (e.g., by the gNB), e.g., based on the capabilities of the WTRU. The WTRU may be configured to prioritize the first grant, e.g., if the start time of the second grant is scheduled within a y ms window after the start of transmission of the first grant. The value of y may be set (e.g., by the gNB), e.g., based on the capabilities of the WTRU.

[0111] In an example, the first grant may be a UL CG transmission and the second grant may be a UL DG transmission, e.g., as shown in Figures 2 and 3. Figure 2 shows an example where a WTRU receives a DCI scheduling a DG on an HARQ PID before a TB transmission and after the WTRU has constructed a PDU for the HARQ PID, where the start time of the DG is before the start time of the CG and the DG overlaps with the CG in the time domain. Figure 3 shows an example where a WTRU receives a DCI scheduling a DG on an HARQ PID during a TB transmission on a CG and after the WTRU has constructed a PDU for the HARQ PID, where the start time of the DG is after the start time of the CG.

[0112] The WTRU may stop the CG timer associated with the overlapping HARQ process (e.g., in the case of a CG grant transmission). The WTRU may stop the CGRT associated with the HARQ PID where the overlap occurred, e.g., if the priority of the CG transmission is to be demoted. The WTRU may, for example, treat the PDU generated for the flushed TB as a priority-demoted PDU and associate the PDU with the next available CG resource and / or another HARQ PID. For example, the WTRU may be configured to use DG resources (e.g., instead of CG resources) if the data transmitted in the CG is associated with a similar (e.g., the same) or higher priority and / or if the indicated TBS on the DG is the same or larger than the TBS of the CG. For example, in the case of a larger TBS, the WTRU may be configured to use padding bits.

[0113] For example, when the WTRU flushes data associated with a first HARQ process, the WTRU may be configured to map and / or move transport blocks of the first HARQ process to a second HARQ process. For example, the WTRU may prioritize DG transmissions over CG transmissions, and both DG and CG transmissions may have the same HARQ PID with value x. The WTRU may, for example, move, copy, and / or map the TB to another HARQ PID with value y=f(x) before flushing the TB from HARQ PID x. The mapping function f() may, for example, be configured (e.g., provided and / or indicated to the WTRU) in the form of a table. For example, if the WTRU is configured with M HARQ PIDs that may be used for CG transmissions, a pool and / or table with M rows may be configured. For example, if there is one corresponding HARQ PID (e.g., only one corresponding HARQ PID), the configured table may include two columns (e.g., only two columns for a given HARQ PID). For example, if the WTRU has more than one HARQ PID, the configured table may include more than two columns. The function f() may be a function of the CG associated with the original HARQ process. The WTRU may map the PDU to a HARQ PID applicable to the same CG and / or a PID configured for a different CG to support the PDU, e.g., based on the TBS or configured LCP and / or LCH mapping restrictions.

[0114] 2 shows an example where a WTRU receives a DCI scheduling a DG on an HARQ PID before a TB transmission and after the WTRU constructs a PDU for the HARQ PID, where the start time of the DG is before the start time of the CG and the DG overlaps with the CG in the time domain. The WTRU may flush the HARQ process buffer for the TB created for transmission on a different CG opportunity, e.g., if a higher priority DG is signaled for the same HARQ process and overlaps with the CG in the time domain (and, e.g., the CG transmission has not yet started). The WTRU may stop the CG timer associated with the overlapping HARQ process (e.g., when switching the new data indicator (NDI), flushing the HARQ PID buffer, and / or moving the TB to another HARQ process). The WTRU may stop the CGRT associated with the HARQ PID where the overlap occurred, e.g., if the priority of the CG transmission is demoted. The different CG opportunities may belong to different CG configurations.

[0115] The WTRU may map an existing TB to another HARQ PID applicable to CG transmissions. The WTRU may be configured with multiple equivalent HARQ processes to which the WTRU can move a TB. For example, the WTRU may move a TB to another HARQ PID if the PID is applicable to CG transmissions with the same or larger TBS and / or if the HARQ process is applicable to the same CG configuration. The WTRU may treat a PDU already generated for CG as a de-priority PDU and retransmit it in a CG opportunity associated with a different HARQ PID (e.g., a subsequent CG opportunity).

[0116] The WTRU may, for example, take an already generated TB and transmit it in an overlapping DG (e.g., using the same HARQ PID for which the overlap was determined) if the TBs are of the same or higher priority (and, for example, the TBSs are the same). For example, if the TBS of the TB is larger than the TBS of the already generated TB, the WTRU may reconstruct the TB to fit into the DG.

[0117] 3 shows an example in which the WTRU receives a DCI scheduling a DG on the HARQ PID while the WTRU is transmitting a TB on a CG and after constructing a PDU for the HARQ PID, where the start time of the DG is later than the start time of the CG. For example, the WTRU may discard the second grant (e.g., DG) if it has the same TBS and / or if the second grant (e.g., DG) has the same or lower priority as the TB generated for transmission on the first grant (e.g., CG). For example, if transmission on the first grant (e.g., CG) has already started, the WTRU may discard the overlapping second grant (e.g., DG).

[0118] For example, if the priority of the second grant (e.g., DG) is equal to or greater than the priority of the first grant (e.g., CG), the WTRU may abort the transmission (e.g., an ongoing transmission that was already started) on the first grant (e.g., CG) and treat the associated PDU as a priority-degraded PDU. The WTRU may map the priority-degraded PDU onto the overlapping second grant (e.g., DG).

[0119] For example, the WTRU may transmit the same TB in multiple grants (e.g., two grants) if the first and second grants (e.g., DG and CG) do not overlap in time but have the same PID (and, e.g., if the TBS is the same as the TBS of both grants and / or if the TBS of each grant is larger than the size of the PDUs already stored and / or generated in the HARQ PID buffer). For example, the WTRU may discard the lower priority grant if the grants have different priorities and / or if the later grant starts within km ms of the end (or, e.g., start) of the first grant. For example, the WTRU may transmit two different TBs if the WTRU determines (e.g., receives) an ACK for the transmission of the first grant before the start of the second grant and / or receives a switched NDI before the start of the second grant.

[0120] The WTRU may prioritize among the CG (re)transmission types. The WTRU may be configured with a set of parameters to use for transmitting the TB. The set of parameters may be configured (e.g., per HARQ process) and / or determined (e.g., as a function of the data to be transmitted in the TB). The set of parameters may be associated with the CG resource. The set of parameters associated with the TB and / or CG resource may include, for example, at least one of a CGRT, a configured grant timer (CGT), a TB priority index, a TB priority, an MCS, a TBS, etc.

[0121] The CGRT may be a parameter associated with the TB and / or CG resources. For example, the value of the CGRT may depend on the priority of the data in the TB. In one example, the CGRT may depend on the CG resources used for transmission.

[0122] The CGT may be a parameter associated with the TB and / or CG resources. For example, the value of the CGT may depend on the priority of the data in the TB. The CGT may depend on the CG resources used for the n-th transmission (e.g., the first transmission) of the TB.

[0123] The priority index of a TB may be a parameter associated with the TB and / or CG resources. The WTRU may maintain the priority index of the TB. The priority index may be determined from priority indication information (e.g., in the DCI). The priority index may also be determined from at least one LCH multiplexed into the TB.

[0124] The priority of a TB may be a parameter associated with the TB and / or CG resources. The WTRU may determine the priority from a priority index (e.g., indicated by the DCI), from scheduling characteristics, from indication information by the DCI, and / or from the highest priority LCH that can be or is already multiplexed for transmission on the associated grant.

[0125] The MCS and / or TBS may be parameters associated with the TB and / or CG resources. For example, the TB may be associated with the MCS and / or TBS.

[0126] The WTRU may prioritize among conflicting transmissions. The WTRU may transmit (e.g., attempt to transmit) a TB on a CG resource. The WTRU may, for example, receive a scheduling DCI indicating that a DG transmission is expected at the same time as a CG resource (e.g., overlapping in the time domain). The WTRU may transmit a first TB on a first CG resource. The WTRU may, for example, transmit (e.g., attempt to transmit) a second TB on a second CG resource and / or in the same CG resource opportunity while the CGRT is being performed. The WTRU may retransmit multiple TBs (e.g., both TBs) in subsequent CG resources and / or opportunities. The TBs (e.g., each TB) may be a different transmission (e.g., a new transmission) from the previous or current transmission, or may be a retransmission. The next CG resource may be applicable to either TB. The WTRU may multiplex transmissions into one CG resource. The WTRU may include indication information, for example, to describe and / or indicate that multiplexing (e.g., of two CG TBs) has occurred in the CG resource, that the sub-PDUs are of the same size, and / or that the TBS of the CG opportunity can accommodate them. The WTRU may include a sub-header in the combined PDU, for example, to indicate where the first multiplexed TB / sub-PDU ends and the next TB begins, and / or the number of multiplexed TBs / previously generated sub-PDUs. The sub-header may include, for example, the TBS of each sub-PDU.

[0127] The WTRU may transmit a TB (e.g., a single TB) in the CG resource. The selection of the TB to transmit may depend on a prioritization rule (e.g., a prioritization rule in the WTRU may be applied to determine which transmission to select and / or transmit). In an example, it may be unfair to transmit (e.g., always transmit) the highest priority TB (e.g., as determined by the LCH) if, for example, lower priority TBs may experience excessive latency.

[0128] The WTRU may, for example, prioritize multiple pending TBs (e.g., all pending TBs) and / or available grants to determine which TB to transmit (e.g., at a given moment). The one or more prioritization rules may depend on, for example, at least one of the following: a priority index, a priority indicated in the DCI, an LCH priority, whether the transmission is an initial transmission or a retransmission, the RV of the transmission, the reason for the transmission, the number of times the TB was not transmitted, the CAPC used in the LBT process to obtain a channel for transmission, the CGT value, the contents of the TB, whether the TB is part of a repeating bundle, and / or others.

[0129] One or more TB prioritization rules may depend, for example, on a priority index. For example, the WTRU may maintain a priority index for a TB (e.g., each TB). An initial value for the priority index may be determined from the data to be transmitted (e.g., its priority). The initial value of the priority index may be applicable to a new HARQ process. The priority index may be incremented or decremented, for example, as a function of whether the TB was transmitted when originally intended. For example, a TB may have a priority index x. If a TB is not transmitted at its intended time (e.g., on CG resource 1), e.g., due to a collision with a higher priority TB or a failed UL LBT, the WTRU may increment the priority index to x+1. For example, if a (re)transmission is successful, the TB's priority index may be decremented. For example, if the WTRU successfully transmits a TB, the WTRU may decrement the initial priority index x to x-1 (e.g., if a retransmission is requested). In examples, the opposite of the above may be used (e.g., the priority index is decremented when a transmission fails and incremented when a transmission is successful). The WTRU may maintain a priority index for each grant (or for example, configured grants) and / or may use the priority index when selecting a grant (e.g., from among multiple grants during prioritization within the WTRU).

[0130] The one or more TB prioritization rules may depend, for example, on the priority indicated by the DCI. The WTRU may select a TB to transmit based, for example, on the highest or lowest priority indicated by the DCI.

[0131] The one or more TB prioritization rules may depend, for example, on the priority of the LCH. The WTRU may select a TB to transmit based, for example, on the priority of at least one LCH multiplexed onto the TB (e.g., the highest priority LCH). The WTRU may prioritize and rank pending TBs / transmissions in order of the highest priority LCH that is (or, for example, can be) multiplexed onto them.

[0132] One or more TB prioritization rules may depend, for example, on whether the transmission is an initial transmission or a retransmission. The WTRU may prioritize the TB based, for example, on whether a previous transmission of the TB occurred, if a previous transmission of the TB did not occur (e.g., due to a drop or UL LBT failure), or if the transmission is or is intended to be a first attempt to transmit the TB.

[0133] The one or more TB prioritization rules may depend, for example, on the RV of the transmission.

[0134] One or more TB prioritization rules may depend, for example, on the reason for the transmission. The prioritization may depend on whether the transmission is or will be the first attempt of transmission, a retransmission due to a NACK (e.g., a retransmission of information in a TB for which a NACK was received in a DFI may have higher priority than a retransmission of information in a TB without a DFI), a retransmission due to a drop (e.g., due to an intra-WTRU collision), a retransmission due to a drop (e.g., due to an inter-WTRU collision), a retransmission due to an expired CGRT, or a retransmission due to a failed UL LBT. In one example, a TB that has not been transmitted (e.g., never transmitted due to a failed UL LBT) may have higher priority than a new TB (e.g., given that a TB that has not been transmitted resides in the buffer longer). A TB that has not been transmitted may have higher priority than a previously transmitted TB for which a retransmission is predicted due to a NACK (e.g., given that the HARQ process for which the TB was NACKed is at least known to the gNB).

[0135] The one or more TB prioritization rules may depend, for example, on the number of times a TB was not transmitted. The WTRU may maintain a counter for the number of times a TB was dropped (e.g., due to a collision with a higher priority TB transmission) and / or the number of times a TB was not transmitted (e.g., due to an UL LBT failure). The WTRU may use one or more counters to determine the priority associated with a TB. The counter may be reset, for example, if the TB is (re)transmitted at least once. The counter may be reset, for example, if an HARQ process is flushed. The WTRU may maintain multiple counters (e.g., two counters), for example, a first counter for drops due to collisions with higher priority TBs and a second counter for UL LBT failures for the TB.

[0136] The one or more TB prioritization rules may depend, for example, on the CAPC used in the LBT process to acquire a channel for transmission.

[0137] One or more TB prioritization rules may depend, for example, on the CGT value. The priority of a TB may be determined, for example, based on the remaining time of a CG timer associated with the TB, thereby supporting (re)transmission of the TB before the CG timer expires.

[0138] The one or more TB prioritization rules may depend, for example, on the contents of the TB. The prioritization may depend, for example, on whether the TB includes MAC CEs and / or the types of MAC CEs that the TB includes (e.g., CG confirmation MAC CEs, beam failure recovery (BFR) MAC CEs, UL LBT failure MAC CEs, cell RNTI (C-RNTI) MAC CEs, and / or buffer status report (BSR) MAC CEs). The WTRU may be configured with a priority for each MAC CE (or, for example, for each subset of MAC CEs), which the WTRU may use to compare and / or prioritize overlapping transmissions.

[0139] The one or more TB prioritization rules may depend, for example, on whether the TB is part of a repeat bundle. The priority may be determined based, for example, on whether the TB is part of a repeat bundle, the number of repeats in the bundle, and / or the number of successfully or unsuccessfully transmitted repeats in the repeat bundle.

[0140] The WTRU may use a combination of factors (e.g., as described herein) to determine the prioritization of multiple TBs and / or to determine which TBs to transmit and / or drop. The combination may weight different factors (e.g., by applying different weights to different factors). The weighting of the factors may be configurable and / or may be determined, for example, as a function of CG resources and / or the timing of the transmission. One or more prioritization factors (e.g., as described herein) may not be overridden (e.g., never overridden) by one or more other factors. For example, the WTRU may maintain a priority index that may be incremented or decremented, for example, based on whether a TB has been transmitted previously. The priority index value of a first TB may be meaningless, for example, when a second TB with a particular LCH and / or MAC CE is transmitted (e.g., needs to be transmitted). The second TB may have a higher priority than the first TB, for example, regardless of the value of the priority index of the first TB.

[0141] 4 illustrates an example of prioritization used to determine which information of multiple TBs to transmit, e.g., on resources associated with a CG opportunity. The prioritization may include intra-WTRU prioritization among retransmissions and / or initial transmissions (e.g., new transmissions). As shown in 500, a first TB (e.g., TB1) may be constructed, e.g., as described with respect to FIGS. 2 and 3. At 500, one or more PDUs may be constructed to transmit first information in the first TB. The first TB may be associated with a first HARQ PID (e.g., HARQ PID 1).

[0142] The WTRU may transmit the first information of the first TB on resources associated with the CG opportunity using, for example, one or more PDUs constructed in 500. As shown in FIG. 4, the WTRU may transmit the first information of the first TB on resource(s) of the CG1 opportunity 502.

[0143] At 505, a second TB (e.g., TB 2) may be constructed for a second HARQ PID (e.g., HARQ PID 2), e.g., as described with respect to Figures 2 and 3. One or more PDUs may be constructed for transmitting second information for the second TB, at 505. The second TB may be associated with the second HARQ PID (e.g., HARQ PID 2).

[0144] The first information for the first TB may not be received. For example, the WTRU may be in poor coverage (e.g., limited coverage). Due to the poor coverage, the first information for the first TB may not be received. The WTRU may receive feedback for the transmission of the first information. As shown in FIG. 4, the WTRU may determine a NACK for HARQ PID 1 at 510. The WTRU may receive a DFI (e.g., DFI HARQ Feedback (FB)) at 510. The DFI HARQ FB may indicate a NACK for HARQ PID 1. As shown in FIG. 4, the CGRT may be started. For example, if the transmission of the first information for the first TB has stopped, the CGRT may be started. The WTRU may determine a NACK for the transmission of the first information on the resource(s) of the CG1 opportunity 502 based on the expiration of the CGRT. The WTRU may decide to attempt a retransmission of the first information for the first TB.

[0145] The WTRU may attempt to transmit second information for the second TB, for example, on the resource(s) of the CG1 opportunity 504. This attempt may be unsuccessful. As shown in FIG. 4, the WTRU may perform an LBT, and an LBT failure 513 may occur.

[0146] 4, the first TB and the second TB may be pending at 511. The first information may be in a buffer of the WTRU. The second information may be in a buffer of the WTRU.

[0147] At 514, the WTRU may determine, for example, which information (e.g., the first information of the first TB or the second information of the second TB) to transmit on the resource(s) of the next opportunity of CG1. The next opportunity of CG1 may be CG1 opportunity 506. The decision of which information to transmit may be based on receipt of a DFI. As shown in FIG. 4, the WTRU may determine, for example, to transmit the first information of the first TB on the resource(s) of the CG1 opportunity 506, but not the second information of the second TB. The decision that the first information of the first TB should be transmitted may be based on receipt of a DFI at 510 and / or not receiving a DFI associated with the second information of the second TB. The WTRU may not receive a DFI associated with the second information of the second TB due, for example, to a failed LBT associated with an attempt to transmit the second information. In some examples, the WTRU may not receive a DFI for the second information of the second TB due to a busy channel or channel congestion (e.g., the network fails to access the DFI channel even though the network received the second information.) The decision to transmit the first information of the first TB on the resource(s) of the CG1 opportunity 506 may be overridden by the receipt of a DG or other conditions.

[0148] At 515, a DCI may be received. The DCI may indicate (e.g., schedule) a DG 517. The DG may schedule a transmission on a third HARQ PID (e.g., HARQ PID 3). The transmission may include third information for a third TB (e.g., TB3). The third information for the third TB may be transmitted on the resource(s) of the CG1 opportunity 506. The first TB may be demoted in priority. The decision at 514 to transmit the first information for the first TB on the resource(s) of the CG1 opportunity 506 may be overridden, for example, based on intra-WTRU prioritization. The intra-WTRU prioritization may include a higher priority for the DG than a priority for the CG. As shown in FIG. 4, the third information for the third TB may be transmitted at 518. The first TB and the second TB may be on hold at 518.

[0149] At 520, the WTRU may, for example, determine which information (e.g., first information of the first TB or second information of the second TB) to transmit on resources of the next opportunity of CG1. The next opportunity of CG1 may include CG1 opportunity 508. The determination of which information to transmit may be based on why the first information of the first TB was not transmitted in a previous opportunity (e.g., opportunity 506) and / or why the second information of the second TB was not transmitted in a previous opportunity (e.g., opportunity 504). The first information of the first TB was not transmitted on resource(s) of CG1 opportunity 506 due to a priority demotion. The second information of the second TB was not transmitted on resource(s) of CG1 opportunity 504 due to an LBT failure. The WTRU may, for example, prioritize TBs that have been deprioritized due to inter-WTRU or intra-WTRU prioritization over TBs associated with an LBT failure. The WTRU may, for example, decide to transmit the first information of the first TB, rather than the second information of the second TB, on the resource(s) of the CG1 opportunity 508. The first information of the first TB may be transmitted on the resource(s) of the CG1 opportunity 508. At 516, the second TB and / or other TBs may be in a pending state.

[0150] In some examples, an LBT failure may occur when the WTRU attempts to transmit first information of a first TB on resource(s) of the CG1 opportunity 508. If an LBT failure occurs when the WTRU attempts to transmit first information of a first TB on resource(s) of the CG1 opportunity 508, the first and second TBs may be pending at 516. Other TBs may also be pending at 516 due to the LBT failure. For example, a fourth TB (e.g., TB4) may be pending at 516. The fourth TB may be pending if the WTRU constructs a fourth TB for HARQ PID 4. For example, if a DCI enabling a second CG (e.g., CG2) is received, the fourth information of the fourth TB may include a CG confirmation MAC CE. For example, if a DCI enabling CG2 is received, the opportunity 508 may be a CG2 opportunity.

[0151] In FIG. 4 , at 519, the WTRU may receive a DCI enabling the second CG. At 525, the WTRU may, for example, determine which information (e.g., the fourth information of the fourth TB or the second information of the second TB) to transmit in the resource(s) of the next opportunity. The next opportunity may include opportunity 512. Opportunity 512 may be a CG2 opportunity. The decision of which information to transmit may be based on the nature of the content of the second TB and / or the nature of the content of the fourth TB. The WTRU may, for example, determine to transmit the fourth information of the fourth TB in opportunity 512 rather than the second information of the second TB. The fourth TB may include a high-priority MAC CE. The decision to transmit the fourth information of the fourth TB may be based on one or more of the high-priority MAC CE of the fourth TB (e.g., a CG confirmation MAC CE) and / or other conditions. For example, the other condition may be that the fourth information of the fourth TB has not been transmitted. Another condition may be that the second information of the second TB includes data (e.g., only data). Another condition may be that the second information of the second TB was attempted to be transmitted, for example, on the resource(s) of opportunity 504 of CG1. Another condition may be that the second information of the second TB was transmitted using a previous opportunity. At 534, the fourth information of the fourth TB may be transmitted, and the second TB may be in a pending state.

[0152] In some examples, URLLC data may arrive in a buffer associated with the WTRU at 525. If an LBT failure occurs when the WTRU attempts to transmit first information of the first TB on the resource(s) of the opportunity 508 of CG1, some or all of the first TB, the second TB, the fourth TB, or the URLLC data may be pending at 530. The WTRU may determine which information, e.g., the first information of the first TB, the second information of the second TB, the fourth information of the fourth TB, or the URLLC data, to transmit on the resource(s) of the opportunity 512.

[0153] For example, a flag may be set in the WTRU (e.g., for each LCH) indicating that the first transmission of buffered data on the LCH can (e.g., should) be prioritized over pending retransmissions.

[0154] The WTRU may prioritize between (re)transmissions, for example, based on the highest priority data and / or LCH present (or, for example, that can be transmitted) in a transmission (e.g., each transmission). The priority may be determined, for example, based on an L1 priority index and / or from L2 (e.g., based on an LCH priority). The prioritization determination may operate, for example, between the initial transmission and a retransmission, or between different retransmissions.

[0155] The WTRU may determine the priority of a grant (e.g., from among multiple overlapping grants available for transmission) based on channel conditions, e.g., when LCH-based prioritization is configured. In one example, the WTRU may determine whether a grant falls within an ongoing COT, e.g., based on the start and end times of the grant. The WTRU may select a grant (e.g., from among multiple overlapping grants) within the same COT or a shared COT to transmit a pending TB (even if, e.g., the grant overlaps with another grant that may be considered high priority according to legacy intra-WTRU prioritization / selection rules, e.g., even if data associated with a high priority LCH may be multiplexed onto another overlapping grant that is outside the COT). In an example, the WTRU may make a grant selection decision based, e.g., on the probability of success or failure of the LBT associated with the grant (e.g., each grant), and / or may assign grant priority according to the probability of LBT success. For example, the WTRU may prioritize grants based on the number of LBT successes (or, e.g., the number of LBT failures) associated with the grant, e.g., over a configured and / or predetermined observation period. The WTRU may select a grant (e.g., the grant associated with the fewest number of LBT failures) from a set of overlapping grants.

[0156] The WTRU may apply the LCP restriction that applies to the initial transmission when selecting resources for a retransmission based on, for example, one or more of the following: the retransmission is WTRU autonomous, the CGRT is configured, or the TB was originally transmitted on a CG / HARQ process with a CGRT configured. For example, the WTRU may select CG1 to transmit TB1 (e.g., if TB1 multiplexes data from LCH1 and LCH1 is configured with an LCP mapping restriction to only CG1). When retransmitting TB1 autonomously, the WTRU may, for example, select CG1 even if other CGs are available (e.g., either before or during the next CG opportunity associated with CG1). The WTRU may filter out grants from the set of overlapping grants (e.g., when selecting grants according to intra-WTRU prioritization rules) that do not meet the LCP restriction of the retransmitted TB. The WTRU may relax one or more LCP restrictions, for example, if the grants are within the same ongoing COT or a shared COT (e.g., if data can be multiplexed on the grants). For example, the WTRU may select a grant and / or build a TB (e.g., even if it does not meet LCP restrictions) if the grant may be unused and / or if the grant is within the same ongoing COT or a shared COT.

[0157] UL timing and / or latency may be maintained. The WTRU may compensate and / or adjust a reference time distributed by the gNB. Compensation may be applied, for example, as a permanent offset and / or adjustment to the reference time. The WTRU may apply an offset to one or more transmissions (e.g., a subset of transmissions), including, for example, one or more of the following: one or more signals (e.g., all UL signaling), monitoring of DL signaling, traffic type (e.g., URLLC type traffic), grant type (e.g., Type 1 or Type 2 CG), transmissions for initial access (e.g., monitoring transmission or reception of synchronization signal blocks (SSBs), system information block (SIB) messages, and / or random access channel (RACH) messages), data (e.g., of a particular priority level and / or LCH), transmissions (e.g., with a particular or range of subcarrier spacing), one-shot offsets (e.g., for the next packet and / or transmission received on the DL or sent on the UL), and / or others.

[0158] The ability of a WTRU to correct the received reference time may be based on (e.g., depend on) one or more WTRU capabilities. For example, the WTRU may have positioning capability and / or a reference clock or clock drift that meets accuracy criteria. In an example, the ability of a WTRU to apply a WTRU autonomous compensation offset may be, for example, a WTRU capability that can be enabled or disabled by the network (e.g., via RRC signaling and / or MAC CE).

[0159] The reference timing compensation may be applied, for example, based on detection and / or trigger. The WTRU may compensate and / or adjust the reference time delivered by the gNB in ​​a dynamic manner (e.g., based on or in response to one or more events). The WTRU may trigger a compensation action to adjust the reference timing to align with the serving gNB, for example, based on one or more of the following: RSRP / RSRQ fluctuations, receipt of a transmission that is not aligned with the WTRU reference time, propagation delay, arrival of data of a particular LCH and / or priority level, arrival of a particular traffic type and / or service, and / or others.

[0160] The WTRU can trigger a compensatory action to adjust its reference timing to align with the serving gNB, for example, based on variations in RSRP / RSRQ. The WTRU can trigger a compensatory action to adjust its reference timing to align with the serving gNB, for example, based on (e.g., upon detection) that the RSRP / RSRQ resources fall below a threshold, exceed a threshold, or are within one or more ranges of RSRP / RSRQ values. The RSRP / RSRQ value can be associated, for example, with an estimate of the distance from the serving gNB. The RSRP / RSRQ value can be set, for example, by the serving gNB via RRC signaling. The RSRP / RSRQ value can be set independently (e.g., for UL timing and / or latency) or can reference a set value for other purposes (e.g., for measurement mitigation and / or selection of 2-step versus 4-step RACH).

[0161] The WTRU may trigger a compensating action to adjust its reference timing to align with the serving gNB, for example, based on receiving a transmission that is not time-aligned to the WTRU reference time. The WTRU may receive a DL transmission (e.g., an RS, PDCCH, DL data, or DL ​​signaling from the serving gNB that the WTRU can expect at a given time and / or frequency resource). The WTRU may adjust its reference timing proportional to the offset, for example, based on detecting that a DL transmission has arrived at a time that is not synchronized with the expected reference timing.

[0162] The WTRU may trigger a compensation operation to adjust its reference timing to align with the serving gNB, for example, based on a propagation delay. The WTRU may trigger a compensation operation to adjust its reference timing to align with the serving gNB, for example, based on calculating the propagation delay from the WTRU to the gNB and detecting that the propagation delay value is below a threshold, above a threshold, or within one or more ranges of propagation delay values. The propagation delay value may be set by the network, for example, via RRC signaling. The propagation delay may be estimated by the WTRU, for example, from knowledge of the location of the WTRU and / or the gNB (e.g., via global positioning system (GPS) and / or global navigation satellite system (GNSS) technology) or by network positioning techniques.

[0163] The WTRU may trigger a compensatory action to adjust its reference timing to align with the serving gNB, for example, based on the arrival of data of a particular (e.g., configured, indicated, and / or selected) LCH and / or priority level.

[0164] The WTRU may trigger a compensatory action to adjust its reference timing to align with the serving gNB, for example, based on the arrival of a particular (e.g., configured, indicated, and / or selected) traffic type and / or service.

[0165] The WTRU may update (e.g., periodically) the reference timing. The periodicity of the reference timing updates may be based on a timer. The timer and the applicability of the timer value may be configured by the network, e.g., via RRC signaling. The reference timing update may be triggered (e.g., by the WTRU) upon expiration of a timer, for example. The WTRU may reset the timer based, for example, on receipt of one or more of a timing advance MAC CE, an absolute timing advance MAC CE, a timing advance included in Msg3 or MsgB, a reference timing modification by the WTRU (e.g., based on propagation delay estimation and / or compensation), and / or others.

[0166] The periodicity of the reference timing update may be based on a counter. The counter may be based on, for example, a number of frames, slots, and / or symbols, which may be set by the network. The WTRU may trigger an operation related to updating the reference timing based, for example, on reaching a predetermined number of resources. The WTRU may reset the counter based, for example, on receiving one or more of a timing advance MAC CE, an absolute timing advance MAC CE, a timing advance included in Msg3 or MsgB, a correction of the reference timing by the WTRU (e.g., based on propagation delay estimation and / or compensation), and / or others.

[0167] The periodicity of the reference timing updates may depend on, for example, WTRU characteristics and / or data characteristics, which may be configured (e.g., explicitly or implicitly configured). The periodicity at which the WTRU updates the reference timing may be based on (e.g., associated with), for example, one or more of the service type, the WTRU's speed, the grant type, the data and / or LCH priority, and / or others.

[0168] The periodicity with which the WTRU updates the reference timing may be based on, for example, the service type. A WTRU may have different timing expectations (e.g., timing requirements) associated with different data types. For example, a WTRU with URLLC or time-sensitive communication (TSC) traffic may perform reference timing updates more periodically than for eMBB data.

[0169] The periodicity at which the WTRU updates the reference timing may be based on, for example, the velocity of the WTRU. The WTRU may use more frequent reference timing updates, for example, if the WTRU is in a high mobility state. The WTRU may be determined to be in a high mobility state based on, for example, one or more of a mobility state estimation flag, an internal sensor (e.g., an accelerometer), the number of handovers performed within a given time period, detection of one or more consecutive large variations in propagation delay, positioning, RSRP / RSRQ measurements, the type of gNB to which the WTRU is connected (e.g., NTN satellite), and / or others.

[0170] The periodicity with which a WTRU updates its reference timing may be based on the grant type, for example, a WTRU with semi-persistent resources and / or configured grant resources (e.g., Type 1 or Type 2 grant resources) may perform reference timing updates more frequently than a WTRU transmitting data via a dynamic grant.

[0171] The period at which the WTRU updates the reference timing may be based on, for example, the priority of the data and / or the LCH.

[0172] The WTRU can obtain a compensation value to apply to the initial reference time. The WTRU can detect that the reference timing provided by the gNB expects (e.g., requires) an offset, for example, based on one or more of the following: based on the WTRU's estimation of propagation delay, in response to an offset transmission, based on measurements, based on expiration of a timer, or based on reaching a counter value, and / or other. The WTRU can perform one or more actions on the reference time and / or one or more transmissions (e.g., a subset of transmissions), for example, based on the detection that the reference timing provided by the gNB expects (e.g., requires) an offset (e.g., based / conditionally on WTRU capabilities and / or if compensation by the WTRU is enabled by the network). The one or more actions the WTRU can take on the reference time and / or one or more transmissions can include, for example, one or more of applying an estimated timing correction, notifying the gNB of a possible timing drift, transmitting a RACH message to receive a timing advance to align with the clock, and / or other.

[0173] The WTRU may apply an estimated timing correction. The timing correction may be based on a calculation (e.g., an explicit calculation of the propagation delay to the network node and / or the observed offset between the expected time of transmission and the actual time of reception). The WTRU may select from a pre-configured subset of values ​​that may, for example, be linked to a particular measurement. For example, the WTRU may have an association between an RSRP / RSRQ value or a range of values ​​and the timing values ​​to apply.

[0174] The WTRU may notify the gNB of a possible timing drift. The WTRU may notify the gNB (e.g., through explicit signaling), for example, based on detecting that the reference time received from the gNB may require an offset (e.g., an additional offset). The signaling may be, for example, a timing advance command MAC CE, for example, a flag in the UCI or via HARQ feedback. The WTRU may notify (e.g., implicitly notify) the gNB, for example, by applying a timing offset to future UL transmissions. The WTRU may provide an estimate of the needed and / or requested timing offset to the gNB. The WTRU may perform (e.g., be configured to perform) one or more of the following operations: receive and apply a MAC CE (e.g., an absolute timing advance MAC CE or a timing advance MAC CE) and / or monitor the timing advance in Msg2 / MsgB.

[0175] The WTRU may transmit a RACH message to receive a timing advance to align its clock. The WTRU may perform a RACH to receive a timing advance (TA) command in Msg2 or Msg4, for example, based on detecting an offset in the reference time (e.g., to synchronize timing).

[0176] UL timing, latency, and / or mobility may be maintained. The WTRU may adjust the reference time provided by the source cell (e.g., based on mobility) to meet synchronization at the target cell. The WTRU may use a TA command provided by the target cell to adjust the reference time and / or apply propagation delay compensation. The WTRU may apply a timing offset, for example, based on a handover to a cell (e.g., a cell neighboring the cell for which the reference time was provided). The timing offset may be provided, for example, by the previous serving gNB. The timing offset may be calculated (e.g., explicitly calculated) by the WTRU, for example, based on information provided by the network (e.g., the geographical location of the target cell).

[0177] In examples, there may be a master clock provided by an external source, such as the network, another WTRU, or a dedicated function, and various propagation delays may be taken into account. For example, the WTRU may receive master clock information using GPS and / or GNSS information. The WTRU may determine that a reference time is shared among multiple WTRUs and / or gNBs (e.g., all WTRUs and / or gNBs) within a region, such as a RAN notification area (RNA) or tracking region, or within a gNB belonging to a TSN network. The WTRU may synchronize its grandmaster clock (e.g., before mobility and / or initial access) to support proper timing, for example, before cell access.

[0178] The WTRU may set a validity timer (e.g., during which the applied pre-compensation or timing values ​​are determined to be correct). In an example, the WTRU may obtain (e.g., calculate) and / or apply additional timing corrections, e.g., based on expiration of a timer (e.g., a validity timer). The WTRU may report to the network that it has updated the timing values ​​(e.g., including the calculated timing values).

[0179] In an example, expiration of the validity timer may trigger the WTRU to send a notification and / or request to the network to verify that the time correction is valid. The WTRU may include, for example, one or more of the currently applied timing compensation, when the timing compensation was applied, and / or whether the timing compensation is a network-calculated compensation value or a WTRU-calculated compensation value.

[0180] Timing compensation (eg, WTRU-based timing compensation) may be enabled and / or controlled.

[0181] The WTRU may enable or disable (e.g., request to enable or disable) timing pre-compensation. The WTRU may obtain (e.g., calculate) a timing compensation value based on, for example, receiving and / or detecting an enablement indication / command, and may apply (e.g., immediately apply) the compensated and / or corrected value. In examples, a threshold may be provided (e.g., additionally provided) and / or pre-configured to the WTRU; for example, if the timing correction is below the threshold, the WTRU may ignore the timing compensation indication. In examples herein, timing correction and timing compensation may be used synonymously.

[0182] If the WTRU receives a disable command and / or instruction information, the WTRU may, for example, refrain from calculating timing compensation values ​​and / or rely on network corrections, or may maintain WTRU-based timing compensation value calculations and not apply the values ​​unless instructed, for example, by the network (e.g., a one-shot command or re-enabling of WTRU-based compensation).

[0183] Enabling or disabling of WTRU-based timing compensation can be semi-statically configured. For example, the WTRU can enable (or, e.g., disable) WTRU-based timing compensation for a period of time or until it receives an indication to disable (or, e.g., enable) compensation. In an example, the WTRU can be dynamically instructed (e.g., via an indication to disable or enable compensation), for example, via a MAC CE or DCI.

[0184] The enabling or disabling of timing compensation may be indicated (e.g., explicitly indicated) to the WTRU via, for example, system information or SIB (e.g., the WTRU may detect in SIB(s) whether the WTRU is configured and / or expected to apply WTRU-based compensation in the cell), RRC signaling, DCI, and / or MAC CE. The WTRU may be provided with, for example, a timing advance MAC CE that may provide timing pre-compensation. In an example, the WTRU may receive a different MAC CE (e.g., a second MAC CE and / or a new MAC CE) with a finer granularity of timing advance (e.g., specifically for TSN compensation).

[0185] In examples, the following techniques: when timing advance is provided by the gNB (e.g., when the WTRU performs timing compensation (e.g., MAC The WTRU may be implicitly instructed to enable or disable WTRU-based timing compensation using one or more of the following: if it receives a TA command in Msg3 (CE or CE), the WTRU may determine that timing compensation is under network control and / or may disable WTRU-based timing compensation; if a TA command is not received in Msg3 (e.g., the WTRU may enable WTRU-based timing compensation if a TA command is not received); if the RSRP is above (or, for example, below) a threshold (e.g., the WTRU may enable WTRU-based timing compensation if the RSRP is below a pre-configured threshold; in some examples, the WTRU may disable WTRU-based pre-compensation when it detects that the RSRP is above the threshold); a 2-step RACH (e.g., if the WTRU uses 2-step RACH, the WTRU may disable or not apply WTRU-based timing compensation); based on the deployment scenario, based on the WTRU's location and / or distance to the cell center (e.g., the WTRU may disable WTRU-based timing compensation if it detects that it is near the cell center). In some examples, if the WTRU detects that it is a pre-configured distance away from the cell center or TRP, the WTRU may enable a WTRU-based timing compensation technique, etc.

[0186] The WTRU may, for example, based on receiving implicit instruction information to enable / disable WTRU timing compensation, satisfy (e.g., be required to satisfy) one or more further criteria before enabling / disabling WTRU-based pre-compensation (e.g., if the RSRP exceeds a threshold or if a predetermined time has elapsed since the WTRU applied a previous update).

[0187] In an example, if a WTRU detects one or more of the techniques described herein that implicitly indicate enabling or disabling of WTRU-based compensation, the WTRU may trigger a request to the network to confirm that WTRU-based timing compensation has been enabled or disabled. The WTRU may, for example, indicate (e.g., additionally indicate) one or more of the type of implicit indication information detected, the current RSRP, the current timing compensation value, and / or the current timing compensation technique.

[0188] Discrepancies between the WTRU and network calculated pre-compensation may be resolved.

[0189] The WTRU may, for example, periodically calculate a pre-compensation value (e.g., even if the WTRU does not apply the value), regardless of the TSN deployment scenario or if pre-compensation is performed by the network. The WTRU may compare the calculated value with a compensation value provided by the network or with the current timing correction. In an example, if the value (e.g., a delta value) diverges outside a configured threshold, the WTRU may, for example, report that a discrepancy has occurred, one or more of the delta value between the WTRU-calculated value, the WTRU-calculated value, and / or the network-calculated value. The threshold may be set by the network and / or depend on the TSN deployment scenario and / or timing requirements.

[0190] Although the above-described features and elements are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or may be used in various combinations with or without the other features and elements.

[0191] While the implementations described herein may consider 3GPP-specific protocols, it is understood that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, while the solutions described herein consider LTE, LTE-A, New Radio (NR), or 5G-specific protocols, it is understood that the solutions described herein are not limited to this scenario and may also be applicable to other wireless systems.

[0192] The processes described above may be implemented in a computer program, software, and / or firmware embodied 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 computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, 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 compact disc (CD)-ROM disks and / or digital 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

1. A device, 1. A processor, comprising: receiving configuration information indicating a plurality of resources associated with a configured grant (CG); determining a first transport block (TB) and a second TB, the first TB being associated with first information and the second TB being associated with second information; sending a transmission using a first resource of the plurality of resources associated with the CG; a processor configured to: The transmission includes the first information based on fulfillment of a first plurality of conditions, the first plurality of conditions including a condition that first feedback in response to a first prior transmission including the first information has been received by the device and indicates that the first information has not been received, and a condition that second feedback in response to a second prior transmission including the second information has not been received by the device; or The transmission includes the second information based on the fulfillment of a second plurality of conditions, the second plurality of conditions including a condition that the priority of the second TB is demoted to a second resource before the first resource and the second information is not transmitted, and a condition that a listen-before-talk (LBT) failure associated with the first TB occurs on a third resource before the first resource and the first information is not transmitted.

2. 2. The device of claim 1, wherein the processor is further configured to determine whether to send the first information or the second information in the transmission, wherein the first information is determined to be sent in the transmission based on fulfillment of a third plurality of conditions, the third plurality of conditions including a condition that the first information includes control information and is not being transmitted, and a condition that the second information does not include the control information and is being transmitted.

3. 10. The device of claim 1, wherein the processor is further configured to determine whether to send the first information or the second information in the transmission, and wherein the first information is determined to be sent in the transmission based on fulfillment of a fourth plurality of conditions, the fourth plurality of conditions including a condition that the first information includes a medium access control (MAC)-control element (CE) and is not being transmitted, and a condition that the second information does not include control information and is being transmitted.

4. The device of claim 1 , wherein the configuration information indicates a physical uplink control channel (PUCCH) transmission opportunity associated with the CG, and the first resource is associated with the PUCCH transmission opportunity.

5. The device of claim 1 , wherein the first feedback comprises downlink feedback information (DFI) related to the first prior transmission.

6. The device of claim 1 , wherein the first prior transmission is a most recent transmission of the first information and the second prior transmission is a most recent transmission of the second information.

7. The device of claim 1 , wherein the first preceding transmission comprises a physical uplink channel (PUCCH) transmission opportunity associated with the CG or a PUCCH transmission associated with an uplink grant.

8. 10. The device of claim 1, wherein the processor is further configured to determine whether to send the first information or the second information in the transmission, and wherein the transmission is sent based on the determination of whether to send the first information or the second information in the transmission.

9. The device of claim 1 , wherein the device comprises a wireless transmit / receive unit (WTRU).

10. A method performed by a device, comprising: receiving configuration information indicating a plurality of resources associated with a configured grant (CG); determining a first transport block (TB) and a second TB, the first TB being associated with first information and the second TB being associated with second information; sending a transmission using a first resource of the plurality of resources associated with the CG; Including, The transmission includes the first information based on fulfillment of a first plurality of conditions, the first plurality of conditions including a condition that first feedback in response to a first prior transmission including the first information has been received by the device and indicates that the first information has not been received, and a condition that second feedback in response to a second prior transmission including the second information has not been received by the device; or The method, wherein the transmission includes the second information based on the fulfillment of a second plurality of conditions, the second plurality of conditions including a condition that the priority of the second TB is demoted to a second resource before the first resource and the second information is not transmitted, and a condition that a listen-before-talk (LBT) failure associated with the first TB occurs on a third resource before the first resource and the first information is not transmitted.

11. 11. The method of claim 10, further comprising determining whether to send the first information or the second information in the transmission, wherein the determination to send the first information in the transmission is based on fulfillment of a third plurality of conditions, the third plurality of conditions including a condition that the first information includes control information and is not being transmitted, and a condition that the second information does not include the control information and is being transmitted.

12. 11. The method of claim 10, further comprising: determining whether to send the first information or the second information in the transmission; and determining that the first information is sent in the transmission based on fulfillment of a fourth plurality of conditions, the fourth plurality of conditions including a condition that the first information includes a medium access control (MAC)-control element (CE) and is not being transmitted; and a condition that the second information does not include control information and is being transmitted.

13. The method of claim 10 , wherein the configuration information indicates a physical uplink control channel (PUCCH) transmission opportunity associated with the CG, and the first resource is associated with the PUCCH transmission opportunity.

14. The method of claim 10 , wherein the first prior transmission is a most recent transmission of the first information and the second prior transmission is a most recent transmission of the second information.

15. The method of claim 10 , wherein the first preceding transmission comprises a physical uplink channel (PUCCH) transmission opportunity associated with the CG or a PUCCH transmission associated with an uplink grant.

Images