Multiple transmission time interval (TTI) grant scheduling

Abstract

Certain aspects of the present disclosure provide techniques for scheduling a physical uplink shared channel (PUSCH) across multiple transmission time intervals (TTIs) using a multiple TTI grant.

Description

[0001] This divisional application is a divisional application of the PCT national phase patent application with a PCT international application date of June 27, 2020, national application number 202080045549.6, and titled “Method and Apparatus for Scheduling Multiple Transmission Time Intervals (TTI)”. Technical Field

[0002]

[0004] Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for scheduling a physical uplink shared channel (PUSCH) in multiple transmission time interval (TTI) grants using multiple TTIs. Background Art

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name just a few.

[0004] In some examples, a wireless multiple access communication system may include several base stations (BS), each of which is capable of supporting communication of multiple communication devices (also referred to as user equipment (UE)) simultaneously. In an LTE or LTE-A network, a set of one or more base stations may define an evolved B node (eNB). In other examples (e.g., in a next generation, new radio (NR), or 5G network), a wireless multiple access communication system may include several distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with several central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more DUs in communication with a CU may define an access node (e.g., which may be referred to as a BS, a next generation B node (gNB or g B node), a TRP, etc.). A BS or DU may communicate with a set of UEs on a downlink channel (e.g., for transmission from a BS or DU to a UE) and an uplink channel (e.g., for transmission from a UE to a BS or DU).

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is an enhancement set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0006] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies. Summary of the invention

[0007] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed in the appended claims, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of the present disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0008] Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes: receiving a CG uplink configuration to be used for one or more configured grant (CG) uplink transmissions; receiving downlink control information (DCI) scheduling a plurality of transmission time intervals (TTIs) for grant-based uplink transmissions, wherein a hybrid automatic repeat request (HARQ) process identifier (ID) is assigned to the grant-based transmission in the following manner: starting from the HARQ ID indicated in the DCI and incrementing the HARQ ID by 1 for each subsequent grant-based transmission; determining that at least one HARQ ID to be assigned for a corresponding grant-based uplink transmission set is configured for CG uplink transmission; receiving an indication of whether to assign a HARQ ID configured for the CG uplink transmission to a grant-based transmission; assigning a HARQ ID to the grant-based transmission set based on the received indication; and transmitting the grant-based transmission based on the assigned HARQ ID.

[0009] Certain aspects of the present disclosure provide a method for wireless communication by a base station (BS). The method generally includes: transmitting a CG uplink configuration to be used for one or more configured grant (CG) uplink transmissions; transmitting downlink control information (DCI) scheduling a plurality of transmission time intervals (TTIs) for grant-based uplink transmissions, wherein a hybrid automatic repeat request (HARQ) process identifier (ID) will be assigned to the grant-based uplink transmission in the following manner: starting from the HARQ ID indicated in the DCI and incrementing the HARQ ID by 1 for each subsequent grant-based transmission; determining that at least one HARQ ID to be assigned for a corresponding grant-based uplink transmission set is configured for CG uplink transmission; transmitting an indication of whether to assign a HARQ ID configured for CG uplink transmission to a grant-based transmission; and receiving a grant-based uplink transmission based on the HARQ ID assigned according to the indication.

[0010] Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes: receiving information related to a set of (HARQ) process identifiers (IDs) to be assigned for grant-based uplink transmissions; receiving downlink control information (DCI) scheduling a plurality of transmission time intervals (TTIs) for grant-based uplink transmissions, wherein the HARQ process IDs are assigned to the grant-based uplink transmissions from the set of HARQ process IDs; and transmitting the grant-based uplink transmissions based on the assigned HARQ IDs.

[0011] Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes: transmitting information related to a set of (HARQ) process identifiers (IDs) to be assigned for grant-based uplink transmissions; transmitting downlink control information (DCI) scheduling a plurality of transmission time intervals (TTIs) for grant-based uplink transmissions, wherein HARQ process IDs will be assigned to the grant-based uplink transmissions from the set of HARQ process IDs; and receiving the grant-based uplink transmissions based on the assigned HARQ process IDs.

[0012] Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes: receiving a CG uplink configuration to be used for one or more configured grant (CG) uplink transmissions; receiving downlink control information (DCI) that schedules multiple uplink transmissions across multiple transmission time intervals (TTIs); determining a scrambling type for scrambling a cyclic redundancy check (CRC) portion of the DCI; determining a UE behavior associated with the CG uplink configuration based on the scrambling type; and transmitting the one or more CG uplink transmissions according to the CG uplink configuration based on the determined UE behavior.

[0013] Certain aspects of the present disclosure provide a method for wireless communication by a base station (BS). The method generally includes: transmitting a CG uplink configuration to be used for one or more configured grants (CG) uplink transmissions; generating downlink control information (DCI) to schedule multiple uplink transmissions across multiple transmission time intervals (TTIs); determining a scrambling type to be used to scramble a cyclic redundancy check (CRC) portion of the DCI; scrambling the DCI using the determined scrambling type; transmitting the scrambled DCI; and receiving the one or more CG uplink transmissions according to the CG uplink configuration based on the scrambling type.

[0014] Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes: receiving a downlink control information (DCI) according to a format that can schedule multiple physical uplink shared channel (PUSCH) transmissions across multiple transmission time intervals (TTIs), wherein at least one field of the DCI is assigned one or more bits for each of a maximum number of PUSCH transmissions that can be scheduled by the DCI; determining that the DCI schedules a portion of the maximum number of PUSCH transmissions that can be scheduled by the DCI; and interpreting one or more unused bits assigned to the at least one field as code block group transmission information (CBGTI) for the scheduled PUSCH transmissions, the one or more unused bits corresponding to the remaining unscheduled portion of the maximum number of PUSCH transmissions.

[0015] Certain aspects of the present disclosure provide a method for wireless communication by a base station (BS). The method generally includes: transmitting a downlink control information (DCI) according to a downlink control information (DCI) format that can schedule multiple physical uplink shared channel (PUSCH) transmissions across multiple transmission time intervals (TTIs), wherein at least one field of the DCI is assigned one or more bits for each of a maximum number of PUSCH transmissions that can be scheduled by the DCI, and the DCI schedules a portion of the maximum number of PUSCH transmissions that can be scheduled by the DCI; and using one or more unused bits assigned to the at least one field to transmit code block group transmission information (CBGTI) for the scheduled PUSCH transmissions, the one or more unused bits corresponding to the remaining unscheduled portion of the maximum number of PUSCH transmissions.

[0016] Certain aspects of the present disclosure provide a method for wireless communication by a user equipment. The method generally includes: receiving downlink control information (DCI) scheduling a plurality of transmission time intervals (TTIs) for uplink transmission, wherein the DCI includes a CSI request field containing a request for a channel state information (CSI) report; and in response to receiving the request, transmitting the CSI report in at least one of the scheduled TTIs that meets a processing time requirement after receiving the request.

[0017] Certain aspects of the present disclosure provide a method for wireless communication by a base station (BS). The method generally includes: transmitting downlink control information (DCI) scheduling a plurality of transmission time intervals (TTIs) for uplink transmission, wherein the DCI includes a CSI request field containing a request for a channel state information (CSI) report; and in response to the request, receiving the CSI report from a user equipment (UE) in at least one of the scheduled TTIs that meets a processing time requirement after receiving the request at the UE.

[0018] Certain aspects of the present disclosure provide an apparatus for wireless communications by a user equipment (UE).The apparatus generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: receive a CG uplink configuration to be used for one or more configured grant (CG) uplink transmissions; receive downlink control information (DCI) scheduling multiple transmission time intervals (TTIs) for grant-based uplink transmissions, wherein a hybrid automatic repeat request (HARQ) process identifier (ID) is assigned to the grant-based transmission in the following manner: starting from the HARQ ID indicated in the DCI and incrementing the HARQ ID by 1 for each subsequent grant-based transmission; determine that at least one HARQ ID to be assigned for the corresponding grant-based uplink transmission set is configured for CG uplink transmission; receive an indication as to whether to assign a HARQ ID configured for CG uplink transmission to the grant-based transmission; assign a HARQ ID to the grant-based transmission set based on the received indication; and transmit the grant-based transmission based on the assigned HARQ ID.

[0019] Certain aspects of the present disclosure provide a device for wireless communication by a base station (BS). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: transmit a CG uplink configuration to be used for one or more configured grant (CG) uplink transmissions; transmit downlink control information (DCI) for multiple transmission time intervals (TTIs) scheduled for grant-based uplink transmissions, wherein a hybrid automatic repeat request (HARQ) process identifier (ID) will be assigned to the grant-based uplink transmission in the following manner: starting from the HARQ ID indicated in the DCI and incrementing the HARQ ID by 1 for each subsequent grant-based transmission; determine that at least one HARQ ID to be assigned for the corresponding grant-based uplink transmission set is configured for CG uplink transmission; transmit an indication of whether to assign a HARQ ID configured for CG uplink transmission for grant-based transmission; and receive grant-based uplink transmission based on the HARQ ID assigned according to the indication.

[0020] Certain aspects of the present disclosure provide a device for wireless communication by a user equipment (UE). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: receive information related to a set of (HARQ) process identifiers (IDs) to be assigned for grant-based uplink transmissions; receive downlink control information (DCI) for scheduling a plurality of transmission time intervals (TTIs) for grant-based uplink transmissions, wherein the HARQ process ID is assigned to the grant-based uplink transmission from the set of HARQ process IDs; and transmit the grant-based uplink transmission based on the assigned HARQ ID.

[0021] Certain aspects of the present disclosure provide a device for wireless communication by a base station (BS). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: transmit information related to a set of (HARQ) process identifiers (IDs) to be assigned for grant-based uplink transmissions; transmit downlink control information (DCI) for a plurality of transmission time intervals (TTIs) scheduled for grant-based uplink transmissions, wherein the HARQ process IDs will be assigned to the grant-based uplink transmissions from the set of HARQ process IDs; and receive grant-based uplink transmissions based on the assigned HARQ process IDs.

