Multi-TB scheduling for single DCI-based multi-TRP and panel transmissions

Abstract

To facilitate the implementation of single DCI-based multi-TRP / panel transmission and multi-TB scheduling for single DCI-based single-TRP / panel transmission. [Solution] The communication device includes a receiver that, in operation, receives single downlink control information (DCI) including scheduling information, wherein the scheduling information indicates the radio resources of a plurality of transport blocks (TBs); and a circuit that, in operation, acquires the radio resources of a plurality of TBs based on the scheduling information.

Description

Technical Field

[0001] The following disclosure relates to a communication device, a base station, a communication method, and an integrated circuit for implementing multi-transmission reception point (TRP) and / or panel transmission based on single downlink control information (DCI) configured during operation and / or multi-transport block (TB) scheduling for single TRP and / or panel transmission based on single DCI.

Background Art

[0002] New Radio (NR) is a new radio air interface developed by the 3rd Generation Partnership Project (3GPP) (registered trademark) for the fifth generation (5G) mobile communication system. 5G is expected to support a wide range of use cases including enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communications (mMTC), with high flexibility, scalability, and efficiency.

[0003] One of the important objectives of 5G is to enable connected industries. 5G connectivity can play a catalytic role in the next wave of industrial transformation and digitization, bringing improvements such as enhanced flexibility, increased productivity and efficiency, reduced maintenance costs, and improved operational safety. Devices in such an environment include, for example, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, etc. It is desired to connect these sensors and actuators to a 5G network.

[0004] Furthermore, 5G connectivity can also act as a catalyst for the next wave of smart city innovation. For example, wearables such as smartwatches and smart rings, e-health devices, medical monitoring equipment, and small devices such as capacity-reducing (RedCap) devices will benefit from improved 5G connectivity. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 38.300 v15.6.0 [Non-Patent Document 2] 3GPP TS 38.211 v15.6.0 [Non-Patent Document 3] ITU-R M.2083 [Non-Patent Document 4] TR 38.913 [Non-Patent Document 5] TS 23.501 v16.1.0 [Non-Patent Document 6] TS 38.213 [Overview of the project] [Problems that the invention aims to solve]

[0006] However, there has been no discussion to date regarding single DCI-based multi-TRP / panel transmissions configured during operation, as well as multi-TB scheduling for single DCI-based single TRP and / or panel transmissions.

[0007] Therefore, there is a need for a communication device and communication method that can solve the aforementioned problems. Furthermore, by considering the following detailed description and the attached claims together with the attached drawings and the section on the background art of this disclosure, other desirable features and characteristics will become apparent. [Means for solving the problem]

[0008] One non-limiting and exemplary embodiment facilitates the implementation of single DCI-based multi-TRP / panel transmission and multi-TB scheduling for single DCI-based single-TRP / panel transmission in operation. This includes the case of implementations in which single-TRP / panel transmission mode is dynamically or semi-statically switched to multi-TRP / panel transmission mode, and vice versa. The switching decision is made by the gNB based on various criteria. For example, by using implicit or explicit indications from the gNB, such as the transmission configuration indicator (TCI) state, only one of multiple TRPs / panels is activated in operation.

[0009] In one embodiment, the technology disclosed herein provides a communication device. For example, the communication device may be a subscriber UE, which may be a regular (non-RedCap or Release 15 / 16 / 17) UE, a RedCap UE, or another similar type of UE. The communication device comprises a receiver that, in operation, receives single downlink control information (DCI) including scheduling information, the scheduling information indicating radio resources of a plurality of transport blocks (TBs); and a circuit that, in operation, acquires radio resources of a plurality of TBs based on the scheduling information.

[0010] In other embodiments, the technology disclosed herein provides a communication device. For example, the communication device may be a base station or gNodeB (gNB) comprising: a circuit that, in operation, generates a single DCI including scheduling information, the scheduling information indicating radio resources of a plurality of transport blocks (TBs); and a transmitter that, in operation, transmits the single DCI to the communication device.

[0011] In other embodiments, the technology disclosed herein provides a communication method, which includes receiving a single DCI containing scheduling information, the scheduling information indicating a plurality of TB radio resources, and acquiring a plurality of TB radio resources based on the scheduling information.

[0012] It should be noted that general or specific embodiments can be implemented as systems, methods, integrated circuits, computer programs, storage media, or any selective combination thereof.

[0013] Further benefits and advantages of the disclosed embodiments will become apparent from this specification and the drawings. These benefits and / or advantages can be obtained individually by the various embodiments and features of this specification and the drawings, and it is not necessary to provide all of these features in order to obtain one or more of such benefits and / or advantages. [Brief explanation of the drawing]

[0014] Those with ordinary art in this field will be able to fully understand and easily grasp the embodiments of this disclosure by reading the following description, which is merely an example, with reference to the drawings. [Figure 1] This figure shows an example of the architecture of a 3GPP NR system. [Figure 2] This is a schematic diagram showing the functional division between NG-RAN and 5GC. [Figure 3] This is a sequence diagram for the RRC connection setup / reconfiguration procedure. [Figure 4] This is a schematic diagram illustrating usage scenarios for high-speed, high-capacity (eMBB: enhanced Mobile Broadband), massive simultaneous connections (mMTC: massive Machine Type Communications), and ultra-reliable and low-latency (URLLC: Ultra Reliable and Low Latency Communications). [Figure 5]It is a block diagram showing an example of a 5G system architecture for a non-roaming scenario. [Figure 6] It is an exemplary illustration of single DCI-based multi-TRP / panel transmission. [Figure 7] It is a diagram showing an example of a method by which a TB is segmented into portions according to various embodiments. [Figure 8] It is a diagram showing an example of a new time domain resource assignment (TDRA) table for multi-TB scheduling for TRP / panel transmission in a downlink (DL: Downlink) physical downlink shared channel (PDSCH: Physical Downlink Shared Channel) according to Embodiment 1. [Figure 9] It is a user equipment (UE: user equipment) flowchart for showing a time domain resource assignment (TDRA) for multi-TB scheduling for multi-TRP / panel operation according to Embodiment 1 when multiple TCI states are indicated by a gNB. FIG. 9 also shows that when one TCI state is indicated by a gNB, a single TRP / panel is activated during operation and the TDRA for multi-TB scheduling is then used for single TRP / panel operation. [Figure 10] It is a diagram showing an extended PDSCH-TimeDomainResourceAllocation information element (IE: information element) indicating configuration information according to Embodiment 1. [Figure 11] It is a diagram showing an exemplary table of time domain resource sets of four parts of TRP#1 and TRP#2 according to Embodiment 1. [Figure 12] It is an exemplary illustration of multi-TB scheduling for single DCI-based multi-TRP / panel transmission in TDM according to Embodiment 1. [Figure 13]FIG. is an example of a PDSCH-TimeDomainResourceAllocation IE extended to show configuration information for multi-TB scheduling with repetition according to Embodiment 2. [Figure 14] FIG. is an example of a time domain resource set of four parts of TRP#1 and TRP#2 according to Embodiment 2. [Figure 15] FIG. is an illustrative diagram of multi-TB scheduling with repetition for single DCI-based multi-TRP / panel transmission according to Embodiment 2. [Figure 16] FIG. is an illustrative diagram of multi-TB scheduling with repetition for single DCI-based multi-TRP / panel transmission in a frequency division multiplexing (FDM) scheme according to Embodiment 4. [Figure 17] FIG. is an illustrative diagram of multi-TB scheduling for a cross-carrier scheduling scenario in a plurality of transmission time intervals according to Embodiment 4. [Figure 18] FIG. is a UE flowchart for transmission configuration indicator (TCI) state-based retransmission according to Embodiment 7. FIG. 18 also shows that a single TRP / panel is activated during operation when one TCI state is indicated by the gNB. [Figure 19] FIG. is a flowchart of a communication method for implementing multi-TB scheduling for single DCI-based multi-TRP / panel transmission according to various embodiments. [Figure 20] FIG. is a schematic diagram of a communication device that can be used for implementing multi-TB scheduling for single DCI-based multi-TRP / panel transmission according to various embodiments.

[0015] Those skilled in the art will understand that the elements in the figures are illustrated in a concise and clear manner and are not necessarily drawn to the correct scale. To facilitate a deeper understanding of embodiments of the present invention, for example, the dimensions of some elements in the illustrations, block diagrams, or flowcharts may be exaggerated compared to other elements. [Modes for carrying out the invention]

[0016] Some embodiments of this disclosure will be described only as examples, with reference to the drawings. Similar reference numerals and letters in the drawings refer to similar or equivalent elements.

[0017] <5G NR System Architecture and Protocol Stack> 3GPP is working on the next release of fifth-generation cellular technology (simply called 5G), which will include the development of a new radio access technology (NR) that will operate at frequencies up to 100 GHz. The first version of the 5G standard will be completed at the end of 2017, which will allow for testing and commercial deployment of smartphones compliant with the 5G NR standard.

[0018] In particular, the overall system architecture envisions an NG-RAN (Next Generation Radio Access Network) with gNBs, which terminate the NG Radio Access User Plane (SDAP / PDCP / RLC / MAC / PHY) and Control Plane (RRC) protocols toward the UE. The gNBs are interconnected with each other via Xn interfaces. Furthermore, the gNBs are connected to the NGC (Next Generation Core) via Next Generation (NG) interfaces, more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that performs the AMF) via the NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity that performs the UPF) via the NG-U interface. Figure 1 shows the NG-RAN architecture (see Section 4 of Non-Patent Literature 1).

[0019] The user plane protocol stack in NR (see, for example, section 4.4.1 of Non-Patent Literature 1) includes the PDCP (Paper Data Convergence Protocol, see section 6.4 of Non-Patent Literature 1) sublayer, the RLC (Radio Link Control, see section 6.3 of Non-Patent Literature 1) sublayer, and the MAC (Medium Access Control, see section 6.2 of Non-Patent Literature 1) sublayer, which are terminated at the gNB on the network side. In addition, a new access layer (AS) sublayer (SDAP: Service Data Adaptation Protocol) is introduced on top of PDCP (see, for example, section 6.5 of Non-Patent Literature 1). A control plane protocol stack is also defined in NR (see, for example, section 4.4.2 of Non-Patent Literature 1). An overview of the Layer 2 functions is described in section 6 of Non-Patent Literature 1. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are described in sections 6.4, 6.3, and 6.2 of Non-Patent Document 1, respectively. The function of the RRC layer is described in section 7 of Non-Patent Document 1.

[0020] The Media Access Control (MAC) layer handles, for example, logical channel multiplexing and scheduling and scheduling-related functions (including processing of various numerologies).

