Preemption during CSI-RS mobility measurements

Abstract

The present disclosure relates to “Preemption during CSI-RS mobility measurement”. A base station is disclosed, the base station communicating with a first user equipment (UE) and a second UE. The base station determines a first configuration of the first UE for a channel state information reference signal (CSI-RS) on a symbol; schedules data transmission of the second UE on the symbol, wherein the CSI-RS is configured such that the CSI-RS and the data transmission collide on the symbol; and when the CSI-RS and the data transmission collide on the symbol, determines a second configuration of the first UE.

Description

[0001] Priority claim / incorporation by reference

[0002] This patent application claims priority to U.S. Provisional Application Serial No. 63 / 028,323, filed on May 21, 2020, entitled “Pre-emption During CSI-RS Mobility Measurements,” which is incorporated herein by reference in its entirety. Background Art

[0003] Channel state information reference symbols (CSI-RS) may be configured by a 5G New Radio (NR) network for a user equipment (UE) to perform mobility measurements. The UE may monitor the downlink channel for CSI-RS transmissions from the network according to the resource locations identified by the CSI-RS configuration. Upon receiving the CSI-RS transmission, the UE may generate channel quality information (CQI) for the serving cell and / or one or more neighboring cells, e.g., for layer 3 (L3) mobility management.

[0004] Preemption involves prioritization of data traffic for specific applications that require fast and reliable data transmission, such as public safety applications. For example, in 5G NR, a UE in an enhanced mobile broadband (eMBB) configuration may have an eMBB service preempted by an ultra-reliable low latency communication (URLLC) service. A preemption indication may be transmitted to the UE, and the UE may assume that there is no transmission to the UE in the physical resource block (PRB) and the OFDM symbol indicated by the preemption bit. However, when the OFDM symbol indicated by the preemption bit collides with the UE's CSI-RS transmission, the UE behavior for mobility measurements may be unclear. Summary of the invention

[0005] Some exemplary embodiments relate to a processor of a base station that communicates with a first user equipment (UE) and a second UE and is configured to perform operations. The operations include determining a first configuration of the first UE for a channel state information reference signal (CSI-RS) on a symbol; scheduling data transmission of the second UE on the symbol, wherein the CSI-RS is configured such that the CSI-RS and the data transmission collide on the symbol; and when the CSI-RS and the data transmission collide on the symbol, determining a second configuration of the first UE.

[0006] Other exemplary embodiments relate to a processor of a first base station that communicates with a first user equipment (UE) and a second UE and is configured to perform operations. The operations include exchanging timing information with the second base station; determining whether a channel state information reference signal (CSI-RS) configured for the first UE for measuring CSI on the second base station collides with a data transmission of the second UE on the same symbol x; and configuring a zero power CSI-RS (ZP-CSI-RS) as the CSI-RS for the first UE CSI measurement on the second base station.

[0007] Yet another exemplary embodiment relates to a processor of a first base station, the first base station communicating with a first user equipment (UE) and a second UE and configured to perform operations. The operations include configuring the second UE for data transmission on symbol x; and transmitting a preemption indication to the first UE on symbol x, wherein the preemption indication configures the first UE to not decode a physical downlink shared channel (PDSCH) on symbol x, and when a channel state information reference signal (CSI-RS) is configured for the first UE to measure CSI from the second base station on symbol x, the first UE performs the CSI measurement on symbol x.

[0008] Additional exemplary embodiments relate to a processor of a base station that communicates with a first user equipment (UE) and a second UE and is configured to perform operations. The operations include determining a configuration of the first UE for a special physical downlink shared channel (PDSCH) on a symbol; scheduling data transmission of the second UE on the symbol, wherein the special PDSCH is configured so that the special PDSCH and the data transmission collide; and transmitting a preemption indication for the symbol to the first UE, wherein the first UE ignores the preemption indication and decodes the special PDSCH.

[0009] Additional exemplary embodiments relate to a processor of a base station that communicates with a first user equipment (UE) and a second UE in an ultra-reliable low-latency communication (URLLC) configuration and is configured to perform operations. The operations include determining a configuration of the first UE for a special physical downlink shared channel (PDSCH) on a symbol; and scheduling data transmission of the second UE on the symbol, wherein the special PDSCH is configured such that the special PDSCH and the data transmission collide; wherein the second UE ignores the data transmission and decodes the PDSCH.