[0022] Certain aspects of the present disclosure provide a device for wireless communication by a user equipment (UE). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: receive a CG uplink configuration to be used for one or more configured grant (CG) uplink transmissions; receive downlink control information (DCI) for multiple transmission time intervals (TTIs) scheduled for transmission; determine the scrambling type for scrambling a cyclic redundancy check (CRC) portion of the DCI; determine the UE behavior associated with the CG uplink configuration based on the scrambling type; and transmit the one or more CG uplink transmissions according to the CG uplink configuration based on the determined UE behavior.

[0023] Certain aspects of the present disclosure provide a device for wireless communication by a base station (BS). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: transmit a CG uplink configuration to be used for one or more configured grants (CG) uplink transmissions; generate downlink control information (DCI) for multiple transmission time intervals (TTIs) scheduled for uplink transmissions; determine the scrambling type to be used to scramble the cyclic redundancy check (CRC) portion of the DCI; scramble the DCI using the determined scrambling type; transmit the scrambled DCI; and receive the one or more CG uplink transmissions according to the CG uplink configuration based on the scrambling type.

[0024] Certain aspects of the present disclosure provide a device for wireless communication by a user equipment (UE). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: receive a DCI according to a multi-TTI downlink control information (DCI) format that can schedule multiple transmission time intervals (TTIs) for uplink transmission, wherein at least one field of the DCI is assigned one or more bits for each of the maximum number of TTIs that can be scheduled by the DCI; determine that the DCI schedules a portion of the maximum number of TTIs that can be scheduled by the DCI; and interpret one or more unused bits assigned to the at least one field as code block group transmission information (CBGTI) for the scheduled TTI, the one or more unused bits corresponding to the remaining unscheduled portion of the maximum number of TTIs.

[0025] Certain aspects of the present disclosure provide a device for wireless communication by a base station (BS). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: transmit DCI according to a multi-TTI downlink control information (DCI) format that can schedule multiple transmission time intervals (TTIs) for uplink transmission, wherein at least one field of the DCI is assigned one or more bits for each of the maximum number of TTIs that can be scheduled by the DCI, and the DCI schedules a portion of the maximum number of TTIs that can be scheduled by the DCI; and use one or more unused bits assigned to the at least one field to transmit code block group transmission information (CBGTI) for the scheduled TTI, and the one or more unused bits correspond to the remaining unscheduled portion of the maximum number of TTIs.

[0026] Certain aspects of the present disclosure provide a device for wireless communication by a user equipment (UE). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: receive downlink control information (DCI) scheduling a plurality of transmission time intervals (TTIs) for uplink transmission, wherein the DCI includes a CSI request field containing a request for a channel state information (CSI) report; and in response to receiving the request, transmit the CSI report in at least one TTI in the scheduled TTI that meets the processing time requirement after receiving the request.

[0027] Certain aspects of the present disclosure provide a device for wireless communication by a base station (BS). The device generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: transmit downlink control information (DCI) scheduling multiple transmission time intervals (TTIs) for uplink transmission, wherein the DCI includes a CSI request field containing a request for a channel state information (CSI) report; and in response to the request, receive the CSI report from a user equipment (UE) in at least one TTI in the scheduled TTI that meets the processing time requirement after receiving the request at the UE.

[0028] Aspects of the present disclosure provide apparatuses, devices, processors, and computer-readable media for performing techniques and methods that may be complementary to operations performed by a UE (eg, a BS) described herein.

[0029] To achieve the foregoing and related ends, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of several of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to understand in detail the manner in which the above-stated features of the present disclosure are used, a more particular description of the content briefly summarized above may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

[0031] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0032] Figure 2 is a block diagram illustrating an example architecture of a distributed radio access network (RAN) in accordance with certain aspects of the present disclosure.

[0033] Figure 3 An example of a frame format for a telecommunications system is illustrated in accordance with certain aspects of the present disclosure.

[0034] Figure 4 An example assignment 400 of HARQ process IDs for UL CG and grant-based transmissions is illustrated.

[0035] Figure 5 Illustrated are example operations 500 performed by a UE for assigning a HARQ process ID for a grant-based uplink transmission (eg, a PUSCH transmission), in accordance with certain aspects of the present disclosure.

[0036] Figure 6 Illustrated are example operations 600 performed by a base station (BS) (e.g., gNB, TP, DU, etc.) for assigning a HARQ process ID for a grant-based uplink transmission (e.g., a PUSCH transmission) in accordance with certain aspects of the present disclosure.

[0037] Figure 7 Illustrated are example operations 700 performed by a UE for assigning a HARQ process ID for a grant-based transmission based on a configured set of HARQ process IDs, in accordance with certain aspects of the present disclosure.

[0038] Figure 8 Illustrated are example operations 800 performed by a BS (e.g., gNB, TP, DU, etc.) for assigning HARQ process IDs for grant-based transmissions based on a configured set of HARQ process IDs in accordance with certain aspects of the present disclosure.

[0039] Fig. 9 Illustrated are example operations 900 performed by a UE based on a scrambling type for DCI scheduling multiple TTIs / transmissions, in accordance with certain aspects of the present disclosure.

[0040] Fig.10 Illustrated are example operations 1000 performed by a BS (e.g., gNB, TP, DU, etc.) based on a scrambling type of a DCI for scheduling multiple TTIs / transmissions in accordance with certain aspects of the present disclosure.

[0041] Fig.11 Illustrated is an example new form 1100 of multi-TTI UL CG transmission in accordance with certain aspects of the present disclosure.

[0042] Fig.12 Illustrated are example operations 1200 performed by a UE for utilizing unused bits in a multi-TTI grant for CBGTI indication in accordance with certain aspects of the present disclosure.

[0043] Fig.13Illustrated are example operations 1300 performed by a BS (e.g., gNB, TP, DU, etc.) for using unused bits in a multi-TTI grant for CBGTI indication in accordance with certain aspects of the present disclosure.

[0044] Fig.14 Illustrated are example operations 1400 performed by a UE for transmitting a CSI report based on a CSI request field in a multi-TTI grant, in accordance with certain aspects of the present disclosure.

[0045] Fig.15 Illustrated are example operations 1500 performed by a BS (e.g., gNB, TP, DU, etc.) for receiving a CSI report based on a CSI request field in a multi-TTI grant in accordance with certain aspects of the present disclosure.

[0046] Fig.16 Illustrated is an example CSI report transmission 1600 triggered by a CSI request field in a multi-TTI grant in accordance with certain aspects of the present disclosure.

[0047] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation. DETAILED DESCRIPTION

[0048] A multiple transmission time interval (multi-TTI) grant generally refers to a single grant (e.g., downlink / uplink grant) that schedules multiple transport blocks (TBs) (e.g., PDSCH or PUSCH) over multiple TTIs. A multi-TTI grant that schedules multiple PUSCH transmissions across multiple TTIs may be referred to as a multi-TTI PUSCH grant or a multi-PUSCH grant. Similarly, a multi-TTI grant that schedules multiple PDSCH transmissions across multiple TTIs may be referred to as a multi-PDSCH grant.

[0049] In one aspect, a TTI includes a slot or mini-slot of an NR subframe. Multi-TTI grants are particularly useful for multi-TTI PUSCH grants in NR-based access to unlicensed spectrum (NRU). For example, without multi-TTI PUSCH grants, multiple downlink portions may have to be used to transmit multiple PUSCH grants, which will not only result in additional overhead, but will also involve multiple switches between downlink and uplink. Since NRU uses listen-before-talk (LBT) to gain access to the medium, switching between downlink and uplink can potentially result in medium loss.

[0050] Aspects of the present disclosure describe techniques for scheduling multiple TTIs using multi-TTI grants.

[0051] The following description provides examples rather than limiting the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Moreover, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality, or structures and functionality as supplements to the various aspects of the present disclosure set forth herein or in addition. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The wording "exemplary" is used herein to mean "used as an example, instance, or explanation". Any aspect described herein as "exemplary" need not be interpreted as being superior to or superior to other aspects.

[0052] The techniques described herein may be used for various wireless communication technologies, such as 3GPP Long Term Evolution (LTE), Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably.

[0053] A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network may implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the Third Generation Partnership Project (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).

[0054] New Radio (NR) is an emerging wireless communication technology being developed in collaboration with the 5G Technical Forum (5GTF). NR access (e.g., 5G NR) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80MHz or higher), millimeter wave (mmW) targeting high carrier frequency (e.g., 25GHz or higher), massive machine type communication MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission critical services targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0055] The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although various aspects may be described herein using terms typically associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations, such as 5G and later generations, including NR technologies.

[0056] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be performed. For example, the wireless communication network 100 may be an NR system (e.g., 5G NR). For example, the wireless communication network 100 may include a UE 120 configured to perform the following reference Figure 5 , 7 , 9, 12 and / or 14 to process the DCI for scheduling transmission across multiple TTIs. Similarly, the wireless communication network 100 may include a BS 110, which is configured to perform the following reference Figure 6 , 8 , 10, 13 and / or 15 described operations to generate and send (to UE 120) DCI that schedules transmission across multiple TTIs.

[0057] like Figure 1As illustrated in , the wireless communication network 100 may include several base stations (BS) 110 and other network entities. The BS may be a station that communicates with a user equipment (UE). Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a B node (NB) and / or a NB subsystem serving the coverage area, depending on the context in which the term is used. In the NR system, the term "cell" and BS, next generation B node (gNB or g B node), access point (AP), distributed unit (DU), carrier, or transmission reception point (TRP) may be used interchangeably. In some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move according to the location of the mobile BS. In some examples, the BS may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces (such as direct physical connections, wireless connections, virtual networks, or analogs using any suitable transmission networks).