[0021] The physical layer (PHY) is responsible for tasks such as encoding, PHY HARQ processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. Furthermore, the physical layer (PHY) handles the mapping of transport channels to physical channels. The physical layer (PHY) serves the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmitting a particular transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels for uplinks include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel), while for downlinks, there are PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel).

[0022] Use cases / deployment scenarios for NR include Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and Massive Machine Type Communications (mMTC), and these services have diverse requirements regarding data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps downlink and 10 Gbps uplink) and user-perceived data rates on the order of three times that provided by IMT-Advanced. URLLC, on the other hand, imposes more stringent requirements, such as extremely low latency (user plane latency of 0.5 ms for both uplink and downlink) and high reliability (1 to 10⁻⁵ within 1 ms). Furthermore, mMTC may preferably require high connectivity density (1,000,000 devices per 1 km² in urban environments), wide coverage in harsh environments, and extremely long-life batteries (15 years) to reduce device costs.

[0023] Therefore, an OFDM numerology (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) suitable for a certain use case may not function well in another use case. For example, in a low-latency service, a shorter symbol duration (and thus a larger subcarrier spacing) than in mMTC services, and / or fewer symbols per scheduling interval (also referred to as TTI) may preferably be required. Further, in a deployment scenario with a large channel delay spread, a longer cyclic prefix (CP) duration may preferably be required than in a scenario with a short delay spread. In order to maintain a similar cyclic prefix (CP) overhead, the subcarrier spacing should be optimized according to the delay spread. In NR, two or more values of subcarrier spacing may be supported. Therefore, currently, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz,... are being considered. The symbol duration Tu and the subcarrier spacing Δf are directly related by the equation Δf = 1 / Tu. Similar to the case of the LTE system, the term "resource element" can be used to represent the smallest resource unit composed of one subcarrier with respect to the length of one OFDM / SC-FDMA symbol.

[0024] In the new radio system 5G NR, for each numerology and carrier, a resource grid of subcarriers and OFDM symbols is defined in each of the uplink and downlink. Each element in the resource grid is called a resource element and is identified based on the frequency index in the frequency domain and the symbol position in the time domain (see Non-Patent Document 2).

[0025] <5G NR Function Split between NG-RAN and 5GC> Figure 2 shows the function split between NG-RAN and 5GC. The logical nodes of NG-RAN are gNB or ng-eNB. The logical nodes of 5GC are AMF, UPF, and SMF.

[0026] gNB and ng-eNB handle the following key functions in particular:

[0027] - Radio Resource Management functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and dynamic resource allocation (scheduling) to UEs in both uplink and downlink directions. - IP header compression, encryption, and data integrity protection - Selection of AMF when UE attaches if routing to AMF cannot be determined from the information provided by the UE. - Routing user plane data to UPF - Routing of control plane information to AMF - Establishing and releasing connections - Scheduling and sending paging messages - Scheduling and transmission of system broadcast information (sent from AMF or OAM) - Setting up measurements and measurement reporting for mobility and scheduling. - Transport-level packet marking in uplink - Session management - Support for network slicing - QoS flow management and mapping to data radio bearers - Support for UEs in the RRC_INACTIVE state - NAS message delivery function - Wireless access network sharing - Double connection - Close interworking between NR and E-UTRA

[0028] The Access and Mobility Management Function (AMF) handles the following key functions: - Termination of Non-Access Stratum (NAS) signaling - NAS signaling security - Security control at the Access Layer (AS) - Core Network (CN) node-to-node signaling for mobility between 3GPP access networks - Reachability of idle mode UE (including control and execution of paging retransmissions) - Registration Area Management - Support for intra-system and inter-system mobility - Access Authentication - Access authentication including roaming rights check - Mobility management and control (subscriptions and policies) - Support for network slicing - Selection of Session Management Function (SMF)

[0029] Furthermore, the User Plane Function (UPF) handles the following key functions: - Anchor points for mobility within / between RATs (when applicable) - External PDU session points for interconnection with the data network - Packet routing and forwarding - User plane portion of packet inspection and policy rule enforcement - Traffic usage report - Uplink classifier to support routing of traffic flow to data networks - Branching points to support multi-homed PDU sessions - QoS processing in the user plane (e.g., packet filtering, gating, UL / DL rate enforcement) - Verification of uplink traffic (mapping from SDF to QoS flow) - Buffering of downlink packets and triggering of downlink data notifications

[0030] Finally, the Session Management Function (SMF) processes the following main functions. - Session management - Allocation and management of UE IP addresses - Selection and control of the UP function - Configuration of traffic steering in the User Plane Function (UPF) to route traffic to the correct destination - Policy enforcement and the QoS control part - Downlink data notification

[0031] <Procedures for RRC connection setup and reconfiguration> Figure 3 illustrates the interaction between the UE, gNB, and AMF in the NAS portion when the UE transitions from RRC_IDLE to RRC_CONNECTED (see Non-Patent Literature 1). RRC is a higher-layer signaling (protocol) used for configuring the UE and gNB. Specifically, in this transition, the AMF creates UE context data (e.g., including PDU session context, security key, UE radio capability, UE security capability, etc.) and sends it to the gNB via INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE, which is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding to the gNB with a SecurityModeComplete message. The gNB then performs a reconfiguration to establish the signaling radio bearer 2 (SRB2) and data radio bearer (DRB), which is done by the gNB sending an RRCReconfiguration message to the UE, and the gNB receiving an RRCReconfigurationComplete from the UE in response. In the case of a signaling-only connection, SRB2 and DRB are not established, so these steps related to RRCReconfiguration are skipped. Finally, the gNB notifies the AMF that the establishment procedure is complete via the INITIAL CONTEXT SETUP RESPONSE.

[0032] Accordingly, this disclosure provides a fifth-generation core (5GC) entity (e.g., AMF, SMF, etc.) comprising, during operation, a control circuit for establishing a next-generation (NG) connection with a gNodeB, and, during operation, a transmitter for sending an initial context setting message to the gNodeB via the NG connection to establish a signaling radio bearer between the gNodeB and the user equipment (UE). Specifically, the gNodeB sends RRC (Radio Resource Control) signaling, including resource allocation setting information elements, to the UE via the signaling radio bearer. The UE performs uplink transmission or downlink reception based on the resource allocation setting.

[0033] <IMT Usage Scenarios from 2020 Onward> Figure 4 illustrates some use cases for 5G NR. The 3GPP (Third Generation Partnership Project) New Radio (3GPP NR) considers three use cases envisioned to support various services and applications under IMT-2020. Phase 1 specifications for Enhanced Mobile Broadband (eMBB) have been finalized. Current and future work includes further expanding eMBB support, as well as standardization of Ultra-Reliable Low-Latency Communications (URLLC) and Massive Machine-Type Communications. Figure 4 shows some examples of envisioned use scenarios for IMT-2000 and beyond (see, for example, Figure 2 in Non-Patent Document 3).

[0034] URLLC use cases have stringent requirements regarding capabilities such as throughput, latency, and availability, and are envisioned as one means of realizing future vertical applications such as wireless control of industrial manufacturing and production processes, remote medical surgery, power distribution automation in smart grids, and transportation safety. The ultra-high reliability of URLLC is supported by identifying the technology to meet the requirements set out in Non-Patent Document 4. In NR URLLC of Release 15, a key requirement is a target user plane latency of 0.5 ms for both UL (uplink) and DL (downlink), respectively. Typical URLLC requirements for a single packet transmission are a BLER (block error rate) of 1E-5 for a packet size of 32 bytes with a user plane latency of 1 ms.

[0035] From a physical layer perspective, several ways to improve reliability are possible. Current approaches to reliability improvements include defining separate CQI tables for URLLC, a more compact Downlink Control Information (DCI) format, and PDCCH iteration. However, as NR becomes more stable and development progresses (regarding key requirements for NR URLLC), the scope for achieving ultra-high reliability may expand. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0036] Furthermore, the technical enhancements targeted by NR URLLC aim to improve latency and reliability. Technical enhancements to improve latency include configurable numerology, non-slot-based (mini-slot-based) scheduling using flexible mapping, grant-free (configured grant) uplinks, slot-level iteration on data channels, and downlink preemption. Preemption means that a transmission for which resources have already been allocated is aborted, and the allocated resources are used for another transmission requested later with lower latency / higher priority requirements. Thus, a transmission that has already been permitted is preempted by a later transmission. Preemption applies regardless of service type. For example, a transmission of service type A (URLLC) can be preempted by a transmission of service type B (e.g., eMBB). Technical enhancements related to improved reliability include a dedicated CQI / MCS table for the 1E-5 target BLER.

[0037] The use case for mMTC (Massive Machine Type Communication) is characterized by a very large number of connected devices transmitting relatively small amounts of data, which are generally less affected by latency. These devices are required to be low-cost and have extremely long battery life. From a noise reduction (NR) perspective, utilizing a very narrow bandwidth is one possible solution to achieve power savings from a UE perspective and enable long battery life.

[0038] As described above, it is predicted that the reliability range in NR will expand. One important requirement necessary in all cases, especially in the case of URLLC and mMTC, is high reliability or ultra-high reliability. From the perspective of wireless and network, several mechanisms for improving reliability can be considered. Generally, there are several important areas that may help improve reliability. These areas include compact control channel information, repetition of data channels / control channels, diversity related to the frequency domain, time domain, and / or spatial domain. These areas are generally applicable to reliability regardless of the specific communication scenario.

[0039] In the case of NR URLLC, further use cases with more stringent requirements have been identified, such as factory automation, transportation, and power distribution. The more stringent requirements include, depending on the use case, higher reliability (up to the 10-6 level), higher availability, a packet size of up to 256 bytes, time synchronization on the order of several μs (1 μs to several μs depending on the frequency range), a short latency on the order of 0.5 to 1 ms, especially a target user plane latency of 0.5 ms.

[0040] Furthermore, in the case of NR URLLC, several technical enhancements have been identified from the perspective of the physical layer. In particular, enhancements related to PDCCH (Physical Downlink Control Channel) include compact DCI, repetition of PDCCH, and increased PDCCH monitoring. Also, enhancements related to UCI (Uplink Control Information) include enhancements of HARQ (Hybrid Automatic Repeat Request) and CSI feedback. In addition, enhancements of PUSCH related to hopping at the mini-slot level and enhancements of retransmission / repetition have also been recognized. The term "mini-slot" means a TTI (Transmission Time Interval) that contains fewer symbols than a slot (a slot contains 14 symbols).

