Multi-TRP base station for radar sensing

Abstract

The network node may schedule a first set of time slots for simultaneous sensing and sTRP communication with the UE. The network node may send a first indication to the UE that schedules the first set of slots for simultaneous sensing and sTRP communications. The network node may schedule a second set of time slots for mTRP communication with the UE. The network node may send a second indication to the UE that schedules the second set of slots for mTRP communications. The first set of time slots and the second set of time slots may include at least one same time slot. The network node may be associated with the first TRP and the second TRP.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to multiple transmit receive point (TRP) network nodes that can also perform radio detection and ranging (radar) sensing. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may receive a first indication from a network node of a first group of time slots scheduled for simultaneous sensing and single transmit receive point (TRP) (sTRP) communications. The apparatus may receive a second indication from the network node of a second group of time slots scheduled for multi-TRP (mTRP) communications. The first group of time slots and the second group of time slots may include at least one identical time slot. The network node may be associated with a first TRP and a second TRP.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a network node. The apparatus may schedule a first set of time slots for simultaneous sensing and sTRP communication with a UE. The apparatus may schedule a second set of time slots for mTRP communication with the UE. The first set of time slots and the second set of time slots may include at least one identical time slot. The network node may be associated with a first TRP and a second TRP.

[0007] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0009] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0010] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0011] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0012] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0014] Figure 4 Typical circuits in a telecommunication device that may perform radio frequency (RF) communication and RF sensing according to aspects of the present disclosure are illustrated.

[0015] Figure 5 is a diagram illustrating an mTRP base station including two TRPs or associated with two TRPs.

[0016] Fig. 6A , Figure 6B and Figure 6C is a diagram illustrating aspects of a technique for radar sensing using an mTRP base station according to one or more aspects.

[0017] Figure 7 is an example diagram illustrating one or more RX-TX switches according to one or more aspects.

[0018] Fig. 8A is an example diagram illustrating TCI state selection for multi-slot TDM communications scheduled across a boundary between sensing slots and non-sensing slots according to one or more aspects.

[0019] Figure 8B is an example diagram illustrating TCI state selection for multi-slot TDM communication scheduled across boundaries between sensing slots and non-sensing slots based on a half-and-half mode according to one or more aspects.

[0020] Fig. 9 is an example diagram illustrating a resolution of conflicts between dynamically scheduled mTRP communications and dynamically scheduled radar sensing according to one or more aspects.

[0021] Fig.10 is an example diagram illustrating potential sensing time slots configured by a base station according to one or more aspects.

[0022] Fig.11 is a flow chart of a wireless communication method.

[0023] Fig.12 is a flow chart of a wireless communication method.

[0024] Fig.13 is a flow chart of a wireless communication method.

[0025] Fig.14 is a flow chart of a wireless communication method.

[0026] Fig.15 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0027] Fig.16 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION

[0028] In some aspects, the use of integrated sensing and communication (ISAC) may enable a cellular communication network to provide unmanned aerial vehicle (UAV) sensing services. In particular, for cooperative UAVs, UAV sensing services may include providing surrounding airspace information (including flight dynamics of other UAVs, airspace environment, etc.) to the UAV operator. In addition, UAV sensing services for cooperative UAVs may include supervision of the UAV to ensure compliance with the UAV's pre-approved flight plan. For non-cooperative UAVs, UAV sensing services may include intruder UAV detection in restricted or restricted areas (e.g., airports).

[0029] When using the mTRP system for both sensing and cellular wireless communications, a continuous (long and uninterrupted) sensing duration comprising multiple time slots may be desirable for several reasons. For example, a continuous sensing duration may result in fewer interruptions associated with TX-RX or RX-TX switching.

[0030] In addition, in order to perform Doppler correlation estimation, phase continuity over time may be desired. For this reason, continuous sensing duration may also be desired. For example, it may take several milliseconds to tens of milliseconds to perform Doppler estimation on micro-Doppler features associated with the propellers of the UAV target in order to identify the UAV target. Continuous sensing duration that can ensure phase continuity over a sufficiently long period of time can help perform Doppler estimation.

[0031] In some configurations, for semi-statically configured radar sensing (e.g., for target UAV detection), optimization may be performed for a single TRP (sTRP)-mTRP timeslot pattern associated with periodic continuous sensing timeslots (opportunities), where sTRP communications may be performed in the same sensing timeslots. In some additional configurations, for dynamically (on-demand) triggered radar sensing (e.g., for UAV tracking after a UAV is detected), the behavior of the system may be defined in the case where the same timeslot has been scheduled for mTRP communications (sensing and mTRP communications may not be performed in the same timeslot).

[0032] In one or more aspects, a network node may schedule a first set of time slots for simultaneous sensing and sTRP communications with a UE. The network node may send a first indication to the UE of the first set of time slots scheduled for simultaneous sensing and sTRP communications. The network node may schedule a second set of time slots for mTRP communications with the UE. The network node may send a second indication to the UE of the second set of time slots scheduled for mTRP communications. The first set of time slots and the second set of time slots may include at least one identical time slot. The network node may be associated with a first TRP and a second TRP. Thus, an sTRP-mTRP time slot pattern associated with periodic continuous sensing time slots may be optimized. In addition, the behavior of the system may be defined in the event that there may be a conflict at one or more time slots between scheduled mTRP communications and scheduled simultaneous sensing and sTRP communications.

[0033] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0034] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0035] As an example, an element, or any part of an element, or any combination of elements, may be implemented as a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, or any combination thereof.

[0036] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. For example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0037] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The various techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0038] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment such as a base station (BS), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0039] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0040] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0041] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 140 simultaneously.

[0042] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals on a wired transmission medium or send signals to one or more of the other units. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals on a wireless transmission medium or send signals to one or more of the other units, or both.

[0043] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0044] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as that defined by 3GPP. In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0045] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0046] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0047] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0048] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0049] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmission diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0050] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0051] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although distinct from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0053] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0054] In view of the above, unless otherwise specifically stated, if the term "below 6 GHz" or the like is used in this document, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" or the like is used in this document, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0055] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction for the base station 102 may be the same or may be different. The transmit direction and receive direction of the UE 104 may be the same or may be different.

[0056] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0057] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement results and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0058] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite broadcasts, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, user stations, mobile units, user units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile user stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or some other suitable terms. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0059] Reference again Figure 1 , in some aspects, the UE 104 may include an mTRP component 198, which may be configured to receive a first indication from a network node of a first group of time slots scheduled for simultaneous sensing and sTRP communication. The mTRP component 198 may be configured to receive a second indication from the network node of a second group of time slots scheduled for mTRP communication. The first group of time slots and the second group of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP. In some aspects, the base station 102 may include an mTRP component 199, which may be configured to schedule a first group of time slots for simultaneous sensing and sTRP communication with the UE. The mTRP component 199 may be configured to schedule a second group of time slots for mTRP communication with the UE. The first group of time slots and the second group of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0060] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured to have any of the various available slot formats 0 to 61. Slot formats 0 and 1 are DL and UL, respectively. Other slot formats 2 to 61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0061] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For conventional CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0062]

[0063] For normal CP (14 symbols / slot), different parameter sets μ 0 to 4 allow 1, 2, 4, 8 and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing can be equal to 2μ*15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

[0064] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0065] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0066] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0067] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0068] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0069] Figure 3 370 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0070] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) decoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived based on reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0071] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0072] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0073] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0074] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0075] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0076] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0077] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The mTRP component 198 combines various aspects.

[0078] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The mTRP component 199 combines various aspects.