[0058] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, subcarrier, frequency channel, frequency modulation, subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0059] A BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1In the example shown in FIG. 1 , BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more (e.g., three) cells.

[0060] The wireless communication network 100 may also include a relay station. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or a UE) and sends transmissions of the data and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. Figure 1 In the example shown in , a relay station 110r may communicate with a BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r. A relay station may also be referred to as a relay BS, a relay, or the like.

[0061] The wireless communication network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relays, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless communication network 100. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, a femto BS, and a relay may have a lower transmit power level (e.g., 1 watt).

[0062] The wireless communication network 100 may support synchronous or asynchronous operation. For synchronous operation, each BS may have similar frame timing, and transmissions from different BSs may be roughly aligned in time. For asynchronous operation, each BS may have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0063] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. Network controller 130 may communicate with BSs 110 via a backhaul. BSs 110 may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.

[0064] UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless communication network 100, and each UE may be stationary or mobile. UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical equipment, biometric sensor / device, wearable device (such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), transportation component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide connectivity for or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0065] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 RBs), and for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, there may be 1, 2, 4, 8, or 16 subbands, respectively. In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe. In NR, a subframe is still 1 ms, but the basic TTI is called a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16... slots), depending on the subcarrier spacing. NR RBs are 12 consecutive frequency subcarriers. NR may support a base subcarrier spacing of 15 KHz, and other subcarrier spacings may be defined relative to the base subcarrier spacing, e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. The symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.

[0066] NR may utilize OFDM with CP on both uplink and downlink and include support for half-duplex operation using TDD. Beamforming may be supported and beam directions may be dynamically configured. MIMO transmissions with precoding may also be supported. In some examples, MIMO configurations in the DL may support up to 8 transmit antennas (with multi-layer DL transmissions of up to 8 streams) and up to 2 streams per UE. In some examples, multi-layer transmissions of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells.

[0067] In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., BS) allocates resources for communication between some or all devices and equipment within its service area or cell. A scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities utilize resources allocated by the scheduling entity. A base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may be used as a scheduling entity, and resources for one or more subordinate entities (e.g., one or more other UEs) may be scheduled, and other UEs may use resources scheduled by the UE for wireless communications. In some examples, a UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh network example, UEs may communicate directly with each other in addition to communicating with a scheduling entity.

[0068] In some examples, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh networks, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal that is communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, the sidelink signal may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

[0069] exist Figure 1 In FIG. 1 , a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and / or uplink. A thin dashed line with double arrows indicates potentially interfering transmissions between a UE and a BS.