[0010] Still other exemplary embodiments relate to a processor of a base station that communicates with a user equipment (UE) in an ultra-reliable low-latency communication (URLLC) configuration and is configured to perform operations. The operations include determining a configuration of the UE for a mobility downlink (DL) measurement of the base station or one or more neighboring base stations on a symbol; and scheduling a data transmission of the UE on the symbol, wherein the special PDSCH is configured such that the special PDSCH and the data transmission collide; wherein the UE decodes the data transmission in preference to the mobility DL measurement. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 Network arrangements according to various exemplary embodiments are shown.

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

[0013] Figure 3 An exemplary network base station is shown according to various exemplary embodiments.

[0014] Figure 4 Methods for performing mobility measurements for a UE in an enhanced mobile broadband (eMBB) configuration according to various exemplary embodiments are shown.

[0015] Figure 5 A first network configuration for performing L3 CSI-RS neighbor cell measurements according to various exemplary embodiments is shown.

[0016] Figure 6 A second network configuration for performing L3 CSI-RS neighbor cell measurements according to various exemplary embodiments is shown. DETAILED DESCRIPTION

[0017] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein similar elements have the same reference numerals. The exemplary embodiments describe a network configuration for a user equipment (UE) to manage a scenario in which a mobility measurement reference signal (e.g., a channel state information reference signal (CSI-RS)) may conflict / collide with a high priority data (e.g., URLLC data transmission).

[0018] Figure 1An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a plurality of UEs 110, 112. Those skilled in the art will appreciate that a UE may be any type of electronic component configured to communicate via a network, such as a component of a connected car, a mobile phone, a tablet computer, a smart phone, a tablet phone, 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, an example with two UEs 110, 112 is provided for illustrative purposes only. In some exemplary embodiments described below, a UE group may be employed to perform corresponding channel measurements.

[0019] UE 110, 112 can communicate directly with one or more networks. In the example of network configuration 100, the network with which UE 110, 112 can wirelessly communicate is 5G NR radio access network (5G NR-RAN) 120, LTE radio access network (LTE-RAN) 122 and wireless local area network (WLAN) 124. Therefore, UE 110, 112 may include a 5G NR chipset communicating with 5G NR-RAN 120, an LTE chipset communicating with LTE-RAN 122, and an ISM chipset communicating with WLAN 124. However, UE 110, 112 may also communicate with other types of networks (e.g., traditional cellular networks), and UE 110 may also communicate with the network through a wired connection. With respect to an exemplary embodiment, UE 110, 112 may establish a connection with 5G NR RAN 122. The connection may be either an enhanced mobile broadband (eMBB) connection or an ultra-reliable low latency communication (URLLC) connection.

[0020] 5G NR-RAN 120 and LTE-RAN 122 may be parts of cellular networks that may be deployed by cellular providers (e.g., Verizon, AT&T, 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.).

[0021] UE 110, 112 may be connected to 5G NR-RAN via at least one of next generation Node B (gNB) 120A and / or gNB 120B. gNB 120A, 120B may be configured with 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. Reference to two gNBs 120A, 120B is for illustrative purposes only. The exemplary embodiments may apply to any appropriate number of gNBs. UE 110, 112 may also be connected to LTE-RAN 122 via either or both of eNBs 122A, 122B, or to any other type of RAN, as described above.

[0022] In the network arrangement 100, UEs 110, 112 are shown as having a connection with a gNB 120A. In some embodiments, UE 110 may be connected to gNB 120A via an eMBB connection, and UE 112 may be connected to gNB 120A via a URLLC connection. gNB 120A may transmit a preemption indication to an eMBB UE (e.g., UE 110) such that a URLLC data transmission may be sent to the URLLC UE (e.g., UE 112) on a preemption symbol where transmissions over the eMBB connection cause little or no interference. The preemption indication may be a downlink control information (DCI) signal, e.g., DCI format 2_1. gNB 120B may be a neighboring cell of gNB 120A and may be used for channel state information (CSI) measurements, as described in further detail below.