[0079] Integrated sensing and communication (ISAC) is a term that describes the convergence of RF communications and RF sensing, such as radio detection and ranging (radar). The trend toward digitalization in commercial radars is converging the architecture of their RF front ends (i.e., all components in the receiver that process the signal at the raw incoming radio frequency and then convert it to a lower intermediate frequency) and their waveforms to become increasingly similar to those used for communications. For example, waveforms used for vehicular radars are evolving from analog frequency-modulated carriers (FMCW) to orthogonal frequency-division multiplexing (OFDM) symbols, such as those used in telecommunications. Furthermore, carrier frequencies used for telecommunications are gradually shifting to higher frequency bands (24 GHz, 60 GHz, 77 GHz, and potentially even higher) that include frequencies used for radar.

[0080] Figure 4 4 illustrates a typical circuit in a device 400 that can perform RF communication and RF sensing according to various aspects of the present disclosure. Figure 4 In FIG. 4 , device 400 includes transmitter circuit 402 and receiver circuit 404. Data source 406 provides communication data and sensed data to transmitter circuit 402. Receiver circuit 404 provides received data to radar processor circuit 408 and data demodulation circuit 410. Device 400 operates within environment 412 (which may also be referred to as a channel). Data source 406 also provides sensed data to radar processor circuit 408. Figure 4 As can be seen in FIG. 1 , using OFDM symbols for RF sensing provides the following benefit: the same RF front end can be used for both RF communication and RF sensing, ie both functions can use shared components.

[0081] Thus, ISACs may provide benefits such as cost effectiveness (e.g., there may be a joint RF hardware platform for communications and radar) and spectrum effectiveness (e.g., always-on availability of spectrum for both communications and radar functions). Another benefit is that RF sensing is an additional motivation for the market introduction of vehicle-to-everything (V2X) communications. Use cases for ISACs may include macro sensing use cases (e.g., weather monitoring, autonomous driving, dynamic mapping, low-altitude airspace management (UAV (UAV) sensing), intruder detection, etc.) as well as micro sensing use cases (e.g., gesture recognition, vital signs detection, high-resolution imaging in the terahertz (THz) band, etc.). Use cases for ISACs may also include sensing-assisted communications, such as beam management.

[0082] In some aspects, after the FFT, the general processing of the operation of the OFDM radar at the receiver side includes the following: (1) removing the modulation symbols (data content), which eliminates the resource element (RE) modulation symbols by dividing the transmitted value of each resource element (RE) modulation symbol at the associated RE; (2) using the time domain (symbol-by-symbol) FFT for target velocity (Doppler) estimation; and (3) using the frequency domain (subcarrier-by-subcarrier) IFFT for target range estimation. Operations (2) and (3) are similar to the 2D-FFT processing of the FMCW radar, and the performance of the OFDM radar is similar to that of the FMCW radar.

[0083] It should be noted that OFDM signals can be used for radar purposes if the modulation symbols (data content) of the transmitted OFDM signal are known at the receiver. For a monostatic radar where the transmitter and receiver are the same node, the receiver naturally knows the exact transmitted signal. For a bistatic radar where the transmitter and receiver are different nodes, the receiver may still know the exact transmitted signal, for example, when a known or predefined transmitted signal sequence is used, or if the data is correctly decoded, such as by a received communication signal with a cyclic redundancy check (CRC). It should also be noted that, unlike a phase modulated carrier (PMCW) based radar where the autocorrelation property of the sequence may be necessary, for an OFDM radar, a specific sequence is not mandatory (except for possible considerations of the peak-to-average power ratio (PAPR)). For example, an OFDM signal based on a Zadoff-Chu sequence has a constant amplitude and will therefore have a higher signal-to-noise ratio (SNR) at the receiver side.

[0084] Here are some considerations for NR-based ISAC: For range resolution, wideband signals can be considered; for stable availability during the observation time, broadcast signals can be considered instead of demand-triggered data channels. Therefore, the following signals or channels are considered together as radar signals for sensing:

[0085] For the downlink: SSB, which is wideband from the system perspective; CSI-RS; and Downlink Positioning Reference Signal (DL-PRS).

[0086] For uplink: SRS; and Sidelink Positioning Reference Signal (SL-PRS).

[0087] The following table lists various reference signals and their potential uses for NR-based ISAC.

[0088]

[0089] A multiple-input multiple-output (MIMO) antenna includes many antenna elements, each of which can operate as a Tx antenna element or an Rx antenna element.

[0090] In some aspects, the use of ISACs may enable a cellular communication network to provide UAV sensing services. In particular, for cooperative UAVs, UAV sensing services may include providing surrounding airspace information (including flight dynamics of other UAVs, airspace environment, etc.) to the UAV operator. In addition, UAV sensing services for cooperative UAVs may include supervision of the UAV to ensure compliance with the UAV's pre-approved flight plan. For non-cooperative UAVs, UAV sensing services may include intruder UAV detection in restricted or restricted areas (e.g., airports).

[0091] Providing UAV sensing services using cellular communication networks (e.g., 4G, 5G, 6G, etc. cellular networks) can bring multiple benefits. For example, because the network nodes are already installed at existing physical sites, the deployment costs associated with UAV sensing services can be reduced. In addition, the shared RF / baseband hardware shared between the cellular communication function and the UAV sensing service can help save hardware costs. In addition, the cellular frequency band can be reused for radar sensing, which can lead to higher spectrum efficiency. With more intermediate frequency bands between 3GHz and 24Hz expected to be allocated to cellular wireless communications in the future (existing spectrum for commercial UAV detection radars may include X-band (8GHz-12GHz) or Ku-band (12GHz-18GHz)), it may become more likely that the cellular frequency band will be reused for radar sensing. In addition, for wide-area airspace management with mobile targets (e.g., UAVs in operation), the networking of cellular wireless communication systems can be naturally suitable for collaborative sensing and target tracking.

