User equipment and scheduling node

Abstract

To provide user equipment (UE) and a scheduling node and a corresponding method.SOLUTION: A method includes carrying a TCI indicator specifying that two or more Transmission Configuration Indication (TCI) states are configured and an indication indicating time domain resources for transmission and an association of the two or more TCI states with the time domain resources by downlink control information (DCI) signaling, each time domain resource is associated with one of the two or more TCI states, and during an operation, the transceiver receives or transmits, for each of the two or more TCI states, data on the time domain resource associated with the respective TCI states.EFFECT: Efficient utilization of resources, including efficient signaling of time domain resources for multiple TCI states is facilitated.SELECTED DRAWING: Figure 10

Description

Technical Field

[0001] The present disclosure relates to the transmission and reception of signals in a communication system. In particular, the present disclosure relates to methods and apparatuses for such transmission and reception.

Background Art

[0002] 3GPP (3rd Generation Partnership Project) is working on technical specifications for next-generation cellular technologies, also known as the 5th generation, including NR (New Radio) radio access technology (RAT) operating in the frequency range up to 100 GHz. NR is a successor to the technologies represented by LTE (Long Term Evolution) and LTE-A (LTE-Advanced).

[0003] For systems such as LTE, LTE-A, and NR, further improvements and options may facilitate the efficient operation of not only specific devices related to the system but also the communication system.

Summary of the Invention

[0004] One non-limiting and exemplary embodiment facilitates the efficient utilization of resources, including efficient signaling of time-domain resources for multiple transmission / reception points (TRPs), i.e., multiple Transmission Configuration Indication (TCI) states.

[0005] In embodiments, the technology disclosed herein features a user device (UE) comprising: a transceiver that receives downlink control information (DCI) signaling during operation; a processor that, during operation, obtains from the DCI signaling a TCI indicator that specifies that two or more TCI (Transmission Configuration Indication) states are set; a time-domain resource for transmission and an instruction indicating the association between the two or more TCI states and the time-domain resource, each of which time-domain resources is associated with one of the two or more TCI states, wherein the transceiver receives or transmits data on the time-domain resource associated with each of the two or more TCI states during operation.

[0006] It should be noted that the whole or specific embodiments may be implemented as a system, method, integrated circuit, computer program, storage medium, or a selective combination thereof.

[0007] Further benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. Benefits and / or advantages may also be obtained individually by the various embodiments and features of the specification and drawings, and these do not all need to be provided in order to obtain one or more such benefits and / or advantages. [Brief explanation of the drawing]

[0008] In the following, exemplary embodiments will be described in more detail with reference to the attached drawings. [Figure 1] This is a schematic diagram illustrating an exemplary architecture of a 3GPP NR system. [Figure 2] This block diagram shows exemplary user and control plane architectures for LTE eNB, gNB, and UE. [Figure 3] This is a schematic diagram showing the functional division between NG-RAN and 5GC. [Figure 4]This is a sequence diagram for the RRC connection setup / reconfiguration procedure. [Figure 5] This is a schematic diagram illustrating usage scenarios for eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communications), and URLLC (Ultra Reliable and Low Latency Communications). [Figure 6] This is a block diagram illustrating an example of a 5G system architecture. [Figure 7] This is a block diagram showing user equipment (UE) and scheduling nodes (base stations) communicating on a channel. [Figure 8] This is a block diagram showing the processing circuit portion of the user equipment (UE). [Figure 9] This is a block section for the processing circuitry of a base station. [Figure 10] This is a block diagram showing how it is executed in UE. [Figure 11] This is a schematic diagram illustrating the first specific example of multiple TRP time-domain resources. [Figure 12] This is a schematic diagram illustrating a second specific example of time-domain resources for multiple TRPs. [Figure 13] This is a schematic diagram illustrating a third specific example of time-domain resources for multiple TRPs. [Figure 14] This is a schematic diagram showing a fourth specific example of multiple TRP time-domain resources. [Figure 15] This is a schematic diagram showing a fifth specific example of multiple TRP time-domain resources. [Figure 16] This is a schematic diagram showing a sixth specific example of multiple TRP time-domain resources. [Figure 17] This is a schematic diagram showing a seventh specific example of multiple TRP time-domain resources. [Figure 18] This is a flowchart showing how the process is implemented at the UE and base station. [Modes for carrying out the invention]

[0009] 5G NR system architecture and protocol stack 3GPP has been working on the next release of fifth-generation cellular technology, simply called 5G, which includes the development of NR (New Radio Access Technology) that operates at frequencies up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, enabling the trial and practical application of smartphones compliant with the 5G NR standard.

[0010] In particular, the overall system architecture envisions an NG-RAN (Next Generation-Radio Access Network) including gNBs, providing NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol terminations to the UE. The gNBs are interconnected with each other via Xn interfaces. The gNBs are also connected to the NGC (Next Generation Core) via NG (Next Generation) interfaces, more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that performs the AMF) via NG-C interfaces, and to the UPF (User Plane Function) (e.g., a specific core entity that performs the UPF) via NG-U interfaces. The NG-RAN architecture is shown in Figure 1 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0011] A variety of different deployment scenarios are supported (see, for example, 3GPP TR 38.801 v14.0.0). For example, a decentralized deployment scenario (see, for example, section 5.2 of TR 38.801; a decentralized deployment is shown in section 5.4) is presented there, where base stations supporting 5G NR can be deployed. Figure 2 shows an exemplary decentralized deployment scenario (see, for example, Figure 5.2-1 of TR 38.801), while further showing user equipment (UE) connected to both the LTE eNB and gNB. A new eNB for NR 5G may, exemplary, be called a gNB. The eLTE eNB is an evolution of the eNB that supports connectivity with the EPC (Evolved Packet Core) and NGC (Next Generation Core).

[0012] The user plane protocol stack for NR (see, for example, 3GPP TS 38.300, section 4.4.1) includes the PDCP (Packet Data Convergence Protocol, see section 6.4 of TS 38.300), RLC (Radio Link Control, see section 6.3 of TS 38.300), and MAC (Medium Access Control, see section 6.2 of TS 38.300) sublayers, which are terminated at the gNB on the network side. Further, a new AS (Access Stratum) sublayer (SDAP, Service Data Adaptation Protocol) is introduced above the PDCP (see, for example, sub-clause 6.5 of 3GPP TS 38.300). A control plane protocol stack is also defined for NR (see, for example, TS 38.300, section 4.4.2). An overview of the layer 2 functions is given in sub-clause 6 of TS 38.300. The functions of the PDCP, RLC, and MAC sublayers are listed in sections 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in sub-clause 7 of TS 38.300.

[0013] For example, the MAC layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling of different numerologies.

[0014] The physical layer (PHY) is responsible for, for example, encoding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. It also processes the mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. The physical channel corresponds to a set of time-frequency resources used for the transmission of a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, one physical channel is the PRACH (Physical Random Access Channel) used for random access.

[0015] Use cases / deployment scenarios for NR may include eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliable Low-Latency Communications), mMTC (massive Machine Type Communication) with diverse requirements regarding data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and user experience data rates on the order of three times that provided by IMT-Advanced. On the other hand, in the case of URLLC, more stringent requirements are imposed for ultra-low latency (0.5 ms for UL and DL respectively for user plane latency) and high reliability (1 to 10 -5 ) within 1 ms. Finally, mMTC may preferably require a high connection density (1,000,000 devices / km in an urban environment 2 ), large coverage in harsh environments, and extremely long-life batteries (15 years) for low-cost devices.

[0016] Therefore, OFDM neurology suitable for one use case (e.g., subcarrier interval, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval, etc.) may not work well for another use case. For example, low-latency services may preferably require shorter symbol durations (and larger subcarrier intervals) and / or fewer symbols per scheduling interval (aka TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require longer CP durations than scenarios with shorter delay spreads. The subcarrier interval should be optimized accordingly to maintain similar CP overhead. NR may support multiple values ​​for the subcarrier interval. In response to this, subcarrier intervals of 15kHz, 30kHz, 60kHz, etc. are currently being considered. The symbol duration Tu and subcarrier interval Δf are directly related through the equation Δf = 1 / Tu. Similar to LTE systems, the term “resource element” can be used to refer to the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0017] In each new 5G-NR radio system for neurology and carriers, a resource grid of subcarriers and OFDM symbols is defined for both the uplink and downlink. Each element in the resource grid is called a resource element and is identified based on its frequency index in the frequency domain and its symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0018] 5G NR function splitting between NG-RAN and 5GC

[0019] Figure 3 shows the functional partitioning between NG-RAN and 5GC. NG-RAN logical nodes are gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.

[0020] In particular, gNB and ng-eNB provide the following main functions: - Wireless resource management functions such as wireless bearer control, wireless admission control, connectivity mobility control, and dynamic resource allocation (scheduling) to UEs in both uplink and downlink. - Data IP header compression, encryption, and integrity protection -Selection of AMF in UE attachment when 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 - Connection setup and release - Scheduling and sending paging messages - Scheduling and transmission of system broadcast information (originating from AMF or OAM) - Measurement and measurement report settings for mobility and scheduling - Transport-level packet marking in uplink - Session management - Network slicing support - QoS flow management and mapping to data wireless bearers - Support for UEs in RRC_INACTIVE state - NAS message delivery function - Wireless access network sharing - Dual connectivity - Close cooperation between NR and E-UTRA

[0021] AMF (Access and Mobility Management Function) provides the following key functions: - NAS (Non-Access Stratum) signaling termination - NAS signaling security -AS (Access Stratum) Security Control - Core Network (CN) inter-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) - Network slicing support -SMF (Session Management Function) selection Furthermore, UPF (User Plane Function) provides the following key features: - Anchor points for mobility within / between RATs (when applicable) - External PDU session points for interconnection with data networks - 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 - User plane QoS handling such as packet filtering, gating, and UL / DL rate enforcement. - Uplink traffic verification (mapping from SDF to QoS flow) - Downlink packet buffering and downlink data notification triggering Finally, the Session Management Function (SMF) provides the following key features: - Session management -UE IP address allocation and management - Selection and control of UP function - Configuring traffic steering in UPF (User Plane Function) to route traffic to the correct destination. -Policy enforcement and QoS control section - Downlink data notification

[0022] RRC Connection Setup and Reconfiguration Procedure

[0023] Figure 4 shows some interactions between the UE, gNB, and AMF (5GC entities) in the context of the UE transition from RRC_IDLE to RRC_CONNECTED for the NAS part (see TS 38.300 v15.6.0).

[0024] RRC is a higher-layer signaling protocol used for configuring UEs and gNBs. Specifically, this transition involves the AMF preparing UE context data (including, for example, PDU session context, security key, UE radio capability, UE security capability, etc.) and sending it to the gNB via an 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. Subsequently, the gNB performs a reconfiguration to set up the signaling radio bearer 2 (SRB2) and data radio bearer (DRB) by sending an RRCReconfiguration message to the UE, and the gNB receiving an RRCReconfigurationComplete from the UE in response. For signaling-only connections, the steps related to RRCReconfiguration are omitted because SRB2 and DRB are not configured. Finally, the gNB notifies the AMF that the configuration procedure is complete via the INITIAL CONTEXT SETUP RESPONSE.