[0023] 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 traffic of the cellular network. The cellular core network 130 also manages the 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.

[0024] Figure 2An 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 providing a limited power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, a sensor for detecting the status of the UE 110, and the like. Figure 2 The UE 110 shown may also represent UE 112.

[0025] Processor 205 may be configured to execute multiple engines of UE 110. For example, the engines may include CSI engine 235. CSI engine 235 may perform operations based on network configuration taking into account potential conflicts with URLLC data transmissions, including performing channel measurements (e.g., for CSI-RS).

[0026] 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.

[0027] The memory 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, the LTE RAN 122, etc. Therefore, the transceiver 225 may operate on multiple different frequencies or channels (e.g., a continuous frequency group).

[0028] Figure 3An exemplary network base station (in this case, gNB 120A) is shown according to various exemplary embodiments. As described above with respect to UE 110, gNB 120A may represent a base station that provides service to UE 110. gNB 120A may represent any access node of a 5G NR network through which UEs 110, 112 may establish connections and manage network operations. Figure 3 The gNB 120A shown may also represent gNB 120B.

[0029] The gNB 120A may include a processor 305, a memory arrangement 310, an input / output (I / O) device 320, a transceiver 325, and other components 330. The other components 330 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, a port for electrically connecting the gNB 120A to other electronic devices, and the like.

[0030] The processor 305 may be configured to execute multiple engines of the gNB 120A. For example, the engines may include a CSI management engine 335 and a URLLC data management engine 340. The CSI management engine 335 may perform operations including configuring the UE to perform channel measurements in view of potential conflicts with URLLC data transmissions. The URLLC data management engine 340 may perform operations including configuring the UE for URLLC data transmissions.

[0031] The engines described above are each an application (e.g., a program) executed by the processor 305 for exemplary purposes only. The functionality associated with the engines may also be represented as separate, integrated components of the gNB 120A, or may be modular components coupled to the gNB 120A, such as integrated circuits with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. In addition, in some gNBs, the functionality described for the processor 305 is split between multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the gNB.

[0032] The memory 310 may be a hardware component configured to store data related to operations performed by the UE 110, 112. The I / O device 320 may be a hardware component or port that enables a user to interact with the gNB 120A. The transceiver 325 may be a hardware component configured to exchange data with the UE 110, 112 and any other UE in the system 100. The transceiver 325 may operate on a variety of different frequencies or channels (e.g., a contiguous group of frequencies).

[0033] Preemption involves prioritization of data traffic for specific applications that require fast and reliable data transmission, such as public safety applications. In 5G NR, a UE in an enhanced mobile broadband (eMBB) configuration may have eMBB services preempted by an ultra-reliable low latency communication (URLLC) service.

[0034] In the third generation partnership (3GPP) technical specification TS 38.212, DCI format 2_1 is defined for 5G NR. DCI format 2_1 can be used to inform the UE of physical resource blocks (PRBs) and OFDM symbols, where the UE can assume that no transmission is intended for the UE. The following information can be transmitted via DCI format 2_1 with a cyclic redundancy check (CRC) scrambled by INT-RNTI: preemption indication 1, preemption indication 2, ..., preemption indication N. The size of DCI format 2_1 can be configured by a high layer of up to 126 bits (according to clause 11.2 of [5, TS 38.213]). Each preemption indication is 14 bits.

[0035] The UE behavior when the UE receives DCI format 2_1 may be as follows. If the UE detects DCI format 2_1 from a serving cell of a set of configured serving cells, the UE may assume that there is no transmission to the UE in the PRBs and symbols indicated by DCI format 2_1 from a set of PRBs and a set of symbols from the last monitoring period. The indication of DCI format 2_1 does not apply to the reception of SS / PBCH blocks. In the example started above, when an eMBB UE (e.g., UE 110) receives DCI format 2_1, UE 110 will understand that there is no transmission to UE 110 in the indicated symbols. Therefore, UE 110 may not monitor these symbols because there will be no transmission to UE 110.