[0070] Figure 2 BS 110 and UE 120 (eg, in Figure 1 For example, antenna 252, processors 266, 258, 264, and / or controller / processor 280 of UE 120 may be configured to perform the following with reference to Figure 5 , 7 , 9, 12 and / or 14 described operations to process DCI for scheduling transmission across multiple TTIs. For example, antenna 234, processor 220, 230, 238 and / or controller / processor 240 of BS 110 may be configured to perform the following reference Figure 6 , 8, 10, 13 and / or 15 described operations to generate and send (to UE 120) DCI that schedules transmission across multiple TTIs.

[0071] At BS 110, a transmit processor 220 may receive data from a data source 212 and control information from a controller / processor 240. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 220 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide output symbol streams to modulators (MODs) 232a-232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a-232t may be transmitted via antennas 234a-234t, respectively.

[0072] At UE 120, antennas 252a-252r may receive downlink signals from BS 110 and may provide received signals to demodulators (DEMODs) 254a-254r in the transceiver, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all demodulators 254a-254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information to a controller / processor 280.

[0073] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from a data source 262 (e.g., data for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., control information for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for a reference signal (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by a demodulator 254a-254r in a transceiver (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signal from the UE 120 may be received by the antenna 234, processed by the modulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240 .

[0074] Controllers / processors 240 and 280 may direct the operation at BS 110 and UE 120, respectively. Controller / processor 240 and / or other processors and modules at BS 110 may perform or direct the execution of processes for the techniques described herein. Memories 242 and 282 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0075] Figure 3 300 for NR. The transmission timeline of each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes with indices 0 to 9, each subframe being 1 ms. Each subframe may include a variable number of slots, depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the subcarrier spacing. An index may be assigned to the symbol period in each slot. A mini slot (which may be referred to as a subslot structure) refers to a transmission time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols).

[0076] Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible) for data transmission, and the link direction for each subframe may be switched dynamically. The link direction may be based on the slot format. Each slot may include DL / UL data and DL / UL control information.

[0077] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and two-symbol PBCH. The SS block can be in a fixed time slot position (such as Figure 3 ) is transmitted in the codewords 0-3 shown in . PSS and SSS can be used by UE for cell search and acquisition. PSS can provide half-frame timing, and SS can provide CP length and frame timing. PSS and SSS can provide cell identity. PBCH carries some basic system information, such as downlink system bandwidth, timing information within a radio frame, SS burst set periodicity, system frame number, etc. SS blocks can be organized into SS bursts to support beam sweeping. Further system information (such as remaining minimum system information (RMSI), system information block (SIB), other system information (OSI)) can be transmitted on the physical downlink shared channel (PDSCH) in certain subframes. SS blocks can be transmitted up to 64 times, for example, up to 64 different beam directions for mmW. Up to 64 transmissions of SS blocks are called SS burst sets. SS blocks in SS burst sets are transmitted in the same frequency region, while SS blocks in different SS burst sets can be transmitted at different frequency positions.

[0078] Multi-TTI Grant Scheduling

[0079] As described above, a multi-transmission time interval (multi-TTI) grant generally refers to a single grant (e.g., downlink / uplink grant) that schedules multiple transport blocks (TBs) (e.g., PDSCH or PUSCH) over multiple TTIs. On the one hand, a TTI includes a time slot or mini-time slot of an NR subframe. Multi-TTI grants are particularly useful for multi-TTI PUSCH grants in NR-based access to unlicensed spectrum (NRU). For example, in the absence of multi-TTI PUSCH grants, multiple downlink portions may have to be used to transmit multiple PUSCH grants, which will not only result in additional overhead, but will also involve multiple switching between the downlink and uplink. Since the NRU uses listen-before-talk (LBT) to gain access to the medium, switching between the downlink and uplink can potentially result in medium loss.

[0080] In certain aspects, a multi-TTI grant may be of larger size (since certain scheduling parameters are not common across scheduled slots / mini-slots) and need to be indicated for each slot in the grant. Examples of such parameters include, but are not limited to, Redundancy Version (RV), New Data Indicator (NDI), Code Block Group Transmission Information (CBGTI), and HARQ Process Identifier (ID). For example, for a CBG-based transmission with 8 code block groups (CBGs) per slot and a multi-TTI grant scheduling 8 slots, 64 bits are required in the DCI just for the CBGTI parameters.

[0081] In certain aspects, certain concepts related to multi-TTI grants in licensed assisted access (LAA) may be used for scheduling using multi-TTI grants in NR.

[0082] Multi-TTI grants in LAA use DCI formats 0B / 4B according to the 3GPP LTE specifications. The LTE specifications include several definitions for multi-TTI UL grants. According to these LTE specifications, the "maxNumberOfSchedSubframes (maximum number of scheduled subframes)" parameter is configured via radio resource control (RRC) signaling. This parameter configures the maximum number of TTIs (e.g., 2 or 4 subframes) that can be scheduled by a multi-TTI grant. DCI is used to dynamically indicate how many TTIs or subframes a specific multi-TTI grant DCI actually schedules. On the one hand, based on the maximum number of scheduled TTIs configured via RRC signaling being 2 or 4 TTIs, respectively, the DCI uses 1 bit or 2 bits for the dynamic indication. On the one hand, the DCI size is independent of the number of dynamically scheduled TTIs and only varies depending on the maximum number of scheduled TTIs configured semi-statically via RRC signaling. On the one hand, the UL grant indicates the HARQ process ID of the first scheduled TTI / subframe. The HARQ process ID for the remaining scheduled subframes is determined by incrementing the HARQ process ID for each subframe. In one aspect, the RVID is selected between RVID 0 or 2. Thus, only one bit is used per HARQ process to indicate the RVID in the UL grant. Since each scheduled TTI is assigned a different HARQ process, the length of the RV field is equal to the "maxNumberOfSchedSubframes" parameter. In one aspect, one bit is used per HARQ process to indicate the NDI per HARQ process. Thus, the length of the NDI field is also equal to the "maxNumberOfSchedSubframes" parameter.

[0083] In certain aspects, some of the concepts described above as applicable to LAA may be advantageously used for scheduling using multi-TTI grants in other types of systems (e.g., NR).

[0084] In certain aspects, an RRC parameter N may be defined (e.g., N=maxNumberOfTx) that defines the maximum number of slots and / or mini-slots that are allowed to be scheduled by a multi-TTI grant. In one aspect, each TTI includes a slot or a mini-slot. In one aspect, assuming one transmission (e.g., PUSCH) per slot / mini-slot, the parameter N defines the maximum number of transmissions (e.g., the maximum number of PUSCHs), where a transmission includes new transmissions and retransmissions. In one aspect, the parameter N is similar to the "maxNumberOfSchedSubframes" parameter in LAA.

[0085] In one aspect, similar to the LAA design, the DCI for multi-TTI grants may dynamically indicate the actual number of slots / mini-slots scheduled by the multi-TTI grant (n<=N). Similarly, assuming one transmission per slot, the DCI dynamically indicates the actual number of transmissions (including new transmissions and / or retransmissions) scheduled by the multi-TTI grant. In one aspect, each transmission is assigned a different HARQ process and, thus, a different corresponding HARQ process ID. Thus, each slot / mini-slot scheduled by the multi-TTI grant corresponds to a different new transmission / retransmission and associated HARQ process ID. For example, if the DCI schedules 5 slots and / or mini-slots, HARQ process IDs 1-5 are assigned in ascending order to the transmissions scheduled in these slots / mini-slots, where HARQ process ID #1 is assigned to the transmission scheduled in the first slot / mini-slot and HARQ process ID #5 is assigned to the transmission scheduled in the fifth slot / mini-slot. In one aspect, similar to the LAA design, a multi-TTI grant may indicate the HARQ process ID of the first scheduled TTI (e.g., slot / mini-slot). The HARQ process IDs of the remaining scheduled slots / mini-slots may be determined by incrementing the HARQ process ID (and performing modulo operations as needed) for each slot / mini-slot in the scheduling order.

[0086] In one aspect, the NDI field length (eg, bit width) is equal to the maximum number of transmissions N that a multi-TTI grant is allowed to schedule, with each HARQ process ID corresponding to one bit of the NDI field.

[0087] In one aspect, if CBG-based retransmission is supported for multi-TTI grants (e.g., multi-TTI UL grants) in NR, the CBGTI may be signaled per PUSCH of retransmission, per PUSCH, or only for a fixed number of PUSCHs.

[0088] The NR standard defines a CSI request field in the DCI to request channel state information (CSI) feedback. The CSI request field is generally applicable to a single PUSCH transmission. In the context of multi-TTI grants, there is no consensus in NR on the relationship between the timing of the triggered CSI-RS and the PUSCH carrying the CSI feedback and how to determine which of the multiple scheduled PUSCHs carries the CSI feedback.

[0089] As mentioned above, similar to LAA, NR will most likely agree on having an RRC configuration parameter N that determines the maximum number of PUSCHs allowed in a multi-TTI uplink grant, while the actual number n<=N scheduled PUSCHs will be dynamically signaled in the DCI and certain fields (e.g., NDI and RV) will have a length that varies with N.

[0090] NR defines two types of uplink grants, namely, uplink (UL) configured grant (CG) and grant-based UL. UL CG transmissions are generally configured via RRC signaling. Grant-based UL transmissions are generally scheduled via DCI grants.

[0091] In certain aspects, when one or more UL CG processes are configured, some of the available HARQ process IDs are generally assigned to those UL CG processes. According to 3GPP Release 15, the HARQ process ID for a UL transmission based on a grant is indicated via DCI. For UL CG transmissions, the HARQ process ID is determined from the timing by performing a modulo operation on the number of configured HARQ processes represented by the parameter nrofHARQ-Processes (number of HARQ processes). In one aspect, the parameter nrofHARQ-Processes is configured via RRC signaling. For example, the HARQ process ID for the UL CG is given by:

[0092] HARQ process ID = [round down (CURRENT_symbol (current symbol) / periodicity)] modulo nrofHARQ-Processes,

[0093] in:

[0094] CURRENT_symbol=(SFN×numberOfSlotsPerFrame (number of time slots per frame)×numberOfSymbolsPerSlot (number of code symbols per time slot)+time slot number in the frame×numberOfSymbolsPerSlot+code symbol number in the time slot).

[0095] For example, if the number of HARQ processes = 4, consecutive UL CG transmissions will have HARQ process IDs such as 0, 1, 2, 3, 0, 1, 2, 3, ... Note that the total number of available HARQ process IDs may be greater than 4 (e.g., up to 16 HARQ process IDs). However, according to the configured parameter nrofHARQ-Processes, only the first four HARQ process IDs of the available HARQ process IDs are used for UL CG transmission opportunities. Thus, consecutive HARQ process IDs are typically assigned to each of the UL CG HARQ processes starting from the lowest HARQ process ID (e.g., starting from HARQ process ID = 0).

[0096] In certain aspects, the standard allows grant-based uplink to use the HARQ ID configured for the UL CG. However, in this case, the grant-based UL generally has a higher priority than the UL CG. For example, a transmission opportunity corresponding to the UL CG with the HARQ process ID used by the grant-based transmission is not transmitted within a pre-configured timer to avoid conflict with the grant-based transmission.

[0097] In certain aspects, when a single TTI USCH transmission is scheduled for grant-based UL, only one corresponding HARQ process ID needs to be assigned for the single TTI USCH transmission. Thus, the gNB generally has control over which HARQ process ID (e.g., of the 16 configured HARQ process IDs) it assigns for the single TTI transmission and signals the HARQ process ID in the DCI. Thus, the gNB may choose to either select a HARQ ID that is not assigned for the UL CG or may select a HARQ ID that is assigned to the UL CG.

[0098] However, in the case of grant-based multi-TTI PUSCH transmissions (e.g., scheduled by a multi-TTI uplink grant DCI), there is much less control over which HARQ process IDs are assigned for multiple grant-based scheduled transmissions than for single-TTI transmissions. The reason for the reduced control over HARQ process ID assignment for multi-TTI grants is that, as described above, multi-TTI DCI signaling notifies the HARQ process ID for the first scheduled PUSCH transmission and increments the HARQ process ID by 1 (and modulo operations as needed) for each subsequent PUSCH transmission in the scheduling order. This mechanism for HARQ process ID assignment for grant-based transmissions may result in some grant-based PUSCH transmissions being assigned HARQ process IDs that have been configured for UL CG transmissions.

[0099] Figure 4 An example assignment 400 of HARQ process IDs for UL CG and grant-based transmissions is illustrated. Figure 4 A total of 16 configured HARQ process IDs (HARQ process IDs #0-15) are shown that can be assigned for UL CG and grant-based transmissions. The example assignment 400 assumes that 4 HARQ processes are configured for UL CG (e.g., number of HARQ processes = 4). Thus, as Figure 4 As shown in , HARQ process IDs 0-3 are assigned to 4 UL CG transmissions. In addition, the example assignment 400 assumes that HARQ process IDs 7, 11, and 13 are not available for assignment by, for example, the gNB because the gNB may still be waiting for a previous transmission with these HARQ process IDs or due to processing of previously scheduled TBs with these HARQ process IDs.

[0100] Now, assuming that a multi-TTI grant schedules 4 PUSCH transmissions, and given that the current standard requires consecutive HARQ process IDs to be assigned for grant-based multi-TTI transmissions, the gNB cannot avoid assigning HARQ process IDs to these 4 grant-based PUSCH transmissions without assigning one or more HARQ process IDs 0-3 configured for UL CG. For example, while the gNB can assign HARQ process IDs (14,15,0,1) to these 4 grant-based PUSCH transmissions, the current standard does not allow HARQ process IDs (14,15,4,5) to be assigned to grant-based PUSCH transmissions. However, if the gNB wishes to not use the HARQ process IDs configured for UL CG transmissions, it may be beneficial to allow the gNB to assign non-consecutive HARQ process IDs (e.g., 14,15,4,5) to grant-based PUSCH transmissions, for example to avoid collision of UL CG transmission opportunities with grant-based UL transmission opportunities.

[0101] In certain aspects, in order to assign HARQ process IDs for multi-TTI PUSCH transmissions scheduled by a multi-TTI grant (grant-based transmissions), the gNB may be allowed to use the HARQ process IDs configured for the CG UL or not use the HARQ process IDs configured for the CG UL. In one aspect, the gNB may indicate to the UE whether the UE is to skip the HARQ process IDs corresponding to the CG UL transmissions or not to skip the HARQ process IDs corresponding to the UL CG transmissions when assigning HARQ process IDs to grant-based UL transmissions after receiving a multi-TTI grant.

[0102] Figure 5 Illustrated are example operations 500 performed by a UE for assigning a HARQ process ID for a grant-based uplink transmission (eg, a PUSCH transmission), in accordance with certain aspects of the present disclosure.

[0103] Operations 500 begin, at 502, by receiving a UL CG configuration to be used for one or more UL CG transmissions.

[0104] At 504, the UE receives a DCI scheduling a plurality of TTIs for grant-based UL transmissions, wherein a HARQ process ID is assigned to the grant-based transmissions by starting with the HARQ ID indicated in the DCI and incrementing the HARQ ID by one for each subsequent grant-based transmission.

[0105] At 506, the UE determines that at least one HARQ ID assigned for the corresponding grant-based uplink transmission set is configured for UL CG transmission;

[0106] At 508, the UE receives an indication as to whether the HARQ ID configured for UL CG transmission is to be assigned for grant-based transmission.

[0107] At 510, the UE assigns a HARQ ID for the grant-based transmission set based on the received indication.

[0108] At 512, the UE transmits a grant-based uplink transmission based on the assigned HARQ ID.

[0109] Figure 6 Illustrated are example operations 600 performed by a base station (BS) (e.g., gNB, TP, DU, etc.) for assigning a HARQ process ID for a grant-based uplink transmission (e.g., a PUSCH transmission) in accordance with certain aspects of the present disclosure.

[0110] Operations 600 begin, at 602, by transmitting a UL CG configuration to be used for one or more UL CG transmissions.

[0111] At 604, the BS transmits a DCI scheduling a plurality of TTIs for grant-based UL transmissions, wherein a HARQ process ID is to be assigned to the grant-based transmissions by starting with the HARQ ID indicated in the DCI and incrementing the HARQ ID by one for each subsequent grant-based transmission.

[0112] At 606, the BS determines that at least one HARQ ID to be assigned for the corresponding grant-based uplink transmission set is configured for CG uplink transmission.

[0113] At 608, the BS transmits an indication as to whether to assign a HARQ ID configured for CG uplink transmission for grant-based transmission.

[0114] At 610, the BS receives a grant-based uplink transmission based on the HARQ ID assigned according to the indication.

[0115] In one aspect, when the UE receives an indication that a HARQ ID configured for UL CG transmission is assigned for grant-based transmission (i.e., HARQ IDs configured for UL CG are not skipped), the UE assigns at least one HARQ ID configured for UL CG to the grant-based transmission set. Additionally or alternatively, the UE does not transmit a UL CG transmission corresponding to the at least one HARQ ID assigned for grant-based transmission. For example, referring to Figure 4 In the example assignment 400 shown in , to schedule 4 grant-based PUSCH transmissions via multi-TTIDCI, if the starting HARQ ID signaled by the DCI is 14, the HARQ ID assignment for the scheduled grant-based PUSCH transmissions can be (14, 15, 0, 1). In this context, the UE may not transmit UL CG transmissions with HARQ IDs 0 and 1.

[0116] In one aspect, when the indication includes an indication not to assign a HARQ ID configured for CG uplink transmission for a grant-based transmission (i.e., skipping the UL CG HARQ ID), the UE skips the at least one HARQ ID configured for the UL CG when assigning a HARQ ID to a grant-based transmission. For example, referring to Figure 4 In the example assignment 400 shown in , to schedule 4 grant-based PUSCH transmissions via multi-TTIDCI, if the starting HARQ ID signaled by the DCI is 14, the HARQ ID assignment for the scheduled grant-based PUSCH transmissions can be (14,15,4,5). In this context, since there is no conflict between the HARQ ID configured for CG UL transmissions and the HARQ ID assigned for grant-based transmissions, in addition to transmitting all four grant-based UL transmissions, all four UL CG transmissions can also be transmitted.

[0117] In one aspect, the UE skips HARQ IDs configured for one or more UL CG transmissions only when the UL CG transmission is indicated as active. In one aspect, the UE receives an indication from the gNB as to whether one or more configured UL CG transmissions are active. For example, according to the NR standard, for type 1 UL CG, activation is indicated via RRC signaling, and for type 2 UL CG, activation is indicated via DCI. In one aspect, when the UL CG is deactivated, the UE does not skip the HARQ process IDs configured for the UL CG when assigning HARQ IDs for grant-based UL transmissions, even though the UE may have received an explicit indication to skip the UL CG HARQ IDs.

[0118] In one aspect, the gNB may indicate via at least one of RRC signaling or DCI (e.g., via multi-TTI grant DCI) whether to skip the HARQ process ID configured for the UL CG.

[0119] 3GPP Release 15 defines a maximum of one CG configuration. However, multiple CG configurations (e.g., up to 12 CG configurations) are agreed upon in Release 16. In this context, if multiple CG configurations are configured, skipping / not skipping of UL CG HARQ process IDs may be indicated per CG configuration. Additionally or alternatively, if a particular CG configuration (e.g., among multiple configured CG configurations) is not active, skipping is not performed on the HARQ process ID corresponding to the particular CG configuration.

[0120] In certain aspects, as an alternative to indicating skip / not skip UL CG HARQ IDs, a HARQ process ID set may be configured for multi-TTI grants (e.g., via RRC signaling). The HARQ process IDs used for grant-based transmissions are assigned from the configured HARQ process ID set. In one aspect, the gNB avoids including HARQ IDs configured for UL CG in the HARQ process ID set, thereby avoiding conflicts with UL CG transmissions. In addition, configuring a HARQ process ID set for assignment to grant-based transmissions provides more control over the HARQ ID sequence signaled in the multi-TTI grant. In one aspect, the HARQ process ID set may only be applicable to grant-based transmissions scheduled by a multi-TTI grant.

[0121] Figure 7 Illustrated are example operations 700 performed by a UE for assigning a HARQ process ID for a grant-based transmission based on a configured set of HARQ process IDs, in accordance with certain aspects of the present disclosure.

[0122] Operations 700 begin by receiving, at 702, information related to a set of HARQ process IDs to be assigned for grant-based uplink transmissions.

[0123] At 704, the UE receives a DCI scheduling a plurality of TTIs for a grant-based uplink transmission, wherein a HARQ process ID is assigned to the grant-based uplink transmission from the set of HARQ process IDs.

[0124] At 706, the UE transmits a grant-based uplink transmission based on the assigned HARQ ID.

[0125] Figure 8Illustrated are example operations 800 performed by a BS (e.g., gNB, TP, DU, etc.) for assigning HARQ process IDs for grant-based transmissions based on a configured set of HARQ process IDs in accordance with certain aspects of the present disclosure.

[0126] Operations 800 begin by transmitting, at 802, information related to a set of HARQ process IDs to be assigned for grant-based uplink transmissions.

[0127] At 804, the BS transmits DCI scheduling a plurality of TTIs for grant-based uplink transmissions to which HARQ process IDs are to be assigned from the set of HARQ process IDs.

[0128] At 806, the BS receives a grant-based uplink transmission based on the assigned HARQ process ID.

[0129] In one aspect, the HARQ ID set does not include HARQ IDs assigned for UL CG transmissions. In one aspect, the UE receives information about the HARQ process ID set from the gNB via RRC signaling. In one aspect, the HARQ process ID set is used to assign HARQ process IDs only for grant-based transmissions scheduled by a multi-TTI grant.

[0130] 3GPP Release 15 defines UE behavior for granted UL and UL CG based on how the cyclic redundancy check (CRC) portion (e.g., CRC bits) of the DCI is scrambled when the UE receives DCI that schedules a single TTI. In one aspect, scrambling the DCI generally includes scrambling the cyclic redundancy check (CRC) portion of the DCI with a cellular cell radio network temporary identifier (C-RNTI) or a configured scheduling radio network temporary identifier (CS-RNTI). It can be noted that references to scrambled DCI or scrambled DCI in the present disclosure include the CRC portion of the scrambled DCI or the scrambled CRC of the DCI, respectively.

[0131] According to 3GPP Release 15, when a received DCI is scrambled with C-RNTI, the DCI is intended for scheduling grant-based UL and the HARQ ID used for the scheduled UL transmission is indicated in the DCI. If the grant-based transmission / timing scheduled by the DCI overlaps with the UL CG transmission / timing, the grant-based transmission takes precedence and the CG UL transmission is not transmitted. In addition, if the HARQ ID indicated in the DCI is one of the HARQ IDs configured for UL CG, the UL CG transmission corresponding to the same HARQ ID is not transmitted within a pre-configured time period, even if the UL CG transmission timing corresponding to the HARQ ID does not overlap with the grant-based transmission timing.

[0132] According to 3GPP Release 15, when a received DCI is scrambled with a CS-RNTI, if the NDI field in the DCI is set to zero (e.g., NDI=0), the DCI is intended to be used to activate or deactivate a UL CG (e.g., for a type 2 UL CG) and the HARQ ID indicated in the DCI is set to zero. This means that the HARQ ID indicated in the DCI will not be used. On the other hand, if the NDI field in the DCI is set to 1 (e.g., NDI=1), the DCI is intended to be used to schedule a PUSCH retransmission of a previous UL CG transmission. In this case, the HARQ process ID indicated in the DCI is used and is generally one of the HARQ IDs configured for the UL CG (e.g., the same as the HARQ ID used for the previous UL CG transmission).

[0133] The current NR standard does not define similar UE behavior for multiple TTIDCI grants scheduling multiple uplink TTIs / transmissions.

[0134] Fig. 9 Illustrated are example operations 900 performed by a UE based on a scrambling type for DCI scheduling multiple TTIs / transmissions, in accordance with certain aspects of the present disclosure.

[0135] Operations 900 begin, at 902, by receiving a UL CG configuration to be used for one or more UL CG transmissions.

[0136] At 904, the UE receives downlink control information (DCI) scheduling multiple uplink transmissions (eg, UL PUSCH transmissions) across multiple TTIs.

[0137] At 906, the UE determines a scrambling type for scrambling the CRC portion of the DCI.

[0138] At 908, the UE determines UE behavior related to the UL CG configuration based on the scrambling type.

[0139] At 910, the UE transmits one or more UL CG uplink transmissions according to the UL CG configuration based on the determined UE behavior.

[0140] Fig.10 Illustrated are example operations 1000 performed by a BS (e.g., gNB, TP, DU, etc.) based on a scrambling type of a DCI for scheduling multiple TTIs / transmissions in accordance with certain aspects of the present disclosure.

[0141] Operations 1000 begin by transmitting, at 1002, a UL CG configuration to be used for one or more UL CG transmissions.

[0142] At 1004, the BS generates a DCI that schedules multiple uplink transmissions across multiple TTIs.

[0143] At 1006, the BS determines a scrambling type to be used to scramble the CRC portion of the DCI.

[0144] At 1008, the BS scrambles the DCI using the determined scrambling type.

[0145] At 1010, the BS transmits the scrambled DCI.

[0146] At 1012, the BS receives the one or more UL CG transmissions according to the UL CG configuration based on the scrambling type.

[0147] As described above, the DCI schedules each TTI for a different transmission (eg, a PUSCH transmission) associated with a different HARQ process ID.

[0148] In certain aspects, the multi-TTIDCI may be scrambled with only the C-RNTI, and the UE does not monitor the multi-TTIDCI format with the CS-RNTI. In this context, for each of the PUSCH transmissions scheduled by the multi-TTIDCI, the gNB and UE behavior may be similar to the gNB / UE behavior defined in Release 15 for single TTI transmissions. For example, for each grant-based scheduled PUSCH transmission, if the transmission overlaps with a UL CG transmission, the grant-based transmission takes precedence and the UE does not transmit the CG UL transmission. In addition, for each grant-based scheduled PUSCH transmission, if the HARQ ID assigned to the PUSCH transmission (e.g., based on the starting PUSCH HARQ ID indicated in the DCI) is one of the HARQ IDs configured for the UL CG, the UE does not transmit a UL CG transmission corresponding to the same HARQ ID within a preconfigured time period, even if the UL CG transmission timing corresponding to the HARQ ID does not overlap with the grant-based transmission timing.

[0149] In certain aspects, multi-TTI DCI may be scrambled with either C-RNTI or CS-RNTI, and the gNB / UE behavior may be determined based on the scrambling type used for that DCI.

[0150] In one aspect, when the UE detects that the DCI is scrambled with the C-RNTI, the UE follows the same behavior as described above.

[0151] In one aspect, when the UE detects that the DCI is scrambled with the CS-RNTI, the UE behavior is decided based on the NDI field of the DCI.

[0152] In one aspect, when all NDI bits are set to zero, the UE determines that the DCI activates or deactivates the UL CG transmission on the corresponding UL CG opportunity. In this case, the UE does not use the HARQ process ID indicated in the DCI. In one aspect, the HARQ ID for a particular UL CG transmission may be assigned based on the location of the corresponding UL CG opportunity for the particular UL CG transmission.

[0153] In this context, a new form of multi-TTI UL CG transmission may be defined, which is different from the UL CG transmission currently defined in the NR standard.

[0154] Fig.11 Illustrated is an example new form 1100 of multi-TTI UL CG transmission in accordance with certain aspects of the present disclosure.

[0155] like Fig.11 As shown in , multiple CG UL transmissions can be configured on corresponding CG UL opportunities in each period according to a predetermined configured periodicity. In one aspect, when the DCI is scrambled with the CS-RNTI, a HARQ ID is assigned to each CG uplink transmission based on the position of the corresponding CG uplink opportunity of the UL CG uplink transmission. In addition, each assigned HARQ ID is from the set of HARQ IDs configured for CG uplink transmissions. For example, for Fig.11 In the example ULCG configuration shown in , the configured HARQ process ID set includes HARQ IDs 0-5. Fig.11 As shown in , HARQ process IDs 0-5 are assigned to UL CG opportunities across the transmission period, and modulo operations are performed within the configured HARQ ID set.

[0156] In one aspect, when the UE detects that a multi-TTI grant DCI is scrambled with a CS-RNTI and when all NDI bits are set to 1, the UE determines that the DCI schedules one or more UL CG retransmissions (e.g., PUSCH retransmissions) of a previous UL CG transmission. In this context, the multi-TTI grant DCI includes a starting HARQ process ID assigned to a first UL CG retransmission among the UL CG retransmissions, and wherein the HARQ ID is assigned to each subsequent UL CG retransmission among the UL CG retransmissions by incrementing the HARQ ID by 1 for the subsequent retransmission. In addition, the modulo operation is performed within a set of HARQ IDs configured for the CG uplink configuration. In one aspect, multiple PUSCH retransmissions scheduled by the multi-TTI grant DCI may correspond to multiple previous UL CG transmissions across different periods of the multi-TTI UL CG transmissions. For example, referring to Fig.11, the DCI can schedule the retransmission of initial UL CG transmissions from multiple cycles (e.g., the initial UL CG transmissions with HARQ ID (0,1) from the first cycle and the initial UL CG transmissions with HARQ ID (4,5) from the second cycle). In an alternative aspect, multiple PUSCH retransmissions scheduled by the multi-TTI grant DCI can correspond to multiple previous UL CG transmissions within a single cycle of the multi-TTI UL CG transmission. For example, referring to Fig.11 , the multi-TTI DCI can only schedule the retransmission of the initial transmission from the first cycle.

[0157] In one aspect, when the UE detects that the multi-TTI grant DCI is scrambled with CS-RNTI and when some NDI bits are set to 1 and other bits are set to 0, the UE ignores the DCI.

[0158] CBGTI indication using unused bits in the multi-TTI grant

[0159] In some aspects, the multi-TTI grant does not always schedule the maximum number of transmissions (N) that can be scheduled by the multi-TTI grant. As described above, the multi-TTI grant DCI can schedule n <= N transmissions. For example, the DCI can indicate n = 1 and only schedule one PUSCH transmission. The current NR standard has not reached an agreement on the CBGTI indication in the multi-TTI grant DCI.

[0160] In some aspects, as described above, some fields in the multi-TTI DCI (e.g., NDI and RV) can have a fixed size (e.g., fixed bit width) that depends on the maximum number of transmissions (RRC parameter N) that can be scheduled by the multi-TTI grant DCI. Thus, regardless of how many transmissions (n) out of the maximum number (N) of transmissions that can be scheduled by the multi-TTI grant DCI are actually scheduled, the NDI and RV fields have the same number of bits. However, if the multi-TTI grant DCI schedules only a portion of the N allowed transmissions (e.g., n < N), then some bits in each of the NDI and RV fields may not be used. For example, when N = 4 but n = 1, the NDI field has 4 bits (one bit per N PUSCH transmissions), and the RV field can have 4 bits or 8 bits (one or two bits per N PUSCH transmissions). In this case, since only one PUSCH is scheduled, 3 bits in the NDI field are not used, and 3 bits or 6 bits in the RV field are not used.

[0161] In some aspects, if the multi-TTIDCI schedules only a part of the maximum allowed PUSCH transmissions (e.g., when n < N), some of the unused DCI bits can be interpreted as CBGTI bits for the scheduled transmissions. For example, when only one PUSCH transmission is scheduled (e.g., when n = 1), some or all of the unused bits from the RV and NDI fields can be interpreted as CBGTI for the scheduled PUSCH transmission.

[0162] Fig.12 Illustrates example operation 1200 performed by a UE in accordance with aspects of the present disclosure for CBGTI indication using unused bits in multi-TTI grants.

[0163] Operation 1200 begins at 1202, where a downlink control information (DCI) is received according to a DCI format that can schedule multiple physical uplink shared channel (PUSCH) transmissions across multiple transmission time intervals (TTIs), wherein at least one field of the DCI is assigned one or more bits for each of the maximum number of PUSCH transmissions that can be scheduled by the DCI.

[0164] At 1204, the UE determines that the DCI schedules a part of the maximum number of PUSCH transmissions that can be scheduled by the DCI.

[0165] At 1206, the UE interprets one or more unused bits assigned to the at least one field as codeblock group transmission information (CBGTI) for the scheduled PUSCH transmission, the one or more unused bits corresponding to the remaining unscheduled part of the maximum number of PUSCH transmissions. In one aspect, the at least one field includes at least one of NDI or RV.

[0166] Fig.13 Illustrates example operation 1300 performed by a BS (e.g., gNB, TP, DU, etc.) in accordance with certain aspects of the present disclosure for CBGTI indication using unused bits in multi-TTI grants.

[0167] Operation 1300 begins at 1302, where a DCI is transmitted according to a DCI format that can schedule multiple physical uplink shared channel (PUSCH) transmissions across multiple transmission time intervals (TTIs), wherein at least one field of the DCI is assigned one or more bits for each of the maximum number of PUSCH transmissions that can be scheduled by the DCI, the DCI scheduling a part of the maximum number of PUSCH transmissions that can be scheduled by the DCI. In one aspect, the part includes one PUSCH transmission. In one aspect, the at least one field includes at least one of NDI or RV.

[0168] At 1304, the BS transmits code block group transmission information (CBGTI) for the scheduled PUSCH transmissions using one or more unused bits assigned to the at least one field, the one or more unused bits corresponding to a remaining unscheduled portion of the maximum number of PUSCH transmissions.

[0169] In certain aspects, how many unused bits (e.g., unused RV and NDI bits) are used / interpreted as CBGTI for scheduled transmissions may be based on the maximum number of code block groups configured per TB. In one aspect, according to the NR standard, the maximum number of code block groups configured per TB is given by the RRC parameter "maxCodeBlockGroupsPerTransportBlock". For example, for DCI format 0_1, the length of the CBGTI field may be 0, 2, 4, 6, or 8, as determined by the parameter "maxCodeBlockGroupsPerTransportBlock".

[0170] The same DCI format 0_1 ​​can schedule a single PUSCH or multiple PUSCHs. The maximum number of PUSCHs that the DCI can schedule can be determined by the time domain resource allocation table (the maximum number can be configured to be 8). In this way, the number of NDI bits and RV bits in the DCI format 0_1 ​​can be determined based on the configured TDRA table. For example, each PUSCH can have 1 RV bit in the case of scheduling multiple PUSCHs, or there can be 2 RV bits for the PUSCH in the case of scheduling only a single PUSCH.

[0171] The payload size of DCI format 0_1 ​​may be determined based on the largest of the DCI size for scheduling one PUSCH or the DCI size for scheduling multiple PUSCHs, via the configured TDRA table. When UL DCI 0_1 schedules more than one PUSCH, there may be no uplink shared channel (UL-SCH) indicator field, and there may be no CBGTI field (e.g., because there may be no unused bits). When UL DCI 0_1 schedules a single PUSCH, there may be a UL-SCH indicator field, and there may be a CBGTI field (unused bits that would otherwise carry information if multiple PUSCHs were scheduled).

[0172] In certain aspects, the number of code block groups may be determined for a scheduled TTI based on the number of unused bits. In an aspect, the number of unused bits depends on the RRC parameter N and the DCI design for a multi-TTI grant.

[0173] CSI reporting fields in multi-TTI grants

[0174] As mentioned in the above paragraphs, the NR standard defines a CSI request field in the DCI to request channel state information (CSI) feedback. The CSI request field is generally applicable to a single PUSCH transmission. According to 3GPP Release 15, the UE CSI calculation time for aperiodic CSI reports (e.g., requested by the CSI request field in DCI format 0_1) is based on processing times Z and Z'. The parameter Z represents Z symbols after the last symbol of the PDCCH that triggered the CSI report. The parameter Z' represents Z' symbols after the last symbol of the most recent aperiodic CSI-RS, CSI-IM or NZP CSI-RS used to perform channel / interference measurements to generate the CSI report. According to the NR standard, when the CSI request field in DCI 0_1 triggers a CSI report in a scheduled PUSCH transmission, the UE shall provide a valid CSI report if the first symbol of the PUSCH transmission starts Z symbols after the end of the last symbol of the PDCCH that triggered the CSI report, and if the first symbol of the PUSCH transmission starts Z' symbols after the end of the last symbol of the most recent aperiodic CSI-RS, CSI-IM or NZP CSI-RS used to make channel / interference measurements to generate the CSI report. In one aspect, the values ​​of Z and Z' depend on the UE reporting capabilities, subcarrier spacing, CSI report type, and other factors.

[0175] In the context of multi-TTI grants, there is no consensus in NR on the relationship between the timing of the CSI request field that triggers CSI reporting and the CSI-RS used for measurements to generate the CSI reports and the timing of the PUSCH carrying the CSI feedback, and how to determine which of the multiple scheduled PUSCHs carries the CSI feedback.

[0176] Fig.14 Illustrated are example operations 1400 performed by a UE for transmitting a CSI report based on a CSI request field in a multi-TTI grant, in accordance with certain aspects of the present disclosure.

[0177] Operations 1400 begin, at 1402, by receiving a DCI scheduling a plurality of TTIs for uplink transmission, wherein the DCI includes a CSI request field including a request for a CSI report.

[0178] At 1404, the UE transmits the CSI report in response to receiving the request in at least one of the scheduled TTIs that meets the processing time requirement after receiving the request.

[0179] Fig.15Illustrated are example operations 1500 performed by a BS (e.g., gNB, TP, DU, etc.) for receiving a CSI report based on a CSI request field in a multi-TTI grant in accordance with certain aspects of the present disclosure.

[0180] Operations 1500 begin by transmitting, at 1502, a DCI scheduling a plurality of TTIs for uplink transmission, wherein the DCI includes a CSI request field including a request for a CSI report.

[0181] At 1504, the BS receives the CSI report from the UE in response to the request in at least one of the scheduled TTIs that meets the processing time requirement after receiving the request.

[0182] In certain aspects, in the context of multi-TTI grant, if the CSI request field in the multi-TTI grant DCI triggers a CSI report, the CSI report may be transmitted by the UE in the first PUSCH transmission that meets both Z and Z' processing time requirements among the scheduled PUSCH transmissions.

[0183] In an alternative aspect, given that both processing time requirements Z and Z' are met, the UE may always transmit the CSI report in the last scheduled PUSCH transmission.

[0184] Fig.16 Illustrated is an example CSI report transmission 1600 triggered by a CSI request field in a multi-TTI grant in accordance with certain aspects of the present disclosure.

[0185] like Fig.16 As shown in , the multi-TTI grant DCI 1602 schedules 4 PUSCH transmissions 1610 and also transmits a CSI request field that triggers a CSI report. As shown, the UE may transmit a CSI report in PUSCH 3 (shown as option 1), which is the first scheduled PUSCH transmission that meets both Z and Z' processing time requirements. Additionally or alternatively, the UE may transmit a CSI report in the last scheduled PUSCH transmission (shown as option 2) that also meets both Z and Z' processing time requirements.

[0186] Example Embodiments

[0187] Embodiment 1: A device for wireless communication, comprising: a memory; and a processor coupled to the memory, the memory and the processor being configured to: receive a downlink control information (DCI) according to a downlink control information (DCI) format capable of scheduling multiple physical uplink shared channel (PUSCH) transmissions across multiple transmission time intervals (TTIs), wherein at least one field of the DCI is assigned one or more bits for each of a maximum number of PUSCH transmissions that can be scheduled by the DCI; determine that the DCI schedules a portion of the maximum number of PUSCH transmissions that can be scheduled by the DCI; and interpret one or more unused bits assigned to the at least one field as code block group transmission information (CBGTI) for the scheduled PUSCH transmissions, the one or more unused bits corresponding to the remaining unscheduled portion of the maximum number of PUSCH transmissions.

[0188] Embodiment 2: The device as described in Embodiment 1, wherein the portion includes a PUSCH transmission.

[0189] Embodiment 3: The apparatus as described in any one of embodiments 1-2, wherein the at least one field includes at least one of a new data indicator (NDI) or a redundancy version (RV).

[0190] Embodiment 4: The device as described in any one of embodiments 1-3, wherein the memory and the processor are further configured to: determine the number of unused bits to be interpreted as the CBGTI based on the maximum number of code block groups (CBGs) configured for each transport block (TB).

[0191] Embodiment 5: The apparatus as described in any one of embodiments 1-4, wherein the memory and the processor are further configured to: determine the number of code block groups used for the scheduled PUSCH transmission based on the number of unused bits.

[0192] Embodiment 6: A device for wireless communication, comprising a memory; a processor coupled to the memory, the memory and the processor being configured to: transmit a downlink control information (DCI) according to a downlink control information (DCI) format capable of scheduling multiple physical uplink shared channel (PUSCH) transmissions across multiple transmission time intervals (TTIs), wherein at least one field of the DCI is assigned one or more bits for each of a maximum number of PUSCH transmissions that can be scheduled by the DCI, and the DCI schedules a portion of the maximum number of PUSCH transmissions that can be scheduled by the DCI; and transmit code block group transmission information (CBGTI) for the scheduled PUSCH transmission using one or more unused bits assigned to the at least one field, the one or more unused bits corresponding to the remaining unscheduled portion of the maximum number of PUSCH transmissions.

[0193] Embodiment 7: The device as described in Embodiment 6, wherein the portion includes a PUSCH transmission.

[0194] Embodiment 8: The apparatus as described in any of embodiments 6-7, wherein the at least one field includes at least one of a new data indicator (NDI) or a redundancy version (RV).

[0195] Embodiment 9: The device as described in any one of embodiments 6-8, wherein the memory and the processor are further configured to: determine the number of unused bits to be used for the CBGTI based on the maximum number of code block groups (CBGs) configured for each transport block (TB).

[0196] Embodiment 10: The apparatus as described in any of Embodiments 6-9, wherein the memory and the processor are further configured to: determine the number of code block groups used for the scheduled PUSCH transmission based on the number of unused bits.

[0197] Embodiment 11: A device for wireless communication, comprising: a memory; and a processor coupled to the memory, the memory and the processor being configured to: receive a CG uplink configuration to be used for one or more configured granted (CG) uplink transmissions; receive downlink control information (DCI) for scheduling multiple uplink transmissions across multiple transmission time intervals (TTIs); determine a scrambling type for scrambling a cyclic redundancy check (CRC) portion of the DCI; determine a UE behavior associated with the CG uplink configuration based on the scrambling type; and transmit the one or more CG uplink transmissions according to the CG uplink configuration based on the determined user equipment (UE) behavior.

[0198] Embodiment 12: The apparatus of embodiment 11, wherein each TTI is scheduled for a different one of the transmissions associated with a different hybrid automatic repeat request (HARQ) process identifier (ID).

[0199] Embodiment 13: A device as described in any of Embodiments 11-12, wherein determining the scrambling type includes determining that the CRC portion of the DCI is scrambled with a cellular cell radio network temporary identifier (C-RNTI), and further includes determining, based on the scrambling type, that each of the transmissions scheduled by the DCI includes a grant-based transmission.

[0200] Embodiment 14: An apparatus as described in any one of Embodiments 11-13, wherein the UE behavior includes: for each scheduled grant-based transmission, when the grant-based transmission overlaps with the CG uplink opportunity of the CG uplink configuration, deciding not to transmit the corresponding CG uplink transmission in the CG uplink opportunity.

[0201] Embodiment 15: A device as described in Embodiment 13, wherein the UE behavior includes: for each scheduled grant-based transmission, when the hybrid automatic repeat request (HARQ) process identifier (ID) of the scheduled grant-based transmission is one of the HARQ process IDs configured for CG uplink transmission, deciding not to transmit the corresponding CG uplink transmission with the same HARQ process ID within a predetermined time period.

[0202] Embodiment 16: The apparatus of any of Embodiments 11-15, wherein determining a scrambling type comprises determining that the CRC portion of the DCI is scrambled with a configured scheduling radio network temporary identifier (CS-RNTI).

[0203] Embodiment 17: A device as described in Embodiment 16, wherein the UE behavior includes: when all bits in the new data identifier (NDI) field of the DCI are set to zero: determining that the DCI activates or deactivates the CG uplink transmission of the CG uplink configuration on the corresponding CG uplink opportunity, and determining not to use the (HARQ) process identifier (ID) indicated by the DCI.

[0204] Embodiment 18: The device as described in Embodiment 17, wherein the CG uplink configuration configures multiple different CG uplink transmissions in each cycle.

[0205] Embodiment 19: The device as described in Embodiment 18, wherein the memory and the processor are further configured to: assign a HARQ ID to the CG uplink transmission based on the position of the corresponding CG uplink opportunity of each of these CG uplink transmissions, wherein each assigned HARQ ID is from a set of HARQ IDs configured for CG uplink transmission.

[0206] Embodiment 20: The device as described in any one of embodiments 11-19, wherein the UE behavior includes:

[0207] When all bits in the new data indicator (NDI) field of the DCI are set to one, it is determined that the DCI schedules one or more retransmissions of one or more CG uplink transmissions corresponding to the DCI.

[0208] Embodiment 21: The apparatus of embodiment 20, wherein the DCI includes a start (HARQ) process identifier (ID) assigned to a first one of the retransmissions, and wherein the HARQ ID is assigned to each subsequent one of the retransmissions by incrementing the HARQ ID by 1 for the subsequent retransmission and performing a modulo operation within a set of HARQ IDs configured for the CG uplink configuration.

[0209] Embodiment 22: The apparatus of embodiment 21, wherein the one or more scheduled retransmissions include multiple retransmissions corresponding to multiple CG uplink transmissions previously transmitted in different periods defined by the CG uplink configuration.

[0210] Embodiment 23: An apparatus as described in any one of Embodiments 11-22, wherein the one or more scheduled retransmissions include multiple retransmissions corresponding to multiple CG uplink transmissions previously transmitted in a single period defined by the CG uplink configuration.

[0211] Embodiment 24: An apparatus as described in any one of Embodiments 11-23, wherein the UE behavior includes: deciding to ignore the DCI when a portion of the bits of a new data indicator (NDI) field of the DCI are set to one and the rest of the bits of the NDI field are set to zero.

[0212] Embodiment 25: A device for wireless communication, comprising: a memory; and a processor coupled to the memory, the memory and the processor being configured to: transmit a CG uplink configuration to be used for one or more configured grant (CG) uplink transmissions; generate downlink control information (DCI) to schedule multiple uplink transmissions across multiple transmission time intervals (TTIs); determine a scrambling type to be used to scramble a cyclic redundancy check (CRC) portion of the DCI; scramble the DCI using the determined scrambling type; transmit the scrambled DCI; and receive the one or more CG uplink transmissions according to the CG uplink configuration based on the scrambling type.

[0213] Embodiment 26: The apparatus of embodiment 25, wherein each TTI is scheduled for a different one of the transmissions associated with a different hybrid automatic repeat request (HARQ) process identifier (ID).

[0214] Embodiment 27: An apparatus as described in any of Embodiments 25-26, wherein when the scrambling type includes using a cellular cell radio network temporary identifier (C-RNTI) to scramble the CRC portion of the DCI, each of the transmissions scheduled by the DCI includes a grant-based transmission.

[0215] Embodiment 28: The device as described in Embodiment 27, wherein the memory and the processor are further configured to: for each scheduled grant-based transmission, when the grant-based transmission overlaps with the CG uplink opportunity of the CG uplink configuration, not receive the corresponding CG uplink transmission in the CG uplink opportunity.

[0216] Embodiment 29: An apparatus as described in any one of Embodiments 25-28, wherein the memory and the processor are further configured to: for each scheduled grant-based transmission, when a hybrid automatic repeat request (HARQ) process identifier (ID) of the scheduled grant-based transmission is one of the HARQ process IDs configured for CG uplink transmission, not receive a corresponding CG uplink transmission with the same HARQ process ID within a predetermined time period.

[0217] Embodiment 30: The apparatus of any one of Embodiments 25-29, wherein the scrambling type comprises scrambling the CRC portion of the DCI using a configured scheduling radio network temporary identifier (CS-RNTI).

[0218] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0219] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0220] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" (unless specifically stated) but "one or more". Unless otherwise specifically stated, the term "some / some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents currently or hereafter known to ordinary technicians in the art and are explicitly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims. Any element of the claim should not be interpreted under the provisions of 35 U.S.C. §112 (f), unless the element is explicitly stated using the phrase "device for..." or in the case of a method claim, the element is stated using the phrase "step for...".