[0041] <QoS Control> The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bitrate (GBR QoS flows) and QoS flows that do not require a guaranteed flow bitrate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the finest granularity of QoS differentiation within a PDU session. Within a PDU session, QoS flows are identified by a QoS flow ID (QFI) transmitted in the encapsulation header via the NG-U interface.

[0042] The 5GC establishes one or more PDU sessions for each UE. The NG-RAN establishes at least one data radio bearer (DRB) with each UE along with the PDU session, and can then configure additional DRBs for the QoS flow of that PDU session, as described above, for example, with reference to Figure 3 (the NG-RAN decides when to configure them). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filtering in the UE and 5GC associates UL and DL packets with QoS flows, and AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0043] Figure 5 shows the non-roaming standard architecture for 5G NR (see Section 4.23 of Non-Patent Document 5). Application Functions (AFs) (e.g., external application servers handling 5G services as illustrated in Figure 4) interact with the 3GPP core network for the purpose of providing services. For example, they support the application's influence on traffic routing, access Network Exposure Functions (NEFs), and interact with policy frameworks for policy control (e.g., QoS control) (see Policy Control Functions (PCFs)). Based on the operator's deployment, application functions (AFs) that are considered trusted by the operator may be allowed to interact directly with the relevant Network Functions. Application functions (AFs) that are not authorized by the operator to directly access Network Functions interact with the relevant Network Functions using external exposure frameworks via NEFs.

[0044] Figure 5 shows further functional units of the 5G architecture, namely the Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN) (e.g., operator services, internet access, or third-party services). All or some of the core network functions and application services may be deployed and run in a cloud computing environment.

[0045] Single DCI-based multi-transmit / receive point (multi-TRP) or panel transmission is supported in NR. A gNB can schedule transport blocks (TBs) in a DL from multiple TRPs, where TBs from different TRPs are transmitted on different layers, as illustrated in Figure 600. For example, a TB is transmitted from TRP#1 602 to communication device 606 via PDCCH on layer #1, and the same TB is transmitted from TRP#2 604 to communication device 606 on layer #2. The TCI state within the DCI indicates the TRP or panel associated with the TB. A single DCI can schedule only a single TB. Repetition of a single TB in a DL from multiple TRPs using a single DCI is also supported. Furthermore, multiple TBs in a UL scheduled by a single DCI are supported in NR-U for single-TRP configurations, and multiple TBs in a DL or UL scheduled by a single DCI are supported for single TRP in LTE Enhanced Machine-Type Communication / Narrowband Internet of Things (eMTC / NB-IoT).

[0046] Since DCI-only slots without TB scheduling in DL or UL consume UE power, it is desirable to provide a solution to address this problem. For example, a gNB can reduce the number of DCI-only slots and reduce UE power consumption by scheduling two or more TBs with a single DCI (i.e., multi-TB scheduling). Furthermore, this multi-TB scheduling with a single DCI should be applied to multi-TRP / panel scenarios to obtain the benefits of multi-TRP / panel. It will be understood that "multiple TBs" can be used interchangeably with "plurality of TBs".

[0047] According to Embodiment 1, the DCI indicates two or more TCI states, each indicated TCI state corresponding to the activation of one TRP or panel, and scheduling DL radio resources for multiple TBs by indicating an entry in the Time-Domain Resource Allocation (TDRA) table. In the entry, each of the multiple TBs is defined by a start and length indicator value (SLIV) and its association with one of the indicated TCI states. Alternatively, a start symbol and allocation length may be used instead of the start and length indicator value (SLIV), or a slot offset may be used. Furthermore, a TRP or panel may be used instead of an indicated TCI state. It is understood that the TCI states and TRPs are interchangeable in the embodiments and examples described herein, for example, TCI state #1 corresponds to TRP #1, TCI state #2 corresponds to TRP #2, and so on.

[0048] Furthermore, the DCI indicates the TCI state of the code point corresponding to the activation of a single TRP or panel. In this way, the single TRP / panel transmit mode is dynamically switched to the multi-TRP / panel transmit mode, and vice versa. The switching decision is made by the gNB and signaled to the UE based on several TCI states indicated in the DCI. For example, if a TCI state is indicated in the DCI, either TRP#1 or TRP#2 will be activated during operation.

[0049] According to Embodiment 1, the DCI schedules the radio resources of multiple TBs associated with a given TCI state by indicating a TCI state corresponding to the activation of one TRP or panel.

[0050] In Modification 1.0 of Embodiment 1, the association between each of a plurality of TBs and one of the indicated TCI states is indicated either explicitly or implicitly. In an explicit manner, this association is indicated using at least a DCI, MAC control element (CE), or RRC message. In an implicit manner, this association is indicated by a pre-configured rule. For example, TBs with even indices are associated with TCI states with even indices, and TBs with odd indices are associated with TCI states with odd indices. In other examples, this association is defined based on a link between each indicated TCI state of a plurality of TBs and scheduled DL or UL radio resource parameters, including at least an SLIV, start symbol, allocation length, or slot offset.