[0092] Figure 55 is a diagram illustrating an mTRP base station including or associated with two TRPs. Hereinafter, a TRP may also be referred to as a panel or an antenna panel. The base station 102, and in particular the RU of the base station 102, may be associated with a first TRP 502 (which may also be referred to as TRP#0) and a second TRP 504 (which may also be referred to as TRP#1). In one or more configurations, each of the first TRP 502 or the second TRP 504 may have an array of antenna element pairs 506. In some configurations, the first TRP 502 and the second TRP 504 may be spatially separated by a distance.

[0093] In some configurations, the base station 102 may use two spatially separated TRPs to perform full-duplex communication, wherein one of the TRPs may serve as a TX TRP and the other of the TRPs may serve as an RX TRP at the same time. In some configurations, the base station 102 may use two TRPs based on a time pattern. For example, the base station 102 may alternately use a first TRP 502 and a second TRP 504 in a series of time slots for communication (uplink (RX) or downlink (TX)) (e.g., the base station 102 may use the first TRP 502 in a first time slot, the second TRP 504 in a second time slot immediately following the first time slot, the first TRP 502 in a third time slot immediately following the second time slot, the second TRP 504 in a fourth time slot immediately following the third time slot, etc.).

[0094] In some configurations where the RU of base station 102 includes an ISAC component, base station 102 may use these two TRPs for both wireless communication and radar sensing, as will be described in further detail below.

[0095] Fig. 6A , Figure 6B and Figure 6C are diagrams 600A, 600B, and 600C illustrating aspects of techniques for radar sensing using mTRP base stations in accordance with one or more aspects. For mTRP base stations, spatially distributed TRPs (antenna arrays) may be used for bistatic or multistatic radar operations. Fig. 6A , Figure 6B and Figure 6CBistatic radar sensing is illustrated, where two TRPs 602 and TRP 604 can perform radio operations as a TX node and an RX node, respectively. In one or more configurations, when radar sensing is not performed, both TRP 602 and TRP 604 can operate as TRPs in a conventional mTRP system (i.e., a system in which multiple network-side remote radio heads (RRHs) (within a physical cell or from different cells) can be used for downlink and uplink transmissions with a UE), where the two TRPs can be used for cellular wireless communication (downlink or uplink).

[0096] In one or more configurations, when radar sensing is being performed, at most only one of the two TRPs 602 and TRP 604 may be used for communication, that is, in some configurations, when radar sensing is being performed, the system may operate in an sTRP communication mode (i.e., the UE may communicate with a single network-side RRH), or alternatively, in some other configurations, when radar sensing is being performed using two TRPs 602 and TRP 604, the system may not perform wireless communication functionality at all.

[0097] exist Fig. 6A In the example configuration shown, while the system is performing radar sensing (e.g., to detect an object 608, such as a UAV), there may be no cellular wireless communication with the UE 606. In other words, sensing may simply be considered an interruption to wireless communication. Figure 6B and Figure 6C The example configuration illustrated in FIG. 1 involves performing simultaneous radar sensing and sTRP wireless communication. In particular, in Figure 6B In the embodiment, the first TRP 602 can simultaneously send downlink communications to the UE 606 based on the multiplexing technique when operating as a TX node for radar sensing. Figure 6C In the embodiment, the second TRP 604 can simultaneously receive uplink communications from the UE 606 based on multiplexing technology when operating as an RX node for radar sensing. Figure 6B and Figure 6C The example configuration illustrated in FIG. 1 may be the focus of various aspects of the present disclosure that will be described in detail below.

[0098] In one or more configurations, during a sensing opportunity or time slot, Figure 6B The operation illustrated in (i.e., sTRP DL) and Figure 6CThe operations illustrated in (i.e., sTRP UL) may be performed alternately based on a time pattern (e.g., using time division multiplexing (TDM)). In one or more configurations, within a sensing timeslot, techniques for multiplexing radar sensing with sTRP communications may include frequency division multiplexing (FDM) and space division multiplexing (SDM) (e.g., upward sensing of a UAV target and simultaneous communication with a ground UE).

[0099] When using the mTRP system for both sensing and cellular wireless communications, a continuous (long and uninterrupted) sensing duration comprising multiple time slots may be desirable for several reasons. For example, a continuous sensing duration may result in fewer interruptions associated with TX-RX or RX-TX switching.

[0100] Figure 7 700 is an example diagram illustrating one or more RX-TX switches according to one or more aspects. Figure 7 As shown in FIG, immediately before a first boundary 702 between a sensing time slot and a non-sensing time slot, TRP#1 operating as an RX node for radar sensing may perform an RX-TX switch 704. Similarly, immediately before a second boundary 706 between a non-sensing time slot and a sensing time slot, TRP#0 operating as a TX node for radar sensing may perform an RX-TX switch 708. Furthermore, immediately before a third boundary (e.g., a boundary at the RX-TX switch 708) between a sensing time slot and a non-sensing time slot, TRP#0 may perform another RX-TX switch 710.

[0101] In addition, in order to perform Doppler correlation estimation, phase continuity over time may be desired. For this reason, continuous sensing duration may also be desired. For example, it may take several milliseconds to tens of milliseconds to perform Doppler estimation on micro-Doppler features associated with the propellers of the UAV target in order to identify the UAV target. Continuous sensing duration that can ensure phase continuity over a sufficiently long period of time can help perform Doppler estimation.

[0102] In some configurations, for semi-statically configured radar sensing (e.g., for target UAV detection), an optimization may be performed on a sTRP-mTRP timeslot pattern associated with periodic continuous sensing timeslots (opportunities), where sTRP communications may be performed in the same sensing timeslots. In some additional configurations, for dynamically (on-demand) triggered radar sensing (e.g., for UAV tracking after a UAV is detected), the behavior of the system may be defined when the same timeslot has been scheduled for mTRP communications (sensing and mTRP communications may not be performed in the same timeslot). In one or more configurations, mTRP communications may also be dynamically scheduled (e.g., scheduled based on a DCI message or MAC-Control Element (CE) (MAC-CE)) or semi-statically configured (e.g., configured based on an RRC message).

[0103] In some aspects, radar sensing may be configured semi-statically, while mTRP communications may be dynamically scheduled. In one or more configurations, for dynamically scheduled mTRP communications, the base station may avoid scheduling mTRP communications (e.g., PDSCH, PUSCH, or PUCCH communications) in sensing timeslots. However, for multi-slot TDM mTRP transmissions (i.e., repeated transmissions associated with different TRPs across multiple timeslots), avoiding scheduling mTRP communications in sensing timeslots may limit scheduling flexibility because each multi-slot mTRP transmission may be limited in non-sensing timeslots.

[0104] In one or more configurations, for multi-slot TDM communications (e.g., PDSCH, PUSCH, or PUCCH communications) associated with two TRPs, where each TRP is associated with a respective transmit configuration indicator (TCI) state (two TCI states in total), the repetition may be extended into the sensing slots. However, within the sensing slots, only one TCI (i.e., one TRP) may be used instead of two TCI states. In particular, in one configuration, the base station may explicitly select the TCI state used in the sensing slot from a set of pre-configured TCI states for the sensing slots. In another configuration, the TCI state used in the sensing slot may be implicitly determined (i.e., without explicit communication) from two TCI states based on a pre-configuration (e.g., the first TCI state may always be used for sTRP communications in the sensing slots). In addition, in non-sensing slots, the TDM communication may be an mTRP communication that may utilize two TRPs.

[0105] In one or more configurations, in order to more balanced use of the two TRPs during repetition, the TCI state for each time slot can be selected based on a half-and-half pattern across the multi-slot TDM communication. In particular, when the multi-slot TDM communication is scheduled across the boundary between the sensing time slot and the non-sensing time slot, selecting the TCI state for each time slot based on a half-and-half pattern across the entire multi-slot TDM communication can help maintain a balanced use of the two TRPs.

[0106] Fig. 8A 800 is an example diagram illustrating TCI state selection for multi-slot TDM communication scheduled across the boundary between sensing slots and non-sensing slots according to one or more aspects. The example multi-slot TDM communication may occupy a total of 8 slots. Diagram 802 illustrates TCI state selection based on a cyclic mapping mode rather than a half-and-half mode. Because only one TCI state can be used in a sensing slot, the cyclic mapping mode cannot be used in the sensing slot. Instead, within the sensing slot, the first TCI state is used for all four sensing slots that also contain wireless communication. In addition, within the non-sensing slot, the cyclic mapping mode can be used: for four non-sensing slots containing mTRP wireless communication, the TCI state can be selected based on the cyclic mapping mode: first TCI state (TRP#0), second TCI state (TRP#1), first TCI state (TRP#0), second TCI state (TRP#1), first TCI state (TRP#0), second TCI state (TRP#1), first TCI state (TRP#0), second TCI state (TRP#1), first TCI state (TRP#0), second TCI state (TRP#1), etc. As shown in diagram 802, over eight time slots associated with multi-slot TDM communications across the boundary between sensing time slots and non-sensing time slots, TRP #0 may be used in 6 time slots, while TRP #1 may be used in only 2 time slots. In other words, the use of the two TRPs may be unbalanced.

[0107] In addition, diagram 804 illustrates TCI state selection based on a sequential mapping mode rather than a half-and-half mode. Similar to the scenario of diagram 802, since only one TCI state can be used in a sensing slot, a cyclic mapping mode cannot be used in a sensing slot. Instead, within a sensing slot, the first TCI state is used for all four sensing slots that also contain wireless communication. In addition, within a non-sensing slot, a sequential mapping mode can be used: for four non-sensing slots containing mTRP wireless communication, a TCI state can be selected based on a sequential mapping mode: first TCI state (TRP#0), first TCI state (TRP#0), second TCI state (TRP#1), second TCI state (TRP#1), first TCI state (TRP#0), first TCI state (TRP#0), second TCI state (TRP#1), second TCI state (TRP#1), etc. As shown in diagram 804, over eight time slots associated with multi-slot TDM communications across the boundary between sensing time slots and non-sensing time slots, TRP #0 may be used in 6 time slots, while TRP #1 may be used in only 2 time slots. In other words, the use of the two TRPs may be unbalanced.

[0108] In contrast, diagram 806 illustrates TCI state selection based on a half-and-half mode. Within a sensing timeslot, a first TCI state is used for all four sensing timeslots that also include wireless communication. Then, the half-and-half mode can take into account all timeslots of multi-slot TDM communication. Because the first TCI state has been used for four sensing timeslots, the second TCI state can be used for four non-sensing timeslots for non-sensing timeslots. Therefore, as shown in diagram 806, on eight timeslots associated with multi-slot TDM communication across the boundary between sensing timeslots and non-sensing timeslots, TRP#0 can be used in 4 timeslots, and TRP#1 can be used in 4 timeslots. In other words, when using the half-and-half mode, the use of the two TRPs can be balanced.

[0109] Figure 8B 808 is an example diagram illustrating TCI state selection for multi-slot TDM communication scheduled across the boundary between sensing slots and non-sensing slots based on a half-and-half mode according to one or more aspects. In diagram 808, a first TCI state may be used in 4 slots including 3 sensing slots and 1 non-sensing slot. In addition, a second TCI state may also be used in 4 slots consisting entirely of non-sensing slots. Therefore, when using the half-and-half mode, the use of the two TRPs may be balanced.

[0110] In addition, in diagram 810, 5 time slots of an 8-time slot TDM communication may be located within a sensing time slot, while the 3 remaining time slots may be located within a non-sensing time slot. Based on a full half-and-half mode, two TCI states may each be used for 4 time slots. However, because only one TCI state may be used in a sensing time slot, a first TCI state may be used for 5 sensing time slots, while a second TCI state may be used for the remaining 3 time slots in a non-sensing time slot. In other words, a sensing time slot configuration may override a TCI state selection that would otherwise be used based on a full half-and-half mode at time slot 812: based on a full half-and-half mode, a second TCI state may be used for time slot 812; however, a sensing time slot configuration may override a TCI state selection that would otherwise be used, and may cause the first TCI state to be used for time slot 812 instead.

[0111] In some aspects, radar sensing may be semi-statically configured and mTRP communications may also be semi-statically scheduled. For periodic or semi-persistent (SPS) communications, conflicts at one or more time slots between scheduled or configured mTRP communications and scheduled or configured sensing (sTRP communications) may be resolved in various ways.

[0112] In one or more configurations, the base station may avoid configuring mTRP communications at sensing time slots. In addition, the UE may not expect conflicts between scheduled or configured mTRP communications and scheduled or configured sensing (sTRP communications).

[0113] In one or more configurations, the base station may configure sensing communications and periodic or SPS mTRP communications separately. When a conflict between scheduled or configured mTRP communications and scheduled or configured sensing (sTRP communications) occurs at one or more time slots, the scheduled or configured sensing (sTRP communications) may be prioritized and the scheduled or configured mTRP communications may be overridden. Thus, the UE may recognize that the time slots where the conflict exists may actually be sensing time slots.

[0114] In one configuration, the base station may explicitly select the TCI state used in the sensing slot from a set of pre-configured TCI states for the sensing slot. In another configuration, the TCI state used in the sensing slot may be implicitly determined (i.e., without explicit communication) from two TCI states based on pre-configuration (e.g., the first TCI state may always be used for sTRP communication in the sensing slot).

[0115] In one or more configurations, the configured periodic or SPS mTRP communications may include one or more of: PDCCH monitoring (e.g., two PDCCH candidates that may be linked as recurring, where each of the two PDCCH candidates may be from a corresponding one of the two TRPs and may be associated with a corresponding one of the two corresponding TCI states), one or more periodic or SPS PUSCHs, or one or more periodic or SPSPUCCHs.

[0116] In one or more configurations, for PDCCH monitoring in a sensing timeslot, CORESETs associated with TCI states not used for or not relevant to the sensing timeslot may be deactivated (deactivated CORESETs may not be monitored by the UE).

[0117] In some aspects, radar sensing may be dynamically configured, and mTRP communications may also be dynamically scheduled. In one or more configurations, when a conflict between dynamically scheduled or configured TDM mTRP communications and dynamically scheduled or configured sensing (sTRP communications) occurs at one or more time slots, the dynamically scheduled or configured sensing (sTRP communications) may be prioritized, and the dynamically scheduled or configured TDM mTRP communications may be overridden. Thus, the UE may recognize that the time slots where the conflict exists may actually be sensing time slots.

[0118] Fig. 9 is an example diagram 900 illustrating a solution to a conflict between dynamically scheduled mTRP communications and dynamically scheduled radar sensing according to one or more aspects. In particular, diagram 910 illustrates a solution to a conflict between dynamically scheduled SDM mTRP communications and dynamically scheduled radar sensing. In one or more configurations, when a conflict between dynamically scheduled or configured SDMed mTRP communications and dynamically scheduled or configured sensing (sTRP communications) occurs at one or more time slots, the dynamically scheduled or configured sensing (sTRP communications) may be prioritized, and the dynamically scheduled or configured SDMmTRP communications may be overridden. Thus, the UE may recognize that the time slot where the conflict exists may actually be a sensing time slot. In particular, at the sensing time slot, the UE may assume that the transmit power associated with the DM-RS port and data layer associated with the unused TCI state is 0.

[0119] Diagram 950 illustrates a resolution of a conflict between dynamically scheduled FDM mTRP communications and dynamically scheduled radar sensing. In one or more configurations, when a conflict between dynamically scheduled or configured FDMmTRP communications and dynamically scheduled or configured sensing (sTRP communications) occurs at one or more time slots, the dynamically scheduled or configured sensing (sTRP communications) may be prioritized and the dynamically scheduled or configured FDMed mTRP communications may be overridden. Thus, the UE may recognize that the time slot in which the conflict exists may actually be a sensing time slot. In particular, in one configuration, at a sensing time slot, sTRP communications may use all RBs allocated to (e.g., UE) (e.g., RBs associated with both TRP#0 and TRP#1 in FDM mTRP communications). In one configuration, at a sensing time slot, sTRP communications may use half of all RBs allocated to (e.g., UE) (e.g., RBs associated only with TRP#1 in FDM mTRP communications).

[0120] In one or more configurations, the processing timeline may be met between the dynamic sensing indication or configuration and any PDSCH transmission. Otherwise, the UE may still assume that the PDSCH is transmitted based on the scheduled mTRP and therefore errors may occur in the reception of the PDSCH.

[0121] In some aspects, radar sensing may be dynamically configured, while mTRP communications may be semi-statically scheduled. Semi-statically scheduled mTRP communications may include one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH. In one or more configurations, when a conflict between mTRP communications that may include PDCCH monitoring and dynamically scheduled or configured sensing (sTRP communications) occurs at one or more time slots, dynamically scheduled or configured sensing (sTRP communications) may be prioritized, and semi-statically scheduled PDCCH monitoring may be overridden.

[0122] Fig.10 1000 is an example diagram illustrating potential sensing time slots configured by a base station according to one or more aspects. In one or more configurations, the base station may pre-configure some time slots as potential sensing time slots. Fig.10 As shown in , the scheduled time slots may include one or more sensing time slots, one or more non-sensing time slots, and one or more potential sensing time slots.

[0123] In one configuration, if the semi-statically configured mTRP transmission at a potential sensing slot includes PDCCH monitoring, the UE may still monitor the link pairs of repeated PDCCH candidates in the same manner as the UE may monitor the link pairs of PDCCH candidates in a non-sensing slot. However, the UE may also monitor one of the PDCCH candidates in the candidate link pair (e.g., a PDCCH candidate associated with TRP#0 in the (potential) sensing slot) as a separate PDCCH candidate. The configuration may be based on a probability of triggering dynamic sensing, which may be estimated, for example, by a base station. In particular, the probability of triggering dynamic sensing may be based on the UAV flight plan, the UAV current location, or whether an intruding UAV is detected nearby.

[0124] In a different configuration, an individual PDCCH candidate or a pair of candidate links may be configured as a preferred PDCCH candidate that may take precedence over another.

[0125] In one or more configurations, for mTRP periodicity or SPS PUSCH or PUCCH in potential sensing timeslots, the base station may send periodicity or SPS PUSCH or PUCCH with two TCI states (e.g., treating potential sensing timeslots as similar to non-sensing timeslots) or with only one TCI state (e.g., treating potential sensing timeslots as similar to sensing timeslots). The configuration may be based on the probability of triggering dynamic sensing, which may be estimated, for example, by the base station. In particular, the probability of triggering dynamic sensing may be based on the UAV flight plan, the current location of the UAV, or whether an intruding UAV is detected nearby. For example, if the probability of triggering dynamic sensing is estimated to be high, the potential sensing timeslot may be treated as similar to a sensing timeslot. Conversely, if the probability of triggering dynamic sensing is estimated to be low, the potential sensing timeslot may be treated as similar to a non-sensing timeslot.

[0126] Fig.11 1100 is a flow chart of a wireless communication method. A network node 1104 may be associated with a first TRP 1104a and a second TRP 1104b. At 1106, the network node 1104 may schedule a first set of time slots for simultaneous sensing and sTRP communication with the UE 1102 (i.e., sensing and sTRP communication at the same time, not TDM).

[0127] At 1108, the network node 1104 may send a first indication to the UE 1102 of a first set of time slots scheduled for simultaneous sensing and sTRP communications, and the UE 1102 may receive the first indication from the network node.

[0128] At 1110, the network node 1104 may schedule a second set of time slots for mTRP communications with the UE 1102. The first set of time slots and the second set of time slots may include at least one identical time slot.

[0129] At 1112 , the network node 1104 may send a second indication to the UE 1102 of a second set of time slots scheduled for mTRP communication, and the UE 1102 may receive the second indication from the network node 1104 .

[0130] In one configuration, the first set of time slots may be semi-statically scheduled. The second set of time slots may be dynamically scheduled. The mTRP communication may be TDM. The sTRP communication with the UE may be associated with a single TRP between the first TRP 1104a and the second TRP 1104b.

[0131] In one configuration, the first TRP 1104a and the second TRP 1104b may be associated with an equal number of time slots across the first set of time slots and the second set of time slots with respect to sTRP communications or mTRP communications.

[0132] In one configuration, the first set of time slots may be semi-statically scheduled. The second set of time slots may be semi-statically scheduled. At least one identical time slot may be omitted from the second set of time slots. For example, at least one identical time slot may be considered to be exactly a time slot in the first set of time slots and may be identified as a time slot for simultaneous sensing and sTRP communication.

[0133] In one configuration, the first set of time slots may be associated with a pre-configured TCI state.

[0134] In one configuration, mTRP communication may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPSPUCCH.

[0135] In one configuration, the first set of time slots may be dynamically scheduled. The second set of time slots may be dynamically scheduled. At least one identical time slot may be omitted from the second set of time slots.

[0136] In one configuration, the mTRP communication may be SDM. The mTRP communication may be associated with at least one PDSCH.

[0137] In one configuration, the mTRP communication may be FDM. The mTRP communication may be associated with at least one PDSCH.

[0138] In one configuration, sTRP communications may be associated with all allocated RBs used to communicate with the UE.

[0139] In one configuration, sTRP communications may be associated with half of all allocated RBs used to communicate with the UE.

[0140] In one configuration, the first set of time slots may be dynamically scheduled. The second set of time slots may be semi-statically scheduled. mTRP communications may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH.

[0141] Fig.12 1200 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104 / 350 / 1102; device 1504). At 1202, the UE may receive a first indication from a network node of a first group of time slots scheduled for simultaneous sensing and sTRP communication. For example, 1202 may be performed by Fig.15 Component 198 in the implementation. Fig.11 , at 1108, UE 1102 may receive a first indication from network node 1104 of a first set of time slots scheduled for simultaneous sensing and sTRP communications.

[0142] At 1204, the UE may receive a second indication from the network node of a second group of time slots scheduled for mTRP communication. The first group of time slots and the second group of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP. For example, 1204 may be Fig.15 Component 198 in the implementation. Fig.11 At 1112, UE 1102 may receive a second indication from network node 1104 of a second set of time slots scheduled for mTRP communications.

[0143] In one configuration, reference Fig.11 , the first set of time slots may be semi-statically scheduled. The second set of time slots may be dynamically scheduled. mTRP communications may be TDM. sTRP communications with the UE may be associated with a single TRP between the first TRP 1104a and the second TRP 1104b.

[0144] In one configuration, reference Fig.11 , the first TRP 1104a and the second TRP 1104b may be associated with an equal number of time slots across the first group of time slots and the second group of time slots with respect to sTRP communication or mTRP communication.

[0145] In one configuration, the first set of time slots may be semi-statically scheduled. The second set of time slots may be semi-statically scheduled. At least one identical time slot may be omitted from the second set of time slots.

[0146] In one configuration, the first set of time slots may be associated with a pre-configured TCI state.

[0147] In one configuration, mTRP communication may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPSPUCCH.

[0148] In one configuration, the first set of time slots may be dynamically scheduled. The second set of time slots may be dynamically scheduled. At least one identical time slot may be omitted from the second set of time slots.

[0149] In one configuration, the mTRP communication may be SDM. The mTRP communication may be associated with at least one PDSCH.

[0150] In one configuration, the mTRP communication may be FDM. The mTRP communication may be associated with at least one PDSCH.

[0151] In one configuration, sTRP communications may be associated with all allocated RBs used to communicate with the UE.

[0152] In one configuration, sTRP communications may be associated with half of all allocated RBs used to communicate with the UE.

[0153] In one configuration, the first set of time slots may be dynamically scheduled. The second set of time slots may be semi-statically scheduled. mTRP communications may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH.

[0154] Fig.13 1300 is a flow chart of a wireless communication method. The method may be performed by a base station / network node (e.g., base station 102 / 310 / 1104; network entity 1502). At 1302, the network node may schedule a first set of time slots for simultaneous sensing and sTRP communication with a UE. For example, 1302 may be performed by Fig.16 Component 199 in the reference Fig.11 , at 1106, the network node 1104 may schedule a first set of time slots for simultaneous sensing and sTRP communication with the UE 1102.

[0155] At 1304, the network node may schedule a second set of time slots for mTRP communication with the UE. The first set of time slots and the second set of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP. For example, 1304 may be performed by Fig.16 Component 199 in the reference Fig.11 , at 1110, the network node 1104 may schedule a second set of time slots for mTRP communication with the UE 1102.

[0156] Fig.141400 is a flow chart of a wireless communication method. The method may be performed by a base station / network node (e.g., base station 102 / 310 / 1104; network entity 1502). At 1402, the network node may schedule a first set of time slots for simultaneous sensing and sTRP communication with a UE. For example, 1402 may be performed by Fig.16 Component 199 in the reference Fig.11 , at 1106, the network node 1104 may schedule a first set of time slots for simultaneous sensing and sTRP communication with the UE 1102.

[0157] At 1404, the network node may schedule a second set of time slots for mTRP communication with the UE. The first set of time slots and the second set of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP. For example, 1404 may be performed by Fig.16 Component 199 in the reference Fig.11 , at 1110, the network node 1104 may schedule a second set of time slots for mTRP communication with the UE 1102.

[0158] In one configuration, reference Fig.11 , the first set of time slots may be semi-statically scheduled. The second set of time slots may be dynamically scheduled. mTRP communications may be TDM. sTRP communications with the UE may be associated with a single TRP between the first TRP 1104a and the second TRP 1104b.

[0159] In one configuration, reference Fig.11 , the first TRP 1104a and the second TRP 1104b may be associated with an equal number of time slots across the first group of time slots and the second group of time slots with respect to sTRP communication or mTRP communication.

[0160] In one configuration, the first set of time slots may be semi-statically scheduled. The second set of time slots may be semi-statically scheduled. At least one identical time slot may be omitted from the second set of time slots.

[0161] In one configuration, the first set of time slots may be associated with a pre-configured TCI state.

[0162] In one configuration, mTRP communication may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPSPUCCH.

[0163] In one configuration, the first set of time slots may be dynamically scheduled. The second set of time slots may be dynamically scheduled. At least one identical time slot may be omitted from the second set of time slots.

[0164] In one configuration, the mTRP communication may be SDM. The mTRP communication may be associated with at least one PDSCH.

[0165] In one configuration, the mTRP communication may be FDM. The mTRP communication may be associated with at least one PDSCH.

[0166] In one configuration, sTRP communications may be associated with all allocated RBs used to communicate with the UE.

[0167] In one configuration, sTRP communications may be associated with half of all allocated RBs used to communicate with the UE.

[0168] In one configuration, the first set of time slots may be dynamically scheduled. The second set of time slots may be semi-statically scheduled. mTRP communications may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH.

[0169] In one configuration, to schedule a first set of time slots for simultaneous sensing and sTRP communication, at 1402a, the network node may send a first indication to the UE of scheduling a first set of time slots for simultaneous sensing and sTRP communication. For example, 1402a may be Fig.16 Component 199 in the reference Fig.11 At 1108, the network node 1104 may send a first indication to the UE 1102 of a first set of time slots scheduled for simultaneous sensing and sTRP communications.

[0170] To schedule a second set of time slots for multi-TRP communication with the UE, at 1404a, the network node may send a second indication to the UE of scheduling a second set of time slots for multi-TRP communication. For example, 1404a may be Fig.16 Component 199 in the reference Fig.11 , at 1112, the network node 1104 may send a second indication to the UE 1102 of a second set of time slots scheduled for multi-TRP communication.

[0171] Fig.151500 is an example of a hardware implementation of an example device 1504. The device 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1504 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., a cellular RF transceiver). The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the device 1504 may also include one or more subscriber identity module (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power source 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include their own dedicated antennas and / or communicate using antennas 1580. The cellular baseband processor 1524 communicates with the UE 104 and / or with the RU associated with the network entity 1502 through the transceiver 1522 via one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory module 1526 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 1524 / application processor 1506 to perform the various functions described above when executed by the cellular baseband processor 1524 / application processor 1506. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 when executing the software.The cellular baseband processor 1524 / application processor 1506 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1504 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1524 and / or the application processor 1506, while in another configuration, the device 1504 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1504.

[0172] As discussed above, component 198 is configured to receive a first indication of a first group of time slots scheduled for simultaneous sensing and sTRP communication from a network node. Component 198 may be configured to receive a second indication of a second group of time slots scheduled for mTRP communication from a network node. The first group of time slots and the second group of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP. Component 198 may be in a cellular baseband processor 1524, an application processor 1506, or in both a cellular baseband processor 1524 and an application processor 1506. Component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. As shown, device 1504 may include a variety of components configured for various functions. In one configuration, the device 1504 (and in particular the cellular baseband processor 1524 and / or the application processor 1506) includes means for receiving a first indication from a network node of a first set of time slots scheduled for simultaneous sensing and sTRP communications. The device 1504 (and in particular the cellular baseband processor 1524 and / or the application processor 1506) includes means for receiving a second indication from a network node of a second set of time slots scheduled for mTRP communications. The first set of time slots and the second set of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP.

[0173] In one configuration, the first group of time slots may be scheduled semi-statically. The second group of time slots may be scheduled dynamically. The mTRP communication may be TDM. The sTRP communication with the UE may be associated with a single TRP between the first TRP and the second TRP. In one configuration, the first TRP and the second TRP may be associated with an equal number of time slots across the first group of time slots and the second group of time slots with respect to sTRP communication or mTRP communication. In one configuration, the first group of time slots may be scheduled semi-statically. The second group of time slots may be scheduled semi-statically. At least one identical time slot may be omitted from the second group of time slots. In one configuration, the first group of time slots may be associated with a preconfigured TCI state. In one configuration, the mTRP communication may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH. In one configuration, the first group of time slots may be scheduled dynamically. The second group of time slots may be scheduled dynamically. At least one identical time slot may be omitted from the second group of time slots. In one configuration, mTRP communications may be SDM. mTRP communications may be associated with at least one PDSCH. In one configuration, mTRP communications may be FDM. mTRP communications may be associated with at least one PDSCH. In one configuration, sTRP communications may be associated with all allocated RBs for communicating with the UE. In one configuration, sTRP communications may be associated with half of all allocated RBs for communicating with the UE. In one configuration, the first group of time slots may be dynamically scheduled. The second group of time slots may be semi-statically scheduled. mTRP communications may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH.

[0174] A means may be a component 198 of the apparatus 1504 configured to perform the functions recited by the means. As described above, the apparatus 1504 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, a means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0175] Fig.161600 is a diagram illustrating an example of a hardware implementation of a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or a RU 1640. For example, depending on the layer functionality handled by the component 199, the network entity 1602 may include a CU 1610; both the CU 1610 and the DU 1630; each of the CU 1610, the DU 1630, and the RU 1640; the DU 1630; both the DU 1630 and the RU 1640; or the RU 1640. The CU 1610 may include a CU processor 1612. The CU processor 1612 may include an on-chip memory 1612'. In some aspects, the CU 1610 may also include an additional memory module 1614 and a communication interface 1618. CU 1610 communicates with DU 1630 via a midhaul link such as an F1 interface. DU 1630 may include a DU processor 1632. DU processor 1632 may include on-chip memory 1632'. In some aspects, DU 1630 may also include additional memory modules 1634 and communication interfaces 1638. DU 1630 communicates with RU 1640 via a fronthaul link. RU 1640 may include a RU processor 1642. RU processor 1642 may include on-chip memory 1642'. In some aspects, RU 1640 may also include additional memory modules 1644, one or more transceivers 1646, antenna 1680, and communication interface 1648. RU 1640 communicates with UE 104. On-chip memory 1612', 1632', 1642' and additional memory modules 1614, 1634, 1644 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1612, 1632, 1642 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0176] As discussed above, component 199 is configured to schedule a first group of time slots for simultaneous sensing and sTRP communication with the UE. Component 199 is configured to schedule a second group of time slots for mTRP communication with the UE. The first group of time slots and the second group of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP. Component 199 may be within one or more processors of one or more of CU1610, DU 1630, and RU 1640. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. Network entity 1602 may include a variety of components configured for various functions. In one configuration, network entity 1602 includes a component for scheduling a first group of time slots for simultaneous sensing and sTRP communication with the UE. Network entity 1602 includes a component for scheduling a second group of time slots for mTRP communication with the UE. The first set of time slots and the second set of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP.

[0177] In one configuration, the first group of time slots may be scheduled semi-statically. The second group of time slots may be scheduled dynamically. The mTRP communication may be TDM. The sTRP communication with the UE may be associated with a single TRP between the first TRP and the second TRP. In one configuration, the first TRP and the second TRP may be associated with an equal number of time slots across the first group of time slots and the second group of time slots with respect to sTRP communication or mTRP communication. In one configuration, the first group of time slots may be scheduled semi-statically. The second group of time slots may be scheduled semi-statically. At least one identical time slot may be omitted from the second group of time slots. In one configuration, the first group of time slots may be associated with a preconfigured TCI state. In one configuration, the mTRP communication may be associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH. In one configuration, the first group of time slots may be scheduled dynamically. The second group of time slots may be scheduled dynamically. At least one identical time slot may be omitted from the second group of time slots. In one configuration, mTRP communications may be SDM. mTRP communications may be associated with at least one PDSCH. In one configuration, mTRP communications may be FDM. mTRP communications may be associated with at least one PDSCH. In one configuration, sTRP communications may be associated with all allocated RBs for communicating with a UE. In one configuration, sTRP communications may be associated with half of all allocated RBs for communicating with a UE. In one configuration, a first group of time slots may be dynamically scheduled. A second group of time slots may be semi-statically scheduled. mTRP communications may be associated with one or more of PDCCH monitoring, periodic or SP SPUSCH, or periodic or SPS PUCCH. In one configuration, a component for scheduling a first group of time slots for simultaneous sensing and sTRP communications with a UE may be further configured to: send a first indication to the UE of a first group of time slots scheduled for simultaneous sensing and sTRP communications. The component for scheduling a second set of time slots for multi-TRP communication with the UE may be further configured to send a second indication to the UE of scheduling the second set of time slots for multi-TRP communication.

[0178] A means may be a component 199 of the network entity 1602 configured to perform the functions described in the means. As described above, the network entity 1602 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, a means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described in the means.

[0179] Return to reference Figures 4 to 16, the network node may schedule a first set of time slots for simultaneous sensing and sTRP communications with the UE. The network node may send a first indication to the UE of the first set of time slots scheduled for simultaneous sensing and sTRP communications. The network node may schedule a second set of time slots for mTRP communications with the UE. The network node may send a second indication to the UE of scheduling a second set of time slots for mTRP communications. The first set of time slots and the second set of time slots may include at least one identical time slot. The network node may be associated with the first TRP and the second TRP. Therefore, the sTRP-mTRP time slot pattern associated with periodic continuous sensing time slots may be optimized. In addition, the behavior of the system may be defined in the event that there may be a conflict at one or more time slots between the scheduled mTRP communication and the scheduled simultaneous sensing and sTRP communication.

[0180] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0181] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ......" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean instantaneous action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or instantaneous time limit for the occurrence of the action is required. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device by a collection of devices. All structural and functional equivalents that are known or will be known later to those of ordinary skill in the art throughout the elements of the various aspects described in this disclosure are expressly incorporated herein by reference and are covered by the claims. In addition, anything disclosed herein is not intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. "Module", "mechanism", "element", "equipment" and other words cannot replace the word "component". Therefore, no claim element will be interpreted as a functional component unless the element is explicitly recorded using the phrase "component for...".

[0182] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0183] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0184] Aspect 1 is a method for performing wireless communication at a UE, the method comprising: receiving a first indication of a first group of time slots scheduled for simultaneous sensing and sTRP communication from a network node; and receiving a second indication of a second group of time slots scheduled for mTRP communication from the network node, the first group of time slots and the second group of time slots including at least one identical time slot, and the network node being associated with the first TRP and the second TRP.

