Semi-persistent Scheduling (SPS) for Multiple Transmitter Receiver Points (TRPs) Based on Multiple DCIs

Abstract

Certain aspects of the present disclosure provide techniques for handling semi-persistent scheduling (SPS) transmissions activated by downlink control information (DCI) transmissions in a system with multiple transmitter receiver points (TRPs).

Description

[0001] Priority claim

[0002] This application claims priority to U.S. Application No. 16 / 914,068, filed on June 26, 2020, which claims priority to and the benefit of U.S. Provisional Application No. 62 / 868,576, filed on June 28, 2019, and No. 62 / 914,305, filed on October 11, 2019, the entire contents of which are expressly incorporated by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for handling semi-persistent scheduling (SPS) transmissions activated by downlink control information (DCI) transmissions in a system having multiple transmitter receiver points (TRPs). Background Art

[0004] Wireless communication systems are widely used 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 the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) system, the Advanced LTE (LTE-A) system, the Code Division Multiple Access (CDMA) system, the Time Division Multiple Access (TDMA) system, the Frequency Division Multiple Access (FDMA) system, the Orthogonal Frequency Division Multiple Access (OFDMA) system, the Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and the Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system, etc.

[0005] In some examples, a wireless multiple access communication system may include multiple base stations (BSs), each of which is capable of simultaneously supporting communications for multiple communication devices, which are 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 eNodeB (eNB). In other examples (e.g., in a next generation, new radio (NR) or 5G network), a wireless multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.), which communicate with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more DUs communicating with a CU may define an access node (e.g., which may be referred to as a BS, a 5G NB, a next generation NodeB (gNB or gNodeB), 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).

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

[0007] However, as the demand for mobile broadband access continues to increase, 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

[0008] 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, certain features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description of the Invention," it will be understood how the features of the present disclosure provide advantages including the following: Improved communication between access points and stations in a wireless network.

[0009] Certain aspects provide a method for wireless communication by a user equipment (UE). The method generally includes: detecting at least one downlink control information (DCI) from each of at least a first transmit reception point (TRP) and a second TRP, each DCI activating an SPS physical downlink shared channel (PDSCH) transmission according to a semi-persistent scheduling (SPS) configuration, detecting an SPS PDSCH transmission from each of the first TRP and the second TRP, determining a codebook resource for providing confirmation feedback for the SPS PDSCH transmission, and providing confirmation feedback for the SPS PDSCH transmission based on the determination.

[0010] Certain aspects provide a method for wireless communication by a user equipment (UE). The method generally includes receiving configuration signaling of at least a first semi-persistent scheduling (SPS) configuration and a second SPS configuration associated with at least a first control resource set (CORESET) and a second CORESET, detecting at least one downlink control information (DCI) activating or releasing the first SPS configuration or the second SPS configuration, and determining whether the activation or release is for the first SPS configuration or the second SPS configuration.

[0011] Certain aspects provide a method for wireless communication by a user equipment (UE). The method generally includes receiving configuration signaling of at least a first semi-persistent scheduling (SPS) configuration and a second SPS configuration associated with at least a first control resource set (CORESET) and a second CORESET, each CORESET being associated with a CORESET group identified by an index, detecting at least one downlink control information (DCI) activating the first SPS configuration or the second SPS configuration in at least one of the first CORESET or the second CORESET, and determining a data scrambling identity of one or more SPS physical downlink shared channels (PDSCHs) for the activated SPS configuration based on the CORESET group in which the DCI is detected.

[0012] Certain aspects provide components, means, and / or computer-readable media having computer-executable code stored thereon for performing the techniques described herein.

[0013] To accomplish 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 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

[0014] Therefore, in order that the manner in which the features of the present disclosure set out above may be understood in detail, a more particular description of what has been 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 therefore not to be considered limiting of the scope of the present disclosure, as the description may allow other equally effective aspects.

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

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

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

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

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

[0020] Figure 6 Figure illustrates an example of a frame format for a New Radio (NR) system, in accordance with certain aspects of the present disclosure.

[0021] Figure 7 is a diagram illustrating an example multiple transmit reception point (TRP) transmission scenario according to certain aspects of the present disclosure.

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

[0023] Figure 9-11A The diagram shows a method in which certain aspects of the present disclosure can be applied. Figure 8 Example scenario of the operation.

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

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

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

[0027] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for processing semi-persistent scheduling (SPS) transmissions activated by downlink control information (DCI) transmissions in a system having multiple transmitter receiver points (TRPs).

[0028] The following description provides examples, but is not a limitation of the scope, applicability or examples stated in the claims. Without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may omit, replace or add various processes or components as appropriate. For example, the described method may be performed in an order different from the described order, and various steps may be added, omitted or combined. Similarly, the features described with respect to certain examples may be combined in certain 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 disclosure is intended to cover devices or methods practiced using other structures, functionality or structures and functionality as additions to the various aspects of the disclosure set forth herein or in addition to the various aspects of the disclosure set forth herein. It should be understood that any aspect of the present disclosure may be embodied by one or more elements in the claims. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily to be interpreted as being more preferred or advantageous than other aspects.

[0029] 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 generally 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), IEEE802.20, Flash-OFDMA, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS).

[0030] New Radio (NR) is an emerging wireless communication technology developed together with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are UMTS versions using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). Cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The technology described herein can be used for the wireless networks and radio technologies mentioned above and other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used herein to describe aspects, aspects of the present disclosure may be applied to communication systems based on other generations, such as 5G and subsequent generations, including NR technologies.

[0031] New Radio (NR) access (e.g., 5G technology) can support various wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) for high carrier frequency (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) for non-backward compatible MTC technology, and / or mission critical 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.

[0032] Example Wireless Communication System

[0033] Figure 1 An example wireless communication network 100 is shown in which aspects of the present disclosure may be implemented. For example, Figure 1 The UE 120 may be configured to perform the following reference Figure 8 , 12 and / or the operations described in 13 to handle SPS transmission in a multi-TRP system.

[0034] The wireless communication network 100 may be, for example, a New Radio (NR) or 5G network. Figure 8 , 12 As described in the operations of 13, BS 110 may involve multiple transmission and reception points (multi-TRP) transmission of UE 120.

