Downlink Control Information (DCI) for semi-persistent scheduling

Abstract

A wireless communication system and method are provided related to opportunities for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration. A first wireless communication device determines opportunities for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration. The first wireless communication device communicates with a second wireless communication device based on the determined opportunities.

Description

Technical Field

[0001] The present application relates to wireless communication systems including piggyback opportunities for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems are capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include multiple base stations (BSs), each of which simultaneously supports communication for multiple communication devices, which may also be referred to as user equipment (UE).

[0003] In order to meet the growing demand for extended mobile broadband connections, wireless communication technology is evolving from long-term evolution (LTE) technology to next-generation new radio (NR) technology, which may be referred to as the fifth generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability than LTE. NR is designed to operate on a wideband array, for example, from low bands below about 1 gigahertz (GHz) and from about 1 GHz to about 6 GHz mid-bands to high bands such as millimeter wave (mmWave) bands. NR is also designed to operate across different spectrum types (from licensed spectrum to unlicensed and shared spectrum). Spectrum sharing enables operators to opportunistically aggregate spectrum to dynamically support high-bandwidth services. Spectrum sharing can extend the benefits of NR technology to operating entities that may not have access to licensed spectrum.

[0004] Semi-persistent scheduling (SPS) can be configured on a downlink shared channel to support periodic downlink transmissions. SPS can avoid the use of a downlink control channel because periodic transmissions can be configured for SPS instead of dynamically scheduling separate transmissions using downlink control information (DCI) transmitted on a downlink control channel. However, SPS activation and changes to SPS configuration can be transmitted to the UE via downlink control information (DCI) on a downlink control channel, which can increase downlink control channel usage in the case of a large number of UEs each with an SPS configuration. Summary of the invention

[0005] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an extensive review of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in the form of an overview, as a preface to a more detailed description presented later.

[0006] For example, in one aspect of the present disclosure, a method of wireless communication includes: determining, by a first wireless communication device, a piggyback opportunity for communicating downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration, and communicating, by the first wireless communication device, the first communication with a second wireless communication device based on the determined piggyback opportunity.

[0007] In an additional aspect of the present disclosure, a first wireless communication device includes a processor configured to determine a piggyback opportunity for communicating DCI in an SPS configuration, and a transceiver configured to communicate the first communication with a second wireless communication device based on the determined piggyback opportunity.

[0008] In an additional aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon, the program code, when executed by a processor in a first wireless communication device, includes code for causing the first wireless communication device to perform the following operations: determine a piggyback opportunity for communicating DCI in an SPS configuration, and communicate the first communication with a second wireless communication device based on the determined piggyback opportunity.

[0009] In an additional aspect of the disclosure, a first wireless communication device includes means for determining a piggyback opportunity for communicating a DCI in an SPS configuration, and means for communicating the first communication with a second wireless communication device based on the determined piggyback opportunity.

[0010] When reading the following description of specific exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features and embodiments of the present invention will become apparent to those of ordinary skill in the art. Although the features of the present invention can be discussed with respect to certain embodiments and accompanying drawings below, all embodiments of the present invention may include one or more of the advantageous features discussed herein. That is, although one or more embodiments may be discussed as having certain advantageous features, one or more of these features may also be used according to the various embodiments of the present invention discussed herein. In a similar manner, although exemplary embodiments may be discussed below as device, system or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 A wireless communication network in accordance with some aspects of the present disclosure is shown.

[0012] Figure 2A is a timing diagram illustrating a transmission frame structure according to some aspects of the present disclosure.

[0013] Figure 2B A hybrid automatic repeat request (HARQ) communication scenario according to some aspects of the present disclosure is shown.

[0014] Figure 2C A multi-component carrier (multi-CC) communication scheme according to some aspects of the present disclosure is shown.

[0015] Figure 3 A multi-CC, semi-persistent scheduling (SPS) communication scheme according to some aspects of the present disclosure is shown.

[0016] Figure 4 is a block diagram of a user equipment (UE) according to some aspects of the present disclosure.

[0017] Figure 5 is a block diagram of an exemplary base station (BS) according to some aspects of the present disclosure.

[0018] Figure 6 An SPS communication scenario according to some aspects of the present disclosure is shown.

[0019] Figure 7 An SPS communication scenario according to some aspects of the present disclosure is shown.

[0020] Figure 8 An SPS communication scenario according to some aspects of the present disclosure is shown.

[0021] Fig. 9 An SPS communication scenario according to some aspects of the present disclosure is shown.

[0022] Fig.10 is a flow chart of a communication method according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0023] The specific embodiments described below in conjunction with the accompanying drawings are intended to be descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein can be practiced. For the purpose of providing a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some examples, well-known structures and components are shown in block diagram form to avoid making these concepts difficult to understand.

[0024] The present disclosure generally relates to wireless communication systems (also referred to as wireless communication networks). In various embodiments, the techniques and apparatus may be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global system for mobile communications (GSM) networks, 5th generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0025] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between a group of telecommunications associations that aims to define a globally applicable third generation (3G) mobile phone specification. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the development of wireless technologies in accordance with LTE, 4G, 5G, NR, etc., using a new and different set of radio access technologies or radio air interfaces for shared access to wireless spectrum between networks.

[0026] Specifically, 5G networks consider different deployments, different spectrums, and different services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to expand to cover (1) networks with ultra-high density (e.g., ~1M nodes / km) 2 ), ultra-low complexity (e.g., ~10s of bits / s), ultra-low energy (e.g., ~10+ years of battery life), and deep coverage to reach challenging locations for a large Internet of Things (IoT); (2) including mission-critical control, with strong security to protect sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1ms), and a wide range of mobile or immobile users; and (3) with enhanced mobile broadband, including very high capacity (e.g., ~10Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, 100+Mbps user experienced rates), and deep perception with advanced discovery and optimization.

[0027] 5G NR can be implemented to use an optimized OFDM-based waveform with scalable digital schemes and transmission time intervals (TTI); with a general, flexible framework to effectively multiplex services and functions through dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) design; and with advanced wireless technologies such as massive multiple-input, multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the digital scheme in 5G NR, including the scaling of subcarrier spacing, can effectively address the operation of different services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing can occur at 15kHz on bandwidths (BW) such as 5, 10, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing can occur at 30kHz on 80 / 100MHz BW. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, subcarrier spacing can occur at 60kHz over 160MHz BW. Finally, for various deployments using mmWave components to transmit with TDD at 28GHz, subcarrier spacing can occur at 120kHz over 500MHz BW.

[0028] 5G NR's scalable digital scheme implements scalable TTI for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long TTIs and short TTIs allows transmissions to start on symbol boundaries. 5G NR also considers a self-contained integrated subframe design with UL / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive UL / downlink, which can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current business needs.

[0029] Various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in a variety of forms, and any specific structure, function, or structure and function disclosed herein is merely representative and non-restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that an aspect disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice a method. In addition, other structures, functions, or structures and functions other than or different from one or more aspects set forth herein can be used to implement such a device or practice such a method. For example, a method can be implemented as a part of a system, device, device, and / or an instruction stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect can include at least one element of a claim.

[0030] Semi-persistent scheduling (SPS) can be configured on a physical downlink shared channel (PDSCH) to support periodic downlink transmission. SPS activation, SPS reactivation, reconfiguration or change of the SPS configuration, and other information related to the SPS configuration can be transmitted to the UE via downlink control information (DCI) on a physical downlink control channel (PDCCH). For example, the SPS configuration may be changed after becoming mismatched with the changing operating environment over a period of time. Mismatched SPS configurations may result in an increase in the number of dynamic grant retransmissions and / or SPS reactivations, each of which utilizes PDCCH resources. In addition, in a scenario with a large number of UEs with SPS configurations, the DCI associated with SPS may utilize a correspondingly large amount of PDCCH resources.

[0031] The present application describes a mechanism for carrying various types of DCI related to SPS configuration on SPS PDSCH transmission. For example, DCI about activating, reactivating, reconfiguring or otherwise changing SPS configuration can be carried on SPS PDSCH (i.e., carried on PDSCH in SPS configuration). In some aspects, DCI related to SPS configuration (such as modulation and coding scheme (MCS), zero power channel state information reference signal (ZP-CSI-RS) indicator, transmit power control (TPC), and physical uplink control channel (PUCCH) resource indicator (PRI) for transmitting confirmation and negative confirmation (ACK / NACK) related to SPS PDSCH) can be carried on SPS PDSCH transmission. In some aspects, information related to the retransmission of SPS PDSCH data (such as hybrid automatic repeat request (HARQ) identifier (ID), redundant version (RV) information and new data indicator (NDI)) can be carried on SPS PDSCH. In some aspects, information regarding the group ACK codebook used for early communication of SPS HARQ responses may be piggybacked on the SPS PDSCH transmission.

[0032] Various aspects of the present disclosure may provide several benefits. For example, the present disclosure includes communicating DCI associated with the SPS configuration on the PDSCH, which beneficially avoids the use of PDCCH resources, which can instead be used for dynamic authorization or transmitting other DCI to the UE. In addition, the SPS PDSCH provides power savings for the UE of the network because the UE can avoid monitoring or blind decoding the PDCCH for DCI. In addition, the present disclosure includes configuring SPS retransmissions in the SPS PDSCH, which beneficially avoids retransmissions using dynamic authorization based on PDCCH. In addition, the present disclosure includes configuring a group ACK codebook for early communication of SPS HARQ responses, which beneficially allows the BS to receive ACK / NACK from the UE early so that in the case of ACK, the HARQ process can be used to send new data. Utilizing the group ACK codebook also beneficially reduces the overhead associated with the HARQ response by configuring the UE to send a group of responses at a time. Thus, the present disclosure improves UE and network performance with respect to downlink and HARQ-based communications, beneficially providing higher data rates, higher capacity, better spectral efficiency, and increased reliability.

