Multicast sensing tracking reference signal

Abstract

In an aspect, the first UE and the second UE each detect a target associated with a point of deflection of a transmission beam from the BS to the respective UE, and each transmit information associated with the target to the BS. The BS transmits STRS configuration information to the first UE and the second UE. The BS multicasts STRS to the first UE and the second UE on the transmission beam in accordance with the STRS configuration information.

Description

Technical Field

[0001] This disclosure relates generally to wireless communication, and more specifically to multicast sensing tracking reference signals (STRS). Background Technology

[0002] Wireless communication systems have evolved through multiple generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data and internet-enabled wireless service, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), and so on.

[0003] The fifth-generation (5G) wireless standard, known as New Radio (NR), demands higher data transmission speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide tens of megabits per second (Mbps) of data rate for each of tens of thousands of users, or 1 gigabit per second (Gbps) for dozens of employees on an office floor. It should support hundreds of thousands of simultaneous connections to support large-scale sensor deployments. Therefore, the spectral efficiency of 5G mobile communications should be significantly improved compared to the current 4G standard. Furthermore, signaling efficiency should be enhanced, and latency should be substantially reduced compared to the current standard.

[0004] 5G enables wireless communication between network nodes such as base stations, user equipment (UE), vehicles, and automated factory machinery using mmW RF signals. However, mmW RF signals can also be used for other purposes. For example, they can be used in weapon systems (e.g., as short-range fire control radar in tanks and aircraft), security screening systems (e.g., in scanners that detect weapons and other dangerous objects carried under clothing), and pharmaceuticals (e.g., treating diseases by altering cell growth). Summary of the Invention

[0005] The following is a simplified overview relating to one or more aspects disclosed herein. Thus, this overview should not be considered an exhaustive overview relating to all aspects of the conception, nor should it be considered to identify key or decisive elements relating to all aspects of the conception or to depict the scope associated with any particular aspect. Accordingly, the following overview serves only to present, in a simplified form, certain concepts relating to one or more aspects of the mechanism disclosed herein before the detailed descriptions presented below.

[0006] In one aspect, the method of operating a base station includes: receiving information associated with a first target from a first user equipment (UE), the first target being associated with a deflection point of a transmission beam from the base station to the first UE; receiving information associated with a second target from a second UE, the second target being a deflection point of a transmission beam from the base station to the second UE; sending Sensing Tracking Reference Signal (STRS) configuration information based on the information associated with the first target and the second target to the first UE and the second UE; and multicasting the Sensing Tracking Reference Signal (STRS) to the first UE and the second UE on the transmission beam according to the SRS configuration information.

[0007] In some aspects, the SRS configuration information is sent to the first UE and the second UE via unicast.

[0008] In some respects, the first target and the second target correspond to a common target, and the SRS configuration information is sent by the base station without the base station knowing that the first target and the second target correspond to a common target.

[0009] In some aspects, the first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for a common target, and wherein the second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for a common target.

[0010] In some aspects, the SRS configuration information is sent to the first UE and the second UE via multicast.

[0011] In some respects, the SRS configuration information is sent via multicast to the first and second UEs in response to the determination at the base station that the first and second targets correspond to a common target.

[0012] In some aspects, multicast SRS configuration information includes network-specific identifiers for common targets.

[0013] In some respects, SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0014] In one aspect, the method of operating a user equipment (UE) includes: detecting a target associated with a deflection point of a transmission beam from a base station to the UE; sending information associated with the target to the base station; receiving sensing tracking reference signal (STRS) configuration information based on the information associated with the target from the base station; and receiving multicast sensing tracking reference signals (STRS) on a receiving beam associated with the transmission beam according to the SRS configuration information.

[0015] In some respects, the SRS configuration information is received via unicast.

[0016] In some aspects, the SRS configuration information includes UE-specific identifiers for targets.

[0017] In some respects, SRS configuration information is received via multicast.

[0018] In some aspects, multicast SRS configuration information includes the target's network-specific identifier.

[0019] In some respects, SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0020] In one aspect, the base station includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive information associated with a first target from a first user equipment (UE) via the at least one transceiver, the first target being associated with a deflection point of a transmission beam from the base station to the first UE; receive information associated with a second target from a second UE via the at least one transceiver, the second target being a deflection point of a transmission beam from the base station to the second UE; transmit sensing tracking reference signal (STRS) configuration information based on the information associated with the first target and the second target to the first UE and the second UE via the at least one transceiver; and multicast the sensing tracking reference signal (STRS) to the first UE and the second UE on the transmission beam according to the SRS configuration information.

[0021] In some aspects, the SRS configuration information is sent to the first UE and the second UE via unicast.

[0022] In some respects, the first target and the second target correspond to a common target, and the SRS configuration information is sent by the base station without the base station knowing that the first target and the second target correspond to a common target.

[0023] In some aspects, the first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for a common target, and wherein the second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for a common target.

[0024] In some aspects, the SRS configuration information is sent to the first UE and the second UE via multicast.

[0025] In some respects, the SRS configuration information is sent via multicast to the first and second UEs in response to the determination at the base station that the first and second targets correspond to a common target.

[0026] In some aspects, multicast SRS configuration information includes network-specific identifiers for common targets.

[0027] In some respects, SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0028] In one aspect, the user equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: detect a target associated with a deflection point of a transmission beam from a base station to the UE; transmit information associated with the target to the base station via the at least one transceiver; receive sensing tracking reference signal (STRS) configuration information based on the target-associated information from the base station via the at least one transceiver; and receive multicast sensing tracking reference signals (STRS) on a receive beam associated with the transmission beam via the at least one transceiver according to the SRS configuration information.

[0029] In some respects, the SRS configuration information is received via unicast.

[0030] In some aspects, the SRS configuration information includes UE-specific identifiers for targets.

[0031] In some respects, SRS configuration information is received via multicast.

[0032] In some aspects, multicast SRS configuration information includes the target's network-specific identifier.

[0033] In some respects, SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0034] In one aspect, the base station includes: means for receiving information associated with a first target from a first user equipment (UE), the first target being associated with a deflection point of a transmission beam from the base station to the first UE; means for receiving information associated with a second target from a second UE, the second target being a deflection point of the transmission beam from the base station to the second UE; means for transmitting Sensing Tracking Reference Signal (STRS) configuration information based on the information associated with the first target and the second target to the first UE and the second UE; and means for multicasting the Sensing Tracking Reference Signal (STRS) to the first UE and the second UE on the transmission beam according to the SRS configuration information.

[0035] In one aspect, the SRS configuration information is sent to the first UE and the second UE via unicast.

[0036] In some respects, the first target and the second target correspond to a common target, and the SRS configuration information is sent by the base station without the base station knowing that the first target and the second target correspond to a common target.

[0037] In some aspects, the first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for a common target, and wherein the second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for a common target.

[0038] In one aspect, the SRS configuration information is sent to the first UE and the second UE via multicast.

[0039] In some respects, the SRS configuration information is sent via multicast to the first and second UEs in response to the determination at the base station that the first and second targets correspond to a common target.

[0040] In some aspects, multicast SRS configuration information includes network-specific identifiers for common targets.

[0041] In one aspect, the SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0042] In one aspect, the user equipment (UE) includes: components for detecting a target associated with a deflection point of a transmission beam from a base station to the UE; components for transmitting information associated with the target to the base station; components for receiving sensing tracking reference signal (STRS) configuration information based on the information associated with the target from the base station; and components for receiving multicast sensing tracking reference signals (STRS) on a receiving beam associated with the transmission beam according to the SRS configuration information.

[0043] In some respects, the SRS configuration information is received via unicast.

[0044] In some aspects, the SRS configuration information includes UE-specific identifiers for targets.

[0045] In some respects, SRS configuration information is received via multicast.

[0046] In some aspects, multicast SRS configuration information includes the target's network-specific identifier.

[0047] In some respects, SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0048] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a base station, cause the base station to: receive information associated with a first target from a first user equipment (UE), the first target being associated with a deflection point of a transmission beam from the base station to the first UE; receive information associated with a second target from a second UE, the second target being a deflection point of a transmission beam from the base station to the second UE; transmit sensing tracking reference signal (STRS) configuration information based on the information associated with the first and second targets to the first and second UEs; and multicast the sensing tracking reference signal (STRS) to the first and second UEs on the transmission beam according to the SRS configuration information.

[0049] In some aspects, the SRS configuration information is sent to the first UE and the second UE via unicast.

[0050] In some respects, the first target and the second target correspond to a common target, and the SRS configuration information is sent by the base station without the base station knowing that the first target and the second target correspond to a common target.

[0051] In some aspects, the first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for a common target, and wherein the second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for a common target.

[0052] In some aspects, the SRS configuration information is sent to the first UE and the second UE via multicast.

[0053] In some respects, the SRS configuration information is sent via multicast to the first and second UEs in response to the determination at the base station that the first and second targets correspond to a common target.

[0054] In some aspects, multicast SRS configuration information includes network-specific identifiers for common targets.

[0055] In some respects, SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0056] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: detect a target associated with a deflection point of a transmission beam from a base station to the UE; send information associated with the target to the base station; receive sensing tracking reference signal (STRS) configuration information based on the information associated with the target from the base station; and receive multicast sensing tracking reference signals (STRS) on a receiving beam associated with the transmission beam according to the SRS configuration information.

[0057] In some respects, the SRS configuration information is received via unicast.

[0058] In some aspects, the SRS configuration information includes UE-specific identifiers for targets.

[0059] In some respects, SRS configuration information is received via multicast.

[0060] In some aspects, multicast SRS configuration information includes the target's network-specific identifier.

[0061] In some respects, SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0062] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. Attached Figure Description

[0063] The accompanying drawings are presented as examples to help describe one or more aspects of the disclosed subject matter, and are provided only to illustrate these examples and not to limit it.

[0064] Figure 1 An example wireless communication system according to various aspects of this disclosure is shown.

[0065] Figure 2A and Figure 2B An example wireless network architecture according to various aspects of this disclosure is shown.

[0066] Figures 3A to 3C This is a simplified block diagram of several example aspects of components that can be adopted in wireless communication nodes and configured to support communications as taught herein.

[0067] Figure 4A An example monostation radar system is shown.

[0068] Figure 4B An example bistatic radar system is shown.

[0069] Figure 5 This is an example graph showing the radio frequency (RF) channel response over time.

[0070] Figure 6 An example single-target beam management use case for dual-station RF sensing is shown.

[0071] Figure 7 An example multi-target beam management use case for dual-station RF sensing is shown.

[0072] Figure 8A An example scan phase with dual-station RF sensing is shown.

[0073] Figure 8B An example tracking phase with dual-station RF sensing is shown.

[0074] Figure 8C This is an example message stream for beam-dependent target tracking with dual-station RF sensing beam management.

[0075] Figure 9A An example use case for multi-target detection using dual-station radio frequency sensing is shown.

[0076] Figure 9B This is an example message stream for multi-target bi-station RF sensing beam management.

[0077] Figure 10A An example use case for target group detection using dual-station radio frequency sensing is shown.

[0078] Figure 10B This is an example message stream for target group bi-station RF sensing beam management.

[0079] Figure 11A An example use case for single-sided beam management for dual-station RF sensing is shown.

[0080] Figure 11B This is an example message stream for single-sided dual-station RF sensing beam management.

[0081] Figure 12 Multi-UE tracking scenarios are illustrated according to aspects of this disclosure.

[0082] Figure 13A bi-station radio frequency sensing beam management process 1300 according to aspects of this disclosure is illustrated.

[0083] Figure 14 A multi-UE tracking scenario is shown according to another aspect of this disclosure.

[0084] Figure 15 An exemplary wireless communication process according to aspects of this disclosure is shown.

[0085] Figure 16 An exemplary wireless communication process according to aspects of this disclosure is shown.

[0086] Figure 17 The aspects according to this disclosure are shown respectively. Figures 15 to 16 An example implementation of the process.

[0087] Figure 18 Each shows another aspect according to this disclosure. Figures 15 to 16 An example implementation of the process. Detailed Implementation

