Communication device, scheduling node, method and integrated circuit

Abstract

The invention provides a communication device, a scheduling node, a method and an integrated circuit. The communication apparatus includes: a transceiver that receives downlink control information (DCI) signaling; and a processor to obtain a transmission configuration indication (TCI) indicator from the DCI signaling, the TCI indicator specifying that at least two TCI states are configured; wherein an even number of precoding resource block groups (PRGs) is assigned to a first TCI state, and an odd number of PRGs is assigned to a second TCI state.

Description

[0001] This application is a divisional application of the invention patent application filed on August 11, 2020, with application number 202080046093.5 and title "User Equipment and Scheduling Equipment". Technical Field

[0002] This disclosure relates to the transmission and reception of signals in a communication system. Specifically, this disclosure relates to methods and apparatus for such transmission and reception. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) is dedicated to the technical specifications of next-generation cellular technologies, also known as fifth-generation (5G), which include “New Radio” (NR) Radio Access Technology (RAT) operating at frequencies up to 100 GHz. NR is a follower of technologies represented by Long Term Evolution (LTE) and LTE-A Advanced (LTE-A).

[0004] For systems like LTE, LTE-A, and NR, further modifications and options can contribute to the effective operation of the communication system and the specific devices belonging to that system. Summary of the Invention

[0005] A non-limiting and exemplary embodiment helps to make efficient use of resources, including efficient signaling for frequency domain resources of multiple transmit / receive points (TRPs), i.e., for multiple transport configuration indication (TCI) states.

[0006] In embodiments, the technology disclosed herein is characterized by a user equipment (UE) comprising: a transceiver receiving downlink control information (DCI) signaling; and a processor obtaining from the DCI signaling: a TCI indicator specifying that two or more Transmission Configuration Indication (TCI) states are configured; and a frequency domain resource assignment indicating frequency domain resources allocated for the two or more TCI states; determining one or more regions in the frequency domain for each of the two or more TCI states, each region having an integer multiple of precoded resource block groups (PRGs) equal to or greater than 1, wherein the regions of different TCI states do not overlap, and wherein the transceiver receives or transmits data for each TCI state on the frequency domain resources in the determined frequency domain regions.

[0007] In an embodiment, the technology disclosed herein is characterized by a communication device comprising: a transceiver that receives downlink control information (DCI) signaling; and a processor that obtains a transmission configuration indication (TCI) indicator from the DCI signaling, the TCI indicator specifying that at least two TCI states are configured; wherein an even-numbered precoded resource block group (PRG) is assigned to a first TCI state, and an odd-numbered PRG is assigned to a second TCI state.

[0008] In an embodiment, the technology disclosed herein is characterized by a scheduling node comprising: a transceiver that transmits downlink control information (DCI) signaling; and a processor that provides a transmission configuration indication (TCI) indicator in the DCI signaling, the indicator specifying that at least two TCI states are configured; wherein an even-numbered precoded resource block group (PRG) is assigned to a first TCI state, and an odd-numbered PRG is assigned to a second TCI state.

[0009] In an embodiment, the technology disclosed herein is characterized by a method comprising: receiving downlink control information (DCI) signaling; and obtaining a transmission configuration indication (TCI) indicator from the DCI signaling, the indicator specifying that at least two TCI states are configured; wherein an even-numbered precoded resource block group (PRG) is assigned to a first TCI state, and an odd-numbered PRG is assigned to a second TCI state.

[0010] In an embodiment, the technology disclosed herein is characterized by a method comprising: sending downlink control information (DCI) signaling; and providing a transmission configuration indication (TCI) indicator in the DCI signaling, the indicator specifying that at least two TCI states are configured; wherein an even-numbered precoded resource block group (PRG) is assigned to a first TCI state and an odd-numbered PRG is assigned to a second TCI state.

[0011] In an embodiment, the technology disclosed herein is characterized by an integrated circuit comprising a circuit that controls receiving downlink control information (DCI) signaling and controls obtaining a transmission configuration indication (TCI) indicator from the DCI signaling, the indicator specifying that at least two TCI states are configured; wherein an even-numbered precoded resource block group (PRG) is assigned to a first TCI state, and an odd-numbered PRG is assigned to a second TCI state.

[0012] In an embodiment, the technology disclosed herein is characterized by an integrated circuit comprising circuitry that: controls the transmission of downlink control information (DCI) signaling; and controls the provision of a transmission configuration indication (TCI) indicator in the DCI signaling, the indicator specifying that at least two TCI states are configured; wherein an even-numbered precoded resource block group (PRG) is assigned to a first TCI state, and an odd-numbered PRG is assigned to a second TCI state.

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

[0014] Additional benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. Benefits and / or advantages may be obtained individually from the various embodiments and features in the specification and drawings, and it is not necessary to provide all of these embodiments and features to obtain one or more of such benefits and / or advantages. Attached Figure Description

[0015] In the following description, exemplary embodiments will be described in more detail with reference to the accompanying drawings.

[0016] Figure 1 This is a schematic diagram illustrating an exemplary architecture of a 3GPP NR system;

[0017] Figure 2 This is a block diagram illustrating an exemplary user and control plane architecture for LTE eNB, gNB, and UE;

[0018] Figure 3 This is a schematic diagram illustrating the functional division between NG-RAN and 5GC;

[0019] Figure 4 This is a sequence diagram of the RRC connection establishment / reconfiguration procedure;

[0020] Figure 5 This is a schematic diagram illustrating the use cases of enhanced mobile broadband, massive machine-type communication (mMTC), and ultra-reliable and low latency communication (URLLC);

[0021] Figure 6 This is a block diagram illustrating an exemplary 5G system architecture;

[0022] Figure 7 This is a block diagram illustrating user equipment (UE) and scheduling equipment (base station) communicating via a wireless channel;

[0023] Figure 8 This is a block diagram illustrating the functional structure of a user equipment (UE);

[0024] Figure 9 This is a block diagram illustrating the functional structure of network nodes;

[0025] Figure 10 This is a flowchart illustrating an exemplary method performed at the UE;

[0026] Figure 11 This is a flowchart illustrating an exemplary method of communication performed on the UE side and the network side;

[0027] Figure 12 This is a schematic diagram illustrating a first exemplary mapping from a region to a precoded resource group;

[0028] Figure 13 This is a schematic diagram illustrating a second exemplary mapping from a region to a precoded resource group;

[0029] Figure 14 This is a schematic diagram illustrating a third exemplary mapping from a region to a precoded resource group;

[0030] Figure 15 This is a schematic diagram illustrating a fourth exemplary mapping from a region to a precoded resource group;

[0031] Figure 16 This is a schematic diagram illustrating a fifth exemplary mapping from a region to a precoded resource group; and

[0032] Figure 17 This is a schematic diagram illustrating the sixth exemplary mapping from a region to a precoded resource group. Detailed Implementation

[0033] 5G NR System Architecture and Protocol Stack

[0034] 3GPP has been working on the next version of fifth-generation cellular technology (5G), including developing a new radio access technology (NR) that operates at frequencies up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, which allowed for trials and commercial deployment of smartphones compliant with the 5G NR standard.

[0035] Among other things, the overall system architecture assumes the gNB's NG-RAN (Next Generation Radio Access Network) provides the UE with NG-Radio Access User Plane (SDAP / PDCP / RLC / MAC / PHY) and Control Plane (Radio Resource Control, RRC) protocol termination. gNBs interconnect via the Xn interface. gNBs also connect to the NGC (Next Generation Core) via the Next Generation Interface (NG), more specifically, to the AMF (Access and Mobility Management Functions) (e.g., specific core entities performing the AMF) via the NG-C interface, and to the UPF (User Plane Functions) (e.g., specific core entities performing the UPF) via the NG-U interface. The NG-RAN architecture is as follows: Figure 1 As shown (for example, see Section 4 of 3GPP TS38.300v15.6.0).

[0036] It can support a variety of different deployment scenarios (see, for example, 3GPP TR 38.801v14.0.0). For example, it presents a decentralized deployment scenario (see, for example, Section 5.2 of TR 38.801; centralized deployment is described in Section 5.4), in which base stations supporting 5G NR can be deployed. Figure 2 An exemplary decentralized deployment scenario is illustrated (see, for example, TR 38.801). Figure 5 .2.-1), and also shows the LTE eNB and the user equipment (UE) connected to both the gNB and the LTE eNB. The new eNB for NR 5G can be exemplarily referred to as the gNB. The eLTE eNB is an evolution of the eNB that supports connectivity to the EPC (Evolved Packet Core) and NGC (Next Generation Core).

[0037] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, Section 4.4.1) includes PDCP (Packet Data Convergence Protocol, see TS 38.300, Section 6.4), RLC (Radio Link Control, see TS 38.300, Section 6.3), and MAC (Media Access Control, see TS 38.300, Section 6.2) sublayers, which terminate at the network-side gNB. Furthermore, a new Access Layer (AS) sublayer (SDAP, Service Data Adaptation Protocol) is introduced on top of PDCP (see, for example, 3GPP TS 38.300, Subclause 6.5). A control plane protocol stack is also defined for NR (see, for example, TS 38.300, Section 4.4.2). Subclause 6 of TS 38.300 provides an overview of Layer 2 functions. Sections 6.4, 6.3, and 6.2 of TS 38.300 list the functions of the PDCP, RLC, and MAC sublayers, respectively. The functions of the RRC layer are listed in subclause 7 of TS 38.300.

[0038] For example, the media access control layer handles logical channel multiplexing, as well as scheduling and scheduling-related functions, including handling different sets of parameters (numerologies).

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

[0040] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), and massive machine-type communication (mMTC), each with different requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20Gbps for downlink and 10Gbps for uplink) and approximately three times the user experience data rate offered by IMT-Advanced. On the other hand, in the case of URLLC, ultra-low latency (0.5ms for both UL and DL) and high reliability (1-10 within 1ms) are crucial. -5 This places even stricter requirements on mMTC. Ultimately, mMTC may best require high connection density (1,000,000 devices / km in urban environments). 2 ), wide coverage in harsh environments, and ultra-long-life batteries (15 years) for low-cost devices.

