RU2791937C1 - A system and method for receiving shared channels transmitting multiple trp - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: invention relates to wireless communication. A wireless communication node configures a plurality of state fields in the form of two control elements (CE) media access control (MAC) objects, associates them with corresponding group identifiers of configuration resource sets (CORESET) and with corresponding group identifiers of configured states, transmits a CE MAC object of two CE MAC objects and a CORESET corresponding group identifier.

EFFECT: invention prevents severe interference between transmissions from multiple Transmission Points (TRPs) in a deployed transport network by coordinating transmissions from TRPs and supporting independent physical layer scheduling between coordinated TRPs using two separate CE MAC objects, which also helps resolving whether the received CE MAC object corresponds to CORESET Group ID 0 or to CORESET Group ID 1.

14 cl, 7 dwg, 2 tbl

Description

The field of technology to which the invention belongs

The disclosure relates generally to wireless communications, and in particular to systems and methods for receiving shared channels for transmissions using multiple transceiver points (TRPs).

State of the art

In NR version 15, the transmission of multiple TRPs was not considered within the 5G specification. In other words, the current Rel-15 specification does not support transmitting data from multiple TRPs to a single UE, where two TRPs (eg, TRP 0 and TRP 1) transmit the PDSCH to the same UE. In addition, the cost of providing an ideal backhaul to achieve nearly perfect synchronization between multiple TRPs is generally high, forcing operators to deploy a non-ideal backhaul between TRPs. In the case of deployment of a non-ideal transport communication network, multiple TRPs that transmit data to the same UE cannot dynamically interact with each other due to the lack of synchronization between them. This can lead to severe interference between transmissions from multiple TRPs unless systems and methods are developed to coordinate transmissions from multiple TRPs with each other on at least a semi-static basis.

The essence of the invention

The exemplary embodiments disclosed herein are directed to solve problems associated with one or more of the problems presented in the prior art, as well as to provide additional features that will become apparent when referring to the following detailed description taken in conjunction with the accompanying drawings. In accordance with various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are provided by way of example and are not limiting, and those skilled in the art reading the present disclosure will appreciate that various modifications to the disclosed embodiments may be made while remaining within the scope of the present disclosure.

In one embodiment, an exemplary wireless communication method comprises: defining, by a wireless node, a plurality of sets of rate matching configurations. The method further comprises: associating, by the wireless node, a plurality of rate matching configuration sets with respective group IDs and transmitting, by the wireless node to the wireless communication device, a signal indicating the plurality of rate matching configuration sets and the group IDs.

In another embodiment, a wireless communication method comprises: dividing, by the wireless communication node, a plurality of media access control (MAC) control (CE) state fields into a plurality of field sets. The method further comprises: associating, by the wireless communication node, a plurality of field sets with respective group identifiers and transmitting, by the wireless communication node to the wireless communication device, a signal indicating the plurality of field sets and the associated group identifiers.

In yet another embodiment, a wireless communication method comprises: receiving, by a wireless communication device from a wireless communication node, a signal indicating a plurality of rate matching configuration sets and associated group identifiers. The method further comprises: identifying, by the wireless communication device, based on the received control channel, the first of the group identifiers and one of the plurality of rate matching configuration sets corresponding to the first group identifier, and determining, by the wireless communication device, resources to be excluded from receiving the shared channel, according to the identified set of rate matching configurations.

In another embodiment, a wireless communication method comprises receiving, by a wireless communication device, a signal indicating a plurality of field sets and corresponding group identifiers from a wireless node. The method further comprises: retrieving, by the wireless communication device, associating a plurality of field sets with corresponding group identifiers and determining, by the wireless communication device, resources that should be used to receive a shared channel or CSI trigger, in accordance with one of the plurality of field sets corresponding to one from the corresponding group IDs.

The above and other aspects and their implementation are described in more detail in the following description with reference to the drawings and in the claims.

Brief description of the drawings

Various exemplary embodiments of the present disclosure are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of the present disclosure in order to facilitate the reader's understanding of the present disclosure. Thus, the drawings should not be construed as limiting the breadth, scope, or applicability of the present disclosure. It should be noted that, for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

In FIG. 1 shows an exemplary cellular communication network in which the technologies and other aspects disclosed herein may be implemented in accordance with an embodiment of the present disclosure.

In FIG. 2 is a block diagram of an exemplary base station and user equipment device in accordance with some embodiments of the present disclosure.

In FIG. 3A shows an exemplary wireless network illustrating independent scheduling of multiple TRPs for UEs.

In FIG. 3B shows an exemplary wireless network implementation in which NR and LTE base stations provide coverage of the same geographic area while supporting transmission of multiple TRPs to the UE.

In FIG. 4 shows a method, from a wireless node's point of view, of transmitting a signal to a wireless communication device indicating a plurality of rate matching configuration sets and corresponding group IDs.

In FIG. 5 shows a method, from a wireless node's point of view, of signaling to a wireless communication device indicating a plurality of media access control (MAC) control element (CE) field sets and associated group identifiers.

In FIG. 6 shows the method from the perspective of a wireless communication device that receives a signal from a wireless node regarding resources to be used for shared channel scheduling.

Detailed description of the invention

Various exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings to enable a person skilled in the art to make and use the present disclosure. As will be apparent to those skilled in the art, after reading this disclosure, various changes or modifications may be made to the examples described herein without deviating from the scope of this disclosure. Thus, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Depending on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be changed while remaining within the scope of this disclosure. Thus, those skilled in the art will appreciate that the methods and techniques disclosed herein are the various steps or steps in an exemplary order, and the present disclosure is not limited to the specific order or hierarchy presented, unless expressly stated otherwise.

It is preferable to provide data transmission from multiple TRPs to a single UE, where two TRPs (e.g., TRP 0 and TRP 1) transmit the PDSCH to the same UE for 5G NR communication systems in order to achieve receive diversity at the UE and be able to support higher data rate in the UE. In one embodiment, the present disclosure provides systems and methods to support improved signaling for multiple TRP transmission by mitigating potential interference between transmissions of multiple TRPs, even though such multiple TRP transmission is not supported in the 5G Rel-15 specification. In another embodiment, the present disclosure provides systems and methods for maintaining separate indications of dynamic information for two coordinated TRPs, in particular, separate quasi-colloquial location (QCL) information. The operation of these embodiments and their embodiments are described in detail in the remainder of this disclosure.

In FIG. 1 shows an exemplary wireless communications network and/or system 100 in which the technologies disclosed herein may be implemented in accordance with an embodiment of the present disclosure. In the following discussion, wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an exemplary network 100 includes a Next Generation Node B (gNB), a TRP, or simply a base station 102 (hereinafter "BS 102") and a user equipment device 104 (hereinafter "UE 104") that can communicate with each other via a link. 110 (eg, wireless link) and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 overlapping geographic area 101. FIG. 1, BS 102 and UE 104 are within the respective geographic boundary of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating in its allocated bandwidth to provide adequate radio coverage to intended users.