[0033] Figure 1A wireless communication network 100 according to some aspects of the present disclosure is shown. The network 100 may be a 5G network. The network 100 includes a plurality of base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. The BS 105 may be a station that communicates with the UE 115, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to this particular geographic coverage area of ​​the BS 105 and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0034] BS105 may provide communication coverage for macro cells or small cells (e.g., pico cells or femto cells) and / or other types of cells. Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells such as pico cells typically cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells such as femto cells also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access for UEs associated with the femto cells (e.g., UEs in a closed subscriber group (CSG), UEs for users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 In the example shown, BS105d and 105e are conventional macro BSs, while BS105a-105c are macro BSs capable of using one of three-dimensional (3D), full-dimensional (FD) or massive MIMO. BS105a-105c can utilize its higher-dimensional MIMO capability to utilize 3D beamforming in both elevation beamforming and azimuth beamforming to increase coverage and capacity. BS105f can be a small cell BS, which can be a home node or a portable access point. BS105 can support one or more (e.g., two, three, four, etc.) cells.

[0035] Network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.

[0036] UE 115 is dispersed throughout the wireless network 100, and each UE 115 can be fixed or mobile. UE 115 can also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc. UE 115 can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, UE 115 can be a device including a universal integrated circuit card (UICC). On the other hand, UE can be a device that does not include UICC. In some aspects, UE 115 that does not include UICC can also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the network 100. UE 115 can also be a machine that is specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. UE 115e-115h is an example of various machines configured for communication to access network 100. UE 115i-115k is an example of a vehicle equipped with a wireless communication device configured for communication to access network 100. UE 115 is capable of communicating with any type of BS, whether macro BS, small cell, etc. Figure 1 , a lightning graphic (e.g., a communication link) indicates wireless transmission between UE 115 and a serving BS 105 (which is a BS designated to serve UE 115 on a downlink (DL) and / or uplink (UL)), or indicates desired transmission between BS 105, backhaul transmission between BSs, or sidelink transmission between UE 115.

[0037] In operation, BS 105a-105c uses 3D beamforming and cooperative spatial technology (e.g., coordinated multi-point (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro BS 105d can perform backhaul communications with BS 105a-105c and small cell BS 105f. Macro BS 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber Alerts or Gray Alerts.

[0038] The BS 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communications with the UE 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., through the core network) via a backhaul link (e.g., X1, X2, etc.), which may be a wired or wireless communication link.

[0039] The network 100 may also support mission-critical communications with ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e and a link from a small cell BS 105f. Other machine-type devices, such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device) may communicate directly with a BS (e.g., small cell BS 105f and macro BS 105e) through the network 100, or in a multi-step configuration by communicating with another user device that relays its information to the network (e.g., UE 115f transmits temperature measurement information to a smart meter (UE 115g), which then reports it to the network through the small cell BS 105f). The network 100 may also communicate via dynamic, low-latency TDD / FDD (e.g., between UE 115i,

[0040] V2V, V2X, C-V2X communications between UE 115j or 115k and other UEs 115, and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j or 115k and BS 105 to provide additional network efficiency.

[0041] In some embodiments, the network 100 communicates using an OFDM-based waveform. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, frequency bands, etc. Each subcarrier can be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI can be scalable.

[0042] In some aspects, BS 105 may assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS 105 to UE 115, while UL refers to the transmission direction from UE 115 to BS 105. Communications may be in the form of radio frames. A radio frame may be divided into a plurality of subframes or time slots, e.g., about 10. Each time slot may be further divided into mini-time slots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In TDD mode, UL and DL transmissions occur in different time periods using the same frequency band. For example, a subset of subframes in a radio frame (e.g., DL subframes) may be used for DL ​​transmissions, and another subset of subframes in a radio frame (e.g., UL subframes) may be used for UL transmissions.

[0043] The DL subframe and the UL subframe may be further divided into several regions. For example, each DL or UL subframe may have a predefined region for transmitting reference signals, control information, and data. A reference signal is a predetermined signal that facilitates communication between BS 105 and UE 115. For example, a reference signal may have a specific pilot pattern or structure, wherein a pilot tone may span an operating BW or frequency band, and each pilot tone may be located at a predefined time and a predefined frequency. For example, BS 105 may send a cell-specific reference signal (CRS) / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate a DL channel. Similarly, UE 115 may send a sounding reference signal (SRS) to enable BS 105 to estimate an UL channel. Control information may include resource allocation and protocol control. Data may include protocol data and / or operational data. In some aspects, BS 105 and UE 115 may communicate using a self-contained subframe. A self-contained subframe may include a portion for DL ​​communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a duration for DL ​​communication that is longer than a duration for UL communication. A UL-centric subframe may include a duration for UL communication that is longer than a duration for DL ​​communication.

[0044] In some aspects, network 100 may be an NR network deployed on a licensed spectrum. BS 105 may send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in network 100 to achieve synchronization. BS 105 may broadcast system information associated with network 100 (e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to achieve initial network access. In some instances, BS 105 may broadcast PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) on a physical broadcast channel (PBCH), and may broadcast RMSI and / or OSI on a physical downlink shared channel (PDSCH).

[0045] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting the PSS from the BS 105. The PSS may enable synchronization of period timing and may indicate a physical layer identity value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identity value that may be combined with the physical layer identity value to identify the cell. The PSS and SSS may be located in the center portion of the carrier or at any suitable frequency within the carrier.

[0046] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (PDCCH) monitoring, physical UL control channel (PUCCH), physical UL shared channel (PUSCH), power control, and SRS.

[0047] After obtaining the MIB, RMSI and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL authorization, a temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105, and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, the RAR, the connection request, and the connection response may be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may send a random access preamble and a connection request in a single transmission, and the BS 105 may respond by sending a random access response and a connection response in a single transmission.

[0048] After the connection is established, the UE 115 and the BS 105 may enter a normal operation phase, in which operational data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL ​​communications. The BS 105 may send an UL and / or DL ​​scheduling grant to the UE 115 via the PDCCH. The scheduling grant may be sent in the form of DL control information (DCI). The BS 105 may send a DL communication signal (e.g., carrying data) to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may send an UL communication signal to the BS 105 via the PUSCH and / or PUCCH according to the UL scheduling grant.

[0049] In some aspects, the network 100 may operate on a system BW or a component carrier (CC) BW. The network 100 may divide the system BW into multiple BWPs (e.g., parts). The BS 105 may dynamically assign the UE 115 to operate on a certain BWP (e.g., a certain part of the system BW). The assigned BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP to find signaling information from the BS 105. The BS 105 may schedule the UE 115 to perform UL or DL ​​communications in the active BWP. In some aspects, the BS 105 may assign a pair of BWPs within the CC to the UE 115 for UL and DL communications. For example, the BWP pair may include a BWP for UL communication and a BWP for DL ​​communication.

[0050] In some aspects, network 100 may include BS 105 (or BSs 105, for example) communicating downlink information in an SPS configuration. Figure 2B BS214, Figure 6 BS 500) and UE 115 (or for example Figure 2B US215, Figure 5 UE 400). In some aspects, the network 100 and / or BS 105 can configure the SPS configuration using periodic PDSCH transmissions and retransmissions from BS 105 to UE 115. In some aspects, BS 105 and UE 115 can also communicate via PDCCH, PUCCH, PUSCH channels, etc. In some aspects, UE 115 can transmit a confirmation or negative confirmation to BS 105 on PUCCH as to whether the UE has received the SPS PDSCH transmission. In some aspects, the network 100 and / or BS 105 can configure UE 115 to transmit DCI about SPS configuration (e.g., reactivation, MCS, TPC, ZP-CSI-RS triggering) to BS 105 by carrying DCI on SPS PDSCH.

[0051] Figure 2A 2 is a timing diagram illustrating a transmission frame structure 200 according to some embodiments of the present disclosure. The transmission frame structure 200 may be used by a BS (such as BS 105) and a UE (such as UE 115) in a network (such as network 100) for communication. Specifically, the BS may communicate with the UE using the time-frequency resources configured as shown in the transmission frame structure 200. Figure 2A , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. Transmission frame structure 200 includes radio frame 201. The duration of radio frame 201 may vary depending on the embodiment. In an example, radio frame 201 may have a duration of approximately ten milliseconds. Radio frame 201 includes M time slots 202, where M may be any suitable positive integer. In an example, M may be approximately 10.

[0052] Each time slot 202 includes a number of subcarriers 204 in frequency and a number of symbols 206 in time. The number of subcarriers 204 and / or the number of symbols 206 in the time slot 202 may vary according to the embodiment, for example, based on the channel bandwidth, subcarrier spacing (SCS) and / or CP mode. One subcarrier 204 in frequency and one symbol 206 in time form one resource element (RE) 210 for transmission.

[0053] BS (e.g. Figure 1 BS 105 in the example may schedule UEs (eg, Figure 1UE 115 in the UE 115) performs UL and / or DL ​​communication. Each time slot 202 can be divided into K mini-time slots 208. Each mini-time slot 208 can include one or more symbols 206. The mini-time slots 208 in the time slot 202 can have variable lengths. For example, when the time slot 202 includes N symbols 206, the mini-time slot 208 can have a length between one symbol 206 and (N-1) symbols 206. In some embodiments, the mini-time slot 208 can have a length of about two symbols 206, about four symbols 206, or about seven symbols 206.

[0054] Figure 2B A hybrid automatic repeat request (HARQ) communication scenario according to some aspects of the present disclosure is shown. The functionality of scenario 250 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other appropriate components) or other appropriate means of a wireless communication device. Scenario 250 may correspond to a HARQ communication scenario in network 100. In some aspects, such as Figure 2B UE 115, UE 215 or Figure 4 The wireless communication device of UE 400 may utilize one or more components such as processor 402, memory 404, SPS module 408, transceiver 410, modem 412, and one or more antennas 416 to perform the steps of scenario 250. Figure 2B Base station (BS) 105, BS214 or Figure 5 The wireless communication device of BS 500 may utilize one or more components such as processor 502, memory 504, SPS module 508, transceiver 510, modem 512, and one or more antennas 516 to perform the steps of scenario 200. Scenario 250 may be implemented as follows: Figure 1-2A Similar mechanisms as described in 2C-10. Figure 2B In , the x-axis represents time in some arbitrary unit. Figure 2A The scene 250 is described by a substantially similar transmission frame structure, and for simplicity, the same Figure 2A The same reference numerals are used in the drawings.

[0055] In scenario 250, BS 214 (or, for example, Figure 5 BS 105, BS 500) can use HARQ to communicate with UE 215 (or, for example, Figure 4UE 115, UE 400) communicates DL data. For HARQ communication, a sending node (e.g., BS214) may send data to a receiving node (e.g., BS214). The receiving node may provide feedback to the sending node about the reception status of the data. For example, the receiving node may send an ACK to the sending node to indicate successful decoding of the data. Conversely, the receiving node may send a NACK to the sending node to indicate a failure to decode the data. When the sending node receives an ACK from the receiving node, the sending node may send new data in subsequent transmissions. However, when the sending node receives a NACK from the receiving node, the sending node may retransmit the same data to the receiving node. In some aspects, the sending node may send the same coded version of the data in the initial transmission and the retransmission. In some aspects, the sending node may send different coded versions of the data in the initial transmission and the retransmission. In some aspects, the receiving node may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. To simplify the discussion and illustration, Figure 2B The HARQ communication is shown in the context of DL data communication, although similar HARQ mechanisms may be applied to UL data communication.

[0056] In the example, BS214 includes a HARQ component 211. The HARQ component 211 is configured to perform multiple parallel HARQ processes 212 for DL ​​data communication. The HARQ processes 212 can operate independently of each other. That is, for each HARQ process at BS214 and UE 215, ACK, NACK and / or retransmission are determined and processed separately. Each HARQ process 212 can be identified by a HARQ process ID. For example, the HARQ process 212 can be identified by an identifier H1, H2, ..., Hn. BS214 can communicate with UE 215 in units of time slots 202. Time slots 202 are shown as S1, S2, ..., S8. BS214 can configure multiple potential transmission opportunities 222 (e.g., PDSCH transmission opportunities) for UE 215 in time slots 202. That is, BS214 can potentially send DL communication signals to UE 215 in each transmission opportunity 222. Accordingly, UE 215 may monitor DL ​​transmissions from BS 214 in each transmission opportunity 222 .

[0057] To simplify the discussion, Figure 2BHARQ transmissions for one HARQ process H1 212 are shown, but it will be appreciated that embodiments of the present disclosure may be extended to more HARQ processes 212 (e.g., 2, 3 to 16 or more). As shown, BS 214 sends a scheduling grant 220a (e.g., via PDCCH) in time slot S2 202. The scheduling grant 220a may be sent as a PDCCH DCI. The scheduling grant 220a indicates scheduling for a data block 230 (e.g., PDSCH data) in time slot S2 202. In some examples, the scheduling grant 220a may additionally indicate resources for sending HARQ feedback for the data block 230 (e.g., in time slot S3 202). Subsequently, BS 214 sends the data block 230 (e.g., via PDSCH) according to the schedule. The data block 230 may be in the form of a transport block (TB). The TB may include an encoded medium access control (MAC) layer packet data unit (PDU) containing information bits. For example, UE 215 successfully receives and decodes data block 230. Therefore, UE 215 sends ACK 240 (labeled as A) to BS 214 in time slot S3 202 to indicate successful decoding of data block 230.

[0058] After receiving the ACK 240, the BS 214 sends a scheduling grant 220b to schedule the UE 215 for the new data block 232 in the time slot S4 202. The scheduling grant 220b may additionally indicate resources in the time slot S5 202 for sending HARQ feedback for the data block 232. For example, the UE 215 receives the data block 232, but fails to decode the data block 232. Therefore, the UE 215 sends a NACK 242 (labeled as N), for example, in the time slot S5 202 to indicate the reception failure of the data block 232.

[0059] Upon receiving NACK 242, BS 214 sends scheduling grant 220c to schedule UE 215 for retransmission of data block 232 in time slot S6 202. BS 214 retransmits data block 232 in time slot S6 202. Retransmitted data block 232 is shown as 232b. In some aspects, retransmitted data block 232b may be the same as initial data block 232. In some aspects, retransmitted data block 232b may carry the same information bits as initial data block 232, but may include a different coded version than initial data block 232. UE 215 fails to detect scheduling grant 220c, and therefore may not send an ACK or NACK for data block 232b (shown by the crossed symbols in time slot S7 202). When no ACK or NACK for data block 232b is received, BS 214 may retransmit data block 232 again. BS 214 may retransmit data block 232 multiple times until UE 215 correctly receives data block 232 or until a certain retransmission limit is reached. As can be observed from scenario 200, DL communication errors (e.g., where UE 215 fails to detect and / or decode PDCCH or PDSCH) may be corrected through HARQ retransmissions.

[0060] Figure 2C A multi-CC communication scenario 260 according to some aspects of the present disclosure is shown. Scenario 260 may be used by a BS (such as BS 105) and a UE (such as UE 115) in a network (such as network 100) for communication. Specifically, the BS may configure a PDCCH search space for the UE in multiple CCs, and may activate or deactivate the PDCCH search space in a CC, as shown in scenario 260. Figure 2C In , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. For the purpose of simplifying illustration and discussion, Figure 2C Two CCs are shown: a primary CC (PCC) 265 and a secondary CC (SCC) 266. However, it will be appreciated that embodiments of the present disclosure may be extended to more CCs (eg, 3, 4, 5, 6, or more).

[0061] PCC 265 and SCC 266 may be in any suitable frequency range (e.g., FR1 and / or FR2). PCC 265 may be referred to as an anchor CC, and SCC 266 may be referred to as a non-anchor CC. An anchor PCC 265 may always be active and may process control signaling and / or data communications. Non-anchor SCC 266 may be activated or deactivated based on need (e.g., to improve data throughput and / or reliability). The BS may configure a PDCCH search space for a UE in PCC 265 and / or SCC 266 within a time period 268. Time period 268 includes multiple transmission time slots 202 or transmission time intervals (TTIs) on PCC 265 and SCC 266. Each time slot 202 may span any suitable duration. In some examples, each time slot 202 may have a duration of approximately 1 ms. The search space may define certain time-frequency resources in which a BS may send DL control information (DCI) (e.g., carrying scheduling information). The UE may monitor the search space for DCI from the BS.

[0062] The BS may activate or deactivate a search space. At time T0, the BS activates a PDCCH search space in the PCC 265 (shown as active search space 270) and deactivates a PDCCH search space in the SCC 266 (shown as inactive search space 272). At time T1, the BS activates the search space in the SCC 266, as indicated by arrow 292. At time T2, the BS deactivates the search space in the SCC 266, as indicated by arrow 296. The activation and / or deactivation of the SCC 266 may be based on channel conditions and / or traffic load and / or throughput requirements in the PCC 265 and / or SCC 266.

[0063] The BS may send a PDCCH signal 282 in the active search space 270 to schedule the UE for UL and / or communications. For example, the BS may send a PDCCH signal 282 in slot n0 202 via the PCC 265 to schedule PDSCH 280 communications on the PCC 265 in slot n1 202 (as indicated by arrow 290). Similarly, after activating the search space in the SCC 266, the BS may send a PDCCH signal 282 in slot n2 202 via the SCC 266 to schedule PDSCH 280 communications on the SCC 266 in slot n2+1 202 (as indicated by arrow 294).

[0064] In some instances, time period 268 may correspond to an on-duration of a connected mode-discontinuous reception (C-DRX) cycle. C-DRX is a power saving technique in which a BS may configure a UE to cycle through a sleep-wake cycle or an on-off duration, wherein the UE is not expected to monitor transmissions from the BS during the off duration or the sleep duration. In some other instances, time period 268 may be a time period during a connection when C-DRX is not used. Dynamic deactivation of a search space in a CC may allow power savings at the UE regardless of whether C-DRX is enabled for the UE.

[0065] Figure 3 A multi-CC, semi-persistent scheduling (SPS) communication scenario 300 according to some aspects of the present disclosure is shown. Scenario 300 may be used by a BS (such as BS 105) and a UE (such as UE 115) in a network (such as network 100) for communication. Specifically, the BS may configure multiple CCs for the UE for communication with hybrid automatic request to provide high communication reliability, as shown in scenario 300. Figure 3 In this example, the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. To simplify the illustration and discussion, Figure 3 Two frequency bands (band 310 and band 312) and four CCs (CC1 320 and CC2 322 in band 310 and CC3 324 and CC4 326 in band 310) are shown. However, it will be appreciated that embodiments of the present disclosure may be extended to any suitable number of CCs (e.g., 2, 3, 5, or more) in any suitable number of frequency bands (e.g., 1, 3, 4, or more). Figure 2C Scenario 260 may be used in conjunction with scenario 300 to configure, activate and / or deactivate PDCCH search spaces (eg, search spaces 270 and 272 ) in CC1 320 , CC2 322 , CC3 324 , and / or CC4 326 .

[0066] Frequency bands 310 and 312 may be within any suitable frequency range and may be configured for transmissions utilizing any suitable subcarrier spacing (SCS). In some instances, frequency band 310 may correspond to FR2 (e.g., between approximately 24 GHz and 56 GHz) and frequency band 312 may correspond to FR1 (e.g., sub-6 GHz frequencies). Transmissions in frequency band 310 may use an SCS of approximately 120 kHz, while transmissions in frequency band 312 may use an SCS of approximately 60 kHz. The BS may configure an active CC set including CC1 320, CC2 322, CC3 324, and CC4 326 for the UE during time period 301. Time period 301 includes multiple transmission time slots 302, which may be substantially similar to time slot 202. Time period 301 may also be referred to as a transmission cycle. Time period 301 may have any suitable duration. In some instances, time period 301 may have a duration of approximately 1 ms. For purposes of simplifying illustration and discussion, Figure 3 Eight time slots 302 are shown, shown as S0 to S7. However, it will be appreciated that embodiments of the present disclosure may extend to any suitable number of time slots 302 (e.g., 2, 3, 4, 5, 6, 7, 9, 10, or more) or other time units (e.g., subframes, frames, arbitrary units) in time period 301.

[0067] In some aspects, the BS may utilize SPS to schedule UEs for DL ​​data transmission (e.g., PDSCH transmission). SPS may be used for a certain data stream. SPS may include specific allocations (e.g., time-frequency resources or RBs) according to a specific period. The BS may determine SPS based on a known business pattern of the data stream. For example, in an industrial IoT (IIOT) scenario, IOT devices may upload measurement readings or reports to a network server at a preconfigured time. The BS may schedule SPS resources on multiple CCs to provide high communication reliability. For example, the BS may configure periodic SPS resources for the UE in one or more of CC1 320, CC2 322, CC3 324, and CC4 326. The UE may monitor PDSCH transmissions from the BS based on the configured SPS resources.

[0068] like Figure 3As shown, SPS resources 306 are configured for time slot S0 302 in CC1 320. The BS may configure SPS resources 306 during a previous transmission cycle or time period before time period 301. The BS may send a PDSCH data block 330a to the UE in the SPS resource 306. The PDSCH data block 330a may be sent in the form of TBs. The transmission of the PDSCH data block 330a in the SPS resource 306 may be referred to as a configured transmission, in which no dynamic scheduling DCI is used for scheduling. The PDSCH data block 330a may be associated with a HARQ process.

[0069] The UE may monitor the SPS resources 306 based on the SPS configuration to look for PDSCH transmissions from the BS. Upon receiving the PDSCH data block 330a, the UE may provide the BS with a reception status of the PDSCH data block 330a. For example, the UE fails to decode the PDSCH data block 330a and may therefore send a NACK to the BS. The configuration of the SPS resources 306 may indicate resources for corresponding ACK / NACK transmissions. For example, the ACK / NACK resources for the SPS resources 306 are located in time slot S1 302. Therefore, the UE may send a PUCCH signal 334a indicating a NACK for the PDSCH data block 330a in time slot S1 302. The NACK may be sent in the form of UCI.

[0070] Upon receiving the NACK, the BS may schedule a retransmission of the PDSCH data block 330a. The BS may schedule the retransmission in another CC that is more reliable than the CC used for the initial transmission. For example, the initial transmission may be performed on a mmWave band that may be susceptible to signal blocking, while the retransmission may be performed on a sub-6 GHz band that may be more reliable. Figure 3 As shown, the BS schedules retransmissions in CC3 324 during time slot S3 302. The BS may send a PDCCH signal 332 (in the form of a DCI) in time slot S3 302 indicating the retransmission schedule. In some aspects, the PDCCH signal 332 and the retransmission schedule may be associated with a dynamic grant for downlink communications. The BS may retransmit the PDSCH data block 330a according to the retransmission schedule. The retransmission is shown as 330b. The retransmission 330b may include the same TB as the PDSCH data block 330a.

[0071] In some instances, the TBs may be segmented into code block groups (CBGs), and the UE may provide a separate ACK / NACK for each CBG. However, CBG segmentation may not be allowed when the retransmission is in a different CC from the initial transmission. For example, the TB in the PDSCH data block 330a is segmented into three CBGs, and the UE fails to decode only one of these CBGs. For retransmissions on CC3 324, the BS may retransmit the entire TB instead of just the failed CBG, because the UE may not know that the successfully decoded CBG received in CC1 320 and the retransmitted CBG in CC3 324 belong to the same TB.

[0072] The UE may monitor the PDCCH signal 332 based on a pre-configured search space (e.g., active search space 220) in time slot S3 302. Upon detecting a retransmission schedule in the PDCCH signal 332, the UE may receive the PDSCH data block 330b based on the retransmission schedule. The UE may perform demodulation and decoding to recover the data in the PDSCH data block 330b. For example, the UE successfully decodes the PDSCH data block 330b. Therefore, the UE may send a PUCCH signal 334b ​​indicating an ACK in time slot S7 302.

[0073] In some aspects, the BS may configure SPS resources in each of the active CC1 320, CC2 322, CC3 324, and CC4 326, and may send PDSCH transmissions in the most reliable CC. Therefore, the UE may be required to monitor and / or demodulate all active CC1 320, CC2 322, CC3 324, and CC4 326 to search for DL ​​transmissions from the BS. Similarly, the UE may be required to monitor and / or demodulate all active CC1 320, CC2 322, CC3 324, and CC4 326 to search for PDCCH decoding (e.g., DCI) because the BS may schedule transmissions in any of the active CC1 320, CC2 322, CC3 324, and CC4 326 based on channel conditions. In addition, the UE may be configured with a configured grant or resource for UL transmissions in one or more of CC1 320, CC2 322, CC3 324, and CC4 326. The BS may schedule the UE with a retransmission schedule when it fails to decode an UL transmission. The UL retransmission schedule may be in any one of CC1 320, CC2 322, CC3 324, and CC4 326, similar to the DL retransmission schedule. Therefore, the UE may be required to monitor all active CC1 320, CC2 322, CC3 324, and CC4 326. Thus, for each DL transmission opportunity including SPS resources and / or PDCCH search space, the UE may be required to monitor and / or demodulate all active CC1 320, CC2 322, CC3 324, and CC4 326.

[0074] Accordingly, the present disclosure provides techniques for determining a piggyback opportunity for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration. The present disclosure also provides techniques for configuring SPS retransmissions in an SPS configuration via piggyback DCI.

[0075] Figure 4 4 is a block diagram of an exemplary UE 400 according to some aspects of the present disclosure. For example, UE 400 may be the Figure 1 1. As shown, UE 400 may include a processor 402, a memory 404, an SPS module 408, a transceiver 410 including a modem subsystem 412 and a radio frequency (RF) unit 414, and one or more antennas 416. These elements may communicate with each other directly or indirectly, for example, via one or more buses.

[0076] The processor 402 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 402 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0077] The memory 404 may include cache memory (e.g., cache memory of the processor 402), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one embodiment, the memory 404 includes a non-transitory computer-readable medium. The memory 404 may store or have recorded thereon instructions 406. The instructions 406 may include instructions that, when executed by the processor 402, cause the processor 402 to perform the various embodiments described herein with reference to the UE 115 in conjunction with the present disclosure (e.g., Figure 2A-3 Instructions 406 may also be referred to as program code. The program code may be used to cause the wireless communication device to perform the operations, for example, by causing one or more processors (such as processor 402) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be broadly interpreted to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, processes, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

[0078] The SPS module 408 may be implemented via hardware, software, or a combination thereof. For example, the SPS module 408 may be implemented as a processor, circuit, and / or instructions 406 stored in the memory 404 and executed by the processor 402. In some examples, the SPS module 408 may be integrated within the modem subsystem 412. For example, the SPS module 408 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 412. In some examples, the UE may include one or more SPS modules 408.

[0079] The SPS module 408 can be used in various aspects of the present disclosure, for example, Figure 2A-3and aspects of 6-10. The SPS module 408 is configured to communicate downlink information based on the SPS configuration. The SPS module 408 is also configured to determine a piggyback opportunity for communicating DCI in the SPS configuration. The SPS module 408 is also configured to determine a HARQ process associated with a retransmitted SPS PDSCH communication. The SPS module 408 is also configured to communicate communications associated with piggyback opportunities, including piggyback DCI on the PDSCH or ACK / NACK on the PUCCH. The SPS module 408 is also configured to associate one or more piggyback opportunities with the SPS configuration based on radio resource control (RRC) information, a medium access control control element (MAC-CE), or an SPS activation DCI. The SPS module 408 is also configured to receive and process piggyback DCI associated with the MAC-CE. The SPS module 408 is also configured to receive and process piggyback DCI on the SPS PDSCH, including, for example, a physical uplink channel (PUCCH) resource indicator (PRI) associated with a block acknowledgment configuration of the SPS configuration.

[0080] As shown, the transceiver 410 may include a modem subsystem 412 and an RF unit 414. The transceiver 410 may be configured to communicate bidirectionally with other devices, such as the BS 105. The modem subsystem 412 may be configured to modulate and / or encode data from the memory 404 and / or the SPS module 408 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 414 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., PUCCH, PUSCH, UCI, ACK / NACK, group ACK / NACK, CG uplink transmission, channel report, SRS) from the modem subsystem 412 (on outbound transmissions) or from another source (such as a UE 115 or BS 105). The RF unit 414 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 410, the modem subsystem 412 and the RF unit 414 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.