[0041] Therefore, an OFDM parameter set suitable for one use case (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) may not be suitable for another use case. For example, low latency services may preferably require shorter symbol durations (and therefore larger subcarrier spacing) and / or fewer symbols per scheduling interval (also known as TTI) compared to mMTC services. Furthermore, deployment scenarios with large channel latency spreads may preferably require longer CP durations compared to scenarios with short latency spreads. Subcarrier spacing should be optimized accordingly to maintain similar CP overhead. NR can support more than one value for subcarrier spacing. Accordingly, subcarrier spacings of 15kHz, 30kHz, 60kHz… are currently being considered. Symbol duration T u The subcarrier spacing Δf is obtained through the formula Δf = 1 / T u Directly related. In a similar manner to LTE, the term "resource element" can be used to denote the smallest resource unit, which consists of a subcarrier of one OFDM / SC-FDMA symbol length.

[0042] In the new 5G-NR radio system, for each parameter set and carrier, resource grids for subcarriers and OFDM symbols are defined for both 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.211v15.6.0).

[0043] 5G NR Function Division between NG-RAN and 5GC

[0044] Figure 3 The functional partitioning between NG-RAN and 5GC is illustrated. NG-RAN logical nodes are either gNBs or ng-eNBs. 5GC has logical nodes AMF, UPF, and SMF.

[0045] Specifically, gNB and ng-eNB host the following main functions:

[0046] - Functions for radio resource management, such as radio bearer control, radio access control, connection mobility control, and dynamic communication to the UE in both uplink and downlink.

[0047] Allocate resources (schedule);

[0048] - Data IP header compression, encryption, and integrity protection;

[0049] - When the route to the AMF cannot be determined based on the information provided by the UE, the selection of the AMF is made at the UE attachment.

[0050] - Routing user plane data to UPF;

[0051] - Routing control plane information to AMF;

[0052] - Connection establishment and release;

[0053] - Scheduling and transmission of paging messages;

[0054] - Scheduling and transmission of system broadcast information (originating from AMF or OAM);

[0055] - Mobility and scheduling measurement and measurement reporting configuration;

[0056] -Transmission class grouping markers in the uplink;

[0057] -Session management;

[0058] -Support for network slicing;

[0059] - QoS flow management and mapping to data radio carriers;

[0060] - Supports UEs in the RRC_INACTIVE state;

[0061] -NAS message distribution functionality;

[0062] - Radio access network sharing;

[0063] - Dual connectivity;

[0064] -Close interoperability between NR and E-UTRA.

[0065] The Access and Mobility Management (AMF) function performs the following main functions:

[0066] - Non-Access Stratum (NAS) signaling termination;

[0067] -NAS signaling security;

[0068] - Access Layer (AS) security controls;

[0069] - Core network inter-network (CN) node signaling for mobility between 3GPP access networks;

[0070] - Idle mode UE reachability (including paging retransmission control and execution);

[0071] -Registration area management;

[0072] -Supports mobility within and between systems;

[0073] -Access authentication;

[0074] - Access authorization, including checking roaming permissions;

[0075] - Mobility management controls (subscriptions and policies);

[0076] -Support for network slicing;

[0077] - Session Management Function (SMF) selection.

[0078] In addition, the User Plane Function (UPF) performs the following main functions:

[0079] - Anchor points for movement within / between RATs (where applicable);

[0080] - External PDU session points for interconnection to the data network;

[0081] - Packet routing and forwarding;

[0082] - Group checks and user plane components for policy rule enforcement;

[0083] - Traffic usage report;

[0084] - Supports uplink classifiers that route traffic flows to the data network;

[0085] -Supports branch points for multi-homed PDU sessions;

[0086] - QoS processing in the user plane, such as packet filtering, gating, and UL / DL rate implementation;

[0087] - Uplink traffic verification (SDF to QoS flow mapping);

[0088] - Downlink packet buffering and downlink data notification triggering.

[0089] Finally, the Session Management Function (SMF) carries out the following main functions:

[0090] -Session management;

[0091] -UE IP address allocation and management;

[0092] -Selection and control of UP function;

[0093] - Configure traffic steering in the User Plane Function (UPF) to route traffic to the correct destination;

[0094] - The control section for QoS and policy enforcement;

[0095] - Downlink data notification.

[0096] RRC connection establishment and reconfiguration procedure

[0097] Figure 4 This illustrates some interactions between the UE, gNB, and AMF (5GC entity) in the context of the UE transitioning from RRC_IDLE to RRC_CONNECTED for the NAS section (see TS 38.300v15.6.0).

[0098] RRC is a higher-layer signaling (protocol) used for UE and gNB configuration. Specifically, this transition involves: the AMF preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sending it to the gNB along with an Initial Context Setup Request. The gNB then activates AS security with the UE, which is performed by the gNB sending a SecurityModeCommand message to the UE, and the UE responding to the gNB with a SecurityModeComplete message. Afterwards, the gNB performs reconfiguration by sending an RRCReconfiguration message to the UE, and in response, receiving an RRCReconfigurationComplete message from the UE, to establish Signalling Radio Carrier 2 (SRB2) and Data Radio Carrier (DRB). For signaling-only connections, the steps related to RRCReconfiguration are skipped because SRB2 and DRB are not established. Finally, gNB notifies AMF that the setup process is complete with an Initial Context Set Response (INITIAL CONTEXT SETUPRESPONSE).

[0099] Therefore, this disclosure provides an entity for a fifth-generation core (5GC) (e.g., AMF, SMF, etc.), comprising: a control circuit that establishes a next-generation (NG) connection with a gNodeB (or gNB); and a transceiver that sends an initial context establishment message to the gNodeB via the NG connection to obtain the establishment of a signaling radio carrier between the gNodeB and the user equipment (UE). Specifically, the gNodeB sends radio resource control (RRC) signaling containing resource allocation configuration information elements to the UE via the signaling radio carrier. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0100] For IMT use cases in 2020 and beyond

[0101] Figure 5 Some use cases for 5G NR are shown. In the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases are being considered, envisioned to support a wide variety of services and applications for IMT-2020. The first phase of specifications for Enhanced Mobile Broadband (eMMB) has been completed. In addition to further expanding eMMB support, current and future work will involve the standardization of Ultra-Reliable and Low Latency Communication (URLLC) and Massive Machine-Type Communication. Figure 5Examples of envisioned use cases for IMT in 2020 and beyond are shown.

[0102] URLLC use cases have stringent requirements for capabilities such as throughput, latency, and availability, and are envisioned as one of the enablers for future vertical applications such as wireless control of industrial manufacturing or production processes, telemedicine surgery, distribution automation in smart grids, and transportation security. Ultra-reliability for URLLC is supported by identifying technologies that meet the requirements set forth in TR 38.913. For NR URLLC in Release 15, key requirements include a target user plane latency of 0.5 ms for UL (uplink) and 0.5 ms for DL ​​(downlink). A typical URLLC requirement for a single packet transmission is a user plane latency of 1 ms for a BLER (Block Error Rate) of 1E-5 with a packet size of 32 bytes.

[0103] From RAN1's ​​perspective, reliability can be improved in several ways. Current methods for improving reliability include defining a separate CQI table for URLLC, a more compact DCI format, and PDCCH repetition. However, as NR becomes more stable and evolves, the scope for achieving ultra-reliability may expand (for NR's critical requirements). Specific use cases for NRURLCC in Rel.15 include augmented reality / virtual reality (AR / VR), eHealth, eSafety, and mission-critical applications.