For example, BS 102 may operate with dedicated channel bandwidth to provide adequate coverage for UE 104. BS 102 and UE 104 may communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118/124 may be further divided into subframes 120/127, which may include data symbols 122/128. In the present disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes" that can typically apply the methods disclosed herein. Such communication nodes may support wireless and/or wired communication in accordance with various embodiments of the present disclosure. It should be understood that in the following description, the terms gNB and TRP may be used interchangeably.

In FIG. 2 shows a block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals, such as OFDM/OFDMA signals, in accordance with some embodiments of the present disclosure. System 200 may include components and elements configured to support known or conventional operating features that do not need to be described in detail herein. In one exemplary embodiment, system 200 may be used to transmit (eg, send and receive) data symbols in a wireless communication environment, such as wireless communication environment 100 in FIG. 1 as described above.

System 200 typically includes a base station 202 (hereinafter "BS 202") and user equipment 204 (hereinafter "UE 204"). The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being connected and connected to each other as needed via the bus 220 data transmission. The UE 204 includes a user equipment (UE) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being connected and connected to each other as needed via a communication bus 240. BS 202 communicates with UE 204 via communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.

As will be appreciated by those skilled in the art, system 200 may further include any number of modules other than those shown in FIG. 2. Those skilled in the art will appreciate that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination of them. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described broadly in terms of their functionality. Whether such functionality is implemented in hardware, firmware, or software may depend on the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality appropriately for each particular application, but such implementation decisions should not be interpreted as limiting the scope of this disclosure.

In accordance with some embodiments, UE transceiver 230 may be referred to herein as "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to antenna 232. Duplex Switch (not shown) may alternately connect the uplink transmitter or receiver to the uplink antenna in time duplex mode. Similarly, in accordance with some embodiments, the BS transceiver 210 may be referred to herein as the "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 212. Duplex the downlink switch may alternately connect the downlink transmitter or receiver to the downlink antenna 212 in time duplex mode. The operation of the two transceiver modules 210 and 230 can be time-coordinated so that the uplink receiver circuit is connected to the uplink antenna 232 to receive transmissions on the wireless data link 250 at the same time that the downlink transmitter is connected. to the antenna 212 downlink. In some embodiments, there is close timing with a minimum guard time between changes in the duplex direction.

UE transceiver 230 and base station transceiver 210 are configured to communicate via wireless data link 250 and cooperate with an appropriately configured RF antenna device 212/232 that can support a particular wireless communication protocol and modulation scheme. In some exemplary embodiments, UE transceiver 210 and base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE), emerging new 5G standards, and the like. However, it should be understood that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Instead, UE transceiver 230 and base station transceiver 210 may be configured to support alternative or additional wireless communication protocols, including future standards or variations thereof.

According to various embodiments, the BS 202 may be, for example, a next generation Node B (gNB), a TRP, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, UE 204 may be implemented in various types of user devices such as a mobile phone, smartphone, personal digital assistant (PDA), tablet computer, laptop computer, wearable computing device, and so on. Processor modules 214 and 236 may be implemented or implemented with a general purpose processor, memory addressable information, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of them that are designed to perform the functions described in this document. Thus, a processor may be implemented as a microprocessor, controller, microcontroller, state machine, and the like. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration.

In addition, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any of them. practical combination. The memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. in this field of technology. In this regard, memory modules 216 and 234 may be connected to processor modules 210 and 230, respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

Network communication module 218 is typically hardware, software, firmware, processing logic, and/or other components of base station 202 that provide bi-directional communication between base station transceiver 210 and other network components and communication nodes implemented with the ability to communicate with the base station 202. For example, the network communication module 218 can be configured to support Internet traffic or WiMAX traffic. In a typical deployment, but not limited to, the network communication module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 can communicate with a conventional Ethernet-based computer network. Thus, the network communication module 218 may include a physical interface for connecting to a computer network (eg, to a Mobile Switching Center (MSC)). As used in this document, the terms "configured for", "capable of", and their associations with respect to a specific operation or function, refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed , formatted and/or configured to perform a particular operation or function.

Referring to FIG. 3A, wireless network 300 is shown with independent physical layer shared channel scheduling with multiple TRPs (TRP 0, denoted 310, and TRP 1, denoted 320) for UE 325. Among TRP 0 (310) and TRP 1 (320 ) there is no dynamic coordination (or near-perfect timing) due to a non-ideal backhaul (not shown in Fig. 3A) between TRPs. But systems and methods according to the present disclosure provide coordination between TRPs (even in the absence of synchronization between TRPs), so that independent physical layer scheduling among TRPs can be maintained. As shown in FIG. 3A, TRP 0 (310) and TRP1 (320) schedule PDSCH 0 and PDSCH 1 with PDCCH 0 and PDCCH 1, respectively.

Since TRP 0 (310) and TRP1 (320) have different locations, the quasi-colloquial location (QCL) information sent to UE 325 from coordinated TRP 0 (310) and TRP1 (320) must be different for both PDCCH and PDSCH transmissions. . In addition, other physical layer channels, eg, ACK/NACK feedback, HARQ processing, PDSCH scrambling, etc., must also be separate for coordinated TRPs, TRP 0 (310) and TRP1 (320).

For specification clarity, one higher level index configured for each control resource set (CORESET) is used to identify the TRP. For example, the PDCCH (or DCI) and the scheduled PDSCH of the higher layer CORESET with index 0 can be considered as those of TRP 0, the PDCCH (or DCI) and the scheduled PDSCH of the higher layer CORESET with index 1 can be considered as those of TRP 1. In short, the higher level index configured for CORESET is TRP. Different higher-level indexes refer to different TRPs. For simplicity, we refer to the higher-level index configured for CORESET as the CORESET group ID.

Many 5G base stations in the early stages of deployment will likely be autonomous (NSA) and need to rely on LTE base stations to transmit control signaling to NR UEs. These 5G base stations must coexist with an LTE base station in the same coverage area. However, some signals from an LTE base station will cause severe interference to NR UEs, such as LTE CRS (Cell Specific Reference Signals). Thus, in coexistence between LTE and UE, the NR needs to perform rate negotiation around resource elements (REs) of one or more LTE CRSs in the serving cell. In other words, LTE CRS REs are not available for PDSCH reception of all NR UEs in the same serving cell. Thus, the base station NR can configure one LTE CRS (lte-CRS-ToMatchAround) configuration for all UEs of the serving cell. In other words, lte-CRS-ToMatchAround is a serving cell-specific parameter. The UE is typically informed of the serving cell or carrier over a broadcast channel. Therefore, all UEs in the serving cell can perform rate negotiation to receive the PDSCH. Typically, it is configured in the ServingCellConfig or ServingCellConfigCommon parameter, which are the serving cell-specific cell parameters of the serving cell of the UE. Cell-specific CRS configuration is very efficient because each TRP or each gNB (ie NR base station) does not need to configure this parameter many times for each UE in the serving cell. However, this may cause some problems if transmission using multiple TRPs is considered.

