Patent Description:
One type of information on the PDCCH is scheduling of a physical downlink shared channel (PDSCH) transmission and a beam over which 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) with scheduling of a PDSCH on a different component carrier (in a different serving cell). However, regardless of which beam is identified in the PDCCH, if the PDSCH is scheduled with a time offset that is less than a time it takes the UE to switch beams (timeDurationForQCL), the UE may use a default beam to receive the PDSCH. Also, if the gNB does not configure a beam for the UE to receive the PDSCH, the UE would also use the default beam to receive the PDSCH in this case. The default beam selected by the UE is the beam that corresponds to the lowest TCI codepoint from a plurality of TCI codepoints, each of which includes two different TCI states.

Multiple PDSCHs (e.g., two PDSCHs) may be scheduled for UE reception via multi-transmission reception points (TRP) to improve the throughput of the UE. The PDSCHs may partially or fully overlap in frequency (overlapping reference elements (REs)) and/or in time (e.g., two PDSCHs received at the same time).

Also, because <NUM> NR spectrum is difficult to obtain and expensive, operators have utilized dynamic spectrum sharing (DSS) so that <NUM> NR and Long Term Evolution (ETE) transmissions can coexist in the same spectrum. However, to minimize or eliminate interference between communications of the two networks, one method the <NUM> NR network may use is rate matching its signals around the LTE signals.

Further background information can be found in the following documents:.

The exemplary embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The exemplary embodiments relate to reporting user equipment (UE) physical downlink shared channel (PDSCH) overlapping capability with a gNB of a <NUM> new radio (NR) network. The exemplary embodiments further relate to default beam selection by a UE in self-scheduled and cross-carrier scheduled PDSCH reception. The exemplary embodiments further 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 by the UE.

The exemplary embodiments are described with regard to a UE. However, the use of a UE is merely for illustrative purposes. The exemplary embodiments may be utilized with any electronic component that may establish a connection with a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any electronic component.

The exemplary embodiments are also described with regard to a network that includes <NUM> NR radio access technology (RAT). However, reference to a <NUM> NR network is merely provided for illustrative purposes. The exemplary embodiments may be utilized with any network that implements multiple transmission and reception points. Therefore, the <NUM> NR network as described herein may represent any network that includes the functionalities associated with multi-TRP.

Release <NUM> of <NUM> NR supports multi-downlink control information (DCI), multi-transmission reception point (TRP) communications. As such, a UE can receive two physical downlink shared channel (PDSCH) transmissions from two TRPs. Release <NUM> also supports fully overlapping, partially overlapping, and non-overlapping PDSCHs in the time domain and/or the frequency domain. However, an issue that arises with two PDSCHs overlapping in the frequency domain (overlapping resource elements (REs)) is interference. The network is unaware of the capability of the UE to handle such overlapping.

According to exemplary embodiments, the UE may group capabilities regarding overlapping PDSCHs into a plurality of groups and report the UE's capability based on the groups to the gNB. In this manner, the network is advantageously aware of the UE's capabilities when scheduling more than one PDSCH.

In multi-DCI, multi-TRP communications some issues that may arise when scheduling the PDSCH are (<NUM>) the transmission configuration indicator (TCI) field in the downlink control information (DCI) of the PDSCH is not configured; or (<NUM>) 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 undesirable to require the UE to buffer all component carriers (CCs) on a serving cell to determine which beam to use to receive the PDSCH.

According to exemplary embodiments, the UE determines a default beam to receive the PDSCH that overcomes these issues.

In a dynamic spectrum sharing (DSS) environment, both <NUM> NR signals and LTE signals are transmitted within the same spectrum. However, a possible issue that arises from this coexistence on the same spectrum is interference when the DMRS of a <NUM> NR transmission collides with a cell-specific reference signal (CRS) of an LTE transmission.

According to exemplary embodiments, the gNB shifts the DMRS in some scenarios when a collision with a CRS is expected.