[0185] Aspect 2 is a method according to Aspect 1, wherein the first group of time slots is semi-statically scheduled, the second group of time slots is dynamically scheduled, the mTRP communication is TDM, and the sTRP communication with the UE is associated with a single TRP between the first TRP and the second TRP.

[0186] Aspect 3 is a method according to Aspect 2, wherein the first TRP and the second TRP are associated with an equal number of time slots across the first group of time slots and the second group of time slots with respect to the sTRP communication or the mTRP communication.

[0187] Aspect 4 is a method according to aspect 1, wherein the first group of time slots is semi-statically scheduled, the second group of time slots is semi-statically scheduled, and the at least one identical time slot is omitted from the second group of time slots.

[0188] Aspect 5 is a method according to aspect 4, wherein the first set of time slots is associated with a pre-configured TCI state.

[0189] Aspect 6 is a method according to any one of Aspects 4 and 5, wherein the mTRP communication is associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH.

[0190] Aspect 7 is a method according to aspect 1, wherein the first set of time slots is dynamically scheduled, the second set of time slots is dynamically scheduled, and the at least one identical time slot is omitted from the second set of time slots.

[0191] Aspect 8 is a method according to aspect 7, wherein the mTRP communication is SDMed and the mTRP communication is associated with at least one PDSCH.