[0025] Accordingly, this disclosure provides a fifth-generation core (5GC) entity (e.g., AMF, SMF, etc.) which includes a control circuit that establishes a Next Generation (NG) connection with a gNodeB (or gNB) during operation, and a transmitter that sends an initial context setup message to the gNodeB via the NG connection that causes a signaling radio bearer configuration between the gNodeB and the user equipment (UE) during operation. In particular, the gNodeB transmits a Radio Resource Control (RRC) signal to the UE via the signaling radio bearer, which includes resource allocation configuration information elements. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0026] IMT usage scenarios from 2020 onwards

[0027] Figure 5 shows some use cases for 5G NR. 3GPP NR (3rd Generation Partnership Project New Radio) is considering three use cases where IMT-2020 is expected to support a wide range of services and applications. Phase 1 specifications for eMBB have been finalized. In addition to further expanding eMBB support, current and future work will involve the standardization of URLLC and mMTC. Figure 5 shows some specific examples of envisioned ideal scenarios for IMT beyond 2020.

[0028] URLLC use cases have stringent requirements for capabilities such as throughput, latency, and availability, and are envisioned as one means of enabling 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 by TR 38.913. For NR URLLC in Release 15, the key requirements include target user plane delays of 0.5 ms for UL (uplink) and 0.5 ms for DL ​​(downlink). The overall URLLC requirement for a single packet transmission is a Block Error Rate (BLER) of 1E-5 for a 32-byte packet size with a user plane delay of 1 ms.

[0029] From a RAN1 perspective, reliability can be improved in several possible ways. Current scope for improving reliability concerns specifying separate CQI tables for URLLC, a more compact DCI format, and PDCCH repetition. However, this scope may expand to achieve ultra-reliability as NR becomes more stable and developed (for key requirements of NR URLLC). Specific use cases for NR URLLC in Rel. 15 include AR / VR (Augmented Reality / Virtual Reality), e-health, e-safety, and mission-critical applications.

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

[0031] The use case for mMTC is characterized by a very large number of connected devices transmitting relatively small amounts of data, typically with minimal latency impact. The devices need to be low-cost and have extremely long battery life. From a noise reduction (NR) perspective, utilizing a very narrow bandwidth segment is one possible solution to achieve power savings and long battery life from a UE perspective.

[0032] As mentioned above, a broader range of reliability is expected in NR. One key requirement for all cases, particularly URLLC and mMTC, is high reliability or very high reliability. Several mechanisms can be considered to improve reliability from both a radio and network perspective. In general, there are several key areas that can help improve reliability. These areas include compact control channel information, data channel / control channel repetition, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability regardless of the specific communication scenario.

[0033] For NR URLLC, further use cases with more stringent requirements have been identified, including factory automation, the transportation industry, and power distribution, including power distribution. These stringent requirements necessitate higher reliability (10 -6 This includes higher availability (up to level 1), packet size up to 256 bytes, and time synchronization down to the order of a few microseconds, with values ​​on the order of 0.5 to 1 ms, depending on the frequency range and short delay, and especially depending on the use case, with a target user plane delay of 0.5 ms, it can be on the order of 1 or a few microseconds.

[0034] Furthermore, several technical enhancements to NR URLLC from a RAN1 perspective have been identified. These include PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repeat, and increased PDCCH monitoring. UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. Additionally, PUSCH enhancements related to minislot level hopping and retransmission / repeat enhancements are identified. The term "minislot" refers to a transmit time interval (TTI) containing fewer symbols than a slot (a slot consisting of 14 or 12 symbols).

[0035] In slot-based scheduling or allocation, a slot corresponds to the timing granularity (TTI: Transmit Time Interval) for scheduling and allocation. Generally, the TTI determines the timing granularity for scheduling and allocation. A single TTI is the time interval at which a given signal is mapped to the physical layer. For example, conventionally, the TTI length is variable from 14 symbols (slot-based scheduling) to 2 symbols (non-slot-based scheduling). Downlink (DL) and uplink (UL) transmissions are specified to be organized into frames (10 ms duration) consisting of 10 subframes (1 ms duration). In slot-based transmission, subframes are further divided into slots, and the number of slots is defined by the neurology / subcarrier interval. The specified range of values ​​is between 10 slots per frame (1 slot per subframe) for a 15 kHz subcarrier interval and 80 slots per frame (8 slots per subframe) for a 120 kHz subcarrier interval. The number of OFDM symbols per slot is 14 for normal cyclic prefixes and 12 for extended cyclic prefixes (see sections 4.1 (general frame structure), 4.2 (Numerologies), 4.3.1 (frames and subframes), and 4.3.2 (slots) of 3GPP TS 38.211 V15.3.0, Physical channels and modulation, 2018-09). However, the allocation of time resources for transmission may also be non-slot-based. In particular, TTI in non-slot-based allocation may correspond to minislots rather than slots; that is, one or more minislots may be allocated to the requested transmission of data / control signaling. In non-slot-based allocation, the shortest length of TTI may be, for example, 1 or 2 OFDM symbols.

[0036] [QoS control] The 5G QoS (Quality of Service) model 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), based on 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) carried in the encapsulation header via the NG-U interface.

