Pruning rules for DCI repetition

Abstract

Certain aspects of the present disclosure provide techniques for utilizing and handling repeated DCI transmissions that schedule common uplink or downlink transmissions. The techniques allow the UE to decide which repeated DCI to use to determine resources for the uplink or downlink transmissions.

Description

[0001] This application is a divisional application of Chinese invention patent application 201980080970.8 (PCT / US2019 / 066344) with a filing date of December 13, 2019 and entitled “Pruning Rules for DCI Duplication”. Technical Field

[0002] Aspects of the present disclosure relate generally to wireless communications and, more particularly, to techniques for handling transmissions scheduled with repeated downlink control information transmissions (DCI). 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 simultaneously supporting communication of multiple communication devices (also referred to as user equipment (UE)). 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 5G NB, a next generation B node (gNB or g B node), a transmission reception point (TRP), etc.). A BS or DU may communicate with a set of UEs on downlink channels (eg, for transmissions from the BS or DU to the UEs) and uplink channels (eg, for transmissions from the UEs to the 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. NR (e.g., New Radio or 5G) 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 provide a method for wireless communication by a user equipment (UE). The method generally includes: detecting at least a first downlink control information (DCI) and a second DCI, both of which indicate the same or similar scheduling information about a common uplink data transmission or a downlink data transmission; selecting at least one of the first DCI or the second DCI to be used to determine scheduling parameters to be used for the uplink data transmission, or to be used for receiving the downlink data transmission, or to be used for uplink control information (UCI) transmission to provide feedback for the downlink data transmission; and utilizing the scheduling parameters to perform at least one of the following operations: processing the DL data transmission, or sending the uplink data transmission or UCI transmission.

[0009] Certain aspects provide a method for wireless communication by a network entity. The method generally includes: transmitting at least a first downlink control information (DCI) and a second DCI, the first DCI and the second DCI both indicating the same or similar scheduling information about a common uplink or downlink transmission; determining a first resource and a second resource to monitor for the uplink transmission or for an uplink control information (UCI) transmission providing feedback for the downlink transmission based on the first DCI and the second DCI; and monitoring the first resource and the second resource for the uplink transmission or the UCI transmission.

[0010] Certain aspects provide apparatus, devices, and / or computer-readable media having computer-executable code stored thereon for the techniques described herein for processing DCI for multi-TRP transmissions.

[0011] 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

[0012] 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.

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

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

[0015] Figure 3 is a diagram illustrating an example physical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

[0016] Figure 4 is a block diagram conceptually illustrating designs of example base stations (BSs) and user equipment (UEs) in accordance with certain aspects of the present disclosure.

[0017] Figure 5 is a diagram illustrating an example for implementing a communication protocol stack in accordance with certain aspects of the present disclosure.

[0018] Figure 6

[0013] Diagrams illustrating example multiple transmission reception point (TRP) transmission scenarios in accordance with certain aspects of the present disclosure are illustrated.

[0019] Figure 7 is a block diagram illustrating an example of scheduling with repeated DCIs in accordance with certain aspects of the present disclosure.

[0020] Figure 8 is a flow diagram illustrating example operations that may be performed by a UE in accordance with certain aspects of the present disclosure.

[0021] Fig. 9 is a flow diagram illustrating example operations that may be performed by a network entity in accordance with certain aspects of the present disclosure.

[0022] Fig.10 Illustrated are communications devices that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0023] Fig.11 Illustrated are communications devices that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0024] 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

[0025] Various aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for processing transmissions with multiple (repeated) downlink control information (DCI) transmissions. These techniques can be implemented in wireless systems where any type of network entity (gNB or transmit reception point TRP) uses repeated DCI to schedule transmissions to enhance reliability.

[0026] 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 equipment or methods practiced using other structures, functionalities, or structures and functionalities 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 as "exemplary" herein need not be interpreted as being superior to or superior to other aspects.

[0027] The technology described herein can be used for various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes other variants of Wideband CDMA (WCDMA) and CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS).

[0028] New Radio (NR) is an emerging wireless communication technology being developed in collaboration with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Advanced LTE (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 "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization called "3rd Generation Partnership Project 2" (3GPP2). 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 commonly 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.

[0029] New Radio (NR) access (e.g., 5G technology) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz 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.

[0030] Example Wireless Communication System

[0031] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be performed. For example, BS 110 may perform Fig. 9 The operations 900 are as part of a multi-transmission reception point (multi-TRP) session with the UE 120. In some cases, the execution Figure 8 Operation 800 of processing multiple (duplicate) DCIs received during the session.

[0032] like Figure 1As illustrated in , the wireless communication network 100 may include several base stations (BS) 110 and other network entities. A 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 the next generation B node (gNB or g B node), NR BS, 5G NB, access point (AP), or transmission reception point (TRP) may be interchangeable. 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 base station may be interconnected to each other and / or to one or more other base stations 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).

[0033] 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.

[0034] 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.

[0035] 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.

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

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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 partitioned into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0041] Although aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may be applicable to other wireless communication systems, such as NR. NR may utilize OFDM with CP on the uplink and downlink and include support for half-duplex operation using TDD. Beamforming may be supported and the beam direction may be dynamically configured. MIMO transmission with precoding may also be supported. 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. 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.

[0042] 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. The 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.

[0043] 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 a downlink and / or uplink. A thin dashed line with double arrows indicates interfering transmissions between a UE and a BS.

[0044] Figure 2 An example logical architecture of a distributed radio access network (RAN) 200 is illustrated, which may be Figure 1 200. The 5G access node 206 may include an access node controller (ANC) 202. The ANC 202 may be a central unit (CU) of the distributed RAN 200. The backhaul interface to the next generation core network (NG-CN) 204 may be terminated at the ANC 202. The backhaul interface to the adjacent next generation access node (NG-AN) 210 may be terminated at the ANC 202. The ANC 202 may include one or more TRPs 208 (e.g., cellular cells, BSs, gNBs, etc.).

