Apparatus and method for wireless communication

Abstract

An apparatus and method for wireless communication are provided. The apparatus includes a processor configured to: determine that a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook is scheduled to be transmitted in a first time slot, where a physical uplink control channel (PUCCH) resource indication identifier (PRI) is associated with the HARQ-ACK codebook; determining to discard the scheduled transmission of the HARQ-ACK codebook in the first time slot; determining a PUCCH (Physical Uplink Control Channel) resource set associated with the HARQ-ACK codebook; selecting a resource from the PUCCH resource set at least based on the PRI; determining transmission time; and transmitting the HARQ-ACK codebook at the determined transmission time, the HARQ-ACK codebook being transmitted at the determined transmission time being transmitted on the selected resource in a second time slot.

Description

[0001] This application is a divisional application of the invention patent application with the application date of February 12, 2020, application number 202080018158.5, and invention name “Device and method associated with wireless communication”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 805,023, filed on February 13, 2019, the contents of which are incorporated herein by reference. Technical Field

[0004] The present application relates to the field of wireless communications. Background Art

[0005] Mobile communications are undergoing a continuous evolution and are already on the doorstep of their fifth version - 5G. Summary of the invention

[0006] The present invention discloses systems, methods and means that can be associated with hybrid automatic repeat request acknowledgement (HARQ-ACK) transmission, for example, HARQ-ACK codebook adaptation associated with HARQ-ACK transmission.

[0007] According to some embodiments of the present invention, a device is disclosed, including: a processor, the processor being configured to: determine that a hybrid automatic repeat request confirmation (HARQ-ACK) codebook is scheduled to be transmitted in a first time slot, wherein a physical uplink control channel (PUCCH) resource indicator (PRI) is associated with the HARQ-ACK codebook; determine to discard the scheduled transmission of the HARQ-ACK codebook in the first time slot; determine a PUCCH resource set associated with the HARQ-ACK codebook; select resources from the PUCCH resource set based on at least the PRI; determine a transmission time; and transmit the HARQ-ACK codebook at the determined transmission time, wherein the transmission of the HARQ-ACK codebook at the determined transmission time is transmitted on the selected resources in a second time slot.

[0008] According to some embodiments of the present invention, a method is disclosed, including: determining that a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook is scheduled to be transmitted in a first time slot, wherein a physical uplink control channel (PUCCH) resource indicator (PRI) is associated with the HARQ-ACK codebook; determining to discard the scheduled transmission of the HARQ-ACK codebook in the first time slot; determining a PUCCH resource set associated with the HARQ-ACK codebook; selecting resources from the PUCCH resource set based at least on the PRI; determining a transmission time; and transmitting the HARQ-ACK codebook at the determined transmission time, wherein the transmission of the HARQ-ACK codebook at the determined transmission time is transmitted on the selected resources in a second time slot.

[0009] According to some embodiments of the present invention, a wireless transmit / receive unit (WTRU) is disclosed, comprising: a processor, the processor being configured to at least: determine that a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook is scheduled for transmission; receive an indication from a network device via semi-static signaling, wherein the indication indicates a pre-configured radio resource control (RRC) parameter to be used for transmission of the HARQ-ACK codebook, wherein the indication is a beta offset, and wherein the beta offset indicates a reserved index value; and transmit the HARQ-ACK codebook based on the beta offset.

[0010] According to some embodiments of the present invention, a wireless transmit / receive unit (WTRU) is disclosed, including: a processor, wherein the processor is configured to at least: determine that a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook is scheduled for transmission; and determine to discard at least a portion of the scheduled transmissions of the HARQ-ACK codebook.

[0011] The present invention discloses a device, such as a wireless transmit / receive unit (WTRU), which may be configured to have multiple physical uplink channels, such as a physical uplink control channel (PUCCH), in a time slot. Each physical uplink channel may have a corresponding HARQ-ACK codebook. In an example, the WTRU may determine that a first physical uplink channel and a second physical uplink channel overlap in a time slot. In this case, the WTRU may determine that a first HARQ-ACK codebook associated with the first physical uplink channel has a higher priority than a second HARQ-ACK codebook associated with the second physical uplink channel. The WTRU may transmit a first HARQ-ACK codebook on a first physical uplink channel in a time slot. The WTRU may transmit a portion of a second HARQ-ACK codebook in a time slot and transmit a portion of a second HARQ-ACK codebook in a subsequent time slot (e.g., a next time slot, a future time slot, etc.). For example, the WTRU may determine a first subcodebook of a second HARQ-ACK codebook and a second subcodebook of a second HARQ-ACK codebook. The WTRU may transmit a first subcodebook of a second HARQ-ACK codebook on a first physical uplink channel in a time slot and transmit a second subcodebook of the second HARQ-ACK codebook in a subsequent time slot (e.g., on a second physical uplink channel). The WTRU may transmit the first subcodebook of the second HARQ-ACK codebook using a non-overlapping portion of the second physical uplink channel (e.g., a portion / symbol of the second physical uplink channel that does not overlap with the first physical uplink channel in the time slot).