<FIG> shows an exemplary network arrangement <NUM> according to various exemplary embodiments. The exemplary network arrangement <NUM> includes a UE <NUM>. Those skilled in the art will understand that the UE <NUM> may be any type of electronic component that is configured to communicate via a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (IoT) devices, etc. It should also be understood that an actual network arrangement may include any number of UEs being used by any number of users. Thus, the example of a single UE <NUM> is merely provided for illustrative purposes.

The UE <NUM> may be configured to communicate with one or more networks. In the example of the network configuration <NUM>, the networks with which the UE <NUM> may wirelessly communicate are a <NUM> New Radio (NR) radio access network (<NUM> NR-RAN) <NUM>, an LTE radio access network (LTE-RAN) <NUM> and a wireless local access network (WLAN) <NUM>. However, it should be understood that the UE <NUM> may also communicate with other types of networks and the UE <NUM> may also communicate with networks over a wired connection. Therefore, the UE <NUM> may include a <NUM> NR chipset to communicate with the <NUM> NR-RAN <NUM>, an LTE chipset to communicate with the LTE-RAN <NUM> and an ISM chipset to communicate with the WLAN <NUM>.

The <NUM> NR-RAN <NUM> and the LTE-RAN <NUM> may be portions of cellular networks that may be deployed by cellular providers (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). These networks <NUM>, <NUM> may include, for example, cells or base stations (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc.) that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set. The WLAN <NUM> may include any type of wireless local area network (WiFi, Hot Spot, IEEE <NUM>. 11x networks, etc.).

The UE <NUM> may connect to the <NUM> NR-RAN <NUM> via the gNB 120A. The gNB 120A may be configured with the necessary hardware (e.g., antenna array), software and/or firmware to perform massive multiple in multiple out (MIMO) functionality. Massive MIMO may refer to a base station that is configured to generate a plurality of beams for a plurality of UEs. During operation, the UE <NUM> may be within range of a plurality of gNBs. Thus, either simultaneously or alternatively, the UE <NUM> may also connect to the <NUM> NR-RAN <NUM> via the gNB 120B. Reference to two gNBs 120A, 120B is merely for illustrative purposes. The exemplary embodiments may apply to any appropriate number of gNBs. Further, the UE <NUM> may communicate with the eNB 122A of the LTE-RAN <NUM> to transmit and receive control information used for downlink and/or uplink synchronization with respect to the <NUM> NR-RAN <NUM> connection. The gNB may perform various operation related to determining a shift of a DMRS when a collision between a DMRS of the <NUM> NR RAN <NUM> collides with a CRS of the LTE RAN <NUM>.

Those skilled in the art will understand that any association procedure may be performed for the UE <NUM> to connect to the <NUM> NR-RAN <NUM>. For example, as discussed above, the <NUM> NR-RAN <NUM> may be associated with a particular cellular provider where the UE <NUM> and/or the user thereof has a contract and credential information (e.g., stored on a SIM card). Upon detecting the presence of the <NUM> NR-RAN <NUM>, the UE <NUM> may transmit the corresponding credential information to associate with the <NUM> NR-RAN <NUM>. More specifically, the UE <NUM> may associate with a specific base station (e.g., the gNB 120A of the <NUM> NR-RAN <NUM>).

In addition to the networks <NUM>, <NUM> and <NUM> the network arrangement <NUM> also includes a cellular core network <NUM>, the Internet <NUM>, an IP Multimedia Subsystem (IMS) <NUM>, and a network services backbone <NUM>. The cellular core network <NUM> may be considered to be the interconnected set of components that manages the operation and traffic of the cellular network. The cellular core network <NUM> also manages the traffic that flows between the cellular network and the Internet <NUM>. The IMS <NUM> may be generally described as an architecture for delivering multimedia services to the UE <NUM> using the IP protocol. The IMS <NUM> may communicate with the cellular core network <NUM> and the Internet <NUM> to provide the multimedia services to the UE <NUM>. The network services backbone <NUM> is in communication either directly or indirectly with the Internet <NUM> and the cellular core network <NUM>. The network services backbone <NUM> may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that may be used to extend the functionalities of the UE <NUM> in communication with the various networks.