[0088] Aspects of this disclosure are provided in the following description and in the related figures for the various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of this disclosure. Furthermore, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0089] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior or advantageous over other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0090] Those skilled in the art will understand that any of a variety of different techniques and skills can be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof, depending in part on the specific application, in part on the required design, in part on the corresponding technology, etc.

[0091] Furthermore, many aspects are described with respect to the sequence of actions to be performed by elements of a computing device, for example. It will be understood that the various actions described herein can be performed by a particular circuit (e.g., an application-specific integrated circuit (ASIC)), program instructions executed by one or more processors, or a combination of both. Moreover, the sequence of actions described herein can be considered entirely embodied in any form of computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or instruct the associated processor of the device to perform the functionalities described herein. Therefore, various aspects of this disclosure can be embodied in many different forms, all of which are contemplated within the scope of the claimed subject matter. Additionally, for each aspect described herein, any corresponding form of such aspect can be described herein as, for example, "logic configured to perform the described actions."

[0092] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “Base Station” (BS) are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). Typically, a UE can be any wireless communication device used by a user to communicate via a wireless communication network (e.g., mobile phone, router, tablet, laptop, tracking device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Equipment,” “Mobile Terminal,” “Mobile Station,” or variations thereof. Typically, a UE can communicate with a core network via the RAN, and through the core network, a UE can connect to external networks (such as the Internet) and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as via a wired access network, a wireless local area network (WLAN) (e.g., based on IEEE 802.11, etc.).

[0093] A base station may operate under one of several RATs (Radio Access Points) communicating with the UE, depending on the network in which it is deployed, and may be alternatively referred to as an Access Point (AP), Network Node, NodeB, Evolved NodeB (eNB), Next Generation eNB (ng-eNB), New Radio (NR) NodeB (also referred to as gNB or gNodeB), etc. The base station may primarily be used to support the UE's radio access, including supporting the data, voice, and / or signaling connections of the supported UE. In some systems, the base station may provide purely edge node signaling functions, while in others it may provide additional control and / or network management functions. The communication link through which the UE can signal to the base station is referred to as an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can signal to the UE is referred to as a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term Traffic Channel (TCH) may refer to an uplink / reverse or downlink / forward traffic channel.

[0094] The term "base station" can refer to a single physical transmit-receive point (TRP) or multiple physical TRPs, which may or may not be co-located. For example, when the term "base station" refers to a single physical TRP, the physical TRP can be an antenna of the base station, corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple co-located physical TRPs, the physical TRPs can be antenna arrays of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRPs can be a distributed antenna system (DAS) (a spatially separated network of antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, a non-co-located physical TRP can be a serving base station that receives measurement reports from the UE and neighboring base stations where the UE is measuring its reference RF signal (or simply "reference signal"). Since the TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station will be understood to refer to the specific TRP of the base station.

[0095] In some implementations that support UE positioning, the base station may not support the UE's radio access (e.g., it may not support the UE's data, voice, and / or signaling connections), but may instead transmit reference signals to the UE for measurement by the UE, and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to the UE) and / or a location measurement unit (e.g., when receiving and measuring signals from the UE).

[0096] An “RF signal” comprises electromagnetic waves of a given frequency that transmit information across space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a “multipath” RF signal. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal,” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.

[0097] refer to Figure 1 An example wireless communication system 100 is illustrated. The wireless communication system 100 (also referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. Base stations 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). In one aspect, macrocell base stations may include eNBs and / or ng-eNBs where the wireless communication system 100 corresponds to an LTE network, or gNBs where the wireless communication system 100 corresponds to an NR network, or a combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

[0098] Base stations 102 can collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) via backhaul link 122, and reach one or more location servers 172 (which may be part of or outside the core network 170). Among other functions, base stations 102 can perform one or more of the following related functions: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, non-access stratum (NAS) message distribution, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC / 5GC) via backhaul link 134, which can be wired or wireless.

[0099] Base station 102 can wirelessly communicate with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used to communicate with a base station (e.g., on a frequency resource (referred to as carrier frequency, component carrier, carrier, frequency band, etc.)) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI)) to distinguish cells operating via the same or different carrier frequencies). In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), etc.). Because a cell is supported by a specific base station, the term “cell” can refer to one or both of the logical communication entity and the base station that supports it, depending on the context. Additionally, since the TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area of ​​a base station (e.g., a sector), provided that the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0100] Although the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in handover areas), some of the geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macro cell base stations 102. A network that includes both small and macro cell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that can provide service to restricted groups referred to as Closed Subscriber Groups (CSGs).

[0101] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may use one or more carrier frequencies. Carrier allocation may be asymmetrical relative to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).

[0102] The wireless communication system 100 may also include a wireless local area network (WLAN) access point (AP) 150, which communicates with a WLAN station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a free channel assessment (CCA) or listen-before-talk (LBT) process to determine whether the channel is available before communication.

[0103] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5GHz unlicensed spectrum as WLAN AP 150. Employing LTE / 5G in unlicensed spectrum can enhance coverage of the access network and / or increase its capacity. NR in unlicensed spectrum can be referred to as NR-U. LTE in unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0104] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180, which can communicate with the UE 182 at mmW and / or near-mmW frequencies. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF ranges from 30 GHz to 300 GHz and has wavelengths between 1 mm and 10 mm. Radio waves in this band can be referred to as millimeter waves. Near-millimeter waves can extend down to frequencies of 3 GHz, with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz and are also referred to as centimeter waves. Communication using mmW / near-mmW radio bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it should be understood that in alternative configurations, one or more base stations 102 may also transmit using mmW or near-mmW and beamforming. Therefore, it should be understood that the foregoing description is merely illustrative and should not be construed as limiting any aspect of the disclosure herein.

[0105] Transmit beamforming is a technique used to focus RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectional). Using transmit beamforming, the network node determines the location of a given target device (e.g., a UE) (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing the receiving device with a faster (in terms of data rate) and stronger RF signal. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (called a "phased array" or "antenna array") that creates the RF beam, which can be "steered" to point in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to the individual antennas with the correct phase relationship so that radio waves from the individual antennas are superimposed to increase radiation in the desired direction while canceling out radiation in undesired directions.

[0106] Transmit beams can be quasi-co-located, meaning they appear to have the same parameters to the receiver (e.g., UE), regardless of whether the transmit antennas of the network nodes are physically co-located. In NR, there are four types of quasi-co-located (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about a second reference RF signal on a second beam can be derived from information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of type QCL D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0107] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver may increase the gain setting and / or adjust the phase setting of the antenna array in a specific direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver performs beamforming in a certain direction, it means that the beam gain in that direction is higher than the beam gain in other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction for all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signal received from that direction.

[0108] The receive beam can be spatially correlated. Spatial correlation means that the parameters of the transmit beam used for the second reference signal can be derived from information about the receive beam of the first reference signal. For example, the UE can use a specific receive beam to receive one or more reference downlink reference signals (e.g., Position Reference Signal (PRS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell Specific Reference Signal (CRS), Channel State Information Reference Signal (CSI-RS), Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Synchronization Signal Block (SSB), etc.) from the base station. The UE can then form a transmit beam for transmitting one or more uplink reference signals (e.g., Uplink Position Reference Signal (UL-PRS), Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), PTRS, etc.) to the base station based on the parameters of the receive beam.

[0109] Note that a "downlink" beam can be either a transmit or receive beam, depending on the entity forming it. For example, if a base station is forming a downlink beam to transmit a reference signal to a UE, then the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, then it is a receive beam for receiving downlink reference signals. Similarly, an "uplink" beam can be either a transmit or receive beam, depending on the entity forming it. For example, if a base station is forming an uplink beam, then it is an uplink receive beam, and if a UE is forming an uplink beam, then it is an uplink transmit beam.

[0110] In 5G, the spectrum in which radio nodes (e.g., base stations 102 / 180, UE 104 / 182) operate is divided into multiple frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In multi-carrier systems, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by UE 104 / 182 and the cell in which UE 104 / 182 performs the initial Radio Resource Control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all public and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured when establishing an RRC connection between UE 104 and the anchor carrier and can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only the necessary signaling information and signals; for example, those specific to the UE may not be present in the secondary carrier because the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether PCell or SCell) corresponds to the carrier frequency / component carrier on which a base station is communicating, the terms “cell,” “serving cell,” “component carrier,” “carrier frequency,” etc., are used interchangeably.

[0111] For example, still refer to Figure 1 One of the frequencies used by macro cell base station 102 can be an anchor carrier (or "PCell"), and the other frequencies used by macro cell base station 102 and / or mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two aggregated 20MHz carriers in a multi-carrier system theoretically result in a doubling of the data rate (i.e., 40MHz) compared to a single 20MHz carrier.

[0112] The wireless communication system 100 may also include a UE 164, which can communicate with the macro cell base station 102 via communication link 120 and / or with the mmW base station 180 via mmW communication link 184. For example, the macro cell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0113] The wireless communication system 100 may also include one or more UEs (such as UE 190) that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1 In the example, UE 190 has D2D P2P links 192 and 194, where one of UEs 104 is connected to one of base stations 102 via D2D P2P link 192 (e.g., UE 190 can indirectly obtain cellular connectivity through it), and WLAN STA 152 is connected to WLAN AP 150 via D2D P2P link 194 (UE 190 can indirectly obtain WLAN-based Internet connectivity through it). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D) or WiFi Direct (WiFi-D). wait.

[0114] refer to Figure 2A An example wireless network architecture 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can functionally be considered as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which cooperate to form the core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to control plane functions 214 and user plane functions 212. In an additional configuration, the ng-eNB 224 can also connect to the 5GC 210 via the NG-C 215 to control plane function 214 and the NG-U 213 to user plane function 212. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNB 222s, while other configurations include one or more of ng-eNB 224 and gNB 222. The gNB 222 or ng-eNB 224 can be used with UE 204 (e.g., Figure 1 The UE 204 can communicate with any of the UEs depicted in the diagram. Another optional aspect may include a location server 230, which can communicate with the 5GC 210 to provide location assistance to the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204, which may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not shown). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be external to the core network.

[0115] refer to Figure 2B Another example wireless network architecture 250 is shown. For example, 5GC 260 can be functionally viewed as a control plane function provided by Access and Mobility Management Function (AMF) 264 and a user plane function provided by User Plane Function (UPF) 262, which cooperate to form the core network (i.e., 5GC 260). User plane interface 263 and control plane interface 265 connect ng-eNB 224 to 5GC 260 and specifically to UPF 262 and AMF 264, respectively. In an additional configuration, gNB 222 can also connect to 5GC 260 via control plane interface 265 to AMF 264 and user plane interface 263 to UPF 262. Furthermore, ng-eNB 224 can communicate directly with gNB 222 via backhaul connection 223, with or without a direct gNB connection to 5GC 260. In some configurations, the new RAN 220 may have only one or more gNB 222s, while other configurations include one or more of ng-eNB 224 and gNB 222. The gNB 222 or ng-eNB 224 can be used with UE 204 (e.g., Figure 1 The base station of the new RAN 220 communicates with the AMF 264 via the N2 interface and with the UPF 262 via the N3 interface.

[0116] The functions of AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transmission of Session Management (SM) messages between UE 204 and Session Management Function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of Short Message Service (SMS) messages between UE 204 and Short Message Service Function (SMSF) (not shown), and Security Anchoring Function (SEAF). AMF 264 also interacts with Authentication Server Function (AUSF) (not shown) and UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM)-based authentication, AMF 264 retrieves security material from AUSSF. The functions of AMF 264 also include Security Context Management (SCM). SCM receives a key from SEAF, which is used to derive an access network-specific key. The AMF 264 also includes functions for location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between new RAN 220 and LMF 270, allocation of Evolved Packet System (EPS) bearer identifiers for interoperability with EPS, and UE 204 mobility event notification. Additionally, the AMF 264 supports functions for non-3GPP access networks.