[0012] For example, the WTRU may autonomously determine to use the remaining symbols of the configured PUCCH for the discarded HARQ-ACK codebook transmission based on one or more of the following: the remaining symbols available for PUCCH; the HARQ-ACK codebook size; or the BLER target value / service type associated with the HARQ-ACK codebook.

[0013] The present invention discloses a WTRU that can be configured with a PUCCH resource set specific to a discarded HARQ-ACK codebook transmission, wherein one or more of the following items can apply: the PUCCH resource indication within the resource set can depend on the PRI of the discarded HARQ-ACK codebook transmission; or, the K1 timing can be associated with the timing used for the transmission and dynamically indicated to the WTRU.

[0014] The WTRU may use the configured grant / dynamic grant PUSCH for the discarded HARQ-ACK codebook transmission.The WTRU may autonomously determine which UL grant to use based on one or more of: the arrival timing of the grant; or a beta offset indication.

[0015] The WTRU may combine the remaining bits of the discarded HARQ-ACK codebook into the next codebook of the same service type / requirement. This may be based on the counter DAI and / or the total DAI step size. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented;

[0017] Figure 1B It is shown that according to one embodiment, Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within the communication system shown;

[0018] Figure 1C It is shown that according to one embodiment, Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used within the illustrated communication system;

[0019] Figure 1D It is shown that according to one embodiment, Figure 1A A system diagram of another exemplary RAN and another exemplary CN used in the communication system shown;

[0020] Figure 2 Overlapping HARQ-ACK codebooks are shown;

[0021] Figure 3 An example is shown associated with a WTRU configured with a PUCCH resource set for discarding a codebook;

[0022] Figure 4 An example associated with separating a discarded HARQ-ACK codebook into sub-codebooks is shown;

[0023] Figure 5 HARQ-ACK transmission on multiple PUCCH resources in a time slot for two TBs with different priorities is shown;

[0024] Figure 6 HARQ-ACK transmission on multiple PUCCH resources in a time slot for two different services is shown;

[0025] Figure 7 shows HARQ-ACK transmission on multiple PUCCH resources in time slots with different durations; and

[0026] Figure 8 HARQ-ACK transmission on multiple PUCCH resources in a slot with different RB offsets is shown. DETAILED DESCRIPTION

[0027] Figure 1A 1 is a schematic diagram illustrating 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 through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0028] 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, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include 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 operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0029] 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 that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

[0032] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. 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).

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

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

[0035] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example 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).

[0036] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rates for Evolution (EDGE), GSM EDGE (GERAN), etc.

[0037] Figure 1A The base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, 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 implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0038] 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, delay requirements, error 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 calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the specification, the CN 106 / 115 may be 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. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0039] 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 networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless 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, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0040] 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 via 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.

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

[0042] 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, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable 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, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0044] Although the transmit / receive element 122 is Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

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

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

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

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

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

[0050] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via hardware (e.g., choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In one embodiment, the WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous.

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

[0052] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-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 evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0053] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0054] 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. While each of the foregoing elements is depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

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

[0056] The SGW 164 may be connected to each of the evolved Node-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 perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

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

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

[0059] Although the WTRU Figures 1A to 1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments, such a terminal may (eg, temporarily or permanently) use a wired communications interface with a communications network.

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

[0061] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent by the AP, for example, wherein the source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between the source and destination STAs (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

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

[0063] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0064] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 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 non-continuous 80MHz channels (this can be called 80+80 configuration). For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be transmitted by transmitting STA. At the receiver of the receiving STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

[0065] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 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 may support instrument type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0066] WLAN systems that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only the 1MHz operating mode) is transmitting to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

[0067] 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. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

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

[0069] 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 utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) techniques. For example, the WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0070] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying absolute time lengths).

[0071] 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 while also not accessing other RANs (e.g., such as the evolved Node-Bs 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 anchor points. 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 WTRUs 102a, 102b, 102c may communicate or connect with the gNBs 180a, 180b, 180c while also communicating or connecting with other RANs, such as the eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-Bs 160a, 160b, 160c may serve as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0072] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0073] 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 possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

[0075] 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 configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

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

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

[0078] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU102a-d, base station 114a-b, evolved Node B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other device described herein. The simulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0080] The one or more simulation devices may perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. The one or more simulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) may be used by the simulation device to transmit and / or receive data.