<FIG> shows an exemplary UE <NUM> according to various exemplary embodiments. The UE <NUM> will be described with regard to the network arrangement <NUM> of <FIG>. The UE <NUM> may represent any electronic device and may include a processor <NUM>, a memory arrangement <NUM>, a display device <NUM>, an input/output (I/O) device <NUM>, a transceiver <NUM> and other components <NUM>. The other components <NUM> may include, for example, an audio input device, an audio output device, a battery that provides a limited power supply, a data acquisition device, ports to electrically connect the UE <NUM> to other electronic devices, one or more antenna panels, etc..

The processor <NUM> may be configured to execute a plurality of engines of the UE <NUM>. For example, the engines may include a downlink (DL) management engine <NUM>. The DL management engine <NUM> may perform various operations related to determining UE capability with regards to PDSCH overlapping and default beam selection.

The above referenced engine being an application (e.g., a program) executed by the processor <NUM> is only exemplary. The functionality associated with the engine may also be represented as a separate incorporated component of the UE <NUM> or may be a modular component coupled to the UE <NUM>, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor <NUM> is split among two or more processors such as a baseband processor and an applications processor. The exemplary embodiments may be implemented in any of these or other configurations of a UE.

The memory arrangement <NUM> may be a hardware component configured to store data related to operations performed by the UE <NUM>. The display device <NUM> may be a hardware component configured to show data to a user while the I/O device <NUM> may be a hardware component that enables the user to enter inputs. The display device <NUM> and the I/O device <NUM> may be separate components or integrated together such as a touchscreen. The transceiver <NUM> may be a hardware component configured to establish a connection with the <NUM> NR-RAN <NUM>, the LTE-RAN <NUM>, the WLAN <NUM>, etc. Accordingly, the transceiver <NUM> may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies).

<FIG> shows a method <NUM> of performing overlapping PDSCH capability signaling by a UE (e.g., UE <NUM>) according to various exemplary embodiments. The method <NUM> assumes that the gNB 120A or 120B has two PDSCHs to transmit to the UE <NUM>. At <NUM>, the UE <NUM> groups the UE's capabilities for handling overlapping PDSCHs into multiple groups.

In some embodiments, the UE <NUM> may determine three (<NUM>) groups. In some embodiments, group <NUM> includes PDSCHs that do not overlap in the frequency domain, but are fully overlapping, partially overlapping, or not overlapping in the time domain. In this group, there is no interference of any REs between the two PDSCHs. However, the two PDSCHs can arrive in any temporal order. For example, the two PDSCHs can arrive at the same time or can overlap in time.

In some embodiments, group <NUM> includes PDSCHs that fully overlap. Group <NUM> can be classified in two ways: (<NUM>) both PDSCHs have the same number of resource blocks (RBs) and every resource elements (REs) of a first PDSCH overlaps with the REs of a second PDSCH; or (<NUM>) the first PDSCH includes the same amount of or 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 a subset of the first PDSCH REs. Although fully overlapping PDSCHs cause interference, this interference is constant because it is across all REs.

In some embodiments, group <NUM> includes PDSCHs that partially overlap. Group <NUM> can be classified in two ways: (<NUM>) for at least one PDSCH (the first OR second PDSCH), at least one RE does not overlap with an RE of the other PDSCH; or (<NUM>) for each PDSCH (the first AND second PDSCH), at least one RE does not overlap with an RE of the other PDSCH. In group <NUM>, demodulation of the PDSCHs will result in no interference on some REs but some interference on other REs. The UE <NUM> may use two receivers to handle the two PDSCHs (<NUM> for each PDSCH).