[0081] The RF unit 414 may provide modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to the antenna 416 for transmission to one or more other devices. The antenna 416 may also receive data messages sent from other devices. The antenna 416 may provide the received data messages for processing and / or demodulation at the transceiver 410. The transceiver 410 may provide the demodulated and decoded data (e.g., broadcast channel, DL data block, CC configuration, PDSCH, PDCCH, DCI, MCS, TPC, CSI-RS, ZP CSI-RS trigger, SPS configuration, SPS PDSCH, MAC-CE, group ACK codebook, dynamic grant (DG) configuration, configured grant (CG) configuration, DG PDCCH, reference signal) to the SPS module 408 for processing. The antenna 416 may include multiple antennas of similar or different designs to maintain multiple transmission links. The RF unit 414 may configure the antenna 416.

[0082] In one embodiment, the UE 400 may include multiple transceivers 410 that implement different RATs (e.g., NR and LTE). In one embodiment, the UE 400 may include a single transceiver 410 that implements multiple RATs (e.g., NR and LTE). In one embodiment, the transceiver 410 may include various components, where different combinations of components may implement different RATs.

[0083] Figure 5 is a block diagram of an exemplary BS 500 according to some aspects of the present disclosure. For example, BS 500 may be as described above in Figure 1 As shown, BS 500 may include a processor 502, a memory 504, an SPS module 508, a transceiver 510 including a modem subsystem 512 and an RF unit 514, and one or more antennas 516. These elements may communicate with each other directly or indirectly, for example, via one or more buses.