[0037] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one data radio bearer (DRB) with the PDU session, and additional DRBs for the QoS flow of that PDU session may be configured thereafter, for example, as described above with reference to Figure 4 (when and how they are configured is at the discretion of the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate 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.

[0038] Figure 6 shows the 5G NR non-roaming standard architecture (see TS 23.501 v16.1.1, section 4.23). Application functions (AFs), such as the external application server providing 5G services as illustrated in Figure 5, interact with the 3GPP core network to provide services, for example, to support the application's influence on interaction with policy controls such as traffic routing, access to the Network Exposure Function (NEF), or QoS control (see Policy Control Function (PCF)). Based on the operator's deployment, application functions considered trusted by the operator may be allowed to directly interact with the relevant network functions. Application functions not authorized by the operator to directly access network functions interact with the relevant network functions via the NEF using an external exposure framework.

[0039] Figure 6 further shows the functional units of the 5G architecture, namely NSSF (Network Slice Selection Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), AMF (Access and Mobility Management Function), SMF (Session Management Function), and DN (Data Network) such as carrier services, internet access, or third-party services.

[0040] A terminal, user terminal, or user device is referred to as a user device (UE) in LTE and NR. This may be a mobile device or communication device such as a wireless telephone, smartphone, tablet computer, or USB (Universal Serial Bus) stick with the functionality of a user device. However, the term mobile device is not limited thereto, and generally a relay may also have the functionality of such a mobile device, and a mobile device may function as a relay.

[0041] A base station is, for example, a network node that forms part of a network to provide services to a terminal. A base station is a network node or scheduling node that provides radio connectivity to a terminal. Communication between a terminal and a base station is typically standardized. In LTE and NR, the radio interface protocol stack includes the physical layer, the MAC (Medium Access Control) layer, and the upper layers. In the control plane, the upper layer protocol RRC (Radio Resource Control) protocol is provided. Through RRC, the base station can control the configuration of a terminal, and the terminal may communicate with the base station to perform control tasks such as connection and bearer establishment, correction, measurement, and other functions. The term used in LTE is eNB (or eNodeB), while the term currently used for 5G NR is gNB.

[0042] A service for transferring data provided by one layer to a higher layer is typically called a channel. For example, LTE and NR distinguish between logical channels provided by the MAC layer to higher layers, transport channels provided by the physical layer to the MAC layer, and physical channels that define mappings on physical resources.

[0043] Logical channels are various data transfer services provided by MACs. Each logical channel type is defined by the type of data being transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for transferring only control plane information. Traffic channels are used for transferring only user plane information.

[0044] Logical channels are mapped to transport channels by the MAC layer. For example, logical traffic channels and some logical control channels may be mapped to a transport channel referred to as the downlink shared channel DL-SCH in the downlink and to a transport channel referred to as the uplink shared channel UL-SCH in the uplink.

[0045] Downlink control channel monitoring, PDCCH, DCI Many of the functions operated by the UE include monitoring downlink control channels (e.g., PDCCH; see 3GPP TS 38.300 v15.6.0, section 5.2.3) to receive specific control information or data addressed to the UE.

[0046] As described above, PDCCH monitoring is performed by the UE to identify and receive information destined for the UE, such as user traffic (e.g., DCI on the PDCCH and user data on the PDSCH notified by the PDCCH), along with control information.

[0047] Downlink control information (which can be called Downlink Control Information DCI) serves the same purpose in 5G NR as DCI in LTE, namely, a special set of control information that schedules, for example, downlink data channels (e.g., PDSCH) or uplink data channels (e.g., PUSCH). In 5G NR, there are already several different DCI formats defined (see TS 38.212 v15.6.0 section 7.3.1).

[0048] Each of these PDCCH monitoring functions serves a specific purpose and is therefore initiated until the end. PDCCH monitoring is typically controlled based at least on a timer operated by the UE. The timer serves the purpose of controlling PDCCH monitoring, for example, by limiting the maximum time the UE monitors the PDCCH. For example, the UE does not need to monitor the PDCCH indefinitely and may stop monitoring after a certain period of time to conserve power.

[0049] As described above, one of the purposes of DCI on PDCCH is the dynamic scheduling of resources in downlink, uplink, or sidelink. In particular, several formats of DCI are provided to carry notifications of resources to be allocated to data channels for a particular user (resource allocation RA). Resource allocation may include the specification of resources in the frequency domain and / or time domain.

[0050] Resource allocation In the time domain, scheduling timing (for example, for scheduling the resources mentioned above) may be communicated within the DCI by using a Time Domain Resource Allocation (TDRA) table, as specified in Release 15 (NR), for example. In particular, a UE may be communicated in the DCI by communicating one entry (row) in the TDRA table, for example by communicating the entry (row) index. Since TDRA entries are summarized as a table in the standard specification for NR, the term "table" is used here as a logical term.

[0051] Repetition on PDSCH and PUSCH A transmission in NR may include spontaneous repetitions of data (i.e., without being triggered by (H)ARQ). In such cases, the same data (e.g., a transport block) is transmitted N times, where N is an integer greater than 1. The number of repetitions may be configurable.

[0052] Multiple transmit / receive point TRP The physical layer in NR may provide multi-antenna operation, such as MIMO (Multiple Input Multiple Output), which may include the use of multiple transmit / receive points (multi-TRPs). For example, a user device may receive data from multiple TRPs (transmit / receive points), and the multiple TRPs may be controlled by the same or different network nodes. The terms multipoint transmission or coordinated multipoint transmission (CoMP) may also be used for multi-TRP communication or transmission.

[0053] The technologies described herein are not limited to a specific arrangement of TRPs or a specific relationship between TRPs and gNBs. For example, multi-TRP operation may be performed by a gNB having different antenna panels or radio heads corresponding to the TRPs and different radio frequency units operating with each antenna.

[0054] Furthermore, in a multi-TRP configuration, several options are possible regarding the positional relationship between TRPs, and the distance between two TRPs can vary. For example, TRPs may be close together so that UEs receive signals from them at similar angles. However, TRPs may also be placed at considerably greater distances from each other, for example, at remote locations within a network cell. UEs serviced by two TRPs may send and receive signaling to and from each TRP over uncorrelated channels. Thus, the gain of channel diversity can be optimally utilized.

[0055] For example, a multi-TRP may be classified into two higher-level categories. That is, the distinction between categories may be made with respect to the backhaul type of the backhaul link between two given TRPs.

[0056] On the other hand, an ideal backhaul would be one with very high throughput and very low latency, such as a dedicated point-to-point connection using optical fiber. An ideal backhaul is assumed to enable communication between TRPs with approximately or nearly 0 milliseconds of latency (for example, for LTE-A, technical report 3GPP TR 36.932 V15.0.0 (2018-06) mentions a unidirectional latency of less than 2.5 μs in section 6.1.3, but does not include propagation latency in fiber / cable).

[0057] On the other hand, non-ideal backhauls are other backhauls such as DSL, microwave, and relay, which may include a finite (unidirectional) delay of 2ms or 5ms for communication between two given TRPs.

[0058] Apart from the classification into ideal and non-ideal backhaul, a further classification in multi-TRP MIMO technology may be made in terms of how the (central) baseband unit is shared among the TRPs.

[0059] For example, given two TRPs, each may have a different RF (Radio Frequency) unit, while the TRPs share the same baseband unit. In this case, the links between the RF unit and the baseband unit may be ideal or non-ideal. Alternatively, each TRP may have both a different (central) baseband unit and a different RF unit. In this case, not only the links between the baseband unit and the RF unit, but also the links between the different baseband units may be ideal or non-ideal.

[0060] This invention relates to time-domain resource allocation for transmissions from multiple TRPs (particularly PDSCH repetitions). Generally, PDSCH repetitions from multiple TRPs may be scheduled using single DCI-based scheduling from one of the TRPs.

[0061] An example of such a PDSCH iteration is shown in Figure 11. As can be seen from the figure, a single DCI (PDCCH) from TRP1 schedules five PDSCH iterations. More specifically, three PDSCH iterations are scheduled from TRP1 (i.e., the first, second, and fourth iterations), and two are scheduled from TRP2 (i.e., the third and fifth iterations). Both inter-slot and intra-slot iterations are supported, and an ideal backhaul between multiple TRPs is considered.

[0062] Note that each TRP can be associated with a separate TCI state, and that TCI states and TRPs are interchangeable. In particular, below, TCI state 1 may be referred to as TRP1, TCI state 2 as TRP2, and so on.

[0063] However, when multiple TRPs are scheduled, there are several issues in scheduling and associating repetitions. More specifically, scheduling repetitions of PDSCHs from multiple TRPs by a single DCI from one of the TRPs presents the following unresolved issues for time-domain resource allocation:

[0064] Firstly, the UE needs to be notified which repetition is associated with which TRP. For example, the UE in Figure 12 needs to know that TRP1 sends the first, second, and fourth repetitions, while TRP2 sends the third and fifth repetitions.

[0065] Secondly, the time-domain resources for each iteration need to be communicated to the UE. For example, the UE in Figure 12 needs to know the start symbol, slot, and length of each of the five iterations.

[0066] Thirdly, the number of transmissions to be scheduled from each TRP and the combined total number of transmissions from all TRPs must be communicated to the UE. For example, the UE in Figure 12 must know that the total number of scheduled transmissions is 5, where 3 are from TRP1 and 2 are from TRP2.

[0067] In general, semi-static or dynamic notification to the UE is possible regarding repeated associations to one of the TRPs. For semi-static associations, the pattern regarding which repetition is associated with which TRP may be fixed. However, such an approach does not provide sufficient flexibility to apply associations depending on the availability of TRPs and / or corresponding time-domain resources.

[0068] Dynamic associations may be notified by DCI. However, if explicit instructions in the form of a bitmap are used, the size of the bitmap may increase in proportion to the increase in the number of repetitions and / or TRPs.

[0069] An exemplary UE according to one embodiment is shown in Figure 7. According to this embodiment, a user device (UE) 760 is provided which includes a transceiver 770. The transceiver 770 receives downlink control signaling (DCI) during operation. The UE may further include a processor (or processing circuit) 780 which obtains a Transmission Configuration Indication (TCI) indicator that specifies that two or more TCI states are set from the DCI signaling during operation. Furthermore, the processor 780 may obtain a notification indicating a time-domain resource for transmitting and associating a time-domain resource which has two or more TCI states during operation. Effectively, each time-domain resource is associated with one of the two or more TCI states. The transceiver may further receive or transmit data on the time-domain resource associated with each of the two or more TCI states during operation.

[0070] Circuit 780 may implement more functionality than the time-domain resource determination described above for transmission / reception using multiple TRPs. Therefore, circuit 780 may include a time-domain resource determination circuit 785 configured to perform time-domain resource determination. This configuration may be provided by hardware adaptation and / or software.

[0071] Figure 8 shows the functional configuration of the time-domain resource determination circuit 785. In particular, the time-domain resource determination circuit 785 includes a PDCCH processing circuit 870 that acquires the TCI indicator from the DCI and the association between each TCI state and a time-domain resource, along with a notification indicating a time-domain resource for transmission. The time-domain resource determination circuit 785 further includes a resource determination circuit 880 that determines the allocation of a time-domain resource for each TCI state when the TCI indicator shows two or more TCI states based on the time-domain resource notification. The processing circuit 780 may then control the transceiver 770 to receive or transmit data on the determined resource.

[0072] In another embodiment, a base station 710 (scheduling node) is provided, comprising a processor 730. The processor 730 generates downlink control information (DCI) signaling that notifies a TCI (Transmission Configuration Indication) indicator specifying that two or more TCI states are set during operation. The TCI signaling further notifies the association of two or more TCI states with time-domain resources and time-domain resources for transmission, each time-domain resource being associated with one of the two or more TCI states. The base station further comprises a transceiver 720 that transmits the DCI signaling during operation. The transceiver receives or transmits data on the time-domain resources associated with each of the two or more TCI states during operation (e.g., to the UE 760). Similar to the processor 780 of the UE, the processor 730 may also perform a variety of different tasks. Here, a time-domain resource allocation circuit 735 represents a functional part of the processor 730, which performs the time-domain allocation tasks described above, including determining resources and providing the corresponding signaling to the UE 760.

[0073] The scheduling device may further include, as part of circuit 730, an allocation circuit that performs scheduling for one or more UEs. As a result of scheduling, a time-domain resource allocation is generated, and along with the TCI indicator and resource allocation, corresponding DCI signaling is generated that shows the association between TCI states and resources. The circuit then controls the transceiver 720 to transmit or receive data on the resources scheduled for one or more UEs.

[0074] An exemplary functional configuration of the time-domain resource allocation circuit 735 is shown in Figure 9. In particular, the time-domain resource allocation circuit 735 may include a scheduling circuit 936 and a PDCCH generation circuit 937. The scheduling circuit 920 performs scheduling, for example, by collecting measurement results from one or more UEs and, based on thereon, assigns resources to each UE in the time domain (and possibly the frequency domain and TRP) based on requests from the UEs and / or the availability of their resources. The PDCCH generation circuit 930 then generates a DCI that includes associations between TCI states and time-domain resources, along with TCI indicators and resource allocations, according to the scheduling results for each of the one or more UEs.

[0075] As can be seen from Figure 7, the UE760 and the scheduling node 710 can form a communication system, that is, they can communicate via channel 750.

[0076] Generally, DCI signaling may be a single bit field of a DCI (e.g., a Time-Domain Resource Allocation (TDRA) field). DCI signaling may be configured to signal the association of the time-domain resource of a first data transmission to one of two or more TCI states, along with the time-domain resource of the first data transmission (e.g., the first transmission indicated by the DCI signaling). DCI signaling may further indicate the time-domain resources of further data transmissions (e.g., repetitions of the first data transmission) and each of their associations to one of two or more TCI states. In other words, a bit field of DCI signaling may signal multiple (e.g., two or more) transmission time-domain resources and the associations of two or more TCI states with time-domain resources together.

[0077] It should be noted that further data transmissions may be associated with the same or a different TCI state as the first data transmission. In other words, two or more transmissions may be associated with two or more identical or different TCI states.

[0078] Furthermore, generally, a TCI state may be set in which no time-domain resources (indicated by DCI signaling) are associated. However, two or more TCI states may be set in which time-domain resources are effectively associated. In other words, two or more time-domain resources are effectively associated with different TCI states.

[0079] Furthermore, effectively, each time-domain resource may be associated with a single TCI state of two or more TCI states. In other words, notification / DCI signaling may indicate only a single association for each time-domain resource, linking the time-domain resource to a single TCI state of two or more TCI states.

[0080] Furthermore, it should be noted that, generally speaking, a further transmission may be a repetition, meaning it may be a transmission of the same transport block (TB) as the one transmitted in the first transmission. However, the present invention is not limited thereto, and a further transmission may be a transmission of a TB different from that of the first transmission. In other words, the present invention can be applied directly (similarly) not only to transmissions of different TBs but also to repetitions thereof. Thus, generally speaking, the TBs of all transmissions may be different from each other, some transmissions may have different TBs while others have the same TBs, or all (first and further) transmissions may have the same TBs. Therefore, generally speaking, the terms “transmission” and “repetition” are used interchangeably.

[0081] Furthermore, it should be noted that the present invention is applicable to any number of Transmission Reception Points (TRPs) and / or any number of TCI states. In other words, the specific examples explicitly described below refer to a simple case with only two TRP / TCI states for the sake of simplification. Also, each TRP may be associated with or correspond to each TCI state, and vice versa, and consequently, the terms “TRP” and “TCI state” are used interchangeably in this disclosure.

[0082] Generally, a processor may obtain TCI indicators and notifications by parsing DCI signaling based on syntax and semantics defined by standards and / or possibly configurable at least partially by the network.

[0083] In particular, using a single bit field of a single DCI, the time-domain resources for each transmission, the association of each transmission with one of the notified TCI states, the total number of transmissions associated with each notified TCI state, the number of TCI states (TRPs) actually used for transmission, and / or the total number of repetitions across all TRPs may be determined either by explicit notification or based on implicit instructions.

[0084] In some embodiments, the instructions that the UE obtains from DCI signaling are indexes that point to entries in the TDRA (Time-Domain Resource Assignment) table.

[0085] Generally, entries in a TDRA table typically correspond to rows in the TDRA table. However, other definitions of a TDRA table are also possible, for example, by entries in columns. DCI signaling may include indications for DCI indexes (hereinafter also referred to as DCI indexes). In other words, DCI signaling may generally indicate entries in a TDRA table by indicating the index for each row / column. This DCI index may generally be indicated / notified in DCI signaling by code points. Note that the terms “row” and “entry” in TDRA are used interchangeably below.

[0086] Furthermore, a UE may generally be configured with two or more TDRA tables. The use of TDRA tables should be synchronized with the base station. For example, the base station informs the UE which TDRA table should be applied. Alternatively, in some scenarios, the UE and base station may implicitly derive which TDRA table should be used based on other parameters known to both parties, in the same manner.

[0087] Generally, the more explicit and extensive the information, the greater the flexibility in resource allocation and association, but this may also increase signaling overhead.

[0088] In some embodiments, entries in the TDRA table include two or more sets (or groups) of SLIVs (Start and Length Indicator Values). Effectively, each set corresponds to each TCI state, and each SLIV corresponds to each transmission, indicating the start position and length of the time-domain resource for each transmission. The time-domain resource for each transmission may be associated with the TCI state corresponding to each set of SLIVs (e.g., the SLIV that indicates its time-domain resource).

[0089] Generally, an entry in a TDRA table may contain or indicate one or more SLIV values. SLIVs indicate or specify time-domain resources, for example, by indicating / specifying the start position and length of the time-domain resource. In particular, an SLIV may correspond to an ordered pair of two numbers (in particular integers), one indicating the start position of the time-domain resource and the other indicating the length of the time-domain resource. Generally, an SLIV may indicate a time-domain resource for a single transmission / repetition, and each time-domain resource for a transmission / repetition may be indicated by a single SLIV.

[0090] Generally, each SLIV in a TDRA table may be associated with or correspond to each TCI state. In particular, each SLIV may correspond to only a single TCI state. On the other hand, an entry may indicate zero or more SLIVs for a single TCI state. In other words, an entry may contain or indicate a set of SLIVs for each TCI state of two or more TCI states (e.g., configured TCI states). However, each SLIV may belong to only a single group of SLIVs, which are also called a “group” of SLIVs. These sets may be empty or may contain one or more SLIVs. The time-domain resources indicated by the SLIVs are associated with the same TCI state as each SLIV (i.e., the SLIV indicating the time-domain resource).

[0091] In this regard, please also note that the terms “group,” “set,” and “grouping” in SLIV are used interchangeably.

[0092] Generally, it should be noted that a TDRA entry may further include, or indicate, a Physical Downlink Shared Channel (PDSCH) map type and, for example, a K2 value. The K2 value indicates the slot offset of the starting position indicated by the SLIV of the same TDRA entry. It should be noted that indication of the PDSCH mapping type and notification of the signaling of the slot offset K2 are not required for the present invention. The slot offset may relate to the slot of the DCI signaling indicating the entry in the TDRA table. Furthermore, for repetitions between slots, one or more TDRA tables may include multiple values ​​for K2.

[0093] A specific example of a TDRA table according to this embodiment is shown in TDRA Table 1 below. [Table 1] To make it clear, TDRA Table 1 shows two groups of time-domain resources (SLIVs) for each value of the DCI index; more specifically, the fourth column shows SLIV group 1 and the fifth column shows SLIV group 2. However, in general, a TDRA table may show more than two groups of SLIVs for each value of the DCI index.

[0094] To make it clear, in TDRA Table 1, each group is associated with one of the TCI states. More specifically, in this example, SLIV group 1 corresponds to TCI state 1, and SLIV group 2 corresponds to TCI state 2. In general, the TDRA table may show more groups, each group being associated with a TCI state. In general, groups may be associated with different TCI states. However, the present invention is not limited thereto, and some groups may be associated with the same TCI state.

[0095] In general, each group may have multiple time-domain resources (SLIVs) corresponding to all iterations associated with each TCI state. However, the present invention is not limited thereto, and some groups may have zero or only one SLIV.

[0096] In the specific example shown in TDRA Table 1, a DCI index value of 0 indicates two SLIVs for SLIV group 1, namely SLIV1-0-1 and SLIV1-0-2, and two SLIVs for SLIV group 2, namely SLIV2-0-1 and SLIV2-0-2. On the other hand, a DCI index value of 1 indicates two SLIVs for SLIV group 1, namely SLIV1-1-1 and SLIV1-1-2, but only one SLIV for SLIV group 2, namely SLIV2-1-2. Therefore, in general, within each SLIV group, there can be any number of SLIVs, independently of the number of SLIVs in other SLIV groups and / or the number of SLIVs in other DCI index SLIV groups. In particular, the number of SLIVs in an SLIV group may be zero.

[0097] Generally, based on a TDRA table having the general form of TDRA Table 1 and the notified index shown in DCI (or, in other words, based on entries as shown in TDRA Table 1), the time-domain resources for each iteration may be determined as follows: Each SLIV is mapped one-to-one to each iteration to determine the start symbol and length in a slot by offset K2 from the scheduling PDCCH (e.g., from the slot in the DCI signaling that shows the entry by offset K2). The sequence of SLIVs from all groups is determined by the increasing order of their start symbol values.

[0098] Furthermore, based on TDRA Table 1 (in particular, based on the entries in the TDRA table indicated by the DCI index shown in DCI signaling), the association of each iteration with one of the notified / configured TCI states is determined on a group basis. More specifically, based on the SLIV group, each iteration (or each time-domain resource) is associated with one of the notified TRP / TCI states.

[0099] If a group exists but no SLIV is indicated within that group, it means that the transmission from TRP is not associated with that group. For example, in TDRA Table 1, if SLIV group is 2 and DCI index = 15, then no SLIV has been notified.

[0100] Furthermore, based on TDRA Table 1, the total number of repetitions associated with each configured TCI state may be determined by the number of SLIVs in a given group. In other words, for each entry, the total number of repetitions associated with a TCI state may be determined by counting the SLIVs in the TCI group of that entry. For example, in TDRA Table 1, for SLIV group 2, the total number of repetitions is 2, 1, 2, and 0 for DCI indices 0, 1, 2, and 15, respectively. Furthermore, based on the TDRA table, the number of TCI states (or TRPs) actually used for transmission may be determined by the number of groups in an entry indicated by a DCI index that has at least one notified SLIV. In other words, for a given entry, the number of TCI states actually used may be determined by counting the TCI groups of that entry that have at least one notified SLIV.

[0101] Furthermore, based on TDRA Table 1, the total number of repetitions across all TRPs may be determined by the total number of SLIVs across all groups. For example, in TDRA Table 1, the total number of repetitions is 4, 3, 3, and 2 for DCI indices 0, 1, 2, and 15, respectively.

[0102] A more explicit example of TDRA Table 1 according to this embodiment is shown in TDRA Table 2 below. [Table 2] When DCI index 0 of TDRA Table 2 is notified to the UE, the allocation and association of time-domain resources to the TRP will be as shown in Figure 12.

[0103] In particular, the slot offset for initiating transmission is the "1" slot after the DCI signaling (scheduling PDCCH). More specifically, the "1" slot offset means that the start position of the time-domain resource indicated by the SLIV is specified with respect to the first slot after the DCI signaling. Here, generally, the "certain" DCI signaling is the DCI signaling that indicated the entry by the slot offset.

[0104] To make it clear, SLIV group 1 has three SLIVs, namely "{0,3}", "{4,2}", and "{12,2}", and SLIV group 2 has one SLIV, namely "{8,4}", and each SLIV is represented in the general form "{start position of time-domain resource, length of time-domain resource}". Therefore, based on the start symbol index of the SLIV in the first entry of TDRA Table 2 (corresponding to the second row in TDRA Table 2 by DCI index 0, which is the convention adopted thereafter), the sequence of repetitions is "{0,3}", "{4,2}", "{8,4}", and "{12,2}". Thus, in total, there are four repetitions across TRP 1 (TCI state 1) and TRP 2 (TCI state 2).

[0105] Furthermore, based on the grouping shown in the first entry of the table, the first, second, and fourth repeats are associated with TCI state 1 and therefore from TRP 1, and the third repeat is associated with TCI state 2 and therefore from TRP 2. Thus, there are three repeats from TRP 1 and one repeat from TRP 2.

[0106] All of this is also shown in Figure 12. Explicitly, the time-domain resource for the first transmission / repetition is the first three symbols of TRP 1 in the first slot after DCI signaling (e.g., by indices 0, 1, and 2). The time-domain resource for the second repetition is the symbols of TRP 1 at indices 4 and 5 in the first slot after DCI signaling. The time-domain resource for the third repetition is the symbols of TRP 2 at indices 8, 9, 10, and 11 in the first slot after DCI signaling, and the time-domain resource for the fourth repetition is the symbols of TRP 1 at indices 12 and 13 in the first slot after DCI signaling.

[0107] This embodiment (for example, a TDRA table in the form of TDRA Table 2) provides complete flexibility, having the ability to assign any unique SLIV value, any order of TCI states to each transmission, and an equal number of repetitions to different TCI states.

[0108] In an exemplary implementation, each set contains one or fewer SLIVs, and the entry in the TDRA table contains an indication of the total number of transmissions (e.g., the total number of transmissions explicitly or implicitly scheduled / instructed by this entry).

[0109] In these embodiments, each group may have only one time-domain resource (SLIV) corresponding to the first transmission associated with each TCI state. Furthermore, each entry in the TDRA table may indicate the total number of repetitions, where the total number of transmissions refers to the total number of transmissions scheduled by that entry in the TDRA table (the entry that also indicates the total number).

[0110] It should be noted that the total number of SLIVs indicated by an entry (for example, by an entry in TDRA Table 2) implicitly indicates the total number of transmissions. This implicit number may be obtained simply by counting the explicitly indicated SLIVs. However, an entry may also explicitly and / or separately indicate the total number of transmissions from the implicit indication described above by the number of SLIVs. Therefore, in general, the total number of transmissions indicated by an entry may differ from (for example, be greater than) the total number of SLIVs explicitly indicated by that entry. Thus, such an entry implicitly indicates the existence of transmissions other than those explicitly indicated by the SLIVs of that entry.

[0111] In some embodiments, the UE's processor determines, for each set containing one SLIV during operation, the start position and length of the time-domain resource for each first transmission of the set (e.g., a first transmission with the TCI state corresponding to the set) according to the SLIV contained in the set (i.e., the one SLIV). Alternatively, the processor may determine, for each transmission that is not one of the first transmissions during operation, i) an association between one of two or more TCI states and a time-domain resource for transmission by pattern, where the pattern represents a sequence of TCI states and corresponds to the start position of the time-domain resource for the first transmission; ii) the length of the time-domain resource for transmission (a first transmission of an notified transmission having the same TCI state as each transmission), where the time-domain resource for each first transmission and the time-domain resource for transmission are associated with the same TCI state; and / or iii) the start position of the time-domain resource for transmission, according to the offset, start position and length of the time-domain resource for one of the transmissions preceding the transmission. Here, the offset may correspond to (or be determined from / based on) the start position and / or length of time-domain resources for at least two first transmissions.

[0112] The above determination process is explained with reference to TDRA Table 3. [Table 3]

[0113] To make it clear, the sixth column of TDRA Table 3 (explicitly) indicates the total number of repetitions. In general, TDRA may include a separate column (not necessarily the sixth column) that (explicitly) indicates the total number of repetitions. Based on such a table, the total number of repetitions across all TRP / TCI states may therefore be determined from the explicit indication in the separate column. More generally, entries in a TDRA table may indicate / include the total number of repetitions across all TRP / TCI states, and therefore that total is determined from the explicit indication.

[0114] In general, based on a TDRA table having the general form of TDRA Table 3 and the notified DCI index (or, i.e., based on entries as shown in TDRA Table 3), the number of TRP / TCI states actually used for transmission may be determined by the number of SLIV groups in an entry (e.g., an entry indicated by DCI) that has at least one SLIV indicated for that group. In other words, for a given entry, the number of TCI states actually used may be determined by counting the TCI groups of that entry that have at least one specified SLIV.

[0115] As far as time-domain resources are concerned, for each TCI group, up to one SLIV corresponding to the start symbol and length of the first iteration from the associated TRP can be specified. For the first iteration, the time-domain resource is associated with the TCI state of the TCI group of the SLIV that explicitly specifies that time-domain resource.

[0116] Furthermore, if the total number of transmissions actually used is greater than the number of TCI states, there are further / successive iterations not explicitly specified by the SLIV in the TDRA entry. Here, these further / successive transmissions may correspond to the "total number of transmissions" minus the "number of TCI states actually used".

[0117] The association of these further repetitions may be determined by distributing them (e.g., evenly) according to a pattern across the TCI states actually used (e.g., the TCI states specified in each TDRA entry for the first repetition). The pattern may be predetermined, semi-static, and / or RRC-configured. For example, all alternating repetitions may be associated with the alternating TCI states. Alternatively, or further, subsequent repetitions may be associated with the TCI states actually used in a round-robin manner, for example, based on the order of the TCI states in the first repetition. For example, the order of the first repetition may repeat periodically. In general, the pattern may be predetermined or may be derived from the SLIV of the first repetition, in particular from the order of the TCI states in the first repetition. Generally, such a pattern represents a sequence of configured TCI states.

[0118] The starting position (also called the start symbol) of the time-domain resource (SLIV) for subsequent iterations is determined as follows: The start symbol for each iteration may be determined, for example, by a symbol offset between the start and / or end symbols of the SLIV from different SLIV groups. Alternatively, the offset value may be predetermined, semi-static, and / or RRC set. For example, the offset may be set to 1, which corresponds to the sequential allocation of the resource.

[0119] The symbol offset may be calculated from the notified SLIV by subtracting the start / end positions of the time-domain resource explicitly indicated by two (different) SLIVs (the end position may be the start position plus a length).

[0120] The symbol offset may be added to the start / end position of a time-domain resource for a single repetition in order to obtain the start / end position of the time-domain resource for subsequent (e.g., consecutive) repetitions. It should also be noted that, in general, all time-domain resources for subsequent transmissions may be determined based on the same symbol offset. Alternatively, different symbol offsets may be used for each subsequent repetition.

[0121] The length of the time-domain resources for subsequent / further iterations (e.g., iterations other than the first iteration) may be based on the length of the time-domain resources for the first iteration. In particular, the length of a subsequent transmission may be based on the length of the first transmission within the same group as this subsequent transmission. For example, the length of a subsequent iteration may be the same as the length of the first iteration of each corresponding group.

[0122] Furthermore, the total number of repetitions associated with each configured TCI state may be determined by dividing the total number of repetitions explicitly specified by the number of TCI states actually used for transmission. Alternatively, for each entry, the total number of repetitions associated with the TCI state may be determined by counting the SLIVs within the TCI group for that entry.

[0123] This design option is less flexible, but it requires a smaller table size and lower DCI overhead to represent the table rows.

[0124] A more explicit example of TDRA Table 3 according to this embodiment is shown in TDRA Table 4. [Table 4]

[0125] When DCI index 0 of TDRA Table 4 is notified to the UE, the allocation and association of time-domain resources to the TRP will be as shown in Figure 13, corresponding to in-slot scheduling.

[0126] In particular, K2 in the first entry is shown to be "1", and therefore the slot offset for starting the transmission is the "1" slot after the scheduling PDCCH. Based on "{0,3}" in SLIV 1, the first iteration is from TRP 1, starting with symbol #0 and spanning 3 symbols. That is, the time-domain resources for the first iteration are the symbols by indices #0, #1 and #2. Furthermore, based on "{5,3}" in SLIV 2, the first iteration is from TRP 2 (the entirety of the second iteration), starting with symbol #5 and spanning 3 symbols (i.e., symbols #5, #6 and #7). The symbol offset between iterations is calculated as 3 (the difference between the first symbol index of #5 in SLIV 2 and the last symbol index of #3 in SLIV 1).

[0127] Since the total number of repetitions is shown as "3", there is one subsequent repetition (the entire third repetition). In this example, the repetition associations follow an alternating pattern, and since the second repetition is from TRP 2, the third repetition will be from TRP 1. Furthermore, based on the symbol offset "3" and the index "7" of the last symbol of the second repetition, the index of the starting symbol of the third repetition will be #10. The length of the third repetition is the same as the length of the first repetition, and the first repetition uses the same TRP as the third repetition. As a result, the third repetition will span three symbols (i.e., symbols #10, #11, and #12).

[0128] Another explicit example of TDRA Table 3 according to this embodiment is shown in TDRA Table 5. [Table 5]

[0129] When DCI index 0 of TDRA Table 5 is notified to the UE, the allocation and association of time-domain resources to the TRP will be as shown in Figure 14, corresponding to inter-slot and intra-slot scheduling.

[0130] To make it clear, the entry for DCI index 0 in TDRA Table 5 differs from the entry for DCI index 0 in TDRA Table 4 only in that the total number of repetitions is indicated as "4" (instead of "3" as indicated by TDRA Table 4). Therefore, the time-domain resources for the first, second, and third repetitions are identical to those in TDRA Table 4, and for simplicity, the corresponding explanations will not be repeated.

[0131] However, in the case of TDRA Table 5, there is an additional subsequent iteration (the entire fourth iteration). In this example, the association of the iterations follows an alternating pattern, and since the third iteration is from TRP 1, the fourth iteration will be from TRP 2. Furthermore, based on the symbol offset "3" and the index "12" of the last symbol in the third iteration, the index of the starting symbol for the third iteration is #15. However, in this example, the total number of symbols in each slot is only 14 (i.e., slots #0 to #13). Therefore, the third iteration starts from the second slot after scheduling PDCCH at symbol position #1, which is calculated by subtracting 14 from 15.

[0132] The length of the fourth repeat is the same as the length of the second repeat, and the second repeat uses the same TRP as the fourth repeat. As a result, the fourth repeat spans three symbols (i.e., symbols #15, #16, and #17).

[0133] This embodiment (for example, a TDRA table in the form of TDRA Table 3, 4, or 5) offers the benefits of a smaller table size and lower DCI overhead for representing rows / entries in a TDRA table.

[0134] In some embodiments, an entry in the TDRA table includes an indication of the total number of transmissions, an indication of the offset between transmissions, and a single SLIV. The single SLIV indicates the start position of the time-domain resource for the first transmission and the length of the time-domain resource for the first transmission (e.g., for the first transmission, as explicitly or implicitly indicated by the entry).

[0135] As shown in TDRA Table 6, in some embodiments, each entry in the TDRA table explicitly indicates only a single SLIV, symbol offset, and total number of repetitions. Specifically, in the example shown in TDRA Table 6, the fourth, fifth, and sixth columns indicate a single SLIV, symbol offset, and total number of repetitions, respectively.

[0136] A time-domain resource indicated by a single SLIV may correspond to the first transmission from a first TCI state. In other words, a single SLIV indicated by an entry may be used to calculate the start symbol and length of the time-domain resource for the first iteration from the first TCI state. This first TCI state may be predetermined, semi-static, and / or RRC set.

[0137] Time-domain resources (SLIVs) for subsequent iterations may be implicitly notified / determined and associated with TCI states configured using predetermined, semi-static, and / or RRC-configured patterns. For example, subsequent iterations may be associated with TCI states configured in a round-robin manner. [Table 6]

[0138] In an exemplary implementation, the UE's processor determines the start position of the time-domain resource for the first transmission according to the start position indicated by a single SLIV for the first transmission during operation. Alternatively, the processor may determine the length of the time-domain resource for the first transmission according to the length indicated by a single SLIV for the first transmission. Alternatively, the processor may determine, for each transmission other than the first transmission, i) the length of the time-domain resource for the transmission according to the length of the time-domain resource for the first transmission, ii) the start position of the time-domain resource for the transmission according to the offset indication and the start position and length of the time-domain resource for the first transmission, and / or iii) the association of two or more TCI states with the time-domain resource for the transmission according to a predetermined pattern.

[0139] In general, based on a TDRA table having the general form of TDRA Table 6 and the notified DCI index (i.e., in other words, based on entries as shown in TDRA Table 6), the number of TRP / TCI states actually used for transmission may be determined by counting all TCI states indicated by TCI code points (i.e., code points of bit fields that may associately encode TCI indicators together with some further parameters). Furthermore, the total number of repetitions across all TRP / TCI states may be notified by explicit indications in separate columns and thus determined from these explicit indications.

[0140] The time-domain resource for the first iteration may be indicated by a single SLIV and therefore determined from a single SLIV. In other words, the single SLIV indicated by the entry may be used to calculate the start symbol and length of the time-domain resource for the first iteration from a first TCI state. This first TCI state may be predetermined, semi-static, and / or RRC set.

[0141] Furthermore, if the total number of transmissions is greater than 1, there are further / successive repetitions not explicitly specified by SLIV in the TDRA entry. Here, the number of these further successive transmissions may correspond to the "total number of transmissions" minus "1".

[0142] These further recurring associations may be determined by distributing them (e.g., evenly) according to a pattern (e.g., in a round-robin manner) across the TCI states actually used (e.g., TCI states indicated by code points). The pattern may be predetermined, semi-static, and / or RRC-set. For example, all alternating recursions may be associated with alternating TCI states, and / or the pattern may represent a set of TCI states that repeat periodically. In general, such predetermined patterns represent a set sequence of TCI states.

[0143] For example, the length of the time-domain resource for subsequent iterations, such as iterations other than the first iteration, may be determined based on the length of the first iteration. For example, the length of subsequent iterations may be the same as the length of the first iteration.

[0144] The start position (also known here as the start symbol) of the time-domain resource (SLIV) for subsequent iterations may be implicitly determined / notified using a notified offset. More specifically, the symbol offset may be added to the start / end position of the time-domain resource for one iteration to obtain the start / end position of the time-domain resource for subsequent (e.g., consecutive) iterations. It should also be noted that, in general, the time-domain resources for all subsequent transmissions may be determined based on the same symbol offset. Alternatively, a different symbol offset may be used for each subsequent iteration.

[0145] Furthermore, the total number of repetitions associated with each configured TCI state may be determined by dividing the total number of explicitly specified repetitions by the number of TCI states actually used for transmission. Alternatively, for each entry, the total number of repetitions associated with a TCI state may be determined by counting the SLIVs in that TCI group for that entry.

[0146] A more explicit example of the TDRA table in this embodiment is shown in TDRA Table 7. [Table 7]

[0147] When DCI index 0 of TDRA Table 7 is notified to the UE, the allocation and association of time-domain resources to the TRP will be as shown in Figure 15.

[0148] In particular, K2 of the first entry is shown to be "1", and therefore the slot offset for initiating transmission is the "1" slot after the scheduling PDCCH.

[0149] Based on a single SLIV "{0,3}", the first iteration starts from TRP 1, beginning with symbol #0 and spanning three symbols. In other words, the time-domain resources of the first iteration are the symbols with indices #0, #1, and #2.

[0150] The total number of iterations is shown to be "3," and therefore the association between the two iterations and the time-domain resources are implicitly communicated.

[0151] In this example, association / grouping is based on an alternating pattern, resulting in two TCI states. Consequently, the first and third repetitions originate from TRP 1, and the second repetition originates from TRP 2. Therefore, the total number of repetitions associated with TRP 1 is 2, and the total number of repetitions associated with TRP 2 is 1.

[0152] Furthermore, based on the notified offset "3" of the first iteration and the index "2" of the last symbol (generally, the last symbol of a certain / previous iteration may be used as a reference for the offset), the second iteration begins with symbol #5. Depending on the length of the first iteration, the length of the second iteration is 3 symbols. Thus, in summary, the second iteration is from TRP 2, begins with symbol #5, and spans three symbols (i.e., symbols #5, #6, and #7).

[0153] Furthermore, based on the notified offset "3" of the second iteration and the index "7" of the last symbol, the third iteration begins with symbol #10. Depending on the length of the first iteration, the length of the second iteration is 3 symbols. Thus, in summary, the second iteration is from TRP 1, begins with symbol #10, and spans 3 symbols (i.e., symbols #10, #11, and #12).

[0154] This embodiment (for example, a TDRA table in the form of TDRA Table 6 or 7) offers the advantages of a smaller TDRA table size and lower DCI overhead compared to other tables, which are required to display rows / entries in the TDRA table. Furthermore, the symbol offset between repetitions allows the UE to tolerate beam switching delays for receiving from one TRP to another. When transmissions with different TCI states occur consecutively, the UE may not have enough time to beam switch to receive transmissions from different TRPs.

[0155] In other exemplary implementations, an entry in the TDRA table includes a first SLIV, a second SLIV, and an indicator indicating the total number of transmissions (e.g., the total number of transmissions explicitly or implicitly indicated by the entry), where the first SLIV may indicate the start position of the time-domain resources for the first transmission and the length of the time-domain resources for the first transmission, and the second SLIV may indicate the start position of the time-domain resources not available for transmission and the length of the time-domain resources not available for transmission.

[0156] As shown in TDRA Table 8, in some embodiments, each entry in the TDRA table explicitly indicates the first time-domain resource, the second time-domain resource (e.g., by each SLIV), and the total number of repetitions. The TDRA table may further indicate the symbol offset and PDSCH mapping type for each value of the DCI index. In particular, in the exemplary TDRA Table 8, the columns labeled “SLIV 1” and “SLIV 2” indicate the first and second time-domain resources, respectively.

[0157] Generally, only one of the two SLIVs may indicate a time-domain resource for a transmission, for example, for the first transmission of the transmission indicated by each entry. In other words, the first time-domain resource (SLIV) may correspond to a first transmission from a first TCI state. This first TCI state may be predetermined, semi-static, and / or RRC set.

[0158] Subsequently, time-domain resources (SLIVs) for subsequent iterations (or, generally, other iterations not explicitly indicated by the first SLIV) may be implicitly determined and associated with TCI states set using predetermined, semi-static, and / or RRC-set patterns. For example, subsequent iterations may be associated with TCI states set in a round-robin manner.

[0159] The other SLIV of two SLIVs may indicate a time-domain resource that is not available for repetition. In other words, the second time-domain resource (SLIV) corresponds to a symbol and / or time-domain resource that is not available for data transmission. The time-domain resource for repetition, in particular the time-domain resource for subsequent repetitions, may be determined by taking into account that the time-domain resource indicated by the second SLIV is not available for repetition. [Table 8]

[0160] In general, based on a TDRA table having the general form of TDRA Table 6 and the notified DCI index (i.e., in other words, based on entries as shown in TDRA Table 6), the number of TRP / TCI states actually used for transmission may be determined by counting all TCI states indicated by TCI code points (i.e., code points of bit fields that can associately encode TCI indicators together with some further parameters). Furthermore, the total number of repetitions across all TRP / TCI states may be indicated by explicit indications in a separate column and thus determined from these explicit indications.

[0161] The time-domain resource for the first iteration may be indicated by and thus determined from one of the two SLIVs, for example, the first SLIV. In other words, the first SLIV indicated by the entry may be used to calculate the start symbol and length of the time-domain resource for the first iteration from the first TCI state.

[0162] Furthermore, if the total number of transmissions is greater than 1, there are further / successive repetitions not explicitly specified by the SLIV in the TDRA entry. Here, the number of these further successive transmissions may correspond to the "total number of transmissions" minus "1".

[0163] These further recurring associations may be determined by distributing them (e.g., evenly) according to a pattern (e.g., in a round-robin manner) across the TCI states actually used (e.g., TCI states indicated by code points). The pattern may be predetermined, semi-static, and / or RRC-set. For example, all alternating recursions may be associated with alternating TCI states. Generally, such predetermined patterns represent a set sequence of TCI states.

[0164] For example, the length of the time-domain resource for subsequent iterations, such as iterations other than the first iteration, may be determined based on the length of the first iteration. For example, the length of subsequent iterations may be the same as the length of the first iteration.

[0165] The starting position of the time-domain resource (SLIV) for subsequent iterations may be determined using an offset. The value of the offset may be predetermined, semi-static, and / or RRC set. For example, the offset may be set to 1, corresponding to the continuous allocation of resources. For example, if there is no conflict with the time resource indicated / determined by the second SLIV, subsequent iterations may be allocated continuously (corresponding to the offset set to 1). However, if there is a conflict between the time resource determined by the second SLIV and any of the time symbols of any iteration, these particular symbols may not be used in that transmission. Also note that, in general, the time-domain resources for all subsequent transmissions may be determined based on the same symbol offset. Alternatively, different symbol offsets may be used for each subsequent iteration.

[0166] Furthermore, the total number of repetitions associated with each configured TCI state may be determined by dividing the explicitly specified total number of repetitions by the number of TCI states actually used for transmission. Alternatively, for each entry, the total number of repetitions associated with a TCI state may be determined by counting the SLIVs in that TCI group for that entry.

[0167] In some embodiments where an entry in the TDRA table indicates a time-domain resource not available for transmission, the processor determines, during operation, the mapping of the transmission to the time-domain resource. In this mapping, the length of the time-domain resource for each transmission is the same as the length indicated by the first SLIV for the first transmission. In this mapping, the transmission is mapped to available time-domain resources for two or more TCI states according to a predetermined offset, starting from the starting position of the time-domain resource for the first transmission indicated by the first SLIV, where the predetermined offset may indicate separation between time-domain resources for consecutive transmissions. Each time-domain resource may be associated with one of two or more TCI states according to a predetermined pattern (in other words, the processor determines, during operation, the association of two or more TCI states with time-domain resources according to a predetermined pattern).

[0168] Here, the term "mapping" refers to the allocation of time-domain resources to a transmission, and each allocated time-domain resource is associated with one of the (configured) TRP / TCI states. In other words, mapping allocates resources of the configured TCI states to a transmission.

[0169] A more explicit example of TDRA Table 8 according to this embodiment is shown in TDRA Table 9. [Table 9]

[0170] When DCI index 0 of TDRA Table 9 is notified to the UE (and the mapping according to this embodiment is used), the time-domain resource allocation and association to the TRP, or i.e., the mapping, will be as shown in Figure 16.

[0171] Specifically, as in the previous example, the slot offset for initiating transmission is indicated as "1," and therefore the first iteration begins in the slot after the DCI signaling (scheduling PDCCH).

[0172] In this example, it is further assumed that the UE is set by a repetition, two TCI states, and a symbol offset of 1 between TCI state 1 and TCI state 2, and that TCI state 1 is specified as the TCI state of the first repetition and a pattern that changes the TCI state by all repetitions (alternating).

[0173] Since the total number of repetitions is shown as "3", there are two subsequent repetitions, namely the second and third repetitions.

[0174] Based on the set pattern and the first TCI state, it is already determined that there are two repeats from TRP 1, namely the first and third repeats. Similarly, it is determined that there is one repeat from TRP 2, namely the second repeat.

[0175] Based on the symbol offset "1" and the index "#2" of the last symbol in the first iteration, it can be determined that the second iteration begins with symbol #3.

[0176] Based on the SLIV 1 "{0,3}" of the first entry, the first iteration spans three symbols, meaning the time-domain resource for the first iteration is 3 (symbols). Furthermore, since the same length as the first iteration is used for subsequent iterations, the time-domain resources for the second and third iterations also have a length of 3 (symbols).

[0177] According to this embodiment, the iteration starts from the start position indicated by the first SLIV and is mapped to the available time-domain resources (only) of the configured TCI state. Details are as follows:

[0178] Based on the SLIV 1 "{0,3}" of the first entry, the starting position of the first iteration is symbol #0, and therefore the mapping starts from symbol #0. Since there are no conflicts with unavailable resources for the first iteration, the first iteration maps to symbols #0, #1, and #2.

[0179] More specifically, the second SLIV "{5,1}" indicates that symbol #5 is not available for transmission. Therefore, the mapping may assume that all symbols of TRP 1 and TRP 2 are available, except for symbol #5 of TRP 1 and symbol #5 of TRP 2.

[0180] Since the symbol offset is "1", the mapping follows the available symbol #3. Note that, according to the present invention, the symbol offset corresponds to the difference between the index of the last symbol in the first iteration and the index of the first symbol in the second iteration. Thus, a symbol offset of "1" means that there is no symbol between the two consecutive transmissions.

[0181] As a result, the second iteration begins with symbol #3. Symbol #4 is also available, and therefore symbol #4 is also assigned to the second iteration. However, since symbol #5 is not available, the mapping of the second iteration to resources continues with the available symbol #6. Thus, in summary, the second iteration maps to symbols #3, #4, and #6. In other words, the second iteration consists of a first part (symbols #3 and #4) and a second part (symbol #6), separated by symbol #5.

[0182] The mapping continues with available symbols #7, #8, and #9 to which the third repetition is mapped. Note that the entire transmission after the collision (at symbol #5) is shifted (in this example, by one symbol).

[0183] In some embodiments, where an entry in the TDRA table indicates a time-domain resource that is not available for transmission, the processor determines the mapping of the transmission to a time-domain resource, starting from the starting position of the time-domain resource for a first transmission indicated by a first SLIV during operation, and mapping the transmission to two or more TCI state time-domain resources according to a predetermined offset. In the mapping, i) a predetermined offset indicates separation between time-domain resources of consecutive transmissions; ii) the time-domain resource to which a transmission is mapped includes available and unavailable time-domain resources; iii) any transmission is mapped to a time-domain resource having a length indicated by a first SLIV for a first transmission, counting the unavailable time-domain resources (along with the available time-domain resources) (of the time-domain resource to which a given transmission is mapped); iv) any transmission mapped to a time-domain resource containing unavailable time-domain resources is punctured; and / or v) each time-domain resource is associated with one of two or more TCI states according to a predetermined pattern (in other words, the processor determines the association of two or more TCI states with time-domain resources according to a predetermined pattern during operation).