[0081] New Radio (NR) technology may be associated with 3GPP. NR may support variable transmission duration / starting symbol and HARQ feedback timing. With variable transmission duration, a PDSCH or PUSCH transmission may, for example, occupy a contiguous set of symbols within a timeslot. With variable feedback timing, the DCI scheduling DL allocations may include an indication of the HARQ feedback timing to the WTRU, for example by pointing to one of the semi-statically configured HARQ timings. NR may support a dynamic HARQ-ACK codebook, where the size of the HARQ codebook may depend on the number of scheduled transport blocks (TBs). The gNB may use a counter downlink allocation index (DAI) and a total DAI in the DCI to indicate the number of previously scheduled TBs. The counter and the total DAI may have a size of 2 bits, for example, which may allow the WTRU to recover up to 4 missing TBs. In an example, NR Rel-15 may support a WTRU that transmits up to one HARQ-ACK codebook within a timeslot.

[0082] The reliability and / or latency of control signaling may have an impact on data transmission in the downlink and uplink. Uplink control information (UCI) with low reliability may increase the decoding error probability of downlink data transmission. For example, HARQ-ACK feedback with high BLER may result in a high probability of NACK to ACK or NACK / ACK loss detection. It may be supported, for example, that HARQ-ACK codebooks for different types of services may be transmitted separately even in the case of scheduled transmissions in the same time slot (e.g., to alleviate the problem). In an example, in the case of overlapping transmissions, the WTRU may discard one of the HARQ-ACK codebooks.

[0083] In the case where the WTRU is configured by the gNB to transmit multiple HARQ-ACK codebooks in overlapping symbols (e.g., in a limited power scenario), the WTRU may discard the HARQ-ACK codebook for service types that do not require low latency and / or high reliability. For example, the WTRU may support eMBB and URLLC, and at a given timeslot, the WTRU may be scheduled to transmit two HARQ-ACK codebooks for different types of services, which may overlap (e.g., partially or completely) within the timeslot. The WTRU may discard the eMBB HARQ-ACK codebook and give priority to the URLLC HARQ-ACK codebook. The eMBB ACK / NACK bits may not be available at the gNB. This may trigger unnecessary retransmissions of eMBB packets (e.g., transport blocks corresponding to the discarded HARQ-ACK codebook). On the WTRU side, the following issue may need to be addressed: how the HARQ-ACK codebook will be constructed considering that transmissions may need to be scheduled in subsequent timeslots. One or more features provided herein may be associated with reconstructing / adjusting the HARQ-ACK codebook, for example, in the event of a discard.

[0084] The term "codebook type" may refer to a HARQ-ACK codebook for services of the same type. For example, where the WTRU groups the ACK / NACK for eMBB TBs in one HARQ-ACK codebook, it may be referred to as codebook type 1. The ACK / NACK for URLLC TBs in another codebook may be referred to as codebook type 2.

[0085] There may be situations where multiple HARQ-ACK codebooks are configured for a WTRU. The multiple HARQ-ACK codebooks may correspond to different types of services and / or transmissions with different requirements. For example, for a URLLC type of service, the WTRU may be configured to maintain different HARQ-ACK codebooks depending on the BLER target value for the transmission. Examples may include the following: -6The target BLER value of URLLC transmission in different HARQ-ACK codebooks is 10 -5 URLLC transmission with a delay requirement of 0.5 ms can be confirmed using a different HARQ code from the URLLC transmission with a delay requirement of 1 ms; etc.

[0086] The discarded HARQ-ACK codebook may be transmitted in a subsequent time slot (e.g., a next time slot, a future time slot, etc.). In an example, this may include features associated with one or more of the following: transmitting the discarded HARQ-ACK codebook on a PUCCH resource; transmitting the discarded HARQ-ACK codebook using a PUSCH transmission; using HARQ-ACK (e.g., a new HARQ-ACK) timing to transmit the discarded HARQ-ACK; or, adjusting the HARQ-ACK codebook (e.g., combining the discarded HARQ-ACK codebook with the next HARQ-ACK codebook transmission of the same codebook type).

[0087] The WTRU may be configured to transmit the discarded HARQ-ACK codebook in a time slot different from the time slot on which the HARQ feedback is scheduled to be transmitted. For example, the WTRU may be configured to transmit the HARQ-ACK codebook in time slot n, and based on one of the triggers described herein, the WTRU may discard the transmission of the HARQ-ACK codebook. The WTRU may keep the A / N bits in its buffer for potential transmission in time slot n+k, where k>0.

[0088] The WTRU may be configured to transmit a discarded HARQ-ACK codebook on a resource (e.g., a PUCCH resource used as an example). The WTRU may be configured with a specific PUCCH resource set for transmitting the discarded HARQ-ACK codebook. Such a PUCCH resource set may be an additional resource set or specified from a resource set already configured for the WTRU. In an example, the WTRU may determine the PUCCH resources within the PUCCH resource set based on a PUCCH resource indicator (PRI) scheduled for the discarded HARQ-ACK codebook. The WTRU may use the same PRI to determine the PUCCH resources from the resource set. The WTRU may apply an offset to the PRI to determine the PUCCH resources from the resource set. The applied offset may depend on one or more of the following: the PRI of the prioritized HARQ-ACK codebook transmission; or, the HARQ-ACK timing of a subsequent attempt to transmit the discarded HARQ-ACK codebook.

