Inter-cell multi-TRP operation for wireless networks
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-24
- Publication Date
- 2026-08-14
AI Technical Summary
例如,超可靠和低时延通信(URLLC)设备可能需要高可靠性和非常低的时延
Smart Images

Figure CN117378165B_ABST
Abstract
Description
Technical Field
[0001] This description relates to wireless communication. Background Technology
[0002] A communication system can be a facility that enables communication between two or more nodes or devices (such as fixed or mobile communication devices). Signals can be transmitted over wired carriers or wireless carriers.
[0003] An example of a cellular communication system is the architecture being standardized by the 3rd Generation Partnership Project (3GPP). Recent developments in this area are often referred to as the Long Term Evolution (LTE) of Universal Mobile Telecommunications System (UMTS) radio access technology. E-UTRA (Evolved UMTS Terrestrial Radio Access) is the air interface for the 3GPP LTE upgrade path for mobile networks. In LTE, base stations or access points (APs) are called Enhanced Node APs (eNBs), providing radio access within a coverage area or cell. In LTE, mobile devices or mobile stations are called User Equipment (UEs). LTE has incorporated many improvements and developments. Various aspects of LTE are continuously being improved.
[0004] Similar to the early evolution of 3G and 4G wireless networks, the development of 5G New Radio (NR) is part of an ongoing evolution of mobile broadband. Furthermore, 5G targets emerging use cases beyond mobile broadband. One goal of 5G is to deliver significant improvements in wireless performance, which can include new levels of data rates, latency, reliability, and security. 5G NR can also scale to efficiently connect massive Internet of Things (IoT) networks and can provide new types of mission-critical services. For example, ultra-reliable and low-latency communication (URLLC) devices may require high reliability and very low latency. Summary of the Invention
[0005] According to an exemplary embodiment, a method may include a user equipment (UE) within a wireless network determining, based on the following, to perform inter-cell multi-transmitter receive point (multi-TRP) operation based on multi-downlink control information (multi-DCI): the UE receives from a network node Transport Configuration Index (TCI) states for multiple Control Resource Sets (CORESETs), wherein the TCI states for the multiple CORESETs are associated with multiple cells having different Physical Cell Identifiers (PCIs) or with multiple cell groups, wherein the TCI states indicate Quasi-Co-location (QCL) characteristics that the UE will use to receive Physical Downlink Control Channels (PDCCHs) associated with multiple cells having different PCIs or with multiple cell groups. The association, wherein multiple cells or multiple cell groups include at least a serving cell and at least one non-serving cell for the user equipment; and the user equipment determines that at least one of the following conditions exists: 1) higher-layer parameters related to multi-DCI-based multi-TRP have been configured for the user equipment; 2) a default mode for multi-TRP operation has been configured for the user equipment; or 3) the user equipment has received control information indicating that the Physical Downlink Shared Channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values is activated; and the user equipment determines to perform inter-cell multi-DCI-based multi-TRP operation, for cells from multiple cells or for cells from multiple cell groups, and performs inter-cell multi-DCI-based multi-TRP operation.
[0006] Additional example embodiments corresponding to each method are provided, including at least the following for each method: an apparatus including components for performing each method; an apparatus including at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code being configured together with the at least one processor to cause the apparatus to at least perform the method; and a non-transitory computer-readable storage medium including instructions stored thereon, which, when executed by the at least one processor, are configured to cause a computing system to perform the method.
[0007] Details of one or more examples of the embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description, drawings, and claims. Attached Figure Description
[0008] Figure 1 This is a block diagram of a wireless network according to an example embodiment.
[0009] Figure 2 This is a diagram illustrating a single cell, multiple DCI, multiple TRP transmission based on an example embodiment.
[0010] Figure 3 This is a diagram illustrating multi-cell (or multi-cell) multi-TRP transmission based on multiple DCI, according to an example embodiment.
[0011] Figure 4 This is a flowchart illustrating the operation of a user equipment (or UE) according to an example embodiment.
[0012] Figure 5 This is a diagram illustrating the operation according to an example embodiment.
[0013] Figure 6 This is a block diagram of a wireless station (e.g., AP, BS, gNB, TRP, network node, user equipment, UE, or other wireless node) according to an example embodiment. Detailed Implementation
[0014] Figure 1 This is a block diagram of a wireless network 130 according to an example embodiment. Figure 1 In the wireless network 130, user equipment 131, 132, 133, and 135 (also referred to as mobile stations (MS) or user equipment (UE)) can connect to (and communicate with) base station 134, which can also be referred to as access point (AP), enhanced node B (eNB), or next-generation node B (gNB). The terms user equipment and user equipment (UE) are used interchangeably. BS can also be referred to as RAN (Radio Access Network) or NG-RAN (Next Generation Radio Access Network) node. At least some of the functions of a BS (such as AP, gNB, eNB, RAN node) can also be performed by one or more network nodes, servers, or hosts, such as centralized units (CU) and distributed units (DU) in a split RAN architecture, which are operatively coupled to remote transceivers, such as remote radio headends (RRHs). BS 134 provides radio coverage within cell 136 (including to user equipment 131, 132, 133, and 135). Although only four user devices are shown connected to or attached to BS134, any number of user devices can be provided. BS134 is also connected to core network 150 via S1 interface 151. This is just a simplified example of a wireless network; other examples can be used.
[0015] According to the illustrative example, a BS (e.g., AP, eNB, gNB, RAN node) can be part of a mobile telecommunications system. The RAN can include one or more RAN nodes (e.g., AP, BS, eNB, gNB) that implement radio access technologies, such as allowing one or more UEs to access the network or core network. Therefore, the RAN node is located between one or more user equipments or UEs and the core network. According to the example embodiment, each RAN node can provide one or more wireless communication services to one or more UEs or user equipments, for example, to allow the UE to wirelessly access the network via the RAN node. Each RAN node can perform or provide wireless communication services, such as allowing a UE or user equipment to establish a wireless connection with the RAN node, and sending data to one or more UEs and / or receiving data from one or more UEs. For example, after establishing a connection with a UE, the RAN node can forward data received from the network or core network to the UE, and / or forward data received from the UE to the network or core network. RAN nodes can perform a wide variety of other radio functions or services, such as broadcasting control information (e.g., system information) to UEs, paging UEs when data is available, assisting UEs with handover between cells, scheduling resources for uplink data transmission from (multiple) UEs and downlink data transmission to (multiple) UEs, and sending control information to configure one or more UEs. These are just a few examples of one or more functions that a RAN node can perform.
[0016] User equipment (user terminal, user equipment (UE), mobile terminal, handheld wireless device, etc.) can refer to portable computing devices, including wireless mobile communication devices with or without a Subscriber Identity Module (SIM), including but not limited to the following types of devices: mobile station (MS), mobile phone, cell phone, smartphone, personal digital assistant (PDA), handheld device, device using a wireless modem (alarm or measuring device, etc.), laptop and / or touchscreen computer, tablet computer, phablet, game console, laptop, vehicle, sensor, wearable device, for example, or any other wireless device. It should be understood that user equipment can also be (or may include) a device with virtually no uplink, an example being a camera or camcorder that loads images or video clips onto a network.
[0017] The core network 150 may include a mobility management entity (MME) or access and mobility management function (AMF) that controls access to the network and handles or assists in the mobility / handover of user equipment between BSs, one or more gateways that can forward data between the BS and the packet data network or the Internet, and other control nodes, functions or blocks.
[0018] Furthermore, by way of illustration, the various example embodiments or technologies described herein can be applied to various types of user equipment or data service types, or to user equipment on which multiple applications may run, which may belong to different data service types. New radio (5G) developments can support a variety of different applications or data service types, such as: Machine-Type Communication (MTC), Enhanced Machine-Type Communication (eMTC), Internet of Things (IoT), and / or Narrowband IoT user equipment, Enhanced Mobile Broadband (eMBB), and Ultra-Reliable and Low-Latency Communication (URLLC). Many applications associated with these new 5G (NR) technologies often require higher performance than previous wireless networks.
[0019] The Internet of Things (IoT) can refer to a growing group of objects that may have internet or network connectivity, allowing them to send and receive information from other network devices. For example, many sensor-type applications or devices can monitor physical conditions or states and, for instance, send reports to servers or other network devices when events occur. Machine-to-machine (MTC) communication, for example, is characterized by fully automated data generation, exchange, processing, and execution between intelligent machines, with or without human intervention. Enhanced Mobile Broadband (eMBB) can support data rates significantly higher than those currently available in LTE.
[0020] Ultra-Reliable and Low-Latency Communication (URLLC) is a new type of data service or new use case supported by new radio (5G) systems. This enables emerging applications and services such as industrial automation, autonomous driving, vehicle safety, and eHealth services. To illustrate, 3GPP aims to provide reliable connections corresponding to a block error rate (BLER) of 10⁻⁵ and U-plane (user / data plane) latency of up to 1 millisecond. Therefore, for example, URLLC user equipment / UEs may require significantly lower block error rates and lower latency (with or without the requirement for simultaneous high reliability) than other types of user equipment / UEs. Thus, for example, a URLLC UE (or URLLC applications on a UE) may require much shorter latency compared to an eMBB UE (or an eMBB application running on a UE).
[0021] Various example embodiments can be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G / New Radio (NR), or any other wireless network or wireless technology operating on the cmWave and / or mmWave bands, as well as a wide variety of communication services, such as IoT, MTC, eMTC, eMBB, URLLC, etc. These example network, technology, or data service types are provided only as illustrative examples.
[0022] The UE can be configured by the gNB (or other network nodes) to perform different measurements and report measurements to the network (or multiple gNBs). The configuration of the UE for performing reference signal (or beam) measurements (e.g., CSI-RS measurements for different beams) and reporting can be executed by the gNB sending a report configuration (e.g., such as CSI-Report-Config) to the UE. The report configuration may, for example, indicate the downlink resources(e.g., CSI-RS reference signals / SSBs, or beams) on which measurements should be performed, the specific quantities or parameters to be measured, and how to perform the report, such as when to report.
[0023] The UE can measure multiple signal parameters (e.g., Reference Signal Received Power (RSRP)) of each of several downlink reference signals (e.g., Synchronization Signal Block / SSB signals, or Channel State Information (CSI)-Reference Signals (CSI-RS)) received by the UE from the gNB / network node (or BS), where each reference signal can be transmitted by the gNB via a different gNB transmit beam (or via different downlink DL reference signals). For example, the UE can determine the strongest beam or reference signal (e.g., one with the highest RSRP) and can then send a measurement report to the gNB (which may identify the N strongest DL reference signals (or beams)) along with the RSRPs (or other measured signal parameters) of these N beams. The gNB can use this measurement report, for example, to determine which beam to use to communicate with the UE.
[0024] According to example embodiments, 1, 2, 4, 8, or 16 consecutive Control Channel Elements (CCEs) can be used to transmit the Physical Downlink Control Channel (PDCCH), where the number of CCEs can be referred to as the aggregation level (or CCE aggregation level). According to example embodiments, a CCE is a building block of the PDCCH, where a CCE can be the minimum set of resources that can be used for the PDCCH. For example, a CCE can be a unit on which a search space for blind decoding can be defined. Therefore, depending on the aggregation level, each PDCCH may include one or more CCEs. According to example embodiments, a CCE may include 6 Resource Element Groups (REGs), each of which may include a resource block in an OFDM symbol.
[0025] The search space may include a set of candidate PDCCHs (candidate downlink control channels) formed by the CCE at a given aggregation level(s), on which the UE should attempt to decode. The UE may have multiple search spaces for different purposes (such as different common search spaces and user-specific search spaces). The search space may include one or more control resource sets (CORESETs). A CORESET may be (or may include) time-frequency resources on which PDCCH(s) are transmitted. Multiple search spaces using the same control resource set (CORESET) may exist, and multiple CORESETs may exist configured for the UE. Furthermore, a control resource set (CORESET) may be (or may include) time-frequency resources on which the UE attempts to decode candidate PDCCHs using one or more search spaces.
[0026] At the configured PDCCH monitoring time (e.g., multiple times or locations within a time slot where PDCCHs may be transmitted) for a search space, the UE will attempt to decode candidate PDCCHs for one or more DCI formats for that search space. For example, up to five (or other numbers) aggregation levels (e.g., corresponding to 1, 2, 4, 8, or 16 CCEs) can be configured for a search space, and there is a given number of PDCCH candidates for each aggregation level. Multiple (e.g., four or other numbers) different DCI formats may exist, and the UE can perform decoding for these different DCI formats. Therefore, different DCI formats may be used for DCI transmission on the PDCCH, and the DCI formats are often unknown to the UE beforehand; therefore, the UE may need to perform blind (e.g., DCI formats unknown to the UE a priori) detection of the DCI format.
[0027] Therefore, the search space configuration can be provided to or transmitted to the UE and can include information identifying one or more of the following: a control resource set (CORESET) indicating the time and frequency resources on which (multiple) PDCCHs may be transmitted; a demodulation reference (DMRS) signal that can be used by the UE for demodulating data or control signals (e.g., DCI); an indication of the timing of PDCCH monitoring, which may include the time or location within (multiple) time slots on which (multiple) PDCCHs may be transmitted; the (multiple) DCI formats to be monitored; and / or the number of PDCCHs (or PDCCH candidates) monitored for each aggregation level.
[0028] From the UE's perspective, each PDCCH can be considered a PDCCH candidate because, for example, a PDCCH may or may not exist (it may not have been sent yet, or it may not have been received yet), may have a DCI format that is the same as or different from the DCI format that the UE is monitoring, and / or may have a CRC scrambled using a UE identifier that is the same as or different from the receiving UE (therefore, the DCI may have been assigned to or intended for use by the receiving UE or another UE). Due to this uncertainty regarding each PDCCH, from the UE's perspective, a PDCCH can be referred to as a PDCCH candidate. Therefore, a PDCCH candidate can be or may include a PDCCH with a DCI format, or a scrambled CRC, or other parameters or configurations that may or may not match what the UE is monitoring or attempting to detect.
[0029] As an illustrative example, PDCCH monitoring may include, for example, demodulating the received signal and decoding the demodulated PDCCH or DCI, for instance, to detect whether (or not) the DCI is allocated to or intended for use by the UE. Therefore, decoding of the downlink control information (DCI) can use blind decoding, where the UE may perform several decoding attempts on several physical downlink control channel (PDCCH) candidates for several defined DCI formats that the UE is monitoring. Monitoring may also include performing CRC checks on the decoded PDCCH. To receive the DCI on the PDCCH, the UE monitors a set of PDCCH candidates at one or more configured monitoring times (times within one or more time slots where the PDCCH will be transmitted) in one or more CORESETs, according to a search space set configuration. For example, the UE may monitor multiple PDCCH candidates based on one or more DCI formats and / or based on its UE identifier.
[0030] Furthermore, network nodes (gNBs or BSs) can use Transmission Configuration Indicator (TCI) states within a control resource set (or CORESET) to provide beam indication to the UE. The beam indication identifies the beam the UE should use for uplink and / or downlink communication with the network node or gNB. Each TCI state can be configured with or associated with a transmit / receive beam pair. Therefore, each TCI state can be associated with a specific beam or a specific reference signal. For example, TCI state 1 can be associated with (or can be used to indicate) CSI-RS#5, TCI state 2 can be associated with CSI-RS#9, and so on (where CSI-RS#5 and CSI-RS#9 can be DL reference signals transmitted by the gNB). Thus, in this way, each TCI state can be associated with a specific reference signal and / or a specific beam (or the TCI state can indicate a specific reference signal and / or a specific beam). For example, for data transmission via the Physical Downlink Shared Channel (PDSCH) and / or via the Physical Uplink Shared Channel (PUSCH), the UE can be configured with 128 candidate TCI states by the gNB via Radio Resource Control (RRC) messages. The gNB can then configure up to, for example, eight (or other numbers) active TCI states for the UE via the MAC (Media Access Control) CE, which can be carried (or attached) to the DL (downlink) data transmission to the UE via the PDSCH. Thus, in this way, the gNB can send an activation message to activate, for example, eight indicated TCI states from the 128 candidate TCI states (within the UE). The network node can request the UE to use the beam associated with any of these eight (or other) active TCI states for communication with the network node or the gNB (e.g., for sending or receiving data). Dynamically (e.g., as provided in the downlink control information / DCI for each subframe or time slot), the gNB may indicate the selection of one of the active TCI states (and thus identify the selected beam) for the UE to use for uplink or downlink data communication (e.g., via PDSCH and / or PUSCH for scheduled uplink (UL) or downlink (DL) communication). The DCI (which, in at least some cases, may identify the selected active TCI state for the UE to use for communication) may be provided in, for example, the PDCCH (Physical Downlink Control Channel) sent to the UE as part of each time slot or subframe.In this way, in some cases, DCI can be used to provide fast beam indication, which indicates the selected TCI state (e.g., the TCI state among multiple active TCI states) associated with a reference signal or beam that will be used by the UE for UL or DL data communication with the network node (BS or gNB).
[0031] The UE can also receive control information (e.g., via Radio Resource Control (RRC) messages) indicating the selected TCI state (and therefore, beam) to be used by the UE to receive PDCCH for each CORESET. Thus, each CORESET can be configured with a TCI state. For example, the UE can receive control information indicating that CSI-RS#6 should be used for CORESET#1 and CSI-RS#9 should be used for CORESET#2. Therefore, when monitoring CORESET#1 for possible PDCCH transmission, the UE will use the beam associated with CSI-RS#6, and when monitoring CORESET#2 for possible PDCCH transmission, the UE will use the beam associated with CSI-RS#9.
[0032] NR version 16 provides support for multiple transport receiver points (TRPs) (or multiple transport points) for downlink in a single cell. This provides the possibility that downlink data can be transmitted simultaneously from two different transport points (TRPs) via the PDSCH (Physical Downlink Shared Channel). These two different transport points (TRPs) can be geographically separated but are provided within the same cell (e.g., transmission of downlink data from two different radio heads or other nodes to the UE within the cell).
[0033] For single-cell, single-DCI-based multi-TRP transmission, a single DCI schedules a single PDSCH, which can support multiple modes of PDSCH transmission. In a single-DCI-based multi-TRP SDM (Space Division Multiplexing) transmission scheme, multiple layers of PDSCH are scheduled by a single DCI, where different PDSCH layers can be transmitted from different TRPs. However, multiple TRPs will transmit a single transport block. Similarly, several other single-DCI-based multi-TRP transmission schemes exist, which follow the FDM (Frequency Division Multiplexing) and TDM (Time Division Multiplexing) methods of multi-TRP transmission.
[0034] For single-cell, multi-DCI, multi-TRP transmission, there is one PDSCH (Physical Downlink Shared Channel, or Downlink Data Channel), and associated transport blocks are sent from each TRP. Each PDSCH is also scheduled by a separate DCI carried by a separate PDCCH (Physical Downlink Control Channel). Since the two PDSCHs can be received independently by the UE, there can be two transport blocks, one from each TRP. Therefore, there will also be two separate HARQ feedbacks (ACK / NAK) from the UE. These can be joint HARQ feedbacks via a single PUCCH (Physical Uplink Control Channel), or separate HARQ feedbacks sent via separate PUCCHs.
[0035] Figure 2 This is an illustration of single-cell multiple DCI multiple TRP transmission according to an example embodiment. UE 210 can communicate with two TRPs (which may be geographically separated) within the cell. TRP#1 can send DCI-1 (provided via PDCCH-1, not shown) and PDSCH-1, where DCI-1 can schedule downlink PDSCH transmissions from TRP#1 to UE 210 and uplink PUSCH transmissions from UE 210 to TRP#1. Furthermore, separate HARQ feedback (ACK / NAK) is shown for each TRP. Therefore, in this example, TRP#1 can provide or send DCI-1 and PDSCH-1 to UE 210 via line 220, and TRP#1 can receive separate HARQ feedback from UE 210 via line 222. Similarly, TRP#2 can provide or send DCI-2 and PDSCH-2 to UE 210 via line 224, and TRP#2 can receive individual HARQ feedback from UE 210 via line 226. Figure 2 Only two TRPs may be illustrated, but it should be understood that in any of the examples herein, a TRP (212 and / or 214) may include one or more TRPs (e.g., a set of TRPs), each providing one or more reference signals (RS) and one or more CORESETs. As an example, in some embodiments, TRP may refer to a set of TRPs.
[0036] Each CORESET can include a value (0 or 1) configured as the CORESETPoolIndex via RRC signaling sent to the UE. Multiple CORESETs can exist within a PDCCH configuration, and each CORESET can be associated with one of these CORESETPoolIndex values. The CORESETPoolIndex values thus divide the CORESETs into (e.g., two) distinct groups. A group of CORESETs is considered a set of uplink and downlink channels (PDCCH / PDSCH / PUSCH / PUCCH) scheduled for the UE for each TRP. When the UE has more than one value configured for its CORESETPoolIndex, the UE assumes multi-TRP operation (intra-cell) based on multiple DCIs, which includes: the UE monitoring DCIs from multiple TRPs (which can be different radio heads within the cell), and receiving data scheduled by the corresponding DCIs, as... Figure 2 As shown. Therefore, in this case, based on the CORESETPoolIndex having two values (e.g., some CORESETs of the UE have a CORESETPoolIndex set to 0, and some CORESETs of the UE are set to 1, as a way to group CORESETs into different groups for multi-TRP operation), various aspects or parameters of multi-TRP operation can be defined or configured for each TRP. These aspects or parameters of multi-TRP operation can be defined or configured individually for each TRP, including, for example, how PDSCH scrambling is performed, PDCCH monitoring, rate matching, individual or combined HARQ feedback from the UE for both TRPs, scheduling of in-order / out-of-order data for transmission, and other multi-TRP operation parameters or settings.
[0037] Currently in 3GPP, two different approaches are discussed regarding possible inter-cell operations (UE monitoring and / or receiving signals from two different cells) within the beam management framework: 1) inter-cell multi-TRP operations using a multi-TRP framework (which uses the CORESETPoolIndex value), where the UE can be configured to monitor signals from at least the serving cell and the non-serving cell; and 2) (L1 / L2 (Layer 1 / Layer 2) centered) inter-cell "mobility," where the UE can be configured to receive signals / channels from both the serving and non-serving cells. Cells used as part of the inter-cell operation are labeled as serving and non-serving cells. However, in some scenarios, L1 / L2 centered inter-cell mobility may not use or configure the CORESETPoolIndex value. However, as further described herein, it may be desirable for the UE to perform (or be able to perform) multi-TRP operations, even when the CORESETPoolIndex value may not be configured, at least for some scenarios or applications.
[0038] In version 17, the current Rel 16 multi-TRP framework can be extended for inter-cell multi-TRP operations. In one possible operating mode, the serving cell configuration includes CORESETs associated with non-serving cells, and inter-cell operations are facilitated by assigning different CORESETPoolIndex values to the non-serving cell CORESETs. In this framework, the UE assumes that CORESETs configured with the same CORESETPoolIndex value are assumed to be coordinated, thus CORESETs configured with the same CORESETPoolIndex do not schedule overlapping transmissions.
[0039] In addition, inter-cell operations are also considered in another approach, which aims to specify inter-cell operations / mobility centered on operations L1 / L2. The existing discussion is to support the measurement of non-serving cell signals (DL reference signals, such as SSB / CSI-RS) within the beam management framework, as well as to further receive downlink channels (PDCCH, PDSCH) from non-serving cells and send UL channels (PUSCH, PUCCH) to non-serving cells.
[0040] From a downlink perspective, receiving PDCCH from a non-serving cell may require support for beam indication of the CORESET, such as activation of the TCI state for the CORESET, where the TCI state is configured with the QCL source reference signal of the non-serving cell. To allow the UE to distinguish whether a DL reference signal / channel is transmitted from (or associated with) a non-serving cell, a PCI (Physical Cell Identifier for Cell) value can be used; for example, the PCI value can be configured for each corresponding DL reference signal / channel. Other association methods may also be used. In the case of inter-cell (or multi-cell) multi-TRP operation, the UE can typically be explicitly configured (using RRC) to indicate multi-TRP operation via higher-layer parameters (e.g., utilizing the CORESETPoolIndex value). However, in the case of L1 / L2-centric inter-cell operation / mobility, it is not yet defined how to configure multi-TRP support (how the UE will be configured to perform multi-TRP operation for this use case), or how the UE can determine that it is being configured for multi-TRP operation, where the UE can be assumed to be simultaneously monitoring PDCCH from multiple cells.
[0041] Therefore, according to example embodiments, the following techniques are provided that allow a UE to determine when it is configured for inter-cell multi-DCI based multi-TRP operations (and therefore when it should perform or operate according to inter-cell multi-DCI based multi-TRP operations), for example, even in the absence of explicit higher-layer configuration for such multi-TRP operations (e.g., even without configuring CORESETPoolIndex values for different CORESETs, which would typically configure the UE for multi-DCI based multi-TRP operations).
[0042] Figure 3 This is a diagram illustrating multi-TRP transmission between (or multiple cells) based on multiple DCIs, according to an example embodiment. UE 210 can communicate with multiple TRPs provided in multiple cells. Each cell can be identified by a PCI. TRP#1 (212) is provided in cell 1, which may be the serving cell. One or more cell groups may also exist, where each cell group may include one or more non-serving cells. For example, cell group 310 may include TRPs of multiple cells (e.g., gNB, radio headend, or other devices or nodes), such as TRP#2 (214A, in cell 2), TRP#3 (214B, in cell 3), and TRP#4 (214C, in cell 4).
[0043] Figure 4This is a flowchart illustrating the operation of a user equipment (or UE) according to an example embodiment. Operation 410 includes the user equipment (UE) within the wireless network determining, based on the following, to perform inter-cell multi-transmitter receive point (multi-TRP) operation for the user equipment based on multiple downlink control information (multi-DCI): Operation 420 includes the user equipment receiving from a network node a Transmission Configuration Index (TCI) state for multiple control resource sets (CORESETs), wherein the TCI states for the multiple CORESETs are associated with multiple cells or multiple cell groups having different physical cell identifiers (PCIs), wherein the TCI states indicate quasi-co-location (QCL) characteristics (e.g., beamforming), which the quasi-co-location (QCL) characteristics will be used by the user equipment to receive physical downlink control channels (PDCCHs) associated with multiple cells or multiple cell groups having different PCIs, wherein the multiple cells or multiple cell groups include at least a serving cell and at least one non-serving cell for the user equipment. Furthermore, operation 430 includes the user equipment determining that at least one of the following conditions exists: 1) multi-DCI-based multi-TRP related higher-layer parameters have been configured to the user equipment; 2) the default mode of multi-TRP operation has been configured to the user equipment; or 3) the user equipment has received control information indicating that the Physical Downlink Shared Channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values is activated. Furthermore, operation 440 includes, based on the determination to perform multi-DCI-based inter-cell multi-TRP operation, the user equipment performs inter-cell multi-DCI-based multi-TRP operation for cells from multiple cells or for cells from multiple cell groups.
[0044] Therefore, as Figure 4 As described in the flowchart, the UE determines (in operation 410) whether to perform inter-cell (or multi-cell) multi-DCI-based multi-TRP operation based on the following two conditions: receiving operation 420, and at least one of three conditions indicating the existence of operation 430. Then, in Figure 4 Operation 440, based on determination (in operation 410), performs inter-cell multi-TRP operation for user equipment, performing inter-cell multi-DCI based multi-TRP operation for cells from multiple cells or for cells from multiple cell groups.
[0045] For example, based on Figure 4The example flowchart shows that the UE can perform inter-cell multi-DCI based multi-TRP operations for cells from multiple cells or for cells from multiple cell groups, where the UE has not been explicitly configured to set the CORESETPoolIndex value for the UE to more than one value for CORESET. In this way, for example, for some applications or use cases such as (by way of example) L1 / L2-centric inter-cell mobility (which does not use or configure the CORESETPoolIndex value), the UE can determine to perform inter-cell multi-DCI based multi-TRP operations (e.g., even when higher-layer signaling (such as CORESETPoolIndex) is not used by such applications or use cases to configure multi-DCI based multi-TRP).
[0046] Furthermore, according to the example embodiment, for multiple cells or for cells from multiple cell groups, performing inter-cell multi-DCI based multi-TRP operations may include: with respect to a first TRP including the serving cell and a second TRP including at least one non-serving cell, the UE performs at least one of the following:
[0047] 1) Individual channel monitoring, data processing, and / or control and data reception and / or transmission of the channel set (PUCCH / PUSCH / PDSCH / PDCCH) (or one or more of these channels) corresponding to each of the serving cell and at least one non-serving cell;
[0048] 2) Monitor downlink control information (DCI) on separate PDCCHs from each of the serving cell and at least one non-serving cell;
[0049] 3) For each of the serving cell and at least one non-serving cell, receive downlink data scheduled by the DCI and received via the corresponding PDSCH channel;
[0050] 4) Descramble the PDSCH channel separately for PDSCH from the serving cell and at least one non-serving cell;
[0051] 5) For each of the serving cell and at least one non-serving cell, perform separate PUSCH scheduling for uplink data transmission based on the corresponding DCI; or send hybrid ARQ (HARQ) feedback for the serving cell and non-serving cell.
[0052] 6) Using the corresponding BFD-RS sets (q0-0 and q0-1) determined based on these methods for the serving cell and non-serving cells, perform (e.g., separate) beam failure detection (and recovery) for each TRP. As an example, the UE may determine to perform beam failure detection for a first TRP including the serving cell and a second TRP including at least one non-serving cell, using the corresponding BFD-RS (beam failure detection reference signals) sets (e.g., q0-0 for the first TRP and q0-1 for the second TRP). To determine the BFD-RS (which may be one or more of CSI-RS and / or SSBs) to be included in the corresponding set for each TRP, the UE may base it on PCI as described herein. When CORESETPoolIndex is not explicitly configured, the UE may determine to perform beam failure detection based on multiple q0 sets. As another example, when the UE has determined to perform (inter-cell) multi-DCI-based multi-TRP operation as described herein, as if the CORESETPoolIndex value were configured (e.g., based on two or more different values of PCI group or PCI), the UE can determine that: the first BFD-RS includes the RS indicated by the active TCI state of the CORESET associated with CORESETPoolIndex = 0, and the second BFD-RS includes the RS indicated by the active TCI state of the CORESET associated with CORESETPoolIndex = 1. When the UE determines not to perform inter-cell multi-DCI-based multi-TRP operation, it can determine to use a set of BFD-RS (e.g., set q0).
[0053] Performing inter-cell multi-DCI based multi-TRP operations may include or involve one or more actions or operations, and some examples of these operations are listed above by way of illustrative examples. Performing inter-cell multi-DCI based multi-TRP operations may include different and / or additional operations. Furthermore, as noted, inter-cell multi-DCI based multi-TRP operations can be performed by the UE even if the UE has not been explicitly configured for this operating mode by setting the CORESETPoolIndex value. Furthermore, for example, even if the user equipment has not been explicitly configured for multi-TRP operations by setting the CORESETPoolIndex value to more than one value for CORESET, the inter-cell multi-DCI based multi-TRP operations (operation 440) performed by the user equipment (UE) for cells from multiple cells or for cells from multiple cell groups, based on the lowest PCI of the two PCIs representing CORESETPoolIndex = 0 and the highest PCI of the two PCIs representing CORESETPoolIndex = 1, can be performed by the user equipment as if the CORESETPoolIndex value were configured.
[0054] Similarly, for example, other allocations can be made using PCI or PCI groups to different CORESETPoolIndex values, such as:
[0055] The highest PCI among the two PCIs is represented by CORESETPoolIndex = 0, and the lowest PCI among the two PCIs is represented by CORESETPoolIndex = 1;
[0056] The serving cell PCI in the two PCIs is represented by CORESETPoolIndex=0, and the non-serving cell PCI in the two PCIs is represented by CORESETPoolIndex=1;
[0057] The predefined PCI in the two PCIs is represented by CORESETPoolIndex = 0, and the remaining PCI in the two PCIs is represented by CORESETPoolIndex = 1;
[0058] The first cell group (e.g., the cell group with the lowest or highest cell group index) is represented by CORESETPoolIndex = 0, and the second cell group is represented by CORESETPoolIndex = 1.
[0059] In addition, different technologies can be used to notify (or transmit) the PCI for each cell group in the cell group to the UE, such as, for example:
[0060] 1) The UE receives a message or signaling from the network node, which indicates the PCI assigned to the cell group;
[0061] 2) The UE receives a measurement configuration from the network node, which also indicates the PCIs assigned to the cell group. Therefore, various messages or signaling can be used to explicitly indicate the PCIs included in one or more cell groups; and / or
[0062] 3) The UE receives a Media Access Control-Control Unit (MAC-CE) indicating PDSCH TCI state activation for two different CORESETPoolIndex values, wherein each TCI state activation is associated with a PCI; and the UE determines a cell group comprising the PCIs associated with the TCI state activations received via the MAC-CE for the CORESETPoolIndex values. Therefore, in this way, the PCI for a cell group can be determined based on the MAC-CE indicating PDSCH TCI state activation and then assigning the associated PCI states of these TCI state activations to the cell group.
[0063] Furthermore, after performing inter-cell multi-DCI based multi-TRP operations, conditions may change, potentially causing the UE to change its operating mode from multi-TRP operation to single-TRP operation. For example, this could include: the UE receiving updated TCI states from a network node for multiple CORESETs, where the TCI states of multiple CORESETs are associated with only one PCI or one cell group; and, based on the received updated TCI states, changing the UE's operation from inter-cell multi-DCI based multi-TRP operation to single-TRP operation.
[0064] Furthermore, in the example embodiment, in response to the UE receiving a TCI state activation for CORESET, wherein different TCI states for the corresponding CORESET are associated with at least two different physical cell identifiers (PCIs), indicating (or indicating to the UE) inter-cell multi-DCI based multi-TRP operation, the UE performs or operates as if it had already configured the CORESETPoolIndex value in the ControlResourceSet (CORESET), and the UE determines the CORESET associated with the serving cell PCI as the CORESET with CORESETPoolIndex = 0.
[0065] In an example embodiment, when a CORESET is not associated with a PCI (e.g., the DL RS (Downlink Reference Signal) indicated by the active TCI state for the CORESET is not explicitly associated with a PCI, or the CORESET is not associated through other configurations), the UE can determine the CORESET as a CORESET with CORESETPoolIndex = 0. The TCI state can be associated with a serving cell index, which can further be associated with a PCI. Through this association, the UE can determine that the CORESET is associated with the serving cell PCI, and the UE can determine the CORESET (or multiple CORESETs) as a CORESET with CORESETPoolIndex = 0.
[0066] Further details and illustrative examples will now be described.
[0067] The UE receives a configuration that provides information related to non-serving cell measurements, including details for measuring the non-serving cell's SSB. In one variation, this configuration may carry additional information indicating whether the non-serving cell measurements are used for multi-TRP operation or another operating mode (e.g., L1 / L2-centric mobility). In another variation (also mentioned below), this information may carry additional information regarding implicit / explicit grouping of non-serving cells, where grouping can be coordinated during PDCCH and PDSCH transmission (ensuring only one cell is active at a given time to serve the UE).
[0068] For grouping non-serving cells (grouping PCIs), DL reference signals (RS) (e.g., synchronization signal blocks (SSBs)) can be grouped, where each group of DL RS is associated with multiple PCIs, which can be understood as a PCI group.
[0069] In one example, the UE may assume that each reception of PDCCH / PDSCH or transmission of PUCCH / PUSCH comes from one of the non-serving cells.
[0070] The UE can receive further configuration / instructions for performing beam measurements and reporting non-serving cell SSB and CSI-RS beams. In one example, the network can configure CSI reporting / beam reporting configurations for each non-serving cell.
[0071] Understanding Multi-TRP Operations
[0072] A) For UEs that support multiple TRP operations (based on UE capabilities) and non-serving cell beam measurement and reporting, the UE may assume (or determine to perform) multiple TRP operations based on the following (e.g., such as when CORESETPoolIndex is not configured).
[0073] If the UE receives a beam activation / indication for the CORESET, i.e., the DL reference signal (RS) indicated by the active TCI state (beam of the CORESET) is associated with multiple cells or multiple cell groups (e.g., for a CORESET associated with at least two different PCIs (e.g., the serving cell and another cell) or PCI groups), and the UE supports option 1, option 2 or option 3 (as indicated below).
[0074] Option 1: If (e.g.) at least one of the following traditional configurations (higher-layer parameters) is configured / indicated, or if more than one higher-layer multi-TRP related parameter is configured for the UE, then for a specific parameter type, such as: 1) more than three CORESETs are configured to the UE for DL BWP (Downlink Bandwidth Partial). In one example, a CORESET with an index higher than the third CORESET index in sequence is considered to be associated with other CORESETPoolindex values (e.g., value = 1); 2) more than one scrambling sequence is configured to the UE; 3) more than one rate matching pattern for LTE-CRS is configured to the UE; 4) joint / separate HARQ reporting is configured to the UE; 5) any other multi-TRP related higher-layer parameters are configured to the UE.
[0075] Option 2: The default mode for multi-TRP operation has been configured for the user equipment. In this option, the traditional RRC operation (without higher-layer multi-TRP operation) parameters associated with multi-TRP operation can be left unconfigured / indicated, but the default operation mode can be defined / assumed by the UE without relying on higher-layer parameters. For example, the default scrambling sequence used for PDSCH can be defined as the PCI associated with the TCI state of PDSCH, and the default HARQ operation can assume a separate feedback mode, etc.
[0076] Option 3: The UE has received control information indicating that the Physical Downlink Shared Channel (PDSCH) TCI state is active corresponding to two different CORESETPoolIndex values. Therefore, for example, in this option, the UE receives a MAC-CE command for the activation of the PDSCH TCI state corresponding to the two different CORESETPoolIndex values (indicated in the MAC-CE command defined for Rel-16). For example, a CORESET packet (associated with different PCIs or PCI packets / cell groups) can be determined or derived based on the PCI associated with the active TCI state of the PDSCH within a given CORESETPoolIndex (indicated in the MAC-CE). This can also be used to more dynamically update any PCI packets (cell groups) or PCIs associated with a CORESETPoolIndex (not necessarily dependent on the PCI packets from above).
[0077] B) When the UE determines that it supports multi-TRP operations based on the above, by following the corresponding conventional operations defined for CORESETPoolIndex, the UE can assume that each CORESETPoolIndex value corresponding to a PCI (or PCI group) follows the conventionally defined multi-TRP operation steps. In other words, when the UE determines (or confirms) inter-cell multi-DCI based multi-TRP operations based on the above description, the UE can perform inter-cell multi-DCI based multi-TRP operations for cells from multiple cells or for cells from multiple cell groups, for example, even if the UE has not been explicitly configured for such inter-cell multi-DCI based multi-TRP operations via higher-layer signaling (e.g., it may not have performed setting the CORESETPoolIndex value to more than one value for the CORESET for the UE). The UE's performance of inter-cell multi-DCI based multi-TRP operations may include, for example, PDCCH monitoring, PDSCH scrambling, rate matching, HARQ, PUSCH scheduling, in-order / out-of-order, default beam assumption, and other actions for each TRP.
[0078] C) Depending on the number of PCIs associated with CORESET, additional features or considerations may be applied.
[0079] If CORESET is associated with only two PCIs: the lowest (or serving cell / highest / predefined) PCI of the two PCIs can represent CORESETPoolIndex = 0, and the other PCIs can represent CORESETPoolIndex = 1. In this option, the UE performs or assumes multi-TRP operation as if the CORESETPoolIndex value were configured without receiving an explicit indication for CORESET. As an example, a PDCCH reception associated with the first PCI can be considered to be from CORESETPoolIndex = 0, and a PDCCH reception on the second PCI (or a PDCCH reception associated with the second PCI) can be considered to be from CORESETPoolIndex = 1.
[0080] If CORESET is associated with more than two PCIs: In one variation, the UE can assume more than two CORESETPoolIndex values corresponding to different PCIs, extending the traditional framework to receive more than two PDCCH / PDSCHs. In another variation of non-serving cell packets (PCI packets / cell groups) (where the configuration provides cell or PCI packets), the lowest indexed PCI group among the two PCI groups can represent CORESETPoolIndex = 0, and the other PCI groups can represent CORESETPoolIndex = 1.
[0081] When updating or replacing a PCI group by activating MAC-CE (option 3 above) based on the TCI status used for PDSCH, a separate MAC-CE command corresponding to a different CORESETPoolIndex can be received and directly used as the corresponding CORESETPoolIndex value.
[0082] D) Possibility of Single TRP (S-TRP) Operation without RRC Reconfiguration. When the active TCI state for (multiple) CORESETs or the DL RS indicated by multiple states (beams) is associated with only one PCI (or PCI group), the UE can assume (or revert to) single TRP operation based on the beam activation / indication for the CORESET. For example, the UE can receive updated TCI states for multiple CORESETs from a network node (e.g., gNB), where the TCI states for multiple CORESETs are associated with only one PCI or one cell group; and, based on the received updated TCI states, the UE can switch or change (or revert to) single TRP operation between cells based on multiple DCIs.
[0083] Figure 5This is an illustration of operation according to an example embodiment. UE 210 is shown and can communicate with one or more cells, including serving cell 530 and / or one or more non-serving cells 532. At 510, serving cell 530 and non-serving cells can coordinate regarding L1 measurements, such as coordinating or determining CSI-RS or SSB beam measurement reporting configurations for UE 210. At 512, serving cell 530 can provide or send non-serving cell configurations for measurements to UE 210, including use cases (e.g., L1 / L2-centric inter-cell operation / mobility, or other use cases for multi-TRP); it can also indicate to UE 210 at message 512 the PCIs assigned to a cell group (PCI group). At 514, UE 210 performs non-serving cell beam measurements and reports to serving cell 530. At 516, serving cell 530 and (multiple) non-serving cells can coordinate to determine, for example, CORESET allocations between serving cell and non-serving cells.
[0084] At 518, the UE receives a Transmission Configuration Index (TCI) status for multiple Control Resource Sets (CORESETs), wherein the TCI status for multiple CORESETs is associated with multiple cells having different Physical Cell Identifiers (PCIs) or with multiple cell groups. For example, the TCI status indicates Quasi-Co-location (QCL) characteristics, which will be used by the user equipment to receive the Physical Downlink Control Channel (PDCCH). The PDCCH is associated with at least two different cells having different PCIs or with at least two different cell groups, wherein the multiple cells or cell groups include at least the serving cell and at least one non-serving cell for the user equipment.
[0085] At 520, UE 210 determines that at least one of the following three options or conditions exists: 1) Multi-DCI-based multi-TRP related higher-layer parameters have been configured to the user equipment; 2) The default mode for multi-TRP operation has been configured to the UE; or 3) The UE has received control information (e.g., MAC-CE) indicating that the Physical Downlink Shared Channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values is active. Operation 522 may include: determining the timing advance (TA) for each TRP.
[0086] Operation 524 may include: UE 210 performing inter-cell multi-DCI based multi-TRP operations for multiple cells (including serving cell 530 and non-serving cell 532). Therefore, for example, even if UE 210 is not explicitly configured for multi-TRP operations by setting the CORESETPoolIndex value to more than one value for CORESET, UE 210 may perform inter-cell multi-DCI based multi-TRP operations as if the CORESETPoolIndex value were configured, for example, based on the lowest of the two PCIs representing CORESETPoolIndex = 0, and the highest of the two PCIs representing CORESETPoolIndex = 1.
[0087] Some other examples will be described:
[0088] Example 1: An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to at least: determine, by a user equipment within a wireless network, to perform inter-cell multi-transmitter receive point (multi-TRP) operation based on multiple downlink control information (multi-DCI) for the user equipment: the user equipment receives from a network node a Transmission Configuration Index (TCI) state for multiple Control Resource Sets (CORESETs), wherein the TCI state for the multiple CORESETs is associated with multiple cells having different Physical Cell Identifiers (PCIs) or with multiple cell groups, wherein the TCI state indicates a Quasi-Co-location (QCL) characteristic that will be used by the user equipment to receive data from multiple cells having different PCIs. The associated or related physical downlink control channel (PDCCH) to multiple cell groups, wherein the multiple cells or multiple cell groups include at least a serving cell and at least one non-serving cell for the user equipment; and the user equipment determines that at least one of the following conditions exists: 1) multi-DCI-based multi-TRP related higher-layer parameters have been configured to the user equipment; 2) the default mode of multi-TRP operation has been configured to the user equipment; or 3) the user equipment has received control information indicating the activation of the physical downlink shared channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values; and the user equipment determines to perform inter-cell multi-DCI-based multi-TRP operation, for cells from multiple cells or for cells from multiple cell groups, and performs inter-cell multi-DCI-based multi-TRP operation.
[0089] Example 2: The apparatus according to Example 1, wherein computer program code is configured such that at least one processor together causes the apparatus to perform inter-cell multi-DCI based multi-TRP operations by a user equipment for cells from a plurality of cells or for cells from a plurality of cell groups, wherein the user equipment is not explicitly configured for inter-cell multi-DCI based multi-TRP operations by setting the CORESETPoolIndex value for the user equipment to more than one value for CORESET.
[0090] Example 3: An apparatus according to any one of Examples 1-2, wherein computer program code is configured, together with at least one processor, to cause the apparatus to perform inter-cell multi-DCI-based multi-TRP operations for the cell from one of the plurality of cells or for the cell from one of the plurality of cell groups, comprising: the computer program code being configured, together with the at least one processor, to cause the apparatus, with respect to a first TRP including the serving cell and a second TRP including the at least one non-serving cell, to perform at least one of the following: separate channel monitoring, data processing, and / or control and separate reception and / or transmission of data with respect to the channel set (PUCCH / PUSCH / PDSCH / PDCCH) corresponding to each of the serving cell and the at least one non-serving cell; respectively Monitor downlink control information (DCI) on individual PDCCHs from each of the serving cell and the at least one non-serving cell; receive downlink data scheduled by the DCI and received via the corresponding PDSCH channel for each of the serving cell and the at least one non-serving cell; descramble the PDSCH channels for the PDSCHs from the serving cell and the at least one non-serving cell respectively; perform individual PUSCH scheduling for uplink data transmission based on the corresponding DCI for each of the serving cell and the at least one non-serving cell; perform individual beam failure detection and / or beam failure recovery for the serving cell and for the non-serving cell; or send hybrid ARQ (HARQ) feedback for the serving cell and the non-serving cell.
[0091] Example 4: An apparatus according to any one of Examples 1-3, wherein computer program code is configured, together with at least one processor, to cause the apparatus to perform inter-cell multi-DCI based multi-TRP operations by the user equipment for the cell from the plurality of cells or for the cell from the plurality of cell groups, as if the CORESETPoolIndex value were configured by the user equipment, even if the user equipment has not been explicitly configured for multi-TRP operations by setting the CORESETPoolIndex value to more than one value for CORESET: 1) the lowest of the two PCIs indicates that the CORESETPoolIndex = 0, and the two PCIs 1) The highest PCI in the two PCIs indicates CORESETPoolIndex = 1; 2) The highest PCI in the two PCIs indicates CORESETPoolIndex = 0, and the lowest PCI in the two PCIs indicates CORESETPoolIndex = 1; 3) The serving cell PCI in the two PCIs indicates CORESETPoolIndex = 0, and the non-serving cell PCI in the two PCIs indicates CORESETPoolIndex = 1; or 4) The predefined PCI in the two PCIs indicates CORESETPoolIndex = 0, and the remaining PCI in the two PCIs indicates CORESETPoolIndex = 1.
[0092] Example 5: An apparatus according to any one of Examples 1-4, wherein computer program code is configured, together with at least one processor, to cause the apparatus to perform inter-cell multi-DCI based multi-TRP operations for the user equipment for the cell from the plurality of cells or for the cell from the plurality of cell groups, which is performed by the user equipment based on more than two CORESETPoolIndex values corresponding to different PCIs or different cell groups.
[0093] Example 6: An apparatus according to any one of Examples 1-5, wherein the first cell group represents CORESETPoolIndex = 0 and the second cell group represents CORESETPoolIndex = 1.
[0094] Example 7: An apparatus according to any one of Examples 1-6, wherein the first cell group and the second cell group each include a plurality of non-serving cells.
[0095] Example 8: An apparatus according to any one of Examples 1-7, wherein 3) the user equipment has received control information indicating activation of the Physical Downlink Shared Channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values, including: the user equipment has received a Media Access Control-Control Unit (MAC-CE) indicating activation of the PDSCH TCI state for two different CORESETPoolIndex values, and wherein each TCI state activation is associated with a PCI; the method further includes: the user equipment determining a cell group including the PCIs associated with the TCI state activations for the CORESETPoolIndex values received via the MAC-CE.
[0096] Example 9: An apparatus according to any one of Examples 1-8, further comprising: computer program code configured together with at least one processor to cause the apparatus to: receive a message or signaling from a network node by a user equipment, the message or signaling indicating a PCI assigned to a cell group.
[0097] Example 10: An apparatus according to any one of Examples 1-9, further comprising: computer program code configured together with at least one processor to cause the apparatus: to receive a measurement configuration from a network node by a user equipment, the measurement configuration further indicating a PCI assigned to a cell group.
[0098] Example 11: An apparatus according to any one of Examples 1-10, wherein computer program code is configured, together with at least one processor, to cause the apparatus to: further perform, by the user equipment, receiving, from a network node, updated TCI states for multiple CORESETs, wherein the TCI states for multiple CORESETs are associated with only one PCI or one cell group; and, based on the received updated TCI states, changing the operation of the user equipment from inter-cell multi-DCI based multi-TRP operation to single-TRP operation.
[0099] Example 12: An apparatus according to any one of Examples 1-11, wherein, in response to the user equipment receiving a TCI state activation for a CORESET, wherein different TCI states for the corresponding CORESET are associated with at least two different physical cell identifiers (PCIs) and indicating inter-cell multi-TRP operation based on multiple DCIs, the user equipment performs an operation as if it had been configured with a CORESETPoolIndex value in a ControlResourceSet (CORESET), and the user equipment determines the CORESET associated with the serving cell PCI as a CORESET with CORESETPoolIndex = 0.
[0100] Example 13: An apparatus according to any one of Examples 1-12, further comprising: computer program code configured together with at least one processor to cause the apparatus to: in response to a user equipment receiving a TCI state activation for a CORESET, wherein different TCI states for a corresponding CORESET are associated with at least two different physical cell identifiers (PCIs), perform beam failure detection by the user equipment using a corresponding set of BFD-RS (beam failure detection reference signals), wherein the reference signal (RS) for the corresponding set of BFD-RS is determined based on the associated PCI values for the serving cell and at least one non-serving cell of the CORESET.
[0101] Example 14: An apparatus according to any one of Examples 1-13, wherein 1) multi-TRP related higher-layer parameters based on multiple DCI have been configured to the user equipment including one or more of the following: more than three CORESETs are configured to the user equipment for the downlink bandwidth portion (DL BWP); more than one scrambling sequence is configured to the user equipment; more than one rate matching pattern for LTE-CRS (LTE cell-specific reference signal) is configured to the user equipment; joint or separate HARQ feedback reports are configured to the user equipment; and / or multi-TRP related higher-layer parameters are configured to the user equipment.
[0102] Example 15: An apparatus according to any one of Examples 1-14, wherein 2) the default mode of multi-TRP operation has been configured for the user equipment to include one or more of the following behaviors at the user equipment: the user equipment expects non-overlapping PDSCH reception; the user equipment expects overlapping and partially overlapping PDSCH reception, which utilizes a scrambling sequence defined based on the PCI applicable to the associated CORESETPoolIndex value; the user equipment operates using separate HARQ feedback operation; the user equipment operates under predefined assumptions for blind decoding limit calculation; the user equipment assumes rate matching on the joint of CRS resources configured for both serving and non-serving cells; the user equipment expects in-order transmission of PDCCH-PDSCH and PDCCH-PUSCH; and / or when conditions are met for multiple CORESETs associated with multiple cells having different Physical Cell Identifiers (PCIs) or with different cell groups, the user equipment follows any other predefined user equipment behavior.
[0103] Example 16: A non-transitory computer-readable storage medium including instructions stored thereon, which, when executed by at least one processor, are configured to cause a computing system to: determine, based on a user equipment within a wireless network, perform inter-cell multi-transmitter receive point (multi-TRP) operations for the user equipment using multiple downlink control information (multi-DCI) based methods: the user equipment receives from a network node Transmission Configuration Index (TCI) states for multiple Control Resource Sets (CORESETs), wherein the TCI states for the multiple CORESETs are associated with multiple cells having different Physical Cell Identifiers (PCIs) or with multiple cell groups, wherein the TCI states indicate Quasi-Co-location (QCL) characteristics that the user equipment will use to receive data associated with multiple cells having different PCIs or with multiple cell groups. The associated physical downlink control channel (PDCCH), wherein multiple cells or multiple cell groups include at least a serving cell and at least one non-serving cell for the user equipment; and the user equipment determines that at least one of the following conditions exists: 1) multi-DCI-based multi-TRP related higher-layer parameters have been configured for the user equipment; 2) the default mode of multi-TRP operation has been configured for the user equipment; or 3) the user equipment has received control information indicating the activation of the physical downlink shared channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values; and the user equipment performs inter-cell multi-DCI-based multi-TRP operation based on determining to perform multi-DCI-based inter-cell multi-TRP operation for cells from multiple cells or for cells from multiple cell groups.
[0104] Example 17: A method comprising: a user equipment in a wireless network determining, based on the following, to perform inter-cell multi-transmitter receive point (multi-TRP) operation for the user equipment based on multiple downlink control information (multi-DCI): the user equipment receiving from a network node Transport Configuration Index (TCI) states for multiple control resource sets (CORESETs), wherein the TCI states for the multiple CORESETs are associated with multiple cells having different physical cell identifiers (PCIs) or with multiple cell groups, wherein the TCI states indicate quasi-co-location (QCL) characteristics that will be used by the user equipment to receive physical downlink control channels (PDCCHs) associated with the multiple cells having different PCIs or with the multiple cell groups. The multiple cells or multiple cell groups include at least a serving cell and at least one non-serving cell for the user equipment; and the user equipment determines that at least one of the following conditions exists: 1) multi-DCI-based multi-TRP related higher-layer parameters have been configured for the user equipment; 2) the default mode of multi-TRP operation has been configured for the user equipment; or 3) the user equipment has received control information indicating the activation of the Physical Downlink Shared Channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values; and the user equipment determines to perform inter-cell multi-DCI-based multi-TRP operation for cells from multiple cells or for cells from multiple cell groups.
[0105] Example 18: According to the method of Example 17, wherein the user equipment performs inter-cell multi-DCI based multi-TRP operation for cells from multiple cells or for cells from multiple cell groups, wherein the user equipment has not been explicitly configured for inter-cell multi-DCI based multi-TRP operation by setting the CORESETPoolIndex value for the user equipment to more than one value for CORESET.
[0106] Example 19: According to any one of Examples 17-18, wherein performing inter-cell multi-DCI-based multi-TRP operation for cells from a plurality of cells or for cells from a plurality of cell groups comprises: the user equipment performing at least one of the following with respect to a first TRP including the serving cell and a second TRP including at least one non-serving cell: separate channel monitoring, data processing, and / or separate reception and / or transmission of control and data with respect to the channel set (PUCCH / PUSCH / PDSCH / PDCCH) corresponding to each of the serving cell and the at least one non-serving cell; and separately monitoring individual PDCCs from each of the serving cell and the at least one non-serving cell. Downlink control information (DCI) on H; receiving downlink data scheduled by DCI and received via the corresponding PDSCH channel for each of the serving cell and the at least one non-serving cell; descrambling the PDSCH channels for the PDSCH from the serving cell and the at least one non-serving cell respectively; performing separate PUSCH scheduling for uplink data transmission based on the corresponding DCI for each of the serving cell and the at least one non-serving cell; performing separate beam failure detection and / or beam failure recovery for the serving cell and the non-serving cell respectively; or sending hybrid ARQ (HARQ) feedback for the serving cell and the non-serving cell.
[0107] Example 20: A method according to any one of Examples 17-19, wherein the user equipment performs inter-cell multi-DCI based multi-TRP operations for the cell from the plurality of cells or for the cell from the plurality of cell groups based on at least one of the following, as if the CORESETPoolIndex value were configured and performed by the user equipment, even if the user equipment has not been explicitly configured for multi-TRP operations by setting the CORESETPoolIndex value to more than one value for CORESET: the lowest of the two PCIs indicates that the CORESETPoolIndex = 0, and the highest of the two PCIs indicates that the CORESETPoolIndex = 0. 1) SETPoolIndex = 1; 2) The highest PCI among the two PCIs indicates that CORESETPoolIndex = 0, and the lowest PCI among the two PCIs indicates that CORESETPoolIndex = 1; 3) The serving cell PCI among the two PCIs indicates that CORESETPoolIndex = 0, and the non-serving cell PCI among the two PCIs indicates that CORESETPoolIndex = 1; or 4) The predefined PCI among the two PCIs indicates that CORESETPoolIndex = 0, and the remaining PCI among the two PCIs indicates that CORESETPoolIndex = 1.
[0108] Example 21: According to any of Examples 17-20, the inter-cell multi-DCI based multi-TRP operation performed by the user equipment for cells from multiple cells or for cells from multiple cell groups is performed by the user equipment based on more than two CORESETPoolIndex values corresponding to different PCIs or different cell groups.
[0109] Example 22: According to any of the methods in Examples 17-21, where the first cell group represents CORESETPoolIndex = 0 and the second cell group represents CORESETPoolIndex = 1.
[0110] Example 23: According to any of the methods in Examples 17-22, where the first cell group and the second cell group each include multiple non-serving cells.
[0111] Example 24: According to any one of Examples 17-23, wherein 3) the user equipment has received control information indicating activation of the Physical Downlink Shared Channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values, the user equipment has received a Media Access Control-Control Unit (MAC-CE) indicating activation of the PDSCH TCI state for two different CORESETPoolIndex values, and wherein each TCI state activation is associated with a PCI; the method further includes: the user equipment determining a cell group, the cell group including the PCIs associated with the TCI state activations for the CORESETPoolIndex values received via the MAC-CE.
[0112] Example 25: The method according to any one of Examples 17-24 further includes: the user equipment receiving from the network node a message or signaling indicating that a PCI has been assigned to a cell group.
[0113] Example 26: The method according to any one of Examples 17-25 further includes: receiving a measurement configuration from a network node by a user equipment, the measurement configuration also indicating the PCI assigned to the cell group.
[0114] Example 27: The method according to any one of Examples 17-26 further includes: receiving updated TCI states for multiple CORESETs from a network node by a user equipment, wherein the TCI states for multiple CORESETs are associated with only one PCI or one cell group; and changing the operation of the user equipment from a multi-TRP operation based on multiple DCIs between cells to a single TRP operation based on the received updated TCI states.
[0115] Example 28: According to any one of Examples 17-27, in response to the user equipment receiving a TCI state activation for CORESET, wherein different TCI states for the corresponding CORESET are associated with at least two different physical cell identifiers (PCIs) and indicate inter-cell multi-TRP operation based on multiple DCIs, the user equipment performs an OR operation as if it had been configured with a CORESETPoolIndex value in ControlResourceSet (CORESET), and the user equipment determines the CORESET associated with the serving cell PCI as a CORESET with CORESETPoolIndex = 0.
[0116] Example 29: According to the method of any one of Examples 17-28, in response to the user equipment receiving a TCI state activation for a CORESET, wherein different TCI states for the corresponding CORESET are associated with at least two different physical cell identifiers (PCIs), the user equipment performs beam failure detection using a corresponding set of BFD-RS (beam failure detection reference signals), wherein the reference signal (RS) for the corresponding set of BFD-RS is determined based on the associated PCI values for the serving cell and at least one non-serving cell of the CORESET.
[0117] Example 30: According to the method of any one of Examples 17-29, wherein 1) the multi-TRP related higher-layer parameters based on multiple DCI have been configured to the user equipment including one or more of the following: more than three CORESETs are configured to the user equipment for the downlink bandwidth portion (DL BWP); more than one scrambling sequence is configured to the user equipment; more than one rate matching pattern for LTE-CRS (LTE cell-specific reference signal) is configured to the user equipment; joint or separate HARQ feedback reports are configured to the user equipment; and / or multi-TRP related higher-layer parameters are configured to the user equipment.
[0118] Example 31: According to the method of any one of Examples 17-30, wherein 2) the default mode of multi-TRP operation has been configured for the user equipment to include one or more of the following behaviors at the user equipment: the user equipment expects non-overlapping PDSCH reception; the user equipment expects overlapping and partially overlapping PDSCH reception, which utilizes a scrambling sequence defined based on the PCI applicable to the associated CORESETPoolIndex value; the user equipment operates using separate HARQ feedback operation; the user equipment operates under predefined assumptions for blind decoding limit calculations; the user equipment assumes rate matching on the joint CRS (Cell-Specific Reference Signal) resources configured for both the serving cell and the non-serving cell; the user equipment expects in-order transmission for PDCCH-PDSCH and PDCCH-PUSCH; and / or when conditions are met for multiple CORESETs associated with multiple cells with different Physical Cell Identifiers (PCIs) or with different cell groups, the user equipment follows any other predefined user equipment behavior.
[0119] Example 32: An apparatus comprising components for determining, by a user equipment in a wireless network, to perform inter-cell multi-transmitter receive point (multi-TRP) operation based on multiple downlink control information (multi-DCI) for the user equipment: receiving, by the user equipment, transmission configuration index (TCI) states for multiple control resource sets (CORESETs) from a network node, wherein the TCI states for the multiple CORESETs are associated with multiple cells having different physical cell identifiers (PCIs) or with multiple cell groups, wherein the TCI states indicate quasi-co-location (QCL) characteristics that the user equipment will use to receive physical downlink control channels (PDCCHs) associated with multiple cells having different PCIs or with multiple cell groups, wherein the multiple A cell or multiple cell groups include at least a serving cell and at least one non-serving cell for a user equipment; a component for the user equipment to determine that at least one of the following conditions exists: 1) multi-DCI-based multi-TRP related higher-layer parameters have been configured for the user equipment; 2) the default mode of multi-TRP operation has been configured for the user equipment; or 3) the user equipment has received control information indicating the activation of the Physical Downlink Shared Channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values; and a component for the user equipment to determine to perform inter-cell multi-DCI-based multi-TRP operation for cells from multiple cells or for cells from multiple cell groups.
[0120] Example 33: According to the apparatus of Example 32, the user equipment performs inter-cell multi-DCI based multi-TRP operation for cells from a plurality of cells or for cells from a plurality of cell groups, wherein the user equipment is not explicitly configured for inter-cell multi-DCI based multi-TRP operation by setting the CORESETPoolIndex value for the user equipment to more than one value for CORESET.
[0121] Example 34: An apparatus according to any one of Examples 32-33, wherein the components for performing inter-cell multi-DCI-based multi-TRP operations for cells from a plurality of cells or for cells from a plurality of cell groups include: components for performing at least one of the following by the user equipment with respect to a first TRP including a serving cell and a second TRP including at least one non-serving cell: separate channel monitoring, data processing, and / or separate reception and / or transmission of control and data with respect to a channel set (PUCCH / PUSCH / PDSCH / PDCCH) corresponding to each of the serving cell and the at least one non-serving cell; monitoring separately from each of the serving cell and the at least one non-serving cell. Downlink control information (DCI) on a separate PDCCH; receiving downlink data scheduled by the DCI and received via the corresponding PDSCH channel for each of the serving cell and the at least one non-serving cell; descrambling the PDSCH channels for the PDSCHs from the serving cell and the at least one non-serving cell respectively; performing separate PUSCH scheduling for uplink data transmission based on the corresponding DCI for each of the serving cell and the at least one non-serving cell; performing separate beam failure detection and / or beam failure recovery for the serving cell and the non-serving cell respectively; or sending hybrid ARQ (HARQ) feedback for the serving cell and the non-serving cell.
[0122] Example 35: An apparatus according to any one of Examples 32-34, wherein a component for performing inter-cell multi-DCI-based multi-TRP operations by the user equipment for the cell from the plurality of cells or for the cell from the plurality of cell groups, based on at least one of the following, is performed by the user equipment as if the CORESETPoolIndex value were configured, even if the user equipment has not been explicitly configured for multi-TRP operations by setting the CORESETPoolIndex value to more than one value for CORESET: 1) the lowest of the two PCIs indicates that the CORESETPoolIndex = 0, and the highest of the two PCIs indicates that the lowest of the two PCIs indicates that the highest of the two PCIs indicates that the lowest of the two PCIs is 0. 1) CORESETPoolIndex = 1; 2) The highest PCI of the two PCIs indicates that CORESETPoolIndex = 0, and the lowest PCI of the two PCIs indicates that CORESETPoolIndex = 1; 3) The serving cell PCI of the two PCIs indicates that CORESETPoolIndex = 0, and the non-serving cell PCI of the two PCIs indicates that CORESETPoolIndex = 1; or 4) The predefined PCI of the two PCIs indicates that CORESETPoolIndex = 0, and the remaining PCI of the two PCIs indicates that CORESETPoolIndex = 1.
[0123] Example 36: An apparatus according to any one of Examples 32-35, wherein the component for performing inter-cell multi-DCI-based multi-TRP operations by the user equipment for cells from a plurality of cells or for cells from a plurality of cell groups is performed by the user equipment based on more than two CORESETPoolIndex values corresponding to different PCIs or different cell groups.
[0124] Example 37: An apparatus according to any one of Examples 32-36, wherein the first cell group represents CORESETPoolIndex = 0 and the second cell group represents CORESETPoolIndex = 1.
[0125] Example 38: An apparatus according to any one of Examples 32-37, wherein the first cell group and the second cell group each include a plurality of non-serving cells.
[0126] Example 39: An apparatus according to any one of Examples 32-38, wherein 3) the user equipment has received control information indicating activation of the Physical Downlink Shared Channel (PDSCH) TCI state corresponding to two different CORESETPoolIndex values, including: the user equipment has received a Media Access Control-Control Unit (MAC-CE) indicating activation of the PDSCH TCI state for two different CORESETPoolIndex values, and wherein each TCI state activation is associated with a PCI; the method further includes the user equipment determining a cell group comprising the PCIs associated with the TCI state activations for the CORESETPoolIndex values received via the MAC-CE.
[0127] Example 40: An apparatus according to any one of Examples 32-39 further includes: a component for receiving, by the user equipment, a message or signaling indicating a PCI assigned to a cell group from a network node.
[0128] Example 41: An apparatus according to any one of Examples 32-40 further includes: a component for receiving a measurement configuration by a user equipment from a network node, the measurement configuration also indicating a PCI assigned to a cell group.
[0129] Example 42: An apparatus according to any one of Examples 32-41 further includes: a component for receiving, by the user equipment, updated TCI states for multiple CORESETs from a network node, wherein the TCI states for multiple CORESETs are associated with only one PCI or one cell group; and, based on the received updated TCI states, changing the operation of the user equipment from inter-cell multi-TRP operation based on multiple DCIs to single TRP operation.
[0130] Example 43: An apparatus according to any one of Examples 32-42, comprising: in response to a user equipment receiving a TCI state activation for a CORESET, wherein different TCI states for a corresponding CORESET are associated with at least two different physical cell identifiers (PCIs) and indicating inter-cell multi-TRP operation based on multiple DCIs, the user equipment performs the operation as if a CORESETPoolIndex value has been configured in the control resource set (CORESET), and the user equipment determines the CORESET associated with the serving cell PCI as a CORESET having CORESETPoolIndex = 0.
[0131] Example 44: An apparatus according to any one of Examples 32-43, comprising a component for: in response to a user equipment receiving a TCI state activation for a CORESET, wherein different TCI states for a corresponding CORESET are associated with at least two different physical cell identifiers (PCIs), the user equipment performs beam failure detection using a corresponding set of BFD-RS (beam failure detection reference signals), wherein the reference signal (RS) for the corresponding set of BFD-RS is determined based on the associated PCI values for the serving cell and at least one non-serving cell of the CORESET.
[0132] Example 45: An apparatus according to any one of Examples 32-44, wherein 1) multiple TRP-related higher-layer parameters based on multiple DCI have been configured to the user equipment including one or more of the following: more than three CORESETs are configured to the user equipment for the downlink bandwidth portion (DL BWP); more than one scrambling sequence is configured to the user equipment; more than one rate matching pattern for LTE-CRS (LTE cell-specific reference signal) is configured to the user equipment; joint or separate HARQ feedback reports are configured to the user equipment; and / or multiple TRP-related higher-layer parameters are configured to the user equipment.
[0133] Example 46: An apparatus according to any one of Examples 32-45, wherein 2) the default mode of multi-TRP operation has been configured for the user equipment to include one or more of the following behaviors at the user equipment: the user equipment expects non-overlapping PDSCH reception; the user equipment expects overlapping and partially overlapping PDSCH reception, which utilizes a scrambling sequence defined based on a PCI that can be applied to the associated CORESETPoolIndex value; the user equipment operates using separate HARQ feedback operation; the user equipment operates under predefined assumptions for blind decoding limit calculations; the user equipment assumes rate matching on the joint CRS (Cell-Specific Reference Signal) resources configured for both the serving cell and the non-serving cell; the user equipment expects in-order transmission of PDCCH-PDSCH and PDCCH-PUSCH; and / or when conditions are met for multiple CORESETs associated with multiple cells having different Physical Cell Identifiers (PCIs) or with different cell groups, the user equipment follows any other predefined user equipment behavior.
[0134] Figure 6 This is a block diagram of a network node (e.g., AP, BS, eNB, gNB, RAN node) 600 according to an example embodiment. For example, the wireless station 600 may include one or more (e.g., Figure 6The two RF (radio frequency) or wireless transceivers 602A and 602B shown include a transmitter for transmitting signals and a receiver for receiving signals in each wireless transceiver. The wireless station also includes a processor or control unit / entity (controller) 604 for executing instructions or software and controlling the transmission and reception of signals, and a memory 606 for storing data and / or instructions.
[0135] Processor 604 may also make decisions or judgments, generate frames, data packets, or messages for transmission, decode received frames or messages for further processing, and perform other tasks or functions described herein. Processor 604 may be a baseband processor, for example, capable of generating messages, data packets, frames, or other signals for transmission via wireless transceiver 602 (602A or 602B). Processor 604 may control the transmission of signals or messages on a wireless network, and may control the reception of signals or messages via a wireless network (e.g., after down-conversion by wireless transceiver 602, etc.). Processor 604 may be programmable and capable of executing software or other instructions stored in memory or other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. For example, processor 604 may be (or may include) hardware, programmable logic, a programmable processor executing software or firmware, and / or any combination of these. For example, using other terms, processor 604 and transceiver 602 together may be considered a wireless transmitter / receiver system.
[0136] In addition, refer to Figure 6 The controller (or processor) 608 can execute software and instructions, providing overall control of station 600, and can also provide... Figure 6 Control of other systems not shown, such as control of input / output devices (e.g., monitor, keyboard), and / or software that can execute one or more applications provided on the wireless station 600, such as email programs, audio / video applications, word processors, VoIP applications, or other applications or software.
[0137] In addition, a storage medium may be provided that includes stored instructions, which, when executed by the controller or processor, may cause the processor 604 or other controller or processor to perform one or more of the aforementioned functions or tasks.
[0138] According to another example embodiment, the RF or (multiple) wireless transceivers 602A / 602B can receive signals or data and / or transmit or send signals or data. The processor 604 (and possibly the transceivers 602A / 602B) can control the RF or wireless transceivers 602A or 602B to receive, transmit, broadcast, or send signals or data.
[0139] Embodiments of the various technologies described herein can be implemented in digital electronic circuits, or computer hardware, firmware, software, or combinations thereof. Embodiments can be implemented as computer program products, i.e., computer programs tangibly embodied in an information carrier (such as in a machine-readable storage device or a transmitted signal) for execution or control of the operation of a data processing apparatus (such as a programmable processor, computer, or multiple computers). Embodiments can also be provided to computer-readable media or computer-readable storage media, which may be non-transitory media. Embodiments of the various technologies may also include embodiments provided via transient signals or media, and / or program and / or software embodiments downloadable via the Internet or (multiple) other networks (wired and / or wireless networks). Furthermore, embodiments can be provided via machine-type communication (MTC) and also via the Internet of Things (IoT).
[0140] Computer programs can be in the form of source code, object code, or some intermediate form, and can be stored on various types of carriers, distribution media, or computer-readable media, which can be any entity or device capable of carrying the program. Examples of such carriers include recording media, computer memory, read-only memory, photoelectric and / or electronic carrier signals, telecommunication signals, and software distribution data packets. Depending on the required processing power, a computer program can be executed in a single electronic digital computer or distributed across several computers.
[0141] Furthermore, embodiments of the various technologies described herein can utilize cyber-physical systems (CPS) (systems of collaborative computing elements that control physical entities). CPS enables the embodiment and utilization of a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber-physical systems are a subcategory of cyber-physical systems, where the physical systems under discussion possess inherent mobility. Examples of mobile physical systems include mobile robots and electronic products transported by humans or animals. The increasing prevalence of smartphones has boosted interest in the field of mobile cyber-physical systems. Therefore, various embodiments of the technologies described herein can be provided via one or more of these technologies.
[0142] Computer programs (such as the aforementioned computer programs) can be written in any programming language, including compiled or interpreted languages, and can be deployed in any form, including as standalone programs or as modules, components, subroutines, or other units or parts suitable for use in a computing environment. A computer program can be deployed to execute on a single computer, or it can be deployed to execute on multiple computers at a single site, or it can be distributed across multiple sites and interconnected via a communication network.
[0143] The method steps may be executed by one or more programmable processors that execute a computer program or portions thereof to perform functions by manipulating input data and generating output. The method steps may also be executed by special-purpose logic circuitry (such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit)), and the apparatus may also be implemented as special-purpose logic circuitry (such as an FPGA or an ASIC).
[0144] For example, processors suitable for executing computer programs include general-purpose and special-purpose microprocessors, as well as any one or more processors of any kind of digital computer, chip, or chipset. Generally, a processor receives instructions and data from read-only memory or random access memory, or both. Components of a computer may include at least one processor for executing instructions and one or more storage devices for storing instructions and data. Generally, a computer may also include or be operatively coupled to one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, to receive data from or transfer data to these devices, or both. Suitable information carriers for embodying computer program instructions and data include various forms of non-volatile memory, such as semiconductor memory devices like EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. Processors and memory may be supplemented by or integrated into special-purpose logic circuitry.
[0145] To provide interaction with the user, embodiments can be implemented on a computer with a display device, such as a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user, and a user interface, such as a keyboard and pointing device, such as a mouse or trackball, through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; input from the user can be received in any form, including sound, speech, or tactile input.
[0146] The embodiments can be implemented in a computing system that includes backend components (e.g., a data server), middleware components (e.g., an application server), frontend components (e.g., a client computer with a graphical user interface or web browser through which a user interacts with the embodiments), or any combination of such backend, middleware, or frontend components. Components can be interconnected via any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks (LANs) and wide area networks (WANs), such as the Internet.
[0147] While certain features of the embodiments have been described herein, many modifications, substitutions, alterations, and equivalents will appear to those skilled in the art. Therefore, it should be understood that the appended claims are intended to cover all such modifications and alterations falling within the true spirit of the various embodiments.
Claims
1. A device for communication, comprising: A component for receiving Transmission Configuration Index (TCI) states for multiple Control Resource Sets (CORESETs) from a network node, wherein the TCI states for the multiple CORESETs are associated with multiple cells having different Physical Cell Identifiers (PCIs) or with multiple cell groups, wherein the TCI states indicate Quasi-Co-location (QCL) characteristics, which the device will use to receive Physical Downlink Control Channels (PDCCHs), the PDCCHs being associated with the multiple cells having different PCIs or with the multiple cell groups, wherein the multiple cells or the multiple cell groups include at least the serving cell for the device and at least one additional cell; as well as When the device has received a Media Access Control-Control Unit (MAC-CE) indicating that the Physical Downlink Shared Channel (PDSCH) TCI state is activated for two different CORESETPoolIndex values. A component for performing inter-cell multi-DCI-based multi-TRP operations for cells from the plurality of cells or for cells from the plurality of cell groups.
2. The apparatus of claim 1, wherein the apparatus has not been explicitly configured for inter-cell multi-DCI-based multi-TRP operations by setting the CORESETPoolIndex value for the apparatus to more than one value for CORESET.
3. The apparatus of claim 1, wherein the component for performing inter-cell multi-DCI-based multi-TRP operations for the cells from the plurality of cells or for the cells from the plurality of cell groups comprises: A component for performing at least one of the following with respect to a first TRP including the serving cell and a second TRP including the at least one additional cell: With respect to the channel set corresponding to each of the serving cell and the at least one other cell, separate channel monitoring, data processing, and / or control and separate reception and / or transmission of data; The downlink control information (DCI) is monitored on separate PDCCHs from each of the serving cell and the at least one other cell. For each of the serving cell and the at least one other cell, downlink data scheduled by the DCI and received via the corresponding PDSCH channel is received; Descramble the PDSCH channels for the serving cell and the at least one other cell respectively; For each of the serving cell and the at least one other cell, a separate Physical Uplink Shared Channel (PUSCH) scheduling for uplink data transmission is performed based on the corresponding DCI. For the serving cell and for the other cells, perform separate beam failure detection and / or beam failure recovery; or Send hybrid ARQ HARQ feedback for the serving cell and the other cell.
4. The apparatus of claim 3, wherein the channel set comprises at least one of the following: Physical uplink control channel (PUCCH) PUSCH, PDSCH, or PDCCH.
5. The apparatus of claim 1, wherein even if the apparatus has not been explicitly configured for multiple TRP operations by setting the CORESETPoolIndex value to more than one value for CORESET, the component for performing inter-cell multi-DCI-based multiple TRP operations for the cells from the plurality of cells or for the cells from the plurality of cell groups still operates based on at least one of the following as if the CORESETPoolIndex value were configured: 1) The lowest PCI among the two PCIs indicates that CORESETPoolIndex=0, and the highest PCI among the two PCIs indicates that CORESETPoolIndex=1; 2) The highest PCI among the two PCIs indicates that CORESETPoolIndex=0, and the lowest PCI among the two PCIs indicates that CORESETPoolIndex=1; 3) The serving cell PCI of the two PCIs indicates that CORESETPoolIndex=0, and the non-serving cell PCI of the two PCIs indicates that CORESETPoolIndex=1; or 4) The predefined PCI among the two PCIs indicates that CORESETPoolIndex=0, and the remaining PCI among the two PCIs indicates that CORESETPoolIndex=1.
6. The apparatus of claim 1, wherein the component for performing inter-cell multi-DCI-based multi-TRP operation for the cell from the plurality of cells or for the cell from the plurality of cell groups is based on more than two CORESETPoolIndex values corresponding to different PCIs or different cell groups.
7. The apparatus of claim 1, wherein the first cell group represents CORESETPoolIndex=0, and the second cell group represents CORESETPoolIndex=1.
8. The apparatus of claim 1, wherein the first cell group and the second cell group each comprise a plurality of additional cells.
9. The apparatus according to claim 1, further comprising: Components for determining cell groups, the cell groups including the PCI associated with TCI state activation received via the MAC-CE for the CORESETPoolIndex value.
10. The apparatus according to claim 1, further comprising: A component for receiving messages or signaling from the network node, the messages or signaling indicating PCIs assigned to a cell group.
11. The apparatus according to claim 1, further comprising: Components for receiving measurement configurations from the network node, the measurement configurations also indicating PCIs assigned to cell groups.
12. The apparatus according to any one of claims 1 to 11, further comprising: Components for receiving updated TCI states for the plurality of CORESETs from the network node, wherein the TCI states for the plurality of CORESETs are associated with only one PCI or one cell group; as well as A component for changing the operation of the device from multi-TRP operation based on multiple DCIs between the cells to single-TRP operation based on the received updated TCI state.
13. The apparatus according to any one of claims 1 to 11, wherein in response to receiving a TCI state activation for a CORESET indicating multi-DCI-based multi-TRP operation between cells, wherein different TCI states for corresponding CORESETs are associated with at least two different physical cell identifiers (PCIs), the apparatus further comprises: The component is for performing / operating as if it had been configured with the CORESETPoolIndex value in ControlResourceSet CORESET, and the component is for determining the CORESET associated with the serving cell PCI as a CORESET with CORESETPoolIndex=0.
14. The apparatus according to any one of claims 1 to 11, further comprising: In response to receiving a TCI state activation for a CORESET, wherein different TCI states for a corresponding CORESET are associated with at least two different Physical Cell Identifiers (PCIs), a component for performing beam failure detection using a corresponding BFD-RS beam failure detection reference signal set, wherein the reference signal RS for the corresponding BFD-RS set is determined based on the associated PCI values for the CORESET for the serving cell and the at least one other cell.
Citation Information
Patent Citations
Phase tracking reference signal port or configuration sharing across multiple physical downlink channels of multiple transmit receive points
CN112514311A
Downlink reception and beam management
US20210099981A1