WTRU and implementation method thereof
Enhanced uplink data transmission methods optimize channel access and power allocation in unlicensed bands, addressing inefficiencies in existing systems and improving data throughput and reliability.
Patent Information
- Application Number
- CN202411100655.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2019-08-12
- Filing Date
- 2020-04-30
- Publication Date
- 2024-12-03
AI Technical Summary
Existing wireless communication systems face challenges in efficiently managing uplink data transmission over configured grants, particularly in unlicensed bands, due to limitations in channel access mechanisms like listen-before-talk (LBT), which can lead to inefficiencies and interference.
Implementing enhanced uplink data transmission methods that include mechanisms for channel access in unlicensed bands, such as dynamic adjustment of configured grant timers and power allocation based on downlink feedback, to optimize data transmission efficiency and minimize interference.
Enhances uplink data transmission by improving channel access and reducing interference, thereby increasing data throughput and reliability in wireless communication systems.
Smart Images

Figure CN119070957A_ABST
Abstract
Description
This application is a divisional application of Chinese patent application No. 202080032541.6, whose filing date is April 30, 2020 and entitled “Methods, devices and systems for enhanced uplink data transmission on configured licenses”. The contents of the parent application are incorporated herein by reference. Cross-references
[0001] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 840,499, filed on April 30, 2019, and U.S. Provisional Patent Application No. 62 / 885,565, filed on August 12, 2019, the contents of each of which are incorporated herein by reference. Technical Field
[0002] Embodiments disclosed herein relate generally to wireless communications and, for example, to methods, apparatus, and systems for enhanced uplink (UL) data transmission over configured grants. Related fields
[0003] A listen-before-talk (LBT) mechanism may be used for channel access (CA) in unlicensed bands. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] A more detailed understanding can be obtained from the following detailed description given by way of example in conjunction with the accompanying drawings. The drawings in the description are examples. Therefore, the drawings and detailed description should not be considered limiting, and other equivalent examples are feasible and possible. In addition, the same reference numerals in the figures indicate the same elements, and among them: Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented; Figure 1B is a diagram showing that according to an embodiment, Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) used within a communication system is shown; Figure 1C is a diagram showing that according to an embodiment, Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used within the communication system shown; Figure 1D is a diagram showing that according to an embodiment, Figure 1A A system diagram of another exemplary RAN and another exemplary CN used within the communication system shown; Figure 2 is a schematic diagram showing an example of a grant (CG) retransmission timer configured when switching between CGs; Figure 3is a schematic diagram showing an example of updating a CG timer based on downlink feedback information (DFI) reception and CG selection; Figure 4 is a flow chart illustrating a representative process for transmission of a transport block; Figure 5 is a flow chart illustrating another representative process for transmission of a PDU; Figure 6 is a flow chart illustrating a further representative process for transmission of a transport block; Figure 7 is a flow chart showing a representative process for COT sharing; Figure 8 is a flow chart illustrating an additional representative process for transmission of a transport block; Fig. 9 is a flow chart of a representative transmission process using allocated / reallocated UL power; Fig.10 is a flow chart illustrating yet another representative process for transmission of a transport block; Fig.11 is a flow chart illustrating a representative transmission process using the calculated transmit power allocation; Fig.12 is a flow chart illustrating a representative process for changing a redundancy version; Fig.13 is a flow chart showing a representative process for modifying CG timing; Fig.14 is a flow chart showing a representative process for CG configuration, CG timing and / or CG resource selection; and Fig.15 is a flowchart showing a representative process of CG transmission. DETAILED DESCRIPTION Example network for implementation of the described embodiments
[0005] Figure 1A1 is a schematic diagram of an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, the communication system 100 may use 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, and filter bank multi-carrier (FBMC), etc.
[0006] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network components. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, any of the WTRUs 102a, 102b, 102c, 102d may be referred to as a “station” and / or “STA”, which may be configured to transmit and / or receive wireless signals, and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices working in an industrial and / or automated process chain environment), consumer electronic devices, and devices working on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.
[0007] The communication 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 facilitate access to one or more communication networks (e.g., CN 106 / 115, Internet 110, and / or other networks 112) by wirelessly interfacing with at least one of the WTRUs 102a, 102b, 102c, 102d. For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B (eNB), a Home Node B (HNB), a Home eNode B (HeNB), a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, and the like. Although each of the base stations 114a, 114b is depicted as a single component, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network components.
[0008] The base station 114a may be part of the RAN 104 / 113, and the RAN may also include other base stations and / or network components (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, and the like. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies called cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a specific geographic area that is relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a 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., each transceiver corresponds to a sector of the cell. In an embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology, and may use multiple transceivers for each sector of the cell. For example, by using beamforming, signals may be transmitted and / or received in a desired spatial direction.
[0009] 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, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).
[0010] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, among others. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed UL Packet Access (HSUPA).
[0011] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).
[0012] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology that may use new radio (NR) to establish the air interface 116, such as NR radio access.
[0013] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access (e.g., using dual connectivity (DC) principles). Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).
[0014] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000EV-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), and GSM EDGE (GERAN), among others.
[0015] Figure 1A The base station 114b in the example may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may use any appropriate RAT to facilitate wireless connectivity in a local area, such as a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In an embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, and the like). As Figure 1A As shown, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114b does not need to access the Internet 110 via the CN 106 / 115.
[0016] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or may perform advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113 employing NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0017] The CN 106 / 115 may also act 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 circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer network devices that use common communication protocols, such as TCP, User Datagram Protocol (UDP), and / or IP in the Transmission Control Protocol / Internet Protocol (TCP / IP) Internet protocol suite. The networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, where the one or more RANs may use the same RAT or a different RAT as the RAN 104 / 113.
[0018] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
[0019] Figure 1B is a system diagram illustrating an exemplary WTRU 102. Figure 1B As shown, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a numeric keypad 126, a display / touchpad 128, a non-removable memory 130, a removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or peripherals 138. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0020] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors 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, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, however it should be appreciated that the processor 118 and the transceiver 120 may also be integrated together in an electronic package or chip.
[0021] The transmit / receive component 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive component 122 may be an antenna configured to transmit and / or receive RF signals. As an example, in another embodiment, the transmit / receive component 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, the transmit / receive component 122 may be configured to transmit and / or receive RF and light signals. It should be appreciated that the transmit / receive component 122 may be configured to transmit and / or receive any combination of wireless signals.
[0022] Although in Figure 1B 102 as a single component, the WTRU 102 may include any number of transmit / receive components 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive components 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0023] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive component 122 and to demodulate signals received by the transmit / receive component 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers that allow the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.
[0024] The processor 118 of the WTRU 102 may be coupled to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data from these components. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store information in any suitable memory such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in memories that are not physically located in the WTRU 102, such as, for example, a server or a home computer (not shown).
[0025] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power for use by other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
[0026] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be appreciated that the WTRU 102 may acquire location information via any suitable positioning method while remaining consistent with an embodiment.
[0027] The processor 118 may also be coupled to other peripheral devices 138, wherein the peripheral devices may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, the peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Modules, frequency modulation (FM) radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. The peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geographic location sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors, etc.
[0028] The processor 118 of the WTRU 102 may be operable to communicate with various peripheral devices 138, including, for example, any of: the one or more accelerometers, the one or more gyroscopes, the USB port, other communication interfaces / ports, the display and / or other visual / audio indicators, to implement representative embodiments disclosed herein.
[0029] The WTRU 102 may include a full-duplex radio in which reception or transmission of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous for the radio. The full-duplex radio may include an interference management unit 139 that reduces and / or substantially eliminates self-interference by means of hardware (e.g., chokes) or by signal processing by a processor (e.g., a separate processor (not shown) or by the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio that transmits and receives some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or DL (e.g., for reception)).
[0030] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c using an E-UTRA radio technology over the air interface 116. The RAN 104 may also communicate with the CN 106.
[0031] The RAN 104 may include eNode-Bs 160a, 160b, 160c, however it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.
[0032] 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 in the UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0033] Figure 1C The illustrated CN 106 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 aforementioned components is described as being part of the CN 106, it should be appreciated that any of these components may be owned and / or operated by an entity other than the CN operator.
[0034] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, performing bearer activation / deactivation processing, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.
[0035] 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 / from the WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane during an inter-eNB handover, triggering paging processing when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.
[0036] The SGW 164 may be connected to the PGW 146, 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.
[0037] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or communicate with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, and the IP gateway may serve as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.
[0038] Although in Figures 1A-1D Although the WTRU is described as a wireless terminal, it should be appreciated that in certain representative embodiments, such a terminal may use a (eg, temporary or permanent) wired communication interface with a communication network.
[0039] In a representative embodiment, the other network 112 may be a WLAN.
[0040] A WLAN using an infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may access or be connected to a distributed system (DS) or other types of wired / wireless networks that send traffic into and / or out of the BSS. Traffic originating from outside the BSS and destined for the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Traffic between STAs within the BSS may be sent through the AP, for example, when the source STA may send traffic to the AP and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. The point-to-point traffic may be sent using a direct link establishment (DLS) between the source and destination STAs (e.g., directly therebetween). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z channelized DLS (TDLS)). For example, a WLAN using an independent BSS (IBSS) mode does not have an AP, and STAs (eg, all STAs) within or using the IBSS can communicate directly with each other. Here, the IBSS communication mode may sometimes be referred to as an "ad-hoc" communication mode.
[0041] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit a beacon on a fixed channel (e.g., a primary channel). The primary channel may have a fixed width (e.g., a bandwidth of 20 MHz) or a width that is dynamically set via signaling. The primary channel may be a working channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access (CSMA / CA) with collision avoidance (e.g., in an 802.11 system) may be implemented. For CSMA / CA, STAs (e.g., each STA) including the AP may sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA may back off. In a specified BSS, there is one STA (e.g., only one station) transmitting at any given time.
[0042] A high throughput (HT) STA may communicate using a 40 MHz wide channel (eg, by combining a 20 MHz wide primary channel with a 20 MHz wide adjacent or non-adjacent channel to form a 40 MHz wide channel).
[0043] Very high throughput (VHT) STA can support channels with widths of 20MHz, 40MHz, 80MHz and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels or by combining two discontinuous 80MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data can be transmitted and passed through a segment parser, which can separate the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed separately on each stream. The stream can be mapped on two 80MHz channels, and the data can be transmitted by the STA performing the transmission. At the receiver of the STA performing the reception, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).
[0044] 802.11af and 802.11ah support working modes below 1 GHz. Compared with 802.11n and 802.11ac, the channel working bandwidth and carrier used in 802.11af and 802.11ah are reduced. 802.11af supports 5MHz, 10MHz and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter type control / machine type communication (MTC) (e.g., MTC devices in macro coverage areas). MTC devices can have certain capabilities, such as limited capabilities including support (e.g., only support) certain and / or limited bandwidths. MTC devices can include a battery, and the battery life of the battery is higher than a threshold (e.g., for maintaining a very long battery life).
[0045] For WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah), these systems include channels that can be designated as primary channels. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by a certain STA, where the STA originates from all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the width of the primary channel can be 1MHz. Carrier sensing and / or network allocation vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy (e.g., because a STA (which only supports the 1MHz operating mode) transmits to the AP), then even if most of the available frequency bands remain idle and available for use, the entire available frequency band can be considered busy.
[0046] In the United States, the available frequency band for 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. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.
[0047] Figure 1D 1 is a system diagram showing the RAN 113 and the CN 115 according to an embodiment. As described above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c using NR radio technology over the air interface 116. The RAN 113 may also communicate with the CN 115.
[0048] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may use beamforming processing to transmit and / or receive signals to and / or from the gNBs 180a, 180b, 180c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to the WTRU 102a and receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).
[0049] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable digital configuration. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the radio 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., containing different numbers of OFDM symbols and / or lasting different absolute time lengths).
[0050] 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 other RANs (e.g., the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect to the gNB 180a, 180b, 180c while communicating / connecting to another RAN (e.g., the eNode-B 160a, 160b, 160c). For example, the WTRU 102a, 102b, 102c may communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c in a substantially simultaneous manner by implementing the DC principle. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRU 102a, 102b, 102c.
[0051] 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, user scheduling in UL and / or DL, support network slicing, dual connectivity, implement interworking between NR and E-UTRA, route user plane data to a user plane function (UPF) 184a, 184b, and route control plane information to an access and mobility management function (AMF) 182a, 182b, and the like. Figure 1D As shown, gNBs 180a, 180b, and 180c can communicate with each other through the Xn interface.
[0052] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include a data network (DN) 185a, 185b. Although each of the aforementioned components is described as part of the CN 115, it should be understood that any of these components may be owned and / or operated by an entity other than the CN operator.
[0053] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act 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 protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, and mobility management, etc. The AMF 182a, 182b may use network slicing processing to customize the CN support provided to the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102c. As an 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, and / or services for machine type communication (MTC) access, etc. The AMF 182 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) using other radio technologies (e.g., LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi).
[0054] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and may configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating WTRU or UE IP addresses (e.g., WTRU IP addresses), managing PDU sessions, controlling policy enforcement and QoS, and providing DL data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0055] The UPF 184a, 184b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which can provide the WTRUs 102a, 102b, 102c with access to packet-switched networks (e.g., the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b can perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-host PDU sessions, processing user plane QoS, buffering DL packets, and providing mobility anchor processing, etc.
[0056] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to 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 the local data network (DN) 185a, 185b via an N3 interface connected to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b and through the UPF 184a, 184b.
[0057] In view of Figures 1A-1D and about Figures 1A-1D In accordance with the corresponding description of the present invention, one or more or all functions described herein in comparison with one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-d, base station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN185ab and / or one or more other devices described herein. These simulation devices may be one or more devices configured to simulate one or more or all functions described herein. For example, these simulation devices may be used to test other devices and / or simulate network and / or WTRU functions.
[0058] The simulation device can be designed to implement one or more tests about other devices in a laboratory environment and / or an operator network environment. For example, the one or more simulation devices can perform one or more or all functions while being implemented and / or deployed as a part of a wired and / or wireless communication network in whole or in part to test other devices inside the communication network. The one or more simulation devices can perform one or more or all functions while being temporarily implemented or deployed as a part of a wired and / or wireless communication network. The simulation device can be directly coupled to other devices to perform the test, and / or can use over-the-air wireless communication to perform the test.
[0059] One or more simulation devices can perform one or more functions, including all functions, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test lab and / or a test scenario of a wired and / or wireless communication network that is not deployed (e.g., testing) to implement tests on one or more components. The one or more simulation devices can be test devices. The simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication with the aid of RF circuits (e.g., which can include one or more antennas).
[0060] In some cases, LBT may be enforced independently of whether the channel is occupied (eg, generally enforced). In other cases, immediate transmission may be applied after a short switching gap.
[0061] In some representative embodiments, a channel may be a continuous portion of a frequency band, while in other representative embodiments, a channel may be multiple non-contiguous portions of one or more frequency bands. In the context of unlicensed frequency bands, a channel may be a spectrum resource that is available for communication as determined by an LBT mechanism / operation.
[0062] For frame-based systems, LBT can be characterized by a clear channel assessment (CCA) time (e.g., in the range of ~20 μs), a channel occupation time (COT) (e.g., minimum 1 ms, maximum 10 ms), an idle period (e.g., minimum 5% of the COT), a fixed frame period (e.g., equal to the COT + idle period), a short control signaling transmission time (e.g., a maximum duty cycle of 5% within an observation period of 50 ms), and / or a CAA energy detection threshold.
[0063] For load-based systems (e.g., the transmit / receive structure may not be fixed in time), LBT may be characterized, for example, by the number N of idle slots corresponding to the extended CCA, rather than by a fixed frame period. N may be selected within a range (e.g., randomly selected).
[0064] For unlicensed spectrum, there may be multiple categories (e.g., two categories) of CCA for UL and / or DL. In the first category, a node may sense a channel for a duration of N time slots, where N is a value (e.g., a random value) selected from a range of allowed values (sometimes referred to hereinafter as a contention window CW). The size of the CW and / or adjustments to the CW may depend on a channel access priority (CAP). In licensed assisted access (LAA) mode, the WTRU 102 may operate on licensed spectrum using at least one carrier using CA. In enhanced licensed assisted access (FeLAA) mode, the WTRU 102 may autonomously transmit using autonomous UL (AUL) transmissions on pre-configured active UL semi-persistent scheduling (SPS) resources, for which hybrid automatic repeat request (HARQ) feedback (e.g., explicit HARQ feedback) may be provided via DFI.
[0065] A New Radio (NR) system may support flexible transmission duration within a timeslot and / or "configured grant" type 1 for UL transmissions. For example, the network (e.g., a network entity) may semi-statically configure the UL grant, and the WTRU 102 may autonomously use the configured UL grant without a layer 1 (L1) (e.g., physical layer) indication and / or activation. Configured grant type 2 may be similar to configured grant type 1 and may take into account the L1 indication / activation. The NR system may support DL SPS resources (and / or DL configured grants) on which the WTRU 102 may receive DL data on an active DL CG without using scheduling for each DL transport block (TB) and / or without scheduling.
[0066] The NR system may support UL and DL services with different QoS requirements, including services with different latency and / or reliability requirements, in a single WTRU 102. NR may support time-sensitive communications and / or networking, including deterministic and / or non-deterministic time-sensitive networking (TSN) traffic patterns and / or flows, which may be used, for example, in a factory automation setting (e.g., ubiquitous use) using licensed and / or unlicensed spectrum.
[0067] NR-based operations using unlicensed spectrum may include initial access operations, scheduling / HARQ and / or mobility operations, and coexistence operations with LTE-LAA and other incumbent radio access technologies (RATs). Deployment scenarios may include standalone NR-based operations, dual connectivity operations (e.g., E-UTRA NR dual connectivity (EN-DC) with at least one group of one or more carriers operating in accordance with the LTE RAT, or NR DC with at least two groups of one or more carriers operating in accordance with the NR RAT), and / or different variants of carrier aggregation (e.g., including different combinations of zero or more carriers of each of LTE and / or NR RAT). NR-U may support multiple CG transmissions and code block group (CGB)-based transmissions for the CG.
[0068] The term "LBT configuration" and / or the term "LBT parameters" may be generally used to include at least one or more of the following: CAP category (CAPC), LBT type, congestion window size, CCA, and / or other parameters used to determine whether the WTRU 102 is able to acquire a channel or transmit UL signals on the channel. The term "highest priority CAPC" is generally synonymous with the lowest CAPC number and / or the lowest CAPC. The term "UL LBT failure" generally means that the WTRU 102 cannot acquire a channel for an UL transmission attempt after the CCA portion of the LBT process, which may be determined, for example, based on receiving a "notification of LBT failure" or "indication of LBT failure" from the physical layer and other determination operations. When the term "UL LBT success" is used, the opposite may apply. For example. The term "UL LBT success" generally means that the WTRU 102 is able to acquire a channel for an UL transmission attempt, for example, after the CCA portion of the LBT process.
[0069] The terms "AUL timer", "CG retransmission timer" and "AUL retransmission timer" may be used interchangeably. The terms "LBT subband" and "LBT bandwidth" may be used interchangeably.
[0070] In a further enhanced Grant Assisted Access (FeLAA) system, the WTRU 102 may not generate a retransmission until the AUL timer expires and no HARQ feedback is received, or until a negative ACK (NACK) is received in the DFI. For NR-Ungranted (NR-U) systems, in addition to or as an alternative to legacy timers (e.g., NR-R15 CG timers), the WTRU 102 may maintain the AUL timer or retransmission timer to control retransmissions on (one or more) active CGs. The AUL timer may be started when a TB is sent on the CG, and may be stopped when HARQ feedback is received in the downlink feedback information (DFI) and / or when a dynamic grant (DG) for the same HARQ process is received. When the AUL timer expires, the WTRU 102 may determine (e.g., may assume) that there is a NACK for a TB previously transmitted on the CG, and the WTRU 102 may be allowed to attempt another transmission or retransmission on an active configured grant with the same HARQ process ID (HARQ PID).
[0071] In certain representative embodiments, upon receiving a HARQ ACK for the applicable HARQ process ID (PID) in the downlink feedback information (DFI), the WTRU 102 may stop the CG timer and may toggle a new data indicator (NDI).
[0072] In certain representative embodiments, the WTRU 102 may update the CG timer value for the applicable HARQ PID based on the periodicity of the CG occasions selected for retransmission.
[0073] In certain representative embodiments, the WTRU 102 may back off for a period of time before selecting the first available CG opportunity, depending on the selected CG and / or instructions received from the gNB 180.
[0074] In certain representative embodiments, the WTRU 102 may increment the RV only after a successful transmission or retransmission of the LBT on the CG.
[0075] In certain representative embodiments, the WTRU 102 may select or reselect different CG resources on different subbands for retransmission or for retry of transmission after several LBT failures.
[0076] In certain representative embodiments, the WTRU 102 may calculate several transmit power allocations (TPAs) and may apply one TPA on different uplinks and / or uplink subband(s) where LBT or CCA was successful based on the LBT results.
[0077] In certain representative embodiments, the WTRU 102 may determine that an upcoming CG opportunity is conditionally added or shifted upon receiving an indication from the gNB 180.
[0078] In certain representative embodiments, the WTRU 102 may conditionally consider a subset of CG opportunities, CG configurations, and / or CG resources as applicable based on LBT results, jitter delay to the next CG opportunity or opportunities, and / or reception of a DL signal or lack of such reception of a DL signal (e.g., based on expiration of a timer). Jitter delay is, for example, a time delay between the arrival of data (e.g., at a data buffer) and the next transmission opportunity.
[0079] In certain representative embodiments, methods, apparatus, and systems may be implemented to include CG-UCI in CG transmissions. For example, such embodiments may include determining a resource in which to map the CG-UCI and / or including multiplexing the CG-UCI, UCI, and data in one or more CG resources.
[0080] In NR-U, the WTRU 102 may be configured with multiple CGs on a given bandwidth part (BWP), a subset or all of which may be active at the same time. Depending on the LBT results, a subset of the active CGs may be used at a given time.
[0081] In certain representative embodiments, methods, apparatus, systems, and / or processes for generating transmissions or retransmissions on a CG in the context of NR-U may be implemented, for example, to provide predictable WTRU behavior. The methods, apparatus, systems, and / or processes may, for example, take into account the impact of and / or may impact the following: (1) transmission timing and LBT on resource selection, 2) redundancy version (RV) selection, (3) CAPC selection, (4) HARQ PID selection, (5) power allocation, and / or (5) one or more retransmission timers, etc. Representative process for retransmission on CG Typical conditions that cause retransmission on CG
[0082] The WTRU 102 may maintain a CG timer (e.g., a legacy NR-R15 CG timer) for each active HARQ PID (e.g., for AUL). The CG timer may be maintained in addition to or as an alternative to the AUL timer. Upon receiving a DG with a HARQ PID for a pending CG retransmission, the WTRU 102 may restart one or more CG timers and may stop the AUL timer. In FeLAA, the AUL timer may be configured per subframe (in units of ms), while the CG timer (e.g., in NR-R15) may be configured in units of the number of CG cycles. For NR-U systems, the AUL timer may expire while the CG timer is still running, or vice versa (e.g., depending on the periodicity of the selected CG), which may lead to undesirable results if the CG timer is not properly maintained when the AUL timer expires.
[0083] Figure 2 This is a diagram showing the switching of the CG retransmission timer between CGs. Figure 2 , the RRC configuration may include an AUL timer set to a first period (e.g., 1 ms), a first CG timer set to 1 period (e.g., one period), for example, for CG1, and a second CG timer set to 6 periods (e.g., six periods), for example, for CG2. In one example, the WTRU 102 may send an initial transmission on CG1 and may start the AUL timer and the CG timer. The next CG opportunity may occur after the CG timer expires. The WTRU 102 may select CG2 for retransmission and may update the CG timer to a different number of elapsed periods (e.g., 2 elapsed periods). The WTRU 102 may successfully send a retransmission at the next CG opportunity. The WTRU 102 may receive an acknowledgment (ACK) via or on the DFI. In this example, the CG timer may continue to run and the WTRU 102 may not use subsequent CG opportunities for new transmissions.
[0084] For example, when the AUL timer expires and the WTRU 102 selects a CG opportunity with a different period than the period selected for the previous transmission or retransmission, if the CG timer is not correctly updated according to the selected CG, the WTRU 102 may toggle (e.g., inadvertently toggle) the new data indicator (NDI) for the HARQ PID for which the TB is pending and may flush the buffer. On the other hand, if the WTRU 102 keeps the CG timer running, even if a retransmission with a shorter period succeeds on the CG (e.g., an ACK is received on the DFI), the WTRU 102 may not be able to use the upcoming CG opportunity for a new transmission until the CG timer expires.
[0085] In certain representative embodiments, after the AUL timer of the HARQ process used to transmit the initial TB expires, the WTRU 102 may retransmit at any active CG opportunity.
[0086] Figure 3 is a schematic diagram showing a representative process for updating the CG timer based on DFI reception and / or CG selection.
[0087] refer to Figure 3 , the RRC configuration may include an AUL timer set to a first period (e.g., 1 ms), a first CG timer set to 1 period (e.g., one period), for example, for CG1, and a second CG timer set to 6 periods (e.g., six periods), for example, for CG2. In one example, the WTRU 102 may send an initial transmission on CG1 and may start the AUL timer and the CG timer. The next CG opportunity may occur after the CG timer expires. The WTRU 102 may select CG2 for retransmission and may update the CG timer to a different number of elapsed periods (e.g., 2 elapsed periods). For example, the WTRU 102 may successfully send a retransmission at the next CG opportunity. The WTRU 102 may receive an acknowledgment (ACK) via or on the DFI. In this example, during the period between the ACK and the subsequent CG opportunity, the WTRU 102 may stop the CG timer and may switch the new data indicator (NDI) for the HARQ PID. The WTRU 102 may use the subsequent CG opportunity for a new transmission.
[0088] In certain representative embodiments, the WTRU 102 may perform at least one of the following operations (e.g., operations / processes, methods, and / or principles) for transmission or retransmission on the CG (e.g., to ensure efficiency of the configured CG resources): (1) Upon receiving a HARQ acknowledgement (ACK) for a TB in a DFI, the WTRU 102 may stop the CG timer for an applicable HARQ PID; (2) the WTRU 102 may switch the NDI for the applicable HARQ PID upon receiving the HARQ ACK for the TB in the DFI, or may switch the NDI at or before the next CG opportunity that occurs after receiving the ACK for the TB on the applicable HARQ PID; (3) When selecting a HARQ PID for an initial transmission on the CG from the HARQ PID pool configured for AUL / CG transmissions, the WTRU 102 may exclude (one or more) HARQ PIDs that meet the following conditions: (i) on which a dynamic license is received, and / or (ii) Transmission of another TB is pending (eg, because the NDI may not have been toggled, the HARQ ACK feedback for the HARQ PID may not have been received, and / or the HARQ buffer of the identified process may not be empty).
[0089] If the AUL timer has expired and the CG timer is running, and the WTRU 102 selects a CG opportunity for a retransmission on an active CG that is different from the active CG used by one or more previous transmissions or retransmissions, the WTRU 102 may perform at least one of the following operations: (1) After the transmission or retransmission of the CG opportunity of the LBT success, the AUL timer is restarted; (2) performing an update of the CG timer value for the applicable HARQ PID according to the period of the selected CG (e.g., Figure 3 As shown, if the WTRU 102 switches to CG2 to perform retransmission when the AUL timer expires, the WTRU 102 can update the CG timer to 2 cycles); (3) not performing switching of the NDI until an ACK for the HARQ PID is received in the DFI (e.g., if the CG timer expires or has expired when the value of the CG timer is updated according to the period of the newly selected CG and / or an ACK for the pending TB has not been received); and / or (4) Performing a conversion of the value configured for the CG timer based on the CG on which the PDU is transmitted or retransmitted (e.g., the WTRU 102 may scale the configuration value configured for the CG timer by one or more factors, such as the period of the selected CG and / or the period of the CG for which the timer is started). Representative process for handling conflicts between or among CGs and DGs
[0090] In NR-U, the WTRU 102 may select (e.g., autonomously select) a HARQ PID from a pool of PIDs configured for CG transmissions. The WTRU 102 may select a PID for which the AUL timer is stopped or not running for the purpose of retransmission or new transmission on the CG, although the network may simultaneously issue a DG with the same HARQ PID. Downlink control information (DCI) for scheduling the DG may be received at the following times: (1) before the AUL transmission; (2) after the WTRU 102 selects a HARQ PID for the CG; and / or (3) after (e.g., shortly after) the transmission begins on the CG. Representative processes for the WTRU 102 to handle such conflicts may be defined and may be implemented as disclosed herein.
[0091] For example, WTRU 102 may determine a HARQ PID conflict based on any of the following: (1) WTRU 102 selects a HARQ PID for a PDU for transmission or retransmission on a CG and receives a DG with the same HARQ PID; (2) WTRU 102 receives a DG that overlaps with the CG in the time domain and / or frequency domain from a resource perspective; and / or (3) WTRU 102 receives a DG with a HARQ PID configured for AUL / CG transmission.
[0092] If the WTRU 102 determines that the HARQ PIDs collide and the NDI of the DG is switched, the WTRU 102 may ignore the switching of the NDI and may keep the PDU in the HARQ buffer for the identified HARQ PID. The WTRU 102 may further consider and / or may determine whether the transport block size (TBS) of the DG and / or the transport blocks overlap in time and / or frequency compared to the TBS of the CG. For example, if TBS(DG)>=TBS(CG) and / or the two grants overlap, the WTRU 102 may ignore the switching of the NDI.
[0093] When the WTRU 102 receives a DG with a HARQ PID configured for a CG transmission with an AUL timer running, and another CG opportunity for which the same HARQ PID is applicable occurs before the start of the physical uplink shared channel (PUSCH) for the DG, the WTRU 102 may prioritize the DG over the CG for retransmission (e.g., if the NDI is not toggled, e.g., as part of the HARQ information provided for the DG). Representative procedure for backing off before retransmission on a CG
[0094] When the channel is busy for an extended duration, assuming that a large number of WTRUs 102 may transmit (e.g., may need to transmit) pending data at the same time, there may be a higher probability of collision on the CG when the channel becomes available again. In the case of high channel load / inter-WTRU congestion, the WTRU 102 may perform a backoff before selecting the first available CG opportunity.
[0095] The WTRU 102 may be configured to start a backoff timer when: (1) LBT fails to transmit to the CG; (2) after several LBT fails to transmit to the CG, and / or (3) once a channel becomes available. The backoff may be achieved by: (1) starting an AUL timer or a CG timer for the applicable CG, or (2) starting another backoff timer. For example, the WTRU 102 may condition the start of the timer on the channel load and / or the priority of the data on the channel. For example, once LBT fails to transmit to the PUSCH on the CG occasion, for example, when the measured received signal strength indicator (RSSI) or channel occupancy (CO) on the channel on which the CG is configured is higher than a certain threshold, the WTRU 102 may start the CG timer and / or the AUL timer. In another example, if the priority of the highest priority data contained in the PDU is lower than the configured threshold, the WTRU 102 may start the backoff timer, the CG timer and / or the AUL timer. The WTRU 102 may maintain one or more backoff timers for each CG resource or each LBT subband or each carrier.
[0096] When the backoff timer expires or stops, the WTRU 102 may transmit or retransmit the PUSCH at the CG timing. The value of the backoff timer may be configured by a higher layer or high layer signaling. Once the backoff timer is started, the WTRU 102 may apply the configured value to the backoff timer, or may start a backoff timer with a random value uniformly distributed between 0 and the configured value. In another example, backoff timer adaptation may be used. In this case, the backoff timer value may depend on the previously used backoff timer for the CG resource and additional time values that may be added or removed.
[0097] The WTRU 102 may be configured with a backoff value per logical channel (LCH), and the WTRU 102 may apply a backoff for one or more new transmissions based on the maximum backoff value configured for the LCH multiplexed on the PDU.
[0098] The WTRU 102 may stop the backoff timer (e.g., CG timer, and / or AUL timer) after the WTRU 102 receives a trigger signal from the gNB 180, which may be received on the same channel as the CG. For example, the WTRU 102 may stop the backoff timer upon receiving a demodulation reference signal (DM-RS) (e.g., on the same channel on which the CG is configured) or upon receiving a preamble signal from the gNB 180. In certain representative embodiments, the WTRU 102 may stop the backoff timer after the WTRU 102 receives an indication from the gNB 180, which the WTRU 102 may determine from explicit DCI and / or MACCE signaling, or may implicitly determine from reception of a DL signal and / or channel prior to the CG opportunity. The gNB 180 may instruct the WTRU 102 to start a backoff timer for the WTRU 102 via a DL indication (e.g., an implicit indication or an explicit indication) such as a media access control (MAC) control element (MAC CE) and / or DCI. The WTRU 102 may receive an indication from the gNB 180 indicating a backoff of CG transmission or retransmission for a period of time or a plurality of upcoming CG opportunities. For example, the WTRU 102 may be preconfigured with an initial backoff period in absolute time or a number of CG cycles, and the WTRU 102 may start the configured backoff period after receiving the backoff indication from the gNB 180. The backoff indication to the WTRU 102 may be applicable to a specific CG or a specific subband. For example, if the WTRU 102 receives a specific backoff indication on the same subband or when the subband and / or CG is explicitly indicated, the WTRU 102 may start the backoff on the specific subband and / or CG. In another example, if the WTRU 102 does not receive an expected or periodic DL trigger signal before the start of the CG opportunity or a subset of CG opportunities (or within or after the period of the start of the CG opportunity or a subset of CG opportunities), the WTRU 102 may start the back-off timer (e.g., a CG timer and / or an AUL timer, etc.). Representative process for redundancy version (RV) selection for transmission on CG
[0099] In a conventional FeLAA LTE system, the WTRU 102 may (e.g., independently) select a RV and may signal a portion of its uplink control information (UCI) in an AUL transmission or retransmission. Unlike turbo codes, low-density parity-check (LDPC) codes may include more systematic bits in the first RV and the last RV. Random RV selection may not work in NR-U as in LTE / FeLAA AUL. If the WTRU 102 keeps incrementing the RV for each transmission attempt without considering the LBT result, the gNB 180 may not benefit from a soft combining perspective if a retransmission is received with the same RV. In certain representative embodiments, the WTRU 102 may select a RV based on a preconfigured behavior or a predetermined behavior, for example to improve the results of a soft combining operation.
[0100] In certain representative embodiments, the WTRU 102 may conditionally increase the RV when LBT was successful for a previous transmission or retransmission. For example, the WTRU 102 may increase the RV after (e.g., only after) a transmission or retransmission in which LBT was successful on a CG. In other representative embodiments, the WTRU 102 may be configured with a sequence and / or pattern to select RVs for transmission or transmissions on applicable CGs. For example, when the WTRU 102 is configured with a RV sequence for repetitions on a CG, if LBT was successful for a given repeated transmission, the WTRU 102 may increment the RV according to the configured sequence.
[0101] After the WTRU 102 switches to a different active CG on a different subband, a different LBT bandwidth, a different BWP, and / or a different UL carrier, the WTRU 102 may reset the RV to 1 (or an initial value or a preconfigured value) for retransmission. Representative process for CG retransmission on different LBT channels
[0102] In certain embodiments, the WTRU 102 may be configured with multiple CG configurations such that each CG may be in a different subband and / or a different carrier. In one exemplary embodiment, the WTRU 102 may be configured to autonomously select a CG from a configured set of CGs for an initial transmission of a transport block (TB) and use the same CG resources for subsequent retransmissions / repetitions of the initially transmitted TB. In another exemplary embodiment, for the same TB, the WTRU 102 may be capable of or configured to select or reselect different CG resources in different subbands for retransmissions / repetitions based on any of the following triggers: (1) The number of channel access failures (e.g., LBT failures) is higher than a threshold, for example, a channel access failure may occur when attempting to retransmit the same repetition block / perform repetition of the same transmission block using the initially selected CG. In certain representative embodiments, the WTRU 102 may select a CG resource in a subband to transmit a TB. The channel access process may have been successful in the first transmission, and during the retransmission / repetition, the WTRU 102 may have failed to access the channel N times and N is higher than the configured threshold. The WTRU 102 may be semi-statically or statically configured with N, or may be dynamically configured with N. In an exemplary embodiment, the WTRU 102 may be configured with a counter to count the number of failed channel accesses. After successfully accessing the channel, the WTRU 102 may reset the counter. In certain representative embodiments, after successfully accessing the channel, the WTRU 102 may continue to run the counter and may reselect a different CG when the counter reaches N); (2) The number of channel access failures (i.e., LBT failures) within a sub-band is higher than a configured threshold (e.g., the WTRU 102 may be semi-statically, statically, or dynamically configured with a maximum number of attempts. In an exemplary embodiment, the WTRU 102 may be configured with a counter to count the number of failed channel accesses within the sub-band. The WTRU 102 may reset the counter after successfully accessing the channel. In certain representative embodiments, the WTRU 102 may keep running the counter after successfully accessing the channel and may select or reselect a different CG when the counter reaches a maximum number. In some embodiments, the WTRU 102 may consider (e.g., only consider) the number of channel access failures that occurred when attempting to transmit some UL signals within the sub-band. For example, the WTRU 102 may consider any of the following: a PUSCH carrying a UCI signal, a physical uplink control channel (PUCCH), and / or a physical random access channel (PRACH) (e.g., a PUSCH, a PUCCH, and / or a PRACH carrying only a UCI signal). In some embodiments, the WTRU 102 may take into account the number of channel access failures that occur when attempting to transmit all UL signals within the sub-band); (3) Systematic / persistent / consistent LBT failure is detected in the MAC layer (e.g., the WTRU MAC may detect a consistent LBT failure in a representative process, and the WTRU 102 may select and / or switch to another active: (1) subband, (2) BWP, and / or (3) carrier to perform the next transmission or retransmission); (4) The elapsed time is above a configured threshold or a predetermined threshold (e.g., from the time the WTRU 102 first attempted to access the channel for an initial transmission); (5) The time that has elapsed is above a configured threshold or a predetermined threshold (e.g., since the WTRU 102 first attempted to access the channel for a retransmission); (6) the measured RSSI or CO per subband is above a configured threshold or a predetermined threshold (e.g., the WTRU 102 may be configured to measure the RSSI per subband and / or the WTRU 102 may be configured to measure the RSSI for each subband before starting the channel access procedure on that subband. The WTRU 102 may determine that the RSSI measured on the subband on which the last transmission or retransmission was attempted is above the configured threshold and may select a different subband. In some embodiments, if the RSSI measured on a different active subband, BWP, and / or carrier is less than the configured threshold, the WTRU 102 may select that subband, BWP, and / or carrier to perform the next transmission or retransmission); (7) The CG period for the initial transmission of the TB is above a configured threshold or a predetermined threshold (e.g., the WTRU 102 may be configured with two CG configurations, namely, a first configuration with a first period (e.g., a relatively large period, such as equal to or above a first threshold) and a second configuration with a second period (e.g., a relatively small period, such as below the first threshold). At the time of the first transmission, the first configuration (e.g., only the first CG configuration) may be available, and the second CG configuration may not be available until the next opportunity (e.g., the next period, the next time frame and / or the next time slot). The WTRU 102 may select the first configuration and may reselect the second configuration for retransmission in the next time slot); (8) within a configured time window, a large number (e.g., above a configured threshold or a predetermined threshold) of HARQ-ACK feedback is lost and / or a large number of NACKs are received for one or more previous transmissions or one or more previous retransmissions (e.g., the WTRU 102 may select CG resources within a subband and may transmit TBs and one or more retransmissions thereof. The WTRU 102 may start a timer to count the number of NACKs and / or lost HARQ-ACK feedbacks for the configured time window. After the timer expires, the WTRU 102 may determine that the number of lost HARQ-ACK feedbacks and / or the number of NACKs is above a configured or predetermined threshold, and the WTRU 102 may, for example, select or reselect a different CG in a different subband); and / or (9) Based on logical channel prioritization (LCP) parameters (e.g., the WTRU 102 may select a different active CG to perform the next transmission or retransmission, such as when the data included in the PDU can be mapped to a grant and / or the grant satisfies the LCP mapping constraints configured for the LCH included in the PDU, etc. Representative process for CAPC selection for transmission on CGS
[0103] In FeLAA, the WTRU 102 may select the lowest channel access priority category among the channel access priority categories configured for the LCH in the PDU. Applying the same rules to NR-U may force the WTRU 102 to group data with the same priority (or CAPC) into the same PDU.
[0104] In some embodiments, the WTRU 102 may exclude certain LCHs in the LCP during PDU construction if any of the following conditions are met: (1) Priority (LCH) ≤ threshold, and / or a higher priority LCH is mapped to a grant, (in one example, the priority threshold may be indicated per grant and / or may be determined by the WTRU 102 based on physical characteristics of the scheduling resources or the grant itself); (2) CAPC priority (LCH) ≤ threshold, and other LCHs with configured higher priority CAPCs are mapped to the grant (in one example, the WTRU 102 may determine the threshold based on whether the PDU includes a MAC CE and / or a subset of high priority MAC CEs. The RRC may configure the mapping between a MAC CE subset and a CAPC). (3) Radio Resource Control (RRC) configures a subset of LCHs for: (1) possible exclusion (e.g., even if the LCH subset satisfies the LCP restrictions) and / or (2) multiplexing with LCHs having similar or higher CAPC priorities (e.g., the RRC may configure all or a subset of LCHs carrying SRBs to be multiplexed with LCHs having the same CAPC or higher priority CAPC. During the LCP procedure, the WTRU 102 may multiplex (e.g., may only multiplex) LCHs configured with a CAPC priority that is >= the CAPC priority configured for the LCHs carrying the SRBs contained in the PDU) and may exclude other LCHs configured with lower CAPC priorities. In another example, when and / or if the PDU includes an LCH carrying an SRB, the WTRU 102 may include (e.g., may only include) LCHs configured with the same or higher LCP priority. (4) The number of LBT failures is ≥ a threshold, such as a threshold configured by RRC; (5) The number of bits (or %) of excluded LCHs “to be mapped” to the grant is ≤ the threshold; (6) The ratio of bits "to be mapped" to the allowed excluded LCH / {bits mapped from non-excluded LCH to the allowed or TBS} is ≤ threshold; (7) the number of bits (or %) that “will be mapped” to the granted non-excluded LCH ≥ threshold; and / or (8) The ratio of bits "to be mapped" to the granted non-excluded LCHs / {bits or TBS mapped from the excluded LCHs to the granted} ≥ threshold, and so on.
[0105] In other representative embodiments, the WTRU 102 may dynamically determine the CAPC and / or exclude data transmissions from certain LCHs based on any of the following: (1) a timer expires and / or the time that has elapsed since the initial transmission was completed is greater than a configured or predetermined threshold (e.g., the WTRU 102 may increment the CAPC priority if the time that has elapsed since the PDU construction or initial transmission is greater than a configured threshold); (2) the priority of the highest priority LCH in the MAC PDU does not meet the threshold requirement (e.g., if the data in the PDU has an LCP priority less than a certain configured or predetermined priority and / or the number of data bits is less than a configured or predetermined threshold, the WTRU 102 may apply the highest priority CAPC (or the lowest configured CAPC number)); (3) the number of padding bits and / or TBS is greater than or equal to a configured or predetermined threshold (e.g., if the number of data bits is less than the configured threshold, the WTRU 102 may apply a lower priority CAPC, and / or if the number of data bits is less than or equal to the configured threshold, or if the number of padding bits is greater than or equal to the configured threshold, the WTRU 102 may apply UL skipping at the CG opportunity); (4) the number of transmissions and / or retransmissions exceeds a configured or predetermined threshold (e.g., the WTRU 102 may change the CAP used based on the number of retransmission attempts or the number of LBT failures); and / or (5) Receiving a muting indication or a change in LBT configuration, for example, from the gNB 180 (e.g., the gNB 180 may determine that some WTRUs 102 or LCHs are unfairly increasing load and / or CO. The WTRU 102 may receive a muting indication (or a change in LBT configuration) for UL transmissions (e.g., some or all UL transmissions), transmission subsets, UL channel subsets, LBT subsets, and / or UL resource subsets. The muting indication or LBT configuration change indication may be valid until (i) otherwise indicated, (ii) scheduled by a dynamic grant, and / or (iii) a period of time has passed (which may be configured by RRC or dynamically indicated), etc. Representative process for transmit power allocation and power control
[0106] The WTRU 102 may be configured to have multiple unlicensed carriers. The WTRU 102 may have CG resources on multiple of those carriers. In some instances, the WTRU 102 may have transmissions on multiple unlicensed carriers. For example, the WTRU 102 may transmit multiple PUSCHs simultaneously on multiple CG resources, e.g., in different carriers, or the WTRU 102 may transmit at least one PUSCH on a CG in one unlicensed carrier and at least one PUSCH on a DG in one (e.g., another) unlicensed carrier, e.g., simultaneously.
[0107] When transmitting simultaneously on multiple carriers, the WTRU 102 may determine the transmit power in each carrier based at least on the total number of simultaneous UL transmissions.
[0108] In certain embodiments, the total power available for the simultaneous UL transmissions (e.g., all of the simultaneous UL transmissions) by the WTRU 102 may be fixed (e.g., fixed to a maximum value (e.g., Pmax)). Since interference may not be a large factor in unlicensed operation, it is contemplated that the transmit power of each PUSCH may be maximized. In such an embodiment, the WTRU 102 may allocate power to each PUSCH, for example, to achieve a maximum total power. For example, the WTRU 102 may determine the power for each PUSCH based on the allocation rules described herein. In some cases, the PUSCH transmit power may have limits (e.g., to achieve regulatory requirements). For example, the WTRU 102 may assign or reallocate any unused power to other PUSCH transmissions, other carriers, and / or LBT subbands.
[0109] In a process where the WTRU 102 may have a maximum total transmit power that may be shared by all of the simultaneous transmissions, the WTRU 102 may determine the amount of power to allocate to each PUSCH transmission based on any of the following: (1) equal power sharing (e.g., the WTRU 102 may divide the total maximum transmit power for PUSCH transmissions (e.g., equally for all PUSCH transmissions); (2) Weighted sharing of power (e.g., each PUSCH may use weighted sharing of power. The maximum transmission power may be shared among PUSCH transmissions (e.g., all of the PUSCH transmissions), and the ratio of the weighted sharing shares used by the PUSCHs may depend on any of the following: (i) Grant type (e.g., DG or CG), such that, for example, the CG can use a larger share of the transmission power (possibly ensuring robustness on the shared CG resources). (ii) One or more parameters of the license, such as frequency allocation (including the number of LBT sub-bands spanned by the allocation), modulation and coding scheme (MCS), TBS, and subcarrier spacing (SCS). (iii) LBT type or parameters for the carrier, such that, for example, the WTRU 102 may determine a weighted share of the power allocation for the PUSCH based on the LBT type or parameters of the carrier used to access the transmission (e.g., based on the parameters of the LBT (e.g., Energy Detection (ED) threshold, Contention Window Size (CWS), and CAPC, etc.) or the LBT type (e.g., CAT2 or CAT4), the WTRU 102 may use different weights. For example, the WTRU 102 may use higher power for carriers using LBT with higher (or lower) priority access priority); (iv) an LCH is mapped to the grant (e.g., based on the LCH priority of the LCH, the WTRU 102 may determine the appropriate power allocation weight); (v) CO measurement (e.g., based on the CO or RSSI measurement, the WTRU 102 may adjust the power allocation weights for transmissions); (vi) the interlace used for the transmission (e.g., the interlace parameters (e.g., the number of PRBs used for the transmission and / or the number of unused PRBs) or the number of interlaces used may determine the weight of the power allocation share for the transmission; (vii) whether the transmission is an original transmission or a retransmission; and / or (viii) Whether a previous transmission attempt for the transport block failed due to LBT failure.
[0110] The WTRU 102 may acquire (e.g., successfully acquire) a subset of carriers for which the WTRU 102 has a DG or the WTRU 102 intends to use CG resources at any given moment. In this case, the WTRU 102 is not expected to or does not perform UL transmissions for the carriers that have had LBT failures. The WTRU 102 is able to reallocate part or all of the power calculated for transmissions on the carriers where LBT failed to at least one other transmission on one or more carriers where LBT was successful. For example, the WTRU 102 may have two simultaneous transmissions occurring on two CGs in two different carriers. LBT may succeed on a first carrier and may fail on a second carrier. In this case, the power allocated for transmissions in the second carrier may be reallocated to transmissions in the first carrier.
[0111] The WTRU 102 may predetermine multiple power allocation values for each PUSCH based on different LBT acquisition results, for example, to facilitate WTRU processing. For example, a WTRU 102 with two transmissions may predetermine three transmission states, each with different power allocation values for the two transmissions (e.g., (P1a, P2a) if both LBTs are successful; (P1b, 0) if only the LBT for the first transmission is successful; and (0, P2b) if only the LBT for the second transmission is successful). If the WTRU 102 has n scheduled simultaneous transmissions, the WTRU 102 may calculate n values for each PUSCH transmission, for example, to reduce the total number of pre-allocated values to be calculated to consider all possible combinations of LBT results. Depending on the number of successful LBTs, the WTRU 102 may select one of the n values calculated.
[0112] The gNB 180 may indicate to the WTRU 102 that the gNB 180 is sharing the COT (e.g., which is acquired before the start of the PUSCH for the CG resources (or any UL resources)). For example, the gNB 180 may indicate to the WTRU 102 that the gNB 180 is sharing the COT and the remaining time before the maximum COT (MCOT) is reached. The WTRU 102 may determine the COT sharing implicitly and / or explicitly.
[0113] The WTRU 102 may determine the COT sharing (e.g., DL to UL switching) based on explicit signaling from the gNB 180. For example, the WTRU 102 may receive information via any of the following: (1) MAC CE; (2) DCI; (3) physical downlink shared channel (PDSCH); and / or (4) broadcast transmission, which indicates the remaining time in the MCOT and possible LBT configuration parameters and / or applicable active CG configuration (or UL resources). The WTRU 102 may determine the COT sharing (DL to UL switching) after receiving the indication in the DCI, the attributes of the DCI, or the attributes of the physical downlink control channel (PDCCH) resources.
[0114] In certain representative embodiments, the WTRU 102 may determine that the COT is shared based on an implicit indication from the gNB 180 (e.g., a DL to UL switch). For example, the WTRU 102 may receive a channel acquisition signal (or trigger), such as a DM-RS or preamble, at the end of a DL transmission to indicate to the WTRU 102 the end of the DL portion of the acquired COT and possible implicit LBT configuration parameters that may be derived for the UL. In another example, the WTRU 102 may determine that the COT is shared based on receiving a DL data transmission that ends within a specific time gap starting from the PUSCH on the first CG opportunity. For example, the WTRU 102 may be configured with a DL SPS resource that may end within a short time gap starting from the PUSCH on the first CG opportunity, such that the short time gap may allow (e.g., may be accepted to allow) COT sharing between the gNB 180 and the WTRU 102. The WTRU 102 may implicitly determine the remaining time in the COT based on the start of the first PDSCH received on the DL SPS resources.
[0115] In certain representative embodiments, the WTRU 102 may indicate to the gNB 180 that the gNB 180 is sharing the COT that it acquired for the purpose of transmitting on the CG. The WTRU 102 may signal the gNB 180 that it no longer has data to transmit for the remaining COT. For example, the WTRU 102 may indicate to the gNB the COT sharing and the remaining time until the MCOT is reached. Such an indication may be implicitly or explicitly indicated. For example, the WTRU 102 may include a MAC CE that indicates the remaining time in the MCOT.
[0116] Aperiodic UL or DL CG may be useful in licensed and / or unlicensed spectrum. In unlicensed spectrum, the time at which a channel becomes available may not be aligned with the next CG opportunity, thereby giving the channel to other technologies. The channel may no longer be available before the CG opportunity begins. When the WTRU 102 transmits or receives time-sensitive communication (TSC) services, the service pattern period may not be aligned with the period of the SPS and / or CG resources. For example, a TSC message period that is a non-integer multiple of the CG / SPS period supported by NR may result in undesirable: (1) delays for a subset of latency-critical messages; and / or (2) additional buffering (e.g., additional buffering for jittered messages that are not aligned with the upcoming CG opportunity).
[0117] In certain embodiments, the WTRU 102 may receive DL signaling or an indication that the next one or more CG opportunities are shifted by a period of time, a number of symbols, and / or a number of time slots. The WTRU 102 may receive the DL signaling or the indication via a DCI, in a DCI field, in a MAC CE, and / or may determine the indication based on a PDCCH attribute. The WTRU 102 may be pre-configured with one or more conditional time shifts, from which the WTRU 102 may select based on the indicated shift or shift index. For example, the WTRU 102 may be pre-configured with multiple time shifts by the RRC or higher layers, and the WTRU 102 may shift the upcoming CG opportunity by an applicable shift indicated by the gNB 180. The WTRU 102 may attempt to transmit on the shifted UL CG opportunity and / or may attempt to receive DL data on the shifted DL CG opportunity. The WTRU 102 may be configured or indicated to apply to multiple upcoming CG occasions, a time period, and / or once every Nth CG occasion, whereby N may be signaled or preconfigured.
[0118] In certain embodiments, the WTRU 102 may be configured or specified to conditionally consider a subset of CG opportunities, CG configurations, and / or CG resources based on LBT results or based on a delay (e.g., jitter delay) to the next one or more CG opportunities.
[0119] The WTRU 102 may be configured or specified to treat a set of CG opportunities and / or CG configurations as one or more conditional CG opportunities applicable to certain conditions. For example, if the WTRU 102 receives a DL signal before some CGs and is not scheduled to receive any DL TBs in unconditional CG opportunities, the WTRU 102 may skip monitoring the next N CG opportunities and / or may skip an additional / conditional set of CG opportunities. The value of N may be configured by higher layers and is at least 1. In another example, if the WRTU receives a DL signal, a trigger signal, or a DRS signal before or during an unconditional CG opportunity, the WTRU 102 may monitor the N upcoming CG opportunities or the set of conditional / additional CG opportunities.
[0120] In one embodiment, if the WTRU 102 does not receive a DL scheduling, a discovery reference signal (DRS) (e.g., a synchronization signal), a wake-up signal, a channel acquisition signal, or / and a triggered DL signal before a given CG resource or conditional CG opportunity begins, the WTRU may consider another conditional CG as active.
[0121] In certain representative embodiments, if the jitter delay between the TSC message arrival time and the upcoming CG opportunity of (one or more) active CG configurations is greater than or equal to a time threshold, the WTRU 102 may consider (or determine) that another CG is active. The time threshold may be pre-configured and / or predetermined based on the period of the applicable CG configuration. The WTRU 102 may determine the TSC arrival time by: (1) based on the TSN service pattern provided by the core network (e.g., a network entity); (2) determined within the WTRU 102, and / or (3) based on the time of arrival at the WTRU buffer. The WTRU 102 may be configured with a mode to switch to another active CG once every Nth CG opportunity for M≥1 CG opportunities, and then the WTRU 102 may switch back to the original CG opportunity, whereby the values of N and M may be configured by RRC.
[0122] In certain representative embodiments, when the WTRU 102 is configured with discontinuous reception (DRX), which DRX is active and the CG is configured such that a subset of CG opportunities do not overlap with the On Duration, the WTRU 102 may autonomously wake up to transmit on CG opportunities that are not aligned with the On Duration. The WTRU 102 may perform this behavior in any of the following situations: (i) the delay between the message arrival time and the next open duration, (ii) the duration since the PDU was constructed, and / or (iii) Number of LBT failures and / or retransmissions of MAC PDUs.
[0123] When UL data is sent, the WTRU 102 may start or restart the DRX Inactivity Timer and DRX-HARQ-RTT-TimerUL even if the CG timing is not aligned with the on-duration.
[0124] Depending on channel sparsity and / or traffic arrival patterns, dynamic indications of additional CG opportunities may be beneficial. In certain representative embodiments, the WTRU 102 may receive dynamic signaling and / or indications that may indicate one or more additional / conditional CG opportunities, or the removal of one or more CG opportunities, which may be valid for a period of time or several cycles. For example, the WTRU 102 may receive signaling on a DCI or via a MAC CE that may indicate one or more additional or conditional CG opportunities. The WTRU 102 may be pre-configured with resource configurations for such additional CG opportunities and / or durations for which such additional opportunities are considered valid (or dynamic indications of these). For example, the RRC may configure a given CG configuration with a regular period of 2 slots, and may configure additional / conditional CG opportunities that are offset by {x, y, or z} symbols.
[0125] The WTRU 102 may indicate the scheduling assistance information portion of the MAC PDU for UL traffic. For example, the WTRU 102 may report any of the following: (1) the time difference between the message arrival time and the CG opportunity, (2) the preferred CG configuration, (3) the preferred subband and / or BWP, (4) one or more channel measurements, (5) the traffic period, (6) the time difference between the message arrival time and the traffic arrival pattern configured by the core network, and / or (7) the need for an additional conditional SPS opportunity before the next CG opportunity of one or more active CGs.
[0126] In certain embodiments, upon receiving a dynamic indication from the gNB 180, the WTRU 102 may increase or decrease the periodicity of the CG by a preconfigured or indicated factor. For example, the WTRU 102 may receive a DL MAC CE indicating a scaling of the periodicity for a given CG by a factor of 2, which may be for a period of time that is preconfigured or indicated in a portion of the MAC CE. As a result of this scaling, the WTRU 102 may consider and / or set additional CG opportunities as conditional or additional opportunities, as described herein. Representative process for UCI on CG transfer
[0127] For CG transmissions, the WTRU 102 may include a CG-UCI. The CG-UCI may enable the gNB and / or access point, for example, to correctly decode the CG. For example, the CG-UCI may include any of the following: (1) WTRU-ID; (2) transport block size (TBS); (3) resource allocation (for example, the CG may be configured with one or more possible resource sets, and the CG-UCI may indicate which resources, which resource set, or which resource sets are used (for example, actually used). In some examples, the CG may implement transmission on multiple interlaces, and the CG-UCI may indicate one or more interlaces used by the WTRU 102); (4) modulation and coding scheme (MCS); (5) the number of antenna ports; (6) precoding matrix; (7) the type of LBT used to acquire the channel, which may indicate the LBT classification and / or CAPC used; (8) transmission configuration indication (TCI) state, which may include quasi-colocation assumption; (9) one or more beams used for the transmission, which may include analog and / or digital (for example, transmitted precoding matrix indicator (TPMI)) beam information; (10) priority of the transmission, which may include reliability and / or delay requirements; and / or (11) CBG related information, etc.
[0128] The UCI may be mapped to the resources of the CG. The network may need and / or require the CG-UCI before demodulation of the CG data. In certain representative embodiments, the CG-UCI may be mapped to resources in the CG slot that are earlier than the resources of the CG. In certain examples, the CG-UCI may be mapped to the first symbol, or a group of first or earlier time slot symbols, such as symbols without DM-RS. In other instances, the CG-UCI position within the CG slot may be located at any fixed position or configurable position within the CG slot.
[0129] In some examples, the CG-UCI may be mapped to a resource (eg, symbol) closest to the DM-RS. In some examples, the CG-UCI may be repeated in different resources of the CG, which may improve the robustness of the CG-UCI.
[0130] In some examples, the CG-UCI may be mapped to, for example, a fixed physical resource block (PRB) or a set of PRBs within an interlace (eg, each interlace). Representative process for reusing CG-UCI, UCI and data
[0131] The WTRU 102 may have a fixed number of resources for the CG-UGI (e.g., resources reserved for the CG-UCI). The number of resources may depend on the encoding of the CG-UCI. In some examples, the number of resources for the CG-UCI may also be fixed, and the encoding of the CG-UCI may be fixed, for example, to provide robustness (e.g., more robust).
[0132] The resources available for data in the CG resources may depend on the total number of resources acquired and the possible fixed number of resources used for the CG-UCI.
[0133] The WTRU 102 may be configured with a β offset value for data in the CG resources. For example, the β offset may ensure that a minimum amount of resources may be reserved for the CG-UCI. The WTRU 102 may determine the TBS for the data to be transmitted in the CG resources based on any of the following: (1) a β offset for the data (e.g., the β offset value may be: (i) semi-statically configured, (ii) selected by the WTRU 102 (e.g., selected from a set of possible values) and / or (iii) included in the CG-UCI; (2) the size of the CG-UCI); (3) the duration of the CG resources, which may be a function of channel acquisition timing; (4) resource allocation (e.g., the number of interleavings used); (5) a β offset for the CG-UCI; and / or (6) a selected MCS, etc.
[0134] In some examples, the CG-UCI may not be required in all CG resources. For example, the CG-UCI may be applied to multiple CG transmissions. Depending on whether the WTRU 102 transmits the CG-UCI, the WTRU 102 may rate match and / or puncture the data around the CG-UCI in the CG resources.
[0135] In some examples, the WTRU 102 may multiplex the UCI in the CG resources. The UCI may include SR, HARQ and / or CSI feedback. When the UCI is multiplexed with the CG, the WTRU 102 may reuse Rel.15 to multiplex the UCI and data for resources not used for the CG-UCI. In some examples, the WTRU 102 may first determine the amount of resources reserved for the CG-UCI. The WTRU 102 may determine the remaining resources to be used for data and / or conventional UCI. The WTRU 102 may use the β offset value for the SR, the HARQ and / or the CSI to calculate the amount of resources used for the UCI.
[0136] In some examples, the WTRU 102 may multiplex the CG-UCI with the regular UCI, may map the combined UCI to the resources of a time slot, and may determine the remaining resources to be used for data transmission. The CG-UCI may be considered to have the highest priority among all UCIs, and the CG-UCI may not be discarded from the CG transmission.
[0137] In some examples, the CG-UCI may be concatenated to one or more types of UCI. For example, the CG-UCI may be concatenated to a HARQ UCI. The WTRU 102 may determine the resources for the CG-UCI+HARQ UCI using the beta offset value applicable to the concatenated UCI.
[0138] Figure 4 is a flow chart illustrating a representative process for transmission of a transport block.
[0139] refer to Figure 4 , the representative process 400 may include: At block 410, the WTRU 102 receives LCH information for at least first and second LCHs. The LCH information may include, for example, a logical channel priority (LCP) and / or a channel access priority class (CAPC) for some or each of the at least first and second LCHs. At block 420, the WTRU 102 may determine to transmit a transport block (TB) including a packet data unit (PDU). At block 430, the WTRU 102 may determine to include data from the first LCH in the PDU based on the LCP of the first LCH. At block 440, the WTRU 102 may generate the PDU. For example, the PDU may include: (1) data from the first LCH; or (2) data from the first LCH and data from the second LCH. The selection of the content of the PDU may be based on a comparison of the CAPC of the second LCH with: (i) a threshold; or (ii) the CAPC of the first LCH. At block 450, the WTRU 102 may transmit the TB including the generated PDU.
[0140] In certain representative embodiments, the WTRU 102 may determine whether to include data from the second LCH in the PDU based on whether the CAPC of the second LCH equals or exceeds the CAPC of the first LCH.
[0141] In certain representative embodiments, the first LCH may have a CAPC restriction, and the generating and / or the selecting of the PDU content may be further based on the LCH restriction.
[0142] In certain representative embodiments, the threshold (eg, CAPC threshold) may be any of: (1) a signaled threshold; or (2) a pre-established threshold.
[0143] In certain representative embodiments, the first LCH may have a CAPC restriction under the condition that the first LCH is carrying priority data / signaling (eg, URLLC information / signaling and / or signaling radio bearer (SBR), etc.).
[0144] In certain representative embodiments, the generated PDU may include data from the second LCH if the CAPC of the second LCH is greater than or equal to the CAPC of the first LCH.
[0145] In certain representative embodiments, where the CAPC of the second LCH is less than the CAPC of the first LCH, the generated PDU may not include data from the second LCH (eg, the PDU may only include data corresponding to a CAPC higher than the CAPC of the first LCH).
[0146] Figure 5 is a flow chart illustrating another representative process for transmitting a PDU.
[0147] refer to Figure 5 , the representative process 500 may include: At block 510, the WTRU 102 determines whether a first LCH having data to be sent in a packet data unit (PDU) has a channel access priority class (CAPC) restriction. At block 520, if the first LCH has a CAPC restriction, the WTRU 102 may determine whether to multiplex the data from the first LCH with data from the one or more other LCHs based on the CAPC of the first LCH and the CAPCs of some or each of the one or more other LCHs. At block 530, the WTRU 102 may selectively multiplex the data from the first LCH and the other LCHs in the PDU based on the CAPC rule. At block 540, the WTRU 102 may transmit the PDU.
[0148] In certain representative embodiments, the WTRU 102 may receive LCH information for a plurality of LCHs. For example, the LCH information may include a logical channel priority (LCP) and / or a channel access priority class (CAPC) for some or each of the plurality of LCHs.
[0149] In certain representative embodiments, the CAPC rule may include any of the following: (1) a comparison of the CAPC of a second LCH among the one or more other LCHs with a CAPC threshold; (2) a comparison of the CAPC of the second LCH with the CAPC of the first LCH; and / or (3) a comparison of whether the CAPC of the second LCH is equal to or exceeds the CAPC of the first LCH.
[0150] In certain representative embodiments, the CAPC threshold may be any of: (1) a signaled threshold; or (2) a pre-established threshold.
[0151] In certain representative embodiments, the first LCH may have a CAPC restriction under the condition that the first LCH is carrying priority data / signaling (eg, URLLC data / signaling and / or signaling radio bearer (SBR), etc.).
[0152] In certain representative embodiments, the WTRU 102 may selectively multiplex data from the first LCH and other LCHs such that data from the second LCH is multiplexed in the PDU if the CAPC of the second LCH is greater than or equal to the CAPC of the first LCH.
[0153] In certain representative embodiments, the WTRU 102 may selectively multiplex data from the first LCH and other LCHs such that, if the CAPC of the second LCH is less than the CAPC of the first LCH, data from the second LCH is not multiplexed in the PDU (e.g., only data corresponding to a CAPC equal to or higher than the CAPC corresponding to the first LCH is multiplexed into the PDU).
[0154] Figure 6 is a flow chart illustrating another representative process for transmission of a transport block.
[0155] refer to Figure 6, the representative process 600 may include: At box 610, the WTRU 102 receives information associated with one or more configured grants (CGs). At box 620, the WTRU 102 may select a first CG corresponding to a first CG configuration. At box 630, the WTRU 102 may transmit a transport block (TB) using resources associated with the first CG at a CG timing associated with the first CG. At box 640, the WTRU 102 may start a CG timer for the first CG in response to the transmission of the TB. At box 650, the WTRU 102 may receive a HARQ acknowledgement (ACK) indication in a downlink feedback information (DFI) of a downlink control information (DCI), which indicates a HARQ-ACK feedback value and is associated with a HARQ process ID (PID). At box 660, after receiving the HARQ ACK indication and under the condition that the HARQ-ACK feedback value is equal to ACK, the WTRU 102 may: (1) stop the CG timer, and / or (2) refresh the HARQ buffer associated with the HARQ PID, and / or (3) switch the NDI for the corresponding HARQ process.
[0156] In certain representative embodiments, after the CG timer expires: the WTRU 102 may select another CG timing corresponding to the first CG configuration or another CG configuration, and may retransmit the TB at the selected CG timing using resources associated with the selected CG.
[0157] In certain representative embodiments, the WTRU 102 may adjust the value of the CG timer and / or CG retransmission timer based on the parameters of the selected CG configuration.
[0158] Figure 7 is a flow chart illustrating a representative process for COT sharing.
[0159] refer to Figure 7 , the representative process 700 may include: At block 710, the WTRU 102 may obtain a channel occupation time (COT) associated with a configured grant (CG). At block 720, the WTRU 102 may determine a remaining time of the COT. At block 730, the WTRU 102 may send information indicating that the WTRU is sharing the COT with the network entity and the remaining time of the shared COT to a network entity during the COT using the CG. At block 740, the WTRU 102 may send a message including any of data or control signaling.
[0160] In certain representative embodiments, the WTRU 102 may receive another message via the network entity during the remaining time of the shared COT based on the information sent by the WTRU 102.
[0161] Figure 8 is a flow chart illustrating an additional representative process for transmission of a transport block.
[0162] refer to Figure 8 , the representative process 800 may include: at box 810, the WTRU 102 uses a listen-before-talk (LBT) operation to determine whether the LBT is successful. At box 820, if the LBT is successful, the WTRU 102 may (1) use the first configured grant (CG) to transmit or retransmit a transport block (TB) using resources associated with the first CG; and / or (2) increment the redundancy version (RV) for the next transmission or the next retransmission using the first CG or the further CG. At box 830, if the LBT is unsuccessful, the WTRU 102 may: (1) skip the transmission or the retransmission of the TB; and / or (2) maintain the RV for the next transmission or the next retransmission using the first CG or the further CG.
[0163] Fig. 9 is a flow chart of a representative transmission procedure using allocated / reallocated UL power.
[0164] refer to Fig. 9 , the representative process 900 may include: at box 910, the WTRU 102 receives configured grant (CG) information including at least a first CG and a second CG.
[0165] At block 920, the WTRU 102 may use listen before talk (LBT) to determine whether one or more of a plurality of channels associated with the received CG are idle for transmission as a result of the determination. At block 930, the WTRU 102 may allocate or reallocate uplink power associated with the CG based on the result of the determination. At block 940, the WTRU 102 may transmit or retransmit via the idle one or more channels associated with the CG using the allocated or reallocated uplink power.
[0166] In certain representative embodiments, the allocating or reallocating the uplink power may include increasing or newly providing uplink power for transmission or retransmission on a CC among multiple component carriers (CCs) used by the WTRU 102 in a carrier aggregation mode in the event that LBT fails on at least one CC among the multiple CCs.
[0167] Fig.10 is a flow chart illustrating yet another representative process for transmission of a transport block.
[0168] refer to Fig.10, the representative process 1000 may include: at block 1010, the WTRU 102 may transmit a transport block (TB) at a CG opportunity associated with a first configured grant (CG) using resources associated with a first CG. At block 1020, the WTRU 102 may retransmit the TB at a CG opportunity associated with a second CG using resources associated with the second CG. At block 1030, after receiving an acknowledgement (ACK), the WTRU 102 may toggle a new data indicator (NDI) at or before a further CG opportunity associated with the second CG. At block 1040, the WTRU 102 may transmit a new TB at the further CG opportunity associated with the second CG using resources associated with the second CG.
[0169] In certain representative embodiments, the WTRU 102 may receive CG information including the first CG and the second CG.
[0170] In certain representative embodiments, the WTRU 102 may determine that the first timer has expired and / or may configure the WTRU 102 to retransmit using a second CG resource and a CG timing associated with the second CG after the first timer has expired.
[0171] In certain representative embodiments, after transmitting or retransmitting the TB, the WTRU 102 may receive downlink feedback information (DFI) including an acknowledgment (ACK) of a successful transmission or successful retransmission of the TB. As an example, the WTRU 102 may switch the NDI based on the ACK included in the received DFI.
[0172] In certain representative embodiments, the WTRU 102 may stop a second timer associated with the second CG based on the ACK included in the received DFI.
[0173] In certain representative embodiments, the WTRU 102 may update the value of the CG timer associated with the selected CG based on the periodicity of transmission or retransmission associated with the selected CG in order to retransmit the TB of the applicable HARQ PID.
[0174] In certain representative embodiments, each of the CG timings and the further CG timings associated with the first CG and the second CG can be selected as any one of: (1) the next CG timing after a triggering event; or (2) the first available CG timing after the end of the backoff period.
[0175] In certain representative embodiments, the triggering event may be an indication received from a network entity.
[0176] In certain representative embodiments, for the retransmission, the WTRU 102 may select a second CG associated with resources on any of: (1) a different subband; (2) a different listen-before-talk (LBT) bandwidth, (3) a different bandwidth part (BWP), and / or (4) a different uplink carrier.
[0177] As disclosed herein, the first and second timers may be any of: a CG timer and / or a retransmission timer.
[0178] Fig.11 is a flow chart illustrating a representative transmission process using calculated transmit power allocation.
[0179] refer to Fig.11 , the representative process 1100 may include: at box 1110, the WTRU 102 receives CG information including at least a first configured grant (CG) and a second CG. At box 1120, the WTRU 102 may use listen before talk (LBT) to determine whether one or more channels of a plurality of channels associated with the received CG are idle for transmission as a determined result. At box 1130, the WTRU 102 may calculate a transmit power allocation associated with the CG based on the determined result. At box 1140, the WTRU 102 may transmit or retransmit via the one or more channels associated with the CG that are idle using the calculated transmit power allocation.
[0180] Fig.12 is a flow chart showing a representative process for changing the redundancy version.
[0181] refer to Fig.12 , a representative process 1200 may include: At block 1210, the WTRU 102 determines that a channel is idle for transmission using a listen-before-talk (LBT) operation. At block 1220, the WTRU 102 may transmit or retransmit a transport block (TB) using a first configured grant (CG) by using resources associated with a first CG. At block 1230, the WTRU 102 may receive an acknowledgment (ACK) or a negative ACK (NACK) regarding the transmission or the retransmission of the TB. At block 1240, the WTRU 102 may change a redundancy version (RV) associated with the retransmission of the TB for a next transmission or a next retransmission using the first CG or a further CG, conditional on a previous transmission or retransmission for which the WTRU 102 performed LBT successfully.
[0182] In certain representative embodiments, the changing of the RV may include any of: incrementing a RV value, decrementing a RV value, resetting a RV value, and / or selecting a RV value based on a sequence or a pattern.
[0183] In certain representative embodiments, the WTRU 102 may select a further CG associated with resources on any of: (1) a different subband; (2) a different list-before-talk (LBT) bandwidth, (3) a different bandwidth part (BWP), and / or (4) a different uplink carrier. For example, the changing the redundancy version (RV) associated with the transmission or the retransmission of the TB for a next transmission or a next retransmission using the further CG may include resetting the RV value to a predetermined value.
[0184] Fig.13 is a flowchart showing a representative process for modifying CG timing.
[0185] refer to Fig.13 , the representative process 1300 may include: at block 1310, the WTRU 102 receives modification information indicating one or more configured grant (CG) opportunities. At block 1320, based on the received modification information, the WTRU 102 may perform any of the following operations: (1) add one or more CG opportunities; (2) shift one or more upcoming CG opportunities in time and / or frequency; and / or (3) remove one or more CG opportunities.
[0186] Fig.14 is a flow chart showing a representative process for CG configuration, CG timing and / or CG resource selection.
[0187] Reference Fig.14 , the representative process 1400 may include: at block 1410, the WTRU 102 receives or obtains a plurality of CG configurations associated with a plurality of configured grant (CG) opportunities and a plurality of CG resources. At block 1420, the WTRU 102 may use listen-before-talk (LBT) to determine whether one or more of a plurality of channels associated with the received CGs are idle for transmission as a result of the LBT determination. At block 1430, the WTRU 102 may select a subset of the CG configurations, the CG opportunities, and / or the CG resources based on the determination result of the LBT, the jitter delay to the next CG opportunity or the next plurality of CG opportunities, and / or the reception or lack of reception of downlink signals.
[0188] Fig.15 is a flowchart showing a representative process for CG transmission.
[0189] refer to Fig.15, the representative process 1500 may include: At block 1510, the WTRU 102 receives a configured grant (CG) for uplink resources from a network entity. At block 1520, the WTRU 102 may map CG uplink control information CG-UCI and data to the uplink resources for a time slot for CG transmission. At block 1530, the WTRU 102 may send the CG transmission to the network entity. The uplink resources associated with the CG-UCI may be sent before the uplink resources associated with the data.
[0190] In certain representative embodiments, the CG-UCI may be mapped to uplink resources that are adjacent to and / or closest to one or more demodulation reference signals (DM-RS).
[0191] In certain representative embodiments, the CG-UCI may be repeated in different uplink resources of the CG transmission.
[0192] In certain representative embodiments, the CG-UCI may be mapped to: (1) a fixed physical resource block (PRB); and / or (2) a set of PRBs within an interlace.
[0193] In certain representative embodiments, the WTRU 102 may obtain and / or set an offset value to indicate the amount of resources reserved for the CG-UCI in the CG.
[0194] In certain representative embodiments, based on the offset value, the WTRU 102 may determine an amount of uplink resources to reserve for the CG-UCI, for data, and / or for regular UCI.
[0195] In certain representative embodiments, the WTRU 102 may multiplex the CG-UCI with a regular UCI. For example, the mapping of the CG-UCI may include mapping the multiplexed CG-UCI and the regular UCI to the uplink resources of the time slot. As another example, the WTRU 102 may map the data to the remaining uplink resources for the CG transmission.
[0196] Systems and methods for processing data according to representative embodiments may be performed by one or more processors executing sequences of instructions contained in a storage device. These instructions may be read into the storage device from other computer-readable media such as (one or more) auxiliary data storage devices. Execution of the sequences of instructions contained in the storage device causes the processor to operate, for example, as described above. In alternative embodiments, hard-wired circuits may be used in place of or in combination with software instructions to implement the present invention.
[0197] Although the features and elements are described above in specific combinations, it will be understood by those skilled in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware embedded in a computer-readable medium and executed by a computer or processor. Examples of non-transitory computer-readable media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, buffer memory, semiconductor storage devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM discs and digital versatile discs (DVDs). A processor associated with software may be used to implement a radio frequency transceiver used in a WTRU, UE, terminal, base station, RNC, or any host computer.
[0198] In addition, in the above-mentioned embodiments, processing platforms, computing systems, controllers and other devices including processors are mentioned. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to symbolic descriptions of actions and operations or instructions may be performed by various CPUs and memories. These actions and operations or instructions may be referred to as "being executed", "computer execution" or "CPU execution".
[0199] Those skilled in the art will appreciate that the operations or instructions described by the actions and symbols include the manipulation of electrical signals by the CPU. The electrical system may represent data bits, which cause the electrical signal to generate a transformation or restoration and the maintenance of the storage location of the data bit in the storage system, thereby reconfiguring or otherwise changing the operation of the CPU and other processing of the signal. The storage location where the data bit is maintained is a physical location with a specific electrical, magnetic, optical or organic property corresponding to or representing the data bit. It should be understood that the representative embodiments are not limited to the above-mentioned platforms or CPUs and other platforms and CPUs may support the provided methods.
[0200] The data bits may also be maintained on a computer-readable medium, including a magnetic disk, an optical disk, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read-only memory ("ROM")) CPU-readable mass storage system. The computer-readable medium may include cooperating or interconnected computer-readable media that reside exclusively on a processor system or distributed among multiple interconnected processing systems that may be local or remote to the processing system. It will be appreciated that the representative embodiments are not limited to the memories described above and that other platforms and memories may support the described methods.
[0201] In the illustrated embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.
[0202] There is a slight distinction between hardware and software implementations of systems. The use of hardware or software is generally (but not always, as the choice between hardware and software can be important in certain environments) a design choice that considers a trade-off between cost and efficiency. There can be various tools (e.g., hardware, software, and / or firmware) that affect the processes and / or systems and / or other technologies described herein, and the preferred tools can change with the context of the deployed processes and / or systems and / or other technologies. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose to use primarily hardware and / or firmware tools. If flexibility is most important, the implementer may choose to use primarily software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.
[0203] The above detailed description has presented various embodiments of the device and / or process through the use of block diagrams, flow charts and / or examples. To the extent that these block diagrams, flow charts and / or examples include one or more functions and / or operations, those skilled in the art will appreciate that each function and / or operation within these block diagrams, flow charts or examples can be implemented separately and / or together by a wide range of hardware, software or firmware or substantially any combination thereof. Suitable processors include, for example, general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application-specific integrated circuits (ASICs), application-specific standard products (ASSPs); field-programmable gate array (FPGA) circuits, any other type of integrated circuit (IC) and / or state machines.
[0204] Although the features and elements are described above in specific combinations, it will be understood by those skilled in the art that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in the present application, which are intended to be examples of various aspects. Many modifications and variations can be made without departing from its essence and scope, which are known to the art at all. The elements, actions or instructions used in the description of the present application should not be understood as being key or necessary to the present invention unless explicitly stated. In addition to these methods and devices listed herein, those skilled in the art can also know functionally equivalent methods and devices within the scope of the present disclosure based on the above description. These modifications and variations should also fall within the scope of the appended claims. The present disclosure is limited only by the appended claims, including the comprehensive scope of their equivalents. It should be understood that the present disclosure is not limited to a specific method or system.
[0205] It should also be understood that the terminology used herein is for the purpose of describing specific embodiments only and is not intended to be limiting. As used herein, when referring to the term "station" and its abbreviation "STA", "user equipment" and its abbreviation "UE" may mean: (i) a wireless transmit and / or receive unit (WTRU), such as described below; (ii) any of multiple embodiments of the WTRU, such as described below; (iii) a wireless and / or wired (e.g., wirelessly communicable) device configured with some or all of the structure and functionality of the WTRU, such as described below; (iii) a device with wireless capabilities and / or wired capabilities that is configured to have less than all of the structure and functionality of the WTRU, such as described below; or (iv) the like. The following references Figures 1A-1D Details are provided for an example WTRU which may represent any of the UEs described herein.
[0206] In certain representative embodiments, some parts of the subject matter described herein may be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will appreciate that some aspects of the embodiments disclosed herein, in whole or in part, may equally be implemented by integrated circuits, as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware, or substantially any combination of these, and that designing circuits and / or writing code for the software and / or firmware according to the present disclosure is known to those skilled in the art. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as program products in various forms, and that the exemplary embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media, such as floppy disks, hard disks, CDs, DVDs, digital tapes, computer memories, etc., and transmission media, such as digital and / or analog communication media (e.g., optical cables, waveguides, wired communication links, wireless communication links, etc.).
[0207] The subject matter described here sometimes shows different components, which are contained in or connected to different other components. It can be understood that these depicted architectures are only examples, and many other architectures that implement the same function in practice can be implemented. Conceptually, any arrangement of components that implement the same function more effectively "associated" can implement the desired function. Therefore, any two components combined here to implement a specific function can be regarded as "associated" to each other to implement the desired function, regardless of the architecture or intermediate components. Similarly, any two components associated can also be regarded as "operationally connected" or "operationally coupled" to implement the desired function, and any two components that can be associated in this way can also be regarded as "operationally couplable" to each other to implement the desired function. Specific examples of operational coupling include but are not limited to physically pairable and / or physically interactive components and / or wirelessly interactive and / or wirelessly interactive components and / or logically interactive and / or logically interactive components.
[0208] With respect to the use of substantially any plural and / or singular terms herein, those skilled in the art may translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. For purposes of clarity, various singular / plural permutations may be explicitly set forth herein.
[0209] Those skilled in the art will appreciate that the terms used herein in general and in particular in the claims (e.g., the body of the claims) are generally "open" terms (e.g., the term "including" should be understood as "including but not limited to", the term "having" should be understood as "having at least", the term "including" should be understood as "including but not limited to", etc.). Those skilled in the art will also appreciate that if a claim is to describe a specific number, it will be explicitly described in the claim, and there is no such meaning in the absence of such description. For example, if only one item is to be indicated, the term "single" or similar language may be used. To aid understanding, the following claims and / or the description herein may include the use of the preposition phrases "at least one" or "one or more" to introduce a claim description. However, the use of these phrases should not be understood to imply that a claim description introduced by the indefinite article "a" will limit any particular claim containing such introduced claim description to an embodiment containing only one such description, even if the same claim includes the preposition phrases "one or more" or "at least one" and an indefinite article (e.g., "a") (e.g., "a" should be understood to mean "at least one" or "one or more"). The same is true for the use of definite articles used to introduce claim descriptions. In addition, even if a specific number of claims described in the claims is explicitly described, it can be understood by those skilled in the art that such description should be understood to mean at least the number described (e.g., the description of "two descriptions" alone without other modifiers means at least two descriptions, or two or more descriptions). In addition, in these instances where a convention similar to "at least one of A, B, and C, etc." is used, generally speaking, such a convention is a convention understood by those skilled in the art (e.g., "the system has at least one of A, B, and C" can include but is not limited to the system having only A, only B, only C, A and B, A and C, B and C, and / or A, B and C, etc.). In these instances where a convention similar to "at least one of A, B, or C, etc." is used, generally speaking, such a convention is a convention understood by those skilled in the art (e.g., "the system has at least one of A, B, or C" can include but is not limited to the system having only A, only B, only C, A and B, A and C, B and C, and / or A, B and C, etc.). Those skilled in the art will also appreciate that substantially any separated word and / or phrase representing two or more alternatives, whether in the specification, claims or drawings, should be understood to include the possibility of including one of the two items, any one or both items. For example, the phrase "A or B" is understood to include the possibility of "A" or "B" or "A" and "B". In addition, the term "arbitrary" used herein followed by multiple items and / or multiple items listed is intended to include "arbitrary", "arbitrary combination", "arbitrary multiple" and / or "any combination of multiple" of the multiple items and / or multiple items, either alone or in combination with other items and / or other items.Furthermore, the terms "set" or "group" as used herein are intended to include any number of items, including zero. Furthermore, the term "number" as used herein is intended to include any number, including zero.
[0210] In addition, if features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also described in terms of any individual member or subgroup of members of the Markush group.
[0211] Those skilled in the art will appreciate that, for any and all purposes, for example, to provide a written description, all scopes disclosed herein also include any and all possible sub-ranges and combinations of sub-ranges thereof. Any listed scope can be easily understood to be sufficient to describe and implement the same scope that is divided into at least equal halves, three parts, four parts, five parts, ten parts, etc. As a non-limiting example, each scope described here can be easily divided into the lower third, the middle third, and the upper third, etc. Those skilled in the art can also understand that all languages such as "up to", "at least", "greater than", "less than", etc. include the described numbers and can be divided into the scope of the above-mentioned sub-ranges therewith. Finally, those skilled in the art can appreciate that the scope includes each individual member. Therefore, for example, a group and / or set with 1-3 cells refers to a group / set with 1, 2, or 3 cells. Similarly, a group / set with 1-5 cells refers to a group / set with 1, 2, 3, 4, or 5 cells, etc.
[0212] Furthermore, the claims should not be read as limited to the order or elements provided unless described to that effect. Furthermore, the use of the term "means for..." in any claim is intended to invoke 35 U.S.C. § 112, 6 or means-plus-function claim format, any claim without the term “means for…” does not have such an intent.
[0213] A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit / receive unit (WTRU), user equipment (UE), terminal, base station, mobility management entity (MME) or evolved packet core (EPC), or any host computer. The WTRU may incorporate modules implemented in hardware and / or software, including software defined radio (SDR), and other components such as a camera, a video camera module, a video phone, an intercom phone, a vibration device, a speaker, a microphone, a television transceiver, a hands-free headset, a keyboard, module, a frequency modulation (FM) radio unit, a near field communication (NFC) module, a liquid crystal display (LCD) display unit, an organic light emitting diode (OLED) display unit, a digital music player, a media player, a video game console module, an Internet browser and / or any wireless local area network (WLAN) or ultra-wideband (UWB) module.
[0214] Although the present invention has been described in terms of a communication system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In certain embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.
[0215] Furthermore, while the invention has been shown and described herein with reference to specific embodiments, the invention is not limited to the details shown. Rather, various modifications may be made to the details within the range of equivalents of the claims and without departing from the invention.
[0216] Throughout the disclosure, a skilled artisan will appreciate that certain representative embodiments may be used instead of or in combination with other representative embodiments.
[0217] Although the features and elements are described above in specific combinations, it will be understood by those skilled in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of non-transitory computer-readable media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, buffer memory, semiconductor storage devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, and any host computer.
[0218] In addition, in the above-mentioned embodiments, processing platforms, computing systems, controllers and other devices including processors are mentioned. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to symbolic descriptions of actions and operations or instructions may be performed by various CPUs and memories. These actions and operations or instructions may be referred to as "being executed", "computer execution" or "CPU execution".
[0219] Those skilled in the art will appreciate that the actions and symbolic descriptions of operations or instructions include the manipulation of electrical signals by the CPU. The electrical system representation may represent data bits, which cause the generation of transformations or restorations of electrical signals and the maintenance of storage locations of data bits in a storage system, thereby reconfiguring or otherwise changing the operation of the CPU and other processing of signals. The storage location where the data bit is maintained is a physical location with specific electrical, magnetic, optical or organic properties corresponding to or representing the data bit.
[0220] The data bits may also be maintained on a computer-readable medium, including a magnetic disk, an optical disk, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read-only memory ("ROM")) CPU-readable mass storage system. The computer-readable medium may include cooperating or interconnected computer-readable media that reside exclusively on a processor system or distributed among multiple interconnected processing systems that may be local or remote to the processing system. It will be appreciated that the representative embodiments are not limited to the above-described memories and that other platforms and memories may support the described methods.
[0221] By way of example, suitable processors include a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), an application specific standard product (ASSP); a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and / or a state machine.
[0222] Although the present invention has been described in terms of a communication system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In certain embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.
[0223] Furthermore, while the invention has been shown and described herein with reference to specific embodiments, the invention is not limited to the details shown. Rather, various modifications may be made to the details within the range of equivalents of the claims and without departing from the invention.
Claims
1. A method implemented by a wireless transmit and receive unit (WTRU), the method include: sending a first transport block (TB) associated with a hybrid automatic repeat request (HARQ) process using a first CG resource of at least one configuration grant (CG), wherein the first CG resource is associated with the HARQ process, and starting a first CG timer associated with the HARQ process and a first CG retransmission timer associated with the HARQ process; receiving HARQ feedback information associated with the HARQ process, wherein the received HARQ feedback information is associated with the first transport block; Based on receiving HARQ feedback information, stop the first CG retransmission timer associated with the HARQ process; Based on receiving the HARQ feedback information indicating an acknowledgement, stopping the first CG timer associated with the HARQ process; and When the first CG timer associated with the HARQ process stops and when the first CG retransmission timer associated with the HARQ process stops, a second TB associated with new data transmission is sent using a second CG resource in the at least one CG, wherein the second CG resource is associated with the HARQ process.
2. The method according to claim 1, further comprising: include: determining a plurality of HARQ processes associated with the CG resources; and A CG timer and a CG retransmission timer are maintained for each of the multiple HARQ processes.
3. The method according to claim 2, in, The CG timer and the CG retransmission timer for a first HARQ process among the multiple HARQ processes are different from the CG timer and the CG retransmission timer for a second HARQ process among the multiple HARQ processes.
4. The method according to claim 1, include: In case HARQ feedback information indicating confirmation is received, a HARQ buffer associated with the HARQ process is flushed, and a new data indicator (NDI) associated with the HARQ process is switched.
5. The method according to claim 1, further comprising: include: Downlink control information (DCI) including the HARQ feedback information is received, wherein the acknowledgement is indicated by a HARQ-ACK feedback value in downlink feedback information (DFI) of the DCI.
6. The method according to claim 1, wherein the first CG timer is stopped when the HARQ feedback information indicating confirmation is received, and wherein the first CG retransmission timer is stopped when the HARQ feedback information indicating confirmation or negative confirmation is received.
7. A wireless transmit and receive unit WTRU, the WTRU comprising a processor, a transceiver unit and a storage unit, the processor operating together with the transceiver unit and the storage unit, the processor being configured to: sending a first transport block (TB) associated with a hybrid automatic repeat request (HARQ) process using a first CG resource of at least one configuration grant (CG), wherein the first CG resource is associated with the HARQ process, and starting a first CG timer associated with the HARQ process and a first CG retransmission timer associated with the HARQ process; receiving HARQ feedback information associated with the HARQ process, wherein the received HARQ feedback information is associated with the first transport block; Based on receiving HARQ feedback information, stop the first CG retransmission timer associated with the HARQ process; Based on receiving the HARQ feedback information indicating an acknowledgement, stopping the first CG timer associated with the HARQ process; and When the first CG timer associated with the HARQ process stops and when the first CG retransmission timer associated with the HARQ process stops, a second TB associated with new data transmission is sent using a second CG resource in the at least one CG, wherein the second CG resource is associated with the HARQ process.
8. The WTRU of claim 7, configured to: determining a plurality of HARQ processes associated with the CG resources; and A CG timer and a CG retransmission timer are maintained for each of the multiple HARQ processes.
9. The WTRU according to claim 8, wherein the CG timer and the CG retransmission timer for the first HARQ process among the multiple HARQ processes are different from the CG timer and the CG retransmission timer for the second HARQ process among the multiple HARQ processes.
10. The WTRU of claim 7, configured to: In case HARQ feedback information indicating confirmation is received, a HARQ buffer associated with the HARQ process is flushed, and a new data indicator (NDI) associated with the HARQ process is switched.
11. The WTRU of claim 7, configured to receive downlink control information (DCI) including the HARQ feedback information, wherein the acknowledgement is indicated by a HARQ-ACK feedback value in downlink feedback information (DFI) of the DCI.
12. A WTRU according to claim 7, wherein the first CG timer is stopped when the HARQ feedback information indicating confirmation is received, and wherein the first CG retransmission timer is stopped when the HARQ feedback information indicating confirmation or negative confirmation is received.