Let us now turn to FIG. 3B, a wireless network 300' is shown in which NR and LTE base stations may cover the same geographic area. For example, base station 350 (which is an example of the previously mentioned NSA mode in which a 5G base station relays control signals using LTE base stations) is shown in FIG. 3B both transmitting both an NR control channel and an LTE control channel, wherein the NR control channel is intended to serve the NR-enabled UE0 (denoted 375), while the LTE-only UE1 (denoted 385) receives the LTE control channel. In FIG. 3B also shows base station 350 transmitting an NR control channel at UE2 395, base station 360 transmitting an NR control channel at UE0 375, and base station 370 transmitting an LTE control channel at UE1 (385). NR and LTE can transmit in the same area, and two NR base stations transmit data to the same UE. Specifically, UE0 375 and UE1 385 are in the serving cell of TRP 0 (350). TRP 0 (350) and TRP 1 (360) perform multiple TRP transmission to UE0 375, and TRP 0 (350) and TRP 2 (370) perform multiple TRP transmission to UE0 375. It should be understood that the wireless networks and components shown in fig. 3A and FIG. 3B are exemplary embodiments of the general wireless network diagrams shown in FIG. 1 and FIG. 2 and contain more detailed information to further explain the operation of the wireless network for 5G communication systems.

Referring again to FIG. 3B, since cell TRP 0 (350) is the serving cell for all UE0 375, UE1 385, and UE2 395, TRP 0 (350) may configure these UEs with an LTE CRS configuration, and then all UEs in the serving cell TRP0 (350) must perform rate negotiation around LTE CRS REs that are transmitted from TRP 0 (350). However, for UE0 375, the PDSCH1 must perform rate negotiation around the CRS REs that are transmitted from TRP 1 (360). Thus, UE0 375 may be configured with two CRS configurations, that is, two CORESET group IDs may be configured for UE0 375 to transmit using multiple TRPs. Similarly, UE1 385 may also be configured with two CRS configurations, but the second CRS configurations for UE0 375 and UE1 385 may be different because they refer to different TRPs. Thus, a simple expansion of a cell-specific CRS configuration into multiple TRPs cannot be performed.

Turning now to FIG. 4, method 400 is shown from the perspective of a wireless node for transmitting a signal to a wireless communication device indicating a plurality of rate matching configuration sets and corresponding group IDs.

At 402, the wireless node determines a plurality of rate matching configuration sets. In one embodiment, the wireless node may be a gNB or a TRP. The rate negotiation configurations may belong to N > 1 TRPs or gNBs, that is, the TRP may define multiple sets of rate negotiation configurations that may belong to multiple TRPs.

In step 404, the wireless node associates the plurality of rate matching configuration sets with the corresponding wireless node group IDs that contribute to the configuration sets. As mentioned earlier, the number N of wireless nodes can be greater than 1 (N > 1), each providing a set of rate negotiation configurations.

In step 406, the wireless node transmits to the wireless communication device a signal indicating a plurality of rate matching configuration sets and corresponding group identifiers. In one embodiment, the wireless communication device may be a UE.

Turning now to FIG. 5, method 500 is shown from the perspective of a wireless node for transmitting a signal to a wireless communication device that specifies a mapping between a plurality of media access control (MAC) control element (CE) field sets and associated group identifiers.

In step 502, the wireless node divides the set of MAC CE state fields into a set of field sets.

At 504, the wireless node associates the plurality of field sets with the corresponding group IDs.

In step 506, the wireless node transmits to the wireless communication device a signal indicating a plurality of field sets and associated group identifiers. In one embodiment, the wireless communication device may be a UE.

Turning now to FIG. 6, method 600 is shown from the perspective of a wireless communication device that receives a signal from a wireless node regarding shared channel scheduling.

In step 602, the wireless communication device receives, from the wireless communication node, a signal indicating a plurality of rate matching configuration sets and associated group identifiers. In one embodiment, the wireless communication device may be a UE, and the signal may comprise a set of rate negotiation configurations for N > 1 wireless nodes. In one embodiment, the wireless node is a gNB.

In step 604, the wireless communication device identifies, based on the received control channel, the first of the group identifiers and one of the plurality of rate matching configuration sets corresponding to the first group identifier.

In step 606, the wireless communication device determines, in accordance with the identified set of rate matching configurations, resources to be excluded from shared channel reception.

In the remainder of the disclosure, various embodiments are described with respect to signaling details, field names, field values, etc., as described in the 5G specification, which should be familiar to one of ordinary skill in the art as applicable to 5G wireless communications. It should be understood that numerous embodiments described below are based on the exemplary wireless network 300' shown above in FIG. 3B. The following is a description of several embodiments that explain how various components of 5G wireless communication systems (TRPs or gNBs or UEs) mitigate the problems of a non-ideal backhaul to overcome potential interference issues between multiple TRP transmissions to a single UE through specific parameter reference, messages and/or fields as defined in the current or future version of the relevant 5G specification. It should be understood that although many of the embodiments describe methods for dealing with interference problems during transmission of multiple TRPs from the point of view of a wireless node or base station (e.g., TRP or gNB), these embodiments also apply to the UE, since it is the UE that receives control channels and/or shared channels transmitted by the wireless node, and performs actions corresponding to the changed signaling or field values described in various embodiments.

In one embodiment, during multiple TRP transmissions, the UE is configured with N>1 LTE CRS configuration sets. At least one set of LTE CRS configurations is cell-specific. The other set(s) are UE-specific, that is, different UEs may be configured with different CRS configuration parameter values. Each set may include more than 1 CRS configuration. This is because one NR carrier corresponding to one serving cell can be much wider than an LTE carrier even for transmission using one TRP. For example, UE2 395 shown in FIG. 3B that receives the NR control channel may be configured with multiple LTE CRS configurations. In addition, a cell-specific CRS LTE configuration set is typically configured in the ServingCellConfigCommon and/or ServingCellConfig. Specific set(s) of UEs are configured in PDSCH-ServingCellConfig or PDSCH-Config or still in ServingCellConfig.

Embodiment 1

In one embodiment, REs from a set of n LTE CRS configurations are not available for one or more PDSCHs associated with n CORESET group IDs, where n=0,...,N-1. It should be understood that the term "unavailable" is used in the present disclosure to mean that the UE excludes the REs corresponding to the LTE configuration(s) when receiving a shared channel (eg, PDSCH) scheduled by the control channel associated with n group IDs. CORESET, where n= 0, ..., N-1. In addition, the first set of CRS LTE configurations is configured in the ServingCellConfig and/or ServingCellConfigCommon section. Other sets are configured in the PDSCH-ServingCellConfig or PDSCH-Config section, or still in the ServingCellConfig section.

