Handling multi-TRP transmissions

Abstract

The invention relates to processing multiple TRP transmissions. A user equipment (UE) is configured with multiple transmission and reception point (multiple TRP) operation. The UE groups capabilities of handling two overlapping physical downlink shared channel (PDSCH) transmissions into a plurality of groups, determines UE capabilities of handling two overlapping PDSCH transmissions based on the plurality of groups, and transmits the UE capabilities to a next generation nodeB (gNB) of a 5G new air interface (NR) wireless network. The UE also determines whether a demodulation reference signal (DMRS) of a physical downlink shared channel (PDSCH) transmission collides with a cell-specific reference signal (CRS) of a long term evolution (LTE) transmission, and determines whether the CRS originates from the same multiple transmission / reception point (TRP) as the DMRS.

Description

[0001] This application is a divisional application of the PCT international application with an international application date of May 15, 2020, national application number 202080100866.3, and invention name “Processing Multiple TRP Transmissions” entering the Chinese national phase. Background Art

[0002] A user equipment (UE) may establish a connection with at least one of a plurality of different networks or network types. When establishing a network connection such as, for example, a connection with a 5G New Radio (NR) network, a next generation NodeB (gNB) transmits downlink control information (DCI) to the UE via a physical downlink control channel (PDCCH). The PDCCH is transmitted to the UE via one or more control resource sets (CORESETs), each control resource set including a transmission configuration indicator (TCI) state configured by the gNB.

[0003] One type of information on the PDCCH is the scheduling of Physical Downlink Shared Channel (PDSCH) transmissions and the beam that the UE should use to receive the PDCCH. In some cases, the UE may receive the PDCCH on one component carrier (in one serving cell) where the PDSCH is scheduled on a different component carrier (in a different serving cell). However, regardless of which beam is identified in the PDCCH, if the time offset at which the PDSCH is scheduled is less than the time required for the UE to switch beams (timeDurationForQCL), the UE may use a default beam to receive the PDSCH. Furthermore, if the gNB does not configure a beam for the UE to receive the PDSCH, in this case the UE will also use a default beam to receive the PDSCH. The default beam selected by the UE is the beam corresponding to the lowest TCI codepoint among multiple TCI codepoints, each TCI codepoint including two different TCI states.

[0004] Multiple PDSCHs (e.g., two PDSCHs) may be scheduled for reception by a UE via multiple transmission reception points (TRPs) to improve the throughput of the UE. The PDSCHs may partially or completely overlap in frequency (overlapping reference elements (REs)) and / or time (e.g., two PDSCHs received simultaneously).

[0005] Furthermore, because 5G NR spectrum is difficult to obtain and expensive, operators have utilized dynamic spectrum sharing (DSS) to allow 5G NR and Long Term Evolution (LTE) transmissions to coexist in the same spectrum. However, in order to minimize or eliminate interference between the communications of the two networks, one method that 5G NR networks can use is to rate match their signals around LTE signals. Summary of the invention

[0006] Some exemplary embodiments relate to a computer-readable storage medium including a set of instructions that, when executed by a processor, cause the processor to perform operations including grouping capabilities for processing two overlapping physical downlink shared channel (PDSCH) transmissions into a plurality of groups, determining UE capabilities for processing two overlapping PDSCH transmissions based on the plurality of groups, and transmitting the UE capabilities to a next generation nodeB (gNB) of a 5G New Radio (NR) wireless network.

[0007] Other exemplary embodiments relate to a computer-readable storage medium including a set of instructions that, when executed by a processor, cause the processor to perform operations including determining whether a demodulation reference signal (DMRS) of a physical downlink shared channel (PDSCH) transmission collides with a cell-specific reference signal (CRS) of a long-term evolution (LTE) transmission and determining whether the CRS originates from the same multiple transmission / reception points (TRPs) as the DMRS.