[0084] The processor 502 may have various characteristics as a particular type of processor. For example, these may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 502 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0085] Memory 504 may include cache memory (e.g., cache memory of processor 502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some embodiments, memory 504 may include non-transitory computer-readable media. Memory 504 may store instructions 506. Instructions 506 may include instructions that, when executed by processor 502, cause processor 502 to perform the operations described herein (e.g., Figure 2A-3 Instructions 506 may also be referred to as code, which may be broadly interpreted as including the above-mentioned instructions. Figure 4 Any type of computer-readable statement in question.

[0086] The SPS module 508 may be implemented via hardware, software, or a combination thereof. For example, the SPS module 508 may be implemented as a processor, circuit, and / or instructions 506 stored in the memory 504 and executed by the processor 502. In some examples, the SPS module 508 may be integrated within the modem subsystem 512. For example, the SPS module 508 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 512. In some examples, the UE may include one or more SPS modules 508.

[0087] The SPS module 508 can be used in various aspects of the present disclosure, for example, Figure 2A-3 and aspects of 6-10. The SPS module 508 is configured to communicate downlink information based on the SPS configuration. The SPS module 508 is also configured to determine a piggyback opportunity for communicating DCI in the SPS configuration. The SPS module 508 is also configured to determine a HARQ process associated with a retransmitted SPS PDSCH communication. The SPS module 508 is also configured to communicate communications associated with piggyback opportunities, including piggyback DCI on the PDSCH or ACK / NACK on the PUCCH. The SPS module 508 is also configured to associate a piggyback opportunity with the SPS configuration based on radio resource control (RRC) information, a medium access control control element (MAC-CE), or an SPS activation DCI. The SPS module 508 is also configured to process and send piggyback DCI associated with the MAC-CE. The SPS module 508 is also configured to process and send piggyback DCI on the SPS PDSCH, which includes, for example, a physical uplink channel (PUCCH) resource indicator (PRI) associated with a block acknowledgement configuration for the SPS configuration.

[0088] As shown, the transceiver 510 may include a modem subsystem 512 and an RF unit 514. The transceiver 510 may be configured to communicate bidirectionally with other devices such as UE 115 and / or 400 and / or another core network element. The modem subsystem 512 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 514 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., broadcast channel, DL data block, CC configuration, PDSCH, PDCCH, DCI, MCS, TPC, CSI-RS, ZP CSI-RS trigger, SPS configuration, SPS PDSCH, MAC-CE, group ACK codebook, dynamic grant (DG) configuration, configured grant (CG) configuration, DG PDCCH, reference signals) from the modem subsystem 512 (on outbound transmissions) or from another source (such as UEs 115 and 400). The RF unit 514 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 510, the modem subsystem 512 and / or the RF unit 514 may be separate devices that are coupled together at the BS 105 to enable the BS 105 to communicate with other devices.

[0089] The RF unit 514 may provide modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to the antenna 516 for transmission to one or more other devices. This may include, for example, the transmission of information to complete attachment to a network and communication with a camped UE 115 or 400 in accordance with various embodiments of the present disclosure. The antenna 516 may further receive data messages sent from other devices and provide the received data messages for processing and / or demodulation at the transceiver 510. The transceiver 510 may provide the demodulated and decoded data (e.g., PUCCH, PUSCH, UCI, ACK / NACK, group ACK / NACK, CG uplink transmission, channel report, SRS) to the SPS module 508 for processing. The antenna 516 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0090] In one embodiment, the BS 500 may include multiple transceivers 510 that implement different RATs (e.g., NR and LTE). In one embodiment, the BS 500 may include a single transceiver 510 that implements multiple RATs (e.g., NR and LTE). In one embodiment, the transceiver 510 may include various components, where different combinations of components may implement different RATs.