[0221] The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These devices may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the accompanying drawings, these operations may have corresponding paired device-plus-function components with similar numbers.

[0222] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), 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 the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0223] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the user terminal 120 (see Figure 1 ), a user interface (e.g., a keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art and will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0224] If implemented in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separated from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor, such as a cache and / or a general register file, which may be the case. As an example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be implemented in a computer program product.

[0225] A software module may include a single instruction, or many instructions, and may be distributed over several different code segments, distributed between different programs, and distributed across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that cause a processing system to perform various functions when executed by an apparatus such as a processor. These software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded into a RAM from a hard drive. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When describing the functionality of a software module as described below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0226] Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Disks, where disks often reproduce data magnetically, and discs reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0227] Thus, some aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions that can be executed by one or more processors to perform the operations described herein. For example, a computer program product for performing the operations described herein and in Figure 4-16 Instructions for the operations explained in .

[0228] In addition, it should be appreciated that modules and / or other appropriate means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that once the storage device is coupled to or provided to a user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to a device may be utilized.

[0229] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A device for wireless communication, comprising: Memory; as well as a processor coupled to the memory, the memory and the processor being configured to: receiving a CG uplink configuration to be used for one or more configured granted CG uplink transmissions; Receiving downlink control information DCI for scheduling multiple uplink transmissions across multiple transmission time intervals TTI; Determining a scrambling type for scrambling a cyclic redundancy check CRC portion of the DCI; determining, based on the scrambling type, a user equipment (UE) behavior associated with the CG uplink configuration; as well as The one or more CG uplink transmissions are transmitted according to the CG uplink configuration based on the determined UE behavior.