[0008] Still other exemplary embodiments relate to a user equipment having a transceiver and a processor. The transceiver is configured to connect to a first next generation NB (gNB) and a second gNB in ​​a single downlink control information (DCI), multiple transmission / reception point (TRP) configuration. The processor is configured to: group capabilities to handle two overlapping physical downlink shared channel (PDSCH) transmissions into a plurality of groups, and determine UE capabilities to handle two overlapping PDSCH transmissions based on the plurality of groups. The transceiver is further configured to transmit the UE capabilities to one of the first gNB or the second gNB. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0010] Figure 2 An exemplary UE according to various exemplary embodiments is shown.

[0011] Figure 3 Methods of performing overlapped PDSCH capability signaling by a user equipment (UE) according to various exemplary embodiments are shown.

[0012] Figure 4 Methods of selecting TCI states for beam selection according to various exemplary embodiments are shown.

[0013] Figure 5 Methods of determining a default beam in cross-carrier PDSCH scheduling according to various exemplary embodiments are shown.

[0014] Figure 6A method of determining a shift of a demodulation reference signal (DMRS) in a dynamic spectrum sharing (DSS) environment according to various exemplary embodiments. DETAILED DESCRIPTION

[0015] The exemplary embodiments may be further understood with reference to the following description and associated drawings, in which similar elements have the same reference numerals. The exemplary embodiments relate to reporting user equipment (UE) physical downlink shared channel (PDSCH) overlap capability with a gNB of a 5G New Radio (NR) network. The exemplary embodiments also relate to default beam selection performed by a UE in self-scheduled and cross-carrier scheduled PDSCH reception. The exemplary embodiments also relate to determining a shift of a demodulation reference signal (DMRS) in a dynamic spectrum sharing (DSS) environment. The exemplary embodiments advantageously improve throughput and reception performed by a UE.

[0016] The exemplary embodiments are described with respect to UE. However, the use of UE is for illustration purposes only. The exemplary embodiments can be utilized with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any electronic component.

[0017] The exemplary embodiments are also described with reference to a network including a 5G NR radio access technology (RAT). However, reference to a 5G NR network is provided for illustration purposes only. The exemplary embodiments may be used with any network that implements multiple transmission and reception points. Therefore, a 5G NR network as described herein may represent any network that includes functionality associated with multiple TRPs.

[0018] Release 16 of 5G NR supports multi-downlink control information (DCI), multi-transmission reception point (TRP) communication. Therefore, the UE can receive two physical downlink shared channel (PDSCH) transmissions from two TRPs. Release 16 also supports fully overlapping, partially overlapping, and non-overlapping PDSCH in the time domain and / or frequency domain. However, the problem of two PDSCHs overlapping in the frequency domain (overlapping resource elements (REs)) is interference. The network is not aware of the UE's ability to handle such overlaps.

[0019] According to an exemplary embodiment, the UE may group the capabilities of the overlapping PDSCH into multiple groups and report the capabilities of the UE to the gNB based on the group. In this way, the network is advantageously aware of the capabilities of the UE when scheduling more than one PDSCH.

[0020] In multi-DCI, multi-TRP communications, some issues that may arise when scheduling PDSCH are: (1) the Transmission Configuration Indicator (TCI) field in the Downlink Control Information (DCI) of the PDSCH is not configured; or (2) the UE does not have enough time to switch beams to receive the PDSCH scheduled by the gNB. In the case of cross-carrier PDSCH scheduling, it is not desirable to require the UE to buffer all component carriers (CCs) on the serving cell to determine which beam to use to receive the PDSCH.

[0021] According to an exemplary embodiment, the UE determines a default beam to receive the PDSCH that overcomes these problems.

[0022] In a dynamic spectrum sharing (DSS) environment, both 5G NR signals and LTE signals are transmitted in the same spectrum. However, a possible problem arising from this coexistence on the same spectrum is interference when the DMRS transmitted by 5G NR collides with the cell-specific reference signal (CRS) transmitted by LTE.

[0023] According to an exemplary embodiment, the gNB shifts the DMRS in some scenarios when a conflict with the CRS is expected.

[0024] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. It should also be appreciated that an actual network arrangement may include any number of UEs used by any number of users. Therefore, for purposes of illustration, only an example with a single UE 110 is provided.