[0104] Furthermore, the technical enhancements targeted by NRURLCC aim to improve latency and reliability. Enhancements for latency improvement include configurable parameter sets, slotless scheduling with flexible mapping, unlicensed (configured licensed) uplinks, slot-level repetition for data channels, and downlink pre-emption. Pre-emption means that a transmission that has already been allocated resources is stopped, and the allocated resources are used for another transmission that is requested later but has a lower latency / higher priority requirement. Therefore, a licensed transmission is pre-empted by a subsequent transmission. Pre-emption applies independently of a specific service type. For example, a transmission of service type A (URLCC) may be pre-empted by a transmission of service type B (such as eMMB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table for the target BLER of 1E-5.

[0105] The use cases for mMTC (massive machine-type communication) are characterized by a large number of connected devices typically sending relatively small amounts of non-latency-sensitive data. Device requirements include low cost and long battery life. From NR's perspective, utilizing a very narrow bandwidth segment is a possible solution, which, from the user equipment's perspective, can save power and extend battery life.

[0106] As mentioned above, the reliability range of NR is expected to become broader. A key requirement, essential for all cases and especially for URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can be considered to improve reliability from both radio and network perspectives. Generally, there are a few key potential areas that can help improve reliability. These areas include compact control channel information, data / control channel repetition, and diversity in the frequency, time, and / or spatial domains. These areas generally apply to reliability regardless of the specific communication scenario.

[0107] For NR URLLC, further use cases with more stringent requirements have been identified, such as factory automation, the transportation industry, and power distribution. These more stringent requirements include higher reliability (up to 10⁻⁶), higher availability, packet sizes up to 256 bytes, and time synchronization as low as approximately a few μs, where this value can be one or several μs depending on the frequency range and short latency of approximately 0.5 to 1 ms, particularly a target user plane latency of 0.5 ms, depending on the use case.

[0108] Furthermore, for NR URLCC, several technical enhancements have been identified from the RAN1 perspective. These include PDCCH enhancements related to compact DCI, PDCCH (Physical Downlink Control Channel) repetition, and increased PDCCH monitoring. Additionally, UCI (Uplink Control Information) enhancements are associated with enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. PUSCH enhancements related to mini-slot-level hops and retransmission / repetition enhancements have also been identified. The term "mini-slot" refers to a Transmission Time Interval (TTI) that includes fewer symbols than a slot (which may contain 14 or 12 symbols).

[0109] In slot-based scheduling or assignment, a slot corresponds to the timing granularity (TTI - Transmission Time Interval) used for scheduling assignment. Generally, the TTI determines the timing granularity used for scheduling assignment. A TTI is the time interval during which a given signal is mapped to the physical layer. For example, conventionally, the TTI length can vary 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 consisting of 10 subframes (1ms duration) (10ms duration). In slot-based transmission, subframes are further divided into slots, the number of which is defined by a parameter set / subcarrier spacing. Specified values ​​range from 10 slots per frame (1 slot per subframe) for a 15kHz subcarrier spacing to 80 slots per frame (8 slots per subframe) for a 120kHz subcarrier spacing. For a normal cyclic prefix, the number of OFDM symbols per time slot is 14, and for an extended cyclic prefix, the number of OFDM symbols per time slot is 12 (see Sections 4.1 (General Frame Structure), 4.2 (Parameter Set), 4.3.1 (Frames and Subframes), and 4.3.2 (Time Slots) of 3GPP TS 38.211 V15.3.0 (Physical Channels and Modulation, 2018-09). However, the allocation of time resources for transmission can also be based on non-time slots. In particular, the TTI in a non-time slot-based allocation can correspond to a micro-time slot instead of a time slot. That is, one or more micro-time slots can be assigned to the requested data / control signaling transmission. In a non-time slot-based allocation, the minimum length of the TTI can be, for example, 1 or 2 OFDM symbols.

[0110] QoS control

[0111] The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows requiring guaranteed flow bit rates (GBRQoS flows) and QoS flows not requiring guaranteed flow bit rates (non-GBR QoS flows). Therefore, at the NAS level, QoS flows represent the finest granularity of QoS differentiation within a PDU session. Within a PDU session, QoS flows are identified by the QoS Flow ID (QFI) carried in the encapsulation header on the NG-U interface.

[0112] For each UE, 5GC establishes one or more PDU sessions. For each UE, NG-RAN establishes at least one Data Radio Carrier (DRB) and PDU session, and additional DRBs for the QoS flows of that PDU session can subsequently be configured (when to do so depends on NG-RAN), for example, as referenced above. Figure 4As shown, NG-RAN maps packets belonging to different PDU sessions to different DRBs. The NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while the AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0113] Figure 6 A 5G NR non-roaming reference architecture is shown (see Section 4.23 of TS23.501v16.1.0). Application functions (AFs), such as bearer functions, are also included. Figure 5 The external application server for the 5G services exemplified in the example interacts with the 3GPP core network to provide services, such as supporting the application's influence on service routing, access network exposure functions (NEF), or interacting with the policy framework for policy control (see Policy Control Function (PCF)), such as QoS control. Based on operator deployment, application functions considered trusted by the operator may be allowed to interact directly with the relevant network functions. Application functions that the operator does not allow to directly access network functions may interact with the relevant network functions via the external exposure framework through the NEF.

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

[0115] In LTE and NR, a terminal or user device is referred to as a User Equipment (UE). This can be a mobile device or communication device, such as a cordless phone, smartphone, tablet, or a USB (Universal Serial Bus) stick with UE functionality. However, the term mobile device is not limited to this; generally, a repeater can also have the functionality of such a mobile device, and a mobile device can also function as a repeater.

[0116] A base station is a network node, for example, part of a network used to provide services to terminals. A base station is a network node or scheduling device that provides radio access to terminals. Communication between terminals and base stations is typically standardized. In LTE and NR, the radio interface protocol stack includes the physical layer, the media access layer (MAC), and higher layers. In the control plane, higher-layer protocols, such as the Radio Resource Control (RRC), are provided. Through RRC, the base station can control the configuration of the terminal, and the terminal can communicate with the base station to perform control tasks (such as connection and carrier establishment, modification, etc.), measurements, and other functions. The term used in LTE is eNB (or eNodeB), while the term currently used in 5G NR is gNB.

[0117] The data transfer service provided from one layer to a higher layer is usually referred to as 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.

[0118] Logical channels are different types of data transmission services provided by the MAC (Machine Interface). Each logical channel type is defined by the type of information being transmitted. Logical channels are divided into two groups: control channels and traffic channels. Control channels are used only to transmit control plane information. Traffic channels are used only to transmit user plane information.

[0119] Then, logical channels are mapped to transport channels by the MAC layer. For example, logical traffic channels and some logical control channels can be mapped to transport channels called the Downlink Shared Channel (DL-SCH) in the downlink, and to transport channels called the Uplink Shared Channel (UL-SCH) in the uplink.

[0120] Downlink Control Channel Monitoring (PDCCH, DCI)

[0121] Many functions operated by the user equipment involve monitoring the downlink control channel (e.g., PDCCH, see 3GPTS 38.300v15.6.0, Section 5.2.3) to receive, for example, specific control information or data destined for the UE.

[0122] As described above, PDCCH monitoring is performed by the UE in order to identify and receive information intended for the UE, such as control information and user traffic (e.g., DCI on the PDCCH and user data on the PDSCH indicated by the PDCCH).

[0123] Downlink control information (which may be referred to as downlink control information, DCI) in 5G NR serves the same purpose as DCI in LTE, namely, as a special set of control information for scheduling, for example, downlink data channels (e.g., PDSCH) or uplink data channels (e.g., PUSCH). In 5G NR, there are many different DCI formats that have been defined (see Section 7.3.1 of TS 38.212v15.6.0).

[0124] PDCCH monitoring for each of these functions serves a specific purpose and thus begins to achieve that purpose. PDCCH monitoring is typically operated by the UE and controlled, at least based on a timer. The purpose of the timer is to control PDCCH monitoring, for example, to limit the maximum amount of time the UE can monitor the PDCCH. For example, the UE may not need to monitor the PDCCH indefinitely, but can stop monitoring after a period of time to save power.

[0125] As mentioned above, one of the purposes of the DCI in PDCCH is to dynamically schedule resources in the downlink, uplink, or even sidelink. Specifically, some formats of the DCI are provided to carry indications (resource allocations, RAs) of the resources allocated to a particular user's data channel. Resource allocations may include the specification of resources in the frequency domain and / or time domain.

[0126] Resource allocation

[0127] In NR version 15, two types of frequency domain resource allocation schemes are used, type 0 and type 1, both of which send signaling notifications for allocation across the active bandwidth portion (BWP).

[0128] Type 0 is a bitmap-based allocation scheme. The most flexible way to indicate the set of resource blocks to be allocated is to include a bitmap of size equal to the number of resource blocks in the BWP. A resource block corresponds to the smallest allocatable unit for data transmission and is defined by the number of subcarriers in the frequency. (Note that the NR definition of a resource block differs from the LTE definition. An NR physical resource block is a one-dimensional measurement spanning only the frequency domain, while LTE uses a two-dimensional resource block with 12 subcarriers in the frequency and one time slot in the time). This allows arbitrary combinations of resource blocks to be scheduled for transmission, but unfortunately, it also results in very large bitmaps for larger bandwidths. Therefore, the bitmap in a Type 0 resource allocation scheme is not used to point to a single resource block, but rather to a contiguous group of resource blocks called an RBG. The size of the RBG depends on the size of the active BWP. For example, as defined in 3GPP TS38.214 V15.4.0 and summarized in Table 1, two different configurations are possible for each size of the BWP.

[0129] Bandwidth portion size Configuration 1 Configuration 2 1–36 2 4 37–72 4 8 73–144 8 16 145–275 16 16

[0130] Table 1

[0131] For example, as shown in Table 1, when application configuration 1 is used, the RBG allocated according to type 0 (where the bandwidth size of the BWP corresponds to the number of RBs from 1 to 36) contains 2 RBs. Therefore, for example, when application configuration 2 is used, the RBG allocated according to type 0 (where the BWP size corresponds to the number of RBs from 73 to 144) contains 16 RBs. That is, the number of RBs in an RBG depends on the bandwidth of the active BWP.

[0132] Type 1 resource allocation schemes do not rely on bitmaps. Instead, they use Resource Indicator Values ​​(RIVs) that encode resource allocations as the start position and length of the allocation based on the number of resource blocks. Therefore, they do not support arbitrary allocation of resource blocks, but only frequency-continuous allocation, thus reducing the number of bits required to signal resource block allocations.

[0133] Both resource allocation types refer to Virtual Resource Blocks (VRBs). For Type 0, a non-interleaved mapping from virtual to physical resource blocks is used, meaning that virtual resource blocks are directly mapped to their corresponding physical resource blocks. On the other hand, for the Type 1 resource allocation scheme, UL supports non-interleaved mapping. For DL, the Type 1 resource allocation scheme supports both interleaved and non-interleaved mapping, where the interleaving size is the bandwidth of the active BWP.

[0134] In the time domain, for example, as specified in Version 15 (NR), scheduling timing (e.g., for scheduling of the aforementioned resources) can be indicated within the DCI using a Time Domain Resource Allocation (TDRA) table. Specifically, the resources allocated in the time domain can be notified to the UE by indicating an entry (row) of the TDRA table in the DCI, for example, by signaling the entry (row) index. The terminology is used herein as logical terminology because, for NR, TDRA entries are summarized as tables in the standard specification.

[0135] Repeats on PDSCH and PUSCH

[0136] Transmissions in NR can include spontaneous (i.e., not triggered by (H)ARQ) repetition of data. In this case, the same data (e.g., a transport block) is sent N times, where N is an integer greater than 1. The number of repetitions can be configured.

[0137] Multiple send / receive points, TRP

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

[0139] The techniques described in this disclosure are not limited to a specific arrangement of the TRP or a specific relationship between the TRP and the gNB. Thus, for example, multi-TRP operation can be performed by a gNB having different antenna panels or radio heads corresponding to the TRP and different radio frequency units operating with the corresponding antennas.

[0140] Furthermore, in a multi-TRP configuration, several options can be considered regarding the positional relationship between TRPs, and the distance between two TRPs can vary. For example, TRPs may be very close, so the UE receives signals from these TRPs from similar angles. However, TRPs may also be far apart, for example, in remote locations within the network cell. A UE served by two TRPs can receive signaling from and send signaling to the corresponding TRP on unrelated channels. Therefore, the gain from channel diversity can be optimally utilized.

[0141] For example, multiple TRPs can be divided into two high-level categories. That is, the categories can be distinguished based on the return type of the return link between two given TRPs.

[0142] On the one hand, an ideal backhaul is a backhaul with very high throughput and very low latency, such as a dedicated point-to-point connection using, for example, fiber optic cables. It is assumed that an ideal backhaul allows communication between TRPs to have a latency of approximately or almost 0 ms (e.g., for LTE-A, technical report 3GPP TR 36.932 V15.0.0 (2018-06) mentions a one-way latency of less than 2.5 μs in section 6.1.3, however, this does not include propagation delay in fiber optic cables).

[0143] On the other hand, non-ideal backhaul is backhaul such as DSL, microwave and other similar relays, and can, for example, involve finite (one-way) delays in the range of 2ms or 5ms for communication between two given TRPs.

[0144] In addition to classifying backhaul as ideal and non-ideal, a further classification in multi-TRP MIMO technology could be about how the (central) baseband unit is shared among TRPs.

[0145] For example, although each of two given TRPs has a different RF (radio frequency) unit, the TRPs can share the same baseband unit. The link between the RF unit and the baseband unit can be ideal or non-ideal. Alternatively, each TRP can have both a different (central) baseband unit and a different RF unit. The corresponding links between the baseband unit and the RF unit, as well as the links between different baseband units, can be ideal or non-ideal.

[0146] This disclosure provides methods that can facilitate multi-TRP operations and can particularly facilitate the scheduling of frequency domain resources used in multi-TRP operations. For example, the disclosed techniques can facilitate URLLC use cases, but can also, or alternatively, facilitate eMBB and mMTC use cases. This disclosure is applicable to scenarios including one or both of ideal and non-ideal backhaul.

[0147] As mentioned above, multiple widely spaced TRPs can allow for spatial diversity gain. Utilizing this spatial diversity gain can be particularly helpful for transmission and reception in the high-frequency range, where congestion of any link or wireless communication channel between the TRP and the UE is especially possible.

[0148] Recently, it has been discussed to use single-DCI-based scheduling from one of two TRPs to schedule the same transport block (TB) from both TRPs in corresponding non-overlapping frequency regions and on the same time symbols. A transport block represents a data unit passed to the physical layer for transmission.

[0149] It should be understood that each TRP transmission (i.e., a transmission from a TRP) in the corresponding non-overlapping frequency region can be associated with a separate TCI state. In particular, each TRP can be associated with a separate TCI state. Therefore, the terms "TCI state" and "TRP" are used interchangeably—for example, TCI state 1 will refer to TRP1, TCI state 2 will refer to TRP2, and so on.

[0150] Support for different MCSs for transmitting the same TB from different TRPs is being considered, depending on the corresponding channel conditions from each TRP to the UE. Using different MCSs could potentially be advantageous if frequency bands of unequal size from the two TRPs are used. Ideal backhaul between multiple TRPs can be considered. However, these are merely some optional deployment scenarios, and this disclosure is not limited thereto.

[0151] For example, in order to schedule the same TB of PDSCH via a single DCI from one of the TRPs and reuse them in two non-overlapping frequency regions belonging to multiple different TRPs, the inventors recognized the following problems, and this disclosure solves these problems. The first problem is how to distribute and indicate multiple non-overlapping frequency regions using scheduling based on a single DCI. The second problem is how to associate the distributed non-overlapping frequency regions with the indicated TCI status. Furthermore, several other optimizations and improvements can be provided to improve the efficiency and / or scalability of resource signaling.

[0152] To address some of the aforementioned issues, according to an embodiment, physical resource blocks in the frequency domain are assigned to regions. Each region is defined as a multiple of precoded resource block groups (PRGs). Each region is associated with a transmission corresponding to a specific TCI state.

[0153] Here, each TCI state (TRP) is associated with one or more regions. Each region is associated with only one TCI state, and these regions do not overlap. A precoded block group is a group of (physical) resource blocks that share the same precoded data. For example, a precoded resource block group applies the same precoded matrix.

[0154] One advantage of defining regions in multiples of PRGs and assigning them to different TRPs is that it allows for separate precoding of each TRP transport. This approach works for both resource allocation types 0 and 1 without affecting the respective schemes.

[0155] This example mentions sending the same TB via multiple TRPs (with multiple TCI states). However, this disclosure is not limited to this, and generally, this scheme can also be applied to the transmission of different TBs via different corresponding TCI states. Furthermore, for simplicity, an example with two TRPs is shown below. However, the scheme discussed here applies to more than two TRPs.

[0156] This disclosure provides exemplary embodiments including devices and methods. For example, Figure 7An exemplary user equipment (UE) 760 is illustrated, including transceiver 770, which receives downlink control information (DCI) via channel 750 (shown by dashed lines). The UE (corresponding to a terminal, or generally, a scheduled device) 760 also includes circuitry 780. This circuitry is processing circuitry (processor) and may be implemented on one or more chips and other electronic components. The term "processor" should be understood as functional and may include one or more general-purpose processors, digital signal processors, programmable hardware, and / or special-purpose hardware. Circuitry (processor) 780 obtains from the DCI signaling a Transport Configuration Indicator (TCI) indicator specifying that two or more TCI states are configured and a frequency domain resource assignment for the frequency domain resources allocated to the two or more TCI states.

[0157] For example, transceiver 770 performs blind decoding of the PDCCH to identify whether a DCI is directed to UE 760. If a DCI for the UE exists, processor 780 parses (extracts) various signaling parameters from the DCI based on its syntax and semantics known at the UE and at the scheduling device 710 that generated the DCI. The syntax and semantics can be defined by standards such as NR or other standards. The syntax and semantics of the DCI can also be configured, in whole or in part, via higher-layer signaling. Generally, a DCI may include one or more bit fields, each containing one or more bits. Typically, the number of bits per field is statically configured (by standards or network operators) or semi-statically configured (by higher-layer signaling, such as RRC). A bit field may indicate a single transmission parameter or several jointly encoded transmission parameters.

[0158] For example, the TCI indicator mentioned above could be a single bit (a one-bit field of one-bit length) indicating whether one or two TCI states are to be applied, or in other words, whether one or two TRPs are to be used for scheduled transmission (uplink) or reception (downlink). However, this exemplary implementation is only applicable to cases where a maximum of two TRPs are used simultaneously. This disclosure is not limited to this implementation. In other exemplary implementations, the TCI indicator could be carried by a separate DCI field dedicated to the TCI indicator, which has more than one bit. In particular, such a TCI indicator could signal how many TCI states (TRPs) are active for scheduled transmission or reception.

[0159] Here, it is assumed that the network provides one or more TRPs; therefore, the TCI indicator specifies how many TRPs are active for the UE 760's transmission or reception. Different TRPs can reside in the same base station or different base stations. Even though it is easier to implement more TRPs on the network side, which generally has greater processing power, especially when the network side consists of one or more base stations or network nodes, in some scenarios, the terminal (UE) can also benefit from employing more than one TRP. In this case, the embodiments and examples shown herein are also applicable. For example, alternatively, or in addition to signaling to the scheduling device 710 how many TRPs to employ, the DCI can also signal to the UE 760 the number of TRPs to employ. The term "scheduling device" in this disclosure is used interchangeably with the term base station and refers to a network node with scheduling capabilities that serves the UE as an access point to the network. Note that a scheduling device, such as a base station, schedules multiple active TRPs regardless of whether the TRPs are actually located at / terminated at the scheduling device.

[0160] Generally, the TCI indicator does not need to be indicated as a separate bit field. It can be indicated in conjunction with another parameter or other parameters. In other words, one or more code points of such a combined bit field can indicate the use of one TRP, while one or more other code points can indicate the use of two TRPs. Similarly, any number of TRPs can be signaled by one or more code points of a combined bit field carrying such a TCI indicator.

[0161] As described above, this disclosure provides specific frequency domain resource assignment and signaling for situations where the TCI indicator specifies that two or more TCI states are configured. The DCI also carries frequency domain resource assignments, which indicate the frequency domain resources allocated to the two or more TCI states. The frequency domain resource assignments may be provided in a separate (dedicated) DCI bit field, or they may be jointly encoded with the TCI indicator and / or one or more other transmission parameters.

[0162] Generally, joint encoding can provide greater efficiency in utilizing the bits available in the DCI. To provide fast scheduling, the number of parameters and the length of the DCI can be kept as low as possible. On the other hand, in some cases, encoding in separate fields can provide backward compatibility. Joint encoding can be implemented, for example, by sending an index of a signaling notification table in the joint bit field, which includes a specific combination of parameter values ​​for each index, with the parameters corresponding to columns in the table. Examples of such tables are, for example, the TDRA table mentioned above, or the MCS table.

[0163] Circuit 780 also determines one or more regions in the frequency domain for each of two or more TCI states. Each region has an integer multiple of precoded resource block groups (PRGs). Integers are equal to or greater than 1. In other words, each region can consist of (constitute) one or more PRGs. This determination can be performed based on the frequency domain resource assignment notified by signaling, for example, if the regions of two or more TCI states are located within the frequency domain resources specified by the frequency domain resource assignment.

[0164] As stated above, regions belonging to different TCI states do not overlap. In other words, the regions are frequency division multiplexed (FDM). In some embodiments, no regions overlap (not only those belonging to different TCI states).

[0165] Circuit 780 can implement more functions than the aforementioned determination of transmit / receive frequency domain resources using more than one TRP. Therefore, circuit 780 is considered to include frequency resource determination circuit 785, which is configured to perform frequency domain resource determination. This configuration can be provided through hardware adaptation and / or software.

[0166] Figure 8 The functional structure of the frequency resource determination circuit 785 is illustrated. Specifically, the frequency resource determination circuit 785 includes a PDCCH processing circuit 870, which extracts the TCI indicator and frequency domain assignment from the DCI. The frequency resource determination circuit 785 also includes a frequency resource control circuit 880, which determines a region based on the assignment when the TCI indicator indicates two or more TCI states, and determines the assignment of frequency resources to each TCI state based on the region. The processing circuit can then control the transceiver 770 to receive or transmit data on the determined resources.

[0167] After determining the region, transceiver 770 receives data for each TCI state on the frequency domain resources within the determined frequency domain region. This applies to downlink cases where the DCI is a downlink resource scheduled by the UE to receive data. For uplink cases, transceiver 770 transmits data for each TCI state on the frequency domain resources within the determined frequency domain region. Depending on whether the received DCI is a downlink-scheduled DCI or an uplink-scheduled DCI, a single UE can have a transceiver that is both a receiver and a transmitter, receiving and transmitting data from / to multiple TRPs.

[0168] Corresponding to UE 760, Figure 7A scheduling node 710 is shown. In the case of 5G-NR, the scheduling device can be any network access node, such as a base station or gNB. According to an embodiment, the scheduling device 710 includes a transceiver 720 that transmits downlink control information (DCI) signaling. The transceiver 720 may have more than one antenna (e.g., an antenna panel) to provide one or more TRPs. However, the TRPs may also be provided by multiple different network nodes. As mentioned above, the UE 760 may also provide more than one TRP, therefore the transceiver 770 of the UE 760 may also include more than one antenna (antenna panel). The DCI can be syntactically and semantically corresponding to the DCI described above to enable communication between the scheduling device 710 and the UE 760.

[0169] The scheduling device 710 also includes a processor 730, which provides DCI signaling including a Transport Configuration Indicator (TCI) indicator specifying that two or more TCI states are configured and a frequency domain resource assignment indicating the frequency domain resources allocated to the two or more TCI states. The aforementioned signaling possibilities are applied to both the TCI indicator and the frequency domain resource assignment. The processor 730 also determines one or more regions in the frequency domain for each of the two or more TCI states, each region having an integer multiple of precoded resource block groups (PRGs) equal to or greater than 1, wherein the regions for different TCI states do not overlap. Therefore, the transceiver 720 transmits (in the case of downlink) or receives (in the case of uplink) data for each TCI state on the frequency domain resources in the determined frequency domain regions. Similar to the processor 780 in the UE, the processor 730 can also perform a variety of different tasks. Here, the frequency resource allocation circuit 735 represents the functional part of the processor 730, which performs the aforementioned frequency domain allocation task, including determining resources and providing corresponding signaling to the UE 760.

[0170] The scheduling device may also include an allocation circuit, as part of circuit 730, which performs scheduling for one or more UEs. As a result of the scheduling, frequency domain resource assignments are generated, and corresponding DCI signaling is generated, indicating the TCI indicator and the assignment. The circuit then controls transceiver 720 to transmit or receive data in the resources scheduled for one or more UEs.

[0171] Figure 9An exemplary functional structure of the frequency resource allocation circuit 735 is illustrated. Specifically, the frequency resource allocation circuit 735 may include a scheduling circuit 920 and a PDCCH generation circuit 930. The scheduling circuit 920 performs scheduling, for example, collecting measurements from one or more UEs and, based on these measurements, and based on requests from the UEs and / or the availability of their resources, assigning resources to the respective UEs in the frequency domain (and possibly in the time domain, and in the TRP). The PDCCH generation circuit 930 then generates a DCI including a TCI indicator and resource assignments based on the scheduling results for the respective one or more UEs.

[0172] like Figure 7 As shown, UE 760 and scheduling node 710 can form a communication system, that is, they can communicate through channel 750.

[0173] Various embodiments regarding regions are described below. In particular, one or more of the following configurations can be considered to define regions:

[0174] a) Number of regions: The number of regions within the allocated frequency resources.