The above grouping is merely an example of how the UE <NUM> may group the UE's overlapping PDSCH capabilities. In some embodiments, the UE <NUM> may group its capabilities in any alternative manner. For example, in some embodiments, group <NUM> may include PDSCHs that do not overlap in frequency nor in time. In other words, each PDSCH is received at a different time than the other PDSCH and none of the REs of either PDSCH overlap with the REs of the other PDSCH. In some embodiments, group <NUM> may include PDSCHs that (<NUM>) fully overlap in the frequency domain; or (<NUM>) do not overlap in the frequency domain, but partially or fully overlap in the time domain.

At <NUM>, the UE <NUM> determines its capability of handling overlapping PDSCHs based on the groups the UE <NUM> determined at <NUM>. In some embodiments, the UE <NUM> may support only Group <NUM>. In some embodiments, the UE <NUM> may support all three groups. The UE <NUM> may support all or a subset of the capability groups. At <NUM>, the UE <NUM> transmits the capabilities to the gNB 120A or 120B. In some embodiments, the network may require that the UE mandatorily support a minimum functionality. For example, the network may require the UE <NUM> to support the functions of Group <NUM> and optionally support the functions of Groups <NUM> and <NUM>.

<FIG> shows a method <NUM> of selecting a TCI state(s) for beam selection according to various exemplary embodiments. At <NUM>, the UE <NUM> receives a PDCCH transmission including DCI information. At <NUM>, the UE <NUM> determines whether the TCI field in is configured in the DCI. If the DCI field is not configured (e.g., by the gNB 120a or 120b), at <NUM>, the UE <NUM> uses the CORESET associated with a monitored search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs within the active bandwidth part (BWP) of the serving cell are monitored. That is, the UE <NUM> selects the CORESET with the lowest ID in the slot in which the UE last monitored the PDCCH in the latest control monitoring duration. The UE <NUM> bases the default beam on the beam used for that particular CORESET for the PDSCH decoding.

If, at <NUM>, the UE <NUM> determines that the DCI field is configured, the UE determines, at <NUM>, whether the configured TCI field indicates a codepoint with two (<NUM>) TCI states. If the TCI field indicates a codepoint with two TCI states, the UE <NUM> uses, at <NUM>, the default beam to receive the single-DCI, multi-TRP scheduling. That is, when the UE <NUM> decodes the TCI field containing <NUM> states, the UE understands that two default beams are used to buffer the PDSCH. After the UE <NUM> decodes the DCI, the UE understands that two PDSCHs are to be decoded. So, the UE <NUM> uses the default beam that contains two TCI states to decode the single DCI, multi-TRP scheduling.

If, at <NUM>, the UE <NUM> determines that the TCI field indicates one (<NUM>) TCI state, the UE may handle this scenario in multiple manners at <NUM>. In this scenario, the UE <NUM> decodes the TCI field including one TCI state and realizes that only one PDSCH is to be decoded. Although the UE <NUM> has two sets of buffers, each having a different beam, it is unnecessary to buffer the single PDSCH using two different beams. In some embodiments, the UE <NUM> is allowed to autonomously/independently decide how to decode the single PDSCH (UE implementation). In some embodiments, the UE may use one of the sets of buffers to decode the PDSCH. In some embodiments, the UE <NUM> may use both sets of buffers to decode the PDSCH to improve performance. In some embodiments, a rule may exist for such a scenario. For example, the rule may instruct the UE <NUM> to prioritize the first TCI state and base the default beam on this TCI state. The rule may instruct the UE <NUM> to prioritize the second TCI state, if it exists, and base the default beam on this TCI state. However, if the second TCI state is absent from the TCI codepoint, then the UE <NUM> may then default to the first TCI state.

<FIG> shows a method <NUM> of determining a default beam in cross-carrier PDSCH scheduling according to various exemplary embodiments. In cross-carrier PDSCH scheduling, the PDCCH is received on a first CC/serving cell but the reception of the PDSCH scheduled by the CSI-RS is on a second CC/serving cell. At <NUM>, the UE <NUM> receives the PDCCH from a first serving cell (e.g., gNB 120a) that schedules reception of the PDSCH in a second serving cell (e.g., gNB 120b).