[0035] like Figure 1 As shown, the wireless communication network 100 may include multiple 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 to a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a Node B (NB) and / or a NB subsystem serving this coverage area, depending on the context in which the term is used. In the NR system, the term "cell" and the next generation NodeB (gNB or gNodeB), NR BS, 5G NB, access point (AP) or transmit receive point (TRP) may be interchangeable. In some examples, the cell may not necessarily be fixed, 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 the following: direct physical connection, wireless connection, virtual network, or similar items using any suitable transmission network.

[0036] Generally speaking, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency can 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 can be deployed.

[0037] 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., a radius of several kilometers) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, 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 1 In the example shown, 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.

[0038] The wireless communication network 100 may also include a relay station. A relay station is a station that receives data and / or other information from an upstream station (e.g., a BS or a UE) and sends 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, 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.

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

[0040] The wireless communication network 100 may support synchronous operation or asynchronous operation. For synchronous operation, the BSs may have similar frame timing and may approximately align transmissions from different BSs in time. For asynchronous operation, the BSs may have different frame timing and may not align transmissions from different BSs in time. The techniques described herein may be used for both synchronous and asynchronous operation.

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

[0042] UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless communication network 100, and each UE may be fixed 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.), vehicle 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 as 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. that can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, which can be narrowband IoT (NB-IoT) devices.

[0043] 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 commonly referred to as frequency tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are sent in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, while the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (referred to as 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), so that for a system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, there may be 1, 2, 4, 8 or 16 subbands, respectively.

[0044] 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 configuration in DL may support up to 8 transmit antennas with multi-layer DL transmission with up to 8 streams and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE may be supported. Aggregation of multiple cells may support up to 8 serving cells.

[0045] In some examples, access to the air interface can 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 may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs may utilize resources scheduled by the UE for wireless communication. In some examples, a UE may be used as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In a mesh network example, in addition to communicating with a scheduling entity, UEs may also communicate directly with each other.

[0046] 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 designed 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.

[0047] Figure 2 The figure shows an example logical architecture of a distributed radio access network (RAN) 200, which can be Figure 1 The distributed RAN 200 is implemented in the wireless communication network 100 shown. 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 terminate at the ANC 202. The backhaul interface to the adjacent next generation access node (NG-AN) 210 may terminate at the ANC 202. The ANC 202 may include one or more TRPs 208 (e.g., cells, BSs, gNBs, etc.).

[0048] 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 shown). 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. The TRPs 208 may each include one or more antenna ports. The TRPs 208 may be configured to provide services to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0049] 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 the transmitting network capabilities (eg, bandwidth, latency, and / or jitter).

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

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

[0052] Logical functions can be dynamically distributed in the logical architecture of the distributed RAN 200. Figure 5 Described 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 may be appropriately placed at the DU (e.g., TRP 208) or the CU (e.g., ANC 202).

[0053] Figure 3 The figure illustrates an example physical architecture of a distributed RAN 300 according to aspects of the present disclosure. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU 302 may be centrally deployed. To handle peak capacity, the C-CU 302 functionality may be offloaded (e.g., to Advanced Wireless Services (AWS)).

[0054] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Alternatively, 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 network edge.

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

[0056] Figure 4 The diagram shows a BS 110 and a UE 120 (eg, Figure 1For example, antenna 452, processor 466, 458, 464 and / or controller / processor 480 of UE 120 may be used to perform the present disclosure with respect to Figure 8 , 12 and / or various operations described in 13.

[0057] 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 the following: 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, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS), etc. The 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 corresponding 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.

[0058] At the UE 120, antennas 452a to 452r can receive downlink signals from the base station 110 and can provide received signals to demodulators (DEMODs) in transceivers 454a to 454r, respectively. Each demodulator 454 can condition (e.g., filter, amplify, downconvert, and digitize) the corresponding received signal to obtain input samples. Each demodulator can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 456 can obtain received symbols from all demodulators 454a to 454r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. The receive processor 458 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 460, and provide decoded control information to the controller / processor 480.