[0175] b) Region assignment: Assigning regions to physical layer resources (mesh), such as precoded resource block groups.

[0176] c) Region size: The region size is expressed in multiples of PRGs, and

[0177] d) Region association: Assign each region to a TRP (TCI state).

[0178] The four configurations a) to d) above can be configured and / or indicated in different ways.

[0179] Note that a region can only be configured and utilized if the code point of the bit field indicated by the TCI indicates more than one TCI state. However, this disclosure is not limited to this, and the concept of resource assignment can also be used in the case of a single TRP.

[0180] In NR, Rel.16 has agreed to use code points of the TCI bit field to indicate two TCI states (instead of one TCI state in Rel.15), which essentially means that two TRP transfers are possible.

[0181] A. Determine the number of areas

[0182] According to the first example, processor 770 (and corresponding processor 730) determines the number (quantity) of regions based on the maximum number of TCI states, which is configured as semi-statically as possible to be indicated by a TCI of the DCI.

[0183] In other words, the UE determines the number of regions in a semi-static manner based on the maximum number of TCI states that are semi-statically configured to be indicated by an index of TCI signaling.

[0184] Specifically, base station 710 can semi-statically configure the DCI by sending an RRC message to UE 760, which indicates how many TCI states can be dynamically configured. For example, the maximum number of TCI states that the RRC message can signal is 1. In this case, the DCI only includes frequency resources for a single TCI state (single TRP). For example, the maximum number of TCI states that the RRC message can signal is 2. In this case, the TCI indicator can signal 1 or 2 TCI states to be applied to the transmission / reception of data scheduled in the same DCI. For example, the maximum number of TCI states that the RRC message can signal is 3 or more. In this case, the DCI can dynamically signal any number of 1, 2, 3, ... up to the maximum value of the TCI states configured by the RRC.