[0184] As mentioned above, the term “mapping” refers to the allocation of time-domain resources to a transmission, and each allocated time-domain resource is associated with one of the (configured) TRP / TCI states. In other words, mapping allocates resources of the configured TCI states to a transmission.

[0185] Another explicit example of TDRA Table 8 according to this embodiment is shown in TDRA Table 10. Note that TDRA Table 10 corresponds to TDRA Table 9. [Table 10]

[0186] When DCI index 0 of TDRA Table 10 is directed to the UE (and the mapping according to this embodiment is used), the time-domain resource allocation and association to the TRP, or in short, the mapping, will be as shown in Figure 16.

[0187] It should be noted that this embodiment differs from the previous embodiment in that the transmitted collision symbols are punctured (not shifted). Therefore, the differences mainly concern the mapping starting with the second repeat collision at symbol #5. The differences in mapping compared to the previous embodiment will be emphasized below.

[0188] According to this embodiment, iterations begin at a starting position indicated by a first SLIV and are mapped to available and unavailable time-domain resources in the configured TCI state. In particular, each transmission is mapped to a time-domain resource of the same length, e.g., the length explicitly indicated by the first SLIV. Here, the length of the time-domain resource to which a given transmission is mapped is the sum of the length of the available time-domain resource to which the given transmission is mapped and the length of the unavailable time-domain resource to which the given transmission is mapped. In other words, the unavailable resource to which a transmission is mapped counts / contributes to the length of the time-domain resource to which the transmission is mapped. Details are as follows.