[0051] In Modification 1.1 of Embodiment 1, multiple (L) TBs are segmented into multiple (K) parts, and the size of each part can be settable. Instead of "each of the multiple TBs" in Embodiment 1, Modification 1.1 uses "each of the multiple parts". An example of this segmentation is shown in Figure 7, diagram 700. L TBs (TB#1 702, TB#2 704~TB#L 706) are segmented into K parts (part #1 722~part #K 724). The TBs include multiple code block groups (CBGs), namely CBG#1 708, CBG#2 710, CBG#M 712, CBG#M+1 714, CBG#2M 716, CBG#(L+1)M+1 718~CBG#LM 720. Since each part can consist of a different number of CBGs, their sizes can differ from one another. For example, part #1 722 consists of CBG #1 708 and CBG #2 710, i.e., the size of two CBGs. On the other hand, part #K 724 does not necessarily contain the same number of CBGs as part #1 722. Furthermore, each part can contain one or more CBGs from one TB or different TBs. The size of each part can be less than, equal to, or greater than the size of the TB. The number of CBGs in each part can be the same or different between parts. It will be understood that "plurality of portions" can be used interchangeably with "multiple portions".

[0052] In variation 1.1a, each of the multiple parts contains one or more TBs, i.e., TB groups, per TRP / panel. In another variation 1.1b, the size of each part is set based on the quality of the communication link between the TCI state (TRP) associated with it and the UE. For example, more CBGs can be configured to contain one part and / or more parts associated with good channel state TCI states, or vice versa. This advantageously allows for adaptation to channel states, improving system performance in terms of spectrum and energy efficiency.

[0053] In Modification 1.2, each of the multiple parts contains one or more TBs from multiple TBs, and two or more TBs related to different TRPs among the multiple TBs may be associated with different parts. Furthermore, two or more TBs related to the same TRP among the multiple TBs may be associated with a single part.

[0054] In Modification 1.3 of Embodiment 1, a new TDRA table is created by adding a new entry to extend the PDSCH-TimeDomainResourceAllocation information element (IE) to support multi-TB scheduling. A single bit field (i.e., the TDRA field) of a single DCI is used to indicate the configuration information for each part. In Modification 1.4, for each part, the TDRA entry additionally includes one or a combination of the following: part index (part #k), the slot offset of the corresponding part transmission after the scheduling DCI slot offset (K0k), the association of this part with different spatial information, a redundant version (RV), and the mapping type. Furthermore, the slot offset of the corresponding part transmission is also determined based on the gap or interval between the corresponding part transmission and one of the other part transmissions. In this way, multiple parts can be transmitted in consecutive or discontinuous slots, and it is possible or impossible to transmit them consecutively in the time domain.

[0055] An example of the new TDRA table 800 is shown in Figure 8. For example, referring to DCI index 0, the PDSCH mapping type is indicated as "B". There are two TRP / TCI states, namely TRP#1 (TCI state #1) and TRP#2 (TCI state #2). TRP#1 (TCI state #1) has two transmissions indicated by time-domain entries {K0k, part #k, Sk, Lk} and {K0j, part #j, Sj, Lj}, and TRP#2 (TCI state #2) also has two transmissions indicated by time-domain entries {K0e, part #e, Se, Le} and {K0f, part #f, Sf, Lf}. Furthermore, K0j can also be determined as K0k+w, where w is the gap or interval between the transmission of part #j and the transmission of part #k. As in Variant 1.3, each time-domain entry includes one or a combination of the following: a partial index (part #k), a slot offset (K0k) for the corresponding partial transmission after the scheduling DCI slot offset, an association between this part and different spatial information, a redundant version (RV), and a mapping type.

[0056] In Modification 1.5, multiple parts are transmitted or received by a single DCI in the same and / or different slots based on their slot offsets (i.e., cross-slot scheduling). In Modification 1.6, multiple parts are transmitted or received in the same slot as a single DCI when the slot offset is 0 (i.e., same-slot scheduling).

[0057] In Modification 1.7, for each TCI state, only one of several associated parts is set by a reference signal (RS) for deriving spatial information, and the remaining parts are set as quasi-co-located (QCL-ed) by this RS (i.e., these remaining parts are not set by a dedicated RS). The advantage of implementing Modification 1.7 is that the system overhead on the air interface is reduced.

[0058] In Modification 1.8, for each TCI state, default spatial information is implicitly or explicitly set for one or more associated parts. The advantage of implementing Modification 1.8 is that if the specified spatial information is not available, the UE can use the default spatial information for channel estimation or precoding.

[0059] It can be assumed that the size of a part is smaller than the TB, or that the TB contains several parts. If each of the multiple parts is associated with spatial information, or if each of these parts is assigned to be transmitted from a different TRP, then the TB has multiple spatial information, i.e., multiple CBGs / parts of this TB have different spatial information. Spatial information from different TRPs to the UE (including QCL types A, B, C, or D) is different from one another.

[0060] Therefore, under Embodiment 1, the UE may operate as follows: The TDRA table signals the UE scheduling information indicating DL / UL radio resources for each of the multiple parts. For each of the multiple parts, the UE uses a 1-bit TDRA field in the scheduling DCI to explicitly or implicitly determine the following: - Time-domain resource sets for each part: Each time-domain resource set {K0k, part #k, Sk, Lk} is mapped one-to-one to each part, and the starting symbol and length values ​​in the slot with an offset from DCI are derived. - Association between each part and one of the indicated TCI states: Based on the location of each part's time-domain resource set in which the assignment is made, i.e., a one-to-one mapping, "TCI state #1" or "TCI state #2". For example, if the DCI index is 0 in table 800 in Figure 8, then {K0k, part #k, Sk, Lk} will be assigned to be associated with TRP #1 (TCI state #1). - The number of transmissions scheduled from the indicated TCI state: This is implicitly derived from the number of time-domain resource sets in a given group associated with the indicated TCI state. For example, if the DCI index is 0 in table 800 in Figure 8, then TCI state #1 has two sets {K0k, part #k, Sk, Lk} and {K0j, part #j, Sj, Lj}, and therefore has two transmissions. This is just one example, and it should be understood that there are many other possibilities in terms of groups depending on the number / order of TRPs, the time-domain resource set, the capabilities of the UE, and / or the implementation of the gNB.

[0061] Based on the derived information and indicated TCI states, the UE decodes or transmits different data from multiple TBs mapped to the corresponding PDSCH receive or PUSCH transmit radio resources. Figure 9 shows a user equipment (UE) flowchart 900 for time division multiplexing (TDM) according to Embodiment 1. In step 902, the UE receives configuration information indicating a new TDRA table for multi-TB scheduling. In step 904, the UE receives the scheduling DCI and checks the TCI state of the TCI code point. In step 906, it is determined whether there is only one TCI state. If so, the process proceeds to step 914, where the UE uses the TDRA table with the new entry. In step 916, the UE obtains the time domain resource for each partial transmission from the TRP / panel. In step 918, the UE receives the multi-TB scheduling data transmission from the TRP / panel based on the assigned associated resource, and the process ends. If it is determined in step 906 that two or more TCI states exist, the process proceeds to step 908, where the UE uses the TDRA table with the new entries. In step 910, the UE retrieves the time domain resources for each partial transmission per TRP / panel. In step 912, the UE receives multi-TB scheduled data transmissions from multi-TRP / panels based on the assigned associated resources, and the process ends.

[0062] In one example of modification 1.3, the PDSCH-TimeDomainResourceAllocation is extended to show the configuration information of Embodiment 1. Referring to Figure 10, which shows the PDSCH-TimeDomainResourceAllocation information element (IE) 1000 extended to show the configuration information according to Embodiment 1, a new entry Multi-MBscheduling 1002 is proposed to show support for multi-TB scheduling, where Sk and Lk are derived using SLIV, maxNrofTCI-States is the maximum number of configured TCI states, and TCI-StateId is the index of the TCI state associated with the corresponding indicated TRP / panel of the TCI code point. A single bit field of DCI is used to show the index of the Time-DomainResourceSet for each partial transmission.

[0063] Figure 11 shows an exemplary table 1100 of the time-domain resource sets for the four parts of TRP#1 and TRP#2 according to an example of Modification 1.1 of Embodiment 1. Figure 12 shows an exemplary diagram 1200 of multi-TB scheduling for single DCI-based multi-TRP / panel transmission in TDM, according to the same example. Two TBs, each having four CBGs, are segmented into four parts. Each part contains two CBGs. These time-domain resource sets for the four parts of TRP#1 and TRP#2 are shown in table 1100 and diagram 1200. Referring to table 1100, for DCI index 0, TRP#1 (TCI state #1) has two parts (part #1{1,1,0,5} and part #4{2,4,7,5}) and TRP#2 (TCI state #2) has two parts (part #2{1,2,6,5} and part #3{2,3,0,5}). If DCI index 0 in table 1100 is shown to the UE, the UE derives the association between the time domain resource set and TRP from the table.

[0064] The time-domain resources allocated to each part are defined as follows: For part #1{1,1,0,5}, the slot offset is 1 slot after the scheduling DCI, the part index is 1, the start symbol is 0, and the length is 5 in slot 1. For part #2{1,2,6,5}, the slot offset is 1 slot after the scheduling DCI, the start symbol is 6, and the length is 5 in slot 1. For part #3{1,1,0,5}, the slot offset is 2 slots after the scheduling DCI, the start symbol is 0, and the length is 5 in slot 2. For part #4{2,4,7,5}, the slot offset is 2 slots after the scheduling DCI, the start symbol is 7, and the length is 5 in slot 2. Regarding the association of each part with one of the indicated TRPs / panels, parts #1 and #4 are sent from TRP#1, and parts #2 and #3 are sent from TRP#2. Furthermore, the actual number of transmissions from TRP#1 and TRP#2 is 2. Therefore, referring to Figure 12, transmission of part #1 is shown at 1202, transmission of part #2 is shown at 1204, transmission of part #3 is shown at 1206, and transmission of part #4 is shown at 1208.

[0065] According to Embodiment 2, instead of the "multiple TBs" in Embodiment 1, multiple repeating TBs can be used. Each of the multiple TBs is associated with one of the indicated TCI states. Alternatively, each repeat of the multiple TBs is associated with one of the indicated TCI states. Advantageously, this configuration supports coverage expansion for non-RedCap UEs and coverage recovery for RedCap UEs. Furthermore, the number of repeats for each of the multiple TBs can be flexibly configured, meaning that each TB can be configured to have a different number of repeats.

[0066] In Modification 2.1 of Embodiment 2, each repetition of a part can be characterized by a higher-layer parameter such as Rk, which can be set as a symbolic value, for example, Rk=0 or absent to indicate the first transmission of the k-th part. The order of the repetitions of the k-th part is set to an ascending rule as a predefined rule. For example, {K0k, part #k, Sk, Lk, Rk=a} means the a-th repetition of part #k, where the value of the slot offset can be different from that of the first transmission of part #k. In another example, for part #1{1,1,0,5,0}, the slot offset is 1 slot from the scheduling DCI. For the second repetition of part #1{2,1,0,5,2}, the slot offset is 2 slots from the scheduling DCI.

[0067] In Modification 2.2 of Embodiment 2, the association and / or spatial information of each part's repetition with one of the indicated TCI states (or TRPs / panels) can be the same as or different from that of the first transmission of this part. In Modification 2.3, different RVs can be applied to each part's repetition. In Modification 2.4, the first transmission of multi-TB scheduling is designed for an indicated TRP with a scheduling DCI called the primary TRP, but the multi-TB scheduling repetitions are used only for the remaining TRPs. The advantage of implementing Modification 2.4 is that it provides diversity gains from multipath transmissions. In Modification 2.5, an interleaving pattern can be applied to the contents of all parts and their repetitions to enable dynamic multi-TB scheduling with repetitions scheduled by DCI. This interleaving pattern can be based on pre-configured rules and can be indicated in the UE. For example, the interleaving pattern can be implicitly indicated by pre-configured rules or explicitly indicated by at least DCI, MAC CE, or RRC signaling. Advantageously, this minimizes the fading effect on data estimation.

[0068] In the examples of modifications 2.1 and 2.2, the PDSCH-TimeDomainResourceAllocation IE is extended to show configuration information for multi-TB scheduling with repetition by adding repetition information. Referring to the PDSCH-TimeDomainResourceAllocation IE1300 shown in Figure 13, the new entries for repetition information are shown in parts 1302 and 1304.

[0069] Examples of time-domain resource sets for the four parts of TRP#1 and TRP#2 are shown in Table 1400 in Figure 14 and Diagram 1500 in Figure 15. DCI index 0 in Table 1400 is shown to the UE, and the UE can derive the time-domain resource set and its association with the TRP accordingly. Referring to Table 1400, the time-domain resources assigned to each part are defined as follows: For part #1 {0,1,2,2,0,0}, the slot offset is 0 slots after the scheduling DCI, the part index is 1, the start symbol is 2, and the length is 2 in slot 0. For the first repeat of part #1 {1,1,12,2,1}, the slot offset is 1 slot after the scheduling DCI, the part index is 1, the start symbol is 12, and the length is 2 in slot 1. For part #2 {0,2,4,2,0}, the slot offset is 0 slots after the scheduling DCI, the sub-index is 2, the starting symbol is 4, and the length is 4 in slot 0. For the first iteration of part #2 {0,2,11,2,1}, the slot offset is 0 slots after the scheduling DCI, the sub-index is 2, the starting symbol is 11, and the length is 2 in slot 0. For part #3 {0,3,7,3,0}, the slot offset is 0 slots after the scheduling DCI, the sub-index is 3, the starting symbol is 7, and the length is 3 in slot 0. For the first iteration of part #3 {1,3,0,3,1}, the slot offset is 1 slot after the scheduling DCI, the sub-index is 2, the starting symbol is 0, and the length is 3 in slot 1. For part #4{1,4,4,3,0}, the slot offset is one slot after the scheduling DCI, the part index is 4, the starting symbol is 4, and the length in slot 1 is 3. For the first repeat of part #4{1,4,8,3,1}, the slot offset is one slot after the scheduling DCI, the part index is 4, the starting symbol is 8, and the length in slot 1 is 3.As shown in Table 1400, with respect to the association of each part with one of the indicated TRPs / panels, part #1, the first repeat of part #3, part #4, and the first repeat of part #4 are sent from TRP #1, while part #2, part #3, the first repeat of part #2, and the first repeat of part #1 are sent from TRP #2. Furthermore, there are four actual transmissions from TRP #1 and TRP #2, and their transmission lengths differ.

[0070] Therefore, referring to Figure 15, the transmission of part #1 is shown at 1502, the first repeated transmission of part #1 is shown at 1504, the transmission of part #2 is shown at 1506, the first repeated transmission of part #2 is shown at 1508, the transmission of part #3 is shown at 1510, the first repeated transmission of part #3 is shown at 1512, the transmission of part #4 is shown at 1514, and the first repeated transmission of part #4 is shown at 1516.

[0071] According to Embodiment 3, instead of "DCI scheduling DL radio resources" as in Embodiment 1 or 2, scheduling can be performed by semi-persistent scheduling (SPS) for DL ​​or configured grant (CG) for UL. Advantageously, with SPS and CG, DCI-free transmission is performed for periodic traffic.

[0072] According to Embodiment 4, instead of using the Time-Domain Resource Assignment (TDRA) table in Embodiment 1 or 2 to represent multiple TBs, a Frequency-Domain Resource Assignment (FDRA) table can be used. For example, DCI represents an entry in the FDRA table. In the entry, multiple TBs are defined by the start and number of PRBs (SNIV) and their association with one of the indicated TCI states. The FDRA table may be set or specified by higher-layer parameters. Entries in the FDRA table can be represented as replacements or additions to frequency-domain resource assignments. In some modifications, a bitmap can be used instead of SNIV. For example, a bitmap may represent a PRB or resource block group (RBG) corresponding to at least one portion and at least one of the indicated TCI states. A TRP or panel can be used instead of an indicated TCI state. The advantage of implementing Embodiment 4 is that the data rate is increased by scheduling multiple TBs in multiple PDSCH transmissions with FDRAs that do not overlap with other PDSCH transmissions.

[0073] In Modification 4.1 of Embodiment 4, at least different modulation orders, coding rates, or redundant versions can be applied to each part from multiple TBs to generate the corresponding PDSCH transmission. In Modification 4.2, instead of the implementation of the "quasi-static configuration base of the current FDRA or FDRA table" in Embodiment 4, the frequency domain resource allocation can be configured by one or a combination of the following: - Dynamic configuration based on FDRA or FDRA tables - In addition to FDRA, an FDRA table is added as an additional allocation. - Each of the multiple dynamic FDRA displays for each of the multiple TCI states

[0074] Figure 16 illustrates an exemplary diagram of multi-TB scheduling with repetitions for single DCI-based multi-TRP / panel transmission in an FDM scheme according to Embodiment 4. For example, assume that physical resource groups (PRGs) #1 and PRG #2 are assigned to TCI states #1 and #2, respectively. Multiple TBs are segmented into four parts of different sizes. Thus, Figure 16 shows an example of time and frequency domain resource sets for the four parts and their repetitions associated with the corresponding TCI states for the corresponding PDSCH transmission opportunities. Part #1 1602, part #4 1614, the first repetition of part #3 1612, and the first repetition of part #4 1616 are associated with TCI state #1, and part #2 1606, part #3 1610, the first repetition of part #1 1604, and the first repetition of part #2 1608 are associated with TCI state #2.

[0075] Embodiment 4 may also be applicable to a cross-carrier scheduling (carrier aggregation) scenario in multiple transmission time intervals (slots or minislots), as shown in Figure 17, diagram 1700. A DCI from a primary cell (PCell) is used to schedule multiple TBs to the PCell and its secondary cells (SCell). Each of the multiple TBs is assigned to one of the serving cells (PCell / PSCell / SCell). The FDRA information for each of the multiple parts is based on the PRB assigned to the serving cell. For example, there is a PCell 1704 with DCI 1702 and two SCells (SCell #1 1706 and SCell #2 1708). The multiple TBs are segmented into six TBs (or six parts). In slot 0, the DCI1702 of PCell1704 is used to schedule parts #1 1710 of PCell1704, part #2 1712 of SCell#1 1706, and part #3 1714 of SCell#2 1708. In slot 1, parts #4 1716 of PCell1704, part #5 1718 of SCell#1 1706, and part #6 1720 of SCell#2 1708 are scheduled by DCI1702 from slot 0.

[0076] In Embodiment 5, code block group (CBG)-based feedback is used in Embodiments 1-4. Each CBG-based feedback in PUCCH or PUSCH corresponds to the CBG of a TB associated with one of the indicated TCI states. If the UE correctly receives all CBs of the CBG, the UE generates an acknowledgment (ACK) for the HARQ-ACK information bits of the CBG; if the UE incorrectly receives at least one CB of the CBG, it generates a negative acknowledgement (NACK) for the HARQ-ACK information bits of the CBG. In Embodiment 5, the number of HARQ-ACK bits is equal to the total number of CBGs from multiple TBs. If multiple TBs are bundled, the number of HARQ-ACK bits is 1. HARQ multiplexing can be applied across CBGs. A PUCCH / PUSCH resource indicator (PRI) is provided by the scheduling DCI. Furthermore, corresponding PUCCH / PUSCH transmissions with HARQ feedback (or response signals) can be processed in various ways. In one option, HARQ feedback from multiple TBs is multiplexed as joint HARQ feedback, sent in a single PUCCH to a TRP with a scheduled DCI, such as TRP#1 (TCI state #1). In another option, each HARQ feedback is sent to its respective TRP. In yet another option, joint HARQ feedback is sent to all TRPs (all TCI states). The advantage of implementing Embodiment 5 is that the retransmission procedure associated with release 15 / 16 can be reused. Furthermore, sending joint HARQ feedback to all TRPs (all TCI states) can improve the robustness of the HARQ feedback.Furthermore, if a PUCCH / PUSCH transmission with HARQ feedback collides with one or more other PUCCH / PUSCH transmissions in the time domain, uplink control information (UCI) multiplexing can be used to carry the HARQ feedback in the corresponding PUCCH / PUSCH transmission. A similar approach also applies to embodiments 6 and 7 below.

[0077] In Embodiment 6, TB-based feedback is used in Embodiments 1-4. Each TB-based feedback in PUCCH / PUSCH corresponds to a TB associated with one of the indicated TCI states, and multiple TBs can have the same HARQ process. For example, if the UE correctly receives all CBs of a TB, the UE generates an ACK for the HARQ-ACK information bits of the TB, and if the UE incorrectly receives at least one CB of a TB, it generates a NACK for the HARQ-ACK information bits of the TB. The number of HARQ-ACK bits is equal to the number of TBs. HARQ multiplexing can be applied across TBs. PUCCH / PUSCH resource indicators are provided by the scheduling DCI. Corresponding PUCCH / PUSCH transmissions with HARQ feedback can also be processed in various ways. Advantageously, by implementing Embodiment 6, HARQ feedback overhead can be reduced.

[0078] In Modification 6.1 of Embodiment 6, if each TB is configured with a different HARQ process, HARQ-related information for each part (or each TCI state) is provided independently. Such information may include a new data indicator (NDI), the number of HARQ processes, redundant versions, PUCCH / PUSCH resource allocation for HARQ feedback, and other similar information.

[0079] In Embodiment 7, TCI state-based feedback is used in Embodiments 1-4. Each TCI state-based feedback in PUCCH / PUSCH corresponds to multiple TBs associated with one of the indicated TCI states. Multiple TCI states have the same HARQ process. For example, if the UE correctly receives all CBs of multiple TBs associated with a TCI state, the UE generates an ACK for the HARQ-ACK information bits of this TCI state, and if the UE incorrectly receives at least one CB of multiple TBs associated with a TCI state, it generates a NACK for the HARQ-ACK information bits of this TCI state. The number of HARQ-ACK bits is equal to the number of TCI states. HARQ multiplexing can also be applied across TCI states. PUCCH / PUSCH resource indicators are provided by the scheduling DCI. Furthermore, corresponding PUCCH / PUSCH transmissions with HARQ feedback can be processed in various ways. Advantageously, compared to CBG-based or TB-based retransmissions, TCI-based feedback generates less HARQ feedback overhead and minimizes the impact of blocking on the probability of requesting a partial retransmission when one of the TCI states (TRPs) is blocked.

[0080] Figure 18 shows a UE flowchart 1800 for TCI state-based retransmission according to Embodiment 7. In step 1802, the UE receives configuration information indicating a TDRA table with new entries for the multi-TB scheduling and retransmission scheme. In step 1804, the UE receives the scheduling DCI and checks the TCI state of the TCI code point. In step 1806, it is determined whether there is only one TCI state. If so, the process proceeds to step 1808, where the UE obtains all CBGs from the indicated TCI state. In step 1810, the UE defines HARQ-ACK feedback behavior only for this TCI state. In step 1812, the UE sends HARQ feedback based on the PRI from the scheduled DCI. The process then terminates. On the other hand, if it is determined in step 1806 that there are two or more TCI states, the process proceeds to step 1814, where the UE obtains associations between each of the multiple CBGs (or parts) and one of the indicated TCI states and defines the number of sets of multiple CBGs per TCI state. In step 1816, the UE defines the HARQ-ACK feedback behavior (i.e., bundling / multiplexing / HARQ-ACK bit count) for each TCI state or for all TCI states. In step 1818, the UE sends HARQ feedback based on the PRI from the scheduled DCI. The process then terminates.

[0081] In embodiments 5, 6, and 7, the HARQ-ACK information / feedback bits are included in the HARQ-ACK codebook, which is set quasi-statically or dynamically by the gNB. For the generation of a quasi-static HARQ-ACK codebook, in release 15 / 16, the procedure is summarized concisely as follows: Step 1: Candidate slots for PDSCH reception are determined by UL slot n and K1 set, and candidate PDSCH reception opportunities are pruned based on TDD settings and all rows r in the TDRA table. · Step 2: For each PDSCH reception opportunity candidate determined in Step 1, HARQ-ACK bits are generated.

[0082] The K1 set is defined in Non-Patent Document 6 according to the DCI format in which the UE is configured to monitor the PDCCH. When dl-DataToUL-ACK-r16 is signaled, the UE shall ignore dl-DataToUL-ACK (without suffix). To enhance the quasi-static HARQ-ACK codebook for multiple PDSCHs scheduled by DCI, the set of PDSCH reception opportunity candidates corresponding to the UL slot having HARQ-ACK transmission is determined as follows based on the set of DL slots and the set of SLIVs corresponding to each DL slot belonging to the set of DL slots. · The set of DL slots includes all unique DL slots that can be scheduled by any row index r of the TDRA table with a DCI indicating the UL slot as the HARQ-ACK feedback timing. · The set of SLIVs corresponding to the DL slots (belonging to the set of DL slots) includes at least all SLIVs that can be scheduled within the DL slot by any row index r of the TDRA table with a DCI indicating the UL slot as the timing of HARQ-ACK feedback.

[0083] Based on this, the UE determines a set of opportunities for PDSCH reception candidates or semi-persistent scheduling (SPS) PDSCH releases according to the pseudo-code structure by using a loop for k < C(K1).

[0084] Furthermore, when generating a dynamic HARQ-ACK codebook, the counter downlink assignment index (C-DAI) or the total downlink assignment index (T-DAI) can be counted per DCI, per PDSCH, or per subset of multiple PDSCHs. If the C-DAI / T-DAI is counted per DCI, there is a limit to the number of PDSCHs that can be scheduled by a DCI. To provide flexibility in the number of PDSCHs scheduled by a DCI, two separate codebooks can be used for single-PDSCH scheduling and multi-PDSCH scheduling by the DCI. This design allows for mixed operation of single-PDSCH scheduling and multi-PDSCH scheduling by the DCI, but there is still a limitation that the number of PDSCHs in multi-PDSCH scheduling must be common. Also, since the number of PDSCHs may change depending on the channel state and / or the length of channel occupancy time (COT), the number of PDSCHs in multi-PDSCH scheduling within a DCI needs to be flexible. Dynamic HARQ-ACK codebook generation requires an increased DAI field size. In Release 15 / 16NR, a 2-bit DAI field can still correctly generate HARQ codebooks even with up to three consecutive DCIs missed. Possible methods for determining the DAI field size to maintain the same robustness when multi-PDSCH scheduling is configured are described below [R1-2105396]. • If only C-DAI is configured, the DAI field size is 2 + log2NMax. • If both T-DAI and C-DAI are configured, the DAI field size is 2 × (2 + log2NMax), If both T-DAI and C-DAI are configured and a group of unscheduled PDSCHs is configured, the DAI field size is 3 × (2 + log2NMax).

[0085] NMax is the maximum number of PDSCH and unscheduled PDSCH groups as defined in TS38.212, where it should be noted that gNB can be triggered to send HARQ-ACKs for "unscheduled PDSCH groups" by the "Number of requested PDSCH groups" field in the DCI (by setting NFI-TotalDAI-Included-r16=enable via RRC). If "Number of requested PDSCH groups" = 0, only HARQ-ACKs for "scheduled PDSCH groups" are sent. If "Number of requested PDSCH groups" = 1, HARQ-ACKs for both "scheduled PDSCH groups" and "unscheduled PDSCH groups" are sent concatenated. Furthermore, another method is to determine the DAI field size of the C-DAI / T-DAI based on the number of SLIVs associated with the row index of the TDRA table, which represents the time-domain allocation resources of multiple PDSCHs scheduled by a single DCI.

[0086] According to the agreement by RAN1#96bis, there are several schemes for multi-TRP-based URLLCs that can be scheduled by at least a single DCI, and these are clarified as follows: Method 2 (FDM): n (n ≤ Nf) TCI states within a single slot, with non-overlapping frequency resource allocations. - Each non-overlapping frequency resource allocation is associated with a single TCI state. - The same single or multiple demodulation reference signal (DMRS) ports are associated with all non-overlapping frequency resource allocations. Method 2a: - A single codeword with one RV is used throughout the entire resource allocation. From the UE's perspective, a common RB mapping (a codeword-to-layer mapping like in Release 15) is applied throughout the entire resource allocation. Method 2b: - A single codeword with one RV is used for each non-overlapping frequency resource allocation. The RVs corresponding to each non-overlapping frequency resource allocation can be the same or different. - It is possible to implement the application of different MCS / modulation orders to different, non-overlapping frequency resource allocations. - It is possible to implement the details of the FDM2a / 2b frequency resource allocation mechanism regarding allocation granularity and time-domain allocation. Method 3 (TDM): n (n ≤ Nt1) TCI states within a single slot, with non-overlapping time resource allocations. - Each TB transmission opportunity has one TCI and one RV at the time granularity of the minislot. - All transmission opportunities(s) within the slot use a common MCS with the same single or multiple DMRS ports(s). - The RV / TCI status may be the same or different between transmission opportunities. - Future challenges (FFS): Channel estimation interpolation across mini-slots with the same TCI index. Method 4 (TDM): n (n ≤ Nt²) TCI states with K (n ≤ K) different slots. - Each transmission opportunity in TB has one TCI and one RV. - All transmission opportunities (or multiple opportunities) across K slots use a common MCS with the same single or multiple DMRS ports (or multiple ports). - The RV / TCI status may be the same or different between transmission opportunities. - FFS: Channel estimation interpolation across slots with the same TCI index.

[0087] The M-TRP / panel-based URLLC method should be compared in terms of improved reliability, efficiency, and impact on specifications. Furthermore, support for the number of layers per TRP can be discussed.

[0088] According to the technical specification (TS) 38.214 ver. 16.1.0, the UE can be configured by a higher-layer parameter such as RepSchemeEnabler set to one of "FDMSchemeA", "FDMSchemeB", or "TDMSchemeA", where the UE is shown two TCI states in the code point. If two TCI states are shown in the DCI and the UE is set to "FDMSchemeA", the UE shall receive a single PDSCH transmit opportunity for the TB, with each TCI state associated with a non-overlapping frequency-domain resource allocation, as described in Clause 5.1.2.3. If two TCI states are shown in the DCI and the UE is set to "FDMSchemeB", the UE shall receive two PDSCH transmit opportunities for the same TB, with each TCI state associated with a PDSCH transmit opportunity having a non-overlapping frequency-domain resource allocation to the other PDSCH transmit opportunity, as described in Clause 5.1.2.3. If two TCI states are shown in the DCI and the UE is set to "TDMSchemeA", the UE will receive two PDSCH transmit opportunities of the same TB, each TCI state associated with a PDSCH transmit opportunity that has a non-overlapping time domain resource allocation to the other PDSCH transmit opportunity, as described in Clause 5.1.2.1, and both PDSCH transmit opportunities will be received within a given slot.

[0089] Regarding frequency domain resource allocation under FDMSchemeA and FDMSchemeB, if P'BWP.i is determined to be wideband, then the first

number

number

[0090] Embodiments 1-4 focus on multi-TB scheduling in DL PDSCH. A similar approach can be directly applied to multi-TB scheduling in UL PUSCH by replacing the corresponding k-th slot offset from K0k to K2k. If only one TRP (TCI state #1 or TCI state #2) is activated, the UE sends data transmissions to this activated TRP. If multiple TRPs are activated, UL data transmissions are based on the best-state TRP. Depending on network availability and UE capabilities, multiple embodiments can be applied together in networks of both non-RedCap (normal / legacy) UEs and RedCap UEs. It will be understood that in the embodiments and examples described herein, TRPs can be replaced with panels.

[0091] In embodiments 1 to 7, the proposed solutions and examples discuss scenarios with two TRPs, but it will be understood that these embodiments are directly applicable to scenarios with three or more TRPs. In such cases, three or more TCI states are used. This, advantageously, allows for gains from more TRPs during operation.

[0092] Instead of using a single DCI in embodiments 1-4, in the case of multiple DCI-based multi-TRP / panel transmissions, each of the multiple DCIs can schedule multiple TB DL radio resources for each of the multiple TRPs or panels. Either joint HARQ feedback or individual HARQ feedback can be used for the multiple TBs.

[0093] In embodiments 1 to 4, the proposed solutions and examples are applicable to transmissions of one or more layers and are also applicable and beneficial to scenarios with relatively long round trip times (RTT), such as non-terrestrial networks (NTNs) above 52.6 GHz. Furthermore, in embodiments 1 to 4, the radio resources of each portion can be quasi-statically represented based on the number of TCI states that are quasi-statically set, as indicated by one index of the TCI signaling.

[0094] Figure 19 shows flowchart 1900 illustrating communication methods according to various embodiments. In step 1902, a single DCI is received, which contains scheduling information, and the scheduling information indicates multiple TB radio resources. In step 1904, multiple TB radio resources are acquired based on the scheduling information.

[0095] Figure 20 shows a schematic, partially segmented diagram of a communications device 2000 that can be implemented to facilitate the implementation of multi-TB scheduling for single DCI-based multi-TRP / panel transmission in various embodiments. The communications device 2000 can be implemented as a base station, gNB, or a regular (non-RedCap or Release 15 / 16 / 17) UE, RedCap UE, or other similar type UE, according to various embodiments.

[0096] The various functions and operations of the communication device 2000 are arranged in layers according to a hierarchical model. In this model, lower layers report to and receive instructions from higher layers, in accordance with the 3GPP specification. For simplicity, the details of the hierarchical model are not discussed in this disclosure.

[0097] As shown in Figure 20, the communication device 2000 may include a circuit 2014, at least one radio transmitter 2002, at least one radio receiver 2004, and a plurality of antennas 2012 (for simplicity, only one antenna is shown in Figure 20 for illustrative purposes). The circuit 2014 may include at least one controller 2006 for use in software and hardware-assisted execution of a task designed to be performed, including controlling communication with one or more other communication devices in a MIMO radio network. The at least one controller 2006 may control at least one transmit signal generator 2008 for generating configuration information, HARQ feedback, ACK, NACK, IE, and / or RRC-Reconfig messages sent to one or more other communication devices via at least one radio transmitter 2002, and at least one receive signal processor 2010 for processing the above configuration information, HARQ feedback, ACK, NACK, IE, and / or RRC-Reconfig messages received from one or more other communication devices via at least one radio receiver 2004. At least one transmit signal generator 2008 and at least one receive signal processor 2010 may be standalone modules of the communication device 2000 communicating with at least one controller 2006 for the functions described above, as shown in Figure 20. Alternatively, at least one transmit signal generator 2008 and at least one receive signal processor 2010 may be included in at least one controller 2006. It will be understood by those skilled in the art that the arrangement of these functional modules is flexible and may change according to actual needs and / or requirements. Data processing, storage, and other related control devices may be provided on a suitable circuit board and / or in a chipset. In various embodiments, at least one radio transmitter 2002, at least one radio receiver 2004, and at least one antenna 2012 may be controlled by at least one controller 2006 during operation.

[0098] In the embodiment shown in Figure 20, at least one wireless receiver 2004, together with at least one received signal processor 2010, forms the receiver of the communication device 2000. The receiver of the communication device 2000 provides, in operation, the necessary functions to facilitate the implementation of multi-TB scheduling for single DCI-based multi-TRP / panel transmission.

[0099] The communication device 2000, in operation, provides the necessary functions to facilitate the implementation of multi-TB scheduling for single DCI-based multi-TRP / panel transmission. For example, the communication device 2000 may be a communication device, and the receiver 2004 may, in operation, receive a single DCI containing scheduling information, which indicates radio resources of multiple TBs. The circuit 2014 may, in operation, acquire radio resources of multiple TBs based on the scheduling information.

[0100] The scheduling information may indicate two or more Transmit Setting Indicator (TCI) states, each indicated TCI state corresponding to the activation of one Transmit / Receive Point (TRP) or panel, and the radio resources of multiple TBs are associated with the indicated TCI state. The scheduling information may indicate one TCI state corresponding to the activation of one TRP or panel, and the radio resources of multiple TBs are associated with the indicated TCI state. A first TB among multiple TBs associated with a first TRP may be associated with a first TCI state among the indicated TCI states, and a second TB among multiple TBs associated with a second TRP may be associated with a second TCI state among the indicated TCI states. Each of multiple TBs may be associated with at least one of the indicated TCI states.

[0101] Multiple TBs may be segmented into multiple parts, each of which includes one or more code blocks (CBs) or one or more code block groups (CBGs) from the multiple TBs, and scheduling information indicates at least one part and at least one radio resource from the indicated TCI states. One of the indicated TCI states may be associated with at least one part. Each of the multiple parts may be associated with at least one TRP or panel, and receiver 2004 may be further configured to receive at least one of the multiple parts from a TRP or panel in downlink transmission using the radio resource. Each of the multiple parts may be associated with at least one TRP or panel, and communication device 2000 may further include transmitter 2002 that, in operation, uses the radio resource to transmit at least one of the multiple parts to one or more TRPs or panels in uplink transmission. The size of each of the multiple parts may be set by other control information such as DCI, MAC CE, or RRC signaling. The size of each of the multiple parts may be determined by the quality of the communication link.

[0102] Scheduling information may indicate different spatial information for each of multiple parts, or for each of one or more TCI states. Scheduling information may set at least one TCI state by reference signal (RS) for deriving spatial information for at least one of the multiple parts associated with the set TCI state. Scheduling information may implicitly or explicitly set at least one TCI state by default spatial information for at least one of the multiple parts associated with the set TCI state. Each of the multiple parts may include one or more TBs from multiple TBs. Two or more TBs associated with different TRPs from multiple TBs may be associated with different parts. Two or more TBs associated with the same TRP from multiple TBs may be associated with one part. Scheduling information may be indicated by semi-persistent scheduling (SPS) for downlink (DL) transmissions or setting grants (CG) for uplink (UL) transmissions.

[0103] The scheduling information may further include a Time-Domain Resource Allocation (TDRA) table or a Frequency-Domain Resource Allocation (FDRA) table, and radio resources of multiple TBs are indicated by the TDRA table or FDRA table. The scheduling information may include a start and length indicator (SLIV) corresponding to at least one part and at least one of the indicated TCI states. The scheduling information may include a start symbol and allocation length corresponding to at least one part and at least one of the indicated TCI states. The scheduling information may include a slot offset corresponding to at least one part and at least one of the indicated TCI states. The scheduling information may include a start physical resource block (PRB) and the number of PRBs corresponding to at least one part and at least one of the indicated TCI states. The scheduling information may include an FDRA corresponding to at least one part and at least one of the indicated TCI states. The scheduling information may include a bitmap showing a PRB or resource block group (RBG) corresponding to at least one part and at least one of the indicated TCI states. Scheduling information may include one or a combination of partial indexes, redundant versions (RVs), mapping types, modulation order, coding rate, and interleave patterns. TDRA tables or FDRA tables may be configured by at least DCI, MAC CE, or RRC signaling. TDRA tables or FDRA tables may be specified in the specification.

[0104] The scheduling information may indicate at least one portion from multiple TBs for the initial transmission and at least one radio resource from the indicated TCI states, and may further indicate at least one repetition of at least one portion for repeated transmissions and at least one radio resource from the indicated TCI states. The association between the portion for the initial transmission and one of the indicated TCI states may be the same as or different from that for repeated transmissions. The scheduling information may further indicate at least one portion for the initial transmission and at least one radio resource from the serving cell (PCell, PSCell, or SCell), and may further indicate at least one repetition of at least one portion for repeated transmissions and at least one radio resource from the serving cell (PCell, PSCell, or SCell). The spatial information for one portion from multiple TBs for the initial transmission may be the same as or different from that for retransmissions. A single DCI may be scheduled to be transmitted from one of multiple TRPs or panels. Scheduling information may further indicate the initial transmission of multiple parts from multiple TBs for a single TRP set in a single DCI called the primary TRP, and repeated transmissions of parts from multiple TBs may be set for the remaining TRPs other than the primary TRP. Interleaving patterns may apply to the content of all parts and their repetitions, and interleaving patterns are implicitly indicated by pre-configured rules or explicitly indicated at least by DCI, MAC CE, or RRC signaling.

[0105] Circuit 2014 may be further configured to generate a response signal for each of the CBGs. If receiver 2004 correctly receives all CBs of the CBG, an acknowledgment (ACK) signal may be generated; if receiver 2004 incorrectly receives at least one CB of the CBG, a negative response (NACK) signal may be generated. Circuit 2014 may be further configured to generate a response signal for each of several parts. If receiver 2004 correctly receives all CBs of a part, an ACK signal may be generated; if receiver 2004 incorrectly receives at least one CB of a part, a NACK signal may be generated. The circuit may be further configured to generate a response signal for each of the indicated TCI states. If receiver 2004 correctly receives all CBs associated with a TCI state, an ACK signal may be generated; if receiver 2004 incorrectly receives at least one CB associated with a TCI state, a NACK signal may be generated. The scheduling information may indicate a PUCCH or PUSCH resource indicator (PRI) for a response signal, and the communication device 2000 may further include a transmitter 2002 that, in operation, transmits response signals for multiple TBs on the corresponding PUCCH or PUSCH based on the scheduling information. The scheduling information may indicate multiplexing the response signals for multiple TBs as a joint HARQ signal, and the transmitter 2002 may be further configured to transmit the joint HARQ signal to a TRP set in a single DCI. The transmitter may be further configured to transmit independent response signals for multiple TBs to their respective TRPs. The transmitter 2002 may be further configured to transmit the joint HARQ signal for multiple TBs to all TRPs. The scheduling information may further indicate independent HARQ-related information for each part or TCI state.

[0106] The communication device 2000 provides the necessary functions to facilitate the implementation of multi-TB scheduling for single DCI-based multi-TRP / panel transmission during operation. For example, the communication device 2000 may be a base station or gNB, and circuit 2014 may, during operation, generate a single DCI containing scheduling information, the scheduling information indicating radio resources of multiple TBs, and transmitter 2002 may, during operation, transmit the single DCI to the communication device.

[0107] As described above, embodiments of the present disclosure provide advanced communication methods and devices that enable the implementation of multi-TB scheduling for single DCI-based multi-TRP / panel transmission.

[0108] This disclosure can be implemented by software, by hardware, or by software working in conjunction with hardware. Each functional block used in the description of each embodiment above can be implemented in whole or in part by an LSI such as an integrated circuit, and each process described in each embodiment can be controlled in whole or in part by the same LSI or combination of LSIs. An LSI can be formed individually as a chip, or it can be formed as a single chip containing some or all of the functional blocks. An LSI can include data input / output units coupled to itself. Depending on the degree of integration, an LSI is also called an IC, a system LSI, a super LSI, or an ultra LSI. However, the technology for implementing an integrated circuit is not limited to LSIs and can be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, an FPGA (Field-Programmable Gate Array), which can be programmed after the manufacture of the LSI, or a reconfigurable processor, which can reconfigure the connections and settings of circuit cells located inside the LSI, can also be used. This disclosure can be implemented as a digital process or an analog process. If LSIs are replaced by future integrated circuit technologies as a result of advancements in semiconductor technology or other derivative technologies, functional blocks can be integrated using those future integrated circuit technologies. Biotechnology can also be applied.

[0109] This disclosure can be implemented by any type of device or system having communication capabilities (referred to as a communication device).

[0110] A communication device may comprise a transceiver and a processing / control circuit. The transceiver may comprise a receiver and a transmitter, and / or may function as both a receiver and a transmitter. A transceiver acting as both a transmitter and a receiver may include an RF (radio frequency) module, including an amplifier, an RF modulator / demodulator, etc., and one or more antennas.

[0111] Some non-exclusive examples of such communication devices include telephones (e.g., mobile phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, e-readers, telemedicine / telemedicine devices, vehicles providing communication capabilities (e.g., automobiles, airplanes, ships), and various combinations thereof.

[0112] Communication devices are not limited to portable or mobile devices, but may include any type of non-portable or fixed device, device, or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in the "Internet of Things (IoT)" network.

[0113] Communication may include steps such as exchanging data through cellular systems, wireless LAN systems, satellite systems, and others, and various combinations thereof.

[0114] A communication device may include devices such as controllers and sensors coupled to a communication device that performs the communication functions described in this disclosure. For example, a communication device may include a controller or sensor that generates control signals or data signals used by the communication device that performs the communication functions of the communication device.

[0115] Communication equipment may further include base stations, access points, and any other devices, devices, or systems that communicate with or control infrastructure equipment, such as the devices in the non-limiting examples above.

[0116] Those skilled in the art will understand that the disclosures shown in particular embodiments can be modified and / or changed in numerous ways without departing from the broadly described spirit or scope of the disclosure. Therefore, the embodiments described herein should be considered in all respects to be illustrative and not limiting to the invention. 1. A communication device comprising: a receiver that receives single downlink control information (DCI) including scheduling information during operation, wherein the scheduling information indicates the radio resources of a plurality of transport blocks (TBs); and a circuit that acquires the radio resources of a plurality of TBs based on the scheduling information during operation. 2. The communication device according to claim 1, wherein the scheduling information indicates two or more Transmit Setting Indicator (TCI) states, each indicated TCI state corresponds to the activation of one Transmit / Receive Point (TRP) or panel, and multiple TB radio resources are associated with the indicated TCI states. 3. The communication device according to claim 1, wherein the scheduling information indicates a single TCI state corresponding to the activation of a single TRP or panel, and the radio resources of multiple TBs are associated with the indicated TCI state. 4. The communication device according to claim 2, wherein the first TB among a plurality of TBs associated with the first TRP is associated with the first TCI state among the indicated TCI states, and the second TB among a plurality of TBs associated with the second TRP is associated with the second TCI state among the indicated TCI states. 5. The communication device according to claim 2, wherein each of the multiple TBs is associated with at least one of the indicated TCI states. 6. A communications device according to claim 2 or 5, wherein a plurality of TBs are segmented into a plurality of parts, each of which includes one or more code blocks (CBs) or one or more code block groups (CBGs) from the plurality of TBs, and the scheduling information indicates at least one part and at least one radio resource from the indicated TCI states. 7. The communication device according to claim 6, wherein one of the indicated TCI states is associated with at least one part. 8. The communication device according to claim 6, wherein each of the multiple parts is associated with at least one of a TRP or panel, and the receiver is further configured to receive at least one of the multiple parts from the TRP or panel in a downlink transmission using a radio resource. 9. The communication device according to claim 6, wherein each of the multiple parts is associated with at least one of a TRP or panel, and the communication device further comprises a transmitter that, in operation, uses radio resources to transmit at least one of the multiple parts to one or more TRPs or panels in an uplink transmission. 10. The communication device according to claim 6, wherein the size of each of the multiple parts is set by control information such as other DCI, MAC CE, or RRC signaling. 11. The communication device according to claim 6, wherein the size of each of the multiple parts is determined by the quality of the communication link. 12. The communication device according to claim 6, wherein the scheduling information indicates different spatial information for each of the multiple parts or for each of one or more TCI states. 13. The communication device according to claim 6, wherein scheduling information sets at least one TCI state by a reference signal (RS) for deriving spatial information for at least one of a plurality of parts associated with the set TCI state. 14. The communication device according to claim 6, wherein the scheduling information implicitly or explicitly sets at least one TCI state by default spatial information for at least one of a plurality of parts associated with the TCI state to be set. 15. The communication device according to claim 6, wherein each of the multiple parts comprises one or more TBs from a plurality of TBs. 16. The communication device according to claim 6, wherein two or more TBs associated with different TRPs among a plurality of TBs are associated with different parts. 17. The communication device according to claim 6 or 16, wherein two or more TBs related to the same TRP among a plurality of TBs are associated with one part. 18. The communication device according to any one of claims 1 to 6, wherein scheduling information is indicated by semi-persistent scheduling (SPS) for downlink (DL) transmission or setting grant (CG) for uplink (UL) transmission. 19. The communication device according to claim 6, wherein the scheduling information further comprises a time-domain resource allocation (TDRA) table or a frequency-domain resource allocation (FDRA) table, and radio resources of multiple TBs are indicated by the TDRA table or FDRA table. 20. The communication device according to claim 19, wherein the scheduling information includes a start and length indicator (SLIV) corresponding to at least one of the indicated TCI states. 21. The communication device according to claim 19, wherein the scheduling information includes a start symbol and an allocation length corresponding to at least one part and at least one of the indicated TCI states. 22. The communication device according to claim 19, wherein the scheduling information includes a slot offset corresponding to at least one portion and at least one of the indicated TCI states. 23. The communication device according to claim 19, wherein the scheduling information includes a starting physical resource block (PRB) and a number of PRBs corresponding to at least one part and at least one of the indicated TCI states. 24. The communication device according to claim 19, wherein the scheduling information includes an FDRA corresponding to at least one part and at least one of the indicated TCI states. 25. The communication device according to claim 19, wherein the scheduling information includes a bitmap showing a PRB or resource block group (RBG) corresponding to at least one portion and at least one of the indicated TCI states. 26. The communication device according to claim 19 or 22, wherein the scheduling information includes one or a combination of a partial index, a redundant version (RV), a mapping type, a modulation order, a coding rate, and an interleave pattern. 27. The communication device according to claim 19, wherein the TDRA table or FDRA table is set by at least DCI, MAC CE, or RRC signaling. 28. The communication device according to claim 19, wherein the TDRA table or FDRA table is specified in the specification. 29. The communication device according to any one of claims 6 to 27, wherein the scheduling information indicates at least one portion from a plurality of TBs for an initial transmission and at least one radio resource from the indicated TCI states, and further indicates at least one repetition of at least one portion for repeated transmissions and at least one radio resource from the indicated TCI states. 30. The communication device according to claim 29, wherein the association between the portion for the initial transmission and one of the indicated TCI states is the same as or different from that for repeated transmissions. 31. The communication device according to any one of claims 6 to 27, wherein the scheduling information further indicates at least one portion and at least one radio resource from among serving cells (PCell, PSCell, or SCell) for an initial transmission, and further indicates at least one repetition of at least one portion and at least one radio resource from among serving cells (PCell, PSCell, or SCell) for repeated transmissions. 32. The communication device according to claim 29, wherein the spatial information of one portion from a plurality of TBs for the initial transmission is the same as or different from that for the retransmission. 33. The communication device according to claim 1, wherein a single DCI is scheduled to be transmitted from one of a plurality of TRPs or panels. 34. The communication device according to claim 29 or 33, wherein the scheduling information further indicates the first transmission of multiple portions from multiple TBs for a single TRP set up in a single DCI called the primary TRP, and repeated transmissions of portions from multiple TBs are set up for the remaining TRPs other than the primary TRP. 35. The communication device according to claim 29, wherein the interleaving pattern is applied to the content of all parts and their repetitions, and the interleaving pattern is implicitly indicated by a pre-set rule or explicitly indicated by at least DCI, MAC CE, or RRC signaling. 36. The communication device according to any one of claims 6 to 8, wherein the circuit is further configured to generate a response signal for each of the CBGs. 37. The communication device according to claim 36, wherein if the receiver correctly receives all of the CBs of the CBG, an acknowledgment (ACK) signal is generated, and if the receiver incorrectly receives at least one of the CBs of the CBG, a negative acknowledgment (NACK) signal is generated. 38. The communication device according to any one of claims 6 to 8, wherein the circuit is further configured to generate response signals for each of the multiple parts. 39. The communication device according to claim 38, wherein an ACK signal is generated when the receiver correctly receives all of the CBs in a portion, and a NACK signal is generated when the receiver incorrectly receives at least one of the CBs in a portion. 40. The communication device according to any one of claims 1 to 8, wherein the circuit is further configured to generate a response signal for each of the indicated TCI states. 41. The communication device according to claim 40, wherein an ACK signal is generated when the receiver correctly receives all CBs related to the TCI state, and a NACK signal is generated when the receiver incorrectly receives at least one CB related to the TCI state. 42. The communication device according to any one of claims 36 to 41, wherein the scheduling information indicates a PUCCH or PUSCH resource indicator (PRI) for a response signal, and the communication device further comprises a transmitter that, in operation, transmits a plurality of TB response signals on the corresponding PUCCH or PUSCH based on the scheduling information. 43. The communication device according to claim 42, wherein the scheduling information indicates that the response signals of multiple TBs are multiplexed as a joint HARQ signal, and the transmitter is further configured to transmit the joint HARQ signal to a TRP set in a single DCI. 44. The communication device according to claim 42, wherein the transmitter is further configured to transmit independent response signals of a plurality of TBs to their respective TRPs. 45. The communication device according to claim 43, wherein the transmitter is further configured to transmit joint HARQ signals of multiple TBs to all TRPs. 46. ​​The communication device according to any one of claims 39 to 42, wherein the scheduling information further indicates independent HARQ-related information for each part or for each TCI state. 47. A base station comprising: a circuit that generates a single DCI including scheduling information during operation, wherein the scheduling information indicates radio resources of a plurality of transport blocks (TBs); and a transmitter that transmits the single DCI to a communication device during operation. 48. A communication method comprising receiving a single DCI containing scheduling information, wherein the scheduling information indicates radio resources of multiple TBs, and acquiring radio resources of multiple TBs based on the scheduling information. 49. A communication method comprising generating a single DCI containing scheduling information, wherein the scheduling information indicates radio resources of multiple transport blocks (TBs), and transmitting the single DCI to a communication device.

Claims

1. A communication device, A receiver that receives a single downlink control information (DCI), A circuit that acquires wireless resources from multiple physical downlink shared channels (PDSCHs) based on the single DCI, Equipped with, Each of the aforementioned PDSCHs includes one or more code blocks (CBs) or one or more code block groups (CBGs), The single DCI indicates two or more transmit configuration indicator (TCI) states. Communication device.

2. Of the plurality of PDSCHs, the first PDSCH is associated with a first start and length indicator value (SLIV) and a first transmit setting indicator (TCI) state, and the second PDSCH is associated with a second SLIV and a second TCI state. The communication device according to claim 1.

3. The size of each of the aforementioned PDSCHs is set by control information or RRC signaling. The communication device according to claim 1.

4. Different spatial information is indicated for each of one or more TCI states. The communication device according to claim 1.

5. The single DCI indicates a TCI state accompanied by at least a reference signal (RS) for deriving spatial information. The communication device according to claim 1.

6. Each of the aforementioned PDSCHs corresponds to one or more transport blocks (TBs), The communication device according to claim 1.

7. The aforementioned multiple PDSCHs are related to transmission using different TRPs, The communication device according to claim 1.

8. The aforementioned multiple PDSCHs are related to transmission using the same TRP, The communication device according to claim 1.

9. The DCI includes a Time-Domain Resource Allocation (TDRA) field, and the radio resources of the plurality of PDSCHs are indicated by the TDRA field. The communication device according to claim 1.

10. The single DCI includes a start-and-length indicator (SLIV) corresponding to each of the plurality of PDSCHs, The communication device according to claim 1.

11. The single DCI includes a slot offset corresponding to each of the plurality of PDSCHs, The communication device according to claim 1.

12. The TDRA table is configured by at least DCI, MAC CE, or RRC signaling, or as specified in the specification. The communication device according to claim 1.

13. The single DCI is scheduled to be transmitted from one of several TRPs or panels. The communication device according to claim 1.

14. The interleaving pattern is applied to all of the plurality of PDSCHs, and the interleaving pattern is implicitly indicated by at least one of DCI, MAC CE, or RRC signaling. The communication device according to claim 1.

15. The circuit is configured to generate a response signal to the CBG. The communication device according to claim 1.

16. When the receiver receives the CBG, an acknowledgment (ACK) signal is generated, and when the receiver does not receive the CBG, a negation (NACK) signal is generated. The communication device according to claim 1.

17. The DCI indicates the PUCCH resource indicator (PRI) for the response signal. The communication device according to claim 1.

18. The transmitter is configured to transmit the joint HARQ signal of multiple TBs in the multiple PDSCHs. The communication device according to claim 1.

19. It is a base station, A circuit that generates a single DCI including scheduling information, A transmitter that transmits the single DCI to a communication device, Equipped with, The scheduling information indicates the wireless resources of multiple physical downlink shared channels (PDSCHs), Each of the aforementioned PDSCHs includes one or more code blocks (CBs) or one or more code block groups (CBGs), The single DCI indicates two or more transmit configuration indicator (TCI) states. Base station.

20. A method of communication, Receiving a single DCI containing scheduling information, The scheduling information indicates the wireless resources of multiple PDSCHs, Based on the scheduling information, acquire the wireless resources for the multiple PDSCHs, Includes, Each of the aforementioned PDSCHs includes one or more code blocks (CBs) or one or more code block groups (CBGs), The single DCI indicates two or more transmit configuration indicator (TCI) states. Communication method.

21. A method of communication, To generate a single DCI containing scheduling information, The scheduling information indicates the wireless resources of multiple physical downlink shared channels (PDSCHs), Transmitting the aforementioned single DCI to a communication device, Includes, Each of the aforementioned PDSCHs includes one or more code blocks (CBs) or one or more code block groups (CBGs), The single DCI indicates two or more transmit configuration indicator (TCI) states. Communication method.

22. It is an integrated circuit, Control the processing of the communication device, The aforementioned process is, A process to receive a single DCI containing scheduling information, The scheduling information indicates the wireless resources of multiple PDSCHs, A process for acquiring the wireless resources for the multiple PDSCHs based on the scheduling information, Includes, Each of the aforementioned PDSCHs includes one or more code blocks (CBs) or one or more code block groups (CBGs), The single DCI indicates two or more transmit configuration indicator (TCI) states. Integrated circuit.

23. It is an integrated circuit, Control the processing at the base station, The aforementioned process is, A process to generate a single DCI including scheduling information, The scheduling information indicates the wireless resources of multiple physical downlink shared channels (PDSCHs), The process of transmitting the single DCI to the communication device, Includes, Each of the aforementioned PDSCHs includes one or more code blocks (CBs) or one or more code block groups (CBGs), The single DCI indicates two or more transmit configuration indicator (TCI) states. Integrated circuit.

Images