[0117] The functions of UPF 262 include acting as an anchor point for intra / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point for interconnection with a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic orientation), lawful interception (user plane collection), traffic usage reporting, user plane Quality of Service (QoS) processing (e.g., uplink / downlink rate enforcement, reflected QoS marking in downlink), uplink traffic authentication (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the transmission of location service messages via the user plane between UE 204 and a location server (such as a Secure User Plane Location (SUPL) Location Platform (SLP) 272).

[0118] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, service orientation configuration at UPF 262 for routing services to appropriate destinations, control over policy enforcement and QoS portions, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0119] Another optional aspect may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each can correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not shown). The SLP 272 can support similar functionality to the LMF 270, but the LMF 270 can communicate with the AMF 264, the new RAN 220, and the UE 204 via the control plane (e.g., using interfaces and protocols designed to transmit signaling messages rather than voice or data), while the SLP 272 can communicate with the UE 204 and external clients via the user plane. Figure 2B (not shown) to communicate (e.g., using protocols designed to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0120] In one aspect, the LMF 270 and / or SLP 272 can be integrated into base stations such as gNB 222 and / or ng eNB 224. When integrated into gNB 222 and / or ng eNB 224, the LMF 270 and / or SLP 272 can be referred to as a “location management component” or “LMC”. However, as used herein, references to LMF 270 and SLP 272 include cases where the LMF 270 and SLP 272 are components of the core network (e.g., 5GC 260) and cases where the LMF 270 and SLP 272 are components of the base station.

[0121] refer to Figure 3A , Figure 3B and Figure 3CSeveral example components (represented by corresponding blocks) are shown that can be incorporated into UE 302 (which may correspond to any of the UEs described herein), base station 304 (which may correspond to any of the base stations described herein), and network entity 306 (which may correspond to or embody any of the network functions described herein, including location server 230 and LMF 270) to support file transfer operations. It should be understood that these components can be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.). The components shown can also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Furthermore, a given device may contain one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0122] UE 302 and base station 304 each include Wireless Wide Area Network (WWAN) transceivers 310 and 350, respectively, configured to communicate via one or more wireless communication networks (not shown) (such as NR networks, LTE networks, GSM networks, etc.). WWAN transceivers 310 and 350 may be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNB, gNB), via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 may be configured differently to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.), respectively, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.) according to a designated RAT. Specifically, transceivers 310 and 350 include one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0123] UE 302 and base station 304 also include, at least in some cases, wireless local area network (WLAN) transceivers 320 and 360, respectively. WLAN transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, for use via at least one designated RAT (e.g., WiFi, LTE-D, etc.) on the wireless communication medium of interest. WLAN transceivers 320 and 360 can be configured differently to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) respectively, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.) respectively according to a specified RAT. Specifically, transceivers 320 and 360 include one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368 respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368 respectively.

[0124] In some implementations, the transceiver circuitry including at least one transmitter and at least one receiver may comprise an integrated device (e.g., transmitter and receiver circuitry embodied as a single communication device), may comprise a separate transmitter device and a separate receiver device in some implementations, or may be embodied in other ways in other implementations. In one aspect, the transmitter may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the respective device to perform transmit "beamforming," as described herein. Similarly, the receiver may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the respective device to perform receive beamforming, as described herein. In one aspect, the transmitter and receiver may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that the respective device may receive or transmit only at a given time, rather than simultaneously. The wireless communication equipment of UE 302 and / or base station 304 (e.g., one or both of transceivers 310 and 320 and / or 350 and 360) may also include network eavesdropping modules (NLMs) for performing various measurements.

[0125] UE 302 and base station 304 also include, at least in some cases, satellite positioning system (SPS) receivers 330 and 370. SPS receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, to receive SPS signals 338 and 378, such as Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. SPS receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing SPS signals 338 and 378, respectively. SPS receivers 330 and 370 appropriately request information and operations from other systems and perform calculations required to determine the location of UE 302 and base station 304 using measurements obtained through any suitable SPS algorithm.

[0126] Base station 304 and network entity 306 each include at least one network interface 380 and 390 for communicating with other network entities. For example, network interfaces 380 and 390 (e.g., one or more network access ports) may be configured to communicate with one or more network entities via a wired or wireless backhaul connection. In some aspects, network interfaces 380 and 390 may be implemented as transceivers configured to support wired or wireless signal-based communication. This communication may involve, for example, sending and receiving messages, parameters, and / or other types of information.

[0127] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302 includes processor circuitry that implements processing system 332 for providing, for example, RF sensing-related functions and for providing other processing functions. Base station 304 includes processing system 384 for providing, for example, RF sensing-related functions and for providing other processing functions. Network entity 306 includes processing system 394 for providing, for example, RF sensing-related functions and for providing other processing functions. In one aspect, processing systems 332, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), or other programmable logic devices or processing circuitry.

[0128] UE 302, base station 304, and network entity 306 include memory circuitry that respectively implements memory components 340, 386, and 396 (e.g., each includes a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). In some cases, UE 302, base station 304, and network entity 306 may each include RF sensing components 342, 388, and 398. RF sensing components 342, 388, and 398 may be hardware circuitry that is part of or coupled to processing systems 332, 384, and 394, respectively, which, when executed, causes UE 302, base station 304, and network entity 306 to perform the functions described herein. In other aspects, RF sensing components 342, 388, and 398 may be external to processing systems 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, RF sensing components 342, 388, and 398 may be memory modules (e.g., stored in memory components 340, 386, and 396, respectively) Figures 3A to 3C As shown, the memory module enables UE 302, base station 304 and network entity 306 to perform the functions described herein when handled by processing systems 332, 384 and 394 (or modem processing system, another processing system, etc.).

[0129] UE 302 may include one or more sensors 344 coupled to processing system 332 to provide motion and / or orientation information independent of motion data derived from signals received by WWAN transceiver 310, WLAN transceiver 320, and / or SPS receiver 330. For example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, sensor 344 may include various different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate position in 2D and / or 3D coordinate systems.

[0130] Additionally, UE 302 includes a user interface 346 for providing instructions to the user (e.g., auditory and / or visual instructions) and / or for receiving user input (e.g., after user actuation of a sensing device such as a keyboard, touchscreen, microphone, etc.). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0131] Referring more specifically to processing system 384, in the downlink, IP packets from network entity 306 can be provided to processing system 384. Processing system 384 can implement functions targeting the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The processing system 384 can provide RRC layer functions associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration of UE measurement reports; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper-layer packet data units (PDUs), error correction via automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority processing, and logical channel priority.

[0132] Transmitter 354 and receiver 352 can implement Layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) can include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 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-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine the decoding and modulation scheme, as well as for spatial processing. The channel estimates can be derived from a reference signal transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas 356. Transmitter 354 can modulate an RF carrier with the corresponding spatial stream for transmission.

[0133] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to processing system 332. Transmitter 314 and receiver 312 implement Layer 1 functions associated with various signal processing functions. Receiver 312 can perform spatial processing on this information to recover any spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. The data and control signals are then provided to the processing system 332 that implements the functions of layer 3 and layer 2.

[0134] In the uplink, processing system 332 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the core network. Processing system 332 is also responsible for error detection.

[0135] Similar to the functions described in conjunction with downlink transmissions performed by base station 304, processing system 332 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority processing, and logical channel priority.

[0136] The channel estimate derived from the reference signal or feedback transmitted by the base station 304 via the channel estimator can be used by the transmitter 314 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can modulate the RF carrier with the corresponding spatial stream for transmission.

[0137] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to processing system 384.

[0138] In the uplink, processing system 384 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from UE 302. IP packets from processing system 384 can be provided to the core network. Processing system 384 is also responsible for error detection.

[0139] For convenience, UE 302, base station 304 and / or network entity 306 are in Figures 3A to 3C The blocks shown are intended to include various components that can be configured according to the various examples described herein. However, it should be understood that the blocks shown may have different functionalities in different designs.