2. The apparatus of claim 1, wherein each TTI is scheduled for a different one of the transmissions associated with a different hybrid automatic repeat request (HARQ) process identifier (ID).

3. The apparatus of claim 1 , wherein determining a scrambling type comprises determining that the CRC portion of the DCI is scrambled with a Cell Radio Network Temporary Identifier (C-RNTI), Further comprising determining, based on the scrambling type, that each transmission scheduled by the DCI comprises a grant-based transmission.

4. The apparatus of claim 3, wherein the UE behavior comprises: For each scheduled grant-based transmission, when the grant-based transmission overlaps with the CG uplink opportunity of the CG uplink configuration, it is decided not to transmit the corresponding CG uplink transmission in the CG uplink opportunity.

5. The apparatus of claim 3, wherein the UE behavior comprises: For each scheduled grant-based transmission, when the hybrid automatic repeat request HARQ process identifier ID of the scheduled grant-based transmission is one of the HARQ process IDs configured for the CG uplink transmission, it is decided not to transmit the corresponding CG uplink transmission with the same HARQ process ID within a predetermined time period.

6. The apparatus of claim 1, wherein determining a scrambling type comprises determining that the CRC portion of the DCI is scrambled with a configured scheduling radio network temporary identifier (CS-RNTI).

7. The apparatus of claim 6, wherein the UE behavior comprises: When all bits in the new data indicator NDI field of the DCI are set to zero: determining that the DCI activates or deactivates the CG uplink transmission of the CG uplink configuration on the corresponding CG uplink opportunity, and It is determined not to use a hybrid automatic repeat request HARQ process identifier ID indicated by the DCI.