[0025] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 100, the networks with which UE 110 may wirelessly communicate are 5G New Radio (NR) radio access network (5GNR-RAN) 120, LTE radio access network (LTE-RAN) 122, and wireless local area network (WLAN) 124. However, it should be understood that UE 110 may also communicate with other types of networks, and UE 110 may also communicate with the network through a wired connection. Therefore, UE 110 may include a 5G NR chipset that communicates with 5G NR-RAN 120, an LTE chipset that communicates with LTE-RAN 122, and an ISM chipset that communicates with WLAN 124.

[0026] 5G NR-RAN 120 and LTE-RAN 122 may be part of cellular networks that may be deployed by cellular providers (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). These networks 120, 122 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0027] The UE 110 may be connected to the 5G NR-RAN 120 via a gNB 120A. The gNB 120A may be configured with the necessary hardware (e.g., antenna array), software and / or firmware to perform massive multiple-input multiple-output (MIMO) functionality. Massive MIMO may refer to a base station configured to generate multiple beams for multiple UEs. During operation, the UE 110 may be within range of multiple gNBs. Therefore, simultaneously or alternatively, the UE 110 may also be connected to the 5G NR-RAN 120 via a gNB 120B. Reference to two gNBs 120A, 120B is for illustrative purposes only. The exemplary embodiments may apply to any appropriate number of gNBs. In addition, the UE 110 may communicate with the eNB 122A of the LTE-RAN 122 to transmit and receive control information for downlink and / or uplink synchronization of the connection with respect to the 5G NR-RAN 120. When a conflict occurs between the DMRS of the 5G NR RAN 120 and the CRS of the LTE RAN 122, the gNB may perform various operations related to determining a shift of the DMRS.

[0028] Those skilled in the art will appreciate that any relevant process may be performed for the UE 110 to connect to the 5G NR-RAN 120. For example, as described above, the 5G NR-RAN 120 may be associated with a particular cellular provider, where the UE 110 and / or its user has a protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may transmit corresponding credential information in order to associate with the 5G NR-RAN 120. More specifically, the UE 110 may be associated with a particular base station (e.g., gNB 120A of the 5G NR-RAN 120).

[0029] In addition to the networks 120, 122, and 124, the network arrangement 100 includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and communication traffic of the cellular network. The cellular core network 130 also manages the communication traffic flowing between the cellular network and the Internet 140. The IMS 150 can be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0030] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1 100 is used to describe the UE 110. The UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a battery to provide a limited power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, one or more antenna panels, etc.

[0031] The processor 205 may be configured to execute multiple engines of the UE 110. For example, the engines may include a downlink (DL) management engine 235. The DL management engine 235 may perform various operations related to determining UE capabilities regarding PDSCH overlap and default beam selection.

[0032] The above-described engine as an application (e.g., program) executed by the processor 205 is merely exemplary. The functions associated with the engine may also be represented as an independent combined component of the UE 110, or may be a modular component coupled to the UE 110, for example, an integrated circuit with or without firmware. For example, an integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing the signal and other information. The engine may also be embodied as an application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 205 is shared between two or more processors such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0033] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables user input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, LTE-RAN 122, WLAN 124, etc. Thus, the transceiver 225 may operate on multiple different frequencies or channels (e.g., a continuous set of frequencies).

[0034] Figure 3 A method 300 of performing overlapping PDSCH capability signaling by a UE (e.g., UE 110) according to various exemplary embodiments is shown. The method 300 assumes that the gNB 120A or 120B has two PDSCHs to transmit to the UE 110. At 305, the UE 110 groups the capabilities of the UEs for handling overlapping PDSCHs into a plurality of groups.

[0035] In some embodiments, UE 110 may determine three (3) groups. In some embodiments, Group 1 includes PDSCHs that do not overlap in the frequency domain, but completely overlap, partially overlap, or do not overlap in the time domain. In this group, there is no interference between any REs of two PDSCHs. However, the two PDSCHs may arrive in any time order. For example, the two PDSCHs may arrive at the same time or may overlap in time.