[0185] Then, based on the TCI indicator, the resource assignment carried in the DCI is interpreted as frequency resources covering the indicated number of TCI states. For example, when the maximum number of TCI states is 1, the entire allocated resource indicated by the frequency resource assignment belongs to the transmit / receive using one TCI state. When the maximum number of TCI states is 2, there will be at least two distinct regions. Generally, there will be two superregions for the corresponding two TCI states. Each superregion may include multiple regions and may be contiguous or discontinuous in the frequency domain, as will be shown later.

[0186] Determining the number of regions semi-statically may help reduce complexity, as it does not have to be determined dynamically.

[0187] However, according to the second example, processor 770 determines the number of regions based on the maximum number of TCI states indicated by the TCI indicator. Accordingly, processor 730 of the base station determines the number of regions that meet the maximum number of TCI states indicated by the TCI indicator. The regions, their number, size, location relative to physical resources, and their assignment to the corresponding TCI states can be determined by scheduling circuitry 920 based on the quality / characteristics of channel 750, UE capabilities, available resources in the cell processed by base station 710, etc.

[0188] In other words, the UE dynamically determines the number of regions based on the maximum number of TCI states dynamically indicated by TCI code points in the DCI. In this example, the determination of the number of super regions is performed dynamically. Therefore, resources can be utilized more efficiently. For example, when the maximum number of TRPs indicated by the RRC is 2, but the current DCI indicates via TCI indicators that only a single TCI state will be used for the transmission / reception of data scheduled by the same DCI, the number of regions will be determined for a TCI count equal to 1. In practice, in this case, it is not necessary to determine the regions.

[0189] For example, when the maximum number of TRPs indicated by RRC is 3, but the current DCI indicates via TCI indicator that only two TCI states will be used for sending / receiving data scheduled by the same DCI, the number or area will be determined for a number of TCIs equal to 2.

[0190] Note that for this example, the maximum number of TCIs does not need to be signaled / evaluated. Specifically, in this example, the number of zones is determined based on dynamic scheduling.

[0191] Region mapping on B.PRG

[0192] In the example, the processor assigns regions to corresponding integer multiples of PRGs in a semi-static manner, without considering dynamic resource allocation based on the DCI. For example, assignment can begin from the start of frequency resources indicated by frequency domain assignment in the DCI, and each PRG can be associated with a specific TCI state according to a predetermined pattern. Different patterns may exist, which will be explained in detail below. For example, an alternating pattern, in which PRGs are alternately assigned to multiple TCI states.

[0193] In other words, before resource allocation is completed, the UE allocates areas on common physical resource blocks (PRBs) in a semi-static manner in multiples of the PRG. Therefore, dynamic allocation may refer only to areas that belong to the dynamically scheduled TCI state (according to semi-static assignment).

[0194] This embodiment, combined with the semi-static determination of the number of regions described above, can provide a simple and effective UE implementation.

[0195] In another example, the processor assigns regions to corresponding integer multiples of PRGs based on the frequency domain resource allocation. In this case, the assignment can facilitate more efficient resource utilization because only those regions are mapped to currently scheduled resources. This embodiment, combined with the aforementioned dynamic determination of the number of regions, can provide efficient resource utilization.

[0196] In other words, in this example, after resource allocation is completed, the UE dynamically assigns regions on the allocated physical resource blocks in multiples of precoded resource block groups (PRGs).

[0197] C. Regional Association Pattern

[0198] In the first example, the processor associates a region with two or more TCI states based on a pre-configured pattern. The pre-configured pattern can be static pre-configured (set by the operator, etc. in the standard), semi-static pre-configured (e.g., via RRC signaling), or dynamically pre-configured via code points in the bit field of the DCI.

[0199] A pre-configured pattern can correspond to round-robin by alternating TCI states after every integer M consecutive regions, where M is not less than 1. Round-robin refers to a method according to which TCI states are cyclically mapped to the PRG in a predetermined order. A simple and efficient mapping might be M = 1. However, this disclosure is not limited to this, and M can be greater than 1. In fact, there may be M1 and M2 defined for two corresponding TCI states, where M1 is different from M2. There can be a number of Mx regions defined for each of x TCI states.

[0200] In other words, in this example, the UE associates each defined region with the indicated TCI state in a configurable mode (static, semi-static, or dynamic); for example, by rotating discontinuously across the entire frequency range.

[0201] On the base station side, the processor 730 must also map the area to resources in the same way so that data is correctly mapped to resources when sending or receiving data.

[0202] According to the second example, processor 780 (and processor 730) sequentially associates consecutive regions with each of two or more TCI states. In other words, the UE (and base station) first sequentially associates each identified region with the indicated TCI state, and then the next remaining region. This can be viewed as associating an entire superregion (containing all regions belonging to a TCI state) with the corresponding configured TCI states, which are sequentially mapped to frequency resources allocated with frequency domain assignments for reception in the DCI. One advantage of this approach may be the reduction in multiplexing complexity.

[0203] According to the third example, processor 770 (and corresponding processor 730) associates a first portion of a contiguous region with two or more TCI states according to the said round-robin (as in the first example), and associates a second portion of the contiguous region with one of the TCI states. In other words, UE 760 (and corresponding base station 710) associates each determined region with an indicated TCI state in two steps, one step including association in a discontinuous round-robin manner, and the other step including contiguous association of a super region (the remaining region of a TCI state) with the remaining PRG. This approach can be advantageous, particularly for cases with different MCSs and / or different TBs mapped to corresponding different TCI states.

[0204] According to the fourth example, the pre-configured pattern is received as a bitmap in semi-static or dynamic signaling. Each bit in the bitmap represents a region, the first value of the bit indicates a first TCI state, and the second value of the bit indicates a second TCI state. In other words, the UE dynamically associates each determined region with the indicated TCI state based on the indication of the bitmap for each region, where "0" indicates no association and "1" indicates association. Note that this pattern signaling is merely exemplary. The bitmap can provide each bit representing a PRG (which corresponds to the case where the region size is 1 PRG). Generally, the fourth example provides the highest flexibility on the one hand, but also requires some additional resources to signal the bitmap.