[0091] Figure 6 A semi-persistent scheduling (SPS) communication scenario according to some aspects of the present disclosure is shown. The functions of scenario 600 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other appropriate components) or other appropriate unit of a wireless communication device. In some aspects, a wireless communication device such as UE 115, UE 215, or UE 400 may utilize one or more components such as a processor 402, a memory 404, an SPS module 408, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of scenario 600. In addition, a wireless communication device such as a base station (BS) 105, BS 214, or BS 500 may utilize one or more components such as a processor 502, a memory 504, an SPS module 508, a transceiver 510, a modem 512, and one or more antennas 516 to perform the steps of scenario 600. Scenario 600 may be implemented as Figure 1-5 Similar mechanisms as described in 7-10. Figure 6 In , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units.

[0092] like Figure 6 As shown in , the BS may configure SPS for the UE on PDSCH 630. The SPS may include periodic PDSCH 630a, 630b, and 630c. The SPS PDSCH may be periodic over a time period 603a having an arbitrary unit. The time period 603a may include sub-periods T0, T1, ... T7 603b having a unit such as a time slot, a subframe, a frame, or an arbitrary unit.

[0093] In some aspects, component carrier CC1 620 on which the SPS PDSCH 630 is communicated includes a piggyback opportunity for DCI (PO-DCI) 635. In some aspects, each of the SPS PDSCHs 630a, 630b, and 630c may include PO-DCI 635a, 635b, and 635c, respectively, piggybacked thereon on the PDSCH 630. In some aspects, the piggybacked PO-DCI 635 (or the following) may be added, appended, concatenated, combined, inserted, punctured, or rate matched to bits. Figure 7-9The PO-DCI 735, PO-DCI 835, or PO-DCI 935 of the BS may be piggybacked onto the SPS PDSCH 630. In some aspects, the piggybacked PO-DCI 635 may be piggybacked onto the SPS PDSCH 630 by sequentially sending the communication PDSCH 630 and the PO-DCI 635 or by sending the PDSCH 630 and the PO-DCI 635 in the same communication or message on the same CC and on the same channel (e.g., PDSCH 630). In some aspects, each of the PO-DCI 635a, 635b, and 635c may include an opportunity in which the BS may or may not send the DCI. In some aspects, the PO-DCI 635 may be piggybacked onto the beginning of the PDSCH 630 so that the PO-DCI 635 is communicated earlier in time than the PDSCH 630. Alternatively, the PO-DCI 635 may be piggybacked onto the end of the PDSCH 630 so that the PO-DCI 635 is communicated later in time than the PDSCH 630, such as Figure 6 shown.

[0094] In some respects, Figure 6 (or below Figure 7-10 ) can include configuring or activating PO-DCI 635 using an RRC message, a MAC-CE, an SPS activation DCI, or a combination of the foregoing communications. In some aspects, the configuration of PO-DCI 635 can override a default configuration for communicating the associated DCI (e.g., via the PDCCH). In some aspects, if the DCI is successfully decoded (e.g., based on a cyclic redundancy check (CRC)), the UE can utilize the information included in the PO-DCI 635.

[0095] In some respects, Figure 6 In the semi-persistent scheduling (SPS) communication scenario, PO-DCI 635 (or the following Figure 7-9PO-DCI 735, PO-DCI 835 or PO-DCI 935) may include MCS information about the modulation and coding scheme (MCS) of the SPS configuration. In some aspects, the MCS is within the range specified by the activation DCI, RRC message and / or MAC-CE for activating the SPS configuration. In some aspects, the MCS included in the PO-DCI 635 is associated with a change or incremental MCS of the MCS so as to reduce the size of the PO-DCI 635 or the overhead associated with the PO-DCI 635. In some aspects, the timing span of the MCS included in the PO-DCI 635 is only applied to the current SPS configuration. In some aspects, the timing span of the MCS included in the PO-DCI 635 is applied to the current SPS configuration and each subsequent SPS configuration until the next SPS reactivation occurs or until other notifications from the BS or network. In some aspects, the timing span of the MCS included in the PO-DCI 635 is based on a bit or parameter received by the UE, the time-frequency resource location of the PDSCH 630 (e.g., PDSCH 630a is associated with only the current SPS configuration option and PDSCH 630b is associated with additional SPS configuration options), or a piggybacking technique (e.g., puncturing is associated with only the current SPS configuration option and rate matching is associated with additional SPS configuration options).

[0096] In some respects, Figure 6 In the semi-persistent scheduling (SPS) communication scenario, PO-DCI 635 (or respectively in the following Figure 7-9 PO-DCI 735, PO-DCI 835, or PO-DCI 935) may include zero-power channel state information reference signal (ZP-CSI-RS) information. In some aspects, the carried ZP-CSI-RS information includes a ZP-CSI-RS trigger that indicates to the UE to avoid rate matching resources carrying CSI-RS for other UEs. In some aspects, the SPS communication scenario includes carried rate matching information with resource block (RB) symbol level granularity. In some aspects, the carried rate matching information includes associated two bits indicating rateMatchPatternGroup1 or rateMatchPatternGroup2 as defined in the 5G standard.

[0097] Figure 7A semi-persistent scheduling (SPS) communication scenario according to some aspects of the present disclosure is shown. The functions of scenario 700 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other appropriate components) or other appropriate unit of a wireless communication device. In some aspects, a wireless communication device such as UE 115, UE 215, or UE 400 may utilize one or more components such as a processor 402, a memory 404, an SPS module 408, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of scenario 700. In addition, a wireless communication device such as a base station (BS) 105, BS 214, or BS 500 may utilize one or more components such as a processor 502, a memory 504, an SPS module 508, a transceiver 510, a modem 512, and one or more antennas 516 to perform the steps of scenario 700. Scenario 700 may be implemented as Figure 1-6 Similar mechanisms as described in 8-10. Figure 7 In , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units.

[0098] like Figure 7 As shown in , the BS may configure SPS for the UE on PDSCH 730. The SPS may include periodic PDSCH 730a, 730b, and 730c. The SPS PDSCH may be periodic over a time period 703a having an arbitrary unit. The time period 703a may include sub-periods T0, T1, ... T7 703b having units such as time slots, subframes, frames, or arbitrary units.

[0099] In some aspects, component carrier CC1 720 on which the SPS PDSCH 730 is communicated includes a piggyback opportunity for DCI (PO-DCI) 735. In some aspects, each of the SPS PDSCHs 730a, 730b, and 730c may include a PO-DCI 735a, 735b, and 735c, respectively, piggybacked thereon on the PDSCH 730. In some aspects, a PUCCH 734 may be configured on component carrier CC2 722. In some aspects, the UE may use the PUCCH 734 for communication of ACK and / or NACK.

[0100] like Figure 7As shown in , the BS may communicate HARQ process information (e.g., HARQ control information) for retransmitting PDSCH 730 via PO-DCI 735. In some aspects, PO-DCI 735 may include HARQ process information, such as a HARQ process ID of one HARQ process among a plurality of HARQ processes N having HARQ process IDs H0, H1, H2, ... H(N-1). In some aspects, each SPS PDSCH 730 may be associated with a default HARQ process ID. For example, PDSCH 730a is associated with a default HARQ process ID H0, PDSCH 730b is associated with H1, and PDSCH 730c is associated with H0.

[0101] In some aspects, the UE may not receive the PDSCH 730a, and the UE may send a NACK in the PUCCH 734a. In some aspects, the BS may use the PDSCH 730b to retransmit the TB or data of the PDSCH 730a, and the BS may indicate that the PDSCH 730b is a retransmission by including HARQ process information (e.g., HO, RV, NDI) in the PO-DCI 735b. In some aspects, the PO-DCI 735 may include information indicating the HARQ process ID of the PDSCH 730 being retransmitted (e.g., PO-DCI 730b indicates H0 associated with PDSCH 730a) only when the HARQ process ID of the PDSCH 730 being retransmitted is different from the default HARQ process ID of the PDSCH 730 for retransmission (e.g., the default ID H1 associated with PDSCH 730b). In some aspects, the lower HARQ process ID may be used with the PO-DCI 735. In some aspects, the PO-DCI 735 may include information indicating the RV (e.g., as shown in FIG. 1 ) only when the RV is different from the default RV in the RV sequence configured for the PDSCH 730. Figure 7 , PO-DCI 735b includes the RV associated with the retransmission PDSCH 730b because it is different from the default RV value associated with PDSCH 730b). In some aspects, PO-DCI 735 may include information indicating the RV only when PDSCH 730 includes a retransmission (e.g., PO-DCI 735b includes the NDI for the retransmission PDSCH 730b). In some aspects, the absence of NDI in PO-DCI 735 may indicate that the associated PDSCH 730 includes new data (e.g., after ACK 734b, the BS may send new data PDSCH 730c and omit the NDI from PO-DCI 735c).

[0102] In some respects, Figure 7 In the semi-persistent scheduling (SPS) communication scenario, PO-DCI 735 (or Figure 6 and 8 -9 PO-DCI 635, PO-DCI 835, or PO-DCI 935) may include carrying to-be-bounded information. In some aspects, the to-be-bounded information may be communicated by one or more bits indicating that the UE will buffer the associated PDSCH 730 (i.e., the PDSCH 730 to which the PO-DCI 735 including the to-be-bounded position is carried) for HARQ combining with one (or more) PDSCH 730 received in the future. In some aspects, the BS may transmit the TB to be HARQ combined using one (or more) dynamic grant-based retransmissions. In some aspects, the BS may retransmit the TB to be HARQ combined using an SPS PDSCH (e.g., a retransmission as shown in scenario 700). In some aspects, the UE may skip providing an ACK / NACK response for the PDSCH to which the to-be-delimited terminating locator is piggybacked, including in the absence of a group ACK configuration (e.g., a group ACK configuration allows the UE to send multiple ACK / NACK responses at a time instead of sending separate ACK / NACK responses), and the UE may instead provide an ACK / NACK in response to a PDCCH or PDSCH carrying a TB to be HARQ combined with the PDSCH having the to-be-delimited terminating locator piggybacked thereon.

[0103] In some respects, Figure 7 In the semi-persistent scheduling (SPS) communication scenario, PO-DCI 735 (or Figure 6 and 8 -9) may include downlink assignment index (DAI) information to provide a dynamic ACK codebook for PUCCH resources for communicating ACK / NACK corresponding to the SPS PDSCH 730. In some aspects, the piggybacked DAI may apply only to the current SPS configuration. In some aspects, the piggybacked DAI may apply to the current SPS configuration and any subsequent SPS configuration until an SPS reactivation process occurs. In some aspects, the piggybacked DAI may apply to the current SPS configuration and any dynamic grants that may report ACK / NACK within the current ACK or block ACK of the SPS configuration.