[0036] The CSI-RS may be configured for the UE to perform mobility measurements. The UE may monitor the downlink channel for CSI-RS transmissions from the network according to the resource location identified by the CSI-RS configuration. Upon receiving the CSI-RS transmission, the UE may generate channel quality information (CQI) for the serving cell and / or one or more neighboring cells, for example, for layer 3 (L3) mobility management. However, it is possible that the CSI-RS transmission may conflict with the OFDM symbols indicated by the preemption bit. If the UE 110 is not monitoring these symbols, the UE 110 will not receive and measure the CSI-RS for mobility and / or any other purpose.

[0037] According to some exemplary embodiments, the network configures URLLC data transmission and / or L3 CSI-RS for serving cell measurements of eMBBUEs so that conflicts between OFDM symbols in preemption indications and CSI-RS can be avoided and / or managed.

[0038] According to other exemplary embodiments, the network may schedule URLLC data for URLLC UEs on symbols where L3 CSI-RS measurements are configured for eMBB UEs. Several exemplary ways of handling this situation are provided below.

[0039] In some exemplary embodiments, in the case where L3 CSI-RS is configured, the network avoids indicating preemption of those symbols to the eMBB UE. In other words, although URLLC data and L3 CSI-RS may collide, the eMBB UE will not receive preemption indications for those symbols, and channel measurements are still performed despite the channel being otherwise used for URLLC data.

[0040] In other exemplary embodiments, the network configures zero power CSI-RS (ZP-CSI-RS) as L3 CSI-RS measurement for eMBB UEs regardless of the preemption configuration. ZP-CSI-RS masks or silences certain resource elements (REs) to make those REs unavailable for physical downlink scheduling channel (PDSCH) transmissions to allow interference measurements. ZP-CSI-RS does not mean that there is no transmission in the resource element. Instead, the resource element includes a non-zero power CSI-RS (NZP-CSI-RS) of another UE (e.g., UE 112 in the current example). In this exemplary embodiment, since ZP-CSI-RS is configured for L3 CSI-RS measurement, URLLC UEs and eMBB UEs will skip those CSI-RS symbols for data reception and use only these symbols for interference and mobility measurements.

[0041] In yet another exemplary embodiment, the network may apply scheduling restrictions on CSI-RS symbols for L3 measurements to all connected UEs (including URLLC UEs and eMBB UEs). For example, the network may not schedule CSI-RS symbols for L3 measurements for certain symbols. In contrast to the above exemplary embodiments in which the network does not schedule URLLC data transmissions and / or L3 CSI-RS to conflict, in these exemplary embodiments, there may be conflicting situations, but there may be certain symbols where the scheduling restrictions will eliminate the conflict by not scheduling CSI-RS symbols for L3 measurements in certain symbols. In these exemplary embodiments, URLLC and eMBB UEs will expect scheduling restrictions on CSI-RS symbols for L3 measurements.

[0042] Figure 4A method 400 for performing mobility measurements for a UE in an enhanced mobile broadband (eMBB) configuration is shown. In 405, the UE receives a first network configuration of a CSI-RS. In 410, the network schedules URLLC data for the URLLC UE on symbols where L3 CSI-RS measurements are configured. As discussed above, in this example, the URLLC data and the CSI-RS may collide.

[0043] In 415, the network determines a second configuration for the eMBB UE in view of the conflict between the URLLC data and the CSI-RS. As discussed above, in some exemplary embodiments, the network will not indicate any preemption of those symbols to the eMBB UE. Therefore, the second configuration will remain the same as the first configuration for the eMBB UE. In other exemplary embodiments, the second configuration includes a ZP-CSI-RS for the L3 CSI-RS, regardless of whether the UE receives a preemption indication. In yet another exemplary embodiment, the network applies the scheduling restrictions discussed above.

[0044] The above exemplary embodiments solve problems related to preemption of CSI-RS measurements relative to the serving cell. The following exemplary embodiments solve problems related to CSI-RS measurements of neighboring cells. According to the following exemplary embodiments, the network configures URLLC data transmission and / or L3CSI-RS for neighboring cell measurements of eMBB UEs so that conflicts between OFDM symbols in preemption indications and CSI-RS can be avoided and / or managed.