[0059] On the uplink, at the UE 120, a transmit processor 464 may receive and process data from a data source 462 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 480 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for reference signals (e.g., for 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 a demodulator in the transceivers 454a to 454r (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. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller / processor 440 .

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

[0061] Figure 5The figure shows a diagram 500 showing an example for implementing a communication protocol stack according to aspects of the present disclosure. The communication protocol stack shown can be implemented by a device operating in a wireless communication system such as a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 illustrates a communication protocol stack including an RRC layer 510, a PDCP layer 515, an RLC layer 520, a MAC layer 525, and a PHY layer 530. In various examples, the layers of the protocol stack can be implemented as separate modules of software, parts of a processor or ASIC, parts of non-collocated devices connected by a communication link, or various combinations thereof. Co-location and non-co-location implementations can be used, for example, in a protocol stack for a network access device (e.g., AN, CU, and / or DU) or a UE.

[0062] The first option 505-a illustrates a split implementation of the protocol stack, where the implementation of the protocol stack is split between a centralized network access device (e.g., Figure 2 ANC 202 in the system) and distributed network access equipment (e.g., Figure 2 In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by a central unit, while the RLC layer 520, the MAC layer 525, and the PHY layer 530 may be implemented by the DU. In various examples, the CU and the DU may be co-located or non-co-located. The first option 505-a may be useful in macro cell, micro cell, or pico cell deployments.

[0063] The second option 505-b shows a unified implementation of the protocol stack, where the protocol stack is implemented in a single network access device. In the second option, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 can each be implemented by an AN. The second option 505-b can be useful in, for example, a femtocell deployment.

[0064] Regardless of whether the network access device implements part or all of the protocol stack, the UE can implement the entire protocol stack as shown in 505-c (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525 and PHY layer 530).

[0065] In LTE, the basic transmission time interval (TTI) or packet duration is a 1ms subframe. In NR, the 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 basic subcarrier spacing of 15KHz, and other subcarrier spacings such as 30kHz, 60kHz, 120kHz, 240kHz, etc. can be defined relative to the basic subcarrier spacing. The symbol and time slot lengths are proportional to the subcarrier spacing. The CP length also depends on the subcarrier spacing.

[0066] Figure 6 is a diagram showing an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be segmented into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be segmented into 10 subframes, each of which is 1 ms and has an index of 0 to 9. 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. The symbol periods in each slot may be assigned an index. A microslot, 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).

[0067] Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible direction) 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.

[0068] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and two symbols of PBCH. It can be transmitted at fixed time slot positions (such as Figure 6SS blocks are sent in the codewords 0-3 shown in the figure. 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 identification. PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set periodicity, system frame number, etc. SS blocks can be organized into SS bursts to support beam sweeping. Further system information such as remaining minimum system information (RMSI), system information block (SIB), other system information (OSI) can be sent on the physical downlink shared channel (PDSCH) in certain subframes. SS blocks can be sent up to sixty-four times, for example, up to sixty-four different beam directions for mmW. The maximum sixty-four transmissions of SS blocks are called SS burst sets. SS blocks in SS burst sets are sent in the same frequency domain, while SS blocks in different SS burst sets can be sent at different frequency positions.

[0069] In some cases, two or more subordinate entities (e.g., UEs) can communicate with each other using side link signals. Practical applications of such side link communications may include public safety, proximity services, UE-to-network relays, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical networks, and / or various other suitable applications. Generally speaking, a side link 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 this communication through a scheduling entity (e.g., UE or BS) (even if the scheduling entity can be used for scheduling and / or control purposes). In some examples, a licensed spectrum (different from a wireless local area network that typically uses an unlicensed spectrum) may be used to communicate side link signals.

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

[0071] Example SPS for multi-TRP scenario based on multi-DCI

[0072] NR networks are expected to utilize multiple transmit and receive 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 services and enhance coverage. Multiple TRPs can be used to implement one or more macro cells, small cells, micro cells, or femto cells, and can include remote radio heads, relay nodes, etc. Figure 7 An example multi-TRP scenario is illustrated where two TRPs (TRP 1 and TRP 2) serve a UE.

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

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

[0075] In the case of multiple TRP transmission based on 2-DCI (such as Figure 7 In the multi-TRP transmission) design shown, the backhaul (BH) conditions for communication between two TRPs can be ideal (relatively small BH delay) or non-ideal (large BH delay).

[0076] In order to monitor DCI sent from different TRPs, multiple different control resource sets (CORESETs) can be used. As used herein, the term CORESET generally refers to a set of physical resources (e.g., a specific area on the NR downlink resource grid) and a set of parameters for carrying PDCCH / DCI. For example, the area of ​​a CORESET can be similar to the LTE PDCCH area (e.g., the first 1, 2, 3, 4 OFDM symbols in a subframe).

[0077] 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 for each CORESET, which may be used to group the CORESETs. For example, for 2 CORESET groups, two indexes may be used (i.e., index=0 and index=1). Thus, the UE may monitor transmissions in different CORESET groups and infer that transmissions issued in different CORESET groups are from different TRPs. Otherwise, the concept of different TRPs may be transparent to the UE.

[0078] There are various options for HARQ-Ack (Ack / Nack or A / N for short) feedback corresponding to PDSCH transmissions scheduled by different TRPs (e.g., two TRPs in the example of two CORESET groups). One option is to provide joint A / N feedback (carried on the same PUCCH), which may be applicable for deployments with ideal BH. The joint A / N in this case may be similar to the downlink carrier aggregation (DL CA) case, where the joint downlink assignment index (DAI) counting process for type 2 feedback, and candidate PDSCH occasions may be independent for each TRP (e.g., each CORESET group for type 1).

[0079] Another option is to use separate A / N feedback (e.g., carried on separate PUCCHs), which may be applicable to both ideal and non-ideal BH deployments. If A / N is sent in the same slot, the A / N codebooks may be separated based on the CORESET group in which the DCI scheduling the PDSCH is received. For type 1 codebook (semi-static) feedback, the determination of candidate PDSCH reception opportunities may be independent across two (or more) CORESET groups. For type 2 codebook (dynamic) feedback, the DAI counting process may be independent for DCI received in different CORESET groups.

[0080] In some systems (e.g., Rel 15), each PUCCH group may support only one active DL SPS configuration (process). In such cases, there may be at least two forms of A / N feedback for SPS: for PDSCH SPS reception and for SPS release. Typically, if the UE receives a PDSCH without receiving the corresponding PDCCH, or if the UE receives a PDCCH indicating an SPS PDSCH release, the UE may generate a corresponding HARQ-ACK information bit. In a given time slot, only 1 bit of HARQ-ACK feedback is generated for PDSCH SPS reception. In other words, the UE does not expect to be in a scenario where HARQ-ACK information is sent for more than one SPS PDSCH reception in the same PUCCH.

[0081] For type 1 codebook feedback, the position of the HARQ-Ack bits in the codebook corresponds to the actual received DL SPS. The position in the type-1 HARQ-ACK codebook for the HARQ-ACK information corresponding to the SPS PDSCH release may be the same as the corresponding SPS PDSCH reception (e.g., only one of them is expected to be used for A / N reporting in the codebook).

[0082] For Type 2 codebook feedback, the UE may append a 1-bit A / N to the end of the HARQ-Ack codebook for PDSCH SPS reception (e.g., if SPS is activated and the UE is configured to receive SPS PDSCH in slot n-K1, where K1 is the PDSCH-to-HARQ-feedback timing value and n is the PUCCH slot in which the HARQ-Ack codebook will be sent). For SPS release, there may be a separate A / N feedback if the corresponding DCI is received with a K1 value pointing to the same slot as the PUCCH transmission for A / N, and the location is determined based on the DAI in the dynamic codebook.

[0083] If the UE sends HARQ-ACK information corresponding only to PDSCH reception without corresponding PDCCH (e.g., SPS PDSCH reception), the PUCCH resources for the corresponding PUCCH transmission with HARQ-ACK information can be provided by n1PUCCH-AN (configured as part of SPS-Config). Otherwise (if the codebook also contains A / N for PDSCH scheduled by DCI or Ack for SPS release), the PUCCH Resource Indicator (PRI) field in DCI can be used for PUCCH resource selection.

[0084] Some systems (e.g., Rel-16) may be designed to support multiple active DL SPS configurations per PUCCH group. For example, to support multiple service types, multiple SPS configurations may be supported for a single TRP (which are not necessarily associated with multiple TRPs). In such cases, there are various options for the details of HARQ-Ack codebook construction and PUCCH resource selection.

[0085] Aspects of the present disclosure can help address various challenges of providing A / N feedback for SPS transmissions in multi-TRP scenarios (e.g., A / N feedback corresponding to PDSCH transmissions scheduled according to SPS configuration or for SPS release without corresponding PDCCH transmissions). Generally, the feedback approach can be considered as two cases: separate A / N feedback for different TRPs or joint A / N feedback. In addition, type 1 (semi-static) and type 2 (dynamic) codebook types are possible.

[0086] Aspects of the present disclosure may provide techniques for solving different scenarios using these approaches and codebook types. According to the first scenario (scenario 1), only one SPS configuration is allowed for each cell group. According to the second scenario (scenario 2), two SPS configurations may be allowed for each cell group, but these SPS configurations may belong to different TRPs. According to the third scenario (scenario 3), multiple SPS configurations are allowed for each cell group, and these SPS configurations may belong to the same or different TRPs. Scenario 3 can be considered as a generalized version of Scenario 2, where each TRP may have more than one SPS configuration. Within a TRP, how to handle A / N feedback sent for multiple SPSs may be similar to the case of multiple SPS configurations for a single TRP.

[0087] Aspects of the present disclosure may also help address SPS activation, SPS release, and PDSCH scrambling for SPS in multi-TRP scenarios.

[0088] Figure 8 The diagram illustrates example operations 800 for processing SPS transmissions in a multi-TRP scenario in accordance with certain aspects of the present disclosure. Operations 800 may be performed, for example, by a UE (e.g., such as UE 120 in wireless communication network 100) for processing SPS PDSCH transmissions.

[0089] Operations 800 begin at 802 by detecting at least one downlink control information (DCI) on each of at least a first control resource set (CORESET) and a second CORESET, each DCI being transmitted according to a semi-persistent scheduling (SPS) configuration activating an SPS physical downlink shared channel (PDSCH).

[0090] At 804, the UE decodes the SPS PDSCH transmission on each of the first CORESET and the second CORESET.In some cases, the CORESETs may be grouped (eg, where CORESETs in the same group have the same index) and TRPs may be differentiated based on the CORESET group.

[0091] At 806, the UE determines a codebook construction of one or more codebooks for providing confirmation feedback for SPS PDSCH transmission. For example, the UE may determine whether to use separate codebooks (providing separate feedback for different SPS transmissions on different CORESET groups) or a single codebook (providing joint feedback for different SPS transmissions on different CORESET groups). At 808, the UE provides confirmation feedback for SPS PDSCH transmission according to the determination.

[0092] As described above, the technology presented in this article can be applied to the various scenarios mentioned above.

[0093] For example, for one SPS configuration (scenario 1), in the case of separate feedback (case 1), the A / N bits for SPS PDSCH reception or for SPS release may be allowed in only one of the two codebooks, where the codebook is determined according to one of various alternatives. For example, according to a first alternative, a codebook associated with the first CORESET group (e.g., index 0) may be used. In some cases, the SPS activation / release may be constrained so that it can only be received in the PDCCH in the first CORESET group. According to a second alternative, which codebook may have the A / N for SPS PDSCH reception / release may depend on determining on which CORESET group the SPS activation / release is received.

[0094] For one SPS configuration (scenario 1), the existing rules for the HARQ-Ack codebook may be sufficient in case of joint feedback (case 2). However, in such a case, there may be a constraint that SPS activation / release can only be received in the PDCCH in one of the CORESET groups.

[0095] For the case of two SPS configurations corresponding to different TRPs (scenario 2), in the case of separate feedback (case 1), the A / N bits for SPS PDSCH reception or for SPS release can be carried in the corresponding codebook, which is determined based on the CORESET group in which the DCI for activating / releasing the SPS configuration is received.

[0096] Fig. 9The figure shows an example of two SPS configurations corresponding to different TRPs in the case of separate feedback (scenario 2, case 1). As shown, the UE can receive a first DCI with an indication of K1=2 activating SPS PDSCH transmission on the first CORESET group (e.g., CORESET with index 0). Parameter K1 generally refers to a scheduling parameter indicating the timing of transmission from PDSCH to the corresponding HARQ feedback.

[0097] The UE may also receive a second DCI with an indication of K1=2, activating an SPS configuration associated with a second CORESET group (e.g., CORESET with index 1). In this case, separate PUCCH resources may be used to provide A / N feedback for SPS PDSCH transmissions received in different CORESET groups. For example, as shown, the UE may send a first PUCCH carrying A / N bits from a first codebook (codebook 1 associated with CORESET group 1) and a second PUCCH carrying A / N bits from a second codebook (codebook 2 associated with CORESET group 2).

[0098] It can be noted that the regular PDSCH (scheduled by the corresponding PDCCH) is not Fig. 9 The A / N feedback for SPS release is also not shown in Fig. 9 Shown in.

[0099] For the case of two SPS configurations corresponding to different TRPs (scenario 2) and joint feedback (case 2), type 1 and type 2 codebook types can be supported. For type 1 codebook, up to 2 bits of A / N can be allowed in the codebook, and these two bits correspond to the two SPS configurations. The position of the A / N bit is determined separately based on the candidate PDSCH opportunities corresponding to the two CORESET groups; among all A / N bits corresponding to the CORESET group, the position of A / N (whether for SPS PDSCH reception or SPS release) is based on the actual received DL SPS.

[0100] Fig.10 The figure shows an example of two SPS configurations corresponding to different TRPs in the case of separate feedback using a type 1 codebook (scenario 2, case 2). As shown, the UE may again receive a first DCI activating SPS PDSCH transmission with an indication of K1=2 on the first CORESET group (e.g., CORESET with index 0).

[0101] The UE may also receive a second DCI activating an SPS configuration associated with a second CORESET group (e.g., CORESET with index 1), but with an indication of K1=3. In this case, the different values ​​of K1 result in SPS PDSCH transmissions occurring at different times (slots n-3 and n-2) within the A / N reporting window being acknowledged with a single PUCCH transmission in the same slot n. As shown, entries in the joint codebook may have bits for acknowledging SPS PDSCH transmissions issued in different CORESET groups.

[0102] It can be noted that the DCI for the regular PDSCH (scheduled by the corresponding PDCCH) is not in Fig.10 , and the A / N feedback for SPS release is also not shown.

[0103] Scenario 2, Case 2, using Type 2 codebook, a maximum of 2 bits of A / N may be allowed in the codebook. For example, these two bits may correspond to two SPS configurations. In this case, Fig.11 As shown, the UE may append a 2-bit A / N to the end of the HARQ-Ack codebook (if both SPS are activated and the UE is configured to receive the SPS PDSCH in time slot n-K1, where K1 is for the SPS configuration (they may have different K1 values, such as Fig.11 In such a case, the first bit may correspond to an SPS transmission associated with a first CORESET group (e.g., from a first TRP) and the second bit may correspond to an SPS associated with a second CORESET group (e.g., a second TRP).

[0104] Fig.11 The figure shows an example of two SPS configurations corresponding to different TRPs in the case of separate feedback using a type 2 codebook (scenario 2, case 2). As shown, the UE may again receive a first DCI with an indication of K1=2 activating SPS PDSCH transmission on the first CORESET group (e.g., CORESET with index 0), and receive a second DCI activating the SPS configuration associated with the second CORESET group (e.g., CORESET with index 1), but with an indication of K1=3. In this case, two A / N bits corresponding to the two SPS configurations are appended to the codebook entry.

[0105] In the figure, the value (x, y) represents the counter DAI and the total DAI as indicated in the DCI for scheduling PDSCH. For example, in time slot n-3, the regular PDSCH (1, 1) indicates that the counter DAI is 1 and the total DAI is 1. Also, it can be noted that the DCI for the regular PDSCH and the A / N for SPS release are not shown.

[0106] This same approach can be applied to scenario 3, but as described above, there may be more than one SPS configuration per TRP (per CORESET group).For SPS release, the position in the codebook may depend on the DAI value.

[0107] There are various options for the joint dynamic HARQ-ACK codebook among multiple TRPs (m-TRPs). Fig.11 The examples shown in and described above (for a joint dynamic codebook) assume that the joint DAI count (both counter DAI and total DAI) spans two TRPs. In this case, the counter DAI is counted jointly across two TRP / CORESET groups (e.g., different higher layer indices configured by the CORESET), and the total (accumulated) DAI counts the total number of DCIs in PDCCH monitoring opportunities across CCs and TRPs.

[0108] In an alternative approach, a counter DAI is counted (tracked) per TRP / CORESET group (per value of higher layer index configured per CORESET), and the total DAI (for each TRP / value of higher layer index configured per CORESET) may count the total number of DCIs in PDCCH monitoring opportunities across CCs for each TRP / CORESET group. In this case, the HARQ-ACK information bits may be concatenated by increasing order of TRPs (i.e., per different higher layer indexes configured per CORESET, if configured). In this case, the dynamic HARQ-Ack codebook consists of two sub-codebooks corresponding to two DAI operations (per TRP). Although it may be possible to use Fig.11 The codebook option shown (to append the two A / N bits corresponding to the SPSPDSCH reception of the two TRPs to the end of the two subcodebooks), but Fig.11A Different options are shown.

[0109] Fig.11A An example is shown considering scenario 2 (two SPS configurations corresponding to different TRPs), case 2 (joint feedback), and a dynamic codebook with counter DAI (cDAI) and total DAI (tDAI) counted per TRP / CORESET group.

[0110] As shown, there may essentially be two sub-codebooks in the joint codebook. The first sub-codebook corresponds to the first TRP / first higher layer index value configured according to the CORESET (based on the first set of cDAI / tDAI values), and the second sub-codebook corresponds to the second TRP / second higher layer index value configured according to the CORESET (based on the second set of cDAI / tDAI values). For SPS PDSCH reception, a maximum of 2 bits of A / N are allowed in the codebooks corresponding to the two SPS configurations. Fig.11A As shown, the UE may append 1 bit A / N to the end of the first subcodebook (if SPS is activated and associated with the first TRP / first CORESET group, and the UE is configured to receive the SPS PDSCH in slot n-K1, where K1 is the PDSCH to HARQ feedback timing value for the SPS configuration and n is the PUCCH slot in which the HARQ-Ack codebook will be sent). Similarly, for the SPS PDSCH associated with the second TRP / second CORESET group, the UE may append 1 bit A / N to the end of the second subcodebook.

[0111] Fig.11 The codebook approach shown can be extended to the case where there may be more than one SPS configuration per TRP (per CORESET group). In this case, for any TRP / CORESET group with more than one SPS configuration, the UE can append more than 1 bit of A / N to the sub-codebook.

[0112] As described above, aspects of the present disclosure may also help address SPS activation, SPS release, and PDSCH scrambling for SPS in multi-TRP scenarios.

[0113] Fig.12 The diagram illustrates example operations 1200 for handling SPS activation and SPS release in a multi-TRP scenario in accordance with certain aspects of the present disclosure. Operations 1200 may be performed, for example, by a UE (e.g., such as UE 120 in wireless communication network 100) for handling SPS PDSCH transmissions.

[0114] Operations 1200 begin at 1202 by receiving configuration signaling of at least a first semi-persistent scheduling (SPS) configuration and a second SPS configuration associated with at least a first control resource set (CORESET) and a second CORESET. At 1204, the UE detects at least one downlink control information (DCI) that activates or releases the first SPS configuration or the second SPS configuration. At 1206, the UE determines whether the activation or release is for the first SPS configuration or the second SPS configuration.

[0115] Each SPS configuration, once activated, may result in multiple (e.g., periodic) SPS PDSCH transmissions. In some cases, the UE may operate under the assumption of separate activation / release for different SPS configurations. For scenario 1, there may be certain restrictions on receiving DCI for SPS activation / release only in one of the CORESET groups (this is related to the A / N feedback discussed in more detail above).

[0116] For scenario 2, according to the first option, the two SPS configurations can be associated with a higher layer index (RRC parameter in SPS-Config) corresponding to the CORESET group (index = 0 and index 1). If SPS activation / release is received in the PDCCH in the CORESET group (higher layer index in CORESET), the corresponding SPS (with the same index in SPS-Config) is activated / released. According to the second option, the two SPS configurations can be associated with two different IDs through high-layer signaling (RRC parameters in SPS-Config). In such cases, the ID can be explicitly indicated in the activation / release DCI. For activation, the ID can be indicated via the PRI field in the DCI (for example, although the PRI field is not used for activation when the PUCCH resource is given by the RRC parameter n1PUCCH-AN, the PRI is used to release the DCI). The second option can also be used for scenario 3, but instead of two IDs, multiple IDs.

[0117] In some cases, a combination of Option 1 and Option 2 may be used. For example, both the SPS ID (0, 1, 2, ...) and the index (0 and 1) may be defined in the SPS-configuration. In such cases, different SPS configurations may not have the same ID and the same index at the same time (but may have the same ID or the same index). In some cases, the ID may be used to distinguish different SPS configurations within the same TRP, while the index is used to distinguish the TRP. Both the explicit DCI signaling of the ID and the CORESET group in which the DCI is received may be used to determine which SPS is activated / released.

[0118] Fig.13 The diagram illustrates example operations 1300 for processing PDSCH scrambling for SPS, in accordance with certain aspects of the present disclosure. Operations 1300 may be performed, for example, by a UE (eg, such as UE 120 in wireless communication network 100) for processing SPS PDSCH transmissions.

[0119] Operations 1300 begin at 1302 by receiving configuration signaling of at least a first semi-persistent scheduling (SPS) configuration and a second SPS configuration associated with at least a first control resource set (CORESET) and a second CORESET, each CORESET being associated with a CORESET group identified by an index. Each SPS configuration, once activated, may result in multiple (periodic) SPS PDSCH transmissions.

[0120] At 1304, the UE detects at least one downlink control information (DCI) transmitted from at least one of the first TRP or the second TRP to activate the SPS PDSCH. At 1306, the UE determines a data scrambling identifier for the PDSCH based on the CORESET group in which the DCI is detected.

[0121] In some systems, at least for eMBB with M-DCI NCJT, in order to generate different PDSCH scrambling sequences, enhanced RRC configuration may be supported to configure multiple dataScramblingIdentityPDSCHs. How to associate dataScramblingIdentityPDSCH with TRP may still be an issue. For grant-based PDSCH (non-SPS), the association of dataScramblingIdentityPDSCH can be based on the CORESET group in which the scheduling DCI is received. In this case, one dataScramblingIdentityPDSCH can correspond to one index (e.g., from two indices that are also configured according to the CORESET, such as index = 0, index = 1). When a DCI scheduling PDSCH is received in a CORESET with a higher layer index (0 or 1), the corresponding dataScramblingIdentityPDSCH is used for PDSCH scrambling.

[0122] However, there are challenges for SPS because there is no corresponding DCI / PDCCH for scheduling PDSCH. Alternatively, aspects of the present disclosure propose that the DCI activating SPS can be used to determine the CORESET group (index) and therefore determine the corresponding dataScramblingIdentityPDSCH. For SPS PDSCH reception (without corresponding PDCCH), it can be processed as described above, where one dataScramblingIdentityPDSCH corresponds to an index (e.g., from two indexes that are also configured according to the CORESET, such as index=0, index=1). In addition, the SPS configuration may correspond to different TRPs associated with different indexes (in SPS-config, the index can be 0 or 1 corresponding to two CORESET groups). The dataScramblingIdentityPDSCH associated with the CORESET group in which the SPS activation DCI is received can be used for SPS PDSCH scrambling.

[0123] Example Embodiments

[0124] Embodiment 1: A method for wireless communication performed by a user equipment (UE), comprising: detecting at least one downlink control information (DCI) on each of at least a first control resource set (CORESET) and a second CORESET, each DCI activating an SPS physical downlink shared channel (PDSCH) transmission according to a semi-persistent scheduling (SPS) configuration; decoding a corresponding SPS PDSCH transmission; determining a codebook construction of one or more codebooks for providing confirmation feedback for the SPS PDSCH transmission; and providing confirmation feedback for the SPS PDSCH transmission based on the determination.

[0125] Embodiment 2: A method as in Embodiment 1, wherein: the DCI received in the first CORSET is sent from a first transmitter receiver point (TRP); and the DCI received in the second CORSET is sent from a second TRP.

[0126] Embodiment 3: A method as in Embodiment 1 or 2, wherein: the first CORESET is associated with a first CORESET group; the second CORESET is associated with a second CORESET group; the one or more codebooks include a codebook associated with the first CORESET group; and the UE provides confirmation feedback for each of the SPS PDSCH transmissions according to the codebook associated with the first CORESET group.

[0127] Embodiment 4: The method as in any one of Embodiments 1 to 3 further includes receiving signaling indicating codebook construction.

[0128] Embodiment 5: A method as described in any one of Embodiments 1 to 4, wherein: the first CORESET is associated with a first CORESET group; the second CORESET is associated with a second CORESET group; the one or more codebooks include a first codebook and a second codebook associated with the first CORESET group and the second CORESET group; and the UE provides confirmation feedback for each of the SPS PDSCH transmissions according to the first codebook or the second codebook based on the CORESET group in which the DCI activating the SPS PDSCH transmission is detected.

[0129] Embodiment 6: The method of embodiment 5 further includes receiving signaling for each CORESET indicating an index of which CORESET group the CORESET belongs.

[0130] Embodiment 7: The method as in Embodiment 5 or 6 further includes: detecting a DCI for releasing an SPS configuration associated with one of the first CORESET or the second CORESET; and determining a CORESET associated with the released SPS configuration based on the CORESET group in which the DCI for releasing the SPS configuration is detected.

[0131] Embodiment 8: The method of embodiment 7 further includes providing confirmation feedback for the release according to a codebook selected based on a CORESET group in which the DCI for releasing the SPS PDSCH transmission is detected.

[0132] Embodiment 9: The method of any one of Embodiments 1 to 8, wherein the determined codebook structure comprises a common codebook whose entries have bits for acknowledging SPS PDSCH transmissions detected on each of the first CORESET and the second CORESET.

[0133] Embodiment 10: A method as in Embodiment 9, wherein: the common codebook comprises a type 1 hybrid automatic repeat request (HARQ) confirmation codebook; the first CORESET is associated with the first CORESET group; the second CORESET is associated with the second CORESET group; and the position of the bit is determined individually based on the candidate PDSCH timings within the reporting window, which are determined individually for each of the CORESET groups.

[0134] Embodiment 11: A method as in Embodiment 9 or 10, wherein: the common codebook comprises a type 2 hybrid automatic repeat request (HARQ) confirmation codebook; bits are appended to codebook entries; one of the bits is used to confirm an SPS PDSCH transmission detected on a first CORESET; and another of the bits is used to confirm an SPS PDSCH transmission detected on a second CORESET.

[0135] Embodiment 12: The method of embodiment 11 further includes: detecting a DCI sent by releasing the SPS PDSCH on at least one of the first CORESET and the second CORESET; and providing confirmation feedback for the release via one or more bits, wherein the position of the entry within the codebook depends at least in part on a downlink assignment index (DAI) value.

[0136] Embodiment 13: The method as in any one of Embodiments 1 to 12 further includes: receiving at least two SPS configurations for at least one of the first CORESET or the second CORESET.

[0137] Embodiment 14: A method for wireless communication performed by a user equipment (UE), comprising: receiving configuration signaling of at least a first semi-persistent scheduling (SPS) configuration and a second SPS configuration associated with at least a first control resource set (CORESET) and a second CORESET, detecting at least one downlink control information (DCI) for activating or releasing the first SPS configuration or the second SPS configuration, and determining whether the activation or release is for the first SPS configuration or the second SPS configuration.

[0138] Embodiment 15: A method as in Embodiment 14, wherein: the first CORESET is associated with a first CORESET group; the second CORESET is associated with a second CORESET group; each SPS configuration is associated with one of the first CORESET group or the second CORESET group; and the UE determines to activate or release an SPS configuration associated with a CORESET group in which a DCI for activating or releasing the SPS configuration is detected.

[0139] Embodiment 16: The method of embodiment 15 further includes receiving signaling for each CORESET indicating an index of which CORESET group the CORESET belongs.

[0140] Embodiment 17: The method of Embodiment 15 or 16 further includes: receiving signaling indicating which SPS configuration is associated with which CORESET group.

[0141] Embodiment 18: A method as in Embodiment 14, wherein: the DCI includes an identifier indicating which SPS configuration the DCI activates or releases.

[0142] Embodiment 19: The method of Embodiment 18 further includes: receiving signaling indicating an identifier for each SPS configuration.

[0143] Embodiment 20: A method as in Embodiment 18 or 19, wherein: the UE receives at least two SPS configurations for at least one of the first CORESET or the second CORESET; and the DCI includes an identifier indicating which of the at least two SPS configurations the DCI activates.

[0144] Embodiment 21: A method as in Embodiment 20, wherein each SPS configuration has an identifier and is associated with a CORESET group.

[0145] Embodiment 22: A method as in Embodiment 21, wherein an identifier is used to distinguish different SPS configurations within the same CORESET group.

[0146] Embodiment 23: A method as in Embodiment 22, wherein which cross-CORESET group in the SPS configuration is distinguished based on the CORESET group in which the DCI for activating or releasing the SPS is received.

[0147] Embodiment 24: A method for wireless communication performed by a user equipment (UE), comprising: receiving configuration signaling of at least a first semi-persistent scheduling (SPS) configuration and a second SPS configuration associated with at least a first control resource set (CORESET) and a second CORESET, each CORESET being associated with a CORESET group identified by an index, detecting at least one downlink control information (DCI) activating the first SPS configuration or the second SPS configuration in at least one of the first CORESET or the second CORESET, and determining a data scrambling identifier of one or more SPS physical downlink shared channels (PDSCH) for the activated SPS configuration based on the CORESET group in which the DCI is detected.

[0148] Embodiment 25: A method as in Embodiment 24, wherein each of the at least two CORESET group indexes is associated with a different data scrambling identifier.

[0149] Embodiment 26: A method as in Embodiment 25, wherein each SPS configuration corresponds to a different CORESET group associated with a different index.

[0150] Embodiment 27: The method of Embodiment 25 or 26, wherein a data scrambling identity associated with a CORESET group in which the DCI is detected is used for SPS PDSCH scrambling.

[0151] Embodiment 28: An apparatus for wireless communication performed by a user equipment (UE), comprising: a component for detecting at least one downlink control information (DCI) on each of at least a first control resource set (CORESET) and a second CORESET, each DCI being sent according to a semi-persistent scheduling (SPS) configuration SPS activated physical downlink shared channel (PDSCH); a component for decoding a corresponding SPS PDSCH transmission; a component for determining a codebook construction of one or more codebooks for providing confirmation feedback for the SPS PDSCH transmission; and a component for providing confirmation feedback for the SPS PDSCH transmission based on the determination.

[0152] The method disclosed herein includes one or more steps or actions for implementing the method. The method steps and / or actions can be interchanged 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 modified without departing from the scope of the claims.

[0153] 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 multiples of the same elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc or any other order of a, b, and c).

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

[0155] 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 apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are intended to be given a full scope consistent with the language of the claims, wherein unless otherwise specified, references to elements in the singular are not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference, and are intended to be covered by the claims. Moreover, none of the contents disclosed herein are intended to be dedicated to the public, regardless of whether such disclosures are explicitly stated in the claims. Any claim element will not be interpreted in accordance with the terms of 35 U.S.C. § 112 (f), unless the phrase "parts for ..." is used to expressly state the element, or the phrase "step for ..." is used to state the element in the case of a method claim.

[0156] The various operations of the above methods may be performed by any suitable components capable of performing the corresponding functions. The components 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 speaking, where operations are shown in the accompanying drawings, those operations may have corresponding counterpart means-plus-function components. For example, Figure 8 , 12 The various operations shown in 13 can be performed by Figure 4 The UE 120 may be executed by various processors shown in FIG. 4 , such as processors 466 , 458 , 464 and / or controller / processor 480 of UE 120 .

[0157] 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. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0158] 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. The bus may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. Among other things, the bus interface may be used to connect a network adapter 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, etc., 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 that can execute software. Those skilled in the art will recognize how to best implement the described functionality for a processing system, depending on the specific application and the overall design constraints imposed on the entire system.

[0159] If implemented in software, the function can be stored or sent as one or more instructions or codes on a computer-readable medium. Software should be broadly interpreted as meaning instructions, data, or any combination thereof, whether it is called software, firmware, middleware, microcode, hardware description language or other. Computer-readable media include both computer storage media and communication media, and communication media include any media that facilitates the transfer of computer programs from one place to another. The processor can be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. The computer-readable storage medium can be coupled to the processor so that the processor can read information from the storage medium and can write information to the storage medium. In an alternative, the storage medium can be integrated with the processor. For example, the machine-readable medium can include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium with instructions stored thereon separated from the wireless node, all of which can be accessed by the processor through a bus interface. Alternatively or additionally, the machine-readable medium or any part thereof can be integrated into the processor, such as the case where there may be a cache and / or a general register file. Examples of machine-readable storage media may include, for example, 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 embodied in a computer program product.

[0160] A software module may include a single instruction or multiple instructions, and may be distributed over several different code segments, distributed among different programs, and distributed across multiple storage media. A computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a sending module and a receiving module. Each software module may reside in a single storage device, or may be distributed across multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard drive into a RAM. During the execution of a software module, a processor may load some of the 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 referring to the functionality of the following software modules, it will be understood that such functionality is implemented by a processor when executing instructions from this software module.

[0161] Likewise, any connection is properly referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave are used to transmit the software from a website, server, or other remote source, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and optical disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and optical disc. Disks, where magnetic disks typically reproduce data magnetically, and optical disks 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 transitory computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0162] Thus, certain 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 instructions stored (and / or encoded) thereon, the instructions being executed by one or more processors to perform the operations described herein. For example, the instructions are for performing the operations described herein and Figure 8 , 12 and / or the operations shown in 13.

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

[0164] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes 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 performed by a user equipment UE, comprising: Detecting at least one downlink control information DCI on each of at least a first control resource set CORESET and a second CORESET, each DCI being sent according to a semi-persistent scheduling SPS configuration activating an SPS physical downlink shared channel PDSCH; Decode the corresponding SPS PDSCH transmission; determining a codebook configuration of one or more codebooks for providing acknowledgment feedback for the SPS PDSCH transmission, wherein the codebook configuration indicates separate codebooks for providing separate acknowledgment feedback for the SPS PDSCH transmission or a single codebook for providing joint acknowledgment feedback; as well as Acknowledgement feedback is provided for the SPS PDSCH transmission based on the determination.

2. The method of claim 1, wherein: The DCI received in the first CORSET is sent from a first transmitter receiver point TRP; and The DCI received in the second CORSET is sent from the second TRP.

3. The method of claim 1, wherein: The first CORESET is associated with a first CORESET group; The second CORESET is associated with a second CORESET group; The one or more codebooks include a codebook associated with the first CORESET group; as well as The UE provides acknowledgment feedback for each of the SPS PDSCH transmissions according to the codebook associated with the first CORESET group. The method of claim 1 , further comprising receiving signaling indicating the codebook construction.

5. The method of claim 1, wherein: The first CORESET is associated with a first CORESET group; The second CORESET is associated with a second CORESET group; The one or more codebooks include a first codebook and a second codebook associated with the first CORESET group and the second CORESET group; as well as The UE provides confirmation feedback for each of the SPS PDSCH transmissions according to the first codebook or the second codebook based on the CORESET group in which the DCI activating the SPS PDSCH transmission is detected.

6. The method of claim 5, further comprising receiving signaling for each CORESET indicating an index of which CORESET group the CORESET belongs to.

7. The method of claim 5, further comprising: detecting a DCI releasing an SPS configuration associated with one of the first CORESET or the second CORESET; as well as Based on the CORESET group in which the DCI to release the SPS configuration is detected, a CORESET associated with the released SPS configuration is determined.

8. The method of claim 7, further comprising providing confirmation feedback for the release according to a codebook selected based on the CORESET group in which the DCI for releasing the SPS PDSCH transmission is detected.

9. The method of claim 1, wherein the determined codebook structure comprises a common codebook whose entries have bits for acknowledging the SPS PDSCH transmission detected at each of the first CORESET and the second CORESET.

10. The method of claim 9, wherein: The common codebook includes a type 1 hybrid automatic repeat request HARQ confirmation codebook; The first CORESET is associated with a first CORESET group; The second CORESET is associated with a second CORESET group; as well as The position of the bit is individually determined based on candidate PDSCH opportunities within a reporting window, the candidate PDSCH opportunities being individually determined for each of the CORESET groups.

11. The method of claim 9, wherein: The common codebook includes a type 2 hybrid automatic repeat request HARQ confirmation codebook; The bit is appended to the codebook entry; One of the bits is used to acknowledge the SPS PDSCH transmission detected on the first CORESET; as well as Another of the bits is used to acknowledge the SPS PDSCH transmission detected on the second CORESET.

12. The method of claim 11, further comprising: Detecting, on at least one of the first CORESET and the second CORESET, a DCI sent by releasing the SPS PDSCH; as well as Confirmation feedback is provided for the release via one or more bits, wherein a position of the entry within the codebook depends at least in part on a downlink assignment index (DAI) value.

13. The method of claim 1, further comprising: At least two SPS configurations are received for at least one of the first CORESET or the second CORESET.

14. An apparatus for wireless communication performed by a user equipment UE, comprising: means for detecting at least one downlink control information DCI on each of at least a first control resource set CORESET and a second CORESET, each DCI being sent according to a semi-persistent scheduling SPS configuration activating an SPS physical downlink shared channel PDSCH; Components for decoding the corresponding SPS PDSCH transmission; means for determining a codebook configuration of one or more codebooks for providing acknowledgment feedback for the SPS PDSCH transmission, wherein the codebook configuration indicates separate codebooks for providing separate acknowledgment feedback for the SPS PDSCH transmission or a single codebook for providing joint acknowledgment feedback; as well as means for providing confirmation feedback for the SPS PDSCH transmission based on the determination.

15. A computer-readable medium storing code for wireless communication by a user equipment (UE), the code comprising instructions which, when executed by a processor, cause the processor to perform the method according to any one of claims 1-13.

Images