Referring again to FIG. 3B, taking N=2 as an example for UE0 375, the first LTE CRS configuration set is cell-specific, and it is configured in the ServingCellConfig and/or ServingCellConfigCommon. If a PDSCH is scheduled by a DCI from a CORESET with a higher layer index 0 (CORESET group ID 0) or no higher index configured, the LTE CRS REs from the first LTE CRS configuration set are not available for that PDSCH resource mapping. The second set of LTE CRS configurations is UE specific and is configured in PDSCH-ServingCellConfig or PDSCH-Config or still in ServingCellConfig. If a PDSCH is scheduled by a DCI from CORESET with higher layer index 1 (CORESET group ID 1), LTE CRS REs from the second LTE CRS configuration set are not available for this PDSCH resource mapping. Based on this embodiment, the LTE CRS patterns configured in the ServingCellConfig and/or ServingCellConfigCommon are still cell specific parameters, ie PDSCH 0, 2, 4 in FIG. 3Bs must perform rate matching around the REs of these CRS patterns. For a single TRP transmission, the same as for a Rel-15 UE, eg UE2 385 in FIG. 3B, it is not necessary to configure the UE2 385 with a UE-specific CRS configuration. Since UE2 385 is not configured for multiple TRP transmission, the CORESET group ID will not be configured for each CORESET. For UE0 375 and UE1 385 using multiple TRP transmissions, CORESET group ID 0 is set to TRP 0 (350). CORESET ID 1 for UE0 375 is considered TRP 1 (360), and CORESET ID 1 for UE1 385 is considered TRP 2 (370). Thus, the rate matching patterns of the second PDSCH (PDSCH 1) for UE0 375 and the second PDSCH (PDSCH3) for UE1 385 may be different because the respective CRS patterns are UE specific.

The cell-specific rate matching parameters also include rate matching patterns that are used to map PDSCH resources to granularity at the RB symbol level. Thus, embodiments of the present disclosure may also be used for rate matching patterns. In other words, cell-specific rate matching patterns are defined, which are not available for the PDSCH scheduled by DCI with CORESET group ID 0. For UE-specific rate matching patterns, some new UE-specific rate matching patterns (not defined in Rel-15) may be introduced for the PDSCH scheduled by DCI with CORESET group ID 1. New UE-specific rate negotiation patterns may be configured in PDSCH-ServingCellConfig or PDSCH-Config.

Considering the complexity of the UE, in one embodiment, a maximum of two TRPs may be allowed for data transmission to the UE. Therefore, one set of LTE CRS configurations corresponds to one LTE serving cell. Thus, in one set, multiple LTE CRS patterns refer to different LTE carriers in the frequency domain. Therefore, the CRS of multiple LTE CRS configurations in the same set (ie, associated with the same CORESET group ID) should not map to the same PRB or should not overlap in the frequency domain.

Option 1-2 implementation

If the interference among the coordinated TRPs is not severe for the transmission of multiple TRPs, or the UE has an advanced receiver to suppress this kind of interference, overhead per PDSCH can be saved in one embodiment. However, interference among coordinated TRPs cannot be neglected, especially for UEs without enhanced receivers, since the channel quality from the UE to all coordinated TRPs is quite good if the UE is configured to transmit multiple TRPs.

In one embodiment, the CRS of TRP 1 (360) may cause severe interference to PDSCH 0 reception, as shown in FIG. 3b. Thus, the decision may be that the PDSCH scheduled by DCI, regardless of which CORESET groups should perform rate negotiation around CRS RE from both cell and UE specific CRS configurations. In other words, REs from both cell and UE specific CRS configurations are not available to a PDSCH that is scheduled by a DCI from any of the CORESET groups (or by a DCI associated with any of the CORESET group IDs). Taking N=2 as an example for UE0 375, the first LTE CRS configuration set is cell specific and it is configured in ServingCellConfig and/or ServingCellConfigCommon. Regardless of whether the PDSCH is scheduled with DCI from CORESET with higher layer index 0 or 1 (CORESET group ID 0 or 1) or no higher index configured, LTE CRS REs from the first LTE CRS configuration set are not available for this PDSCH resource mapping . The second set of LTE CRS configurations is UE specific and is configured in PDSCH-ServingCellConfig or PDSCH-Config. Whether the PDSCH is scheduled with DCI from CORESET with higher layer index 0 or 1 (CORESET group ID 0 or 1) or no higher index configured, LTE CRS REs from the second LTE CRS config set are not available for this PDSCH resource mapping. .

Option 1-3 implementation

Compared to embodiments 1-1 and 1-2, in another embodiment more flexibility can be offered in which REs from the set of n LTE CRS configurations are at least unavailable to one or more PDSCHs associated with the n CORESET group ID, where n=0,...,N-1. Accordingly, the REs from the set of n LTE CRS configurations are not available for multiple PDSCHs associated with the CORESET group ID n, and the gNB should further inform the UE whether REs from the set of n LTE CRS configurations are available for the PDSCH associated with the CORESET group ID n' , where n is not equal to n'. This additional signaling is UE-specific RRC signaling, which can be referred to as a resource control message.

Option 1-4 implementation

Yet another embodiment may be to predetermine that the REs from the LTE CRS Configuration Set are at least not available to one or more PDSCHs associated with the CORESET group ID n, and also to determine that the RE from the first LTE CRS Configuration Set (specific set cell) are not available for one or more PDSCHs associated with any CORESET group ID. In addition, the gNB must further inform the UE whether REs from the LTE CRS configuration set(s) other than the first set are available or not available for one or more PDSCHs associated with CORESET group ID 0. This additional signaling is UE-specific RRC signaling.

Option 1-5 implementation

Another embodiment is to configure one or more indexes for each LTE CRS configuration of the second set of LTE CRS configurations. Option 1 is to configure one higher level index (denoted as CRS Group ID) for each LTE CRS configuration of the second set of LTE CRS configurations. The CRS group ID value can range from 0 to X-1. X takes values of at least 3. Thus, all CRS LTE configurations in the second set of CRS LTE configurations are divided into X groups. For example, X=3, so all configured RateMatchPatternLTE-CRS in the second set are divided into three CRS groups. In the second set of CRS configurations with ID 0, CRS groups are assigned to CRS group 0, CRS configurations with CRS group ID 1 are assigned to CRS group 1, CRS configurations with CRS group ID 2 are assigned to CRS group 2. Then CRS REs in CRS group 0 are unavailable for the PDSCH associated with CORESET group 0. In other words, LTE CRS configuration(s) REs with CRS group ID 0 in the second set are not available for the PDSCH scheduled by the DCI of CORESET with higher layer index 0. CRS REs in CRS group 1 are not available for the PDSCH associated with CORESET group 1. In other words, LTE CRS configuration(s) REs with CRS group ID 1 in the second set are not available for the PDSCH scheduled by the DCI of CORESET with higher layer index 1. CRS REs in CRS group 2 are not available to PDSCHs from either CORESET group 0 or CORESET group 1. In other words, LTE CRS configuration(s) REs with CRS Group ID 2 in the second set are not available for the PDSCH scheduled by the DCI of CORESET with either of the higher layer index 0 or 1.

The following is an example of entering a single CRS group ID.

RateMatchPatternLTE-CRS ::= SEQUENCE {

CRS-group-id INTEGER (0...2), OPTIONAL,

carrierFreqDL INTEGER(0..16383),

carrierBandwidthDL ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1},

mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList, OPTIONAL,

nrofCRS-Ports ENUMERATED {n1, n2, n4},

v-Shift ENUMERATED {n0, n1, n2, n3, n4, n5}

}