[0036] In some embodiments, Group 2 includes completely overlapping PDSCHs. Group 2 can be classified in two ways: (1) the two PDSCHs have the same number of resource blocks (RBs), and each resource element (RE) of the first PDSCH overlaps with an RE of the second PDSCH; or (2) the first PDSCH includes the same amount of RBs as the second PDSCH or includes more RBs than the second PDSCH, and some of the REs of the first PDSCH overlap with all of the REs of the second PDSCH. That is, the second PDSCH REs can be considered as a subset of the first PDSCH REs. Although completely overlapping PDSCHs can cause interference, this interference is constant because it spans all REs.

[0037] In some embodiments, Group 3 includes partially overlapping PDSCHs. Group 3 can be classified in two ways: (1) for at least one PDSCH (either the first or second PDSCH), at least one RE does not overlap with the RE of the other PDSCH; or (2) for each PDSCH (the first and second PDSCH), at least one RE does not overlap with the RE of the other PDSCH. In Group 3, demodulation of the PDSCH will result in no interference on some REs, but some interference on other REs. UE 110 can use two receivers to process two PDSCHs (using 1 receiver for each PDSCH).

[0038] The above groupings are merely examples of how UE 110 may group the UE's overlapping PDSCH capabilities. In some embodiments, UE 110 may group its capabilities in any alternative manner. For example, in some embodiments, Group 1 may include PDSCHs that do not overlap in frequency or in time. In other words, each PDSCH is received at a different time than another PDSCH, and the REs of any one PDSCH do not overlap with the REs of another PDSCH. In some embodiments, Group 2 may include PDSCHs that (1) completely overlap in the frequency domain; or (2) do not overlap in the frequency domain, but partially or completely overlap in the time domain.

[0039] At 310, UE 110 determines its capability to handle overlapping PDSCH based on the group determined by UE 110 at 305. In some embodiments, UE 110 may only support group 1. In some embodiments, UE 110 may support all three groups. UE 110 may support all or a subset of the capability groups in the capability group. At 315, UE 110 transmits the capability to gNB 120A or 120B. In some embodiments, the network may require the UE to support minimum functionality. For example, the network may require UE 110 to support the functionality of group 1 and optionally support the functionality of groups 2 and 3.

[0040] Figure 4A method 400 of selecting a TCI state for beam selection according to various exemplary embodiments is shown. At 405, the UE 110 receives a PDCCH transmission including DCI information. At 410, the UE 110 determines whether the TCI field is configured in the DCI. If the DCI field is not configured (e.g., by the gNB 120a or 120b), at 420, the UE 110 uses the CORESET with the lowest controlResourceSetId associated with the monitored search space in the most recent timeslot in which one or more CORESETs within the active bandwidth part (BWP) of the serving cell are monitored. That is, the UE 110 selects the CORESET with the lowest ID in the timeslot in which the UE last monitored the PDCCH within the most recent control monitoring duration. The UE 110 bases the default beam on the beam of the specific CORESET used for decoding for the PDSCH.

[0041] At 410, if the UE 110 determines that the DCI field is configured, then at 415, the UE determines whether the configured TCI field indicates a code point with two (2) TCI states. If the TCI field indicates a code point with two TCI states, then at 425, the UE 110 uses a default beam to receive a single DCI, multiple TRP schedule. That is, when the UE 110 decodes the TCI field with 2 states, the UE understands that two default beams are used to buffer the PDSCH. After the UE 110 decodes the DCI, the UE understands that two PDSCHs will be decoded. Therefore, the UE 110 uses a default beam with two TCI states to decode the single DCI, multiple TRP schedule.

[0042] If at 415, UE 110 determines that the TCI field indicates one (1) TCI state, the UE may handle this scenario in a variety of ways at 430. In this scenario, UE 110 decodes the TCI field including one TCI state and realizes that only one PDSCH will be decoded. Although UE 110 has two sets of buffers, each with different beams, it is not necessary to use two different beams to buffer a single PDSCH. In some embodiments, UE 110 is allowed to autonomously / independently decide how to decode a single PDSCH (UE specific implementation). In some embodiments, the UE may use one of the two sets of buffers to decode the PDSCH. In some embodiments, UE 110 may use the two sets of buffers to decode the PDSCH to improve performance. In some embodiments, there may be rules for such rules. For example, the rule may instruct UE 110 to prioritize a first TCI state and base the default beam on this TCI state. The rule may instruct UE 110 to prioritize a second TCI state (if any) and base the default beam on this TCI state. However, if the second TCI state is not present in the TCI code point, then UE 110 may then default to the first TCI state.