[0089] Using the prioritized HARQ-ACK codebook transmitted PRI, the WTRU may have received an indication to transmit a first HARQ-ACK codebook with PRI1 and a second HARQ-ACK codebook with PRI2. The WTRU may discard the first codebook and transmit the second codebook. In a subsequent time slot, the WTRU may transmit the discarded codebook using a PUCCH resource with index PRI1+PRI2 from the PUCCH resource set configured for the discarded codebook.

[0090] Using the HARQ-ACK timing of subsequent attempts to transmit the discarded HARQ-ACK codebook, the WTRU may be configured to transmit the discarded HARQ codebook in N slots after the discard. The WTRU may use an index equal to PRI+F(N), where PRI is the indexed initial PUCCH resource indicating the discarded HARQ transmission, and F(.) is a function / mapping / table that relates HARQ timing to a PUCCH index offset.

[0091] The WTRU may be configured to transmit the discarded HARQ-ACK codebook using a PUSCH transmission. In an example, the WTRU may use a DCI-based grant to transmit the HARQ-ACK codebook. For example, the WTRU may use a UL grant received in the next time slot to transmit the discarded feedback. The WTRU may receive an explicit bit field in a DCI requesting transmission of the discarded HARQ codebook on the PUSCH, or autonomously determine that the UL grant should be used for the HARQ-ACK transmission. The WTRU may be configured with an RRC parameter, such as "betaOffsets", which supports a value that may be signaled by, for example, a "Beta_offsetindicator" field in DCI format 0_1, which may indicate that the WTRU needs to transmit the discarded HARQ codebook on the corresponding PUSCH. The WTRU may determine the UL grant for the HARQ-ACK codebook transmission based on one or a combination of the following items: the timing offset between the discarded HARQ codebook and the UL grant is less than a threshold; or, a scheduling request is not sent by the WTRU in the timing window before receiving the grant.

[0092] In the example, when the timing offset between the discarded HARQ codebook and the UL grant is less than a threshold, if the timing offset between the discarded HARQ codebook and the UL grant is less than a threshold, the timing offset between the discarded HARQ codebook and the UL grant is less than a threshold. 符号 After receiving a UL grant, the WTRU may use the uplink grant to transmit the HARQ-ACK codebook. In the example where a scheduling request is not sent by the WTRU in the timing window before receiving the grant, the WTRU may not have sent a scheduling request for uplink scheduling and / or its UL buffer is empty.

[0093] The WTRU may be configured to use a UL configured grant to transmit a discarded HARQ-ACK codebook. The WTRU may receive an indication from the network, wherein the configured grant to be used is from a set of pre-configured / RRC configured grants to be used for the discarded HARQ-ACK codebook transmission. The indication may be semi-statically or dynamically signaled using, for example, a DCI. The WTRU may be configured with an RRC parameter, such as "betaOffsets", which indicates one of the reserved index values ​​that is not mapped to a beta offset value for HARQ-ACK or CSI transmission on the PUSCH (e.g., not mapped to index values ​​19-31 in the RRC configuration of Table 1: beta offsets).

[0094] Table 1: RRC configuration for β offset

[0095]

[0096] The WTRU may be configured with a HARQ-ACK timing (e.g., a new HARQ-ACK timing) to transmit the discarded HARQ-ACK, which may be referred to as, for example, "HARQ timing to new HARQ timing". The granularity of "HARQ timing to new HARQ timing" may be configured in units of slots, subslots, or symbols. In an example, using RRC signaling, the WTRU may be configured with, for example, a mapping between a PDSCH to HARQ timing value and a HARQ timing to new HARQ timing value. Based on the PDSCH to HARQ timing originally scheduled for codebook transmission, and after discarding the codebook, the WTRU may use the configured mapping to determine the timing of the transmission.

[0097] In an example, the WTRU may autonomously determine the HARQ-ACK timing (eg, new HARQ timing) based on one or a combination of the following: control information associated with a discarded transmission; or control information associated with a prioritized transmission.

[0098] For control information related to discarded transmissions, one or more of the following items may apply. A search space configuration on which DCI (e.g., DCI that schedules at least one of the TBs associated with the discarded HARQ-ACK codebook) is received may be used. The search space configuration may include one or more of the following items: monitoring periodicity and duration; monitoring patterns within time slots; or search space indexes. A CORESET configuration on which DCI (e.g., DCI that schedules at least one of the TBs associated with the discarded HARQ-ACK codebook) is received may be used. The CORESET configuration may include one or more of the following items: a CORESET index; a CORESET duration; or a BWP associated with the CORESET. HARQ timing of discarded transmissions may be included.