[0045] Figure 5 A first network configuration 500 for performing L3 CSI-RS neighbor cell measurements according to various exemplary embodiments is shown. In this exemplary embodiment, a first (serving) cell gNB 120A is in a scenario where an eMBB connection is established with a first UE 110 and a URLLC connection is established with a second UE 112. gNB 120B is a neighbor cell.

[0046] In signal 505, serving cell gNB 120A exchanges timing information with neighboring cell gNB 120B. In view of the timing information, gNB 120A determines whether the CSI-RS L3 measurement (signal 510) of eMBB UE 110 on the neighboring cell collides with the URLLC data symbol (signal 515) of URLLC UE 112 on the first cell gNB 120A.

[0047] If the URLLC data channel of the serving cell gNB 120A collides with the CSI-RS on symbol x of the neighboring cell gNB 120B, the serving cell gNB 120A configures ZP-CSI-RS on symbols x-1, x, and x+1 for the eMBB UE 110 to perform CSI-RS L3 neighboring cell measurements. The serving cell gNB 120A will avoid scheduling any PDSCH on those ZP-CSI-RS symbols x-1, x, and x+1. Although the serving cell gNB 120A and the neighboring cell gNB 120B can exchange timing information, there may still be cell phase synchronization misalignment between the cells. This is why the serving cell gNB 120A will configure symbols x-1, x, and x+1 with ZP-CSI-RS instead of just symbol x. However, it should be understood that other combinations of symbols may be configured as ZP-CSI-RS depending on the accuracy of the timing information and alignment.

[0048] The eMBB UE 110 will not decode any PDSCH on the ZP-CSI-RS symbols x-1, x and x+1 indicated by the serving cell gNB 120A, but will perform CSI-RS L3 measurements of the neighboring cell gNB 120B on those symbols.

[0049] Figure 6 A second network configuration 600 for performing L3 CSI-RS neighbor cell measurements according to various exemplary embodiments is shown. In this exemplary embodiment, a first (serving) cell gNB 120A is in a scenario where an eMBB connection is established with a first UE 110 and a URLLC connection is established with a second UE 112. gNB 120B is a neighbor cell.

[0050] In this exemplary embodiment, serving cell gNB 120A indicates a preemption indication (signal 605) on symbol x to eMBB UE 110. The preemption indication corresponds to an OFDM symbol scheduled to carry URLLC data (signal 610) on symbol x to URLLC 112. UE 110 will not decode any PDSCH on symbol x based on the preemption indication. If the CSI-RS (signal 615) for neighbor cell measurement happens to be transmitted on symbol x, then eMBB UE 110 will measure the CSI-RS from the second cell gNB 120B.

[0051] In other exemplary embodiments, the network may schedule conflicting URLLC data transmissions and / or special PDSCHs. For example, the special PDSCH may include remaining minimum system information (RYI) with system information updates for eMBB UEs. In this case, exemplary embodiments may be implemented so that conflicts between OFDM symbols in preemption indications and special PDSCHs may be avoided and / or managed.

[0052] According to some exemplary embodiments, the network avoids configuring preemption of symbols carrying special PDSCHs (e.g., RMSI PDSCH or another PDSCH carrying system information). The network will avoid scheduling URLLC data that will collide with those special PDSCHs on the same frequency / time domain resources.

[0053] In other exemplary embodiments, the network may schedule URLLC data for URLLC UEs on symbols carrying special PDSCH. In these scenarios, when the network configures preemption that conflicts with the special PDSCH, the UE ignores the preemption indication to decode the special PDSCH. For example, the eMBB UE will ignore the preemption to keep decoding the special PDSCH. In another example, the URLLC UE will ignore the URLLC data but decode the special PDSCH.

[0054] According to yet another exemplary embodiment, the network may configure conflicting URLLC data transmissions and / or URLLC DL measurements for the URLLC UE. The exemplary embodiment may be implemented so that conflicts between data channels and DL measurements may be avoided and / or managed.

[0055] In some exemplary embodiments, measurement restrictions may be applied to URLLC data symbols of a URLLC UE. The URLLC UE may prioritize decoding of URLLC data channels over mobility DL measurements of neighboring cells and / or serving cells. For example, the URLLC UE may prioritize decoding of URLLC data channels over radio link monitoring (RLM), beam failure detection (BFD), candidate beam detection (CBD), and layer 1 reference signal received power (L1 RSRP) measurements of the serving cell.