[0192] Aspect 9 is a method according to aspect 7, wherein the mTRP communication is FDMed and the mTRP communication is associated with at least one PDSCH.

[0193] Aspect 10 is a method according to Aspect 9, wherein the sTRP communication is associated with all allocated RBs used to communicate with the UE.

[0194] Aspect 11 is a method according to Aspect 9, wherein the sTRP communication is associated with half of all allocated RBs used for communicating with the UE.

[0195] Aspect 12 is a method according to Aspect 1, wherein the first group of time slots is dynamically scheduled, the second group of time slots is semi-statically scheduled, and the mTRP communication is associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH.

[0196] Aspect 13 is a method for performing wireless communications at a network node, the method comprising: scheduling a first group of time slots for simultaneous sensing and sTRP communication with a UE; and scheduling a second group of time slots for mTRP communication with the UE, the first group of time slots and the second group of time slots including at least one identical time slot, and the network node being associated with a first TRP and a second TRP.

[0197] Aspect 14 is a method according to Aspect 13, wherein the first group of time slots is semi-statically scheduled, the second group of time slots is dynamically scheduled, the mTRP communication is TDM, and the sTRP communication with the UE is associated with a single TRP between the first TRP and the second TRP.

[0198] Aspect 15 is a method according to Aspect 14, wherein the first TRP and the second TRP are associated with an equal number of time slots across the first group of time slots and the second group of time slots with respect to the sTRP communication with the UE or the mTRP communication with the UE.