[0043] Figure 5 A method 500 of determining a default beam in cross-carrier PDSCH scheduling according to various exemplary embodiments is shown. In cross-carrier PDSCH scheduling, a PDCCH is received on a first CC / serving cell, but a PDSCH scheduled by a CSI-RS is received on a second CC / serving cell. At 505, UE 110 receives a PDCCH from a first serving cell (e.g., gNB 120a) that schedules reception of a PDSCH in a second serving cell (e.g., gNB 120b).

[0044] At 510, the UE determines a default beam for reception of the PDSCH. In some embodiments, no default beam is selected. In this embodiment, there is a time offset between the DCI and the PDSCH so that the UE 110 has sufficient time to decode the DCI before the PDSCH arrives. If the gNB does not explicitly identify which beam should be used to receive the PDSCH, the UE may buffer the PDSCH to determine which beam to receive the PDSCH on. Therefore, the UE needs sufficient time to switch beams.

[0045] In some embodiments, UE 110 may base the default beam on the lowest code point among multiple TCI code points with two different TCI states in the scheduled cell (the cell where the UE decodes the PDSCH). In some embodiments, UE 110 may base the default beam on the lowest code point among multiple TCI code points with two different TCI states in the scheduling cell (the cell where the UE decodes the DCI).

[0046] Figure 6 A method 600 for determining a shift of a demodulation reference signal (DMRS) in a dynamic spectrum sharing (DSS) environment according to various exemplary embodiments is provided. Assume that a network (e.g., LTE RAN 122) can configure six (6) CRS patterns in each CC (three CRSs in each of two TRPs). Although CRS signals occupy symbols 0, 4, 7, and 11, the method 600 focuses on the collision between DMRS and CRS at symbol 11.

[0047] At 605, the gNB 120a or 120b determines whether the DMRS of the PDSCH collides with the CRS of the LTE signal. If no collision is detected, the gNB 120a / 120b determines at 615 that a shift of the DMRS is not required.

[0048] However, if the gNB determines at 605 that a collision is detected, the gNB then determines at 610 whether the CRS that collided with the DMRS is from the same TRP as the DMRS. If the CRS and the DMRS are from different TRPs, the gNB determines at 625 that no shifting of the DMRS is required. However, if the gNB determines that the CRS and the DMRS are from the same TRP, then at 620, the gNB shifts the DMRS to the next symbol (e.g., symbol 12).

[0049] In some embodiments, the gNB 120a / 120b determines which TRP the CRS originates from based on the CORESETPoolIndex value in a multi-DCI, multi-TRP system or the TCI state in a TCI codepoint in a single DCI, multi-TRP system. For example, in a multi-DCI, multi-TRP system, a CORESETPoolIndex value of 0 may refer to the first TRP, while a CORESETPoolIndex value of 1 may refer to the second TRP. In a single DCI, multi-TRP system, a first TCI state in a TCI codepoint may be mapped to the first TRP, while a second TCI state in a TCI codepoint may be mapped to the second TRP.

[0050] In some embodiments, if gNB 120A / 120B determines at 605 that the DMRS collides with the CRS, the gNB may jump to 620 and shift the DMRS to the next symbol (e.g., symbol 12) regardless of which TRP the CRS originates from.

[0051] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.

[0052] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0053] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. In other examples, the exemplary embodiments of the above methods may be embodied as a program including lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0054] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. An apparatus, comprising a processing circuit, wherein the processing circuit is configured to: Determining that the user equipment (UE) supports multiple transmission and reception point (multi-TRP) operation based on multiple downlink control information (multi-DCI) with the network; determining capabilities of the UE in multi-DCI multi-TRP operation related to overlapping physical downlink shared channel (PDSCH) transmissions from the network; as well as An information element (IE) indicating the capability of the UE related to the overlapping PDSCH transmission is generated for transmission to the network.