[0099] For control information associated with prioritized transmissions, one or more of the following may apply. A search space configuration on which DCI (e.g., DCI that schedules at least one of the TBs associated with a prioritized HARQ-ACK codebook) is received may be used. The search space configuration may include one or more of the following: monitoring periodicity and / or duration; monitoring patterns within time slots; or search space indexes. A CORESET configuration on which DCI (e.g., DCI that schedules at least one of the TBs associated with a prioritized HARQ-ACK codebook) is received may be used. The CORESET configuration may include one or more of the following: a CORESET index; a CORESET duration; or a BWP associated with the CORESET. HARQ timing for prioritized transmissions may be included.

[0100] The WTRU may adjust the HARQ-ACK codebook. The WTRU may be configured to combine the discarded HARQ-ACK codebook with the next HARQ-ACK codebook transmission of the same codebook type. In an example, the WTRU may be configured to (e.g., dynamically) identify the codebook type. The WTRU may (e.g., if it receives a downlink assignment of the same type) use the PUCCH resource indication and the HARQ feedback timing indication to confirm the transmission (e.g., a new transmission) and / or the discarded HARQ-ACK codebook. For example, the WTRU may be configured to determine the codebook type based on a codebook identifier. In time slot n, the WTRU discards the HARQ-ACK codebook with a codebook identifier equal to k. In time slot n+1, the WTRU may receive a downlink assignment indicating PUCCH resources and HARQ timing in time slot n+4 and using a codebook identifier equal to k. The WTRU may adjust the HARQ-ACK codebook size (e.g., a new HARQ-ACK codebook size) to include the discarded HARQ-ACK codebook in time slot n.

[0101] In an example, the WTRU may be configured to identify whether the discarded HARQ-ACK codebook may be combined with the next HARQ-ACK codebook, for example based on the DAI and / or the counter DAI. The WTRU may be configured to interpret an increase step size above a threshold configured in the counter DAI and / or the total DAI as an indication to combine a transmission of ACK / NACK (e.g., a new transmission of ACK / NACK) with the discarded HARQ-ACK. For example, before the HARQ-ACK is discarded, the last counter DAI indication value received from the WTRU is 1. In the next allocation after the discard, the WTRU may receive a counter DAI and / or a total DAI with a value of 4. The WTRU may then determine that the next HARQ-ACK codebook may contain the discarded HARQ codebook.

[0102] The trigger may be used to discard the HARQ-ACK codebook. The WTRU may be configured to discard the HARQ-ACK codebook scheduled for transmission at a given time slot. The WTRU may be configured to discard the HARQ-ACK codebook at a given time slot based on one or a combination of the following: the HARQ-ACK codebook is overlapping with another uplink transmission (e.g., which has a higher priority than the HARQ-ACK codebook); or there is a power-limited scenario.

[0103] In the case where the HARQ-ACK codebook is overlapping with another uplink transmission having a higher priority than the HARQ-ACK codebook (e.g., another HARQ-ACK codebook as an example), the uplink transmission may include another HARQ-ACK codebook having a higher priority that may be scheduled for transmission on the PUCCH or PUSCH. In the example of a PUSCH transmission, the WTRU may be configured to transmit a URLLC type transmission via a PUSCH that overlaps with the HARQ-ACK codebook.

[0104] In an example associated with a power limited scenario, the WTRU may be configured with multiple overlapping transmissions and / or configured with a maximum transmit power (Pmax). The WTRU may determine that it cannot meet the BLER target value for one of the scheduled transmissions given the current path loss from the gNB.

[0105] The WTRU may be configured to determine the priority of the HARQ-ACK codebook based on the service type associated with the HARQ-ACK codebook and / or whether the HARQ-ACK codebook was discarded in a previous time slot. In an example, the WTRU may be configured to associate a priority with the HARQ-ACK codebook depending on at least the service type of a transport block associated with the HARQ codebook. The WTRU may keep adjusting the priority based on the state of the transmission. For example, after discarding the HARQ-ACK codebook, the WTRU may increase the priority of the discarded HARQ codebook transmission.