[0140] Various components of UE 302, base station 304 and network entity 306 can communicate with each other via data buses 334, 382 and 392 respectively. Figures 3A to 3C Components can be implemented in various ways. In some implementations, Figures 3A to 3C The components can be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functions represented by blocks 310 to 346 can be implemented by the processor and memory components of UE 302 (e.g., through the execution of appropriate code and / or through the appropriate configuration of the processor components). Similarly, some or all of the functions represented by blocks 350 to 388 can be implemented by the processor and memory components of base station 304 (e.g., through the execution of appropriate code and / or through the appropriate configuration of the processor components). Furthermore, some or all of the functions represented by blocks 390 to 398 can be implemented by the processor and memory components of network entity 306 (e.g., through the execution of appropriate code and / or through the appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE", "by the base station", "by the positioning entity", etc. However, as will be understood, such operations, actions and / or functions can actually be performed by specific components or combinations of components of the UE, base station, positioning entity, etc., such as processing systems 332, 384, 394, transceivers 310, 320, 350 and 360, memory components 340, 386 and 396, RF sensing components 342, 388 and 398, etc.

[0141] Wireless communication signals transmitted between the UE and the base station (e.g., RF signals configured to carry OFDM symbols) can be reused for environmental sensing (also known as "RF sensing" or "radar"). Environmental sensing using wireless communication signals can be viewed as a consumer-grade radar with advanced detection capabilities, among others, enabling contactless / device-free interaction with the device / system. The wireless communication signals can be cellular communication signals, such as LTE or NR signals, WLAN signals, etc. As a specific example, the wireless communication signal can be an OFDM waveform used in LTE and NR. High-frequency communication signals (such as mmWRF signals) are particularly advantageous for use as radar signals because the higher frequency provides at least more accurate range (distance) detection.

[0142] Generally speaking, there are different types of radar, especially monostation and bistation radar. Figure 4A and Figure 4B Two of these different types of radar are shown. Specifically, Figure 4A Figure 400 shows a single-station radar scenario, and Figure 4B Figure 430 shows a bistatic radar scenario. Figure 4A In this configuration, base station 402 can be configured for full-duplex operation, and therefore the transmitter (Tx) and receiver (Rx) are located in the same location. For example, the transmitted radio signal 406 can be reflected by a target object (such as building 404), and the receiver on base station 402 is configured to receive and measure the reflected beam 408. This is a typical use case for conventional or traditional radar. Figure 4B In this example, base station 405 can be configured as a transmitter (Tx), and UE 432 can be configured as a receiver (Rx). In this example, the transmitter and receiver are not located in the same place; that is, they are separate. Base station 405 can be configured to transmit a beam, such as a full downlink RF signal 406 that can be received by UE 432. A portion of the RF signal 406 can be reflected or refracted by building 404, and UE 432 can receive the reflected signal 434. This is a typical use case for RF sensing based on wireless communication (e.g., WiFi-based, LTE-based, NR-based). Note that although... Figure 4B The diagram illustrates the use of downlink RF signal 406 as an RF sensing signal, but uplink RF signal can also be used for RF sensing. In the downlink scenario, as shown, the transmitter is base station 405 and the receiver is UE 432, while in the uplink scenario, the transmitter is UE and the receiver is base station.

[0143] For more detailed information, please refer to [link / reference]. Figure 4BBase station 405 sends an RF sensing signal (e.g., PRS) to UE 432, but some of the RF sensing signal will be reflected to a target object, such as building 404. UE 404 can measure the ToA of the RF signal 406 received directly from the base station and the ToA of the reflected signal 434 reflected from the target object (e.g., building 404).

[0144] Base station 405 can be configured to transmit a single RF signal 406 or multiple RF signals to a receiver (e.g., UE 432). However, due to the propagation characteristics of RF signals through multipath channels, UE 432 can receive multiple RF signals corresponding to each transmitted RF signal. Each path can be associated with a cluster of one or more channel taps. Typically, the time when the receiver detects the first cluster of channel taps is considered to be the ToA of the RF signal on the line-of-sight (LOS) path (i.e., the shortest path between the transmitter and receiver). Subsequent clusters of channel taps are considered to have been reflected from objects between the transmitter and receiver and therefore have followed a non-line-of-sight (NLOS) path between the transmitter and receiver.

[0145] Therefore, return to the reference. Figure 4B RF signal 406 follows the LOS path between base station 405 and UE 432, and reflected signal 434 represents an RF sensing signal that follows the NLOS path between base station 405 and UE 432 due to reflection from building 404 (or another target object). Base station 405 may have transmitted multiple RF sensing signals ( Figure 4B (Not shown in the image), some of these signals follow the LOS path and others follow the NLOS path. Alternatively, base station 405 may have transmitted a single RF sensing signal with a sufficiently wide beam such that a portion of the RF sensing signal follows the LOS path and a portion follows the NLOS path.

[0146] Based on the difference between the ToA of the LOS path, the ToB of the NLOS path, and the speed of light, UE 432 can determine the distance to building 404. Additionally, if UE 432 is capable of receiving beamforming, it can determine the approximate direction to building 404 as the direction of the reflected signal 434, which is the received RF sensing signal following the NLOS path. UE 432 can then optionally report this information to transmitting base station 405, an application server associated with the core network, an external client, a third-party application, or some other entity. Alternatively, UE 432 can report the ToA measurement to base station 405 or other entities, and base station 405 can determine the distance to the target object and, optionally, the direction to the target object.

[0147] Note that if the RF sensing signal is an uplink RF signal sent from UE 432 to base station 405, then base station 405 will perform object detection based on the uplink RF signal, just as UE 432 does based on the downlink RF signal.

[0148] refer to Figure 5 Example graph 500 illustrates the RF channel response over time at a receiver (e.g., either the UE or a base station described herein). Figure 5 In the example, the receiver receives multiple (four) channel tap clusters. Each channel tap represents the multipath followed by the RF signal between the transmitter (e.g., either the UE or the base station described herein) and the receiver. That is, the channel tap represents the arrival of the RF signal on the multipath. Each channel tap cluster indicates that the corresponding multipath follows substantially the same path. Different clusters may exist because the RF signal is transmitted on different transmit beams (and therefore at different angles), or because of the propagation characteristics of the RF signal (which may follow a wide range of different paths due to reflections) or both.

[0149] exist Figure 5 Under the channel shown, the receiver receives the first cluster of two RF signals from the channel tap at time T1, the second cluster of five RF signals from the channel tap at time T2, the third cluster of five RF signals from the channel tap at time T3, and the fourth cluster of four RF signals from the channel tap at time T4. Figure 5 In the example, since the first cluster of RF signals arrives first at time T1, it is assumed to be a LOS data stream (i.e., a data stream arriving via LOS or the shortest path), and can correspond to Figure 4B The LOS path shown is (e.g., RF signal 406). The third cluster at time T3 consists of the strongest RF signal and can correspond to... Figure 4B The NLOS path shown (e.g., reflected signal 434). Note that, although... Figure 5 Clusters with two to five channel taps are shown, but it should be understood that these clusters may have more or fewer channel taps than the number shown.

[0150] refer to Figure 6This illustrates an example single-target beam management use case 600 for bi-site radio frequency sensing. Use case 600 includes a base station 602, such as a 5G NR gNB configured to transmit multiple beamforming signals along different azimuth and / or elevation angles, and a UE 610 configured to utilize receive beamforming to improve signal gain based on angle of arrival. Base station 602 can be configured to generate N different reference beams and various azimuth, elevation, and / or beamwidths. In one example, the beams transmitted by base station 602 can be based on SS blocks, CSI-RS, TRS, or PRS resource sets. Other sensing and tracking reference signals can also be used. UE 610 can be configured to utilize phase shifters and other software and hardware techniques to generate receive beams, such as a first receive beam 612, a second receive beam 614, and a third receive beam 616. UE 610 can also be configured to utilize beamforming of the transmitted beams. Base station 602 can transmit a first reference signal 604 in the direction of a target object (such as building 404). This first reference signal 604 can be reflected, and UE 610 can receive the reflected signal 606 using a first receive beam 612. The reflected signal 606 represents the NLOS path from the first reference signal 604 to UE 610. Base station 602 also transmits a second reference signal 608 on a second beam. In one example, the second reference signal 608 can be quasi-collinear (QCLed) with the first reference signal 604. UE 610 receives the second reference signal 608 using a second receive beam 614. The second reference signal 608 is the LOS path to UE 610.

[0151] In operation, UE 610 can be configured to report the channel response of each of the first and second reference signals 604, 608 to base station 602 or another serving cell, and base station 602 can be configured to manage transmit and receive beam pairs for object sensing. For example, base station 602 can be configured to provide UE 610 with transmit and receive beam identification information to track objects such as building 404. The beam identification information can be a Transmission Configuration Indicator (TCI) sent in a DCI message, which includes configurations such as the QCL relationship between the transmit and receive beams.

[0152] refer to Figure 7 For further reference Figure 6 This illustrates an example multi-objective use case 700 for dual-station RF sensing. Use case 700 is extended by including a second objective. Figure 6The single target use case 600. By way of example and not limitation, the second target could be a second building 704. The number and nature of targets can vary depending on the environment and radio sensing application. In use case 700, base station 602 transmits a third reference signal 702 reflected by the second building 704, and the resulting reflected signal 708 is detected by the second receive beam 614 of UE 610. UE 610 can report the channel response of the third reference signal 702 by way of an indication that a measurement was obtained using the second receive beam 614. Base station 602 is configured to manage the beam pair associated with the second target (i.e., the third reference signal 702 and the second receive signal 614). Additional targets and corresponding beam pairs can also be managed by base station 602. Base station 602 can be configured to track one or more of the targets, and thus can provide the UE 610 with the corresponding beam pair information as the QCL / TCI of the corresponding target.

[0153] refer to Figure 8A An example scan phase 800 with bistatic RF sensing is shown. Base station 802 is an example of base station 304 and is configured to transmit multiple beamforming reference signals with varying azimuth, elevation, and / or beamwidth. The reference signals may be SS blocks, CSI-RS, TRS, PRS, or sensing scan reference signals (SSRS) configured for RF sensing applications. UE 810 is an example of UE 302 and may be configured to perform receive beam scanning along different azimuth, elevation, and / or beamwidths relative to the UE 810's orientation. In operation, base station 802 may transmit one or more of the reference signals sequentially (i.e., beam scanning), and UE 810 is configured to perform beam scanning with different receive beams. Scan phase 800 may be used to initially detect potential objects tracked via RF sensing. For example, a first reference signal 804 may be reflected by a first object 820a, and a first reflected reference signal 804a may be detected by UE 810. UE 810 can cycle through different receive beams, such as the first receive beam 812, the second receive beam 814, and the third receive beam 816. For example... Figure 8A As shown, the first reflected reference signal 804a can be received using the first receiving beam 812. The UE 810 can also detect the second reference signal 805 via the LOS path using the second receiving beam 814. Beam scanning on the base station 802 can generate a third reference signal 806, which is reflected from the second object 820b, and the third reflected reference signal 806a is received by the UE 810 on the third receiving beam 816.

[0154] In an embodiment, UE 810 can be configured to detect a target based on the RSRP of the received signal. For example, UE 810 can report RSRP values ​​associated with the first reference signal 804 and the third reference signal 806 that are higher than a threshold. The threshold can be a fixed value or can be scaled based on the RSRP of a LOS signal (such as the second reference signal 805). UE 810 is configured to report one or more channel measurements (e.g., RSRP, RSRQ, SINR) associated with the received reference signals to base station 802 or other network nodes. Measurements obtained during the scan phase 800 can be used in the subsequent tracking phase.

[0155] refer to Figure 8B For further reference Figure 8A An example tracking stage 850 with dual-station RF sensing is shown. (Continued) Figure 8A For example, base station 802 (or another network node in communication system 100) can determine to track one or more objects detected during scan phase 800. For instance, base station 802 may choose to track a first object 820a and will send beam configuration information to UE 810 to enable UE 810 to track the first object 820a. The beam configuration information may include reference signal information and receive beam configuration information for UE 810. Base station 802 may utilize a sense tracking reference signal (STRS) based on a first reference signal 804 to track or refine measurements associated with the first object. In one example, the STRS may be QCLed with the corresponding SSRS (i.e., the first reference signal 804). SS blocks, CSI-RS, TRS, and PRS can be used as STRS. Other reference signals may also be developed and used as STRS. The beam configuration information sent to UE 810 may be transmitted via RRC, Medium Access Control Element (MAC-CE), DCI, or other signaling protocols. After receiving the beam configuration information, UE 810 can, for example, use the first receive beam 812 and STRS to detect the first object 820a.

[0156] Base station 802 can be configured to track multiple targets based on the number of reference signals that base station 802 can generate. In one embodiment, base station 802 can be configured to track one object for each reference signal. For example, base station 802 can track a second object 820b by generating a second SRS based on a third reference signal 806. The beam configuration information sent to UE 810 may include beam parameters of the second SRS and corresponding received beam information (e.g., a third received beam 816) provided by UE 810 during scan phase 800. Therefore, UE 810 can be configured to track a first object 820a and a second object 820b. Up to the number of additional objects generated by base station 802 can be tracked.

[0157] refer to Figure 8C For further reference Figure 8A and Figure 8B An example message flow 870 for beam-related target tracking with bi-station RF sensing beam management is illustrated. Message flow 870 represents at least a portion of the signals exchanged between base station 802 (e.g., gNB) and UE 810 during scan phase 800 and track phase 850. Base station 802 transmits one or more DL scan sensing reference signals (SSRS) 872, such as a first reference signal 804, a second reference signal 805, and a third reference signal 806. SSRS 872 may be an SS block, CSI-RS, TRS, PRS, or other existing or future reference signals configured for channel sounding or specifically for RF sensing measurements. UE 810 is configured to transmit a beam information report 874 based on measurements associated with the received SSRS. The beam information report may include one or more of RSRP, RSRQ, or SINR values, for example, associated with SSRS exceeding a threshold. Beam information report 874 may also include received beam information associated with SSRS exceeding a threshold. Beam Information Report 874 can be sent via RRC message or in other UL signaling.

[0158] In phase 876, base station 802 is configured to select a target for tracking based at least in part on beam information report 874 sent by UE 810. The selection of the object for tracking may be based on upper-layer configuration parameters or other operational considerations. For example, anticipated loss / degradation of the UE's LOS path (e.g., due to extreme weather) may cause the network to need to track static objects. Furthermore, Figures 8A to 8C The example depicts a single base station and a single UE, with additional base stations and UEs that can be used to scan and track objects. SSRS can be associated with a specific base station and beam (e.g., a TRP-ID with a PRS-ID), and the network can be configured to aggregate beam information reports for beams associated with other base stations and multiple UEs.

[0159] During the tracking phase 850, base station 802 may transmit tracking configuration information 878 for the targets selected in phase 876. The tracking configuration information may include a Sensing Tracking Reference Signal (STRS) associated with each of the selected targets. The STRS may be QCLed with the corresponding SSRS 872 transmitted in the scanning phase 800. The tracking configuration information 878 may include received beam information based on beam information report 874. The tracking configuration information 878 may be provided via RRC, MAC-CE, DCI, or other network signaling. The tracking configuration information 878 may be UE-specific or target-specific. Base station 802 transmits DL Sensing Tracking Reference Signals (STRS) 880 based on the targets selected in phase 876. In one example, each target may be associated with a STRS 880. The STRS may be an SS block, CSI-RS, TRS, PRS, or other current and future reference signals developed for RF sensing applications.

[0160] In phase 882, UE 810 is configured to track the target associated with STRS 880. For example, UE 810 can use a first receive beam 812 to receive the STRS based on a first reference signal 804 to detect a first object 820a. If a second object 820b is also selected in phase 876, UE 810 can be configured to use a third receive beam 816 to receive a second STRS (which can be QCLed with a third reference signal 806). In one example, STRS 880 can be periodic or aperiodic (e.g., event-driven).

[0161] refer to Figure 9A This illustrates an example use case 900 for multi-target detection using dual-station RF sensing. Figures 8A to 8CIn contrast to the example in the example, where each target can be identified by a single reference signal, use case 900 highlights a scenario where multiple targets are detected using a single reference signal. For example, base station 902 is an example of base station 304 and is configured to transmit multiple beamformed reference signals with varying angles, elevation angles, and / or beamwidths. The first reference signal 904 can be configured as SSRS and / or STRS and is received by UE 910 via multiple paths. For example, the first reference signal 904 can be reflected from a first target 920a and received by a first receiving beam 912. The first reference signal 904 can be received via a LOS path via a second receiving beam 914. The first reference signal 904 can also be reflected from a second target 920b and received via a third receiving beam 916. Since the first and second targets 920a-b are associated with the same reference signal, the first reference signal 904 is insufficient to uniquely identify each target. In this use case, UE 910 can be configured to assign specific target identifiers to distinguish targets. UE 910 can be configured to distinguish targets based on different receiving beams. For example, the RSRP of the first reference signal 904 may exceed a threshold when received on the first receiving beam 912 and when received on the third receiving beam 916. The UE 910 may assign a first identifier (e.g., target 1) to the first target 920a and a second identifier (e.g., target 2) to the second target 920b. The target identifiers and corresponding reference signal identifier information may be reported to the base station 902.

[0162] refer to Figure 9B For further reference Figure 9AThis illustrates an example message flow 950 for multi-target bistation RF sensing beam management. Message flow 950 represents at least a portion of the signals exchanged between base station 902 (e.g., gNB) and UE 910 during scan phase 800 and track phase 850. Base station 902 transmits one or more DL scan sensing reference signals (SSRS) 952, such as a first reference signal 904. SSRS 952 may be an SS block, CSI-RS, TRP, PRS, or other existing or future reference signals configured for channel sounding or specifically for RF sensing measurements. UE 910 is configured to transmit a beam and target information report 954 based on measurements associated with the received SSRS. If multiple targets are detected, the beam and target information report 954 may include one or more of RSRP, RSRQ, or SINR values, such as those associated with SSRS exceeding a threshold, as well as target identification information. For example, UE 910 can generate target information based on objects detected by different receiving beams (such as a first target 920a detected by a first receiving beam 912 and a second target 920b detected by a third receiving beam 916). In one example, UE 910 can include receiving beam identification information in the beam and target information report 954, and base station 902 can be configured to assign different target identification values ​​based on the receiving beam identification information. The beam and target information report 954 can be sent via RRC messaging or within other UL signaling.

[0163] In phase 956, base station 902 is configured to select a target for tracking based at least in part on beam and target information report 954 transmitted by UE 910. The selection of the object for tracking may be based on upper-layer configuration parameters or other operational considerations. Furthermore, Figure 9A The example depicts a single base station and a single UE, with additional base stations and UEs that can be used to scan and track objects. SSRS can be associated with a specific base station and beam (e.g., TRP-ID with PRS-ID), and received beam and / or target identification values ​​can be associated with reporting UEs (e.g., UE identification information). The network can be configured to aggregate beam and target information reports for beams associated with other base stations and multiple UEs.

[0164] During the tracking phase 850, base station 902 may transmit tracking and target configuration information 958 for the target selected in phase 956. The tracking and target configuration information 958 may include a sensing tracking reference signal (STRS) associated with the selected target. The STRS may be QCLed with the corresponding SSRS 952 transmitted in the scanning phase 800. The tracking and target configuration information 958 may include target identification information based on beam and target information report 954. The tracking and target configuration information 958 may be provided via RRC, MAC-CE, DCI, or other network signaling. The tracking and target configuration information 958 may be specific to UE 910, or specific to one or more of the selected targets. Base station 902 transmits a DL sensing tracking reference signal (STRS) 960 based on the target selected in phase 956. The STRS 960 may be an SS block, CSI-RS, TRS, PRS, or other current and future reference signals developed for RF sensing applications.

[0165] In phase 962, UE 910 is configured to track targets associated with STRS 960. For example, UE 910 may receive STRS based on a first reference signal 904 to detect a first target 920a and / or a second target 920b. In one example, STRS 960 may be periodic or aperiodic (e.g., event-driven).

[0166] refer to Figure 10A This illustrates an example use case 1000 for target swarm detection using dual-station RF sensing. Figures 8A to 8C Examples in and Figure 9A The use cases in the opposite way, where in Figures 8A to 8C In the example, each target can be identified by a single reference signal, and where in Figure 9AIn this use case, each target can be identified by a different receive beam. Use case 1000 highlights a scenario where multiple targets are detected using a single reference signal and a single receive beam. For example, base station 1002 is an example of base station 304 and is configured to transmit multiple beamformed reference signals with varying angles, elevation angles, and / or beamwidths. The first reference signal 1004 can be configured as SSRS and / or STRS and is received by UE 1010 via multiple paths. For example, the first reference signal 1004 can be reflected from the first target 1020a and the second target 1020b and received by the first receive beam 1012. The first reference signal 1004 can also be received via a LOS path through the second receive beam 1014. Since the first and second targets 1020a-b are associated with the same reference signal and the same receive beam, the combination of the first reference signal 1004 and the first receive beam 1012 is insufficient to uniquely identify each of the targets 1020a-b. In this use case, UE 1010 can be configured to assign target group identifiers to identify first and second targets 1020a-b as a target group. When received on the first receive beam 1012, the RSRP of the first reference signal 1004 may exceed a threshold. In one example, UE 1010 can be configured to resolve the target group into individual targets based on clusters and channel taps. UE 1010 can assign target group identifiers (e.g., target group 1) to the first target 1020a and the second target 1020b. The target group identifiers and corresponding reference signal identifier information can be reported to base station 1002.

[0167] refer to Figure 10B For further reference Figure 10AExample message flow 1050 for target group bi-site radio frequency sensing beam management is shown. Message flow 1050 represents at least a portion of the signals exchanged between base station 1002 (e.g., gNB) and UE 1010 during scan phase 800 and track phase 850. Base station 1002 transmits one or more DL scan sensing reference signals (SSRS) 1052, such as a first reference signal 1004. SSRS 1052 may be an SS block, CSI-RS, TRP, PRS, or other existing or future reference signals as previously described. UE 1010 is configured to transmit beam and target group information report 1054 based on measurements associated with the received SSRS. Beam and target group information report 1054 may include one or more of RSRP, RSRQ, or SINR values, such as those associated with SSRS exceeding a threshold, and target group identification information. For example, UE 1010 can generate target group information based on objects detected by a single received beam (such as first and second targets 1020a-b detected by the first received beam 1012). In one example, UE 1010 may include received beam identification information in the beam and target group information report 1054, and base station 1002 may be configured to assign different target group identification values ​​based on the received beam identification information. The beam and target group information report 1054 may be sent via RRC messaging or within other UL signaling.

[0168] In phase 1056, base station 1002 is configured to select a target for tracking based at least in part on the beam and target group information report 1054 transmitted by UE 1010. The selection of the object for tracking may be based on upper-layer configuration parameters or other operational considerations. Furthermore, Figure 10A The example depicts a single base station and a single UE, with additional base stations and UEs that can be used to scan and track target groups. SSRS can be associated with a specific base station and beam (e.g., TRP-ID with PRS-ID), and received beam and / or target group identification values ​​can be associated with reporting UEs (e.g., UE identification information). The network can be configured to aggregate reports of beam and target group information arriving at beams associated with other base stations and multiple UEs.

[0169] During the tracking phase 850, base station 1002 may transmit tracking and target group configuration information 1058 for the target selected in phase 1056. The tracking and target group configuration information 1058 may include a sensing tracking reference signal (STRS) associated with the selected target. The STRS may be QCLed with the corresponding SSRS 1052 transmitted in the scanning phase 800. The tracking and target group configuration information 1058 may include target group identification information based on beam and target group information report 1054. The tracking and target group configuration information 1058 may be provided via RRC, MAC-CE, DCI, or other network signaling. The tracking and target group configuration information 1058 may be specific to UE 1010 or specific to one or more of the selected target groups. Base station 1002 transmits a DL sensing tracking reference signal (STRS) 960 based on the target or target group selected in phase 1056. The STRS 1060 may be an SS block, CSI-RS, TRS, PRS, or other current and future reference signals developed for RF sensing applications.

[0170] In phase 1062, UE 1010 is configured to track a target group associated with STRS 1060. For example, UE 1010 may receive a STRS based on a first reference signal 1004 to detect a target group including a first target 1020a and a second target 1020b. In one example, STRS 1060 may be periodic or aperiodic (e.g., event-driven).

[0171] refer to Figure 11A This illustrates an example use case 1100 for single-sided beam management in bi-station RF sensing. Figures 8A to 8C In contrast to the examples in the example 304, where each target can be identified by a single reference signal, use case 1100 highlights a scenario where multiple target groups are detected using a single reference information. For example, base station 1102 is an example of base station 304 and is configured to transmit multiple beamforming reference signals with varying angles, elevation angles, and / or beamwidths. The first reference signal 1104 can be configured as SSRS and / or STRS and is received by UE 1110 via multiple paths. For example, the first reference signal 1104 can be reflected from a first target 1105a and a second target 1105b and received by a first receiving beam 1112. The first reference signal 1104 can be received by a second receiving beam 1114 via a LOS path and via an NLOS path including reflections from a third target 1106. The first reference signal 1104 can also be reflected from a fourth target 1108 and received via a third receiving beam 1116. Since... Figure 11AAll targets are associated with the same reference signal (i.e., the first reference signal 1104), so the first reference signal 1104 is insufficient to uniquely identify each target. In this use case, the UE 1110 can be configured to assign explicit target group identifiers to distinguish target groups. In one embodiment, target groups can be based on receive beams 1112, 1114, and 1116. For example, the first target group includes first target 1105a and second target 1105b, the second target group includes third target 1106, and the third target group includes fourth target 1108. The relative positions and number of objects in the target groups are merely examples and not limitations. The UE 1110 can utilize wider or narrower receive beams and can be configured to distinguish targets based on different receive beams and corresponding reference signal measurements. For example, the RSRP of the first reference signal 1104 may exceed a threshold when received on the first receive beam 1112, the second receive beam 1114, and the third receive beam 1116. Figure 11A As depicted, the first reference signal 1104 is not detected on the fourth receive beam 1118 (or the RSRP is below a threshold). The UE 1110 can assign a first target group identifier (e.g., target group 1) to the first target 1105a and the second target 1105b, a second target group identifier (e.g., target group 2) to target 1106, and a third target group identifier (e.g., target group 3) to the fourth target 1108. The target group identifier and the corresponding reference signal identifier information can be reported to the base station 1102. In one embodiment, the UE 1110 can be configured to provide the RSRP value and the indication of the corresponding receive beam to the base station 1102, and the base station 1102 (or other network node) can be configured to assign the target group identifier.

[0172] refer to Figure 11B For further reference Figure 11AExample message flow 1150 for single-sided bi-station RF sensing beam management is shown. Message flow 1150 represents at least a portion of the signals exchanged between base station 1102 (e.g., gNB) and UE 1110 during scan phase 800 and track phase 850. Base station 1102 transmits one or more DL scan sensing reference signals (DLSSRS) 1152, such as a first reference signal 1104. DL SSRS 1152 may be SS blocks, CSI-RS, TRS, PRS, or other existing or future reference signals configured for channel sounding or specifically for RF sensing measurements. UE 1110 is configured to transmit a beam and target group information report 1154 based on measurements associated with the received DL SSRS. Beam and target group information report 1154 may include one or more of RSRP, RSRQ, or SINR values, for example, associated with DL SSRS exceeding a threshold. If multiple target groups are detected, beam and target group information report 1154 may also include multiple target group identification values. For example, UE 1110 can generate target group identification values ​​based on objects detected by different receive beams, such as a first target group including first and second targets 1105a-b detected by a first receive beam 1112, a second target group including a third target 1106 detected by a second receive beam 1114, and a third target group including a fourth target 1108 detected by a third receive beam 1116. In one example, UE 1110 can include receive beam identification information in a beam and target group information report 1154. Base station 1102 can be configured to assign different target group identification values ​​based on the receive beam identification information. Beam and target group information report 1154 can be sent via RRC messaging or within other UL signaling.

[0173] In phase 1156, base station 1102 is configured to select one or more target groups for tracking, at least in part, based on beam and target group information report 1154 transmitted by UE 1110. The selection of target groups for tracking may be based on upper-layer configuration parameters or other operational considerations. Furthermore, although Figure 11A The example depicts a single base station and a single UE, but additional base stations and UEs can be used to scan and track objects. SSRS can be associated with a specific base station and beam (e.g., TRP-ID with PRS-ID), and received beam and / or target group identification values ​​can be associated with reporting UEs (e.g., UE identification information). The network can be configured to aggregate beam and target group information reports for beams associated with other base stations and multiple UEs.

[0174] In tracking phase 850, base station 1102 may send tracking and target group configuration information 1158 for the target group selected in phase 1156. Tracking and target group configuration information 1156 may include a sense tracking reference signal (STRS) associated with the selected target group. The STRS may be QCLed with the corresponding SSRS sent in scanning phase 800. Tracking and target group configuration information 1158 may include target group identification information based on beam and target group information report 1154. Tracking and target group configuration information 1158 may be provided via RRC, MAC-CE, DCI, or other network signaling. Tracking and target group configuration information 1158 may be specific to UE 1110, or specific to one or more of the selected target groups. In operation, when multiple target groups are associated with signals STRS (e.g., ... Figure 11B When associated with the STRS#A depicted in the diagram, the tracking and target group configuration information 1158 indicates that the number of times the STRS is repeated is equal to the number of target groups to be tracked. The tracking and target group configuration information 1158 may also include the repetition pattern (e.g., period, time offset, interval, etc.) for repeating the STRS and the corresponding target group identifier for the target groups to be tracked.

[0175] Base station 1102 is configured to transmit DL sensing tracking reference signals (STRS) based on the target group selected in phase 1156 and the repetition pattern in tracking and target group configuration information 1158. For example, a first transmission 1160a of DL STRS#A enables UE 1110 to track a first target group in phase 1162a, a second transmission 1160b of DL STRS#A enables UE 1110 to track a second target group in phase 1162b, and a third transmission 1160c enables UE 1110 to track a third target group. STRS 1160a-c can be SS blocks, CSI-RS, TRS, PRS, or other current and future reference signals developed for RF sensing applications. Tracking at phases 1162a-c may include obtaining one or more reference signal measurements, such as RSRP, RSRQ, or SINR values ​​associated with the DL STRS. STRS 1160a-c can be QCLed with SSRS 1152, which is the basis for beam and target group information reporting 1154. In one example, the STRS1160a-c can be event-driven based on a tracing request received from UE 1110 or another network node.

[0176] Figure 12 A multi-UE tracking scenario 1200 is illustrated according to aspects of this disclosure. (Reference) Figure 12BS 1202 is an example of BS 304 and is configured to transmit multiple beamforming reference signals with varying angles, elevation angles, and / or beamwidths. The first reference signal 1204 may be configured as SSRS and / or STRS and may be transmitted via a first transmit beam 1206 and received by UE 1210 (“UE A”) via multiple paths. For example, the first reference signal 1204 may be reflected (or deflected) from a first target 1220a (“A-1”) and received on a first receive beam 1212 via a deflection signal 1208. The first reference signal 1214 may further be reflected (or deflected) from a second target 1220b (“A-2”) and received on a second receive beam 1216 via a deflection signal 1214.

[0177] refer to Figure 12 The second reference signal 1222 can be configured as SSRS and / or STRS, and can be transmitted via the second transmission beam 1224 and received by UE 1240 (“UE B”) via at least one path. For example, the second reference signal 1222 can be reflected (or deflected) from the third target 1220c (“B-1”) and received on the receiving beam 1228 via the deflection signal 1226.

[0178] Figure 13 A bi-station radio frequency sensing beam management process 1300 according to aspects of this disclosure is illustrated. Figure 13 Process 1300 is a multi-user (or multi-UE) process, in which the BS configured as BS 304 performs bi-site radio frequency sensing beam management on behalf of UEs A and B, wherein each UE can be configured as UE 302. For example, UE A can correspond to Figure 12 UE 1210, and UE B can correspond to Figure 12 UE 1240 in the above reference. Figure 12 As shown, targets 1220a-1220c (or A-1, A-2 and B-1 respectively) are each different targets (or different groups of targets).

[0179] refer to Figure 13 The scanning phase 1302 is performed, the details of which are omitted and can be in any combination (e.g., Figure 8C The 800, etc.) correspond to any of the scanning phases described above. As a result of scanning phase 1302, it is assumed that targets A-1, A-2, and B-1 are identified by BS 304 and selected for tracking. In the following text, A-1, A-2, and B-1 are described as targets, although it should be understood that any of A-1, A-2, and B-1 may alternatively correspond to the targets mentioned above. Figures 9A to 11B The target group described.

[0180] refer to Figure 13 Following the scanning phase 1302, the tracking phase 1304 is executed. At 1306, BS 304 sends tracking configuration information for targets A-1 and A-2 to UEA via unicast. The tracking configuration information may indicate the configuration of the STRS for the identified targets, i.e., A-1 and A-2. In one example, the tracking configuration information 1306 may indicate that the number of times the STRS is repeated is equal to the number of targets to be tracked. For example, in the case of multiple targets or target groups, the tracking configuration information 1306 may include the repetition pattern (e.g., period, time offset, interval, etc.) for repeating the STRS and the corresponding target (or target group) identifier for the target (or target group) to be tracked. The tracking configuration information 1306 may be provided via RRC, MAC-CE, DCI, or other network signaling. The first transmission 1308 of DL STRS#A enables UE A to track target A-1 at 1310, and the second transmission 1312 of DL STRS#A enables UE A to track target A-2 at 1314. STRS 1308 and 1312 can be SS blocks, CSI-RS, TRS, PRS, or other current and future reference signals developed for RF sensing applications. Tracking at 1310 and 1314 may include acquiring one or more reference signal measurements, such as RSRP, RSRQ, or SINR values ​​associated with the DL STRS. In some designs, STRS 1308 and 1312 may be QCLed with the SSRS during the scan phase 1302. In one example, STRS 1308 and 1312 may be event-driven based on a tracking request received from UE A or another network node.

[0181] refer to Figure 13At 1316, BS 304 also sends tracking configuration information for target B-1 to UE B via unicast. The tracking configuration information may indicate the configuration of the STRS for the identified target, i.e., B-1. In one example, tracking configuration information 1316 may indicate that the number of times the STRS is repeated equals the number of targets to be tracked. For example, in the case of multiple targets or target groups, tracking configuration information 1316 may include the repetition pattern (e.g., period, time offset, interval, etc.) for repeating the STRS and the corresponding target (or target group) identifier for the target (or target group) to be tracked. Tracking configuration information 1316 may be provided via RRC, MAC-CE, DCI, or other network signaling. A single transmission 1318 of DL STRS#B enables UE B to track target B-1 at 1320. STRS 1318 may include SS blocks, CSI-RS, TRS, PRS, or other current and future reference signals developed for RF sensing applications. Tracking at 1320 may include acquiring one or more reference signal measurements, such as RSRP, RSRQ, or SINR values ​​associated with the DL STRS. In some designs, the STRS1318 may be QCLed with the SSRS during the scan phase 1302. In one example, the STRS1318 may be event-driven based on a tracking request received from UE B or another network node.

[0182] Figure 14 A multi-UE tracking scenario 1400 according to another aspect of this disclosure is illustrated. (Reference) Figure 14 BS1402 is an example of BS 304 and is configured to transmit multiple beamforming reference signals with varying angles, elevation angles, and / or beamwidths. Reference signals 1404 can be configured as SSRS and / or STRS and can be transmitted via transmit beam 1406 and received by UE 1410 (“UE A”) via multiple paths. For example, reference signal 1404 can be reflected (or deflected) from a first target 1420a (“A-1”) and received on a first receive beam 1412 via deflection signal 1408. Reference signal 1404 can also be reflected (or deflected) from a second target 140b (identified as “A-2” by UE 1410) and received at UE 1410 on a second receive beam 1416 via deflection signal 1414. Reference signal 1404 may be further reflected (or deflected) from second target 1420b (identified as “B-1” by UE 1440) and received at UE 1440 (“UE B”) on third receive beam 1424 via deflection signal 1422.

[0183] exist Figure 14 In the scenario, it can be achieved Figure 13In process 1300, BS 304 fails to recognize that targets A-2 and B1 are actually the same target. Embodiments of this disclosure address aspects where SRS is multicast to multiple UEs, allowing multiple UEs to perform target tracking of corresponding targets based on the multicast SRS. These embodiments can provide various technical advantages, such as fewer SRS transmissions, which can reduce overhead and improve target tracking speed or efficiency. These embodiments can provide specific technical advantages where UEs to which SRS is multicast are tracking the same object, regardless of whether the UE or BS recognizes the same target being tracked.

[0184] Figure 15 An exemplary process 1500 for wireless communication according to an aspect of this disclosure is shown. In one aspect, process 1500 may be performed by a BS (such as BS 304).

[0185] At 1510, BS 304 (e.g., receiver 352, receiver 362, etc.) receives information from the first UE related to a first target, which is associated with a deflection point of the transmission beam from the base station to the first UE. For example, the information received at 1510 may include a scan signal report identifying one or more targets detected at the first UE. The scan signal report may include RSRP information associated with one or more SSRSs in some designs, multiple target IDs, etc. In some designs, the first target may be a single target, while in others, the first target may represent a group of targets.

[0186] At 1520, BS 304 (e.g., receiver 352, receiver 362, etc.) receives information from the second UE associated with a second target, which is associated with a deflection point of the transmission beam from the base station to the first UE (e.g., the same or different deflection point as the first target). For example, the information received at 1520 may include a scan signal report identifying one or more targets detected at the second UE. The scan signal report may include RSRP information associated with one or more SSRSs in some designs, multiple target IDs, etc. In some designs, the second target may be a single target, while in others, the first target may represent a group of targets.

[0187] At 1530, BS 304 (e.g., transmitter 354, transmitter 364, etc.) sends SRS configuration information to the first and second UEs. This SRS configuration information is based on information associated with the first and second targets (e.g., the first and second targets can be determined to be the same target, and the SRS configuration information can then be configured using this knowledge to target multiple UEs that have detected the common target, etc.). In some designs, the SRS configuration information is sent to the first and second UEs via unicast (e.g., a separate unicast message). In other designs, the SRS configuration information is sent to the first and second UEs via multicast (e.g., a single multicast message). In another example, the SRS configuration information can be transmitted via at least one RRC signaling, MAC-CE signaling, or DCI signaling.

[0188] At 1540, BS 304 (e.g., transmitter 354, transmitter 364, etc.) multicasts the STRS to the first and second UEs on the transmission beam according to the STRS configuration information.

[0189] Figure 16 An exemplary process 1600 for wireless communication according to an aspect of this disclosure is shown. In one aspect, process 1600 may be performed by a UE (e.g., UE 302).

[0190] At 1610, UE 302 (e.g., receiver 312, receiver 322, RF sensing component 342, sensor 344, etc.) detects a target associated with the deflection point of the transmission beam from the base station to the first UE. For example, in some designs, the detection at 1610 can be performed based on measurements of one or more SSRS.

[0191] At 1620, UE 302 (e.g., transmitter 312, transmitter 322, etc.) transmits information associated with the target. For example, the information transmitted at 1520 may include a scan signal report identifying one or more targets detected at the UE at 1610. The scan signal report may include RSRP information associated with one or more SSRSs in some designs, multiple target IDs, etc. In some designs, the target may be a single target, while in others, the target may represent a group of targets.

[0192] At 1630, UE 302 (e.g., receiver 314, receiver 324, etc.) receives SRS configuration information from the base station. This SRS configuration information is based on information associated with a target (e.g., the target can be identified as the same target detected by other UEs, and the SRS configuration information can then use this knowledge to configure itself to target multiple UEs that have detected the common target, etc.). In some designs, the SRS configuration information is received via unicast. In other designs, the SRS configuration information is received via multicast (e.g., a single multicast message directed to multiple UEs). In another example, the SRS configuration information can be transmitted via at least one RRC signaling, MAC-CE signaling, or DCI signaling.

[0193] At 1640, UE 302 (e.g., receiver 312, receiver 322, RF sensing component 342, sensor 344, etc.) receives multicast STRS on the receive beam associated with the transmit beam according to the STRS configuration information. Although in Figure 16 While not explicitly stated, UE 302 can perform target tracking based on multicast SRS. In some designs, multiple multicast SRS can be received at UE 302 for tracking individual targets and / or for redundant tracking of specific targets, as described below. Figures 17 to 18 More detailed description.

[0194] Figure 17 The aspects according to this disclosure are shown respectively. Figures 15 to 16 Example implementation of process 1500 to 1600 is shown in 1700. Figure 17 Process 1700 is a multi-user (or multi-UE) process, in which a BS configured as BS 304 performs bi-site radio frequency sensing beam management on behalf of UE A and UE B, each of UE A and UE B being configured as UE 302. For example, UE A could correspond to Figure 14 UE 1410 in the text, and UE B can correspond to Figure 14 UE 1440 in the above. As mentioned above regarding Figure 14 As described, targets A-2 and B-1 (1420b) are the same target (or target group).

[0195] refer to Figure 17 The scanning phase 1702 is performed, the details of which are omitted and can be in any combination (e.g., Figure 8CThe 800, etc.) correspond to any of the scanning stages described above. As a result of scanning stage 1702, it is assumed that targets A-1, A-2, and B-1 are identified by BS 304, and targets A-2 and B-2 are common targets. In this case, even if targets A-2 and B-1 are common targets (i.e., the same targets), it is assumed that BS 304 does not have actual knowledge that targets A-2 and B-1 correspond to common targets.

[0196] refer to Figure 17 Following the scanning phase 1702, the tracking phase 1704 is executed. At 1706, BS 304 sends tracking configuration information for targets A-1 and A-2 to UEA via unicast. The tracking configuration information may indicate the configuration of the STRS for the identified targets; that is, A-1 and A-2. In one example, the tracking configuration information 1706 may indicate that the number of times the STRS is repeated is equal to the number of targets to be tracked. For example, in the case of multiple targets or target groups, the tracking configuration information 1706 may include the repetition pattern (e.g., period, time offset, interval, etc.) for repeating the STRS and the corresponding target (or target group) identifier for the targets (or target groups) to be tracked. The tracking configuration information 1706 may be provided via RRC, MAC-CE, DCI, or other network signaling. In one example, the tracking configuration information 1706 may include UE A-specific target identifiers (A-1 and A-2).

[0197] refer to Figure 17 In step 1708, BS 304 also sends tracking configuration information for target B-1 to UE B via unicast. The tracking configuration information can indicate the configuration of the SRS for the identified target; that is, B-1. In one example, tracking configuration information 1708 can indicate that the number of times the SRS is repeated equals the number of targets to be tracked. For example, in the case of multiple targets or target groups, tracking configuration information 1716 can include the repetition pattern for repeating the SRS (e.g., period, time offset, interval, etc.) and the corresponding target (or target group) identifier for the target (or target group) to be tracked. In this case, tracking configuration information 1708 is the same as tracking configuration information 1706. Therefore, even if UE B is only tracking one target (identified as B-1 by UE B), tracking configuration information 1708 includes two SRS repetitions because UE A is tracking two targets (A-1 and A-2). Tracking configuration information 1708 can be provided via RRC, MAC-CE, DCI, or other network signaling. In one example, tracking configuration information 1708 may include a target identifier (B-1) specific to UE B, even though tracking configuration information 1706 may include a target identifier (A-2) specific to UE A for the same target (e.g., because BS 304 may not know that these targets are actually the same).

[0198] refer to Figure 17 The first multicast transmission 1710 of DL STRS#A+#B enables UE A to track target A-1 at 1712 and further enables UE B to track target B-1 at 1714. The first multicast transmission 1760 of DL STRS#A+#B enables UE A to track target A-2 at 1718 and further (optionally) enables UE B to track target B-2 at 1720. Due to redundancy, tracking at 1720 is optional (e.g., UE B may alternatively choose to skip tracking at 1720 to save power). Alternatively, UE B may perform tracking at 1720 while skipping tracking at 1714 (e.g., either tracking opportunity may be skipped to save power). STRS 1710 and 1716 may include SS blocks, CSI-RS, TRS, PRS, or other current and future reference signals developed for RF sensing applications. Tracking at 1712, 1714, 1718, and / or 1720 may include obtaining one or more reference signal measurements associated with the DL STRS, such as RSRP, RSRQ, or SINR values. In some designs, STRS 1710 and 1716 may be QCLed with the SSRS in scan phase 1702. In one example, STRS 1710 and 1716 may be event-driven based on a tracking request received from UE A or UE B or another network node.

[0199] Figure 18 Each shows another aspect according to this disclosure. Figures 15 to 16 Example implementation of process 1500 to 1600 is shown in 1800. Figure 18 Process 1800 is a multi-user (or multi-UE) process, whereby the BS configured as BS 304 performs bi-site radio frequency sensing beam management on behalf of UE A and UE B, each of which can be configured as UE 302. For example, UE A can correspond to Figure 14 UE 1410 in the text, and UE B can correspond to Figure 14 UE 1440 in the above. As mentioned above regarding Figure 14 As described, targets A-2 and B-1 (1420b) are the same target (or target group).

[0200] refer to Figure 18 The scanning phase 1802 is performed, the details of which are omitted and can be in any combination (e.g., Figure 8C (e.g., 800, etc.) corresponds to any of the scanning stages described above. As a result of scanning stage 1802, it is assumed that targets A-1, A-2, and B-1 are identified by BS 304, and targets A-2 and B-2 are common targets. Figure 17 Conversely, BS 304 assumes that targets A-2 and B-1 correspond to a common target (e.g., based on an assessment of the target's range or velocity, the target's angle relative to the transmit / receive beam or UE A and / or UE B, etc.).

[0201] refer to Figure 18 Following scanning phase 1802, tracking phase 1804 is executed. At 1806, BS 304 sends tracking configuration information for targets A-1, A-2, and B-1 via multicast to UEA and UE B. In some designs, the multicast tracking configuration information may include a single identifier for each unique target (or target group). For example, for targets associated with A-2 and B-1, the target may be identified as A-2, B-1, or some other network-assigned (or network-specific) identifier. In other designs, the multicast tracking configuration information may identify the target as associated with both A-2 and B-1, allowing each of UE A and UE B to identify the corresponding target using its own UE-specific identifier. In one example, tracking configuration information 1808 may indicate that the number of times the SRS is repeated is equal to the number of targets that will be tracked by the UE with the most targets or target groups (e.g., in this case, since UE A is tracking two targets while UE B is only tracking one). For example, in the case of multiple targets or target groups, the tracking configuration information 1808 may include the repetition pattern for repeating the SRS (e.g., period, time offset, interval, etc.) and the corresponding target (or target group) identifier for the target (or target group) to be tracked. The tracking configuration information 1808 may be provided via RRC, MAC-CE, DCI, or other network signaling. Figure 18 The period from 1810 to 1820 corresponds to Figure 17 The period from 1710 to 1720, and therefore for the sake of brevity, will not be described here.

[0202] As can be seen in the detailed description above, different features are combined together in the examples. This manner of disclosure should not be construed as having an intent to include more features than those explicitly mentioned in each clause. Rather, aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the following clauses should be considered as included in the specification, where each clause may serve as a separate example. Although each dependent clause may refer in its clause to a specific combination with one of the other clauses, the aspect of that dependent clause is not limited to that specific combination. It should be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clause, or any feature with other dependent and independent clauses. These combinations are expressly included in the aspects disclosed herein unless they are expressly stated or can be readily inferred not to be intended as a particular combination (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, aspects of a clause may be included in any other independent clause even if the clause is not directly dependent on an independent clause.

[0203] Examples of implementation methods are described in the following numbered clauses:

[0204] Clause 1. A method of operating a base station, comprising: receiving from a first user equipment (UE) information associated with a first target, the first target being associated with a deflection point of a transmission beam from the base station to the first UE; receiving from a second UE information associated with a second target, the second target being a deflection point of a transmission beam from the base station to the second UE; transmitting Sensing Tracking Reference Signal (STRS) configuration information based on the information associated with the first target and the second target to the first UE and the second UE; and multicasting the Sensing Tracking Reference Signal (STRS) to the first UE and the second UE on the transmission beam according to the SRS configuration information.

[0205] Clause 2. The method according to Clause 1, wherein the SRS configuration information is sent to the first UE and the second UE via unicast.

[0206] Clause 3. The method according to Clause 2, wherein the first target and the second target correspond to a common target, and wherein the SRS configuration information is sent without the base station knowing that the first target and the second target correspond to a common target.

[0207] Clause 4. The method according to Clause 3, wherein the first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for a common target, and wherein the second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for a common target.

[0208] Clause 5. The method according to any one of Clauses 1 to 4, wherein the SRS configuration information is sent to the first UE and the second UE via multicast.

[0209] Clause 6. The method according to Clause 5, wherein the STRS configuration information is transmitted via multicast to the first and second UEs in response to determining at the base station that the first target and the second target correspond to a common target.

[0210] Clause 7. The method described in Clause 6, wherein the multicast SRS configuration information includes a network-specific identifier for a common target.

[0211] Clause 8. The method according to any one of Clauses 1 to 7, wherein the STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0212] Clause 9. A method of operating a user equipment (UE) includes: detecting a target associated with a deflection point of a transmission beam from a base station to the UE; sending information associated with the target to the base station; receiving sensing tracking reference signal (STRS) configuration information based on the target-associated information from the base station; and receiving multicast sensing tracking reference signals (STRS) on a receive beam associated with the transmission beam according to the SRS configuration information.

[0213] Clause 10. The method according to Clause 9, wherein the SRS configuration information is received via unicast.

[0214] Clause 11. The method according to Clause 10, wherein the STRS configuration information includes a target identifier specific to the UE.

[0215] Clause 12. The method according to any one of Clauses 9 to 11, wherein the SRS configuration information is received via multicast.

[0216] Clause 13. The method according to Clause 12, wherein the multicast SRS configuration information includes a network-specific identifier of the target.

[0217] Clause 14. The method according to any one of Clauses 9 to 13, wherein the STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0218] Clause 15. A base station comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive information associated with a first target from a first user equipment (UE) via the at least one transceiver, the first target being associated with a deflection point of a transmission beam from the base station to the first UE; receive information associated with a second target from a second UE via the at least one transceiver, the second target being a deflection point of a transmission beam from the base station to the second UE; transmit sensing tracking reference signal (STRS) configuration information based on the information associated with the first target and the second target to the first UE and the second UE via the at least one transceiver; and multicast the sensing tracking reference signal (STRS) to the first UE and the second UE on the transmission beam according to the SRS configuration information.

[0219] Clause 16. The base station as described in Clause 15, wherein the STRS configuration information is sent to the first UE and the second UE via unicast.

[0220] Clause 17. The base station according to Clause 16, wherein the first target and the second target correspond to a common target, and wherein the SRS configuration information is transmitted without the base station knowing that the first target and the second target correspond to a common target.

[0221] Clause 18. The base station according to Clause 17, wherein the first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for a common target, and wherein the second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for a common target.

[0222] Clause 19. A base station according to any one of Clauses 15 to 18, wherein the SRS configuration information is sent to the first UE and the second UE via multicast.

[0223] Clause 20. The base station as described in Clause 19, wherein the STRS configuration information is transmitted via multicast to the first and second UEs in response to determining at the base station that the first target and the second target correspond to a common target.

[0224] Clause 21. The base station as described in Clause 20, wherein the multicast STRS configuration information includes a network-specific identifier for a common target.

[0225] Clause 22. A base station pursuant to any one of Clauses 15 to 21, wherein the STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0226] Clause 23. A user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: detect a target associated with a deflection point of a transmission beam from a base station to the UE; transmit information associated with the target to the base station via the at least one transceiver; receive sensing tracking reference signal (STRS) configuration information based on the target-associated information from the base station via the at least one transceiver; and receive multicast sensing tracking reference signals (STRS) on a receive beam associated with the transmission beam via the at least one transceiver according to the SRS configuration information.

[0227] Clause 24. The UE as described in Clause 23, wherein the SRS configuration information is received via unicast.

[0228] Clause 25. The UE as described in Clause 24, wherein the STRS configuration information includes a target identifier specific to the UE.

[0229] Clause 26. The UE pursuant to any one of Clauses 23 to 25, wherein the SRS configuration information is received via multicast.

[0230] Clause 27. The UE as described in Clause 26, wherein the multicast STRS configuration information includes a network-specific identifier of the target.

[0231] Clause 28. The UE pursuant to any one of Clauses 23 to 27, wherein the STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0232] Clause 29. A base station, comprising: means for receiving information associated with a first target from a first user equipment (UE), the first target being associated with a deflection point of a transmission beam from the base station to the first UE; means for receiving information associated with a second target from a second UE, the second target being a deflection point of the transmission beam from the base station to the second UE; means for transmitting Sensing Tracking Reference Signal (STRS) configuration information based on the information associated with the first target and the second target to the first UE and the second UE; and means for multicasting the Sensing Tracking Reference Signal (STRS) to the first UE and the second UE on the transmission beam according to the SRS configuration information.

[0233] Clause 30. The base station as described in Clause 29, wherein the STRS configuration information is sent to the first UE and the second UE via unicast.

[0234] Clause 31. The base station according to Clause 30, wherein the first target and the second target correspond to a common target, and wherein the SRS configuration information is transmitted without the base station knowing that the first target and the second target correspond to a common target.

[0235] Clause 32. The base station according to Clause 31, wherein the first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for a common target, and wherein the second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for a common target.

[0236] Clause 33. The base station as described in Clause 29, wherein the STRS configuration information is sent to the first UE and the second UE via multicast.

[0237] Clause 34. The base station as described in Clause 33, wherein the STRS configuration information is transmitted via multicast to the first and second UEs in response to determining at the base station that the first target and the second target correspond to a common target.

[0238] Clause 35. The base station as described in Clause 34, wherein the multicast STRS configuration information includes a network-specific identifier for a common target.

[0239] Clause 36. The base station as described in Clause 29, wherein the STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0240] Clause 37. A user equipment (UE) comprising: means for detecting a target associated with a deflection point of a transmission beam from a base station to the UE; means for transmitting information associated with the target to the base station; means for receiving sensing tracking reference signal (STRS) configuration information based on the information associated with the target from the base station; and means for receiving multicast sensing tracking reference signals (STRS) on a receiving beam associated with the transmission beam according to the SRS configuration information.