[0199] Aspect 16 is a method according to aspect 13, wherein the first set of time slots is semi-statically scheduled, the second set of time slots is semi-statically scheduled, and the at least one identical time slot is omitted from the second set of time slots.

[0200] Aspect 17 is a method according to aspect 16, wherein the first set of time slots is associated with a pre-configured TCI state.

[0201] Aspect 18 is a method according to any one of Aspects 16 and 17, wherein the mTRP communication with the UE is associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPSPUCCH.

[0202] Aspect 19 is a method according to aspect 13, wherein the first set of time slots is dynamically scheduled, the second set of time slots is dynamically scheduled, and the at least one identical time slot is omitted from the second set of time slots.

[0203] Aspect 20 is a method according to aspect 19, wherein the mTRP communication with the UE is SDM, and the mTRP communication with the UE is associated with at least one PDSCH.

[0204] Aspect 21 is a method according to aspect 19, wherein the mTRP communication with the UE is FDM, and the mTRP communication with the UE is associated with at least one PDSCH.

[0205] Aspect 22 is a method according to Aspect 21, wherein the sTRP communication with the UE is associated with all RBs used to communicate with the UE.

[0206] Aspect 23 is a method according to Aspect 21, wherein the sTRP communication with the UE is associated with half of all allocated RBs used for communicating with the UE.