[0056] In other exemplary embodiments, timing information may be exchanged between the serving cell and the neighboring cell. Based on the timing information, the network may avoid configuring the URLLC UE to perform measurements on those URLLC data symbols that conflict with the URLLC data transmission.

[0057] In yet another exemplary embodiment, timing information may again be exchanged between the serving cell and the neighboring cell. Based on this timing information, the network may avoid scheduling URLLC data channels that conflict with URLLC DL measurements.

[0058] Example:

[0059] A first example includes a processor of a first base station, the first base station communicating with a first user equipment (UE) and a second UE and configured to perform operations including exchanging timing information with the second base station, determining whether a channel state information reference signal (CSI-RS) configured for the first UE for measuring CSI on the second base station conflicts with a data transmission of the second UE on the same symbol x, and configuring a zero power CSI-RS (ZP-CSI-RS) as the CSI-RS for CSI measurement of the first UE on the second base station.

[0060] The second example includes the processor of the first example, wherein the first UE is in an enhanced mobile broadband (eMBB) configuration with the first base station, and the second UE is in an ultra-reliable low latency communication (URLLC) configuration with the first base station.

[0061] The third example includes the processor of the second example, wherein the ZP-CSI-RS is configured on the symbol x, symbol x-1, and symbol x+1.

[0062] A fourth example includes the processor of the third example, wherein the operations further include configuring the first UE to not decode any physical downlink shared channel (PDSCH) on the symbols x-1, x, and x+1.

[0063] A fifth example includes a processor of a first base station, which communicates with a first user equipment (UE) and a second UE and is configured to perform operations including configuring the second UE for data transmission on symbol x, and transmitting a preemption indication to the first UE on symbol x, wherein the preemption indication configures the first UE to not decode a physical downlink shared channel (PDSCH) on symbol x, and when a channel state information reference signal (CSI-RS) is configured for the first UE to measure CSI from the second base station on symbol x, the first UE performs the CSI measurement on symbol x.

[0064] The sixth example includes the processor of the fifth example, wherein the first UE is in an enhanced mobile broadband (eMBB) configuration with the first base station, and the second UE is in an ultra-reliable low latency communication (URLLC) configuration with the first base station.

[0065] A seventh example includes a processor of a base station, which communicates with a first user equipment (UE) and a second UE and is configured to perform operations including determining a first configuration of the first UE for a special physical downlink shared channel (PDSCH) on a symbol, scheduling data transmission of the second UE on the symbol, wherein the special PDSCH is configured such that the special PDSCH and the data transmission conflict, and transmitting a preemption indication for the symbol to the first UE, wherein the first UE ignores the preemption indication and decodes the special PDSCH.

[0066] The eighth example includes the processor of the seventh example, wherein the first UE is in an enhanced mobile broadband (eMBB) configuration with the base station, and the second UE is in an ultra-reliable low latency communication (URLLC) configuration with the base station.

[0067] A ninth example includes the processor of the seventh example, wherein the special PDSCH is remaining minimum system information (RFIFO).

[0068] The tenth example includes a processor of a base station, which communicates with a first user equipment (UE) and a second UE in an ultra-reliable low latency communication (URLLC) configuration and is configured to perform operations including determining a configuration of the first UE for a special physical downlink shared channel (PDSCH) on a symbol, and scheduling data transmission of the second UE on the symbol, wherein the special PDSCH is configured such that the special PDSCH and the data transmission conflict, wherein the second UE ignores the data transmission and decodes the PDSCH.

[0069] An eleventh example includes a processor of a base station, wherein the base station communicates with a user equipment (UE) in an ultra-reliable low-latency communication (URLLC) configuration and is configured to perform operations including determining a configuration of the UE based on mobility downlink (DL) measurements of the base station or one or more neighboring base stations on a symbol, and scheduling data transmission of the UE on the symbol, wherein the special PDSCH is configured such that the special PDSCH and the data transmission conflict, wherein the UE decodes the data transmission in preference to the mobility DL measurements.