[0045] The TRP 208 may be a distributed unit (DU). The TRP 208 may be connected to a single ANC (e.g., ANC 202) or more than one ANC (not illustrated). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, the TRP 208 may be connected to more than one ANC. Each of the TRPs 208 may include one or more antenna ports. The TRP 208 may be configured to serve traffic to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0046] The logical architecture of the distributed RAN 200 may support fronthaul solutions across different deployment types. For example, the logical architecture may be based on transport network capabilities (eg, bandwidth, latency, and / or jitter).

[0047] The logical architecture of the distributed RAN 200 may share features and / or components with LTE. For example, the next generation access node (NG-AN) 210 may support dual connectivity with NR and may share a common fronthaul for LTE and NR.

[0048] The logical architecture of the distributed RAN 200 may enable collaboration between and among TRPs 208, for example, within a TRP and / or across TRPs via the ANC 202. An inter-TRP interface may not be used.

[0049] Logical functions may be dynamically distributed in the logical architecture of the distributed RAN 200. Figure 5Described in more detail, the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer can be adaptively placed at the DU (e.g., TRP 208) or the CU (e.g., ANC 202).

[0050] Figure 3 An example physical architecture of a distributed RAN 300 in accordance with aspects of the present disclosure is illustrated. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU 302 may be centrally deployed. C-CU 302 functionality may be offloaded (e.g., to Advanced Wireless Services (AWS)) in an effort to handle peak capacity.

[0051] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Optionally, the C-RU 304 may host core network functions locally. The C-RU 304 may have a distributed deployment. The C-RU 304 may be close to the edge of the network.

[0052] The DU 306 may host one or more TRPs (edge ​​node (EN), edge unit (EU), radio head (RH), smart radio head (SRH), etc.) The DU may be located at the edge of the network with radio frequency (RF) functionality.