Option 2 is to introduce a set of higher level indexes (denoted as CRS group ID) for each CRS configuration in the second set. Each CRS group ID corresponds to each CORESET group ID. If the value of ID x of the CRS group is 1 in the CRS configuration, the REs of that CRS configuration will not be available for the PDSCH scheduled by the DCI of the CORESET group x. If the CRS group ID value x is 0 in the CRS configuration, the REs of that CRS configuration will be available for the PDSCH scheduled by the DCI from the CORESET group x. Alternatively, if the CRS group ID value x is 0 in the CRS configuration, the REs of that CRS configuration will not be available for the PDSCH scheduled by the DCI from the CORESET group x. If the CRS group ID value x is 1 in the CRS configuration, the REs of that CRS configuration will be available for the PDSCH scheduled by the DCI from the CORESET group x.

The following is an example of entering two CRS group IDs.

RateMatchPatternLTE-CRS ::= SEQUENCE {

CRS-group-id0 ENUMERATED {0,1} OPTIONAL,

CRS-group-id1 ENUMERATED {0,1} OPTIONAL,

carrierFreqDL INTEGER(0..16383),

carrierBandwidthDL ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1},

mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList OPTIONAL,

nrofCRS-Ports ENUMERATED {n1, n2, n4},

v-Shift ENUMERATED {n0, n1, n2, n3, n4, n5}

}

Based on the above embodiments, each UE-specific CRS configuration can be configured as unreachable REs for PDSCH, scheduled DCI of ID 0, or 1, or both of the CORESET group, thus achieving flexibility in these embodiments. For the LTE CRS configuration in the first set of REs, these CRSs may be predefined as unreachable for the PDSCH scheduled by the DCI of ID 0 of the CORESET group. Alternatively, for an LTE CRS configuration in the first RE set of these CRSs, it may be set to be unreachable for the PDSCH scheduled by DCI from all CORESETs, i.e. any of CORESETs ID 0 or 1 if only two CORESETs are supported.

It should be noted that the name of the CRS Configuration ID may be different in future versions of the NR specification, i.e. the name may not be RateMatchPatternLTE-CRS, but functionality will be provided to match PDSCH resources around an LTE CRS.

Examples of rate matching patterns can be given:

RateMatchPattern ::= SEQUENCE {

rateMatchPatternId,

CRS-group-id INTEGER (0...2), OPTIONAL

...

}

RateMatchPattern ::= SEQUENCE {

rateMatchPatternId RateMatchPatternId,

CRS-group-id0 ENUMERATED {0,1} OPTIONAL,

CRS-group-id1 ENUMERATED {0,1} OPTIONAL,

...

}

In the embodiments described above, a new higher level index is introduced into each CRS configuration to provide maximum flexibility. However, the RateMatchPatternLTE-CRS IE structure will be changed. This may cause some backwards compatibility issue as the RateMatchPatternLTE-CRS IE may not have reserved bits. Thus, in some other embodiments, new RRC signaling is introduced outside of the RateMatchPatternLTE-CRS IE to inform the UE as to whether each LTE CRS pattern in the second set for the DCI scheduled PDSCH is only available from group ID 0, or ID 1 group or any of the CORESET group IDs. In particular, the new RRC signaling is used to indicate three parameters: the LTE CRS template in the second set is not available for the PDSCH scheduled by DCI only from the CORESET ID 0, the CRS LTE template in the second set is not available for the PDSCH scheduled by the DCI only from the CORESET ID 1 , the LTE CRS template in the second set is not available for the PDSCH scheduled by the DCI of the CORESET IDs 0 and 1. The new RRC signaling may still be the same as the CRS group ID, but will be configured for each CRS configuration, and may be outside the scope of the CRS configuration.

Embodiment 2

Since cell-specific parameters may be modified with UE-specific parameters in future versions of the NR specification, various embodiments of the present disclosure may support multiple LTE CRS configurations (i.e., it may not be necessary to enter multiple sets of LTE CRS configurations) and configure one or more indexes for each CRS LTE configuration. Option 1 is to configure one higher level index (denoted as CRS group ID) for each LTE CRS configuration. The CRS group ID value can range from 0 to X-1. X takes a value of at least 3. Thus, all CRS LTE configurations are divided into X groups. For example, with X=3, all configured RateMatchPatternLTE-CRS are divided into three CRS groups. CRS configurations with CRS group ID 0 belong to CRS group 0, CRS configurations with CRS group ID 1 belong to CRS group 1, CRS configurations with CRS group ID 2 belong to CRS group 2. Then CRS REs in CRS group 0 are not available for PDSCH, associated with group 0 CORESET. In other words, LTE CRS configuration(s) REs with CRS group ID 0 are not available for the PDSCH scheduled by the DCI of CORESET with higher layer index 0. CRS REs in CRS group 1 are not available for the PDSCH associated with CORESET group 1. In other words, LTE CRS configuration(s) REs with CRS Group ID 1 are not available for the PDSCH scheduled by the DCI of CORESET with higher layer index 1. CRS REs in CRS group 2 are not available to PDSCHs from either CORESET group 0 or CORESET group 1. In other words, LTE CRS configuration(s) REs with CRS Group ID 2 are not available for the PDSCH scheduled by the DCI of CORESET with index 0 or 1 of the higher layer.

The following is an example of entering a single CRS group ID.

RateMatchPatternLTE-CRS ::= SEQUENCE {

CRS-group-id INTEGER (0...2), OPTIONAL,

carrierFreqDL INTEGER(0..16383),

carrierBandwidthDL ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1},

mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList OPTIONAL, -- Need M

nrofCRS-Ports ENUMERATED {n1, n2, n4},

v-Shift ENUMERATED {n0, n1, n2, n3, n4, n5}

}

Option 2 is to introduce multiple higher level indexes (denoted as CRS group ID) for each CRS configuration. Each CRS group ID corresponds to each CORESET group ID. If the value of ID x of the CRS group is 1 in the CRS configuration, the REs of that CRS configuration will not be available for the PDSCH scheduled by the DCI of the CORESET group x. If the CRS group ID value x is 0 in the CRS configuration, the REs of that CRS configuration will be available for the PDSCH scheduled by the DCI from the CORESET group x. Alternatively, if the CRS group ID value x is 0 in the CRS configuration, the REs of that CRS configuration will not be available for the PDSCH scheduled by the DCI from the CORESET group x. If the CRS group ID value x is 1 in the CRS configuration, the REs of that CRS configuration will be available for the PDSCH scheduled by the DCI from the CORESET group x.

The following is an example of entering two CRS group IDs.

RateMatchPatternLTE-CRS ::= SEQUENCE {

CRS-group-id0 ENUMERATED {0,1} OPTIONAL,

CRS-group-id1 ENUMERATED {0,1} OPTIONAL,

carrierFreqDL INTEGER(0..16383),

carrierBandwidthDL ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1},

mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList OPTIONAL, -- Need M

nrofCRS-Ports ENUMERATED {n1, n2, n4},

v-Shift ENUMERATED {n0, n1, n2, n3, n4, n5}

}