[0241] Clause 38. The UE as described in Clause 37, wherein the SRS configuration information is received via unicast.

[0242] Clause 39. The UE as described in Clause 38, wherein the STRS configuration information includes a target identifier specific to the UE.

[0243] Clause 40. The UE pursuant to any one of Clauses 37 to 39, wherein the SRS configuration information is received via multicast.

[0244] Clause 41. The UE as described in Clause 40, wherein the multicast SRS configuration information includes a network-specific identifier of the target.

[0245] Clause 42. The UE according to any one of Clauses 37 to 41, wherein the STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0246] Clause 43. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a base station, cause the base station to: receive from a first user equipment (UE) information associated with a first target, the first target being associated with a deflection point of a transmission beam from the base station to the first UE; receive from a second UE information associated with a second target, the second target being a deflection point of a transmission beam from the base station to the second UE; transmit to the first UE and the second UE sensor tracking reference signal (STRS) configuration information based on the information associated with the first target and the second target; and multicast the sensor tracking reference signal (STRS) to the first UE and the second UE on the transmission beam according to the SRS configuration information.

[0247] Clause 44. The non-transitory computer-readable medium as described in Clause 43, wherein the SRS configuration information is transmitted to the first UE and the second UE via unicast.

[0248] Clause 45. The non-transitory computer-readable medium as described in Clause 44, wherein the first target and the second target correspond to a common target, and wherein the SRS configuration information is transmitted without the base station knowing that the first target and the second target correspond to a common target.

