Techniques for repeating a transport block using spatial division multiplexing
By using spatial multiplexing technology in wireless communication systems and utilizing different antenna panels for TB-repetitive communication, the problems of insufficient signaling and scheduling in TB-repetitive communication are solved, improving transmission performance and reliability, and making it suitable for telecommunications standards such as LTE and NR.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- QUALCOMM INC
- Filing Date
- 2020-04-21
- Publication Date
- 2026-05-01
AI Technical Summary
The lack of effective support for spatial division multiplexing (SDM) technology in wireless communication systems leads to insufficient signaling, configuration, and scheduling of TB-repeated signals, affecting transmission performance and reliability.
Through indications and DCI messages between the UE and the base station, TB repetition communication is carried out using different antenna panels, including sending or receiving TB repetition indications, scheduling resources that partially overlap in the time and frequency domains, and using SDM technology for TB repetition transmission.
It improves the transmission performance and reliability of wireless communication, enhances spectrum efficiency, and is suitable for various telecommunications standards and multiple access technologies, including LTE and NR.
Smart Images

Figure CN115336345B_ABST
Abstract
Description
Technical Field
[0001] Various aspects of this disclosure generally relate to wireless communications and techniques and apparatus for repeating transport blocks (TBs) using spatial division multiplexing (SDM). Background Technology
[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include 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, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).
[0003] Wireless communication networks may include multiple base stations (BSs) capable of supporting communication between multiple user equipments (UEs). UEs can communicate with base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, and an uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.
[0004] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global levels. New Radio (NR), also known as 5G, is a collection of enhancements to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP). NR aims to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards to better support mobile broadband internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on the downlink (DL), CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation. However, with the continued growth in demand for mobile broadband access, further improvements to LTE and NR technologies are needed. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention
[0005] In some aspects, a wireless communication method performed by a UE may include: sending to a base station an indication that the UE is capable of using spatial division multiplexing (SDM) to transmit or receive transport block (TB) repetitions; receiving from the base station and at least in part based on the indication at least one downlink control information (DCI) message, the at least one downlink control information message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time and frequency domains; and using different antenna panels to perform communication of TBs and TB repetitions according to the at least one DCI message.
[0006] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to send to a base station an indication that the UE is capable of using SDM to send or receive TB repetitions; receive from the base station and at least in part based on the indication at least one DCI message, the at least one DCI message scheduling TBs in a first resource and TB repetitions in a second resource, the first and second resources at least partially overlapping in the time and frequency domains; and, according to the at least one DCI message, use different antenna panels for communication of TBs and TB repetitions.
[0007] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of the UE, the one or more instructions may cause the one or more processors to: send to a base station an indication that the UE is capable of using SDM to send or receive TB repetitions; receive from the base station and at least in part based on the indication at least one DCI message, the at least one DCI message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time and frequency domains; and, according to the at least one DCI message, use different antenna panels to perform communication of TBs and TB repetitions.
[0008] In some aspects, an apparatus for wireless communication may include: an apparatus module for transmitting to a base station an indication that the apparatus is capable of transmitting or receiving TB repetitions using SDM; an apparatus module for receiving at least one DCI message from the base station and at least in part based on the indication, the at least one DCI message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; and an apparatus module for communicating TBs and TB repetitions using different antenna panels according to the at least one DCI message.
[0009] In some respects, this instruction indicates that the UE is able to send or receive TB repetitions in multiple codewords scheduled by a single DCI message.
[0010] In some aspects, the at least one DCI message is a single DCI message that schedules the transmission of a first codeword and a second codeword. In some aspects, the second codeword is a repetition of the first codeword. In some aspects, the first codeword is to be used for a TB, and the second codeword is to be used for a repetition of the TB. In some aspects, the TB size associated with the transmission is at least partially based on the first codeword.
[0011] In some aspects, the method includes receiving a configuration that enables TB repetition using SDM, scheduled by a single DCI message.
[0012] In some aspects, the at least one DCI message indicates that TB repetitions using SDM are scheduled by the at least one DCI message. In some aspects, the Radio Network Temporary Identifier (RNTI) associated with the at least one DCI message indicates that TB repetitions using SDM are scheduled by the at least one DCI message.
[0013] In some respects, this instruction indicates that the UE is able to send or receive TB repetitions scheduled by multiple DCI messages.
[0014] In some aspects, the at least one DCI message includes a first DCI message and a second DCI message, wherein the first DCI message is associated with a first CORESET linked to a first control resource set (CORESET) pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
[0015] In some aspects, the at least one DCI message includes a first DCI message and a second DCI message, wherein the first DCI message schedules the transmission of a first codeword, and the second DCI message schedules the transmission of a second codeword. In some aspects, the second codeword is a repetition of the first codeword.
[0016] In some respects, the at least one DCI message includes a first DCI message and a second DCI message, and the first DCI message and the second DCI message identify the same Hybrid Automatic Repeat Request (HARQ) process identifier, the same TB size, the same New Data Indicator (NDI) value and different beam indicators.
[0017] In some aspects, the method includes receiving a configuration that enables TB repetition using SDM, which is scheduled by multiple DCI messages.
[0018] In some aspects, a wireless communication method performed by a base station may include: receiving from a UE an indication that the UE is capable of using SDM to send or receive TB repetitions; sending to the UE and at least in part based on the indication at least one DCI message, the at least one DCI message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; and performing communication on TBs and TB repetitions according to the at least one DCI message.
[0019] In some aspects, a base station for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to receive from a UE an indication that the UE is capable of using SDM to send or receive TB repetitions; to send to the UE and at least in part based on the indication at least one DCI message, the at least one DCI message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time and frequency domains; and to perform communication of TBs and TB repetitions according to the at least one DCI message.
[0020] In some respects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to: receive from the UE an indication that the UE is able to use SDM to send or receive TB repetitions; send to the UE and at least in part based on the indication at least one DCI message, the at least one DCI message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; and perform communication of TBs and TB repetitions according to the at least one DCI message.
[0021] In some aspects, the apparatus for wireless communication may include: an apparatus module for receiving from a UE an indication that the UE is capable of using SDM to send or receive TB repetitions; an apparatus module for sending at least one DCI message to the UE and at least partially based on the indication, the at least one message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; and an apparatus for communicating TBs and TB repetitions according to the at least one DCI message.
[0022] In some respects, this instruction indicates that the UE is able to send or receive TB repetitions in multiple codewords scheduled by a single DCI message.
[0023] In some aspects, the at least one DCI message is a single DCI message that schedules the transmission of a first codeword and a second codeword. In some aspects, the second codeword is a repetition of the first codeword. In some aspects, the first codeword is to be used for a TB, and the second codeword is to be used for a repetition of the TB. In some aspects, the TB size associated with the transmission is at least partially based on the first codeword.
[0024] In some aspects, the method includes sending a configuration that enables TB repetition using SDM, scheduled by a single DCI message.
[0025] In some aspects, the at least one DCI message indicates that TB repetition using SDM is scheduled by the at least one DCI message. In some aspects, the RNTI associated with the at least one DCI message indicates that TB repetition using SDM is scheduled by the at least one DCI message.
[0026] In some respects, this instruction indicates that the UE is able to send or receive TB repetitions scheduled by multiple DCI messages.
[0027] In some aspects, the at least one DCI message includes a first DCI message and a second DCI message, wherein the first DCI message is associated with a first CORESET pool index and the second DCI message is associated with a second CORESET pool index.
[0028] In some aspects, the at least one DCI message includes a first DCI message and a second DCI message, wherein the first DCI message schedules the transmission of a first codeword, and the second DCI message schedules the transmission of a second codeword. In some aspects, the second codeword is a repetition of the first codeword.
[0029] In some respects, the at least one DCI message includes a first DCI message and a second DCI message, and the first DCI message and the second DCI message identify the same HARQ process identifier, the same TB size, the same NDI value and different beam indications.
[0030] In some aspects, the method includes sending a configuration that enables TB repetition using SDM, which is scheduled by multiple DCI messages.
[0031] The terms generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems, which are basically described herein with reference to the accompanying drawings and description.
[0032] The features and technical advantages of the examples according to this disclosure have been outlined rather broadly above to facilitate a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifications or designs of other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their organization and operation, and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and is not intended to define limitations of the claims. Attached Figure Description
[0033] To gain a more detailed understanding of the features of this disclosure, reference can be made to several aspects for which a brief overview has been provided above, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure, as the description may allow for other equally valid aspects, and should not be considered as limiting its scope. The same reference numerals in different drawings may denote the same or similar elements.
[0034] Figure 1This is a diagram illustrating an example of a wireless communication network according to various aspects of this disclosure.
[0035] Figure 2 This is a diagram illustrating an example of communication between a base station and a UE in a wireless communication network according to various aspects of this disclosure.
[0036] Figure 3 This is a diagram illustrating an example logical architecture of a distributed radio access network (RAN) according to aspects of this disclosure.
[0037] Figure 4 This is a diagram illustrating an example of multi-TRP communication according to various aspects of this disclosure.
[0038] Figures 5A-5D This is a diagram illustrating one or more examples of using SDM to repeat TB according to various aspects of this disclosure.
[0039] Figure 6 This is a diagram illustrating, for example, an example process performed by a UE according to various aspects of this disclosure.
[0040] Figure 7 This is a diagram illustrating, for example, an example process performed by a base station according to various aspects of this disclosure.
[0041] Figure 8 This is a conceptual data flow diagram illustrating the data flow between different components in an example device according to various aspects of this disclosure.
[0042] Figure 9 This is a conceptual data flow diagram illustrating the data flow between different components in an example device according to various aspects of this disclosure. Detailed Implementation
[0043] Various aspects of this disclosure will be described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art should understand that the scope of this disclosure is intended to cover any aspect disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover an apparatus or method practiced using a structure, function, or structure and function other than or different from the aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.
[0044] Several aspects of a telecommunications system will now be described with reference to various devices and technologies. These devices and technologies will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented in hardware or software depends on the specific application and the design constraints on the overall system.
[0045] It should be noted that although terms commonly associated with 3G and / or 4G wireless technologies may be used in this document to describe aspects, aspects of this disclosure may be applied to other generations of communication systems, including NR technologies, such as 5G and later communication systems.
[0046] Figure 1 This is a schematic diagram of a wireless network 100 in which various aspects of this disclosure can be practiced. The wireless network 100 can be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 can include multiple BS 110s (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and can also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.
[0047] A Base Station (BS) can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and can allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and can allow restricted access for UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macrocell can be referred to as a macro BS. A BS for a picocell can be referred to as a pico BS. A BS for a femtocell can be referred to as a femtocell BS or a home BS. Figure 1In the example shown, BS 110a can be a macro BS of macro cell 102a, BS 110b can be a pico BS of pico cell 102b, and BS 110c can be a femto BS of femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” are used interchangeably herein.
[0048] In some respects, the cell is not necessarily stationary, and the geographical area of the cell can move depending on the location of the mobile BS. In some respects, the BS can use any suitable transport network to interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections, virtual networks, etc.
[0049] The wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay station 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay station can also be referred to as a relay BS, relay base station, relay, etc.
[0050] Wireless network 100 can be a heterogeneous network, including different types of base stations (BSs), such as macro BSs, pico BSs, femto BSs, and relay BSs. These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).
[0051] Network controller 130 can be coupled to a collection of BSs and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.
[0052] UEs 120 (e.g., 120a, 120b, 120c) may be distributed across the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biosensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.
[0053] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, location tags, etc., which can communicate with base stations, another device (e.g., remote devices), or some other entity. For example, a wireless node can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120 (e.g., processor components, memory components, etc.).
[0054] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.
[0055] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as a medium for communication with each other). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, mesh networks, etc.). In this case, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations performed by base station 110 as described elsewhere herein.
[0056] As mentioned above, Figure 1 This is provided as an example. Other examples may differ from those provided. Figure 1 As described.
[0057] Figure 2 A block diagram of a design 200 for a base station 110 and a UE 120 is shown. The base station 110 and the UE 120 can be... Figure 1 One of the base stations and one of the UEs. Base station 110 may be equipped with T antennas 234a to 234t, and UE 120 may be equipped with R antennas 252a to 252r, where typically T≥1 and R≥1.
[0058] At base station 110, transmitting processor 220 can receive data from data source 212 of one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from the UE, process (e.g., encode and modulate) the UE's data based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., for semi-static resource allocation information (SRPI), etc.) and control information (e.g., CQI requests, authorizations, upper-layer signaling, etc.), and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted separately via T antennas 234a to 234t. Position coding can be used to generate synchronization signals to convey additional information, according to various aspects described in more detail below.
[0059] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data of UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The channel processor can determine the Received Reference Signal Power (RSRP), Received Signal Strength Indicator (RSSI), Received Reference Signal Quality (RSRQ), Channel Quality Indicator (CQI), etc. In some respects, one or more components of the UE 120 may be included in a housing.
[0060] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting, including RSRP, RSSI, RSRQ, CQI, etc.). The transmitting processor 264 can also generate reference symbols for one or more reference signals. Symbols from the transmitting processor 264 can be pre-encoded (if applicable) by the TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiving processor 238 to obtain decoded data and control information transmitted by UE 120. The receiver processor 238 can provide decoded data to the data sink 239 and decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicates with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.
[0061] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2Any other component may perform one or more techniques associated with using SDM to repeat TB, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can execute or direct, for example Figure 6 Process 600 Figure 7 The operation of process 700 and / or other processes herein. Memory 242 and 282 may store data and program code of base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120, these one or more instructions may execute or direct, for example... Figure 6 Process 600 Figure 7 The operation of process 700 and / or other processes herein. Scheduler 246 can schedule the UE to perform data transmission on the downlink and / or uplink.
[0062] In some aspects, UE 120 may include: an apparatus module for transmitting an indication that UE 120 is capable of transmitting or receiving TB repetitions using SDM; an apparatus module for receiving at least one DCI message based at least partially on the indication, the at least one message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time and frequency domains; and an apparatus module for communicating TBs and TB repetitions using different antenna panels according to the at least one DCI message, etc. In some aspects, such an apparatus module may include a combination of Figure 2 One or more components of the UE120 described, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.
[0063] In some aspects, base station 110 may include: an apparatus module for receiving an indication that a UE can use SDM to send or receive TB repetitions; an apparatus module for sending at least one DCI message at least partially based on receiving the indication, the at least one message scheduling TBs in a first resource and TB repetitions in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; and an apparatus module for communicating TBs and TB repetitions according to the at least one DCI message, etc. In some aspects, such an apparatus module may include a combination of Figure 2One or more components of the described base station 110, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.
[0064] As mentioned above, Figure 2 This is provided as an example. Other examples may differ from those provided. Figure 2 As described.
[0065] Figure 3 This is a diagram illustrating an example logical architecture of a distributed RAN 300 according to aspects of this disclosure.
[0066] 5G access node 305 may include access node controller 310. Access node controller 310 may be the central unit (CU) of a distributed RAN 300. In some aspects, the backhaul interface to the 5G core network 315 may terminate at access node controller 310. 5G core network 315 may include 5G control plane components 320 and 5G user plane components 325 (e.g., 5G gateways), and the backhaul interface of one or both of the 5G control plane and 5G user plane may terminate at access node controller 310. Additionally or alternatively, the backhaul interface to one or more adjacent access nodes 330 (e.g., another 5G access node 305, an LTE access node, etc.) may terminate at access node controller 310.
[0067] Access node controller 310 may include one or more TRPs 335 and / or be able to communicate with one or more TRPs 335 (e.g., via an F1 control (F1-C) interface and / or an F1 user (F1-U) interface). TRP 335 may be a distributed unit (DU) of the distributed RAN 300. In some aspects, TRP 335 may correspond to the combination described above. Figure 1 The base station 110 is described. For example, different TRPs 335 may be included in different base stations 110. Additionally or alternatively, multiple TRPs 335 may be included in a single base station 110. In some aspects, base station 110 may include a CU (e.g., access node controller 310) and / or one or more DUs (e.g., one or more TRPs 335). In some cases, TRPs 335 may be referred to as cells, panels, antenna arrays, arrays, etc.
[0068] The TRP 335 can connect to a single access node controller 310 or multiple access node controllers 310. In some respects, dynamic configuration of decoupled logical functions can exist in the architecture of the distributed RAN 300. For example, the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, etc., can be configured to terminate at the access node controller 310 or the TRP 335.
[0069] In some respects, multiple TRP 335s can transmit communication in the same Transmission Time Interval (TTI) (e.g., time slots, micro-slots, subframes, symbols, etc.) or in different TTIs using different Quasi-Co-location (QCL) relationships (e.g., different spatial parameters, different Transmission Configuration Indicator (TCI) states, different precoding parameters, different beamforming parameters, etc.). In some respects, the TCI state can be used to indicate one or more QCL relationships. TRP 335s can be configured to provide services to UE 120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRP 335s).
[0070] As mentioned above, Figure 3 This is provided as an example. Other examples may differ from those provided. Figure 3 As described.
[0071] Figure 4 This is a diagram illustrating example 400 of multi-TRP communication (sometimes called multi-panel communication) according to various aspects of this disclosure. Figure 4 As shown, multiple TRP 405s can communicate with the same UE 120. The TRP 405 can correspond to the combination described above. Figure 3 The TRP 335 is described.
[0072] Multiple TRPs 405 (shown as TRP A and TRP B) can communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multicast, etc.) to improve reliability, increase throughput, etc. This communication can be coordinated between TRPs 405 via an interface between them (e.g., a backhaul interface, access node controller 310, etc.). When TRPs 405 are located at the same base station 110 (e.g., when TRPs 405 are different antenna arrays or panels of the same base station 110), the interface may have lower latency and / or higher capacity, and when TRPs 405 are located at different base stations 110, the interface may have higher latency and / or lower capacity (compared to being located in the same location). Different TRPs 405 can communicate with the UE 120 using different QCL relationships (e.g., different TCI states), different demodulation reference signal (DMRS) ports, different layers (e.g., layers of multi-layer communication), etc.
[0073] In the first multi-TRP transmission mode (e.g., mode 1), a single physical downlink control channel (PDCCH) can be used to schedule downlink data communication for a single physical downlink shared channel (PDSCH). In this case, multiple TRPs 405 (e.g., TRP A and TRP B) can transmit communication to UE 120 on the same PDSCH. For example, for different TRPs 405, a single codeword with different spatial layers can be used to transmit communication (e.g., one codeword is mapped to a first layer set transmitted by the first TRP 405 and to a second layer set transmitted by the second TRP 405). As another example, multiple codewords can be used to transmit communication, where different codewords are transmitted by different TRPs 405 (e.g., using different layer sets). In either case, different TRPs 405 can use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the first TRP 405 may use a first QCL relationship or a first TCI state for a first DMRS port set corresponding to a first layer set, and the second TRP 405 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) DMRS port set corresponding to a second (different) layer set. In some aspects, the TCI state in downlink control information (DCI) (e.g., transmitted on the PDCCH, such as DCI format 1_0, DCI format 1_1, etc.) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The TCI field in the DCI may be used to indicate the first TCI state and the second TCI state. Typically, in this multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for a single TRP transmission) or multiple TCI states (for the multi-TRP transmission discussed herein).
[0074] In the second multi-TRP transmission mode (e.g., mode 2), multiple PDCCHs can be used to schedule downlink data communication for multiple corresponding PDSCHs (e.g., one PDCCH per PDSCH). In this case, the first PDCCH can schedule the first TRP 405 to send a first codeword, and the second PDCCH can schedule the second TRP 405 to send a second codeword. Furthermore, the first DCI (e.g., sent by the first TRP 405) can schedule first PDSCH communication associated with a first DMRS port set having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 405, and the second DCI (e.g., sent by the second TRP 405) can schedule second PDSCH communication associated with a second DMRS port set having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 405. In this case, the DCI (e.g., having DCI format 1_0, DCI format 1_1, etc.) can indicate the corresponding TCI state of the TRP 405 corresponding to the DCI. The TCI field of a DCI indicates the corresponding TCI state (for example, the TCI field of a first DCI indicates a first TCI state, and the TCI field of a second DCI indicates a second TCI state).
[0075] As mentioned above, Figure 4 This is provided as an example. Other examples may differ from those provided. Figure 4 As described.
[0076] A UE can use multiple antenna panels to perform concurrent (e.g., simultaneous) uplink transmissions or receive concurrent (e.g., simultaneous) downlink transmissions. Concurrent transmission using multiple antenna panels can be referred to as incoherent joint transmission or spatial division multiplexing (SDM). In some wireless networks, TB repetition can be used to improve transmission performance, transmission reliability, etc. However, wireless networks typically lack support for techniques to signal, configure, indicate, schedule, or otherwise implement TB repetition using SDM.
[0077] Therefore, some of the techniques and apparatus described herein provide a framework for TB repetition using SDM. For example, as described herein, a UE can send a capability report to a base station indicating that the UE supports using SDM to transmit or receive TB repetitions, and the base station can provide the UE with higher-level configuration to enable TB repetition using SDM (e.g., via Radio Resource Control (RRC) signaling). The base station can then send a single DCI message or multiple DCI messages to the UE, which schedule TB repetitions in resources that at least partially overlap in the time and frequency domains, and the UE can perform TB repetition communication (e.g., transmit or receive) based on the DCI messages.
[0078] Figures 5A-5D This is a diagram illustrating one or more examples 500 of using SDM to repeat TB according to various aspects of this disclosure. Figures 5A-5D As shown, base station 110 and UE 120 can communicate with each other. In some aspects, UE 120 may use multiple transmit antenna panels (e.g., multiple Physical Uplink Shared Channel (PUSCH) antenna port groups) and / or multiple receive antenna panels (e.g., multiple PDSCH antenna port groups). In some aspects, UE 120 may communicate with multiple TRPs (e.g., multiple antenna panels) associated with base station 110. In some aspects, multiple TRPs may be associated with more than one base station.
[0079] like Figure 5A As shown, via reference numeral 505, UE 120 can send, and BS 110 can receive, an indication that UE 120 is capable of sending and / or receiving TB duplicates using SDM. For example, UE 120 can send a UE capability report indicating that UE 120 is capable of sending and / or receiving TB duplicates using SDM.
[0080] In some respects, this instruction can instruct the UE to use SDM to send and / or receive TB repetitions scheduled by a single DCI message. That is, this instruction can instruct the UE to use SDM to send TB repetitions using two uplink codewords (e.g., the UE can report the capability of TBrepetitionby2ULCW) and / or to receive TB repetitions using two downlink codewords (e.g., the UE can report the capability of TBrepetitionby2DLCW).
[0081] In some respects, this instruction may instruct the UE to use SDM to send and / or receive TB repetitions scheduled by multiple DCI messages (e.g., two DCI messages). For example, this instruction may instruct the UE to use SDM to send TB repetitions scheduled by two uplink DCI messages (e.g., the UE can report the capability of SDMby2ULDCI) and / or receive TB repetitions scheduled by two downlink DCI messages (e.g., the UE can report the capability of SDMby2DLDCI).
[0082] As shown by reference numeral 510 in the accompanying drawings, base station 110 may transmit (e.g., via RRC signaling) and UE 120 may receive a configuration that enables TB repetition using SDM for UE 120. For example, base station 110 may transmit this configuration at least in part based on UE 120's indication of the ability to use TB repetition using SDM.
[0083] In some respects, this configuration can enable TB repetition using SDM scheduled by a single DCI message. For example, this configuration can set the first RRC signaling (flag1) to a first value (e.g., 1) to enable TB repetition scheduled by a single DCI message. Similarly, base station 110 can send another configuration to UE 120 to disable TB repetition using SDM scheduled by a single DCI message. For example, this configuration can set the first RRC signaling to a second value (e.g., 0) to disable TB repetition scheduled by a single DCI message.
[0084] In some respects, this configuration can enable TB repetition using SDM scheduled by multiple DCI messages (e.g., two DCI messages). For example, this configuration can set the second RRC signaling (flag2) to a first value (e.g., 1) to enable TB repetition scheduled by multiple DCI messages. Similarly, base station 110 can send another configuration to UE 120 to disable TB repetition using SDM scheduled by multiple DCI messages (e.g., two DCI messages). For example, this configuration can set the second RRC signaling to a second value (e.g., 0) to disable TB repetition scheduled by multiple DCI messages.
[0085] like Figure 5B As shown, by reference numeral 515a, in some aspects, base station 110 can transmit and UE 120 can receive a single DCI message for scheduling TB (e.g., initial repetition of TB) and at least one repetition of TB. The single DCI message can indicate a single resource allocation for TB and the repetition of TB. That is, the first resource to be used for TB and the second resource to be used for the repetition of TB can overlap in the time and frequency domains (e.g., the first and second resources can be the same).
[0086] Base station 110 may send a single DCI message, at least in part, based on UE 120 instructing UE 120 to use SDM to send and / or receive TB repetitions scheduled by a single DCI message. Furthermore, base station 110 may send a single DCI message after enabling TB repetitions scheduled by a single DCI message for UE 120.
[0087] In some respects, base station 110 may send a message indicating that the maximum number of codewords scheduled by a single DCI message is greater than one (e.g., two codewords). For example, an RRC message may indicate (e.g., using the maxNrofULCodeWordsScheduledByDCI parameter) that the maximum number of uplink codewords scheduled by a DCI message is two uplink codewords. As another example, an RRC message may indicate (e.g., using the maxNrofDLCodeWordsScheduledByDCI parameter) that the maximum number of downlink codewords scheduled by a DCI message is two downlink codewords.
[0088] In some respects, a single DCI message can schedule the transmission of at least a first codeword and a second codeword. For example, a single uplink DCI message can schedule a first uplink codeword and a second uplink codeword, and the second uplink codeword can be a duplicate of the first uplink codeword. As another example, a single downlink DCI message can schedule a first downlink codeword and a second downlink codeword, and the second downlink codeword can be a duplicate of the first downlink codeword.
[0089] In some aspects, a single DCI message can indicate a first parameter of the first codeword (e.g., a first New Data Indicator (NDI) value, a first MCS, a first Redundancy Version (RV), etc.) and a second parameter of the second codeword (e.g., a second NDI value, a second MCS, a second RV, etc.). Furthermore, a single DCI message can indicate a first beam indication of the first codeword and a second beam indication of the second codeword. For example, for the beam indications of the first and second codewords, a single DCI message can indicate the corresponding Transmit Configuration Indicator (TCI) status, the corresponding Sounding Reference Signal (SRS) Resource Indicator (SRI), the corresponding SRS Resource Set Indicator, etc.
[0090] Furthermore, the demodulation reference signal (DMRS) antenna port indication for a single DCI message can be used for both the first and second codewords. For example, the DMRS antenna port indication can be associated with two or more DMRS code division multiplexing (CDM) groups (e.g., when a single DCI message schedules more than one codeword). In this case, the first DMRS CDM group can be associated with the first codeword, and the remaining DMRS CDM groups (e.g., the second DMRS CDM group, etc.) can be associated with the second codeword.
[0091] In some respects, a single DCI message can support the association of TBs and TB repetitions. For example, a first codeword can be used for a TB, and a second codeword can be used for a TB repetition. In some respects, the TB size associated with the TB and the TB repetition is the same (e.g., the TB size is not determined independently for the TB and the TB repetition). In this case, the TB size of the transmission of the first codeword and the second codeword can be at least partially based on the first codeword (e.g., the TB size of the second codeword is the same as that of the first codeword).
[0092] Therefore, a single DCI message can be scheduled for a first PUSCH or PDSCH transmission (denoted as PUSCH / PDSCH 1) and a second PUSCH or PDSCH transmission (denoted as PUSCH / PDSCH 2). The first PUSCH / PDSCH transmission can be associated with a first codeword and can be scheduled for transmission or reception using the first antenna panel and first beam of the UE 120. The second PUSCH / PDSCH transmission can be associated with a second codeword and can be scheduled for transmission or reception using the second antenna panel and second beam of the UE 120.
[0093] In some respects, a single DCI message can provide an indication (e.g., a dynamic indication) of scheduling TB repetitions using SDM (rather than scheduling different TBs using SDM) for a single DCI message. For example, reserved values of one or more fields in a single DCI message can indicate that the single DCI message is scheduling TB repetitions using SDM. As an example, a single DCI message can switch (e.g., set) the NDI associated with a second codeword (e.g., to indicate new data) and identify the MCS of the second codeword indicating retransmission (e.g., the MCS is associated with a modulation order indication rather than a coding rate indication, such as MCS 28, 29, 30, or 31 identified in Table 6.1.4.1-1 of 3GPP Technical Specification 38.214). In other words, UE 120 can determine the scheduling of TB repetitions using SDM indicated by the DCI message based at least in part on the determination of an invalid combination of the NDI value of the second codeword indicated by the single DCI message and the MCS (e.g., a combination indicating new data and retransmission).
[0094] In some respects, the Radio Network Temporary Identifier (RNTI) associated with a single DCI message can provide an indication (e.g., a dynamic indication) of the TB repetition (rather than different TBs scheduled to use the SDM) of a single DCI message. For example, the RNTI can be defined for use with a maximum number of uplink or downlink codewords that are associated with more than one codeword (e.g., two codewords). Therefore, UE 120 can determine the TB repetition of the DCI message scheduled to use the SDM based at least in part on the use of the RNTI to descramble a single DCI message.
[0095] like Figure 5C As shown, by reference numeral 515b, in some aspects, base station 110 can transmit and UE 120 can receive multiple DCI messages (e.g., two DCI messages) for scheduling TB (e.g., initial repetition of TB) and at least one repetition of TB. These multiple DCI messages can indicate corresponding resource allocations for TB and repetitions of TB. That is, the first resource to be used for TB and the second resource to be used for repetitions of TB can at least partially overlap in the time and frequency domains (e.g., partially or completely overlap).
[0096] Base station 110 may send multiple DCI messages, at least in part, based on UE 120 instructing UE 120 to use SDM to send and / or receive TB repetitions scheduled by multiple DCI messages. Furthermore, base station 110 may send the multiple DCI messages after enabling TB repetitions scheduled by multiple DCI messages for UE 120.
[0097] In some respects, before receiving the multiple DCI messages, UE 120 may receive from base station 110 a CORESET configuration (e.g., a configuration of ControlResourceSet parameters) that includes at least two different control resource set (CORESET) pool indexes (e.g., CORESETPoolIndex) values. This configuration may be a PDCCH configuration (e.g., a configuration of a higher-layer parameter PDCCH-Config).
[0098] In some aspects, the plurality of DCI messages may include a first DCI message and a second DCI message. The first DCI message may be associated with a first CORESET that is associated with a first CORESET pool index value (e.g., 0). That is, UE 120 may receive the first DCI message in the first CORESET associated with the first CORESET pool index value. The second DCI message may be associated with a second CORESET that is associated with a second CORESET pool index value (e.g., 1). That is, UE 120 may receive the second DCI message in the second CORESET associated with the second CORESET pool index value.
[0099] In some respects, a first DCI message can schedule the transmission of a first codeword, and a second DCI message can schedule the transmission of a second codeword. For example, a first uplink DCI message can schedule a first uplink codeword, a second uplink DCI message can schedule a second uplink codeword, and the second uplink codeword can be a repetition of the first uplink codeword. As another example, a first downlink DCI message can schedule a first downlink codeword, a second downlink DCI message can schedule a second downlink codeword, and the second downlink codeword can be a repetition of the first downlink codeword.
[0100] In some aspects, the first DCI message and the second DCI message can support the association of TB and TB repetition. For example, a first codeword scheduled by the first DCI message can be used for a TB, and a second codeword scheduled by the second DCI message can be used for TB repetition. In some aspects, the first DCI message and the second DCI message can indicate one or more of the same parameters (e.g., the same Hybrid Automatic Repeat Request (HARQ) process identifier, the same TB size, the same NDI value, etc.) for the first codeword (e.g., for TB) and the second codeword (e.g., for TB repetition). In some aspects, the first DCI message and the second DCI message can indicate corresponding beam indications for the first codeword (e.g., for TB) and the second codeword (e.g., for TB repetition). For example, the first DCI message can indicate the first TCI state, SRI, SRS resource set indicator, etc., of the first codeword, and the second DCI message can indicate the second TCI state, SRI, SRS resource set indicator, etc., of the second codeword.
[0101] Therefore, multiple DCI messages can schedule a first PUSCH or PDSCH transmission (shown as PUSCH / PDSCH 1) and a second PUSCH or PDSCH transmission (shown as PUSCH / PDSCH 2). The first PUSCH / PDSCH transmission can be associated with a first codeword scheduled by the first DCI message and can be scheduled for transmission or reception using the first antenna panel and first beam of the UE 120. The second PUSCH / PDSCH transmission can be associated with a second codeword scheduled by the second DCI message and can be scheduled for transmission or reception using the second antenna panel and second beam of the UE 120.
[0102] like Figure 5D As shown, with reference numeral 520, base station 110 and UE 120 can communicate based on a single DCI message or multiple DCI messages. Both base station 110 and UE 120 can communicate using multiple antenna panels.
[0103] In some aspects, based on a single DCI message or multiple DCI messages, base station 110 can send downlink TB repetitions, and UE 120 can receive downlink TB repetitions. In this case, UE 120 can use multiple antenna panels to receive downlink TB repetitions. For example, UE 120 can use a first antenna panel and a first beam to receive TB (e.g., the initial repetition of TB), and use a second antenna panel and a second beam to receive TB repetitions. In some aspects, UE 120 can receive TB from a first TRP (e.g., associated with base station 110), and receive TB repetitions from a second TRP (e.g., associated with base station 110 or another base station).
[0104] In some aspects, based on a single DCI message or multiple DCI messages, UE 120 can transmit uplink TB repetitions, and base station 110 can receive uplink TB repetitions. In this case, UE 120 can use multiple antenna panels to transmit uplink TB repetitions. For example, UE 120 can use a first antenna panel and a first beam to transmit TB (e.g., the initial repetition of TB), and use a second antenna panel and a second beam to transmit TB repetitions. In some aspects, UE 120 can transmit TB to a first TRP (e.g., associated with base station 110) and transmit TB repetitions to a second TRP (e.g., associated with base station 110 or another base station).
[0105] As mentioned above, Figures 5A-5D Provided as one or more examples. Other examples may differ from those provided. Figures 5A-5D As described.
[0106] Figure 6 This is a diagram illustrating, for example, an example process 600 performed by a UE according to various aspects of this disclosure. Example process 600 is an example of a UE (e.g., UE 120, etc.) performing operations associated with using SDM to repeat TB.
[0107] like Figure 6 As shown, in some aspects, process 600 may include an indication that the UE is capable of using SDM to transmit or receive TB repetitions (block 610). For example, as described above, the UE (e.g., using controller / processor 280, transmit processor 264, TXMIMO processor 266, MOD 254, antenna 252, etc.) may transmit an indication that the UE is capable of using SDM to transmit or receive TB repetitions.
[0108] like Figure 6As further illustrated, in some aspects, process 600 may include receiving at least one DCI message based at least partially on the indication, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain (box 620). For example, as described above, a UE (e.g., using antenna 252, MOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may receive at least one DCI message based at least partially on the indication, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain.
[0109] like Figure 6 As further illustrated, in some aspects, process 600 may include performing repeated communication between TB and TB using different antenna panels based on the at least one DCI message (block 630). For example, as described above, the UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.) may perform repeated communication between TB and TB using different antenna panels based on the at least one DCI message.
[0110] Process 600 may include additional aspects, such as any single aspect or any combination thereof described below, and / or one or more other processes described elsewhere herein.
[0111] In the first aspect, the instruction indicates that the UE is able to send or receive TB repetitions in multiple codewords scheduled by a single DCI message.
[0112] In the second aspect, either alone or in combination with the first aspect, the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
[0113] In the third aspect, either alone or in combination with one or more of the first and second aspects, the second codeword is a repetition of the first codeword.
[0114] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the first codeword is to be used for TB, and the second codeword is to be used for repetition of TB.
[0115] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the TB size associated with the transmission is at least partially based on the first codeword.
[0116] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 600 includes receiving a configuration that enables TB repetition using SDM, scheduled by a single DCI message.
[0117] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the at least one DCI message indicates that the TB repetition using SDM is scheduled by the at least one DCI message.
[0118] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the RNTI associated with the at least one DCI message indicates that the TB repetition of the SDM is scheduled by the at least one DCI message.
[0119] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the indication indicates that the UE is able to send or receive TB repetitions scheduled by multiple DCI messages.
[0120] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the at least one DCI message includes a first DCI message and a second DCI message, wherein the first DCI message is associated with a first CORESET associated with a first CORESET pool index, and the second DCI message is associated with a second CORESET associated with a second CORESET pool index.
[0121] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the at least one DCI message includes a first DCI message and a second DCI message, wherein the first DCI message schedules the transmission of a first codeword and the second DCI message schedules the transmission of a second codeword.
[0122] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the second codeword is a repetition of the first codeword.
[0123] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the at least one DCI message includes a first DCI message and a second DCI message, and the first DCI message and the second DCI message identify the same HARQ process identifier, the same TB size, the same NDI value and different beam indications.
[0124] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, process 600 includes receiving a configuration that enables TB repetition using SDM, scheduled by multiple DCI messages.
[0125] although Figure 6An example box of process 600 is shown, but in some respects, process 600 may include more than Figure 6 The boxes depicted may include more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 600 may be executed in parallel.
[0126] Figure 7 This is a diagram illustrating, for example, an example process 700 performed by a base station according to various aspects of this disclosure. Example process 700 is an example of a base station (e.g., base station 110, etc.) performing operations associated with using SDM to repeat TB.
[0127] like Figure 7 As shown, in some aspects, process 700 may include receiving an indication that the UE is capable of using SDM to transmit or receive TB repetitions (block 710). For example, as described above, the base station (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, etc.) may receive an indication that the UE is capable of using SDM to transmit or receive TB repetitions.
[0128] like Figure 7 As further illustrated, in some aspects, process 700 may include transmitting at least one DCI message based at least partially on the instruction, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain (box 720). For example, as described above, a base station (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.) may transmit at least one DCI message based at least partially on the instruction, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain.
[0129] like Figure 7 As further illustrated, in some aspects, process 700 may include repeating communication between TB and TB based on the at least one DCI message (block 730). For example, as described above, a base station (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, etc.) may perform repeating communication between TB and TB based on the at least one DCI message.
[0130] Process 700 may include additional aspects, such as any single aspect or any combination thereof described below, and / or one or more other processes described elsewhere herein.
[0131] In the first aspect, the instruction indicates that the UE is able to send or receive TB repetitions in multiple codewords scheduled by a single DCI message.
[0132] In the second aspect, either alone or in combination with the first aspect, at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
[0133] In the third aspect, either alone or in combination with one or more of the first and second aspects, the second codeword is a repetition of the first codeword.
[0134] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the first codeword is to be used for TB, and the second codeword is to be used for repetition of TB.
[0135] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the TB size associated with the transmission is at least partially based on the first codeword.
[0136] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 700 includes sending a configuration that enables TB repetition using SDM, scheduled by a single DCI message.
[0137] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the at least one DCI message indicates that the TB repetition using SDM is scheduled by the at least one DCI message.
[0138] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the RNTI associated with the at least one DCI message indicates that the TB repetition of the SDM is scheduled by the at least one DCI message.
[0139] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the indication indicates that the UE is able to send or receive TB repetitions scheduled by multiple DCI messages.
[0140] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the at least one DCI message includes a first DCI message and a second DCI message, wherein the first DCI message is associated with a first CORESET associated with a first CORESET pool index, and the second DCI message is associated with a second CORESET associated with a second CORESET pool index.
[0141] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the at least one DCI message includes a first DCI message and a second DCI message, wherein the first DCI message schedules the transmission of a first codeword and the second DCI message schedules the transmission of a second codeword.
[0142] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the second codeword is a repetition of the first codeword.
[0143] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the at least one DCI message includes a first DCI message and a second DCI message, and the first DCI message and the second DCI message identify the same HARQ process identifier, the same TB size, the same NDI value and different beam indications.
[0144] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 700 includes sending a configuration that enables TB repetition using SDM, which is scheduled by multiple DCI messages.
[0145] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include more than Figure 7 The boxes depicted may include more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 700 may be executed in parallel.
[0146] Figure 8 This is a conceptual data flow diagram 800 illustrating the data flow between different components in example device 802. Device 802 may be a UE (e.g., UE 120). In some aspects, device 802 includes a transmitting component 804 and / or a receiving component 806.
[0147] In some respects, the transmitting component 804 can transmit an indication that the transmitting device 802 can use SDM to transmit or receive a TB repetition. For example, the transmitting component 804 can transmit the indication to the transmitting device 850 (e.g., base station 110).
[0148] In some aspects, receiving component 806 can receive at least one DCI message that schedules a TB in a first resource and a repetition of that TB in a second resource. For example, receiving component 806 can receive the at least one DCI message from device 850. The first resource and the second resource may at least partially overlap in the time and frequency domains. Receiving component 806 can receive the at least one DCI message at least in part based on the indication sent by transmitting component 804.
[0149] In some aspects, the transmitting component 804 and / or the receiving component 806 can communicate TB and TB repetitions based on the at least one DCI message. For example, the transmitting component 804 and / or the receiving component 806 can communicate with the device 850. In some aspects, the transmitting component 804 can transmit TB and TB repetitions. In some aspects, the receiving component 806 can receive TB and TB repetitions.
[0150] Device 802 may include performing the aforementioned Figure 6 Each box of the algorithm in process 600 is an additional component. (The aforementioned...) Figure 6 Each block in process 600 can be executed by a component, and device 802 can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or implemented by some combination thereof.
[0151] Figure 8 The number and arrangement of components shown are provided as an example. In practice, with... Figure 8 Compared to what is shown, there can be additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The set of components shown (e.g., one or more components) can perform actions described by Figure 8 The other set of components shown performs one or more functions.
[0152] Figure 9 This is a conceptual data flow diagram 900 illustrating the data flow between different components in example device 902. Device 902 may be a base station (e.g., base station 110). In some aspects, device 902 includes a receiving component 904 and / or a transmitting component 906.
[0153] In some respects, receiving component 904 may receive indications that device 950 (e.g., UE 120) is capable of using SDM to send or receive TB repetitions. For example, receiving component 904 may receive such indications from device 950.
[0154] In some aspects, transmitting component 906 can transmit at least one DCI message that schedules the repetition of TBs in a first resource and in a second resource. For example, transmitting component 906 can transmit the at least one DCI to device 950. The first and second resources may at least partially overlap in the time and frequency domains. Transmitting component 906 may transmit the at least one DCI message at least in part based on receiving component 904 receiving the instruction.
[0155] In some aspects, receiving component 904 and / or transmitting component 906 can perform communication of TB and TB repetitions based on the at least one DCI message. For example, receiving component 904 and / or transmitting component 906 can communicate with device 950. In some aspects, receiving component 904 can receive TB and TB repetitions. In some aspects, transmitting component 906 can transmit TB and TB repetitions.
[0156] Device 902 may include performing the aforementioned Figure 7 The process 700 is an additional component of each box of the algorithm, etc. (The aforementioned...) Figure 7 Each block in process 700 can be executed by a component, and device 902 can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or implemented by some combination thereof.
[0157] Figure 9 The number and arrangement of components shown are provided as an example. In practice, with... Figure 9 Compared to what is shown, there can be additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The set of components shown (e.g., one or more components) can perform actions described by Figure 9 The other set of components shown performs one or more functions.
[0158] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit these aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from practice in these aspects.
[0159] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented as a combination of hardware, firmware, and / or hardware and software.
[0160] As used in this article, depending on the context, satisfying the threshold can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.
[0161] It is evident that the systems and / or methods described herein can be implemented using various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, this document describes the operation and behavior of the systems and / or methods without reference to specific software code, and it should be understood that software and hardware can be designed to implement the systems and / or methods, at least in part, based on the description herein.
[0162] Even if a specific combination of features is stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically stated in the claims and / or not disclosed in the specification. Although each listed dependent claim may directly depend on only one claim, the disclosure of aspects includes combinations of each dependent claim with every other claim in the claim set. The phrase referring to “at least one” in a series of items means any combination of these items, including single members. For 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 of multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and cccc, or any other order of a, b, and c).
[0163] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with “one or more.” If referring to only one item, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “having,” “possessing,” and / or similar terms are intended to be open-ended terms. Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated.
Claims
1. A method for wireless communication performed by a user equipment (UE), comprising: Send an indication to the network entity that the UE is capable of transmitting or receiving repeating transport block TB in multiple codewords using spatial multiplexing (SDM); At least one downlink control information (DCI) message is received from the network entity and at least in part based on the indication, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; as well as Based on the at least one DCI message, different antenna panels are used to perform repeated communication between the TB and the TB.
2. The method of claim 1, wherein the indication indicates that the UE is able to send or receive TB repetitions in the plurality of codewords scheduled by a single DCI message.
3. The method according to claim 1, wherein the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
4. The method according to claim 3, wherein the second codeword is a repetition of the first codeword.
5. The method of claim 3, wherein the first codeword is to be used for the TB, and the second codeword is to be used for repetition of the TB.
6. The method of claim 5, wherein the TB size associated with the transmission is at least partially based on the first codeword.
7. The method according to claim 1, further comprising: Receive configurations that enable TB repetition using SDM, which are scheduled by a single DCI message.
8. The method of claim 1, wherein the at least one DCI message indicates that the TB repetition using SDM is scheduled by the at least one DCI message.
9. The method of claim 1, wherein the radio network temporary identifier associated with the at least one DCI message indicates that a TB repeat using SDM is scheduled by the at least one DCI message.
10. The method of claim 1, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions scheduled by a plurality of DCI messages.
11. The method of claim 1, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message is associated with a first CORESET linked to a first control resource set CORESET pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
12. The method of claim 1, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message schedules the transmission of the first codeword, and the second DCI message schedules the transmission of the second codeword.
13. The method of claim 12, wherein the second codeword is a repetition of the first codeword.
14. The method of claim 1, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message and the second DCI message share the same Hybrid Automatic Repeat Request Process Identifier, the same TB size, the same New Data Indicator value, and different beam indicators.
15. The method according to claim 1, further comprising: Receive configurations that enable TB repetition using SDM, which are scheduled by multiple DCI messages.
16. A method for wireless communication performed by a network entity, comprising: The user equipment (UE) receives an indication that the UE is capable of transmitting or receiving repeating transport block (TB) in multiple codewords using spatial multiplexing (SDM). At least one downlink control information (DCI) message is sent to the UE and at least in part based on the indication, the DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; as well as Repeated communication between the TB and the TB is performed based on the at least one DCI message.
17. The method of claim 16, wherein the indication indicates that the UE is able to send or receive TB repetitions in the plurality of codewords scheduled by a single DCI message.
18. The method of claim 16, wherein the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
19. The method of claim 18, wherein the second codeword is a repetition of the first codeword.
20. The method of claim 18, wherein the first codeword is to be used for the TB, and the second codeword is to be used for repetition of the TB.
21. The method of claim 20, wherein the TB size associated with the transmission is at least partially based on the first codeword.
22. The method of claim 16, further comprising: Sending configurations that enable TB repetition using SDM, scheduled by a single DCI message.
23. The method of claim 16, wherein the at least one DCI message indicates that the TB repetition using SDM is scheduled by the at least one DCI message.
24. The method of claim 16, wherein the radio network temporary identifier associated with the at least one DCI message indicates that a TB repeat using SDM is scheduled by the at least one DCI message.
25. The method of claim 16, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions scheduled by a plurality of DCI messages.
26. The method of claim 16, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message is associated with a first CORESET linked to a first control resource set CORESET pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
27. The method of claim 16, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message schedules the transmission of the first codeword, and the second DCI message schedules the transmission of the second codeword.
28. The method of claim 27, wherein the second codeword is a repetition of the first codeword.
29. The method of claim 16, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message and the second DCI message share the same Hybrid Automatic Repeat Request Process Identifier, the same TB size, the same New Data Indicator value, and different beam indicators.
30. The method of claim 16, further comprising: Sending configurations that enable TB duplication using SDM, which are scheduled by multiple DCI messages.
31. A user equipment (UE) for wireless communication, comprising: Memory; as well as One or more processors, operatively coupled to the memory, are configured to cause the UE to: Send an indication to the network entity that the UE is capable of transmitting or receiving repeating transport block TB in multiple codewords using spatial multiplexing (SDM); At least one downlink control information (DCI) message is received from the network entity and at least in part based on the indication, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; as well as Based on the at least one DCI message, different antenna panels are used to perform repeated communication between the TB and the TB.
32. The UE of claim 31, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions in the plurality of codewords scheduled by a single DCI message.
33. The UE of claim 31, wherein the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
34. The UE of claim 33, wherein the second codeword is a repetition of the first codeword.
35. The UE of claim 33, wherein the first codeword is to be used for the TB, and the second codeword is to be used for repetition of the TB.
36. The UE of claim 35, wherein the TB size associated with the transmission is at least partially based on the first codeword.
37. The UE of claim 31, wherein the one or more processors are further configured to cause the UE to: Receive configurations that enable TB repetition using SDM, which are scheduled by a single DCI message.
38. The UE of claim 31, wherein the at least one DCI message indicates that a TB repetition using SDM is scheduled by the at least one DCI message.
39. The UE of claim 31, wherein the radio network temporary identifier associated with the at least one DCI message indicates that a TB repeat using SDM is scheduled by the at least one DCI message.
40. The UE of claim 31, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions scheduled by a plurality of DCI messages.
41. The UE of claim 31, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message is associated with a first CORESET linked to a first control resource set CORESET pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
42. The UE of claim 31, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message schedules the transmission of the first codeword, and the second DCI message schedules the transmission of the second codeword.
43. The UE according to claim 42, wherein the second codeword is a repetition of the first codeword.
44. The UE of claim 31, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message and the second DCI message share the same Hybrid Automatic Repeat Request Process Identifier, the same TB size, the same New Data Indicator value, and different beam indicators.
45. The UE of claim 31, wherein the one or more processors are further configured to cause the UE to: Receive configurations that enable TB repetition using SDM, which are scheduled by multiple DCI messages.
46. A network entity for wireless communication, comprising: Memory; as well as One or more processors, operatively coupled to the memory, are configured to cause the network entity to: The user equipment (UE) receives an indication that the UE is capable of transmitting or receiving repeating transport block (TB) in multiple codewords using spatial multiplexing (SDM). At least one downlink control information (DCI) message is sent to the UE and at least in part based on the indication, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; as well as Repeated communication between the TB and the TB is performed based on the at least one DCI message.
47. The network entity of claim 46, wherein the indication indicates that the UE is able to send or receive TB repetitions in the plurality of codewords scheduled by a single DCI message.
48. The network entity of claim 46, wherein the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
49. The network entity of claim 48, wherein the second codeword is a repetition of the first codeword.
50. The network entity of claim 48, wherein the first codeword is to be used for the TB, and the second codeword is to be used for repetition of the TB.
51. The network entity of claim 50, wherein the TB size associated with the transmission is at least partially based on the first codeword.
52. The network entity of claim 46, wherein the one or more processors are further configured to cause the network entity to: Sending configurations that enable TB repetition using SDM, scheduled by a single DCI message.
53. The network entity of claim 46, wherein the at least one DCI message indicates that a TB repetition using SDM is scheduled by the at least one DCI message.
54. The network entity of claim 46, wherein the radio network temporary identifier associated with the at least one DCI message indicates that a TB repeat using SDM is scheduled by the at least one DCI message.
55. The network entity of claim 46, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions scheduled by a plurality of DCI messages.
56. The network entity of claim 46, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message is associated with a first CORESET linked to a first control resource set CORESET pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
57. The network entity of claim 46, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message schedules the transmission of the first codeword, and the second DCI message schedules the transmission of the second codeword.
58. The network entity of claim 57, wherein the second codeword is a repetition of the first codeword.
59. The network entity of claim 46, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message and the second DCI message share the same Hybrid Automatic Repeat Request Process Identifier, the same TB size, the same New Data Indicator value, and different beam indicators.
60. The network entity of claim 46, wherein the one or more processors are further configured to cause the network entity to: Sending configurations that enable TB duplication using SDM, which are scheduled by multiple DCI messages.
61. A non-transitory computer-readable medium storing one or more instructions for wireless communication, said one or more instructions comprising: One or more instructions, when executed by one or more processors of a user equipment (UE), cause the UE to: Send an indication to the network entity that the UE is capable of transmitting or receiving repeating transport block TB in multiple codewords using spatial multiplexing (SDM); At least one downlink control information (DCI) message is received from the network entity and at least in part based on the indication, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; as well as Based on the at least one DCI message, different antenna panels are used to perform repeated communication between the TB and the TB.
62. The non-transitory computer-readable medium of claim 61, wherein the indication indicates that the UE is able to send or receive TB repetitions in the plurality of codewords scheduled by a single DCI message.
63. The non-transitory computer-readable medium of claim 61, wherein the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
64. The non-transitory computer-readable medium of claim 63, wherein the second codeword is a repetition of the first codeword.
65. The non-transitory computer-readable medium of claim 63, wherein the first codeword is to be used for the TB, and the second codeword is to be used for repetition of the TB.
66. The non-transitory computer-readable medium of claim 65, wherein the TB size associated with the transmission is at least partially based on the first codeword.
67. The non-transitory computer-readable medium of claim 61, wherein, when executed by the one or more processors, the one or more instructions further cause the UE to: Receive configurations that enable TB repetition using SDM, which are scheduled by a single DCI message.
68. The non-transitory computer-readable medium of claim 61, wherein the at least one DCI message indicates that a TB repetition using SDM is scheduled by the at least one DCI message.
69. The non-transitory computer-readable medium of claim 61, wherein the radio network temporary identifier associated with the at least one DCI message indicates that a TB repeat using SDM is scheduled by the at least one DCI message.
70. The non-transitory computer-readable medium of claim 61, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions scheduled by a plurality of DCI messages.
71. The non-transitory computer-readable medium of claim 61, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message is associated with a first CORESET linked to a first control resource set CORESET pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
72. The non-transitory computer-readable medium of claim 61, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message schedules the transmission of the first codeword, and the second DCI message schedules the transmission of the second codeword.
73. The non-transitory computer-readable medium of claim 72, wherein the second codeword is a repetition of the first codeword.
74. The non-transitory computer-readable medium of claim 61, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message and the second DCI message share the same Hybrid Automatic Repeat Request Process Identifier, the same TB size, the same New Data Indicator value, and different beam indicators.
75. The non-transitory computer-readable medium of claim 61, wherein, when executed by the one or more processors, the one or more instructions further cause the UE to: Receive configurations that enable TB repetition using SDM, which are scheduled by multiple DCI messages.
76. A non-transitory computer-readable medium storing one or more instructions for wireless communication, said one or more instructions comprising: One or more instructions, when executed by one or more processors of a network entity, cause the network entity to: The user equipment (UE) receives an indication that the UE is capable of transmitting or receiving repeating transport block (TB) in multiple codewords using spatial multiplexing (SDM). At least partially based on the instruction, at least one downlink control information (DCI) message is sent to the UE, the at least one DCI message scheduling the TB in a first resource and the duplication of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; as well as Repeated communication between the TB and the TB is performed based on the at least one DCI message.
77. The non-transitory computer-readable medium of claim 76, wherein the indication indicates that the UE is able to send or receive TB repetitions in the plurality of codewords scheduled by a single DCI message.
78. The non-transitory computer-readable medium of claim 76, wherein the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
79. The non-transitory computer-readable medium of claim 78, wherein the second codeword is a repetition of the first codeword.
80. The non-transitory computer-readable medium of claim 78, wherein the first codeword is to be used for the TB, and the second codeword is to be used for repetition of the TB.
81. The non-transitory computer-readable medium of claim 80, wherein the TB size associated with the transmission is at least partially based on the first codeword.
82. The non-transitory computer-readable medium of claim 76, wherein, when executed by the one or more processors, the one or more instructions further cause the network entity to: Sending configurations that enable TB repetition using SDM, scheduled by a single DCI message.
83. The non-transitory computer-readable medium of claim 76, wherein the at least one DCI message indicates that a TB repetition using SDM is scheduled by the at least one DCI message.
84. The non-transitory computer-readable medium of claim 76, wherein the radio network temporary identifier associated with the at least one DCI message indicates that a TB repeat using SDM is scheduled by the at least one DCI message.
85. The non-transitory computer-readable medium of claim 76, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions scheduled by a plurality of DCI messages.
86. The non-transitory computer-readable medium of claim 76, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message is associated with a first CORESET linked to a first control resource set CORESET pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
87. The non-transitory computer-readable medium of claim 76, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message schedules the transmission of the first codeword, and the second DCI message schedules the transmission of the second codeword.
88. The non-transitory computer-readable medium of claim 87, wherein the second codeword is a repetition of the first codeword.
89. The non-transitory computer-readable medium of claim 76, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message and the second DCI message share the same Hybrid Automatic Repeat Request Process Identifier, the same TB size, the same New Data Indicator value, and different beam indicators.
90. The non-transitory computer-readable medium of claim 76, wherein, when executed by the one or more processors, the one or more instructions further cause the network entity to: Sending configurations that enable TB duplication using SDM, which are scheduled by multiple DCI messages.
91. An apparatus for wireless communication, comprising: A device module for sending to a network entity an indication that the device is capable of transmitting or receiving repeating transport block (TB) in multiple codewords using spatial multiplexing (SDM). A device module for receiving at least one downlink control information (DCI) message from the network entity and at least in part based on the indication, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; as well as A device module for performing repeated communication between the TB and the TB using different antenna panels based on the at least one DCI message.
92. The apparatus of claim 91, wherein the indication indicates that the apparatus is capable of sending or receiving TB repetitions in the plurality of codewords scheduled by a single DCI message.
93. The apparatus of claim 91, wherein the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
94. The apparatus of claim 93, wherein the second codeword is a repetition of the first codeword.
95. The apparatus of claim 93, wherein the first codeword is to be used for the TB, and the second codeword is to be used for repetition of the TB.
96. The apparatus of claim 95, wherein the TB size associated with the transmission is at least partially based on the first codeword.
97. The apparatus of claim 91, further comprising: A device module for receiving configurations that enable TB repetition using SDM, scheduled by a single DCI message.
98. The apparatus of claim 91, wherein the at least one DCI message indicates that a TB repetition using SDM is scheduled by the at least one DCI message.
99. The apparatus of claim 91, wherein the radio network temporary identifier associated with the at least one DCI message indicates that a TB repeat using SDM is scheduled by the at least one DCI message.
100. The apparatus of claim 91, wherein the indication indicates that the apparatus is capable of sending or receiving TB repetitions scheduled by a plurality of DCI messages.
101. The apparatus of claim 91, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message is associated with a first CORESET linked to a first control resource set CORESET pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
102. The apparatus of claim 91, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message schedules the transmission of the first codeword, and the second DCI message schedules the transmission of the second codeword.
103. The apparatus of claim 102, wherein the second codeword is a repetition of the first codeword.
104. The apparatus of claim 91, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message and the second DCI message share the same Hybrid Automatic Repeat Request Process Identifier, the same TB size, the same New Data Indicator value, and different beam indicators.
105. The apparatus of claim 91, further comprising: A device module for receiving configurations that enable TB repetition using SDM, which are scheduled by multiple DCI messages.
106. An apparatus for wireless communication, comprising: A device module for receiving from a user equipment (UE) an indication that the UE is capable of transmitting or receiving repeating transport block (TB) in multiple codewords using spatial multiplexing (SDM); An apparatus module for sending at least one downlink control information (DCI) message to the UE and at least partially based on the indication, the at least one DCI message scheduling a TB in a first resource and a repetition of the TB in a second resource, the first resource and the second resource at least partially overlapping in the time domain and frequency domain; as well as A device module for performing repeated communication between the TB and the TB based on the at least one DCI message.
107. The apparatus of claim 106, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions in the plurality of codewords scheduled by a single DCI message.
108. The apparatus of claim 106, wherein the at least one DCI message is a single DCI message that schedules the transmission of the first codeword and the second codeword.
109. The apparatus of claim 108, wherein the second codeword is a repetition of the first codeword.
110. The apparatus of claim 108, wherein the first codeword is to be used for the TB, and the second codeword is to be used for repetition of the TB.
111. The apparatus of claim 110, wherein the TB size associated with the transmission is at least partially based on the first codeword.
112. The apparatus of claim 106, further comprising: A device module for sending configurations that enable TB repetition using SDM, scheduled by a single DCI message.
113. The apparatus of claim 106, wherein the at least one DCI message indicates that a TB repetition using SDM is scheduled by the at least one DCI message.
114. The apparatus of claim 106, wherein the radio network temporary identifier associated with the at least one DCI message indicates that a TB repeat using SDM is scheduled by the at least one DCI message.
115. The apparatus of claim 106, wherein the indication indicates that the UE is capable of sending or receiving TB repetitions scheduled by a plurality of DCI messages.
116. The apparatus of claim 106, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message is associated with a first CORESET linked to a first control resource set CORESET pool index, and the second DCI message is associated with a second CORESET linked to a second CORESET pool index.
117. The apparatus of claim 106, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message schedules the transmission of the first codeword, and the second DCI message schedules the transmission of the second codeword.
118. The apparatus of claim 117, wherein the second codeword is a repetition of the first codeword.
119. The apparatus of claim 106, wherein the at least one DCI message comprises a first DCI message and a second DCI message, and The first DCI message and the second DCI message share the same Hybrid Automatic Repeat Request Process Identifier, the same TB size, the same New Data Indicator value, and different beam indicators.
120. The apparatus of claim 106, further comprising: A device module for sending TB repetition configurations using SDM that enable scheduling of multiple DCI messages.
Citation Information
Patent Citations
Data and control transmission enhancements for new radio (NR)
WO2020033884A1