8. An apparatus as described in claim 7, wherein the CG uplink configuration configures multiple different CG uplink transmissions in each cycle.

9. An apparatus as claimed in claim 8, wherein the memory and the processor are further configured to: assign a HARQ ID to the CG uplink transmission based on the position of the corresponding CG uplink opportunity of each of the CG uplink transmissions, wherein each assigned HARQ ID is from a set of HARQ IDs configured for the CG uplink transmission.

10. The apparatus of claim 6, wherein the UE behavior comprises: When all bits in the new data indicator NDI field of the DCI are set to 1, one or more retransmissions of one or more CG uplink transmissions corresponding to the DCI scheduling are determined.

11. An apparatus as claimed in claim 10, wherein the DCI includes a starting hybrid automatic repeat request HARQ process identifier ID assigned to a first retransmission among the retransmissions, and wherein the HARQ ID is assigned to each subsequent retransmission among the retransmissions by incrementing the HARQ ID by 1 for the subsequent transmission and performing a modulo operation within a set of HARQ IDs configured for the CG uplink configuration.

12. An apparatus as claimed in claim 11, wherein the scheduled one or more retransmissions include multiple retransmissions corresponding to multiple CG uplink transmissions previously transmitted in different periods defined by the CG uplink configuration.

13. An apparatus as described in claim 11, wherein the scheduled one or more retransmissions include multiple retransmissions corresponding to multiple CG uplink transmissions previously transmitted in a single period defined by the CG uplink configuration.