[0070] The twelfth example includes the processor of the eleventh example, wherein the mobility DL measurement includes one of radio link monitoring (RLM), beam failure detection (BFD), candidate beam detection (CBD) and layer 1 reference signal received power (L1 RSRP) measurement of the serving cell.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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. A processor of a base station, the base station communicating with a first user equipment UE and a second UE and configured to perform operations including: Determine a first configuration of the first UE for a channel state information reference signal CSI-RS on a symbol; Scheduling data transmission of the second UE on the symbol where the CSI-RS is configured, so that the CSI-RS and the data transmission collide on the symbol; as well as When the CSI-RS and the data transmission collide on the symbol, a second configuration of the first UE is determined.

2. The processor of claim 1, wherein the first UE is in an enhanced mobile broadband (eMBB) configuration with the base station, and the second UE is in an ultra-reliable low latency communication (URLLC) configuration with the base station. 3 . The processor of claim 2 , wherein the CSI-RS is used by the first UE to perform Layer 3 (L3) CSI-RS mobility measurements. 4 . The processor of claim 3 , wherein the base station does not indicate preemption to the first UE, and the second configuration is the first configuration. 5 . The processor of claim 3 , wherein the second configuration comprises a zero power CSI-RS (ZP-CSI-RS) as the layer 3 (L3) CSI-RS.

6. The processor of claim 3, wherein the operations further comprise: Scheduling restrictions are applied to the first UE on the symbols.

7. The processor of claim 6, wherein the scheduling restriction comprises not scheduling control or data transmission to the first UE on the symbol.

8. The processor of claim 7, wherein not scheduling data transmission comprises not scheduling physical downlink shared channel (PDSCH) transmission.

9. The processor of claim 6, wherein the operations further comprise: Scheduling restrictions are applied to the second UE on the symbols.

10. A base station, comprising: a transceiver configured to communicate with a first user equipment UE and a second UE; and a processor communicatively coupled to the transceiver and configured to perform operations including: Determine a first configuration of the first UE for a channel state information reference signal CSI-RS on a symbol; Scheduling data transmission of the second UE on the symbol where the CSI-RS is configured, so that the CSI-RS and the data transmission collide on the symbol; as well as When the CSI-RS and the data transmission collide on the symbol, a second configuration of the first UE is determined.

11. The base station of claim 10, wherein the first UE is in an enhanced mobile broadband (eMBB) configuration with the base station, and the second UE is in an ultra-reliable low latency communication (URLLC) configuration with the base station. 12 . The base station of claim 11 , wherein the CSI-RS is used by the first UE to perform Layer 3 (L3) CSI-RS mobility measurement. 13 . The base station of claim 12 , wherein the base station does not indicate preemption to the first UE, and the second configuration is the first configuration. 14 . The base station of claim 12 , wherein the second configuration includes a zero power CSI-RS (ZP-CSI-RS) as the layer 3 (L3) CSI-RS.

15. The base station of claim 12, wherein the operations further comprise: Scheduling restrictions are applied to the first UE on the symbols.

16. The base station of claim 15, wherein the scheduling restriction comprises not scheduling control or data transmission to the first UE on the symbol.

17. The base station of claim 16, wherein not scheduling data transmission comprises not scheduling physical downlink shared channel (PDSCH) transmission.

18. The base station of claim 15, wherein the operations further comprise: Scheduling restrictions are applied to the second UE on the symbols.

19. A processor of a first user equipment UE, the processor being configured to perform operations comprising: receiving, from a base station of a network, a first configuration of a channel state information reference signal (CSI-RS) on symbols, wherein the CSI-RS is used by the first UE to perform layer 3 (L3) CSI-RS mobility measurements, and wherein data transmission by a second UE is also scheduled on the symbols; and A scheduling restriction for the symbol is received from the base station.

20. The processor of claim 19, wherein the scheduling restriction comprises the UE not being scheduled for control or data transmission on the symbol.

21. The processor of claim 20, wherein the first UE is in an enhanced mobile broadband (eMBB) configuration with the base station, and the second UE is in an ultra-reliable low latency communication (URLLC) configuration with the base station.

Images