At <NUM>, the UE determines the default beam to use for reception of the PDSCH. In some embodiments, no default beam is selected. In such an embodiment, there a time offset between the DCI and PDSCH so that before PDSCH arrives, the UE <NUM> has enough time to decode the DCI. 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. As such, the UE needs enough time to switch beams.

In some embodiments, the UE <NUM> may base the default beam on the lowest codepoint from the plurality of TCI codepoints having two different TCI states in the scheduled cell (the cell in which the UE decodes the PDSCH). In some embodiments, the UE <NUM> may base the default beam on the lowest codepoint from the plurality of TCI codepoints having two different TCI states in the scheduling cell (the cell in which the UE decodes the DCI).

<FIG> a method <NUM> of determining a shift of a demodulated reference signal (DMRS) in a dynamic spectrum sharing (DSS) environment according to various exemplary embodiments. It is assumed that the network (e.g., LTE RAN <NUM>) can configure six (<NUM>) CRS patterns in each CC (three CRSs for each of the two TRPs). Although the CRS signal occupies symbols <NUM>, <NUM>, <NUM>, and <NUM>, the method <NUM> focuses on the collision between the DMRS and the CRS at symbol <NUM>.

At <NUM>, the gNB 120a or 120b determines whether the DMRS of a PDSCH collides with a CRS of an LTE signal. If no collision is detected, the gNB 120a/120b determines, at <NUM>, that no shift of the DMRS is necessary.

If, however, the gNB determines that a collision is detected at <NUM>, the gNB then determines, at <NUM>, if the CRS with which the DMRS collides is from the same TRP as the DMRS. If the CRS originates from a different TRP than the DMRS, the gNB determines, at <NUM>, that no shifting of the DMRS is necessary. If, however, the gNB determines that the CRS and the DMRS are from the same TRP, the gNB shifts, at <NUM>, the DMRS to the next symbol (e.g., symbol <NUM>).

In some embodiments, the gNB 120a/120b determines from which TRP the CRS originated based on a CORESETPoolIndex value in a multi-DCI, multi-TRP system or a TCI state in a TCI codepoint in a single-DCI, multi-TRP system. For example, in the multi-DCI, multi-TRP system, a CORESETPoolIndex value of <NUM> may refer to the first TRP and a CORESETPoolIndex value of <NUM> may refer to the second TRP. In the single-DCI, multi-TRP system, the first TCI state in the TCI codepoint may be mapped to the first TRP and the second TCI state in the TCI codepoint may be mapped to the second TRP.

In some embodiments, if, at <NUM>, the gNB 120A/120B determines that the DMRS collides with the CRS, the gNB may skip to <NUM> and shift the DMRS to the next symbol (e.g., symbol <NUM>) regardless of which TRP the CRS originated from.

Those skilled in the art will understand that the above-described exemplary embodiments may be implemented in any suitable software or hardware configuration or combination thereof. An exemplary hardware platform for implementing the exemplary embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc. In a further example, the exemplary embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor.

Claim 1:
A computer readable storage medium comprising instructions which, when executed by a computer, cause the computer to carry out the following steps:
receiving (<NUM>) a physical downlink control channel, PDCCH, transmission configured with downlink control information, DCI, in a single-DCI, multi-transmission/reception point, TRP, operation, wherein the DCI schedules reception of a physical downlink shared channel, PDSCH, transmission, wherein the PDCCH is received on a first serving cell and wherein the DCI includes scheduling of a reception of the PDSCH transmission on a second serving cell;
determining (<NUM>) whether or not a TCI field is configured in the DCI;
when the TCI field is not configured in the DCI, determining (<NUM>) a default beam based on a control resource set, CORESET, with the lowest ID in the PDCCH to decode the PDSCH;
when the TCI field is configured in the DCI, determining whether the TCI field indicates a TCI codepoint which includes two TCI states; and
when the TCI field indicates the codepoint includes two TCI states, selecting (<NUM>) a default beam having two TCI states to decode the single-DCI, multi-TRP scheduling.