[0207] Aspect 24 is a method according to Aspect 13, wherein the first group of time slots is dynamically scheduled, the second group of time slots is semi-statically scheduled, and the mTRP communication with the UE is associated with one or more of PDCCH monitoring, periodic or SPS PUSCH, or periodic or SPS PUCCH.

[0208] Aspect 25 is a method according to Aspect 13, wherein scheduling the first group of time slots for simultaneous sensing and sTRP communication with the UE also includes: sending a first indication of the first group of time slots scheduled for simultaneous sensing and sTRP communication to the UE, and scheduling the second group of time slots for multiple TRP communication with the UE also includes: sending a second indication of the second group of time slots scheduled for the multiple TRP communication to the UE.

[0209] Aspect 26 is an apparatus for wireless communication, the apparatus comprising: at least one processor, the at least one processor being coupled to a memory, and the at least one processor being configured to implement a method as described in any one of Aspects 1 to 25 based at least in part on information stored in the memory.

[0210] Aspect 27 may be combined with Aspect 26, and further comprises: a transceiver coupled to the at least one processor.

[0211] Aspect 28 is a device for graphics processing, the device comprising means for implementing the method as described in any one of Aspects 1 to 25.

[0212] Aspect 29 is a non-transitory computer-readable medium storing computer-executable code, which, when executed by at least one processor, causes the at least one processor to implement the method as described in any one of aspects 1 to 25.