[0189] Based on the SLIV 1 "{0,3}" of the first entry, the starting position of the first iteration is symbol #0, and therefore the mapping starts from symbol #0. Furthermore, each iteration has the same length "3". Note that in this embodiment, iterations are also mapped to unavailable time-domain resources that are counted against the length of the iteration. In other words, the total number of symbols to which a given iteration is mapped (i.e., available and unavailable time-domain resources) is considered the length of the iteration in this embodiment.

[0190] Therefore, assuming an offset of 1 again, the first iteration maps to symbols #0, #1 and #2, the second iteration maps to symbols #3, #4 and #5, and the third iteration maps to symbols #6, #7 and #8.

[0191] However, as with the above embodiment, symbol #5 to which the second repetition is mapped is not available.

[0192] Therefore, according to this embodiment, the first entry in TDRA Table 10 implicitly indicates only symbols #3 and #4 for the second iteration. In other words, the second iteration is punctured to match the length of the available resource to which the second iteration is mapped.

[0193] This embodiment (for example, a TDRA table in the form of TDRA Table 8, 9, or 10) makes it possible to indicate time-domain resources unavailable for transmission. This can facilitate scheduling of available time-domain resources without causing recurring conflicts with unavailable resources.

[0194] Generally, the processor may determine the TDRA table from at least two predetermined TDRA tables according to the TCI indicator during operation (1020).