2. The apparatus of claim 1, wherein the capability is related to PDSCH transmissions that overlap in time but not in frequency. 3 . The apparatus of claim 2 , wherein the PDSCH transmissions completely overlap in time or partially overlap in time.

4. The device according to claim 2, wherein: For multi-DCI multi-TRP operation with the network, the UE supports the capability associated with PDSCH transmissions that overlap in time but not in frequency.

5. An apparatus according to claim 1, wherein the capability is related to PDSCH transmissions that completely overlap in frequency, wherein the overlap in frequency includes a first PDSCH transmission in a first group of PDSCH transmissions completely overlapping on a first resource element (RE) with a second PDSCH transmission in a second group of PDSCH transmissions on a second RE. 6 . The apparatus of claim 5 , wherein the first group of PDSCH transmissions and the second group of PDSCH transmissions completely overlap on each RE.

7. The device according to claim 5, wherein: For multi-DCI multi-TRP operation with the network, the UE is not required to support the capability associated with PDSCH transmissions that completely overlap in frequency.

8. An apparatus according to claim 1, wherein the capability is related to PDSCH transmissions that partially overlap in frequency, wherein the overlap in frequency includes a first PDSCH transmission in a first group of PDSCH transmissions partially overlapping on a first resource element (RE) with a second PDSCH transmission in a second group of PDSCH transmissions on a second RE.

9. The apparatus of claim 8, wherein at least one PDSCH transmission in the first set of PDSCH transmissions does not overlap in frequency with any PDSCH transmission in the second set of PDSCH transmissions.

10. The device according to claim 8, wherein: For multi-DCI multi-TRP operation with the network, the UE is not required to support the capability associated with PDSCH transmissions that partially overlap in frequency.

11. A user equipment (UE), comprising: a transceiver circuit configured to communicate with a network; as well as a processing circuit communicatively coupled to the transceiver circuit and configured to: determining that a user equipment (UE) supports multiple downlink control information (multi-DCI) based multiple transmission and reception point (multi-TRP) operation with the network; determining capabilities of the UE in multi-DCI multi-TRP operation related to overlapping physical downlink shared channel (PDSCH) transmissions from the network; as well as An information element (IE) indicating the capability of the UE related to the overlapping PDSCH transmission is generated for transmission to the network.

12. The UE of claim 11, wherein the capability is related to PDSCH transmissions that overlap in time but not in frequency.

13. The UE of claim 12, wherein the PDSCH transmissions completely overlap in time or partially overlap in time.

14. The UE according to claim 12, wherein: For multi-DCI multi-TRP operation with the network, the UE supports the capability associated with PDSCH transmissions that overlap in time but not in frequency.

15. The UE of claim 11, wherein the capability is related to PDSCH transmissions that are completely overlapped in frequency, wherein the overlap in frequency includes a first PDSCH transmission in a first group of PDSCH transmissions on a first resource element (RE) completely overlapping with a second PDSCH transmission in a second group of PDSCH transmissions on a second RE. 16 . The UE of claim 15 , wherein the first group of PDSCH transmissions and the second group of PDSCH transmissions completely overlap on each RE.

17. The UE according to claim 15, wherein: For multi-DCI multi-TRP operation with the network, the UE is not required to support the capability associated with PDSCH transmissions that completely overlap in frequency.

18. A UE according to claim 11, wherein the capability is related to PDSCH transmissions that partially overlap in frequency, wherein the overlap in frequency includes a first PDSCH transmission in a first group of PDSCH transmissions partially overlapping on a first resource element (RE) with a second PDSCH transmission in a second group of PDSCH transmissions on a second RE.

19. The UE of claim 18, wherein at least one PDSCH transmission in the first set of PDSCH transmissions does not overlap in frequency with any PDSCH transmission in the second set of PDSCH transmissions.

20. The UE according to claim 18, wherein: For multi-DCI multi-TRP operation with the network, the UE is not required to support the capability associated with PDSCH transmissions that partially overlap in frequency.

Images