[0213] Various aspects have been described herein. These and other aspects are within the scope of the following claims.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving, from a network node, a first indication of a first set of time slots scheduled for simultaneous sensing and single transmit receive point (TRP) (sTRP) communications; and A second indication of a second set of time slots scheduled for multi-TRP (mTRP) communications is received from the network node, the first set of time slots and the second set of time slots including at least one identical time slot, the network node being associated with a first TRP and a second TRP.

2. An apparatus according to claim 1, wherein the first group of time slots is semi-statically scheduled, the second group of time slots is dynamically scheduled, the mTRP communication is time division multiplexed (TDM), and the sTRP communication with the UE is associated with a single TRP between the first TRP and the second TRP.

3. An apparatus according to claim 2, wherein the first TRP and the second TRP are associated with an equal number of time slots across the first group of time slots and the second group of time slots with respect to the sTRP communication or the mTRP communication.

4. The apparatus of claim 1, wherein the first set of time slots is semi-statically scheduled, the second set of time slots is semi-statically scheduled, and the at least one identical time slot is omitted from the second set of time slots.

5. The apparatus of claim 4, wherein the first set of time slots is associated with a preconfigured transmit configuration indicator (TCI) state.

6. An apparatus according to claim 4, wherein the mTRP communication is associated with one or more of a physical downlink control channel (PDCCH) monitoring, a periodic or semi-persistent (SPS) physical uplink shared channel (PUSCH), or a periodic or SPS physical uplink control channel (PUCCH).

7. The apparatus of claim 1, wherein the first set of time slots is dynamically scheduled, the second set of time slots is dynamically scheduled, and the at least one identical time slot is omitted from the second set of time slots.

8. The apparatus of claim 7, wherein the mTRP communication is spatial division multiplexed (SDM) and the mTRP communication is associated with at least one physical downlink shared channel (PDSCH).

9. The apparatus of claim 7, wherein the mTRP communication is frequency division multiplexed (FDM) and the mTRP communication is associated with at least one physical downlink shared channel (PDSCH).

10. The apparatus of claim 9, wherein the sTRP communication is associated with all allocated resource blocks (RBs) used to communicate with the UE.

11. An apparatus according to claim 9, wherein the sTRP communication is associated with half of all allocated resource blocks (RBs) used to communicate with the UE.

12. An apparatus according to claim 1, wherein the first group of time slots are dynamically scheduled, the second group of time slots are semi-statically scheduled, and the mTRP communication is associated with one or more of a physical downlink control channel (PDCCH) monitoring, a periodic or semi-persistent (SPS) physical uplink shared channel (PUSCH), or a periodic or SPS physical uplink control channel (PUCCH).

13. The apparatus according to claim 1, further comprising: A transceiver is coupled to the at least one processor.

14. A method of wireless communication at a user equipment (UE), the method comprising: receiving, from a network node, a first indication of a first set of time slots scheduled for simultaneous sensing and single transmit receive point (TRP) (sTRP) communications; as well as A second indication of a second set of time slots scheduled for multi-TRP (mTRP) communications is received from the network node, the first set of time slots and the second set of time slots including at least one identical time slot, the network node being associated with a first TRP and a second TRP.

15. A method according to claim 14, wherein the first group of time slots is semi-statically scheduled, the second group of time slots is dynamically scheduled, the mTRP communication is time division multiplexed (TDM), and the sTRP communication with the UE is associated with a single TRP between the first TRP and the second TRP.

16. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: scheduling a first set of time slots for simultaneous sensing and single transmit receive point (TRP) (sTRP) communication with a user equipment (UE); as well as A second group of time slots is scheduled for multi-TRP (mTRP) communication with the UE, the first group of time slots and the second group of time slots include at least one identical time slot, and the network node is associated with the first TRP and the second TRP.

17. An apparatus according to claim 16, wherein the first group of time slots is semi-statically scheduled, the second group of time slots is dynamically scheduled, the mTRP communication is time division multiplexed (TDM), and the sTRP communication with the UE is associated with a single TRP between the first TRP and the second TRP.

18. An apparatus according to claim 17, wherein the first TRP and the second TRP are associated with an equal number of time slots across the first group of time slots and the second group of time slots with respect to the sTRP communication with the UE or the mTRP communication with the UE.

19. The apparatus of claim 16, wherein the first set of time slots is semi-statically scheduled, the second set of time slots is semi-statically scheduled, and the at least one identical time slot is omitted from the second set of time slots.

20. The apparatus of claim 19, wherein the first set of time slots is associated with a preconfigured transmit configuration indicator (TCI) state.

21. An apparatus according to claim 19, wherein the mTRP communication with the UE is associated with one or more of a physical downlink control channel (PDCCH) monitoring, a periodic or semi-persistent (SPS) physical uplink shared channel (PUSCH), or a periodic or SPS physical uplink control channel (PUCCH).

22. The apparatus of claim 16, wherein the first set of time slots is dynamically scheduled, the second set of time slots is dynamically scheduled, and the at least one identical time slot is omitted from the second set of time slots.

23. The apparatus of claim 22, wherein the mTRP communication with the UE is spatial division multiplexed (SDM), and the mTRP communication with the UE is associated with at least one physical downlink shared channel (PDSCH).

24. The apparatus of claim 22, wherein the mTRP communication with the UE is frequency division multiplexed (FDM), and the mTRP communication with the UE is associated with at least one physical downlink shared channel (PDSCH).

25. An apparatus according to claim 24, wherein the sTRP communication with the UE is associated with all allocated resource blocks (RBs) used to communicate with the UE.

26. An apparatus according to claim 24, wherein the sTRP communication with the UE is associated with half of all allocated resource blocks (RBs) used for communicating with the UE.

27. An apparatus according to claim 16, wherein the first group of time slots are dynamically scheduled, the second group of time slots are semi-statically scheduled, and the mTRP communication with the UE is associated with one or more of a physical downlink control channel (PDCCH) monitoring, a periodic or semi-persistent (SPS) physical uplink shared channel (PUSCH), or a periodic or SPS physical uplink control channel (PUCCH).

28. The apparatus of claim 16, wherein to schedule the first set of time slots for simultaneous sensing and sTRP communication with the UE, the at least one processor is configured to: send a first indication to the UE of the first set of time slots scheduled for the simultaneous sensing and the sTRP communication, In order to schedule the second group of time slots for multi-TRP communication with the UE, the at least one processor is configured to: send a second indication to the UE to schedule the second group of time slots for the multi-TRP communication.

29. The apparatus according to claim 16, further comprising: A transceiver is coupled to the at least one processor.

30. A method for wireless communication at a network node, the method comprising: scheduling a first set of time slots for simultaneous sensing and single transmit receive point (TRP) (sTRP) communication with a user equipment (UE); as well as A second group of time slots is scheduled for multi-TRP (mTRP) communication with the UE, the first group of time slots and the second group of time slots include at least one identical time slot, and the network node is associated with the first TRP and the second TRP.

Images