14. The apparatus of claim 6, wherein the UE behavior comprises: When a portion of the bits of the new data indicator NDI field of the DCI are set to 1 and the rest of the bits of the NDI field are set to 0, it is decided to ignore the DCI.

15. An apparatus for wireless communication, comprising: Memory; as well as a processor coupled to the memory, the memory and the processor being configured to: transmitting a CG uplink configuration to be used for one or more configured granted CG uplink transmissions; Generate downlink control information DCI for scheduling multiple uplink transmissions across multiple transmission time intervals TTI; Determining a scrambling type to be used for scrambling a cyclic redundancy check (CRC) portion of the DCI; scrambling the DCI using the determined scrambling type; transmitting the scrambled DCI; as well as The one or more CG uplink transmissions are received according to the CG uplink configuration based on the scrambling type.

16. The apparatus of claim 15, wherein each TTI is scheduled for a different one of the transmissions associated with a different hybrid automatic repeat request (HARQ) process identifier (ID).

17. The apparatus of claim 15, wherein when the scrambling type comprises scrambling the CRC portion of the DCI using a cell radio network temporary identifier (C-RNTI), each of the transmissions scheduled by the DCI comprises a grant-based transmission.

18. The device of claim 17, wherein: The memory and the processor are further configured to: For each scheduled grant-based transmission, when the grant-based transmission overlaps with a CG uplink opportunity of the CG uplink configuration, the corresponding CG uplink transmission is not received in the CG uplink opportunity.

19. The device of claim 17, wherein: The memory and the processor are further configured to: For each scheduled grant-based transmission, when the hybrid automatic repeat request HARQ process identifier ID of the scheduled grant-based transmission is one of the HARQ process IDs configured for the CG uplink transmission, a corresponding CG uplink transmission with the same HARQ process ID is not received within a predetermined time period.

20. The apparatus of claim 15, wherein the scrambling type comprises scrambling the CRC portion of the DCI using a configured scheduling radio network temporary identifier (CS-RNTI).

Images