[0106] Figure 2 FIG. 4 shows overlapping HARQ-ACK codebooks in a time slot. Figure 2 As shown, PUCCH1 carrying HARQ-ACK codebook 1 may overlap (eg, at least partially overlap) with PUCCH2 carrying HARQ-ACK codebook 2. Figure 2 As shown, the WTRU may be configured with two overlapping HARQ-ACK codebooks in time slot n-3. Figure 2 and / or Figure 4 As shown, the WTRU may prioritize HARQ-ACK codebook 1, for example, codebook 1 over codebook 2, and discard the transmission of the portion of PUCCH2 that overlaps with PUCCH1. Figure 2 As shown, the WTRU may transmit the non-discarded portion of PUCCH2 that does not overlap with PUCCH1. The WTRU may determine the number of remaining symbols for PUCCH2 (e.g., Figure 2 The number of remaining symbols in the portion of PUCCH2 that does not overlap with PUCCH1 (eg, the non-overlapping portion of PUCCH2) shown is higher than a threshold (eg, a configured threshold). Figure 2 and / or Figure 4 As shown, the WTRU may (e.g., if the WTRU determines that the number of remaining symbols of PUCCH2 is above a threshold) separate the HARQ-ACK codebook 2 into two sub-codebooks. The WTRU may, for example, use the sub-codebooks in the time slot (e.g., Figure 2 The WTRU may determine whether a PUCCH resource set for the discarded HARQ-ACK codebook (e.g., a HARQ-ACK subcodebook, such as the second subcodebook or the full HARQ-ACK codebook) is configured (e.g., configured for a subsequent time slot, such as a next time slot, a future time slot, etc.). For example, Figure 2 , Figure 3 and / or Figure 4As shown, the WTRU may decide whether to allocate the UL grant for the discarded HARQ-ACK codebook transmission. In time slot n-2, for example, at the end of T from PUCCH2 符号 Starting thereafter, the WTRU may receive an UL grant. The WTRU may determine to transmit the second subcodebook of HARQ-ACK codebook 2 based on the uplink grant.

[0107] Figure 3 An example is shown associated with a WTRU configured with a PUCCH resource set with a codebook for discarding. Figure 3 As shown, the WTRU may be configured with a discarded HARQ-ACK codebook (e.g., a HARQ-ACK subcodebook such as Figure 2 The second subcodebook or the complete HARQ-ACK codebook). Figure 3 As shown, the WTRU may determine whether the WTRU is configured with a PUCCH resource set for a discarded HARQ-ACK codebook. If the WTRU is configured with a PUCCH resource set for a discarded HARQ-ACK codebook, the WTRU transmission may use PUCCH resources from the resource set by applying an offset to the PRI of the discarded HARQ-ACK codebook. The WTRU may determine the HARQ-ACK timing based on the timing indication of the discarded transmission. If the WTRU is not configured with a PUCCH resource set for a discarded HARQ-ACK codebook, the WTRU may use an UL grant to carry the discarded HARQ-ACK codebook.

[0108] Figure 4 An example associated with separating the discarded HARQ-ACK codebook into sub-codebooks is shown. Figure 4 As shown, the WTRU may be configured with overlapping PUCCHs for corresponding HARQ-ACK transmissions (e.g., corresponding HARQ-ACK codebooks). The WTRU may prioritize a HARQ-ACK codebook over another HARQ-ACK codebook (e.g., see Figure 2 The WTRU may determine the remaining amount of PUCCH symbols (e.g., non-overlapping portions of PUCCH that were not prioritized, such as Figure 2 If the value is above the threshold, the WTRU may separate the discarded HARQ-ACK codebook into two sub-codebooks (e.g., Figure 2 ). The WTRU may select the remaining symbols of the configured PUCCH (e.g., the portion of the configured PUCCH that does not overlap with the prioritized PUCCH, such as Figure 2The WTRU may transmit the first subcodebook in a subsequent time slot (e.g., a next time slot, a future time slot, etc.). The WTRU may transmit the second subcodebook (e.g., the remaining bits of the discarded HARQ-ACK codebook) in a subsequent time slot (e.g., a next time slot, a future time slot, etc.). For example, if the WTRU determines that the number of PUCCH symbols is below a threshold, the WTRU may transmit the bits of the discarded HARQ-ACK codebook (the complete subcodebook) in a subsequent time slot (e.g., a next time slot, a future time slot, etc.).

[0109] The WTRU may be configured to transmit the discarded HARQ-ACK codebook in the time slot on which it is scheduled to initially transmit the HARQ codebook. For example, the WTRU may be configured to transmit the HARQ-ACK codebook in time slot n, and based on one of the triggers listed herein, the WTRU may discard the transmission of the HARQ-ACK codebook. The WTRU may, for example, use the remaining non-overlapping symbols to transmit the A / N bits in the same time slot n.

[0110] There may be a trigger for transmitting the discarded HARQ-ACK codebook in the same timeslot. The WTRU may be configured to determine (e.g., autonomously) whether a portion of the codebook may be transmitted in the remaining non-overlapping symbols of the PUCCH. The WTRU may separate the HARQ-ACK codebook and may transmit a sub-codebook based on one or more of the following: a number of remaining symbols in the timeslot; the size of the discarded HARQ-ACK; the service type associated with the HARQ-ACK codebook; or the BLER requirement of the HARQ-ACK codebook.

[0111] The WTRU may be configured with a number of symbols and if the remaining symbols are higher than the configured number, the WTRU may transmit a portion of the HARQ-ACK codebook (eg, a sub-codebook) in the timeslot.

[0112] The PUCCH resources may be adjusted for transmission. Assuming that the WTRU is configured with two PUCCH resources for HARQ-ACK information transmission in a time slot, if the WTRU detects a first DCI and a second DCI indicating a first resource and a second resource, respectively, for a PUCCH transmission with corresponding HARQ-ACK information in the time slot, the WTRU may transmit the HARQ-ACK information according to one of the following items.

[0113] The WTRU may transmit higher priority HARQ-ACK information in a PUCCH resource with an earlier starting symbol in a time slot (e.g., the 10th symbol), and lower priority HARQ-ACK information in a PUCCH resource with a later starting symbol in a time slot (e.g., the 12th symbol). Figure 5 HARQ-ACK transmission on multiple PUCCH resources in a time slot for two TBs with different priorities is shown.

[0114] The WTRU may transmit HARQ-ACK information associated with a URLLC service in a PUCCH resource having an earlier starting symbol in a time slot (e.g., the nth symbol), and HARQ-ACK information associated with an eMBB service in a PUCCH resource having a later starting symbol in a time slot (e.g., n+2 symbols). Figure 6 HARQ-ACK transmission on multiple PUCCH resources in a timeslot for two different services is shown.

[0115] The WTRU may transmit HARQ-ACK information associated with low delay transmission in a PUCCH resource corresponding to a PUCCH format with a short duration (e.g., 1 to 2 symbols), and HARQ-ACK information associated with high delay tolerant transmission in a PUCCH resource corresponding to a PUCCH format with a long duration (e.g., 10 or 14 symbols). Figure 7 HARQ-ACK transmissions on multiple PUCCH resources in slots with different durations are shown.

[0116] If the PUCCH resources have the same PRB offset, starting symbol, and length, the WTRU may determine that the two PUCCH resources have different cyclic shift indices. In this case, the WTRU may apply a rule (e.g., an implicit rule) to establish an association between each received DCI and the corresponding PUCCH resource. The WTRU may assume that the PUCCH resource with the lowest cyclic shift index is used to transmit the HARQ-ACK information corresponding to the earlier received DCI, and the PUCCH resource with the highest cyclic shift index is used to transmit the HARQ-ACK information corresponding to the later received DCI.

[0117] If the PUCCH resources have the same starting symbol, cyclic shift index, and length, the WTRU resource may determine that the two PUCCH resources have different PRB offsets. In this case, the WTRU may apply a rule (e.g., an implicit rule) to establish an association between each received DCI and the corresponding PUCCH resource. The WTRU may assume that the PUCCH resource with the lowest PRB offset is used to transmit the HARQ-ACK information corresponding to the earlier received DCI or PDSCH, and the PUCCH resource with the highest PRB offset is used to transmit the HARQ-ACK information corresponding to the later received DCI or PDSCH. Figure 8 HARQ-ACK transmission on multiple PUCCH resources in a slot with different RB offsets is shown.

[0118] The A / N bits may be dropped from the HARQ-ACK codebook. The WTRU may adjust the size of the HARQ-ACK codebook so that a portion of the HARQ-ACK codebook may be transmitted in the remaining symbols of the configured PUCCH. The WTRU may separate the HARQ-ACK codebook and transmit a subset of the A / N bits of the HARQ-ACK codebook (e.g., which may be the first subcodebook). The WTRU may select a configured number of bits from the most significant bits or the least significant bits within the HARQ-ACK codebook. For example, the WTRU may have a 1, a2, ..., a N ACK / NACK bits. When dropping this transmission, the WTRU may still have k non-overlapping symbols for PUCCH transmission. The WTRU may transmit a portion of a HARQ-ACK codebook (e.g., which may be the first subcodebook) with M bits, such that M ≤ N, e.g., a1, a2, ... a M or a N-M+1 、a N-M+2 , …, a N The WTRU may be configured to determine the number M based on one or more of: the number of remaining symbols of the PUCCH that overlap with another uplink transmission; or the reliability requirement of the HARQ-ACK codebook transmission.

[0119] As described herein, the WTRU may be configured to transmit the remaining bits of the HARQ-ACK codebook in a subsequent time slot (eg, the next time slot, a future time slot, etc.).

[0120] If the PUSCH indicated by the DCI is overlapping with one of the multiple PUCCH resources used for HARQ-ACK transmission in the time slot, one or more of the following items may apply. The WTRU may transmit HARQ-ACK on the PUCCH resources that do not overlap with the PUSCH and may ignore the scheduling DCI corresponding to the other PUCCH resources or the PUCCH resources that overlap with the PUSCH. The WTRU may multiplex the HARQ-ACK with the transport block and transmit it on the PUSCH indicated by the DCI and may ignore the PUCCH resources or the scheduling DCI corresponding to the PUCCH resources. The WTRU may transmit HARQ-ACK on the PUCCH resources in response to the DCI format detection performed by the WTRU and may ignore the other PUCCH resources as well as the PUSCH. If the WTRU is using the configured UL grant for PUSCH transmission, the WTRU may ignore the PUSCH and may transmit HARQ-ACK on one of the PUCCH resources in response to the DCI format detection performed by the WTRU.

[0121] Although the features and elements of the present disclosure may take into account LTE, LTE-A, New Radio (NR) or 5G specific protocols, it should be understood that the solutions described herein are not limited to this scenario and are also applicable to other wireless systems.

[0122] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill 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 that is incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in 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 the software may be used to implement a radio frequency transceiver for the device described herein.

Claims

1. A device comprising: A processor, the processor being configured to: determining that a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook is scheduled to be transmitted in a first time slot, wherein a physical uplink control channel (PUCCH) resource indicator (PRI) is associated with the HARQ-ACK codebook; Determining to discard scheduled transmission of the HARQ-ACK codebook in the first time slot; Determining a PUCCH resource set associated with the HARQ-ACK codebook; selecting a resource from the PUCCH resource set based at least on the PRI; Determine the transmission time; as well as The HARQ-ACK codebook is transmitted at the determined transmission time, wherein the transmission of the HARQ-ACK codebook at the determined transmission time is transmitted on the selected resource in the second time slot.

2. The device according to claim 1, wherein: The HARQ-ACK codebook is a first HARQ-ACK codebook, and a second HARQ-ACK codebook is scheduled to be transmitted in the first time slot, wherein determining to discard the scheduled transmission of the first HARQ-ACK codebook in the first time slot is based on determining that a priority associated with the second HARQ-ACK codebook is higher than a priority associated with the first HARQ-ACK codebook.

3. The device according to claim 2, wherein: Determining that the second HARQ-ACK codebook has a higher priority than the first HARQ-ACK codebook includes determining that the second HARQ-ACK codebook has a lower delay requirement than the first HARQ-ACK codebook.

4. The device according to claim 2, wherein: Determining that the second HARQ-ACK codebook has a higher priority than the first HARQ-ACK codebook includes determining that the second HARQ-ACK codebook has a higher reliability requirement than the first HARQ-ACK codebook.

5. The device according to claim 2, wherein: The processor is configured to discard scheduled transmissions of the first HARQ-ACK codebook in the first time slot, and the determined transmission time is determined based on control information related to the discarded first HARQ-ACK codebook transmission.

6. The device according to claim 2, wherein: The determined transmission time is determined based on control information related to the scheduled transmission of the second HARQ-ACK codebook.

7. The device according to claim 2, wherein: The processor is configured to apply an offset to the PRI to determine the PUCCH resource set.

8. The device according to claim 7, wherein: The offset is based on a PRI associated with the second HARQ-ACK codebook.

9. A method comprising: determining that a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook is scheduled to be transmitted in a first time slot, wherein a physical uplink control channel (PUCCH) resource indicator (PRI) is associated with the HARQ-ACK codebook; Determining to discard scheduled transmission of the HARQ-ACK codebook in the first time slot; Determining a PUCCH resource set associated with the HARQ-ACK codebook; selecting a resource from the PUCCH resource set based at least on the PRI; Determine the transmission time; as well as The HARQ-ACK codebook is transmitted at the determined transmission time, wherein the transmission of the HARQ-ACK codebook at the determined transmission time is transmitted on the selected resource in the second time slot.

10. The method according to claim 9, wherein: The HARQ-ACK codebook is a first HARQ-ACK codebook, and a second HARQ-ACK codebook is scheduled to be transmitted in the first time slot, wherein determining to discard the scheduled transmission of the first HARQ-ACK codebook in the first time slot is based on determining that a priority associated with the second HARQ-ACK codebook is higher than a priority associated with the first HARQ-ACK codebook.

11. The method of claim 10, wherein determining that the second HARQ-ACK codebook has a higher priority than the first HARQ-ACK codebook comprises determining that the second HARQ-ACK codebook has a lower delay requirement than the first HARQ-ACK codebook.

12. The method according to claim 10, wherein: Determining that the second HARQ-ACK codebook has a higher priority than the first HARQ-ACK codebook includes determining that the second HARQ-ACK codebook has a higher reliability requirement than the first HARQ-ACK codebook.

13. The method of claim 10, further comprising discarding a scheduled transmission of the first HARQ-ACK codebook in the first time slot, and wherein the determined transmission time is determined based on control information related to the discarded first HARQ-ACK codebook transmission.

14. The method according to claim 10, wherein: The determined transmission time is determined based on control information related to the scheduled transmission of the second HARQ-ACK codebook.

15. The method of claim 10, further comprising applying an offset to the PRI to determine the PUCCH resource set.

16. The method according to claim 15, wherein: The offset is based on a PRI associated with the second HARQ-ACK codebook.

17. A wireless transmit / receive unit (WTRU), comprising: A processor configured to at least: Determining that a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook is scheduled for transmission; receiving an indication from a network device via semi-static signaling, wherein the indication indicates a pre-configured radio resource control (RRC) parameter to be used for transmission of a HARQ-ACK codebook, wherein the indication is a beta offset, and wherein the beta offset indicates a reserved index value; and The HARQ-ACK codebook is transmitted based on the β offset.

18. A wireless transmit / receive unit (WTRU), comprising: A processor configured to at least: Determining that a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook is scheduled for transmission; Determining to discard at least a portion of scheduled transmissions of the HARQ-ACK codebook.

Images