[0195] In some embodiments, the UE is configured by multiple TDRA tables. As shown in Figure 10, the UE may be configured by the RRC with an old TDRA table and a new TDRA table (1000). For example, the old TDRA table may point to only one TCI state time-domain resource, while the new TDRA table points to two or more TCI state time-domain resources. Generally, the UE may be configured to use the old TDRA table when the TCI indicator indicates that multiple TCI states are not indicated / configured in the DCI signaling. However, when the TCI indicator indicates that multiple TCI states are indicated / configured in the corresponding DCI signaling, the UE may be configured to use the new TDRA table (i.e., to take entries from the new TDRA table instead of the old TDRA table). Generally, the TCI indicator does not need to be indicated as a separate bit field. It may be indicated together with other parameters. In other words, one or more code points of such a combined bit field may indicate that one TRP is being used, while one or more other code points indicate that two TRPs are being used. Similarly, any number of TRPs may be indicated by one or more code points of a coupled bit field carrying such a TCI indicator.

[0196] Figure 10 shows an exemplary method for the UE. In step 1000, the UE is reconfigured via RRC signaling with old_TDRA_table and new_TDRA_table. old_TDRA_table is the table when only one TRP is active. new_TDRA_table is the table when two or more TRPs are active for sending and receiving data by the UE. In step 1010, the UE receives the scheduling DCI (e.g., on a PDCCH monitored by the UE) and checks the code point for the TCI instruction. In step 1020, the UE evaluates (evaluates / determines) whether the TCI instruction indicates multiple TCI states. If multiple TCI states are indicated (Yes in step 1020), the UE uses new_TDRA_table in step 1030. In other words, the UE adopts the new table for determining resource allocation. Then, in step 1040, the UE determines the time-domain resources and total number of repetitions for each transmission (e.g., each iteration). It should be noted that the present invention is not limited to repetitions, and transmissions may also be transmissions of different transport blocks. The order of steps 1030 and 1040 can be reversed. In step 1050, the UE associates each repetition (or generally transmission) with one of the designated TCI states. Repetitions (transmissions) may be associated with the same or different TCI states. Finally, in step 1060, the UE receives data downlink (or transmits data uplink) from multiple TRPs (TCI states) on the allocation and associated resources.