[0205] To strike a balance between flexibility and signaling effort, hybrid solutions may be possible. For example, the bitmap is statically defined and associated with indexes, which are then semi-statically signaled to the UE from the base station. Note that such indexes are not limited to bitmap representations for different schemes. For instance, two modes, such as polling mode (see the first example above) and continuous mode (see the second example above), can both be statically defined (by standards or operators) as configurable and associated with corresponding indexes (e.g., 0 and 1). The base station then configures the region and indicates the configured scheme by signaling its indexes in RRC messages, etc. For greater flexibility, in some embodiments, the indexes can be signaled in the DCI.

[0206] Alternatively, there can be more than one semi-static signaling notification (pre-configured), for example, in the form of a bitmap or by referring to some predefined (e.g., in the standard) indexes of different modes. Dynamic switching between such pre-configured modes can be made possible by DCI, for example, as an index of a corresponding one of the pre-configured modes. Such an index is dynamically signaled in DCI, either as a field or as a code point jointly encoded with one or more other parameters.

[0207] D. Area size

[0208] According to the first example, the processor (770 and / or 730) configures the size of each region to a fixed size common to all regions across all TCI states. In other words, the UE is statically configured with a common fixed value for each region. For example, each region may have the size of one PRG. However, the region size may also be fixedly set to more than one PRG. Static configuration means that the standard defines the region length (in terms of the number of PRGs), or the network operator defines the region length. Generally, static configuration means that reconfiguration is not possible for an established data carrier.

[0209] According to the second example, the processor (770 and / or 730) configures the size of each region based on semi-static signaling received by the transceiver that specifies the common size of all regions for all TCI states, or specifies the common size of all regions for each TCI state.

[0210] In other words, the UE (by the base station) is semi-statically configured with a common fixed value for each region via RRC signaling. The first possibility, having a common size for all regions across all TCI states, saves signaling resources. The second possibility, configuring different region sizes for different corresponding TCI states, provides greater flexibility and is particularly suitable for situations where different TCI states are configured with different MCSs.

[0211] According to the third example, the processor determines the size of each region from the DCI by one or more of the following:

[0212] - Obtain the absolute size from the DCI, represented by multiples of PRGs.

[0213] - Obtain the ratio between the sizes of regions belonging to different TCI states from the DCI.

[0214] - Obtain the transport block size of the corresponding region belonging to different TCI states from the DCI, and determine the region size based on the transport block size.

[0215] - Divide the total number of PRGs by the number of regions based on resource allocation.

[0216] For example, the UE dynamically determines the size of each region based on dynamic indications via the DCI. This indication can directly include the size (absolute size) or can be indicated by an index associated with that size. For instance, the region size can be part of a region configuration that further includes modes, the number of regions, etc. Such a configuration can be listed in a table and associated with corresponding indexes, which can then be indicated in the DCI. Any other signaling regarding the size within the DCI is possible.

[0217] As mentioned above with reference to semi-static signaling, the UE can be indicated with an absolute size in multiples of PRGs or any other indication of the size individually for each TCI state or in common for all TCI states.

[0218] For example, the proportion between the sizes of each region can be indicated to the UE via DCI signaling. One region can be signaled as an absolute size, and the remaining regions can be signaled as a proportion or difference. As will be apparent to those skilled in the art, other possibilities exist that prevent this disclosure from being limited to any of these examples.

[0219] In another exemplary implementation, the UE determines the size of each region based on the TB size associated with each region, which can be calculated based on a separate MCS indication of the corresponding TCI state. The TB size can be obtained from the MCS, and modulation can also be considered for determination. The MCS is typically indicated by an MCS index in an MCS table, which includes a combination of modulation (sequence) and transport block size (corresponding to code rate).

[0220] According to another exemplary implementation, the UE (and the corresponding base station) determines the size of each region by simply dividing the total number of PRGs by the total number of regions. In this example, it is assumed that the region size is the same for all TCI states. However, this determination can also be combined with signaling notifications of the ratio between the sizes of regions belonging to different TCI states to obtain the size, or this ratio can be defined / derived depending on the MCS.

[0221] Note that the determination and mapping of regions above are different steps A through D, but this is merely exemplary, and in practice, the mapping of TCI states can be directly described / defined onto the PRG. For example, once the size of the region is known, e.g., M, the TCI states are cyclically assigned to each of the M PRGs. Therefore, this disclosure is not limited to performing any particular method of mapping transports belonging to different TRPs onto PRGs, as long as the result is achieved (see, for example...). Figures 13 to 17 (mapping).

[0222] Figure 10A method according to an embodiment is illustrated. The method is executed at the UE and begins in step 1010 with the receipt of RRC signaling, which configures the UE with an FDM mechanism for multiple TRP reception and / or transmission of data. The RRC signaling is received from the network and may include any parameters for configuring regions, such as their size, location, number, and assignment of PRG and TCI states. For example, a base station may configure UEs in its cell via RRC. In step 1020, the UE receives a scheduled DCI and, for a TCI indicator, checks the code point of the relevant bit field in the DCI. Specifically, to receive the DCI, the UE may monitor a pre-configured CORESET (control resource) and perform blind decoding to determine if a DCI addresses the UE. When such a DCI is detected, the UE parses the parameters signaled in the DCI. According to this disclosure, the parameters include a TCI indicator that at least indicates whether one or more TCI states are configured. In some embodiments, the TCI indicator may also indicate the number of configured TCI states. After extracting the TCI indicator from the DCI, in step 1030, it is evaluated (assessed / determined) whether more than one TCI state (indicated by the TCI indicator) is configured.

[0223] If more than one TCI state is indicated in step 1030, steps 1040 through 1060 are executed. Specifically, in step 1040, the UE determines the frequency resources for receiving data. This can be done by extracting the frequency domain assignment from the DCI. However, this disclosure is not limited to this, and the resources can be defined semi-permanently and / or at least partially semi-statically by some previously received DCIs. Then, in step 1050, the UE associates the determined frequency resources with multiple TRPs at a granularity of multiples of PRGs. Here, the multiple can be one or more times (integer multiples) of the PRG. Finally, in step 1060, the UE receives data transmissions from the multiple TRPs on the allocated and associated resources. In this example, it is assumed that the scheduling DCI is the DCI that schedules transmissions in the downlink. However, as stated above, this disclosure applies to the uplink in addition to the downlink, or alternatively. Note that this disclosure can also apply to sidelinks.

[0224] If more than one TCI state is indicated in step 1030, steps 1070 to 1090 are executed. In step 1070, the UE determines the frequency resources used to receive data from one TRP. After step 1070, in step 1080, the UE associates the transmission with the indicated single TCI state. Finally, in step 1090, the UE receives data transmission from one TRP on the allocated resources.

[0225] Figure 11The method is shown to be performed at both the UE and the base station that are communicating with each other.

[0226] The method performed at the base station may include step S1110, in which the base station performs scheduling and allocates resources to the UE on two or more TCI states (TRPs). Based on this allocation, in step S1120, the base station generates a DCI carried on the PDCCH in a manner that provides within the DCI signaling a TCI indicator specifying the configuration of two or more transport configuration indication TCI states and a frequency domain resource assignment for the frequency domain resources allocated to the two or more TCI states. To properly map data transmission onto resources, the base station determines one or more regions in the frequency domain for each of the two or more TCI states, each region having an integer multiple of precoded resource block groups (PRGs), the integer being equal to or greater than 1, wherein regions of different TCI states do not overlap. In step S1130, the base station transmits a PDCCH including the generated DCI. Finally, in step S1170, the base station transmits data for each TCI state on the frequency domain resources in the determined frequency domain regions.

[0227] Accordingly, the method at the UE includes step S1140 of receiving downlink control information (DCI) signaled via PDCCH. In step S1150, the UE obtains from the DCI signaling a TCI indicator specifying two or more Transport Configuration Indicator (TCI) states that are configured, and a frequency domain resource assignment indicating the frequency domain resources allocated for the two or more TCI states. In step S1160, the UE determines one or more regions in the frequency domain for each of the two or more TCI states, each region having an integer multiple of precoded resource block groups (PRGs), the integer being equal to or greater than 1, wherein the regions of different TCI states do not overlap. Therefore, in step S1180, the UE receives data for each TCI state (TRP) on the frequency domain resources within the determined frequency domain regions.

[0228] When referring to frequency domain resources, in this disclosure, it means frequency domain resources of one or more symbols (depending on the uplink / downlink specification of the physical layer technology, OFDM or DFT-S-OFDM, etc.). Typically, the DCI will carry (or its timing implications) the specific time domain resources to which the scheduling carried in the DCI applies.

[0229] In the following description, some specific embodiments are provided for illustrative purposes to illustrate some combinations of the previously described region defining portions A through D. Note that these embodiments do not limit the invention.

[0230] Example 1

[0231] The UE (and base station) divides the PRB in the frequency domain into multiple equally sized regions, where the size of each region is statically configured to be equal to one PRB. The number of super regions is equal to the number of configured TCI states. A semi-static association between regions and TCI states is performed in a round-robin manner. As a result, regions with the same index number (i.e., assigned to the same TCI state) are non-contiguously allocated in the frequency domain on the resources allocated by the frequency domain resource assignment carried by the DCI.

[0232] One advantage of Embodiment 1 is that it requires no additional signaling and relies solely on this new process that will be configured to the UE and applied when the TCI indicator indicates more than one TCI state. Through discontinuous allocation, Embodiment 1 can provide maximum frequency diversity for the UE.

[0233] On the other hand, this embodiment also presents some limitations. The primary use case for this embodiment is when the same MCS is used for transmissions from different TRPs and the PRG size is indicated as 2 or 4 via DCI. Semi-static association means that even unavailable areas may be associated with a TRP, and actual transmissions will only occur on available areas; therefore, the effective association sequence with a TRP may not be round-robin.

[0234] Figure 12 An example of a region according to Embodiment 1 is shown.