[0104] In some respects, Figure 7 In the semi-persistent scheduling (SPS) communication scenario, PO-DCI 735 (or Figure 6 and8 -9) may include piggyback transmit power control (TPC) information to indicate to the UE whether the uplink transmit power of one (or more) channels is to be increased, decreased, or maintained the same. In some aspects, the piggyback TPC information is associated with the transmit power control of the PUCCH 734. In some aspects, the piggyback TPC information is associated with the transmit power control of the uplink sounding reference signal (SRS). In some aspects, the channel to which the TPC information included in the PO-DCI 735 is applied is based on the bit or parameter received by the UE and / or the time-frequency resource location of the PDSCH 730 (e.g., the TPC information in PDSCH 730a is applied to the PUCCH 734, and the TPC information in PDSCH 730b is applied to the SRS).

[0105] Figure 8 A semi-persistent scheduling (SPS) communication scenario according to some aspects of the present disclosure is shown. The functions of scenario 800 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other appropriate components) or other appropriate unit of a wireless communication device. In some aspects, a wireless communication device such as UE 115, UE 215, or UE 400 may utilize one or more components such as a processor 402, a memory 404, an SPS module 408, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of scenario 800. In addition, a wireless communication device such as a base station (BS) 105, BS 214, or BS 500 may utilize one or more components such as a processor 502, a memory 504, an SPS module 508, a transceiver 510, a modem 512, and one or more antennas 516 to perform the steps of scenario 800. Scenario 800 may be implemented as Figure 1-7 Similar mechanisms as described in 9-10. Figure 8 In , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units.

[0106] like Figure 8 As shown in , the BS may configure SPS for the UE on PDSCH 830. The SPS may include periodic PDSCH 830a, 830b, 830c, and 830d. ​​The SPS PDSCH may be periodic over a time period 803a having an arbitrary unit. The time period 803a may include sub-periods T0, T1, ... T7 803b having a unit such as a time slot, a subframe, a frame, or an arbitrary unit.

[0107] In some aspects, component carrier CC1 820 on which the SPS PDSCH 830 is communicated includes a piggyback opportunity for DCI (PO-DCI) 835. In some aspects, each of the SPS PDSCHs 830a, 830b, 830c, and 830d may include PO-DCI 835a, 835b, 835c, and 835d, respectively, piggybacked thereon on the PDSCH 830. In some aspects, a PUCCH 834 may be configured on component carrier CC2 822. In some aspects, the UE may transmit ACK and / or NACK using the PUCCH 834.

[0108] like Figure 8 As shown in , the BS may transmit a piggyback group ACK trigger in PO-DCI 835b, which requests the UE to provide a hint and / or early feedback for the configured HARQ process of the UE. In some aspects, PDSCH 830a may be associated with a block ACK timing span Ts 843, at which time (e.g., about the beginning of T7 803b) the UE sends a group ACK (e.g., using PUCCH 834a', PUCCH 834b', PUCCH 834c and / or PUCCH 834d). In some aspects, the original block ACK timing span Ts 843 ends at a later time point than the hint / early report timing spans Ta 841 and Tb 842 requested by the BS and associated with PDCCH 830a and PDDCH 830b, respectively. In some aspects, the UE may send ACK 834a and ACK 834b in a prompt / early group ACK to indicate successful reception of PDSCH 830a and PDSCH 830b, respectively. In some aspects, in a scenario where the UE sends ACK 834a and ACK 834b associated with PDSCH 830a and PDSCH 830b, the UE may also send NACK 834a' and NACK 834b', thereby allowing the BS to send new data using the HARQ process associated with PDSCH 830a and PDSCH 830b (e.g., the new data may be sent between the end of Tb 842 and the end of Ts 843 or after the end of Ts 843). In some aspects, the BS may send new data using the HARQ process associated with PDSCH 830a and PDSCH 830b based on receiving ACK 834a and ACK 834b (e.g., via Figure 8 In some aspects, the group ACK including NACK 834a' and NACK 834b' may also include PUCCH 834c and PUCCH 834d for sending ACK / NACK associated with PDSCH 830c and PDSCH 830d, respectively.

[0109] Fig. 9 A semi-persistent scheduling (SPS) communication scenario according to some aspects of the present disclosure is shown. The functions of scenario 900 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other appropriate components) or other appropriate unit of a wireless communication device. In some aspects, a wireless communication device such as UE 115, UE 215, or UE 400 may utilize one or more components such as a processor 402, a memory 404, an SPS module 408, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of scenario 900. In addition, a wireless communication device such as a base station (BS) 105, BS214, or BS 500 may utilize one or more components such as a processor 502, a memory 504, an SPS module 508, a transceiver 510, a modem 512, and one or more antennas 516 to perform the steps of scenario 900. Scenario 900 may be implemented in the same manner as described above. Figure 1-8 Similar mechanism as described in 10. Fig. 9 In , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units.

[0110] like Fig. 9 As shown in , the BS may configure SPS 930 for the UE on the PDSCH. The SPS may include periodic PDSCH 930a, 930b, and 930c. The SPS PDSCH may be periodic over a time period 903a having an arbitrary unit. The time period 903a may include sub-periods T0, T1, ... T7 903b having a unit such as a time slot, a subframe, a frame, or an arbitrary unit.

[0111] In some aspects, component carrier CC1 920 on which the SPS PDSCH 930 is communicated includes a piggyback opportunity for DCI (PO-DCI) 935. In some aspects, each of the SPS PDSCHs 930a, 930b, and 930c may include PO-DCI 935a, 935b, and 935c, respectively, piggybacked thereto on the PDSCH 930. In some aspects, a PUCCH 934 may be configured on component carrier CC2 922. In some aspects, the UE may use the PUCCH 934 to transmit ACK and / or NACK.

[0112] like Fig. 9As shown in , the BS may transmit a piggyback PUCCH resource indicator (PRI) (also referred to as a k1 indicator) in a PO-DCI 935a, which indicates the location of a PUCCH 934 for sending an ACK / NACK corresponding to a PDSCH 930. In some aspects, the piggyback PRI 935a (k1) indicates the location of a group or block ACK for indicating ACK / NACK in PUCCH 934a, PUCCH 934b, and PUCCH 934c associated with a plurality of PDSCHs 930 (e.g., PDSCH 930a, PDSCH 930b, and PDSCH 930c), respectively. In some aspects, the piggyback PRI for configuring a group or block ACK in PUCCH 934a, PUCCH 934b, and PUCCH 934c may be transmitted in a PO-DCI 935b or PO-DCI 935c. In the scenario where piggyback PRI is communicated in PO-DCI 935, the group or block ACK for the SPS configuration may be transmitted to the UE using only Layer 1 (ie, physical layer) signaling.

[0113] In some respects, Fig. 9 In the semi-persistent scheduling (SPS) communication scenario, PO-DCI 935 (or Figure 6-8 PO-DCI 635, PO-DCI 735, or PO-DCI 835) may include piggyback radio resource allocation information for indicating to the UE a change in time domain resource allocation (TDRA) and / or frequency domain resource allocation (FDRA) of the SPS PDSCH 930 or PUCCH 934. In some aspects, the change in TDRA and / or FDRA indicated via PO-DCI 935 may be applied only to the current SPS configuration (e.g., the SPS configuration shown in period 903a or a portion of the SPS configuration). In some aspects, the change in TDRA and / or FDRA indicated via PO-DCI 935 may be applied to the current SPS configuration and any subsequent SPS configuration until the UE receives further notification from the BS.

[0114] In some respects, Fig. 9 In the semi-persistent scheduling (SPS) communication scenario, via PO-DCI 935 (or respectively Figure 6-8 The downlink control information communicated using PO-DCI 635, PO-DCI 735 or PO-DCI 835) is communicated as MAC-CE.

[0115] Fig.10A flow chart of a communication method 1000 according to some aspects of the present disclosure is shown. The functions of method 1000 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other appropriate components) or other appropriate means of a wireless communication device. In some aspects, a wireless communication device such as UE 115, UE 215, or UE 400 may utilize one or more components such as a processor 402, a memory 404, an SPS module 408, a transceiver 410, a modem 412, and one or more antennas 416 to perform the steps of method 1000. In addition, a wireless communication device such as base station (BS) 105, BS 214, or BS 500 may utilize one or more components such as a processor 502, a memory 504, an SPS module 508, a transceiver 510, a modem 512, and one or more antennas 516 to perform the steps of method 1000. Method 1000 may be implemented as Figure 1-9 Similar mechanism as described in .

[0116] like Fig.10 As shown in , step 1010 includes: determining, by the first wireless communication device, a piggyback opportunity for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration. In some aspects, each of the network 100, BS 105 or BS 500, and UE 115 or UE 500 may use a processor, memory, and / or software (including, for example, Figure 1 and 4 -5) to perform one or more of the hardware and software components shown in the figure to perform the determination step 1010. Each entity can use a variety of algorithms to perform this step, including, for example, the above-mentioned Figure 2A-3 In some aspects, the determining step 1010 may include an algorithm for determining one or more piggyback opportunities for communicating the DCI based on the algorithm for configuring PO-DCI 635, PO-DCI 735, PO-DCI 835, or PO-DCI 935, respectively, for scenarios 600, 700, 800, or 900, as discussed above and described above in Figure 6-9 As shown in .

[0117] Step 1020 further includes: communicating, by the first wireless communication device and the second wireless communication device, a first communication associated with the determined piggyback opportunity. In some aspects, each of the network 100, BS 105 or BS 500, and UE 115 or UE 500 may use a processor, memory, transceiver, antenna, and / or software (including, for example, Figure 1 and 4-5) to perform one or more of the hardware and software components shown in the communication step 1020. Each entity can use a variety of algorithms to perform this step, including, for example, the above-mentioned Figure 2A-3 and the algorithm described in 6-9.

[0118] In some examples, the determined piggybacking opportunity is based on one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI.

[0119] In some examples, the determined piggybacking opportunity is associated with one of rate matching a physical downlink shared channel (PDSCH) resource or puncturing the PDSCH resource.

[0120] In some examples, the determined piggyback opportunity overrides a default configuration for communicating the DCI.

[0121] In some examples, the determined piggyback opportunities are associated with a piggyback modulation and coding scheme (MCS).

[0122] In some examples, the piggybacked MCS is based on one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI.

[0123] In some instances, the pickup opportunity is associated with a pickup opportunity timing span that includes one of: only the SPS configuration, or the SPS configuration and each of one or more subsequent SPS configurations until a reactivation process.