Similar embodiments may be used for other rate matching parameters, including each rate matching pattern, CSI-RS ZP resource or resource set, CSI-RS NZP periodic or semi-persistent resource, or resource set or resource setting. To avoid modifying the RateMatchPatternLTE-CRS IE structure, in one embodiment, new RRC signaling may be introduced outside the RateMatchPatternLTE-CRS IE to inform the UE of the following: LTE CRS pattern not available for PDSCH scheduled DCI only from CORESET group ID 0, CRS pattern LTE is not available for DCI scheduled PDSCH from CORESET ID 1 only, LTE CRS pattern is not available for DCI scheduled PDSCH from any CORESET ID 0 and 1. In other words, the new RRC signaling is intended to provide a comparison with the UE as to whether each PDSCH CRS template from one CORESET or multiple CORESETs is available or not available. The new RRC signaling is UE specific and may be configured in PDSCH-ServingCellConfig or PDSCH-Config. In this case, multiple LTE CRS configurations are not cell-specific. After receiving multiple LTE CRS configurations, but before receiving new RRC signaling, all CRS configurations are not available for PDSCHs from all CORESET groups. For example, multiple CRS configurations such as 4 are configured in ServingCellConfigCommon and new RRC signaling is configured in PDSCH-ServingCellConfig as follows:

CRS_configuration0 ENUMERATED {0,1, 2}

CRS_configuration1 ENUMERATED {0,1, 2}

CRS_configuration2 ENUMERATED {0,1, 2}

CRS_configuration3 ENUMERATED {0,1, 2}

For each 0 CRS configuration, a value of 0 means that a 0 CRS configuration is not available for a PDSCH in CORESET group 0, a value of 1 means that a 0 CRS configuration is not available for a PDSCH in CORESET group 1, a value of 2 means that a 0 CRS configuration is not available for a PDSCH from any of the group 0 CORESET, nor from group 1.

Embodiment 3

As mentioned earlier, even when a non-ideal transport communication network is deployed, independent physical layer scheduling can be maintained among the coordinated TRPs. For the transmission of multiple TRPs based on a non-ideal transport network, separate indications of dynamic information for two coordinated TRPs can be maintained, especially a separate indication of QCL information.

Typically, the DCI Transmission configuration indication (TCI) is used to select one TCI state from N TCI states activated by the MAC CE, where N<=8. In addition, the MAC CE is used for activated N TCI states out of the M TCI states configured by RRC, where M<=128, or M depends on the capabilities of the UE. Due to the different directions from the two TRPs to the UE, both RRC configured TCI state candidates and MAC CE activated TCI states for the two coordinated TRPs may be separate. For example, it is possible to support two MAC CEs and two configured TCI RRC lists for two TRPs. However, supporting two MAC CEs increases the load on the MAC CEs. In particular, NR MACCE overhead has already become a big problem.

In order to support multiple TCI mapping between code points of the DCI Transfer Configuration Indication field and the TCI states activated by the MAC CE, in one embodiment, the TCI activation/deactivation fields of the MAC CE are divided into X sets of fields, and set x is associated with ID x CORESET groups where x is 0 ... X-1.

Option 3-1 Implementation

In one embodiment, as shown in Table 1 below, one MAC CE TCI enable/disable field refers to one T _i field. In addition, it can be predetermined that all TCI CE MAC activation/deactivation fields with a value of 1 are divided into X field sets. Assuming that the number of TCI CE MAC activation/deactivation fields with value 1 in the MAC CE object is Y, one embodiment is that each set may have TCI activation/deactivation fields floor(Y/X) or ceil(Y/X ) TCI. Y must be less than or equal to 16. The number of TCI CE MAC activation/deactivation fields for each set must not exceed 8, since the TCI field in DCI consists of only 3 bits.

For example, for the case where X=2, the total number of TCI CE MAC activation/deactivation fields is 128, Y=11 and T _i =1, i={2,3,8,18,23, 24, 50.62, 70,88,93}. Tj=0, j is not equal to i. Then, TCI states corresponding to {T2, T3, T8, T18, T23} are associated with CORESET group 0, and TCI states corresponding to {T24, T50, T62, T70, T88, T93} are associated with CORESET group 1. Thus, the first set includes floor(11/2)=5 TCI states and the second set includes 6 TCI states. Since the number of activated TCI states for multiple TRPs generally depends on frequency bands, the number of activated TCI states is the same or similar for different sets. If Y (the total number of T _i with value 1) is an even number, then two TRPs correspond to two CORESET group IDs having the same number of activated TCI states. In this example, the TCI code point in the DCI of CORESET with CORESET group ID 0 is for selecting one of the TCI states corresponding to {T2, T3, T8, T18, T23}, and the TCI code point in DCI of CORESET with CORESET group ID 1 is for to select one of the TCI states corresponding to {T24, T50, T62, T70, T88, T93}.

Table 1 Activation/deactivation of TCI states for UE-specific MAC PDSCH CE entity

Thus, a set x of TCI enable/disable fields CE MAC enable TCI states mapped to TCI code points in DCI mapped by CORESET to CORESET group ID x. In other words, the T _i field (in the TCI CE MAC enable/disable field set x) is set to 1 to indicate that the TCI state with TCI-StateId i is to be enabled and mapped to the code point of the DCI transmission configuration indication field, where DCI is taken from CORESET with CORESET group ID x. Thus, a TCI code point in a DCI of CORESET with CORESET group ID x must select one TCI state from the activated TCI states of set x.

Note that in Rel-15 for T _i : If there is a TCI state with TCI-StateId i as specified in the 5G TS 38.331 specification, this field indicates the activation/deactivation status of the TCI state with TCI-StateId i, otherwise the MAC object must ignore the field T _i . The T _i field is set to 1 to indicate that the TCI state with TCI-StateId i is to be enabled and mapped to the code point of the DCI transmission configuration indication field as specified in the 5G TS 38.214 specification. The T _i field is set to 0 to indicate that the TCI state with TCI-StateId i is to be deactivated and is not mapped to the code point of the DCI transmission configuration indication field. The code point to which the TCI state is mapped is determined by its ordinal position among all TCI states with the T _i field set to 1, i.e. the first TCI state with the T _i field set to 1 must be mapped to the code point value of 0, the second a TCI state with the T _i field set to 1 should be mapped to a code point value of 1, and so on. The maximum number of activated TCI states is 8.

Implementation option 3-2

The embodiment other than Embodiment 3-1 is to predetermine that all MAC CE TCI activation/deactivation fields are divided into X field sets. Assuming that the number of TCI CE MAC activation/deactivation fields in a MAC CE entity is Y, one embodiment is that each set may have TCI activation/deactivation fields floor(Y/X) or ceil(Y/X). In each set, the number of TCI activation/deactivation fields with a value of 1 must not exceed 8.