[0249] Clause 46. The non-transitory computer-readable medium as described in Clause 45, wherein the first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for a common purpose, and wherein the second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for a common purpose.

[0250] Clause 47. A non-transitory computer-readable medium pursuant to any one of Clauses 43 to 46, wherein the SRS configuration information is transmitted to the first UE and the second UE via multicast.

[0251] Clause 48. The non-transitory computer-readable medium as described in Clause 47, wherein the SRS configuration information is transmitted via multicast to the first and second UEs in response to determining at the base station that the first target and the second target correspond to a common target.

[0252] Clause 49. The non-transitory computer-readable medium as described in Clause 48, wherein the multicast SRS configuration information includes a network-specific identifier for a common target.

[0253] Clause 50. A non-transitory computer-readable medium pursuant to any one of Clauses 43 to 49, wherein the STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Media Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0254] Clause 51. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: detect a target associated with a deflection point of a transmission beam from a base station to the UE; transmit information associated with the target to the base station; receive sensing tracking reference signal (STRS) configuration information based on the target-associated information from the base station; and receive multicast sensing tracking reference signals (STRS) on a receiving beam associated with the transmission beam according to the SRS configuration information.

[0255] Clause 52. The non-transitory computer-readable medium as described in Clause 51, wherein the SRS configuration information is received via unicast.