[0124] In some instances, the piggyback opportunity timing span is based on one of: piggyback opportunity timing span information, time-frequency resource location, physical downlink shared channel (PDSCH) puncturing configuration, or PDSCH rate matching configuration.

[0125] In some examples, the determined piggybacking opportunity is associated with a piggybacked zero-power channel state information resource signal (CSI-RS) trigger for avoiding rate matching on a time-frequency resource carrying the CSI-RS.

[0126] In some examples, the determined piggybacking opportunities are associated with a resource block symbol matching pattern, wherein the resource block symbol matching pattern is associated with one of rateMatchPatternGroup1 or rateMatchPatternGroup2.

[0127] In some instances, the determined piggyback opportunity is associated with hybrid automatic repeat request (HARQ) control information (CI), wherein the HARQ CI does not include a redundancy version (RV) indicator based on a preconfigured RV sequence, wherein the HARQ CI does not include a HARQ process identifier (ID) based on a default HARQ process ID, and / or wherein the HARQ CI includes a new data indicator (NDI) based on a retransmission.

[0128] In some instances, the determined piggyback opportunity is associated with to-be-defined piggyback information for a hybrid automatic repeat request (HARQ) for a combined physical downlink shared channel (PDSCH) communication, wherein the PDSCH communication includes a retransmission based on a dynamic grant configuration or one of the SPS configurations, and / or wherein the determined piggyback opportunity is not associated with a HARQ response.

[0129] In some instances, the determined piggyback opportunity is associated with a downlink assignment index (DAI) of a dynamic confirmation codebook, wherein the DAI is associated with one of: only the SPS configuration, or the SPS configuration and one or more dynamic grants, and / or wherein the SPS configuration is associated with a block confirmation configuration.

[0130] In some examples, the determined piggyback opportunities are associated with piggyback triggers for group confirmation.

[0131] In some examples, a method further includes communicating, by the first wireless communication device, a second communication with the second wireless communication device based on the piggyback trigger, wherein the second communication is associated with one of an acknowledgement or a negative acknowledgement.

[0132] In some instances, the determined piggybacking opportunity is associated with transmit power control (TPC) information, wherein the TPC information is associated with a second communication, wherein the second communication is associated with one of: an acknowledgment associated with the SPS configuration, or a sounding reference signal, and / or wherein the second communication is based on a time-frequency resource location.

[0133] In some examples, the determined piggyback opportunity is associated with a piggyback physical uplink control channel (PUCCH) resource indicator (PRI).

[0134] In some examples, a piggyback PRI is associated with a block acknowledgement configuration for the SPS configuration.

[0135] In some examples, the determined piggyback opportunity is associated with a piggyback radio resource allocation, wherein the piggyback radio resource allocation is associated with one of: the SPS configuration, or the SPS configuration and each subsequent SPS configuration.

[0136] In some examples, the determined piggyback opportunity is associated with a Medium Access Control Control Element (MAC-CE).

[0137] In some examples, a method further includes receiving, by the first wireless communication device, a first communication on a physical downlink shared channel (PDSCH) associated with the determined piggyback opportunity.

[0138] In some examples, a method further includes sending, by the first wireless communication device, the first communication on a physical downlink shared channel (PDSCH) associated with the determined piggyback opportunity.

[0139] Information and signals may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0140] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration).

[0141] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on a computer-readable medium or transmitted by a computer-readable medium as one or more instructions or codes. Other examples and embodiments are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. The features that implement the functions can also be physically located at various locations, including being distributed so that the parts of the functions are implemented at different physical locations. In addition, as used herein (including claims), the "or" used in a list of items (e.g., a list of items ending with phrases such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0142] As those skilled in the art will now appreciate and depending on the particular application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the scope of the specific embodiments shown and described herein, as they are merely examples thereof, but should be fully commensurate with the scope of the appended claims and their functional equivalents.

Claims

1. A method of wireless communication, comprising: determining, by a first wireless communication device, a piggyback opportunity for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration, wherein the DCI is to be piggybacked on an SPS physical downlink shared channel (PDSCH), and wherein the DCI carries at least a piggyback modulation and coding scheme (MCS) for the SPS configuration; and The first wireless communication device communicates the first communication with the second wireless communication device based on the determined piggyback opportunity.

2. The method according to claim 1, wherein: The determined piggyback opportunity is based on one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI; The determined piggybacking opportunity is associated with one of rate matching the PDSCH resource or puncturing the PDSCH resource; and The determined piggyback opportunity overrides the default configuration used to communicate the DCI.

3. The method according to claim 1, in, The piggybacked MCS is associated with one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI; wherein the pick-up opportunity is associated with a pick-up opportunity timing span, the pick-up opportunity timing span comprising one of: only the SPS configuration, or the SPS configuration and each of one or more subsequent SPS configurations until a reactivation process; and The piggyback opportunity timing span is based on one of the following: piggyback opportunity timing span information, time-frequency resource location, PDSCH puncturing configuration or PDSCH rate matching configuration.

4. The method according to claim 1, wherein: The determined piggybacking opportunity is associated with a piggybacked zero-power channel state information resource signal (CSI-RS) trigger for avoiding rate matching on a time-frequency resource carrying the CSI-RS.

5. The method according to claim 1, wherein: The determined piggybacking opportunities are associated with a resource block symbol matching pattern, wherein the resource block symbol matching pattern is associated with one of rateMatchPatternGroup1 or rateMatchPatternGroup2.

6. The method according to claim 1, wherein: The determined piggyback opportunity is associated with hybrid automatic repeat request (HARQ) control information (CI); The HARQ CI does not include a redundancy version (RV) indicator based on a pre-configured RV sequence; The HARQ CI does not include a HARQ process ID based on a default HARQ process identifier (ID); and The HARQ CI includes a new data indicator (NDI) based on retransmission.

7. The method according to claim 1, wherein: The determined piggyback opportunity is associated with to-be-defined piggyback information for hybrid automatic repeat request (HARQ) for combined PDSCH communication; wherein the PDSCH communication includes retransmission based on one of a dynamic grant configuration or the SPS configuration; and The determined piggybacking opportunity is not associated with the HARQ response.

8. The method according to claim 1, wherein: The determined piggyback opportunity is associated with a downlink assignment index (DAI) of a dynamic confirmation codebook; wherein the DAI is associated with one of: only the SPS configuration, or the SPS configuration and one or more dynamic grants; and The SPS configuration is associated with the block confirmation configuration.

9. The method according to claim 1, wherein: The determined pickup opportunity is associated with a pickup trigger for group confirmation; And wherein the method further comprises: communicating, by the first wireless communication device, a second communication with a second wireless communication device based on the piggyback trigger; and The second communication is associated with one of an acknowledgement or a negative acknowledgement.

10. The method according to claim 1, wherein: The determined piggybacking opportunities are associated with transmit power control (TPC) information, wherein the TPC information is associated with the second communication; wherein the second communication is associated with one of: an acknowledgement associated with the SPS configuration, or a sounding reference signal; and Wherein, the second communication is based on the time-frequency resource location.

11. The method according to claim 1, wherein: The determined piggyback opportunities are associated with piggyback physical uplink control channel (PUCCH) resource indicators (PRIs).

12. The method according to claim 1, wherein: The determined piggyback opportunity is associated with a piggyback physical uplink control channel (PUCCH) resource indicator (PRI); and The carried PRI is associated with a block confirmation configuration of the SPS configuration.

13. The method according to claim 1, wherein: The determined piggyback opportunities are associated with piggyback radio resource allocations; and The piggyback radio resource allocation is associated with one of: the SPS configuration, or the SPS configuration and each subsequent SPS configuration.

14. The method according to claim 1, wherein: The determined piggyback opportunities are associated with a Medium Access Control Control Element (MAC-CE).

15. The method according to claim 1, wherein: Conducting the communication of the first communication further comprises: The first communication is received by the first wireless communication device on the SPS PDSCH.

16. The method according to claim 1, wherein: Conducting the communication of the first communication further comprises: The first communication is sent by the first wireless communication device on the SPS PDSCH.

17. A first wireless communication device, comprising: A processor configured to: Determining a piggyback opportunity for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration, wherein the DCI is to be piggybacked on an SPS physical downlink shared channel (PDSCH), and wherein the DCI carries at least a piggyback modulation and coding scheme (MCS) for the SPS configuration; and A transceiver configured to: The first communication is communicated with the second wireless communication device based on the determined piggyback opportunity.

18. The first wireless communication device according to claim 17, wherein: The determined piggyback opportunity is based on one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI; The determined piggybacking opportunity is associated with one of rate matching the PDSCH resource or puncturing the PDSCH resource; and The determined piggyback opportunity overrides the default configuration used to communicate the DCI.

19. The first wireless communication device according to claim 17, in, The piggybacked MCS is associated with one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI; wherein the pick-up opportunity is associated with a pick-up opportunity timing span, the pick-up opportunity timing span comprising one of: only the SPS configuration, or the SPS configuration and each of one or more subsequent SPS configurations until a reactivation process; and The piggyback opportunity timing span is based on one of the following: piggyback opportunity timing span information, time-frequency resource location, PDSCH puncturing configuration or PDSCH rate matching configuration.

20. The first wireless communication device according to claim 17, wherein: The determined piggybacking opportunity is associated with a piggybacked zero-power channel state information resource signal (CSI-RS) trigger for avoiding rate matching on a time-frequency resource carrying the CSI-RS.

21. The first wireless communication device according to claim 17, wherein: The determined piggybacking opportunities are associated with a resource block symbol matching pattern, wherein the resource block symbol matching pattern is associated with one of rateMatchPatternGroup1 or rateMatchPatternGroup2.

22. The first wireless communication device according to claim 17, wherein: The determined piggyback opportunity is associated with hybrid automatic repeat request (HARQ) control information (CI); The HARQ CI does not include a redundancy version (RV) indicator based on a pre-configured RV sequence; The HARQ CI does not include a HARQ process ID based on a default HARQ process identifier (ID); and The HARQ CI includes a new data indicator (NDI) based on retransmission.

23. The first wireless communication device according to claim 17, wherein: The determined piggyback opportunity is associated with to-be-defined piggyback information for hybrid automatic repeat request (HARQ) for combined PDSCH communication; wherein the PDSCH communication includes retransmission based on one of a dynamic grant configuration or the SPS configuration; and The determined piggybacking opportunity is not associated with the HARQ response.

24. The first wireless communication device according to claim 17, wherein: The determined piggyback opportunity is associated with a downlink assignment index (DAI) of a dynamic confirmation codebook; wherein the DAI is associated with one of: only the SPS configuration, or the SPS configuration and one or more dynamic grants; and The SPS configuration is associated with the block confirmation configuration.