For example, for the case where X=2, the total number of TCI CE MAC activation/deactivation fields is 128, that is, Y=128 TCI CE MAC activation/deactivation fields divided into X=2 sets of fields, with {T0, ... , T63} is the first set, {T64, ..., T127} is the second set. The T _i field (in the first set, i.e. i=0,...,63) is set to 1 to indicate that the TCI state with TCI-StateId i is to be activated and mapped to the code point of the DCI transmission configuration indicator field, where DCI is taken from CORESET with CORESET group ID 0. The T _i field (in the first set, i.e., i=64,...,127) is set to 1 to indicate that the TCI state with TCI-StateId i is to be activated and mapped to the code point of the DCI transmission configuration indication field, where DCI is taken from CORESET with CORESET group ID 1. If T _i =1, i={2,3,8,18,23,24,50, 62,70,88,93}. Tj=0, j is not equal to i. Then, TCI states corresponding to {T2, T3, T8, T18, T23, T24, T50, T62} are associated with CORESET group 0, and TCI states corresponding to {T70, T88, T93} are associated with CORESET group 1. Thus, the first or second set includes 64 TCI CE MAC activation/deactivation fields, but a maximum of 8 TCI states, i.e. a maximum of 8 TCI CE MAC fields with a value of 1. to select one of the TCI states corresponding to {T2, T3, T8, T18, T23, T24, T50, T62}, and the TCI code point in the DCI of CORESET with ID 1 of the CORESET group is to select one of the TCI states corresponding to {T70 , T88, T93}.

Option 3-3 Implementation

Yet another embodiment is to partition the MAC CE TCI activation/deactivation fields into sets of X fields based on higher layer signaling. One embodiment is to configure X RRC configured TCI state lists, where one RRC configured TCI state list corresponds to one set of MAC CE TCI enable/disable fields. As shown in the following RRC configuration, the TCI states configured with tci-StatesToAddModList and tci-StatesToReleaseList correspond to the first set of MAC CE TCI enable/disable fields. The TCI states configured with tci-StatesToAddModList2 and tci-StatesToReleaseList2 correspond to the second set of TCI enable/disable fields of the MAC CE.

PDSCH-Config ::= SEQUENCE {

tci-StatesToAddModList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State

tci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId

tci-StatesToAddModList2 SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State

tci-StatesToReleaseList2 SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId

}

Thus, in the MAC CE entity as shown in Table 1 above, the first M1 TCI enable/disable fields of the MAC CE correspond to RRC configured TCI states from the first RRC configured TCI state list. M1 is the number of TCI states configured with tci-StatesToAddModList and tci-StatesToReleaseList. The remaining TCI CE MAC enable/disable fields correspond to RRC configured TCI states from the second list of RRC configured TCI states.

For example, M1=30 TCI states are in the first RRC configured TCI state lists and M2=98 TCI states are in the second RRC configured TCI state lists. In addition, the first 30 TCI CE MAC enable/disable fields belong to the first set of TCI CE MAC enable/disable fields. The remaining 98 TCI CE MAC enable/disable fields belong to the second set of TCI CE MAC enable/disable fields. Thus, the T _i field (in the MAC CE TCI activation/deactivation field set x) is set to 1 to indicate that the TCI state with TCI-StateId i is to be activated and mapped to the code point of the DCI transmission configuration indication field, where DCI is taken from CORESET with CORESET group ID x. Thus, a TCI code point in a DCI of CORESET with CORESET group ID x must select one TCI state from the enabled TCI states x of the sets.

Yet another embodiment is to explicitly configure the number M1 of TCI fields in the first set of TCI enable/disable fields of the MAC CE using RRC signaling. The rest belong to the second set. In addition, gNB can explicitly configure the relationship between M1 and M2. Another embodiment may configure a group ID for each configured TCI RRC state. Then, the configured TCI RRC states with group ID x correspond to the set x of TCI CE MAC enable/disable fields. The T _i field is then set to 1 to indicate that the TCI state with ID TCI-StateId i and with group ID x is to be activated and mapped to the code point of the DCI transmission configuration indicator field, where DCI is taken from CORESET with CORESET group ID x. Thus, a TCI code point in a DCI of a CORESET with a CORESET group ID x is to select one TCI state from a set of x TCI CE MAC enable/disable fields with a value of 1, where these TCI states are configured with a group ID x.

Option 3-4 implementation

In an embodiment, a single MAC CE may still be used, but a separate TCI code point mapping for multiple coordinated TRPs may be maintained, and Rel-15 MAC CEs may be completely reused. This embodiment can significantly reduce the MAC CE overhead.

However, a Rel-15 MAC CE can only support P TCI CE MAC enable/disable fields. In other words, T _i i must be less than P. To transmit multiple TRPs, if each TRP supports more than 64 RRC configured TCI states, the total number of RRC configured TCI states (same as P) will be greater than P, then CE MAC Rel-15 will not function. In this case, two separate MAC CE entities may be supported. But if the total number of RRC configured TCIs satisfies <=P, one MAC CE entity can still be used, typically P depends on the UE capabilities or RRC configuration. The maximum number of P is 128.

Option 3-5 implementation

In one embodiment, similar to the TCI case, a separate mapping of CSI trigger states between code points of the DCI CSI request field and CSI trigger states activated by the MAC CE can be maintained. As shown in Table 2 below, one CSI trigger status field activated by MAC CE refers to one T _i . Thus, in one embodiment, the solution is to divide the MAC CE CSI trigger state fields into X sets of fields, and set x is associated with a CORESET group ID x, where x is 0...X-1.

Table 2. Aperiodic CSI Trigger State Subselect MAC CE Entity

In an embodiment, a division of all MAC CE CSI trigger status fields with a value of 1 into X field sets may be specified. Assuming that the number of MAC CE CSI trigger state fields with value 1 in the MAC CE object is Y, one embodiment is that each set may have floor(Y/X) or ceil(Y/X) CSI trigger CSI trigger state fields . An alternative is to pre-determine that all CSI MAC CE trigger state fields are divided into X field sets. Assuming that the number of MAC CE CSI trigger state fields in the MAC CE entity is Y, one embodiment is that each set may have TCI activation/deactivation fields floor(Y/X) or ceil(Y/X) TCI.

In some embodiments, the MAC CE CSI trigger state fields may be partitioned into sets of X fields based on higher layer signaling. In another embodiment, X RRC configured CSI trigger state lists can be configured, one RRC configured CSI trigger state list corresponds to one set of MAC CE CSI trigger state fields. One CSI trigger state list configured by RRC is one higher level "aperiodicTriggerStateList" parameter in the current 5G standard 38.331. Thus, similar embodiments that support a separate TCI mapping can also be used for a separate CSI trigger state mapping.

Option 3-6 implementation

As described in Embodiment 3-4, two separate MAC CE entities may be supported for two coordinated TRP transmissions. However, when the UE receives one MAC CE entity, the UE may not be able to determine whether the MAC CE entity corresponds to ID 0 or 1 of the CORESET group, which may cause ambiguity.

In one embodiment, the ambiguity can be resolved by specifying some rules as follows. For example, if a MAC CE for activating/deactivating TCI PDSCH states is carried by a PDSCH that is scheduled by a DCI associated with CORESET ID 0, the MAC CE will correspond to CORESET ID 0. Then, the N TCI states activating the MAC CE entity are used for any DCI scheduled PDSCH associated with CORESET group ID 0. If the MAC CE for activating/deactivating TCI PDSCH states is carried by a PDSCH that is scheduled by a DCI associated with CORESET ID 1, the MAC CE will correspond to CORESET ID 1. The MAC CE object activating the N TCI states is then used for any DCI scheduled PDSCH associated with CORESET group ID 1.