[0256] Clause 53. The non-transitory computer-readable medium as described in Clause 52, wherein the STRS configuration information includes a target identifier specific to the UE.

[0257] Clause 54. A non-transitory computer-readable medium pursuant to any one of Clauses 51 to 53, wherein the SRS configuration information is received via multicast.

[0258] Clause 55. The non-transitory computer-readable medium as described in Clause 54, wherein the multicast SRS configuration information includes a network-specific identifier of the target.

[0259] Clause 56. A non-transitory computer-readable medium pursuant to any one of Clauses 51 to 55, wherein the SRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Media Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

[0260] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this specification can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0261] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally according to their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art may implement the described functionality in different ways for each specific application; however, such implementation decisions should not be construed as departing from the scope of this disclosure.

[0262] The various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or performed using a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0263] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module can reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium can be a component of the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium can reside as discrete components in the user terminal.

[0264] In one or more exemplary aspects, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on or transmitted thereon on a computer-readable medium. A computer-readable medium includes computer storage media and communication media, which includes any medium that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that may be used to carry or store the required program code in the form of instructions or data structures, and is accessible to a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used in this article, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs, where disks typically copy data magnetically, while optical discs copy data optically using lasers. The combinations described above should also be included within the scope of computer-readable media.

[0265] While the foregoing disclosure illustrates illustrative aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the aspects of the disclosure described herein do not need to be performed in any particular order. Furthermore, although elements of this disclosure may be described or claimed in the singular, the plural form is contemplated unless expressly stated to be limited to the singular.