25. The first wireless communication device according to claim 17, wherein: The determined pickup opportunity is associated with a pickup trigger for group confirmation; And wherein the transceiver is further configured to: communicating a second communication with a second wireless communication device based on the piggyback trigger; and The second communication is associated with one of an acknowledgement or a negative acknowledgement.

26. The first wireless communication device according to claim 17, wherein: The determined piggybacking opportunities are associated with transmit power control (TPC) information, wherein the TPC information is associated with the second communication; wherein the second communication is associated with one of: an acknowledgement associated with the SPS configuration, or a sounding reference signal; and Wherein, the second communication is based on the time-frequency resource location.

27. The first wireless communication device according to claim 17, wherein: The determined piggyback opportunities are associated with piggyback physical uplink control channel (PUCCH) resource indicators (PRIs).

28. The first wireless communication device according to claim 17, wherein: The determined piggyback opportunity is associated with a piggyback physical uplink control channel (PUCCH) resource indicator (PRI); and The carried PRI is associated with a block confirmation configuration of the SPS configuration.

29. The first wireless communication device according to claim 17, wherein: The determined piggyback opportunities are associated with piggyback radio resource allocations; and The piggyback radio resource allocation is associated with one of: the SPS configuration, or the SPS configuration and each subsequent SPS configuration.

30. The first wireless communication device according to claim 17, wherein: The determined piggyback opportunities are associated with a Medium Access Control Control Element (MAC-CE).

31. The first wireless communication device according to claim 17, wherein: The transceiver is further configured to: The first communication is received on the SPS PDSCH.

32. The first wireless communication device according to claim 17, wherein: The transceiver is further configured to: The first communication is sent on the SPS PDSCH.

33. A non-transitory computer readable medium having program code recorded thereon, the program code, when executed by a processor in a first wireless communication device, comprising code for causing the first wireless communication device to: Determining a piggyback opportunity for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration, wherein: The DCI is to be carried on an SPS physical downlink shared channel (PDSCH), and wherein the DCI carries at least a carried modulation and coding scheme (MCS) for the SPS configuration; and The first communication is communicated with the second wireless communication device based on the determined piggyback opportunity.

34. The non-transitory computer readable medium of claim 33, wherein: The determined piggyback opportunity is based on one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI; The determined piggybacking opportunity is associated with one of rate matching the PDSCH resource or puncturing the PDSCH resource; and The determined piggyback opportunity overrides the default configuration used to communicate the DCI.

35. The non-transitory computer readable medium of claim 33, in, The piggybacked MCS is associated with one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI; wherein the pick-up opportunity is associated with a pick-up opportunity timing span, the pick-up opportunity timing span comprising one of: only the SPS configuration, or the SPS configuration and each of one or more subsequent SPS configurations until a reactivation process; and The piggyback opportunity timing span is based on one of the following: piggyback opportunity timing span information, time-frequency resource location, PDSCH puncturing configuration or PDSCH rate matching configuration.

36. The non-transitory computer readable medium of claim 33, wherein: The determined piggybacking opportunity is associated with a piggybacked zero-power channel state information resource signal (CSI-RS) trigger for avoiding rate matching on a time-frequency resource carrying the CSI-RS.

37. The non-transitory computer readable medium of claim 33, wherein: The determined piggybacking opportunities are associated with a resource block symbol matching pattern, wherein the resource block symbol matching pattern is associated with one of rateMatchPatternGroup1 or rateMatchPatternGroup2.

38. The non-transitory computer readable medium of claim 33, wherein: The determined piggyback opportunity is associated with hybrid automatic repeat request (HARQ) control information (CI); The HARQ CI does not include a redundancy version (RV) indicator based on a pre-configured RV sequence; The HARQ CI does not include a HARQ process ID based on a default HARQ process identifier (ID); and The HARQ CI includes a new data indicator (NDI) based on retransmission.

39. The non-transitory computer readable medium of claim 33, wherein: The determined piggyback opportunity is associated with to-be-defined piggyback information for hybrid automatic repeat request (HARQ) for combined PDSCH communication; wherein the PDSCH communication includes retransmission based on one of a dynamic grant configuration or the SPS configuration; and The determined piggybacking opportunity is not associated with the HARQ response.

40. The non-transitory computer readable medium of claim 33, wherein: The determined piggyback opportunity is associated with a downlink assignment index (DAI) of a dynamic confirmation codebook; wherein the DAI is associated with one of: only the SPS configuration, or the SPS configuration and one or more dynamic grants; and The SPS configuration is associated with the block confirmation configuration.

41. The non-transitory computer readable medium of claim 33, wherein: The determined pickup opportunity is associated with a pickup trigger for group confirmation; Wherein, when the program code is executed by the processor in the first wireless communication device, the program code further includes a code for causing the first wireless communication device to perform the following operations: communicating a second communication with a second wireless communication device based on the piggyback trigger; and The second communication is associated with one of an acknowledgement or a negative acknowledgement.

42. The non-transitory computer readable medium of claim 33, wherein: The determined piggybacking opportunities are associated with transmit power control (TPC) information, wherein the TPC information is associated with the second communication; wherein the second communication is associated with one of: an acknowledgement associated with the SPS configuration, or a sounding reference signal; and Wherein, the second communication is based on the time-frequency resource location.

43. The non-transitory computer readable medium of claim 33, wherein: The determined piggyback opportunities are associated with piggyback physical uplink control channel (PUCCH) resource indicators (PRIs).

44. The non-transitory computer readable medium of claim 33, wherein: The determined piggyback opportunity is associated with a piggyback physical uplink control channel (PUCCH) resource indicator (PRI); and The carried PRI is associated with a block confirmation configuration of the SPS configuration.

45. The non-transitory computer readable medium of claim 33, wherein: The determined piggyback opportunities are associated with piggyback radio resource allocations; and The piggyback radio resource allocation is associated with one of: the SPS configuration, or the SPS configuration and each subsequent SPS configuration.

46. ​​The non-transitory computer readable medium of claim 33, wherein: The determined piggyback opportunities are associated with a Medium Access Control Control Element (MAC-CE).

47. The non-transitory computer readable medium of claim 33, wherein: The program code, when executed by a processor in the first wireless communication device, further includes code for causing the first wireless communication device to perform the following operations: The first communication is received on the SPS PDSCH.

48. The non-transitory computer readable medium of claim 33, wherein: The program code, when executed by a processor in the first wireless communication device, further includes code for causing the first wireless communication device to perform the following operations: The first communication is sent on the SPS PDSCH.

49. A first wireless communication device, comprising: means for determining a piggyback opportunity for communication of downlink control information (DCI) in a semi-persistent scheduling (SPS) configuration, wherein the DCI is to be piggybacked on an SPS physical downlink shared channel (PDSCH), and wherein the DCI carries at least a piggyback modulation and coding scheme (MCS) for the SPS configuration; and Means for communicating the first communication with a second wireless communication device based on the determined piggyback opportunity.

50. The first wireless communication device according to claim 49, wherein: The determined piggyback opportunity is based on one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI; The determined piggybacking opportunity is associated with one of rate matching the PDSCH resource or puncturing the PDSCH resource; and The determined piggyback opportunity overrides the default configuration used to communicate the DCI.

51. The first wireless communication device according to claim 49, in, The piggybacked MCS is associated with one of a radio resource control (RRC) message, a medium access control control element (MAC-CE), or an SPS activation DCI; wherein the pick-up opportunity is associated with a pick-up opportunity timing span, the pick-up opportunity timing span comprising one of: only the SPS configuration, or the SPS configuration and each of one or more subsequent SPS configurations until a reactivation process; and The piggyback opportunity timing span is based on one of the following: piggyback opportunity timing span information, time-frequency resource location, PDSCH puncturing configuration or PDSCH rate matching configuration.

52. The first wireless communication device of claim 49, wherein: The determined piggybacking opportunity is associated with a piggybacked zero-power channel state information resource signal (CSI-RS) trigger for avoiding rate matching on a time-frequency resource carrying the CSI-RS.

53. The first wireless communication device of claim 49, wherein: The determined piggybacking opportunities are associated with a resource block symbol matching pattern, wherein the resource block symbol matching pattern is associated with one of rateMatchPatternGroup1 or rateMatchPatternGroup2.

54. The first wireless communication device of claim 49, wherein: The determined piggyback opportunity is associated with hybrid automatic repeat request (HARQ) control information (CI); The HARQ CI does not include a redundancy version (RV) indicator based on a pre-configured RV sequence; The HARQ CI does not include a HARQ process ID based on a default HARQ process identifier (ID); and The HARQ CI includes a new data indicator (NDI) based on retransmission.

55. The first wireless communication device of claim 49, wherein: The determined piggyback opportunity is associated with to-be-defined piggyback information for hybrid automatic repeat request (HARQ) for combined PDSCH communication; wherein the PDSCH communication includes retransmission based on one of a dynamic grant configuration or the SPS configuration; and The determined piggybacking opportunity is not associated with the HARQ response.

56. The first wireless communication device of claim 49, wherein: The determined piggyback opportunity is associated with a downlink assignment index (DAI) of a dynamic confirmation codebook; wherein the DAI is associated with one of: only the SPS configuration, or the SPS configuration and one or more dynamic grants; and The SPS configuration is associated with the block confirmation configuration.

57. The first wireless communication device of claim 49, wherein: The determined pickup opportunity is associated with a pickup trigger for group confirmation; And wherein, the first wireless communication device further comprises: means for communicating a second communication with a second wireless communication device based on the piggyback trigger; and The second communication is associated with one of an acknowledgement or a negative acknowledgement.

58. The first wireless communication device of claim 49, wherein: The determined piggybacking opportunities are associated with transmit power control (TPC) information, wherein the TPC information is associated with the second communication; wherein the second communication is associated with one of: an acknowledgement associated with the SPS configuration, or a sounding reference signal; and Wherein, the second communication is based on the time-frequency resource location.

59. The first wireless communication device of claim 49, wherein: The determined piggyback opportunities are associated with piggyback physical uplink control channel (PUCCH) resource indicators (PRIs).

60. The first wireless communication device of claim 49, wherein: The determined piggyback opportunity is associated with a piggyback physical uplink control channel (PUCCH) resource indicator (PRI); and The carried PRI is associated with a block confirmation configuration of the SPS configuration.

61. The first wireless communication device of claim 49, wherein: The determined piggyback opportunities are associated with piggyback radio resource allocations; and The piggyback radio resource allocation is associated with one of: the SPS configuration, or the SPS configuration and each subsequent SPS configuration.

62. The first wireless communication device of claim 49, wherein: The determined piggyback opportunities are associated with a Medium Access Control Control Element (MAC-CE).

63. The first wireless communication device of claim 49, wherein: The means for conducting a communication of the first communication further comprises: Means for receiving the first communication on the SPS PDSCH.

64. The first wireless communication device of claim 49, wherein: The means for conducting a communication of the first communication further comprises: Means for sending the first communication on the SPS PDSCH.

Images