[0053] Figure 4 Explained (such as Figure 1 1 and 120, which may be used to implement aspects of the present disclosure. For example, antenna 452, processors 466, 458, 464, and / or controller / processor 480 of UE 120 may execute (or be used to execute) Figure 8 Similarly, antenna 434, processors 420, 430, 438 and / or controller / processor 440 of BS 110 may perform (or be used to perform) Fig. 9 Operation 900.

[0054] At BS 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller / processor 440. 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 420 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols (e.g., of 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 430 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) 432a to 432t. Each modulator 432 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 432a through 432t may be transmitted via antennas 434a through 434t, respectively.

[0055] At the UE 120, antennas 452a to 452r may receive downlink signals from the base station 110 and may provide received signals to demodulators (DEMODs) 454a to 454r in the transceiver, respectively. Each demodulator 454 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 456 may obtain received symbols from all demodulators 454a to 454r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller / processor 480.

[0056] On the uplink, at the UE 120, the transmit processor 464 may receive and process data from a data source 462 (e.g., data for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 480 (e.g., control information for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for a reference signal (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466, if applicable, further processed by demodulators 454a to 454r in the 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 434, processed by the modulator 432, detected by the MIMO detector 436, if applicable, and further processed by the receive processor 438 to obtain decoded data and control information sent by the UE 120. Receive processor 438 may provide decoded data to data sink 439 and decoded control information to controller / processor 440 .

[0057] Controllers / processors 440 and 480 may direct the operation at BS 110 and UE 120, respectively. Processor 440 and / or other processors and modules at BS 110 may perform or direct the execution of processes for the techniques described herein. Memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 444 may schedule UEs for data transmission on the downlink and / or uplink.

[0058] In LTE, the basic transmission time interval (TTI) or packet duration is a 1ms subframe. In NR, a subframe is still 1ms, but the basic TTI is called a time slot. A subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16... time slots), depending on the subcarrier spacing. NR RBs are 12 consecutive frequency subcarriers. NR can support a base subcarrier spacing of 15KHz, and other subcarrier spacings can be defined relative to the base subcarrier spacing, such as 30kHz, 60kHz, 120kHz, 240kHz, etc. The symbol and time slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.

[0059] Figure 5is a diagram showing an example of a frame format 500 for NR. The transmission timeline for 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).

[0060] 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.

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

[0062] In some cases, 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 coordinated 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 though 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).

[0063] The UE may operate in various radio resource configurations, including a configuration associated with transmitting a pilot using a dedicated resource set (e.g., a radio resource control (RRC) dedicated state, etc.), or a configuration associated with transmitting a pilot using a shared resource set (e.g., an RRC shared state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated resource set for transmitting a pilot signal to the network. When operating in the RRC shared state, the UE may select a shared resource set for transmitting a pilot signal to the network. In either case, the pilot signal transmitted by the UE may be received by one or more network access devices (such as an AN, or a DU, or parts thereof). Each receiving network access device may be configured to receive and measure a pilot signal transmitted on a shared resource set, and also receive and measure a pilot signal transmitted on a dedicated resource set allocated to a UE, wherein the network access device is a member of a monitoring network access device set for the UE. One or more receiving network access devices or a CU to which the receiving network access device transmits pilot signal measurements may use these measurements to identify a serving cell of the UE or initiate a change in a serving cell for one or more UEs.

[0064] Example Multi-TRP Scenario

[0065] It is expected that NR networks will use multiple transmission and reception points (TRPs) to improve reliability and capacity performance through flexible deployment scenarios. For example, allowing UEs to access wireless networks via multiple TRPs can help support increased mobile data traffic and enhance coverage. Multiple TRPs can be used to implement one or more macro cells, small cells, micro cells, or femto cells, and may include remote radio heads, relay nodes, etc. Figure 6 An example multi-TRP scenario is illustrated where two TRPs (TRP1 and TRP2) serve a UE.

[0066] like Figure 6As explained in , for multi-TRP transmission, multiple PDCCHs (each PDCCH is transmitted from a different TRP in the multiple TRPs) can be used for scheduling. Each PDCCH may include corresponding downlink control information (DCI).

[0067] For example, PDCCH1 (transmitted from TRP1) may carry a first DCI that schedules a first codeword (CW1) to be transmitted from TRP1 in PDSCH1. Similarly, PDCCH2 (transmitted from TRP2) may carry a second DCI that schedules a second codeword (CW2) to be transmitted from TRP2 in PDSCH2.

[0068] In a 2-DCI based design with multiple TRP transmissions (such as Figure 7 In the multi-TRP transmission shown in FIG, the backhaul (BH) condition for the communication between the two TRPs can be ideal (relatively small BH waiting time) or non-ideal (large BH waiting time).

[0069] For monitoring DCI transmitted from different TRPs, several different control resource sets (CORESETs) may be used. As used herein, the term CORESET generally refers to a set of parameters and a set of physical resources (e.g., a specific area on the NR downlink resource grid) used to carry PDCCH / DCI. For example, a CORESET may be similar in area to an LTE PDCCH area (e.g., the first 1, 2, 3, 4 OFDM symbols in a subframe).

[0070] In some cases, TRP differentiation on the UE side may be based on CORESET groups. CORESET groups may be defined by higher layer signaling of an index per CORESET (which may be used to group the CORESETs). For example, for 2 CORESET groups, two indices may be used (i.e., index=0 and index=1). Thus, the UE may monitor transmissions in different CORESET groups and infer that transmissions sent in different CORESET groups are from different TRPs. There may be other ways in which the concept of different TRPs may be transparent to the UE.

[0071] Example pruning rules for DCI duplication

[0072] For enhancing the reliability of PDCCH transmission (e.g., increasing the likelihood of successful reception by the UE), repetition of DCI transmissions may be used to schedule downlink or uplink transmissions, such as PDSCH or PUSCH. As used herein, the term repeated DCI refers to separate DCIs that indicate the same or similar scheduling information for the same PDSCH or PUSCH. Repetition of DCI transmissions may improve reliability by using resources and / or different transmission parameters (different precoders / beams / TCI states / TRPs / panels), via diversity.

[0073] In general, repeated DCIs can be processed separately (focusing on the repetitions) without soft combining (without combining log-likelihood ratios from different transmissions). In other words, it may be sufficient for the UE to decode at least one of the DCIs.

[0074] However, when both DCIs are decoded, the UE may be faced with a decision of which DCI to use (e.g., to determine resources for scheduled transmissions). In such situations, aspects of the present disclosure provide pruning rules that can be employed by the UE so that scheduling parameters for scheduled transmissions (PDSCH and / or PUSCH) can be unambiguously derived.

[0075] Figure 7 Two examples (labeled as Example 1 and Example 2) of repeated DCI (where DCI2 is a repetition of DCI1) are illustrated. As illustrated in Example 1, DCI2 may arrive at the same time as DCI1 (in the same time slot / symbol). Alternatively, the repeated DCI may arrive at different times (different time slots / symbols). For example, DCI 1 may arrive in the first time slot (time slot i) and DCI2 in the next time slot (time slot i+1), as shown in Example 2. However, in both cases, both DCIs occur before the scheduled PDSCH / PUSCH transmission. In addition, the repeated DCI may be in the same or different control resource set (CORESET or CORESET group) / search space set as the first DCI.

[0076] As mentioned above, although the second DCI is referred to herein as a "repeated" DCI, in some cases, the DCI fields of the two DCIs may not be exactly the same due to various factors. For example, if the DCI is sent on different time slots, its scheduling delay (k0 / k2) values ​​(used to point to scheduled PDSCH / PUSCH transmissions) may also be different to point to the same resources. The parameter k0 generally refers to the delay between a DL grant and the corresponding scheduled DL data (PDSCH) repetition, while k2 generally refers to the delay between a UL grant repetition in the DL and the corresponding scheduled UL data (PUSCH) transmission.

[0077] In addition, duplicate DCIs may be sent in different DCI formats (e.g., DCI formats 1-0 and 1-1 (for DL) or DCI formats 0-0 and 0-1 (for UL). This may occur because, for example, they may be sent / received on different CORESETs, CORESET groups, and / or search space sets configured to monitor fallback or non-fallback DCI.

[0078] Aspects of the present disclosure provide techniques that can help a UE resolve ambiguity when determining scheduling parameters (e.g., and corresponding resources) for transmissions scheduled by repeated DCIs and / or for providing feedback for transmissions scheduled by repeated DCIs. These techniques can effectively be used as "pruning rules" that a UE can apply when determining resources for corresponding uplink or downlink transmissions scheduled by a DCI to decide which DCI (of multiple / repeated DCIs) to use.

[0079] As mentioned above, in one case, the DCI fields of (two or more) repeated DCIs are exactly the same. In this case, if both DCIs are successfully decoded, the UE can simply ignore one of them. In addition to all fields being the same, the UE may still need to confirm that both DCIs are related to the same scheduled PDSCH / PUSCH transmission. This may work at least for UL DCI (DCI that schedules PUSCH). However, for DL ​​DCI (DCI that schedules PDSCH), there may be some problems in various special cases as discussed below.

[0080] One problem with DL DCI is that the PUCCH resources / configuration used to convey uplink control information (UCI) with feedback (HARQ acknowledgment) may depend on other factors (besides the DCI field values) even if the value of each DCI field is exactly the same for both DCIs.

[0081] For example, the PUCCH resources may be indicated by a 3-bit PUCCH resource indicator (PRI) in the DCI. These 3 PRI bits may thus signal up to 8 possibilities of PUCCH resources within a PUCCH resource set. However, in some cases, this may not be sufficient (e.g., even the same PRI value may not confirm that the second DCI is a repeat).

[0082] As a first example of how the PRI alone may not be sufficient for resource determination, the first PUCCH resource set (of the four sets) may contain up to 32 PUCCH resources (the size of the "resourceList" for this set may be greater than 8). In this case, the PRI alone is not sufficient to determine the PUCCH resources (r_PUCCH) used for HARQ acknowledgment transmissions. Instead, the r_PUCCH becomes a function of the PRI, the number of CCEs of the CORESET on which the DCI was received (which may be different if the two DCIs are received in different CORESETs or CORESET groups), and the index of the first CCE of the DCI repetition (which may be different for the two DCIs, even if they are in the same CORESET). It may be noted that the first set (of the four sets) can only be selected if the payload of the UCI is equal to or less than 2 bits. There is no problem with the other 3 PUCCH sets, as these sets may have up to 8 PUCCH resources (so that the PRI alone is sufficient for resource determination).

[0083] A second example of how the PRI alone may not be sufficient for resource determination is the case where the UE does not have a dedicated PUCCH resource configuration (before RRC configures the PUCCH resource set(s). Similar to the first example, in this case the set of possibilities is 16 (greater than 8), and the selection of the PUCCH resource (r_PUCCH) becomes a function of the PRI, the number of CCEs of the CORESET, and the index of the first CCE of the DCI repetition.

[0084] Aspects of the present disclosure provide techniques that may help a UE resolve ambiguity in such situations when determining resources for transmissions scheduled by repeated DCIs and / or resources for providing feedback for transmissions scheduled by repeated DCIs.

[0085] Figure 8 is a flow diagram illustrating example operations 800 for wireless communications in accordance with certain aspects of the present disclosure. Operations 800 may be performed, for example, by a UE, such as UE 120 in wireless communications network 100, for processing transmissions scheduled with DCI repetitions.

[0086] Operations 800 begin at 802 by detecting at least first downlink control information (DCI) and second DCI, both of which indicate the same or similar scheduling information about a common uplink data transmission or a downlink data transmission. As described above, repeated DCIs may have exactly the same fields, or may be different (e.g., received in different time slots and / or sent using different transmission parameters).

[0087] At 804, the UE selects at least one of the first or second DCIs to be used to determine scheduling parameters to be used for the uplink data transmission, or to be used to receive the downlink data transmission, or to be used for uplink control information (UCI) transmission to provide feedback for the downlink data transmission. As will be described in more detail below, the selection may be based on various conditions. These scheduling parameters may include various parameters and may point to resources for receiving DL transmissions or resources to be used for uplink transmissions. For DL ​​grants, these scheduling parameters may give scheduling information about both DL data reception and UL control information (UCI) transmission (e.g., indicating resources for both). For UL grants, these scheduling parameters may give scheduling information about UL data transmission.

[0088] At 806, the UE utilizes the scheduling parameters to at least one of: process the DL data transmission, or send the uplink data transmission or UCI transmission.

[0089] Fig. 9 is a flow diagram illustrating example operations 900 for wireless communications in accordance with certain aspects of the present disclosure. Operations 1200 may be performed, for example, by a network entity (such as BS 110 in wireless communication network 100, for example) or a TRP for scheduling transmissions with DCI repetitions.

[0090] Operations 900 begin at 902 with transmitting at least a first downlink control information (DCI) and a second DCI, both of which indicate the same or similar scheduling information about a common uplink or downlink transmission. Likewise, repeated DCIs may have exactly the same fields, or may be different (e.g., received in different time slots and / or sent using different transmission parameters).

[0091] At 904, the network entity determines first and second resources to monitor for the uplink transmission or for uplink control information (UCI) transmission providing feedback for the downlink transmission based on the first and second DCIs. For example, by having knowledge of DCI parameters (e.g., PRI, number of CCEs of a CORESET, and index of a first CCE), the network entity may be able to determine the r_PUCCH corresponding to each DCI.

[0092] The network entity monitors the first and second resources for the uplink transmission or UCI transmission at 906. As will be described in more detail below, the network entity may need to monitor both resource sets because it does not know which DCI was successfully decoded by the UE.

[0093] For situations where the DCI fields are identical and the UE detects both DCIs, the UE may determine that one of the above conditions exists. In such situations, the UE may select one of the DCIs as the basis for making resource determinations. The advantage of the following options is that they each provide the UE with a deterministic approach to selecting one of the DCIs.

[0094] For example, according to the first option, the UE may select a DCI that appears in a later PDCCH monitoring opportunity for determining the scheduling parameters to be used for uplink data transmission or for receiving downlink data transmission. The UE may use the parameters of the DCI or the last DCI (e.g., the number of CCEs of the CORESET and the index of the first CCE) and the PRI in the DCI to determine the PUCCH resources for HARQ acknowledgment feedback. If the two DCIs appear in the same PDCCH monitoring opportunity, the UE may select the DCI with a smaller or larger number of CCEs of the CORESETS and / or the DCI with a smaller or larger index of the first CCE (e.g., appearing first or last).

[0095] According to a second option, the UE may calculate r_PUCCH separately according to the parameters of each DCI, and select the DCI with a smaller or larger r_PUCCH (eg, based on size or occurrence time).

[0096] According to a third option, if DCI is received in different CORESETs (which may be in different CORESET groups), the default CORESET (or CORESET group) may be used to determine the selection. For example, the CORESET with the smallest or largest CORESET ID (or the CORESET group with the smallest or largest index) may be used to determine which DCI to use to determine r_PUCCH.

[0097] According to a fourth option, the UE may choose the DCI received with a higher confidence. The confidence may be determined as a function of one or more of: the channel quality of the DMRS of the two DCIs, the aggregation level (AL) of the DCIs (e.g., based on the assumption that a transmission with a higher AL should result in a more reliable transmission), the log likelihood ratio (LLR) of the two DCIs.

[0098] According to a fifth option, the UE may send PUCCH on both PUCCH resources (determined according to each DCI).

[0099] In either case, on the network side, since the network entity (e.g., gNB) does not know whether both DCIs are decoded or only one of them is decoded, it may need to monitor the resources used for both. In other words, the gNB may need to try to decode two hypotheses: one hypothesis corresponding to PUCCH according to DCI1 and another hypothesis corresponding to PUCCH according to DCI2.

[0100] As mentioned above, there are various reasons why the DCI fields of these two DCIs may not be exactly the same, but both are intended to schedule the same PDSCH / PUSCH transmission. These DCIs may have different k0 and / or k2 values ​​due to the fact that these DCIs are transmitted in different time slots, such as Figure 7 As shown in Example 2 of . DCI may be sent in different DCI formats, for example, DCI formats 1-0 and 1-1 (for DL) or DCI formats 0-0 and 0-1 (for UL).

[0101] Another reason that the DCI fields can be different is that for the DL, the gNB is allowed to indicate two different PUCCH resources / parameters (e.g., two different beams) for transmitting HARQ-A for PDSCH. Thus, the received feedback can be used as a mechanism for selecting parameters for future scheduled transmissions (e.g., selecting a better beam on PUCCH depending on which beam is better for the DCI). In other words, the resources selected for feedback can indicate which DCI was successfully decoded and / or had a larger DMRS SINR. The gNB can then know (infer) which DCI was successfully detected (based on which PUCCH parameters were used).

[0102] In the case where both DCIs are detected by the UE, the UE first needs to determine whether the second DCI is a duplicate. The determination may be based on at least one or more of the following conditions. One condition is that both DCIs point to the same time / frequency domain resources (e.g., the same time slot, symbol, RB) even if the corresponding DCI field values ​​(time / frequency domain resource assignment fields) are different. Other possible conditions include: the two DCIs have the same HARQ process ID, the same (new data indicator) NDI value, the same DCI identifier (determines DL or UL grant), the same redundancy version (RV), the same MCS, and / or the same antenna port.

[0103] After the UE determines that the second DCI is a repetition, the UE may then determine the uplink resources. For situations where the k0 / k2 values ​​are different, in principle, all other values ​​of the DCI field should also be the same. If this is the case, the UE may use either DCI. If this is not the case, the UE may still determine one of the DCIs as valid for use in determining PUCCH resources (e.g., based on any of the (five) options described above), or the UE may treat this as an error situation (and discard both DCIs).

[0104] For the case where the DCI is sent in different DCI formats, some fields may only be present in one of the DCIs (e.g., a non-fallback DCI may have more fields than a fallback DCI). In this case, the UE may still determine one of the DCIs as valid for use in determining PUCCH resources (e.g., based on any of the (five) options described above). For other fields that are only present in one of the DCIs, the UE may use the information from the two DCIs if it does not conflict, or the UE may completely ignore one of the DCIs and determine the resources similar to the options described above.

[0105] For situations where the gNB may want to indicate two different PUCCH resources and / or parameters (e.g., two different beams) for transmitting HARQ-A for PDSCH, the fields related to the PUCCH parameters (e.g., k1, PRI, DAI) may be different. In this case, the UE may still determine one of these DCIs as appropriate for use in determining the PUCCH resources (e.g., based on any of the (five) options described above). Additionally, since the value of k1 (PDSCH to HARQ Timing Indicator field) may be different, an additional option may be to select a DCI with a larger or smaller value of k1. Of course, for these various situations, combinations of these conditions may apply.

[0106] For the various scenarios described herein, the conditions for determining whether a DCI is a duplicate (and the actions based thereon) may also be more specific. For example, in addition to the conditions described, a DCI may also be considered a duplicate in certain situations for the purpose of applying the techniques described herein. For example, a DCI may be considered a duplicate only when the two DCIs are transmitted with different beams / TCI states / TRPs / panels or are received on different UE panels. The UE may determine, for example, that this is the case based on the QCL relationship of each DCI (e.g., when the two DCIs are received on two CORESETs with different TCI states). Applying this condition before a DCI is considered a duplicate can help effectively exclude performing additional processing to confirm that the DCI is a duplicate when this is not very useful.

[0107] Fig.10 The description may include instructions configured to perform operations for the techniques disclosed herein (such as, Figure 8 1000 includes various components (e.g., corresponding to means-plus-function components) of the communication device 1000 and the operation explained in the description. The communication device 1000 includes a processing system 1002 coupled to a transceiver 1008. The transceiver 1008 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1010 via the antenna 1000. The processing system 1002 can be configured to perform processing functions for the communication device 1000, including processing signals received and / or to be transmitted by the communication device 1000.

[0108] The processing system 1002 includes a processor 1004 coupled to a computer-readable medium / memory 1012 via a bus 1006. In some aspects, the computer-readable medium / memory 1012 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1004, cause the processor 1004 to perform Figure 8 , or other operations for performing the various techniques for handling duplicate DCI transmissions discussed herein. In some aspects, the computer-readable medium / memory 1012 stores code 1014 for detecting first and second DCIs; code 1016 for selecting at least one DCI in the first and second DCIs to be used to determine resources for an uplink transmission; and code 1018 for sending the uplink transmission. In some aspects, the processor 1004 has circuitry configured to implement the code stored in the computer-readable medium / memory 1012. The processor 1004 includes circuitry 1020 for detecting first and second DCIs; circuitry 1022 for selecting at least one DCI in the first and second DCIs for determining uplink resources; and circuitry 1024 for sending the uplink transmission.

[0109] Fig.11 The description may include instructions configured to perform operations for the techniques disclosed herein (such as, Fig. 9 1100 includes a communication device 1100 including various components (e.g., corresponding to means-plus-function components) of the operations illustrated in 1100. The communication device 1100 includes a processing system 1102 coupled to a transceiver 1108. The transceiver 1108 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1110 via the antenna 1100. The processing system 1102 may be configured to perform processing functions for the communication device 1100, including processing signals received and / or to be transmitted by the communication device 1100.

[0110] The processing system 1102 includes a processor 1104 coupled to a computer-readable medium / memory 1112 via a bus 1106. In some aspects, the computer-readable medium / memory 1112 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1104, cause the processor 1104 to perform Fig. 9 or other operations for performing the various techniques for multi-TRP transmission discussed herein. In some aspects, the computer-readable medium / memory 1112 stores code 1114 for transmitting first and second DCIs; code 1116 for determining first and second resources to monitor for uplink transmissions; and code 1118 for monitoring the determined resources. In some aspects, the processor 1104 has a circuit system configured to implement the code stored in the computer-readable medium / memory 1112. The processor 1104 includes a circuit system 1120 for transmitting the first and second DCIs; a circuit system 1122 for determining the first and second resources to monitor for uplink transmissions; and a circuit system 1124 for monitoring the determined resources.

[0111] Example aspects

[0112] Aspect 1: A method for wireless communication by a user equipment (UE), comprising: detecting at least a first downlink control information (DCI) and a second DCI, both of which indicate the same or similar scheduling information about a common uplink data transmission or a downlink data transmission; selecting at least one DCI in the first DCI or the second DCI to be used to determine scheduling parameters to be used for the uplink data transmission, or to be used for receiving the downlink data transmission, or to be used for uplink control information (UCI) transmission to provide feedback for the downlink data transmission; and using these scheduling parameters to perform at least one of the following operations: processing the DL data transmission, or sending the uplink data transmission or UCI transmission.

[0113] Aspect 2: The method of aspect 1, wherein the DCIs are detected in different transmission time intervals (TTIs).

[0114] Aspect 3: The method of aspect 2, wherein the DCIs span at least one of different time slots or symbols.

[0115] Aspect 4: The method according to any one of aspects 1-3, wherein if the value of each field of the first DCI and the second DCI is the same, the UE determines that the second DCI is a repetition of the first DCI.

[0116] Aspect 5: A method as in aspect 4, wherein the determination is based on a PUCCH resource indicator (PRI) in the DCI and at least one of: the number of control channel elements (CCEs) of a control resource set (CORESET) in which each DCI is received, or the index of the first CCE of each DCI.

[0117] Aspect 6: The method of any one of aspects 1-5, wherein the selecting comprises: selecting the first DCI or the second DCI that occurs in a physical downlink control channel (PDCCH) monitoring opportunity that occurs later.

[0118] Aspect 7: A method as in any of Aspects 1-6, wherein the first DCI and the second DCI appear in the same physical downlink control channel (PDCCH) monitoring opportunity, and the selection is based on at least one of: the number of control channel elements (CCE) of a control resource set (CORESET) for each DCI, or the index of the first CCE of each DCI.

[0119] Aspect 8: The method according to any one of Aspects 1-7, wherein the UE:

[0120] A first index pointing to the resources used for the uplink control transmission is calculated based on the parameters of the first DCI; a second index pointing to the resources used for the uplink control transmission is calculated based on the parameters of the second DCI; and an index to be used to determine the resources to be used for the uplink control transmission is selected based on a function of the first index and the second index.

[0121] Aspect 9: A method as in any one of Aspects 1-8, wherein the first DCI and the second DCI are detected in different control resource sets (CORESETs), each CORESET is in a different CORESET group, and the first DCI or the second DCI is selected based on the CORESET group of its corresponding CORESET.

[0122] Aspect 10: The method of any one of aspects 1-9, wherein the first DCI or the second DCI is selected based on a corresponding detection confidence level.

[0123] Aspect 11: The method of aspect 10, wherein the detection confidence level of each DCI is determined based on at least one of the following: channel quality of a demodulation reference signal (DMRS), an aggregation level (AL), or a log-likelihood ratio (LLR) value.

[0124] Aspect 12: The method of any one of aspects 1-11, wherein the UE determines different resources to be used for the uplink transmission based on both the first DCI and the second DCI, and the UE uses the different resources to send the uplink transmission.

[0125] Aspect 13: The method of any one of aspects 1-12, wherein the value of at least one field of the first DCI and the second DCI is different, and the UE is configured to determine that the second DCI is a repetition of the first DCI based on one or more conditions.

[0126] Aspect 14: A method as in Aspect 13, wherein the conditions include at least one of the following: the scheduling information about the first DCI and the scheduling information about the second DCI both point to the same time domain and frequency domain resources; the first DCI and the second DCI indicate at least one of the following: the same hybrid automatic repeat request (HARQ) process ID, the same NDI value, or the same DCI identifier; or the first DCI and the second DCI have the same redundancy version (RV), modulation and coding scheme (MCS), or antenna port.

[0127] Aspect 15: The method as in any one of Aspects 1-14 further includes: ignoring the two DCIs in the following circumstances: the scheduling information about the first DCI and the scheduling information about the second DCI both point to the same time domain and frequency domain resources; and the first DCI and the second DCI indicate different hybrid automatic repeat request (HARQ) process IDs or NDI values.

[0128] Aspect 16: The method of any one of aspects 1-15, wherein the UE uses the information from the two DCIs when the information does not conflict.

[0129] Aspect 17: The method of any one of aspects 1-16, wherein the UE is configured to select the DCI based on a value of a PDSCH to HARQ timing indicator field.

[0130] Aspect 18: A method as in any of Aspects 1-17, wherein the one or more conditions include at least one of the following: determining that the first DCI and the second DCI are transmitted using different beams, transmission configuration indicator (TCI) states, transmission reception points (TRPs) or panels; or determining that the DCIs are received on different UE panels, or are received on different control resource sets (CORESETs) with different TCI states from different CORESET groups.

[0131] Aspect 19: A method for wireless communication by a network entity, comprising: transmitting at least a first downlink control information (DCI) and a second DCI, the first DCI and the second DCI both indicating the same or similar scheduling information about a common uplink or downlink transmission; determining, based on the first DCI and the second DCI, a first resource and a second resource to be monitored to search for the uplink transmission or to search for an uplink control information (UCI) transmission that provides feedback for the downlink transmission; and monitoring the first resource and the second resource to search for the uplink transmission or the UCI transmission.

[0132] Aspect 20: The method of Aspect 19, further comprising: adjusting one or more transmission parameters based on the monitoring.

[0133] Aspect 21: A method as in any one of Aspects 19-20, wherein the first DCI and the second DCI are sent using different transmission parameters; and the network entity selects the transmission parameters for the first DCI or the second DCI for subsequent transmission depending on which of the first resources or the second resources the uplink transmission or UCI transmission is detected.

[0134] Aspect 22: A method as in Aspect 21, wherein the first DCI and the second DCI are sent using different beams; and the network entity selects the beam based on the first resource or the second resource in which the uplink transmission or UCI transmission is detected.

[0135] Aspect 23: A device for wireless communication by a user equipment (UE), comprising: a device for detecting at least a first downlink control information (DCI) and a second DCI, both of which indicate the same or similar scheduling information about a common uplink data transmission or a downlink data transmission; a device for selecting at least one DCI in the first DCI or the second DCI to be used to determine scheduling parameters to be used for the uplink data transmission, or to be used for receiving the downlink data transmission, or to be used for uplink control information (UCI) transmission to provide feedback for the downlink data transmission; and a device for utilizing the scheduling parameters to perform at least one of the following operations: processing the DL data transmission, or sending the uplink data transmission or UCI transmission.

[0136] Aspect 24: An apparatus for wireless communications by a network entity, comprising: a device for transmitting at least a first downlink control information (DCI) and a second DCI, both of which indicate the same or similar scheduling information about a common uplink or downlink transmission; a device for determining, based on the first DCI and the second DCI, a first resource and a second resource to be monitored to search for the uplink transmission or to search for an uplink control information (UCI) transmission that provides feedback for the downlink transmission; and a device for monitoring the first resource and the second resource to search for the uplink transmission or UCI transmission.

[0137] Aspect 25: An apparatus for wireless communication by a user equipment (UE), comprising at least one processor, the at least one processor being configured to: detect at least a first downlink control information (DCI) and a second DCI, both of which indicate the same or similar scheduling information about a common uplink data transmission or a downlink data transmission; select at least one of the first DCI or the second DCI to be used to determine scheduling parameters to be used for the uplink data transmission, or to be used to receive the downlink data transmission, or to be used for uplink control information (UCI) transmission to provide feedback for the downlink data transmission; and utilize these scheduling parameters to perform at least one of the following operations: process the DL data transmission, or send the uplink data transmission or UCI transmission; and a memory coupled to the at least one processor.

[0138] Aspect 26: An apparatus for wireless communications by a network entity, comprising at least one processor, the at least one processor being configured to: transmit at least a first downlink control information (DCI) and a second DCI, the first DCI and the second DCI both indicating the same or similar scheduling information about a common uplink or downlink transmission; determine, based on the first DCI and the second DCI, a first resource and a second resource to be monitored to search for the uplink transmission or to search for an uplink control information (UCI) transmission that provides feedback for the downlink transmission; and monitor the first resource and the second resource to search for the uplink transmission or the UCI transmission; and a memory coupled to the at least one processor.

[0139] Aspect 27: A computer-readable medium having stored thereon instructions for the following operations: detecting at least a first downlink control information (DCI) and a second DCI, both of which indicate the same or similar scheduling information about a common uplink data transmission or a downlink data transmission; selecting at least one DCI in the first DCI or the second DCI to be used to determine scheduling parameters to be used for the uplink data transmission, or to be used for receiving the downlink data transmission, or to be used for uplink control information (UCI) transmission to provide feedback for the downlink data transmission; and utilizing these scheduling parameters to perform at least one of the following operations: processing the DL data transmission, or sending the uplink data transmission or UCI transmission.

[0140] Aspect 28: A computer-readable medium having stored thereon instructions for the following operations: transmitting at least a first downlink control information (DCI) and a second DCI, both of which indicate the same or similar scheduling information about a common uplink or downlink transmission; determining, based on the first DCI and the second DCI, a first resource and a second resource to be monitored to search for the uplink transmission or to search for an uplink control information (UCI) transmission that provides feedback for the downlink transmission; and monitoring the first resource and the second resource to search for the uplink transmission or the UCI transmission.

[0141] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be changed without departing from the scope of the claims.

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

[0143] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up 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.

[0144] 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 those of ordinary skill in the art and are expressly 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...".

[0145] 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.

[0146] 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.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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, for performing the operations described herein and in Figure 8 and / or Fig. 9 Instructions for the operations explained in .

[0152] 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.

[0153] 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 method for wireless communication by a user equipment (UE), comprising: detecting at least first downlink control information (DCI) and second DCI, wherein: The second DCI is a repetition of the first DCI, and The first DCI and the second DCI both indicate the same scheduling information about a common uplink data transmission or a downlink data transmission; selecting at least one of the first DCI or the second DCI to be used for determining a parameter to be used for the uplink data transmission or to be used for receiving the downlink data transmission; and The DL data transmission is processed or the uplink data transmission is sent based on the determined parameters.

2. The method of claim 1, wherein the first DCI and the second DCI span at least one of different time slots or codewords.

3. The method of claim 1, wherein: The first DCI and the second DCI occur in the same physical downlink control channel (PDCCH) monitoring opportunity; and The selection is based on the index of the first CCE of each DCI.

4. The method of claim 1, wherein the DCI is detected in different transmission time intervals (TTIs).

5. The method of claim 1, wherein the selecting comprises: The first DCI or the second DCI occurring in a physical downlink control channel (PDCCH) monitoring opportunity occurring later is selected.

6. The method of claim 1, wherein the UE: Calculating a first index pointing to a resource for the uplink control transmission based on a parameter of the first DCI; and calculating a second index pointing to a resource for the uplink control transmission based on a parameter of the second DCI; and An index to be used for determining resources to be used for the uplink control transmission is selected based on a function of the first index and the second index.

7. The method of claim 1, wherein: The first DCI and the second DCI are detected in different CORESETs, each CORESET being in a different CORESET group; and The first DCI or the second DCI is selected based on the CORESET group of its corresponding CORESET.

8. The method of claim 1, wherein: The first DCI or the second DCI is selected based on a corresponding detection confidence level.

9. The method of claim 8, wherein the detection confidence level of each DCI is determined based on at least one of: channel quality of a demodulation reference signal (DMRS), an aggregation level (AL), or a log-likelihood ratio (LLR) value.

10. The method of claim 1, wherein: The UE determines different resources to be used for the uplink transmission based on both the first DCI and the second DCI; and The UE sends the uplink transmission using the different resources.

11. The method of claim 1, wherein: The value of at least one field of the first DCI and the second DCI is different; and The UE is configured to determine, based on one or more conditions, that the second DCI is a repetition of the first DCI.

12. The method of claim 11, wherein the condition comprises at least one of the following: The scheduling information about the first DCI and the scheduling information about the second DCI both point to the same time domain and frequency domain resources; The first DCI and the second DCI indicate at least one of: a same hybrid automatic repeat request (HARQ) process ID, a same NDI value, or a same DCI identifier; or The first DCI and the second DCI have the same redundancy version (RV), modulation and coding scheme (MCS), or antenna port.

13. The method of claim 11, further comprising: These two DCIs are ignored in the following cases: The scheduling information about the first DCI and the scheduling information about the second DCI both point to the same time domain and frequency domain resources; and The first DCI and the second DCI indicate different hybrid automatic repeat request (HARQ) process IDs or NDI values.

14. The method of claim 11, wherein the UE uses the information from the two DCIs when the information does not conflict.

15. The method of claim 11, wherein the UE is configured to select the DCI based on a value of a PDSCH to HARQ timing indicator field.

16. The method of claim 11, wherein the one or more conditions include at least one of the following: determining that the first DCI and the second DCI are transmitted using different beams, transmission configuration indicator (TCI) states, transmission reception points (TRPs), or panels; or It is determined that the DCI is received on different UE panels, or on different CORESETs from different CORESET groups with different TCI states.

17. The method of claim 1, wherein the same scheduling information comprises similar scheduling information.

18. An apparatus for wireless communication by a user equipment (UE), comprising: at least one memory, wherein executable instructions are stored in the at least one memory; as well as one or more processors configured to execute the executable instructions to cause the device to: detecting at least first downlink control information (DCI) and second DCI, wherein: The second DCI is a repetition of the first DCI, and The first DCI and the second DCI both indicate the same scheduling information about a common uplink data transmission or a downlink data transmission; selecting at least one of the first DCI or the second DCI to be used for determining a parameter to be used for the uplink data transmission or to be used for receiving the downlink data transmission; and The DL data transmission is processed or the uplink data transmission is sent based on the determined parameters.

19. The apparatus of claim 18, wherein the first DCI and the second DCI span at least one of different slots or symbols.

20. The apparatus of claim 18, wherein: The first DCI and the second DCI occur in the same physical downlink control channel (PDCCH) monitoring opportunity; and The selection is based on the index of the first CCE of each DCI.

21. The apparatus of claim 18, wherein the DCI is detected in different transmission time intervals (TTIs).

22. The apparatus of claim 18, wherein in order to select at least one of the first DCI or the second DCI, the one or more processors are configured to cause the apparatus to select the first DCI or the second DCI that occurs in a physical downlink control channel (PDCCH) monitoring opportunity that occurs later.

23. The device of claim 18, wherein the one or more processors are configured to cause the device to: Calculating a first index pointing to a resource for the uplink control transmission based on a parameter of the first DCI; as well as Calculating a second index pointing to a resource for the uplink control transmission based on a parameter of the second DCI; as well as An index to be used for determining resources to be used for the uplink control transmission is selected based on a function of the first index and the second index.

24. The apparatus of claim 18, wherein: The first DCI and the second DCI are detected in different CORESETs, each CORESET being in a different CORESET group; and The first DCI or the second DCI is selected based on the CORESET group of its corresponding CORESET.

25. The apparatus of claim 18, wherein: The value of at least one field of the first DCI and the second DCI is different; and The device is configured to determine, based on one or more conditions, that the second DCI is a repetition of the first DCI.

26. The apparatus of claim 25, wherein the condition comprises at least one of: The scheduling information about the first DCI and the scheduling information about the second DCI both point to the same time domain and frequency domain resources; The first DCI and the second DCI indicate at least one of: a same hybrid automatic repeat request (HARQ) process ID, a same NDI value, or a same DCI identifier; or The first DCI and the second DCI have the same redundancy version (RV), modulation and coding scheme (MCS), or antenna port.

27. The apparatus of claim 25, further comprising: These two DCIs are ignored in the following cases: The scheduling information about the first DCI and the scheduling information about the second DCI both point to the same time domain and frequency domain resources; and The first DCI and the second DCI indicate different hybrid automatic repeat request (HARQ) process IDs or NDI values.

28. The apparatus of claim 25, wherein the apparatus is configured to select the DCI based on a value of a PDSCH to HARQ timing indicator field.

29. The apparatus of claim 25, wherein the one or more conditions include at least one of: determining that the first DCI and the second DCI are transmitted using different beams, transmission configuration indicator (TCI) states, transmission reception points (TRPs), or panels; or It is determined that the DCI is received on different UE panels, or on different CORESETs from different CORESET groups with different TCI states.

Images