[0197] In step 1020, if only one TCI state is indicated (No in step 1020), the UE uses (applies) the old_TDRA_table in step 1035. In step 1045, the UE determines the time-domain resource for the corresponding transmission. In step 1055, the UE associates the transmission with the single indicated TCI state. Finally, in step 1065, the UE receives a data transmission from one TRP on the allocated resource.

[0198] For example, in NR Rel.16, it was agreed to use the code point of the TCI bit field to signal two TCI states (instead of one TCI state in Rel.15), which essentially means that two TRP transmissions are possible.

[0199] Switching the TDRA table used and applied by the TCI indicator provides flexibility in changing the TDRA table.

[0200] In general, a transmission may consist of repetitions of the same data portion.

[0201] Figure 18 shows how this is implemented on both the UE and the base station communicating with each other.

[0202] Another embodiment provides a method for a user device UE. The method includes step S1840 of receiving downlink control information DCI in a PDCCH. The method further includes step S1850 of obtaining from DCI signaling a TCI (Transmission Configuration Indication) indicator that two or more TCI states are set, and a notification indicating a time-domain resource for transmission and an association between the time-domain resource and two or more TCI states, each time-domain resource being associated with one of two or more TCI states. The method further includes step S1880 of receiving or transmitting data (as shown in the DCI signaling) relating to the time-domain resource associated with each of the two or more TCI states.

[0203] Another embodiment provides a method to be performed at a base station. This method may include step S1810, which performs the allocation of time-domain resources of a plurality of TRPs to be notified to the UE for transmission. According to this allocation, in step S1820, the base station generates downlink control information DCI signaling to be carried on the PDCCH in a certain manner, so that it provides a TCI (Transmission Configuration Indication) indicator in the DCI signaling that specifies that two or more TCI states are set, and each time-domain resource is associated with one of the two or more TCI states. The method further includes step S1830, which transmits the DCI signaling, and step S1870, which receives or transmits data (as indicated in the DCI signaling) on ​​the time-domain resource associated with each of the two or more TCI states.

[0204] This disclosure can be implemented by software, hardware, or software that interacts with hardware. Each functional block used in the description of each embodiment described above can be implemented partially or entirely by an LSI (Large Scale Integration) such as an integrated circuit, and each process described in each embodiment may be controlled partially or entirely by the same LSI or a combination of LSIs. The LSI may be formed as individual chips, or a single chip may be formed to include some or all of the functional blocks. The LSI may include data inputs and outputs coupled thereto. Here, LSIs may be called ICs, system LSIs, super LSIs, or ultra LSIs depending on the degree of integration. However, the technology for realizing integrated circuits is not limited to LSIs, and may be implemented using dedicated circuits, general-purpose processors, or application-specific processors. Furthermore, a Field Programmable Gate Array (FPGA) that can be programmed after manufacturing of an LSI or reconfigurable processor in which the connections and settings of circuit cells arranged inside the LSI can be reconfigured may be used. This disclosure can be implemented as digital processing or analog processing. As a result of advancements in semiconductor technology and other derivative technologies, if future integrated circuit technology replaces LSIs, functional blocks can be integrated using future integrated circuit technology. Biotechnology can also be applied.

[0205] This disclosure can be implemented by any type of device, apparatus, or system having communication capabilities, referred to as a communication apparatus.

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

[0207] Communication devices are not limited to being portable or mobile, and may include any type of device, system, or apparatus that is non-portable or fixed, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other “thing” in the “Internet of Things (IoT)” network.

[0208] Communication may include, for example, exchanging data via cellular systems, wireless LAN systems, satellite systems, and various combinations thereof.

[0209] The communication device may include devices such as controllers or sensors coupled to a communication device that performs the communication functions described in this disclosure. For example, the communication device may include controllers or sensors that generate control signals or data signals used by the communication device that performs the communication functions of the communication device.

[0210] The communication equipment may also include infrastructure facilities such as base stations and access points, and any other equipment, devices, or systems that communicate with or control such equipment as those in the non-limiting examples above.

[0211] According to the first embodiment, a user device (UE) is provided. The UE includes a transceiver that receives downlink control information (DCI) signaling during operation, a TCI indicator that specifies that two or more TCI (Transmission Configuration Indication) states are set from the DCI signaling during operation, and a processor that obtains a time-domain resource for transmission and an instruction indicating the association between the two or more TCI states and the time-domain resource, each of which the time-domain resource is associated with one of the two or more TCI states, wherein the transceiver receives or transmits data on the time-domain resource associated with each of the two or more TCI states during operation.

[0212] In addition to the first embodiment, according to the second embodiment, the instruction is an index that indicates an entry in the TDRA (Time Domain Resource Assignment) table.

[0213] In addition to the second embodiment, according to the third embodiment, the entries in the TDRA table include two or more sets of SLIVs (Start and Length Indicator Values), each set corresponding to a TCI state, each SLIV corresponding to a transmission, and the start position of the time-domain resource for each transmission, which is associated with the TCI state corresponding to the set of SLIVs, and the length of the time-domain resource for each transmission.

[0214] In addition to the third embodiment, according to the fourth embodiment, each set includes one or fewer SLIVs, and the entries in the TDRA table include an indication of the total number of transmissions.

[0215] In addition to the fourth embodiment, according to the fifth embodiment, the processor, during operation, determines the start position and length of a time-domain resource for each first transmission according to the SLIVs included in the set for each set containing one SLIV, and / or, for each transmission that is not one of the first transmissions, it determines a start position, which is a sequence of TCI states, an association between one of the two or more TCI states and the time-domain resource for the transmission according to a pattern corresponding to the start position of the time-domain resource for the first transmission, the length of the time-domain resource for the transmission by the length of the time-domain resource for each first transmission, wherein each of the time-domain resources for the first transmission and the time-domain resource for the transmission are associated with the same TCI state, and / or, the start position of the time-domain resource for the transmission by the offset, start position and length of the time-domain resource for one of the transmissions preceding the transmission, wherein the offset corresponds to the start position and / or length of at least two time-domain resources for the first transmissions.

[0216] In addition to the second embodiment, according to the sixth embodiment, the entries in the TDRA table include an instruction for the total number of transmissions, an instruction for the offset between transmissions, a single SLIV indicating the start position of the time-domain resource for the first transmission, and the length of the time-domain resource for the first transmission.