A similar approach can be used for the CSI trigger. If the MAC CE entity for aperiodic CSI trigger state subselection is carried by the PDSCH that is scheduled by the DCI associated with CORESET group ID 0, the MAC CE entity will correspond to CORESET group ID 0. Then, CSI Q trigger states activating the MAC CE object are used for any DCI associated with CORESET group ID 0. If the MAC CE for aperiodic CSI trigger state subselection is carried by the PDSCH that is scheduled by the DCI associated with CORESET ID 1, the MAC CE will correspond to CORESET ID 1. Then, CSI Q trigger states activating the MAC CE object are used for any DCI associated with CORESET group ID 1.

While various embodiments of the present disclosure have been described above, it should be understood that they are provided by way of example only and not by way of limitation. Likewise, various diagrams may depict an exemplary architecture or configuration that is provided to enable those skilled in the art to understand the exemplary features and functions of the present disclosure. However, those skilled in the art will appreciate that the disclosure is not limited to the exemplary architectures or configurations illustrated, but may be implemented using a variety of alternative architectures and configurations. In addition, as will be understood by those skilled in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the illustrative embodiments described above.

It should also be understood that any reference to an element in this document using a designation such as "first", "second", etc., as a rule, does not limit the number or order of these elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, referring to the first and second elements does not mean that only two elements can be used, or that the first element must in any way precede the second element.

Furthermore, one of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and signal elements that may be referred to throughout the foregoing description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any their combination.

One of ordinary skill in the art will also appreciate that any of the various illustrative logical blocks, modules, processors, tools, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented using electronic hardware ( for example, a digital implementation, an analog implementation, or a combination thereof), firmware, programs of various kinds, or instructions including a code structure (which may be referred to herein as “software” or “software module” for convenience), or any combination these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art will be able to implement the described functionality in a variety of ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In addition, one of ordinary skill in the art will appreciate that the various illustrative logical blocks, modules, devices, components, and circuits described herein may be implemented within or implemented with an integrated circuit (IC), which may include general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may further include antennas and/or transceivers for communicating with various components on a network or within a device. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other suitable configuration to perform the functions described herein.

If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable storage medium. Thus, the steps of a method or algorithm disclosed herein may be implemented in software stored on a computer-readable storage medium. Computer-readable media includes both computer storage media and communication media, including any media that can be used to transfer a computer program or code from one place to another. A storage medium may be any available storage medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk drive, magnetic disk drive or other magnetic storage devices, or any other storage medium that can be used. to store the desired program code in the form of instructions or data structures that can be accessed by a computer.

Used in this document, the term "module" refers to software, firmware, hardware, and any combination of these elements to perform the associated functions described in this document. In addition, for purposes of discussion, various modules are described as discrete modules; however, as will be appreciated by one of skill in the art, two or more modules may be combined to form a single module that performs associated functions in accordance with embodiments of the present disclosure.

In addition, memory or other storage device as well as communication components may be used in embodiments of the present disclosure. It should be understood that, for the sake of clarity, the foregoing description has described embodiments of the present disclosure with reference to various functional blocks and processors. However, it will be apparent that any suitable distribution of functionality among different functional units, processing logic units, or domains may be used without prejudice to the present disclosure. For example, the illustrated functionality provided by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional blocks are only references to appropriate means to provide the functionality described, and do not indicate a strict logical or physical structure or organization.

Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be given the broadest scope consistent with the new features disclosed herein and the principles set forth in the claims below.

Claims (24)

1. A wireless communication method, comprising: configuring, by the wireless communication node, a plurality of state fields as two medium access control (MAC) control (CE) objects, each MAC CE object including a corresponding set of state fields from the plurality of state fields; associating, by the wireless communication node, two MAC CE entities with respective configuration resource set (CORESET) group IDs and with corresponding configured state group IDs, the group ID being configured for each configured state; And transmitting, by the wireless communication node to the wireless communication device, a MAC CE object of the two MAC CE objects and a corresponding CORESET group ID. 2. The method of claim 1, wherein each of the plurality of status fields includes at least one of: a transmission configuration indicator (TCI) status field or a channel status information (CSI) trigger status field. 3. A wireless communication method, comprising: receiving, by a wireless communication device from a wireless communication node, a medium access control (MAC) control entity (CE), wherein the MAC CE entity includes a set of state fields from a plurality of state fields, where the MAC CE object is associated with the corresponding configuration resource set (CORESET) group ID and with the corresponding configured state group IDs, the group ID being configured for each configured state. 4. The method of claim 1, wherein associating each MAC CE entity with a corresponding CORESET group identifier includes associating the MAC CE entity with a CORESET group identifier associated with downlink control information (DCI) that schedules a communication channel performed with the ability to carry a MAC CE object. 5. The wireless communication method of claim 3, wherein the plurality of state fields includes at least one of a transmission configuration indicator (TCI) state field or a channel state information (CSI) trigger state field. 6. The wireless communication method of claim 3, wherein for each MAC CE of the two MAC CEs, the corresponding CORESET group ID is a CORESET group ID associated with downlink control information (DCI) that schedules a communication channel performed with the ability to carry a MAC CE object. 7. A wireless communications device comprising a processor and a memory, the processor being configured to read a code from the memory to: configuring a plurality of state fields indicating a plurality of configured states as two medium access control (MAC) control (CE) objects, each MAC CE object including a corresponding set of state fields from the plurality of state fields; associating two MAC CE objects with respective configuration resource set (CORESET) group identifiers and with respective configured state group identifiers, the group identifier being configured for each configured state; And transmitting, to the wireless communication device, the MAC CE object and the corresponding CORESET group ID. 8. The wireless communications apparatus of claim 7, wherein the plurality of status fields includes at least one of a transmission configuration indicator (TCI) status field or a channel status information (CSI) trigger status field. 9. The wireless communications apparatus of claim 7, wherein upon associating each MAC CE entity with a corresponding CORESET group identifier, the processor is configured to associate the MAC CE entity with a CORESET group identifier associated with downlink control information (DCI) that schedules the channel. communication, configured to carry the object CE MAC. 10. A wireless communications device comprising a processor and a memory, the processor being configured to read a code from the memory to: receiving, from the wireless node, a medium access control (MAC) control (CE) object, wherein the MAC CE object includes a set of state fields from a plurality of state fields, where the MAC CE object is associated with the corresponding configuration resource set (CORESET) group ID and with the corresponding configured state group IDs, with the group ID configured for each configured state. 11. The wireless communications apparatus of claim 10, wherein the plurality of status fields includes at least one of a transmission configuration indicator (TCI) status field or a channel status information (CSI) trigger status field. 12. The wireless communications apparatus of claim 10, wherein for each MAC CE of the two MAC CEs, the corresponding CORESET group identifier is a CORESET group identifier associated with downlink control information (DCI) that schedules a communication channel performed with the ability to carry a MAC CE object. 13. A computer-readable storage medium containing program code stored thereon, wherein the program code, when executed by the processor, instructs the processor to implement the method specified in any one of claims 1, 2, and 4. 14. A computer-readable storage medium containing program code stored thereon, wherein the program code, when executed by the processor, instructs the processor to implement the method specified in any of claims 3, 5, and 6.

Images