[0235] Two superregions are defined, where superregion 1 is associated with TCI state 1, and superregion 2 is associated with TCI state 2. Each superregion has one consecutive PRG and is generally associated with each TCI state in a round-robin manner. Therefore, the entire superregion is not contiguous. In this example, PRG5 of this region may be unavailable because it has been assigned to another UE. Figure 12 As shown, since the assignment between regions and TCI states is performed before the actual resource allocation, PRG5 belongs to superregion 1 but cannot be assigned / used in TCI state 1. PRG4 and PRG6 both belong to superregion 2 and therefore belong to TCI state 2.

[0236] Example 2

[0237] The implementation is, for example Figure 13As shown. Specifically, the UE (corresponding to the configuration provided and followed by the base station) divides the PRG in the frequency domain into multiple regions of equal size. The size of the region is statically configured to be equal to 1 PRG and is common to all regions for all TCI states. The number (quantity) of regions is equal to the number of indicated TCI states (i.e., the TCI states indicated by the DCI within the TCI indicator (e.g., within the code point of the corresponding bit field). The dynamic association between regions and TCI states is performed in a round-robin manner. Therefore, regions belonging to a TCI state are not contiguously allocated in the frequency domain.

[0238] The association here is done dynamically, meaning that only available resources are considered for creating zones and associating with TCI states. This can provide the advantage of efficient resource utilization. A suitable use case for this embodiment could be when the same MCS is used for transports from different TRPs and the DCI indicates a PRG size of, for example, 2 or 4.

[0239] like Figure 13 As shown, two superregions are defined (in Figure 13 The superregion (represented as Region 1 and Region 2) is used, where the PRG of superregion 1 is associated with TCI state 1, and the PRG of superregion 2 is associated with TCI state 2. Each region of superregion 1 and superregion 2 has a consecutive PRG. Regions are generally associated with each TCI state in a round-robin fashion, therefore the association between regions and TCI states is generally discontinuous. Region 1 corresponds to PRG1, Region 2 corresponds to PRG2, Region 3 corresponds to PRG3, and so on.

[0240] All associated regions are also assigned because association is performed dynamically only on the assigned resources (i.e., on the resources specified in the frequency domain assignment of the DCI).

[0241] Example 3

[0242] Example 3 Figure 14 As shown. Accordingly, the UE (corresponding to the configuration adopted by the base station) divides the PRB in the frequency domain into multiple regions of equal size. The size of the regions is semi-statically configured via the RRC protocol. The number of super regions is equal to the number of indicated TCI states, which is 2 in this example. The dynamic association between regions and TCI states is performed in a round-robin manner, resulting in discontinuous allocation of super regions. The dynamic indication of the region size can be explicitly indicated by a new bit field, or implicitly indicated along with the nominal RBG size indication.

[0243] This is illustrated in Table 2 below, which is a modification of Table 1 above. Therefore, the values ​​in parentheses are exemplary region sizes associated with the RBG size. For example, for a bandwidth portion size between 73 and 144, in Configuration 1, the RBG size is 8 RBs, and the region size is 2 PRGs. Note that this table is merely exemplary to illustrate the possible relationship between RBG sizes (or even those configurable by semi-static signaling) as defined by standards and between region sizes. This relationship can be specified in a manner different from and independent of this table. The advantage of this implicit relationship is reduced signaling overhead for region size signaling.

[0244] Bandwidth portion size Configuration 1 Configuration 2 1–36 2(1) 4(2) 37–72 4(2) 8(2) 73–144 8(2) 16(2) 145–275 16(4) 16(4)

[0245] Table 2

[0246] exist Figure 14 In this framework, two superregions are defined: superregion 1 is associated with TCI state 1, and superregion 2 is associated with TCI state 2. Each region indicates the size of two PRGs, and these regions are associated with each TCI state in a round-robin fashion, resulting in a discontinuous resource distribution for each TCI state. Figure 14 Four regions 1 to 4 are shown, where regions 1 and 3 form superregion 1, and regions 2 and 4 form superregion 2. Superregion 1 is associated with TCI state 1, while superregion 2 is associated with TCI state 2.

[0247] This embodiment is relatively flexible because the area size is not fixed at 1 PRG. In this example, the area size is 2 PRGs. However, as mentioned above, the size can typically be indicated based on the desired frequency diversity. An indication can be provided for all areas. One use case where this embodiment can provide an advantageous implementation is when the same MCS is used for transmissions from different TRPs and the DCI indicates a PRG size of, for example, 2 or 4. To make this embodiment also applicable to different MCSs for different TCI states, an area size indication can be provided for each TCI state.

[0248] Example 4

[0249] In this embodiment, the number of regions (and in this case, the number of superregions) is equal to the number of indicated TCI states. Therefore, the UE divides the PRG in the frequency domain into multiple regions of equal size (or, generally, substantially equal size, where the number of PRGs is not divisible by the number of TCI states). The dynamic association between regions and TCI states is performed in a round-robin manner. In this embodiment, each region is allocated sequentially, and the size of the region is calculated by dividing the total PRG by the number of regions. This embodiment can be advantageous, especially when the precoding granularity is wideband, making sequential allocation more suitable.

[0250] Example 4 Figure 15 As shown, two regions are defined: Region 1 is associated with TCI state 1, and Region 2 is associated with TCI state 2. Each region is defined by dividing the total available PRG into these two parts, each associated with a separate TCI state. Each superregion corresponds to the corresponding region, thus only consecutive PRG allocations occur.

[0251] Example 5

[0252] According to Embodiment 5, the UE divides the PRB in the frequency domain into multiple regions of different sizes. The size of the region is explicitly indicated to the UE in terms of either the absolute value or the proportion of the region's size.

[0253] For example, if 2 and 4 are explicit (absolute) sizes indicated for the corresponding regions of TCI states 1 and 2, then region 1 associated with TCI state 1 has 2 consecutive PRGs, and region 2 associated with TCI state 2 has 4 consecutive PRGs. If a ratio such as (1:2) is indicated, then region 1 associated with TCI state 1 has 1 consecutive PRG, and region 2 associated with TCI state 2 has 2 consecutive PRGs. In this embodiment, the number of superregions is equal to the number of configured TCI states. The dynamic association between regions and TCI states is performed in a round-robin manner, resulting in superregions being allocated discontinuously. This embodiment provides the flexibility to support even cases where different regions are not of equal size when different TBSs are sent from different TRPs.

[0254] Example 6

[0255] In this embodiment, the UE (and the corresponding base station) divides the PRB (specifically the PRG) in the frequency domain into multiple regions of different sizes. Specifically, the size of each region is calculated based on indications of different MCSs for different TRPs. Let's assume that the first TRP is configured with MCS1 and the second TRP is configured with MCS2, where MCS1 and MCS2 are different from each other.

[0256] For example, if the values ​​of MCS1 and MCS2 are within a certain threshold, the size of the region ratio is calculated as (1:1). The threshold is the difference between MCS1 and MCS2. If MCS1 > MCS2 (or vice versa) and the difference between them (MCS1 - MCS2 and / or MCS2 - MCS1, e.g., the absolute difference) is higher than a certain threshold, the size of the region ratio is calculated as (1:2).

[0257] The number of superregions is equal to the number of configured TCI states. The dynamic association between regions and TCI states is performed in a round-robin manner. Therefore, superregions are not allocated contiguously.

[0258] This embodiment calculates the size ratio between different regions based on the MCS indicated for different TRPs, thus eliminating the need for explicit signaling and enabling more efficient resource utilization.

[0259] Figure 16 An example of a region according to this embodiment is shown. Two superregions are defined, where superregion 1 is associated with TCI state 1 and superregion 2 is associated with TCI state 2. The size ratio between region 1 and region 2 is indicated or determined to be (2:1), meaning that region 1 (belonging to superregion 1) has 2 consecutive PRGs and region 2 (belonging to superregion 2) has 1 consecutive PRG. In this embodiment, the total resources associated with each TCI state are not equal.

[0260] Example 7

[0261] In this embodiment, the UE (which is also the base station) divides the PRB (and therefore the PRG) in the frequency domain into multiple regions of equal size. The size of each region is statically configured to be equal to 1 PRG. The number of super regions is equal to the number of configured TCI states. The dynamic association between regions and TCI states is completed in two steps when different TB sizes are sent from different TRPs. The association between regions and TCI states is first completed in a round-robin manner until the lowest TB size associated with one of the TCI states is fully allocated. After the lowest TB size (here, 1 PRG) is fully allocated, the remaining regions are then continuously associated with the TCI state with the highest TB size. Again, in this case, super regions are not continuously allocated. This embodiment is simpler because it requires calculations related to the ratio of sizes between different regions.

[0262] Figure 17An example of this embodiment is shown. Two regions are defined, where region 1 is associated with TCI state 1 and region 2 is associated with TCI state 2. Regions 1 and 2 are defined in a round-robin fashion (1 PRG each) until the lower TBS associated with region 2 is allocated, and then all remaining (allocated) PRGs are allocated sequentially with region 1 because it has a higher TBS. The total resources associated with each TCI state are not equal.

[0263] This disclosure can be implemented through software, hardware, or a combination of software and hardware. Each functional block used in the description of each of the above embodiments can be implemented partially or entirely by an LSI (Large-Scale Integration), such as an integrated circuit, and each process described in each embodiment can be controlled partially or entirely by the same LSI or a combination of LSIs. An LSI can be formed as a single chip or can be formed as a single chip to include some or all of the functional blocks. An LSI can include data inputs and outputs coupled thereto. Depending on the level of integration, the LSI herein can be referred to as an IC, a system LSI, a super LSI, or an ultra-LSI. However, the technology for implementing integrated circuits is not limited to LSIs and can be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Furthermore, an FPGA (Field-Programmable Gate Array) that can be programmed after the LSI is manufactured, or a reconfigurable processor that can reconfigure the connection and configuration of circuit cells arranged within the LSI, can be used. This disclosure can be implemented as digital or analog processing. If future integrated circuit technologies replace LSIs due to advancements in semiconductor technology or other derivative technologies, future integrated circuit technologies can be used to integrate the functional blocks. Biotechnology can also be applied.

[0264] This disclosure can be implemented by any kind of communication device, apparatus or system, which is referred to as a communication device.

[0265] Some non-limiting examples of such communication devices include telephones (e.g., cellular phones, smartphones), tablet computers, personal computers (PCs) (e.g., laptops, desktop computers, 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, remote healthcare / telemedicine (remote healthcare and medical) devices, and vehicles that provide communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.

[0266] The communication device is not limited to portable or mobile devices, but may also include any kind of non-portable or fixed device, equipment or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines and any other “thing” in an “Internet of Things (IoT)” network.

[0267] Communication can include the exchange of data through, for example, cellular systems, wireless LAN systems, satellite systems, and various combinations thereof.

[0268] 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 a controller or sensor that generates control signals or data signals used by the communication device performing the communication functions of the communication device.

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

[0270] In summary, the first embodiment provides a user equipment (UE) including: a transceiver that receives downlink control information (DCI) signaling; and a processor that obtains from the DCI signaling: a TCI indicator specifying two or more transmission configuration indication (TCI) states that are configured; and a frequency domain resource assignment indicating frequency domain resources allocated for the two or more TCI states; determining one or more regions in the frequency domain for each of the two or more TCI states, each region having an integer multiple of precoded resource block groups (PRGs), the integer being equal to or greater than 1, wherein the regions of different TCI states do not overlap, and wherein the transceiver receives or transmits data for each TCI state on the frequency domain resources in the determined frequency domain regions.

[0271] In the second embodiment, in addition to the first embodiment, the processor determines the number of regions based on the maximum number of TCI states, which is configured as semi-statically as possible to be indicated by a TCI of the DCI.

[0272] In the third embodiment, in addition to the first embodiment, the processor determines the number of regions based on the maximum number of TCI states indicated by the TCI indicator.

[0273] In the fourth embodiment, in addition to the first or second embodiment, the processor assigns regions to corresponding integer multiples of PRGs in a semi-static manner, without considering dynamic resource allocation based on the DCI.

[0274] In the fifth embodiment, in addition to the first or third embodiment, the processor assigns regions to corresponding integer multiples of PRGs based on the frequency domain resource assignment.

[0275] In the sixth embodiment, in addition to any of the first to fifth embodiments, the processor associates a region with two or more TCI states according to a pre-configured pattern.

[0276] In the seventh embodiment, in addition to the sixth embodiment, a pre-configured pattern is received as a bitmap in semi-static or dynamic signaling, where each bit of the bitmap represents a region, a first value of the bit indicates a first TCI state, and a second value of the bit indicates a second TCI state.

[0277] In the eighth embodiment, in addition to the sixth embodiment, the pre-configured pattern corresponds to a round-robin by alternating TCI states after every integer M consecutive regions, where M is not less than 1.

[0278] In the ninth embodiment, in addition to the eighth embodiment, the processor associates a first portion of a continuous region with two or more TCI states according to the polling, and associates a second portion of the continuous region with one of the TCI states.

[0279] In the tenth embodiment, except for any of the first to sixth embodiments, the processor sequentially associates a consecutive region with each of two or more TCI states.

[0280] In the eleventh embodiment, except for any of the first to ninth embodiments, the processor configures the size of each region as: (i) a fixed size common to all regions for all TCI states; (ii) either according to semi-static signaling received by the transceiver, and the semi-static signaling specifies: a size common to all regions for all TCI states; or a size common to all regions for each TCI state.

[0281] In the twelfth embodiment, except for any of the first to ninth embodiments, the processor determines the size of each region from the DCI by one or more of the following: (i) obtaining the absolute size from the DCI in terms of multiples of PRGs, (ii) obtaining the ratio between the sizes of regions belonging to different TCI states from the DCI, (iii) obtaining the transport block size of the corresponding region belonging to different TCI states from the DCI and determining the size of the region based on the transport block size, and (iv) dividing the total number of PRGs by the number of regions according to resource allocation.

[0282] According to the thirteenth embodiment, a scheduling device is provided, comprising: a transceiver that transmits downlink control information (DCI) signaling; and a processor that provides within the DCI signaling: a TCI indicator specifying that two or more transmission configuration indication (TCI) states are configured; and a frequency domain resource assignment indicating frequency domain resources allocated for the two or more TCI states; determining one or more regions in the frequency domain for each of the two or more TCI states, each region having an integer multiple of precoded resource block groups (PRGs), the integer being equal to or greater than 1, wherein the regions of different TCI states do not overlap, and wherein the transceiver transmits or receives data for each TCI state on the frequency domain resources in the determined frequency domain regions.

[0283] According to the fourteenth embodiment, a method is provided, comprising: receiving downlink control information (DCI) signaling; obtaining from the DCI signaling: a TCI indicator specifying two or more Transmission Configuration Indicator (TCI) states configured; and a frequency domain resource assignment indicating frequency domain resources allocated for the two or more TCI states; determining one or more regions in the frequency domain for each of the two or more TCI states, each region having an integer multiple of precoded resource block groups (PRGs), the integer being equal to or greater than 1, wherein the regions of different TCI states do not overlap; and receiving or transmitting data for each TCI state on the frequency domain resources in the determined frequency domain regions.

[0284] According to the fifteenth embodiment, a method is provided, comprising: transmitting downlink control information (DCI) signaling; providing within the DCI signaling: a TCI indicator specifying that two or more Transmission Configuration Indicator (TCI) states are configured; and a frequency domain resource assignment indicating frequency domain resources allocated for the two or more TCI states; determining one or more regions in the frequency domain for each of the two or more TCI states, each region having an integer multiple of precoded resource block groups (PRGs), the integer being equal to or greater than 1, wherein the regions of different TCI states do not overlap; and transmitting or receiving data for each TCI state on the frequency domain resources in the determined frequency domain regions.

[0285] Note that embodiments two through twelfth are correspondingly applicable to the scheduling device of embodiment thirteen. Furthermore, the steps performed by the circuitry during operation and the transceiver steps mentioned in the above UE and base station embodiments correspond to the respective methods.

[0286] In addition, a non-transitory medium is provided to store program instructions that, when executed on processing circuitry such as a general-purpose processor, perform all the steps of any of the above-described method embodiments.

[0287] In summary, this disclosure relates to User Equipment (UE) and scheduling nodes, and corresponding methods. Specifically, Downlink Control Information (DCI) signaling carries a Transmission Configuration Indicator (TCI) indicating that two or more TCI states are configured, and a frequency domain resource assignment for the frequency domain resources allocated to the two or more TCI states. For each of the two or more TCI states, one or more regions in the frequency domain are determined, each region having an integer multiple of precoded resource block groups (PRGs), said integer being equal to or greater than 1, wherein the regions for different TCI states do not overlap. Data is received or transmitted for each TCI state on the frequency domain resources within the determined frequency domain regions.

Claims

1. A communication apparatus, comprising: a transceiver that receives downlink control information, DCI, signaling; and a processor that obtains from the DCI signaling a transmission configuration indication, TCI, indicator that specifies that at least two TCI states are configured; wherein even precoding resource block groups, PRGs, are assigned to a first TCI state and odd PRGs are assigned to a second TCI state. at least one PRG of each TCI state is included in a frequency region of each TCI state.

2. The communication apparatus according to claim 1, wherein a codepoint of the TCI indicator indicates a number of the at least two TCI states, and the processor determines a number of frequency regions according to the at least two TCI states.

3. The communication apparatus according to claim 2, wherein the processor assigns a frequency region to an integer number of PRGs according to a frequency domain resource assignment.

4. The communication apparatus according to claim 1, wherein the processor associates a frequency region with the at least two TCI states according to a configured pattern.

5. The communication apparatus according to claim 1, wherein the configured pattern alternates TCI states after every integer M consecutive frequency regions, where M is no less than 1.

6. The communication apparatus according to claim 5, wherein, the processor associates a first portion of the consecutive frequency regions with the at least two TCI states and a second portion of the consecutive frequency regions with one of the at least two TCI states.

7. The communication apparatus according to claim 6, wherein the processor sequentially associates consecutive frequency regions with each of the at least two TCI states.

8. The communication apparatus according to claim 1, wherein the processor configures a size of a frequency region:

9. The communication apparatus according to claim 1, wherein as a fixed size common to all frequency regions of all TCI states; or according to semi-static signaling received by the transceiver that specifies: a size common to all frequency regions of all TCI states; or a size common to all frequency regions of each TCI state. the processor determines a size of a frequency region from the DCI by at least one of:

10. The communication device of claim 1, wherein, obtaining from the DCI an absolute size expressed in PRGs, obtaining from the DCI a ratio between sizes of frequency regions belonging to different TCI states, obtaining from the DCI transport block sizes of frequency regions belonging to different TCI states and determining the size of the frequency regions based on the transport block sizes, or dividing a total number of PRGs by a number of frequency regions. 11.A scheduling node, comprising: a transceiver that transmits downlink control information, DCI, signaling; and a processor that provides in the DCI signaling a transmission configuration indication, TCI, indicator that specifies that at least two TCI states are configured; wherein even precoding resource block groups, PRGs, are assigned to a first TCI state and odd PRGs are assigned to a second TCI state. 12.A method, comprising: receiving downlink control information, DCI, signaling; and obtaining from the DCI signaling a transmission configuration indication, TCI, indicator that specifies that at least two TCI states are configured; wherein even precoding resource block groups, PRGs, are assigned to a first TCI state and odd PRGs are assigned to a second TCI state. 13.A method, comprising: transmitting downlink control information, DCI, signaling; and ​ ​ ​ ​ providing a transmission configuration indication, TCI, indicator in DCI signaling, the indicator specifying that at least two TCI states are configured; wherein, even precoding resource block groups, PRGs, are assigned to a first TCI state and odd PRGs are assigned to a second TCI state.

14. An integrated circuit comprising circuitry that: controls receiving downlink control information, DCI, signaling; and controls obtaining a transmission configuration indication, TCI, indicator from the DCI signaling, the indicator specifying that at least two TCI states are configured; wherein, even precoding resource block groups, PRGs, are assigned to a first TCI state and odd PRGs are assigned to a second TCI state.

15. An integrated circuit comprising circuitry that: controls transmitting downlink control information, DCI, signaling; and controls providing a transmission configuration indication, TCI, indicator in DCI signaling, the indicator specifying that at least two TCI states are configured; wherein, even precoding resource block groups, PRGs, are assigned to a first TCI state and odd PRGs are assigned to a second TCI state.

Images