[0217] In addition to the sixth embodiment, according to the seventh embodiment, the processor, during operation, determines the start position of the time-domain resource for the first transmission by the start position indicated by the single SLIV for the first transmission, the length of the time-domain resource for the first transmission by the length indicated by the single SLIV for the first transmission, and / or, for each transmission that is not the first transmission, (i) the length of the time-domain resource for the transmission by the length of the time-domain resource for the first transmission, (ii) the start position of the time-domain resource for the transmission by the indication of the start position and length of the time-domain resource for the first transmission and the offset, and / or (iii) the association of the two or more TCI states with the time-domain resource for the transmission by a predetermined pattern.

[0218] In addition to the second embodiment, according to the eighth embodiment, the entry in the TDRA table includes an indication of the total number of transmissions, a first SLIV indicating (i) the starting position of the time-domain resources for the first transmission, and (ii) the length of the time-domain resources for the first transmission, and a second SLIV indicating (i) the starting position of the time-domain resources not available for the transmission, and (ii) the length of the time-domain resources not available for the transmission.

[0219] In addition to the eighth embodiment, according to the ninth embodiment, the processor determines the mapping of the transmissions to the time-domain resources during operation, the length of the time-domain resources for each transmission being the same as the length indicated by a first SLIV for the first transmission, the transmissions are mapped to the available time-domain resources of the two or more TCI states according to a predetermined offset starting from the start position of the time-domain resources for the first transmission indicated by the first SLIV, the predetermined offset indicating the interval between the time-domain resources of consecutive transmissions, and each of the time-domain resources is associated with one of the two or more TCI states according to a predetermined pattern.

[0220] In addition to the eighth embodiment, according to the tenth embodiment, the processor determines the mapping of the transmission to the time-domain resource during operation, the transmission is mapped to the time-domain resource of two or more TCI states according to a predetermined offset starting from the start position of the time-domain resource for the first transmission indicated by the first SLIV, the predetermined offset indicating the interval between time-domain resources of consecutive transmissions, the time-domain resource to which the transmission is mapped includes available and unavailable time-domain resources, any transmission that counts an unavailable time-domain resource and maps to a time-domain resource having a length indicated by the first SLIV for the first transmission, any transmission that maps to a time-domain resource containing an unavailable time-domain resource is punctured, and each of the time-domain resources is associated with one of the two or more TCI states according to a predetermined pattern.

[0221] In addition to any of the first to ten embodiments, according to the eleventh embodiment, the processor determines the TDRA table from at least two predetermined TDRA tables in accordance with the TCI indicator during operation.

[0222] In addition to any of the first to eleventh embodiments, according to the twelfth embodiment, the transmission is a repetition of the same data portion.

[0223] According to the 13th embodiment, a base station is provided, comprising: a TCI indicator that specifies that two or more TCI (Transmission Configuration Indication) states are set during operation; a processor that generates downlink control information (DCI) signaling indicating time-domain resources for transmission and associations between the two or more TCI states and the time-domain resources, each of which time-domain resources is associated with one of the two or more TCI states; and a transceiver that transmits the DCI signaling during operation and receives or transmits data on the time-domain resources associated with each of the two or more TCI states.

[0224] A 14th embodiment provides a method for a user device (UE) comprising: receiving downlink control information (DCI) signaling; obtaining from the DCI signaling (i) a TCI indicator indicating that two or more TCI (Transmission Configuration Indication) states are set; and (ii) a time-domain resource for transmission and an indication indicating the association of the two or more TCI states with the time-domain resource, wherein each of the time-domain resources is associated with one of the two or more TCI states; and for each of the two or more TCI states, a method is provided for receiving or transmitting data on the time-domain resource associated with each of the TCI states.

[0225] According to the 15th embodiment, a method for a base station is provided, comprising the steps of: (i) generating a TCI indicator that specifies that two or more TCI (Transmission Configuration Indication) states are to be set; and (ii) generating downlink control information (DCI) signaling indicating a time-domain resource for transmission and an association between the two or more TCI states and the time-domain resource, wherein each of the time-domain resources is associated with one of the two or more TCI states; transmitting the DCI signaling; and for each of the two or more TCI states, receiving or transmitting data on the time-domain resource associated with each of the TCI states.

[0226] It should be noted that embodiments 2 through 12 are applicable to the scheduling device of embodiment 13. Furthermore, the steps performed by the circuit during operation correspond to their respective methods, along with the transceiver steps referenced in the above embodiments of the UE and base station.

[0227] Furthermore, a non-temporary medium is provided that stores program instructions that, when executed on a processing circuit such as a general-purpose processor, perform all the steps of any of the embodiments of the method described above.

[0228] In summary, this disclosure relates to a user equipment (UE) and a scheduling node, along with a corresponding method. In particular, downlink control information (DCI) signaling carries a TCI indicator that specifies that two or more TCI (Transmission Configuration Indication) states are set, and an instruction indicating a time-domain resource for transmission and the association of the two or more TCI states with the time-domain resource, each time-domain resource being associated with one of the two or more TCI states, and the transceiver receives or transmits data on the time-domain resource associated with each of the two or more TCI states during operation.

Claims

1. User equipment (UE), A transceiver that receives downlink control information (DCI) signaling, A processor that obtains from the DCI signaling a TCI indicator that specifies that two or more TCI (Transmission Configuration Indication) states are set, a time-domain resource for transmission, and an instruction indicating the association between the two or more TCI states and the time-domain resource, and each of the time-domain resources is associated with one of the two or more TCI states, It has, The transceiver receives or transmits data on the time-domain resource associated with each of the two or more TCI states. The above instruction is an index that indicates entries in the TDRA (Time Domain Resource Assignment) table, The entries in the aforementioned TDRA table are: The starting position of the time-domain resource for the first transmission, the length of the time-domain resource for the first transmission, and information regarding symbols that are not available for the transmission are provided. User device.

2. The start position of the time-domain resource for transmission, which is an entry in the TDRA table, and the length of the time-domain resource for transmission are SLIV (Start and Length Indicator Value), The TDRA table includes two or more sets of the SLIV, Each set corresponds to its respective TCI state. Each SLIV corresponds to its respective transmission. The starting position of the time-domain resource for each of the aforementioned transmissions, wherein the time-domain resource for each of the aforementioned transmissions is associated with the TCI state corresponding to each of the aforementioned sets of SLIVs, The length of the time-domain resource for each of the aforementioned transmissions, A user device according to claim 1, which provides instructions.

3. The user device according to claim 2, wherein the entries in the TDRA table include an indication of the total number of transmissions.

4. The aforementioned processor, For each set containing one SLIV, the start position and length of the time-domain resource for each first transmission are determined according to the SLIV included in the set, and / or User device according to claim 3, for each transmission other than one of the first transmissions, a sequence of TCI states is shown, an association between one of the two or more TCI states and the time domain resource for the transmission according to a pattern corresponding to the start position of the time domain resource for the first transmission, the length of the time domain resource for the transmission by the length of each of the time domain resources for the first transmission, wherein each of the time domain resources for the first transmission and the time domain resource for the transmission are associated with the same TCI state, the length of the time domain resource, and / or the start position of the time domain resource for the transmission by the offset, start position and length of the time domain resource for one of the transmissions preceding the transmission, wherein the offset corresponds to the start position and / or length of at least two time domain resources for the first transmissions.

5. The entries in the aforementioned TDRA table are: The instruction for the total number of transmissions, An offset instruction during the aforementioned transmission, A single SLIV indicating the start position of the time-domain resource for the first transmission and the length of the time-domain resource for the first transmission, A user device according to claim 1, including the following:

6. The aforementioned processor, The start position of the time-domain resource for the first transmission, indicated by the single SLIV for the first transmission, The length of the time-domain resource for the first transmission, as indicated by the length of the single SLIV for the first transmission, and / or For each transmission other than the first transmission, the length of the time-domain resource for the transmission, the start position of the time-domain resource for the transmission, the start position of the time-domain resource for the transmission, the length of the time-domain resource for the first transmission, and the offset, and / or the association of the two or more TCI states with the time-domain resource for the transmission according to a predetermined pattern. A user device according to claim 5, which determines the user device.

7. The processor determines the mapping of the transmission to the time-domain resource, The length of the time-domain resource for each transmission is the same as the length shown for the first transmission. The transmission is mapped to the available time-domain resources of the two or more TCI states according to a predetermined offset starting from the start position of the time-domain resource for the first transmission, the predetermined offset indicating the interval between time-domain resources of consecutive transmissions. The user device according to claim 1, wherein each of the time-domain resources is associated with one of the two or more TCI states according to a predetermined pattern.

8. The processor determines the mapping of the transmission to the time-domain resource, The transmission is mapped to the two or more TCI state time-domain resources according to a predetermined offset starting from the start position of the time-domain resource for the first transmission. The predetermined offset indicates the interval between time-domain resources of consecutive transmissions. The time-domain resource to which the transmission is mapped includes available and unavailable time-domain resources. Any transmission counts an unavailable time-domain resource and maps it to a time-domain resource having a length indicated for the first transmission. Any transmission that maps to a time domain resource containing an unavailable time domain resource is punctured, The user device according to claim 1, wherein each of the time-domain resources is associated with one of the two or more TCI states according to a predetermined pattern.

9. The user device according to claim 1, wherein the processor determines the TDRA table from at least two predetermined TDRA tables according to the TCI indicator.

10. The user device according to claim 1, wherein the transmission is a repetition of the same data portion.

11. A method for user equipment (UE), The steps include receiving downlink control information (DCI) signaling, Steps to obtain from the DCI signaling a TCI indicator that specifies that two or more TCI (Transmission Configuration Indication) states are set, a time-domain resource for transmission, and an instruction indicating the association between the two or more TCI states and the time-domain resource, wherein each of the time-domain resources is associated with one of the two or more TCI states, For each of the two or more TCI states, the steps include receiving or transmitting data on the time-domain resource associated with each TCI state, Includes, The above instruction is an index that indicates entries in the TDRA (Time Domain Resource Assignment) table, The entries in the aforementioned TDRA table are: The starting position of the time-domain resource for the first transmission, the length of the time-domain resource for the first transmission, and information regarding symbols that are not available for the transmission are provided. method.

12. An integrated circuit that controls the processing of a user device (UE), wherein the processing is: The steps include receiving downlink control information (DCI) signaling, Steps to obtain from the DCI signaling a TCI indicator that specifies that two or more TCI (Transmission Configuration Indication) states are set, a time-domain resource for transmission, and an instruction indicating the association between the two or more TCI states and the time-domain resource, wherein each of the time-domain resources is associated with one of the two or more TCI states, For each of the two or more TCI states, the steps include receiving or transmitting data on the time-domain resource associated with each TCI state, Includes, The above instruction is an index that indicates entries in the TDRA (Time Domain Resource Assignment) table, The entries in the aforementioned TDRA table are: The starting position of the time-domain resource for the first transmission, the length of the time-domain resource for the first transmission, and information regarding symbols that are not available for the transmission are provided. Integrated circuit.

Images