Claims

1. A method for operating a network node, comprising: Information associated with a first target is received from a first user equipment (UE), the first target being associated with a deflection point of the transmission beam from the network node to the first UE; Receive information associated with a second target from the second UE, the second target being a deflection point of the transmission beam from the network node to the second UE; Send Sensing Tracking Reference Signal (STRS) configuration information based on the information associated with the first target and the second target to the first UE and the second UE; as well as Based on the STRS configuration information, a sense tracking reference signal (STRS) is multicast to the first UE and the second UE on the transmission beam. The first objective and the second objective correspond to a common objective.

2. The method according to claim 1, wherein, The STRS configuration information is sent to the first UE and the second UE via unicast.

3. The method according to claim 2, in, The SRS configuration information is sent when the network node is unaware that the first target and the second target correspond to the common target.

4. The method according to claim 3, in, The first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for the common target, and The second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for the common target.

5. The method according to claim 1, wherein, The SRS configuration information is sent to the first UE and the second UE via multicast.

6. The method according to claim 5, wherein, The SRS configuration information is sent via multicast to the first and second UEs in response to the determination at the network node that the first target and the second target correspond to a common target.

7. The method according to claim 6, wherein, The multicast STRS configuration information includes the network-specific identifier of the public target.

8. The method according to claim 1, wherein, The STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

9. A method of operating a user equipment (UE), comprising: Detect targets associated with the deflection point of the transmission beam from the network node to the UE; Send information associated with the target to the network node; Receive sensing tracking reference signal (STRS) configuration information based on the information associated with the target from the network node; as well as Based on the STRS configuration information, a multicast sensing tracking reference signal (STRS) is received on the receiving beam associated with the transmission beam.

10. The method according to claim 9, wherein, The SRS configuration information is received via unicast.

11. The method according to claim 10, wherein, The STRS configuration information includes an identifier for the target specific to the UE.

12. The method according to claim 9, wherein, The SRS configuration information is received via multicast.

13. The method according to claim 12, wherein, The multicast STRS configuration information includes the network-specific identifier of the target.

14. The method according to claim 9, wherein, The STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

15. A network node, comprising: Memory; At least one transceiver; as well as At least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: Information associated with a first target is received from a first user equipment (UE) via the at least one transceiver, the first target being associated with a deflection point of the transmission beam from the network node to the first UE; Information associated with a second target is received from the second UE via the at least one transceiver, the second target being a deflection point of the transmission beam from the network node to the second UE; The sensor tracking reference signal (STRS) configuration information based on the information associated with the first target and the second target is transmitted to the first UE and the second UE via the at least one transceiver; as well as Based on the STRS configuration information, a sense tracking reference signal (STRS) is multicast to the first UE and the second UE on the transmission beam. The first objective and the second objective correspond to a common objective.

16. The network node according to claim 15, wherein, The STRS configuration information is sent to the first UE and the second UE via unicast.

17. The network node according to claim 16, in, The SRS configuration information is sent when the network node is unaware that the first target and the second target correspond to the common target.

18. The network node according to claim 17, in, The first SRS configuration information unicast to the first UE includes a first identifier specific to the first UE for the common target, and The second SRS configuration information unicast to the second UE includes a second identifier specific to the second UE for the common target.

19. The network node according to claim 15, wherein, The SRS configuration information is sent to the first UE and the second UE via multicast.

20. The network node according to claim 19, wherein, The SRS configuration information is sent via multicast to the first and second UEs in response to the determination at the network node that the first target and the second target correspond to a common target.

21. The network node according to claim 20, wherein, The multicast STRS configuration information includes the network-specific identifier of the public target.

22. The network node according to claim 15, wherein, The STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

23. A user equipment (UE), comprising: Memory; At least one transceiver; as well as At least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: Detect targets associated with the deflection point of the transmission beam from the network node to the UE; Information associated with the target is sent to the network node via the at least one transceiver; Receive sensing tracking reference signal (STRS) configuration information based on the information associated with the target from the network node via the at least one transceiver; as well as Based on the STRS configuration information, a multicast sensing tracking reference signal (STRS) is received via the at least one transceiver on a receive beam associated with the transmit beam.

24. The UE according to claim 23, wherein, The SRS configuration information is received via unicast.

25. The UE according to claim 24, wherein, The STRS configuration information includes an identifier for the target specific to the UE.

26. The UE according to claim 23, wherein, The SRS configuration information is received via multicast.

27. The UE according to claim 26, wherein, The multicast STRS configuration information includes the network-specific identifier of the target.

28. The UE according to claim 23, wherein, The STRS configuration information is transmitted via Radio Resource Control (RRC) signaling, Medium Access Control Command Element (MAC-CE) signaling, or Downlink Control Information (DCI) signaling.

29. An apparatus for operating a network node, comprising components for performing the method according to any one of claims 1-8.

30. An apparatus for operating a user equipment (UE), comprising components for performing the method according to any one of claims 9-14.

31. A computer-readable medium having computer instructions recorded thereon, which, when executed by a processor of a network node, cause the processor to perform the method according to any one of claims 1-8.

32. A computer-readable medium having computer instructions recorded thereon, which, when executed by a processor of a user equipment (UE), cause the processor to perform the method according to any one of claims 9-14.

33. A computer program product comprising computer instructions that, when executed by a processor of a network node, cause the processor to perform the method according to any one of claims 1-8.

34. A computer program product comprising computer instructions that, when executed by a processor of a user equipment (UE), cause the processor to perform the method according to any one of claims 9-14.

Images