Velocity estimation with radio frequency (RF) sensing
By receiving Doppler and distance information from multiple TRPs in a wireless communication system and combining it with orientation estimation, accurate measurement of object velocity was achieved, solving the interference problem in wireless communication networks and improving communication quality and resource utilization efficiency.
Patent Information
- Application Number
- CN202480023715.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-04-14
- Filing Date
- 2024-04-08
- Publication Date
- 2025-10-31
AI Technical Summary
Interference exists in wireless communication networks, especially with the increasing demand for mobile broadband access. This leads to a decline in the performance of downlink and uplink between base stations and user equipment, affecting communication quality.
By receiving Doppler information and distance sensing information from multiple transmit/receive points (TRPs), the velocity of an object is determined using Doppler measurements and angle of arrival information, and then accurate velocity estimation is performed by combining orientation estimation information.
It improves the accuracy of object velocity measurement and location determination in wireless communication systems, reduces interference, and optimizes resource utilization and communication efficiency.
Smart Images

Figure CN120883082A_ABST
Abstract
Description
[0001] Cross-reference to related applications
[0002] This application claims the benefit of U.S. Patent Application No. 18 / 301,196, filed April 14, 2023, entitled “VELOCITY ESTIMATION WITH RADIOFREQUENCY (RF) SENSING,” which is expressly incorporated herein by reference in its entirety. Technical Field
[0003] This disclosure relates generally to wireless communication systems, and more specifically to velocity estimation, such as velocity estimation using radio frequency (RF) sensing. Several features enable and provide improved communication, including reduced control overhead, efficient resource utilization, improved ranging or velocity measurement, location determination, transmit / receive point (TRP) selection, reduced interference, or combinations thereof. Background Technology
[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, message sending and receiving, and broadcasting. These wireless networks can be multiple access networks capable of supporting multiple users by sharing available network resources.
[0005] A wireless communication network may include several components. These components may include wireless communication devices, such as a base station (or node B) that can support communication between multiple user equipments (UEs). UEs may communicate with the base station via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the base station to the UE, and an uplink (or reverse link) refers to the communication link from the UE to the base station.
[0006] The base station can transmit data and control information to the UE on the downlink or receive data and control information from the UE on the uplink. On the downlink, transmissions from the base station may encounter interference originating from transmissions from neighboring base stations or other radio frequency (RF) transmitters. On the uplink, transmissions from the UE may encounter interference from other UEs communicating with neighboring base stations or from uplink transmissions from other RF transmitters. This interference can degrade performance on both the downlink and uplink.
[0007] As the demand for mobile broadband access continues to grow, the likelihood of network interference and congestion is also increasing, with more UEs accessing long-range wireless communication networks and more short-range wireless systems being deployed in communities. Research and development are continuously advancing wireless technologies to not only meet the growing demand for mobile broadband access but also to enhance and improve the user experience of mobile communications.
[0008] One or more devices in a wireless communication network can be configured to perform radio frequency (RF) sensing operations. RF sensing operations can be used in a variety of situations, such as monitoring road conditions to identify floods, animal intruders, etc., identifying human activity or detecting intruders in a home, monitoring health conditions, and detecting accidents, as illustrative and non-limiting examples. Additionally, RF sensing operations can be applied to both indoor applications (e.g., estimating the movement of vehicles on roads) and outdoor applications (e.g., estimating the movement of vehicles in a factory). Summary of the Invention
[0009] The following summary outlines some aspects of this disclosure to provide a basic understanding of the techniques discussed. This summary is not an exhaustive overview of all the intended features of this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure, nor to depict the scope of any or all aspects of this disclosure. The sole purpose of this summary is to present some concepts of one or more aspects of this disclosure in a generalized form as a prelude to the more detailed description that follows.
[0010] In one aspect of this disclosure, a method for wireless communication is performed by a network entity. The method includes receiving Doppler information and sensing information indicating a distance associated with an object from each of a plurality of transmitting / receiving points (TRPs). The method further includes determining the velocity of the object based on the sensing information received from the plurality of TRPs.
[0011] In an additional aspect of this disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to receive Doppler information and sensing information indicating a distance associated with an object from each of a plurality of transfer points (TRPs). The at least one processor is also configured to determine the velocity of the object based on the sensing information received from the plurality of TRPs.
[0012] In an additional aspect of this disclosure, an apparatus includes an interface configured to receive Doppler information and sensing information indicating a distance associated with an object from each of a plurality of transfer points (TRPs). The apparatus also includes at least one processor coupled to a memory storing processor-readable code configured to execute the processor-readable code to determine the velocity of the object based on the sensing information received from the plurality of TRPs.
[0013] In an additional aspect of this disclosure, an apparatus includes components for receiving Doppler information and sensing information indicating a distance associated with an object from each of a plurality of transceiver reference points (TRPs). The apparatus also includes components for determining the velocity of the object based on the sensing information received from the plurality of TRPs.
[0014] In an additional aspect of this disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: receiving Doppler information and sensing information indicating a distance associated with an object from each of a plurality of time-return nodes (TRPs). The operations also include: determining the velocity of the object based on the sensing information received from the plurality of TRPs.
[0015] In an additional aspect of this disclosure, a method for wireless communication is performed by a network entity. The method includes: sending configuration information to each TRP in a set of TRPs. The configuration information indicates sensing scheduling information. The method further includes: receiving sensing information associated with an object from each TRP in the set of TRPs. The sensing information indicates a distance value, angle of arrival, and time. The method further includes: determining the velocity of the object based on the sensing information received from the set of TRPs.
[0016] In an additional aspect of this disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to send configuration information to each TRP in a set of TRPs. The configuration information indicates sensing scheduling information. The at least one processor is also configured to receive sensing information associated with an object from each TRP in the set of TRPs. The sensing information indicates a distance value, angle of arrival, and time. The at least one processor is further configured to determine the velocity of the object based on the sensing information received from the set of TRPs.
[0017] In an additional aspect of this disclosure, an apparatus includes a communication interface configured to send configuration information to each TRP in a set of TRPs. The configuration information indicates sensing scheduling information. The communication interface is also configured to receive sensing information associated with an object from each TRP in the set of TRPs. The sensing information indicates a distance value, angle of arrival, and time. The apparatus further includes at least one processor coupled to a memory storing processor-readable code, the at least one processor being configured to execute the processor-readable code to determine the velocity of the object based on the sensing information received from the set of TRPs.
[0018] In an additional aspect of this disclosure, an apparatus includes components for sending configuration information to each TRP in a set of TRPs. The configuration information indicates sensing scheduling information. The apparatus also includes components for receiving sensing information associated with an object from each TRP in the set of TRPs. The sensing information indicates a distance value, angle of arrival, and time. The apparatus further includes components for determining the velocity of the object based on the sensing information received from the set of TRPs.
[0019] In an additional aspect of this disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: sending configuration information to each TRP in a set of Time-Responsible Partners (TRPs). The configuration information indicates sensing scheduling information. The operations also include: receiving sensing information associated with an object from each TRP in the set of TRPs. The sensing information indicates a distance value, angle of arrival, and time. The operations further include: determining the velocity of the object based on the sensing information received from the set of TRPs.
[0020] In an additional aspect of this disclosure, a method for wireless communication is performed by a network entity. The method includes: sending configuration information to each TRP in a set of Telemetry Points (TRPs). The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The method further includes: receiving sensing information from each TRP in the set of TRPs associated with a sensing operation performed based on the measurement configuration. The sensing information indicates a velocity of the object determined based on the orientation estimation information.
[0021] In an additional aspect of this disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to send configuration information to each TRP in a set of TRPs. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The at least one processor is also configured to receive sensing information from each TRP in the set of TRPs, associated with a sensing operation performed based on the measurement configuration. The sensing information indicates a velocity of the object determined based on the orientation estimation information.
[0022] In an additional aspect of this disclosure, an apparatus includes a communication interface configured to send configuration information to each TRP in a set of TRPs. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The apparatus also includes at least one processor coupled to a memory storing processor-readable code, the at least one processor being configured to execute the processor-readable code to cause the at least one processor to receive sensing information from each TRP in the set of TRPs, associated with a sensing operation performed based on the measurement configuration. The sensing information indicates a velocity of the object determined based on the orientation estimation information.
[0023] In an additional aspect of this disclosure, an apparatus includes components for sending configuration information to each TRP in a set of TRPs. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The apparatus also includes components for receiving sensing information from each TRP in the set associated with a sensing operation performed based on the measurement configuration. The sensing information indicates a velocity of the object determined based on the orientation estimation information.
[0024] In an additional aspect of this disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: sending configuration information to each TRP in a set of TRPs. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The operations also include: receiving sensing information from each TRP in the set of TRPs associated with a sensing operation performed based on the measurement configuration. The sensing information indicates a velocity of the object determined based on the orientation estimation information.
[0025] In an additional aspect of this disclosure, a method for wireless communication is performed by a transmitting / receiving point (TRP). The method includes receiving configuration information from a network entity. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. Additionally, the method includes transmitting to the network entity an indicator associated with a sensing operation performed based on the measurement configuration. The indicator indicates a velocity of the object determined based on the orientation estimation information.
[0026] In an additional aspect of this disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to receive configuration information from a network entity. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The at least one processor is also configured to send to the network entity an indicator associated with a sensing operation performed based on the measurement configuration. The indicator indicates a velocity of the object determined based on the orientation estimation information.
[0027] In an additional aspect of this disclosure, an apparatus includes at least one processor coupled to a memory storing processor-readable code, the at least one processor being configured to execute the processor-readable code to cause the at least one processor to receive configuration information from a network entity. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The apparatus also includes a communication interface configured to send to the network entity an indicator associated with a sensing operation performed based on the measurement configuration. The indicator indicates a velocity of the object determined based on the orientation estimation information.
[0028] In an additional aspect of this disclosure, an apparatus includes components for receiving configuration information from a network entity. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The apparatus also includes components for transmitting to the network entity an indicator associated with a sensing operation performed based on the measurement configuration. The indicator indicates a velocity of the object determined based on the orientation estimation information.
[0029] In an additional aspect of this disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: receiving configuration information from a network entity. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The operations also include: sending to the network entity an indicator associated with a sensing operation performed based on the measurement configuration. The indicator indicates a velocity of the object determined based on the orientation estimation information.
[0030] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and their associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims.
[0031] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects and / or the use of devices that can be implemented via integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to use cases or applications, the applicability of various types of the described innovations is evident. The scope of implementations ranges from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) for analog and digital purposes. The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with different sizes, shapes, and constructions. Attached Figure Description
[0032] A further understanding of the nature and advantages of this disclosure can be achieved by referring to the following figures. In the figures, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral.
[0033] Figure 1 It is a block diagram illustrating details of an example wireless communication system based on one or more aspects.
[0034] Figure 2 This is a block diagram illustrating examples of base stations and user equipment (UEs) based on one or more aspects.
[0035] Figure 3 A diagram illustrating an example decomposed base station architecture based on one or more aspects is shown.
[0036] Figure 4This is a block diagram illustrating an example wireless communication system that supports speed estimation based on sensing information from one or more aspects.
[0037] Figure 5 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects.
[0038] Figure 6 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects.
[0039] Figure 7 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects.
[0040] Figure 8 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects.
[0041] Figure 9 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects.
[0042] Figure 10 This is a ladder diagram illustrating an example of velocity estimation based on sensing information from one or more aspects.
[0043] Figure 11 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects.
[0044] Figure 12 This is a ladder diagram illustrating an example of velocity estimation based on sensing information from one or more aspects.
[0045] Figure 13 This is a flowchart illustrating an example process for velocity estimation based on sensing information, supported by one or more aspects.
[0046] Figure 14 This is a flowchart illustrating an example process for velocity estimation based on sensing information, supported by one or more aspects.
[0047] Figure 15 This is a flowchart illustrating an example process for velocity estimation based on sensing information, supported by one or more aspects.
[0048] Figure 16 It is a block diagram of an example network entity that supports velocity estimation based on sensing information from one or more aspects.
[0049] Figure 17 This is a flowchart illustrating an example process for velocity estimation based on sensing information, supported by one or more aspects.
[0050] Figure 18It is a block diagram of an example transmit / receive point (TRP) that supports speed estimation based on sensing information from one or more aspects.
[0051] The same reference numerals and names in different figures denote the same elements. Detailed Implementation
[0052] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of this disclosure. Rather, the detailed description includes specific details for providing a thorough understanding of the subject matter of the invention. It will be apparent to those skilled in the art that these specific details are not necessary in every situation, and in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.
[0053] This disclosure provides systems, apparatus, methods, and computer-readable media that support velocity estimation based on sensing information. For example, in a first aspect, the disclosure describes determining the velocity of an object based on Doppler measurements from multiple transmit / receive points (TRPs). These Doppler measurements may be determined based on one or more monostation sensing operations, one or more bistation sensing operations, or a combination thereof. In a second aspect, the velocity of the object may be determined based on angle of arrival (AoA) information received from one or more TRPs. This AoA information may include distance, AoA, time, or a combination thereof. In a third aspect, the velocity of the object may be determined based on the object's orientation during a sensing operation performed by the TRP.
[0054] Specific embodiments of the subject matter described herein can be implemented to achieve one or more of the following potential advantages or benefits. In some aspects, this disclosure provides techniques for supporting velocity estimation based on sensing information. For example, the techniques described herein enable sensing (such as RF sensing) to estimate the position or velocity of an object. The techniques described herein enable Doppler measurements indicating a component of the object's velocity to be used to determine the object's true velocity. For example, Doppler measurements from multiple TRPs can be used to determine the true velocity. Additionally or alternatively, the Doppler measurement can be used in conjunction with the object's orientation to determine the object's true velocity. Sensing can also be performed to determine AoA information, which can be used to determine the object's true velocity.
[0055] This disclosure relates throughout to providing or participating in licensed shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various specific implementations, technologies and apparatus can be used in wireless communication networks such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, and fifth-generation (5G) or new radio (NR) networks (sometimes referred to as "5G"). NR (Network, System, or Device) and other communication networks. As described herein, the terms “network” and “system” are used interchangeably.
[0056] CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards.
[0057] For example, TDMA networks can implement radio technologies such as the Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standard for the GSM EDGE (Enhanced Data Rate GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of the network connecting GSM / EDGE base stations (e.g., Ater and Abis interfaces) and base station controllers (A interface, etc.). The radio access network represents a component of the GSM network through which telephone calls and packet data are routed from the Public Switched Telephone Network (PSTN) and the Internet to subscriber handsets (also known as user terminals or user equipment (UEs)) and from subscriber handsets to the PSTN and the Internet. A mobile phone operator's network may include one or more GERANs, which may be coupled with UTRAN in the case of UMTS / GSM networks. Additionally, the operator's network may also include one or more LTE networks, or one or more other networks. Different network types may use different radio access technologies (RATs) and RANs.
[0058] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and flash-OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization called the 3rd Generation Partnership Project (3GPP), and cdma2000 is described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration among telecommunications associations aimed at defining globally applicable third-generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP initiative aimed at improving the UMTS mobile phone standard. 3GPP defines specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure may refer to LTE, 4G, or 5G NR technologies to describe certain aspects; however, this description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of this disclosure may relate to shared access to radio spectrum between networks using different radio access technologies or radio air interfaces.
[0059] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices available using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage (1) to massive Internet of Things (IoT) with ultra-high density (e.g., approximately 1 M nodes / km). 2 (1) Ultra-low complexity (e.g., approximately 10 s bits / sec), ultra-low power consumption (e.g., approximately 10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) Includes mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., approximately 99.9999% reliability), ultra-low latency (e.g., approximately 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) Provides enhanced mobile broadband (including extremely high capacity (e.g., approximately 10 Tbps / km)). 2 Coverage with extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates) and deep awareness with advanced discovery and optimization.
[0060] Devices, networks, and systems can be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often referred to (interchangeably) as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise for FR2, which is often (interchangeably) referred to as the “millimeter wave” (mmWave) band in documents and articles, although this is different from the extremely high frequency (EHF) band (30GHz-300GHz) designated as “mmWave” by the International Telecommunication Union (ITU).
[0061] In light of the above, unless otherwise specified, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, it should be understood that when used herein, the term "mmWave" can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.
[0062] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform characteristics. These characteristics may include scalable parameter sets and transmission time intervals (TTI); a common flexible framework for efficiently multiplexing services and characteristics using dynamic, low-latency time-division duplex (TDD) or frequency-division duplex (FDD) designs; and advanced radio technologies such as massive MIMO, robust mmWave transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets and subcarrier spacing in 5G NR efficiently addresses the operation of various services across different spectrums and deployments. For example, in various outdoor and macro coverage deployments with FDD or TDD implementations below 3 GHz, subcarrier spacing may occur at 15 kHz, for example, exceeding bandwidths such as 1 MHz, 5 MHz, 10 MHz, and 20 MHz. For other various outdoor and small cell coverage deployments with TDD above 3 GHz, subcarrier spacing may occur at 30 kHz over an 80 MHz / 100 MHz bandwidth. For various other indoor broadband implementations using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting via mmWave components under 28 GHz TDD, subcarrier spacing may occur at 120 kHz over a 500 MHz bandwidth.
[0063] 5G NR's scalable parameter set facilitates scalable TTIs for diverse latency and Quality of Service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectrum efficiency. Efficient multiplexing of long and short TTIs allows transmission to begin at symbol boundaries. 5G NR also anticipates self-contained integrated subframe designs, where uplink or downlink scheduling information, data, and acknowledgments reside in the same subframe. Self-contained integrated subframes support communication in unlicensed or contention-based shared spectrum, with adaptive uplink or downlink that can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current service demands.
[0064] For clarity, certain aspects of the apparatus and technology may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in the sections described below; however, this description is not intended to be limited to 5G applications.
[0065] Furthermore, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to those skilled in the art that the systems, apparatuses, and methods described herein can be applied to other communication systems and applications besides the specific examples provided.
[0066] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, implementations or uses may be achieved via integrated chip implementations or other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail or purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to use cases or applications, the applicability of various types of the described innovations is evident. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the described aspects. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described aspects. The intention is that the innovations described herein can be implemented in a wide variety of specific implementations of different sizes, shapes and constructions, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed deployments, end-user devices, etc.
[0067] Figure 1 This is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. Wireless network 100 may, for example, include a 5G wireless network. As those skilled in the art will recognize, Figure 1 The components appearing in this network are likely to have corresponding components in other network layouts (including, for example, cellular network layouts and non-cellular network layouts (e.g., device-to-device, peer-to-peer, or self-organizing network layouts)).
[0068] Figure 1The illustrated wireless network 100 includes a plurality of base stations 105 and other network entities. A base station may be a station communicating with a UE and may also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a specific geographic coverage area of a base station or a base station subsystem serving that coverage area, depending on the context in which the term is used. In the specific implementation of the wireless network 100 herein, base stations 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in the specific implementation of the wireless network 100 herein, base station 105 may use one or more frequencies (e.g., one or more bands of licensed spectrum, unlicensed spectrum, or combinations thereof) from the same frequencies as neighboring cells to provide wireless communication. In some examples, a single base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.
[0069] Base stations can provide communication coverage for macro cells, small cells (such as pico cells or femto cells), or other types of cells. Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as pico cells) typically cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as femto cells) also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, provide restricted access by UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in a home, etc.). A base station used for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, pico base station, femto cell base station, or home base station. Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3D, full-dimensional (FD), or massive MIMO. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. A base station can support one or more (e.g., two, three, four, etc.) cells.
[0070] Wireless network 100 can support synchronous or asynchronous operation. For synchronous operation, base stations can have similar frame timings, and transmissions from different base stations can be roughly aligned in time. For asynchronous operation, base stations can have different frame timings, and transmissions from different base stations may not be aligned in time. In some cases, the network can be enabled or configured to handle dynamic switching between synchronous and asynchronous operation.
[0071] UE 115 is distributed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that although mobile devices are generally referred to as UEs in standards and specifications issued by 3GPP, such devices may additionally or otherwise be referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handphone, terminal, user agent, mobile client, client, gaming device, augmented reality device, vehicle component, vehicle equipment or vehicle module, or some other suitable term. In this document, a “mobile” device or UE does not necessarily have the ability to move and may be stationary. Some non-limiting examples of mobile devices include specific implementations that may include one or more UEs 115, including mobile phones, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, and personal digital assistants (PDAs). Mobile devices may additionally be IoT or “Internet of Everything” (IoE) devices, such as automobiles or other transportation vehicles, satellite radios, Global Positioning System (GPS) devices, Global Navigation Satellite System (GNSS) devices, logistics controllers, drones, multi-rotor helicopters, quadcopter helicopters, smart energy or security devices, solar panels or solar arrays, urban lighting, water supply or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smartwatches, health or fitness trackers, mammalian implantable devices, posture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia equipment, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UEs 115a-115d illustrated herein are examples of mobile smartphone-type devices accessing the wireless network 100. The UE can also be a machine specifically configured for connecting communications, including machine-type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 The UE 115e-115k illustrated herein is an example of various machines configured for communication that access the wireless network 100.
[0072] Mobile devices (such as UE 115) can communicate with any type of base station (whether macro base station, pico base station, femto base station, relay station, etc.). Figure 1 In this context, the communication link (represented by a lightning bolt) indicates radio transmissions between the UE and a serving base station (which is designated to serve the UE on the downlink or uplink), or expected transmissions between base stations, and backhaul transmissions between base stations. The UE may operate as a base station or other network node in some scenarios. Backhaul communication between base stations of the wireless network 100 can be performed using wired or wireless communication links.
[0073] In operation, at wireless network 100, base stations 105a-105c use 3D beamforming and cooperative spatial technologies such as Cooperative Multipoint (CoMP) or Multi-Connection to serve UEs 115a and 115b. Macro base station 105d performs backhaul communication with base stations 105a-105c and the small cell (base station 105f). Macro base station 105d also transmits multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber Alerts or Grey Alerts.
[0074] The specific implementation of the wireless network 100 supports mission-critical communication with ultra-reliable and redundant links for mission-critical devices such as the UE 115e used as unmanned aerial vehicles. Redundant communication links with the UE 115e include links from macro base stations 105d and 105e, as well as small cell base station 105f. Other machine-type devices, such as the UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device), can communicate directly with base stations such as the small cell base station 105f and macro base station 105e via the wireless network 100, or in a multi-hop configuration, by communicating with another user device relaying its information to the network. For example, the UE 115f communicates temperature measurement information to the smart meter UE 115g, which then reports it to the network via the small cell base station 105f. Wireless network 100 can also provide additional network efficiency (such as in vehicle-to-vehicle (V2V) mesh networks between UEs 115i-115k communicating with macro base station 105e) through dynamic, low-latency TDD or low-latency FDD communication.
[0075] Base station 105 can communicate with core network 130 and with each other. For example, base station 105 can interface with core network 130 via backhaul link 132 (e.g., via S1, N2, N3 or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) via backhaul links (e.g., via X2, Xn or other interfaces).
[0076] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC), which may include at least one Mobility Management Entity (MME), at least one Serving Gateway (S-GW), and at least one Packet Data Network (PDN) Gateway (P-GW). The MME manages non-access stratum (e.g., control plane) functions, such as mobility, authentication, and bearer management of UE 115 served by base station 105 associated with the EPC. User IP packets can be delivered via the S-GW, which itself can connect to the P-GW. The P-GW provides IP address allocation and other functions. The P-GW can connect to network operator IP services. These operator IP services may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched (PS) streaming services.
[0077] In some implementations, the core network 130 includes or is coupled to a management function 131, which is an entity within the 5G core network (5GC) that supports various functionalities. Management function 131 may include a Location Management Function (LMF) or a Sensing Management Function (SnMF). The SnMF may be configured to manage support for one or more sensing operations or sensing services for one or more devices, such as one or more UEs 115, one or more base stations 105, one or more TRPs, or combinations thereof. For example, the SnMF may include one or more servers, such as multiple distributed servers. Base station 105 may forward sensing messages to the SnMF and may communicate with the SnMF via NR Positioning Protocol A (NRPPa). The SnMF is configured to control sensing parameters of UE 115, and the SnMF may provide information to base station 105 and UE 115 enabling actions to be taken at UE 115, base station 105, or another device. The LMF may be configured to manage support for different location services for one or more UEs. For example, the LMF may include one or more servers, such as multiple distributed servers. Base station 105 can forward location messages to the LMF and can communicate with the LMF via NR Location Protocol A (NRPPa). The LMF is configured to control the location parameters of UE 115, and the LMF can provide information to base station 105 and UE 115, enabling actions to be taken at UE 115. In some implementations, UE 115 and base station 105 are configured to communicate with management function 131 via access and mobility management function (AMF).
[0078] Figure 2 This is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 can be... Figure 1 This refers to any one of the base stations and one of the UEs in the system. For restricted association scenarios (as mentioned above), base station 105 can be... Figure 1 The base station 105 is a small cell base station, and UE 115 can be UE 115c or 115d operating within the service area of base station 105f. UE 115 will be included in the list of accessible UEs of small cell base station 105f in order to access it. Base station 105 can also be some other type of base station. For example... Figure 2 As shown, base station 105 may be equipped with antennas 234a to 234t, and UE 115 may be equipped with antennas 252a to 252r for facilitating wireless communication.
[0079] At base station 105, transmitting processor 220 can receive data from data source 212 and control information from controller 240 (such as a processor). The control information may be for physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), physical downlink control channel (PDCCH), enhanced physical downlink control channel (EPDCCH), MTC physical downlink control channel (MPDCCH), etc. The data may be for physical downlink shared channel (PDSCH), etc. Additionally, transmitting processor 220 can process (e.g., encoding and symbol mapping) the data and control information separately to obtain data symbols and control symbols. Transmitting processor 220 can also generate, for example, reference symbols for primary synchronization signal (PSS) and secondary synchronization signal (SSS), as well as cell-specific reference signals. The transmit (TX) MIMO processor 230 can perform spatial processing (e.g., pre-decoding, where applicable) on data symbols, control symbols, or reference symbols, and can provide an output symbol stream to modulators (MODs) 232a to 232t. For example, spatial processing performed on data symbols, control symbols, or reference symbols may include pre-decoding. Each modulator 232 can (e.g., for OFDM, etc.) process its respective output symbol stream to obtain an output sample stream. Additionally or alternatively, each modulator 232 can process the output sample stream (e.g., perform analog-to-analog conversion, amplification, filtering, and up-conversion) to obtain a downlink signal. The downlink signal from modulators 232a to 232t can be transmitted via antennas 234a to 234t, respectively.
[0080] At UE 115, antennas 252a to 252r can receive downlink signals from base station 105 and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain the received symbols from demodulators 254a to 254r, perform MIMO detection on the received symbols when necessary, and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide the decoded data for UE 115 to data sink 260, and provide the decoded control information to controller 280, such as a processor.
[0081] On the uplink, at UE 115, the transmitting processor 264 can receive and process data from data source 262 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller 280 (e.g., for the Physical Uplink Control Channel (PUCCH)). Additionally, the transmitting processor 264 can also generate reference symbols for reference signals. Symbols from the transmitting processor 264 can be pre-decoded by the TX MIMO processor 266 when needed, further processed by modulators 254a to 254r (e.g., for SC-FDM, etc.), and transmitted to base station 105. At base station 105, the uplink signal from UE 115 can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 when needed, and further processed by receiving processor 238 to obtain the decoded data and control information transmitted by UE 115. The receiver processor 238 can provide the decoded data to the data sink 239 and the decoded control information to the controller 240.
[0082] Controllers 240 and 280 can respectively direct operations at base station 105 and UE 115. Controller 240 or other processors and modules at base station 105 or controller 280 or other processors and modules at UE 115 can perform or direct the execution of various processes used in the techniques described herein, such as performing or directing... Figures 12 to 15 or Figure 17 The process shown or other processes used in the techniques described herein are executed. Memory 242 and 282 may store data and program code for base station 105 and UE 115, respectively. Scheduler 244 may schedule the UE to perform data transmission on the downlink or uplink.
[0083] In some cases, UE 115 and base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, UE 115 or base station 105 may conventionally perform a medium sensing procedure to compete for spectrum access. For example, UE 115 or base station 105 may perform a Listen-Before-Speak or Listen-Before-Transmit (LBT) procedure (such as Clear Channel Assessment (CCA)) before communication to determine if a shared channel is available. In some implementations, CCA may include an energy detection procedure to determine if any other active transmission is present. For example, the device may infer that a change in the Received Signal Strength Indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include the detection of a specific sequence indicating channel usage. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or on acknowledgment / negative acknowledgment (ACK / NACK) feedback for packets it transmits (as a manifestation of a collision).
[0084] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both. The core network 320 may include or correspond to a core network 130. CUs 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links (such as F1 interfaces). DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. RUs 340 may communicate with corresponding UEs 115 via one or more radio frequency (RF) access links. In some implementations, a UE 115 may be served simultaneously by multiple RUs 340.
[0085] Each of these units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO frame 305) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via the transmission medium. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via a wired transmission medium. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive or transmit signals, or both, to one or more other units over a wireless transmission medium.
[0086] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling, as needed.
[0087] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, DU 330 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.
[0088] Lower-layer functionality can be implemented by one or more RU 340s. In some deployments, an RU340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UE 115s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration enables the implementation of the DU 330 and CU 310 in cloud-based RAN architectures such as vRAN architectures.
[0089] SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 305 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, SMO framework 305 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, SMO framework 305 can communicate directly with one or more RU 340s via the O1 interface. SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of SMO framework 305.
[0090] The non-RT RIC 315 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data acquisition and actions through an interface such as an E2 interface, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.
[0091] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 325 and may be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).
[0092] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, can be, or may include in (e.g., as a component of): a base station (e.g., any base station described herein), a Transmitter Receiver Point (TRP), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, Integrated Access and Backhaul (IAB) node, Distributed Unit (DU), Central Unit (CU), Remote Unit (RU), core network, LFM, and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. Alternatively, a network node may be a base station or a network entity. Alternatively, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first or more components, a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second or more components, a second processing entity, etc.
[0093] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.
[0094] Figure 4 This is a block diagram of an example wireless communication system 400 supporting speed estimation based on sensed information, according to one or more aspects. In some examples, the wireless communication system 400 may implement aspects of the wireless network 100. The wireless communication system 400 includes a first TRP 440, a second TRP 442, a third TRP 446, and a core network 130. Although three TRPs are illustrated, in some other specific implementations, the wireless communication system 400 may typically include fewer or more than three TRPs. Additionally, the environment of the wireless communication system 400 may include object 422.
[0095] Object 422 can be a deviceless object that does not have sensing (RF) functionality for communication. For example, the object can be a person, an animal, a car, etc.
[0096] The first TRP 440 may include various components (such as architecture, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 402 (hereinafter collectively referred to as "processor 402"), one or more memory devices 404 (hereinafter collectively referred to as "memory 404"), one or more transmitters 416 (hereinafter collectively referred to as "transmitter 416"), and one or more receivers 418 (hereinafter collectively referred to as "receiver 418"). In some embodiments, the first TRP 440 may include an interface (e.g., a communication interface) comprising transmitter 416, receiver 418, or a combination thereof. Additionally or alternatively, the first TRP 440 may include a sensing device comprising transmitter 416, receiver 418, or a combination thereof. Processor 402 may be configured to execute instructions 405 stored in memory 404 to perform the operations described herein. In some embodiments, processor 402 includes or corresponds to one or more of receive processor 238, transmit processor 220, and controller 240, and memory 404 includes or corresponds to memory 242.
[0097] Memory 404 includes or is configured to store instructions 405, Position Reference Signal (PRS) information 407, object information 409, and sensing information 410. PRS information 407 includes information used by the first TRP 440 to generate the Position Reference Signal (PRS) 474. For example, PRS information 407 may include one or more parameters, such as time, repetition rate, bandwidth configuration, comb pattern configuration, or combinations thereof. The repetition rate may include or indicate the number of times the PRS is transmitted within a time period. The comb pattern may include or indicate a configurable resource block allocation. Object information 409 includes or corresponds to information about object 422. For example, object information 409 may include or indicate the object ID of object 422, the RF signature of object 422, or combinations thereof. Sensing information 410 (such as measurement information) may include or correspond to the results of one or more sensing operations. For example, sensing information may include distance, angle (e.g., AoA), time, position, Doppler measurement, RSRP level, velocity, or combinations thereof.
[0098] Transmitter 416 is configured to transmit reference signals, control information, and data to one or more other devices, and receiver 418 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitter 416 may transmit signaling, control information, and data to core network 130, another TRP, or network entity, and receiver 418 may receive signaling, control information, and data from the core network, another TRP, or network entity. Additionally or alternatively, transmitter 416 may transmit a positioning reference signal (e.g., 474), and receiver 418 may receive a reflected signal (e.g., 476). In some implementations, transmitter 416 and receiver 418 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 416 or receiver 418 may include or correspond to reference signals, synchronization signals, control information, and data. Figure 2 The UE 115 or base station 105 describes one or more components. In some specific implementations, the transmitter 416 or receiver 418 may be configured to operate in full-duplex mode.
[0099] In some embodiments, the first TRP 440 may include one or more antenna arrays. The antenna arrays may include multiple antenna elements configured to perform wireless communication with other devices, such as the core network 130. In some embodiments, the antenna arrays may be configured to perform wireless communication using different beams (also referred to as antenna beams). The beams may include a TX beam and an RX beam. For illustration, the antenna arrays may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements in the antenna array may be configured to communicate using a different corresponding beam, which may have a corresponding direction different from the other beams. For example, a first set of antenna elements in the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements in the antenna array may be configured to communicate via a second beam having a second direction. In other embodiments, the antenna arrays may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements in the antenna array may be configured to generate multiple beams concurrently, for example, using multiple RF chains. Each individual set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number of antenna elements greater than two. Although described as an antenna array, in other specific implementations, an antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to use a different corresponding beam for communication.
[0100] The second TRP 442 and the third TRP 446 may include or correspond to the first TRP 440. For example, the second TRP 442 or the third TRP 446 may include one or more components similar to those of the first TRP 440. In some implementations, the first TRP 440, the second TRP 442, or the third TRP 446 may be synchronized, such as through time synchronization. Additionally or alternatively, the first TRP 440, the second TRP 442, or the third TRP 446 may be configured to share the same coordinate system.
[0101] Core network 130 may include a 3GPP core network, a 4G core network, a 5G core, or an evolved packet core (EPC). Core network 130 may be coupled (e.g., communicatively coupled) to one or more network entities, such as TRP 440, 442, or 446. Core network 130 may include MF 131.
[0102] Although shown and described as being included in core network 130, in some specific implementations, MF 131 may differ from core network 130. For example, MF 131 may include one or more servers, such as multiple distributed servers. MF 131 may be configured to support various functionalities, such as managing support for different location services for one or more UEs, and managing support for different sensing services for one or more UEs or devices. For example, MF 131 may be configured to control sensing parameters of TRPs 440, 442, or 446, and MF 131 may provide information to TRPs 440, 442, or 446 to enable actions or operations to be taken at TRPs 440, 442, or 446. TRPs 440, 442, or 446 (such as base station 105) may forward sensing messages to MF 131 and may communicate with MF 131 via protocols such as NR Positioning Protocol A (NRPPa). In some specific implementations, TRP 440, 442, or 446, or combinations thereof, are configured to communicate with MF 131 via the Access and Mobility Management Function (AMF).
[0103] MF 131 may include various components (such as architecture, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 462 (hereinafter collectively referred to as “processor 462”), one or more memory devices 464 (hereinafter collectively referred to as “memory 464”), one or more transmitters, and one or more receivers. In some embodiments, LMF 431 may include an interface (e.g., a communication interface) comprising one or more transmitters, one or more receivers, or combinations thereof. Processor 462 may be configured to execute instructions stored in memory 464 to perform the operations described herein. In some embodiments, references... Figure 2 The components of the base station 105 include a processor 462 that includes or corresponds to one or more of a receiving processor 238, a transmitting processor 220, and a controller 240, and a memory 454 that includes or corresponds to a memory 242.
[0104] Memory 464 may include or indicate the velocity 465 and orientation information 456 of object 422. In some embodiments, velocity 465 may be the actual velocity. Orientation information 456 may include or indicate a pose estimation model or pose estimation neural network, an orientation estimation model or orientation estimation neural network, or a combination thereof. In some embodiments, the MF 131 of core network 130 may be configured to determine the velocity 465 of object 422 based on sensing information 478 from one or more TRPs. Furthermore, LMF 131 may be configured to transmit velocity data indicating velocity 465.
[0105] In some implementations, the wireless communication system 400 implements a 5G NR network. For example, the wireless communication system 400 may include multiple 5G-capable UEs 115 and multiple 5G-capable base stations 105, such as UEs and base stations configured to operate according to 5G NR network protocols (such as the 5G NR network protocols defined by 3GPP). In some other implementations, the wireless communication system 400 implements a 6G network.
[0106] During operation of the wireless communication system 400, the core network 130 (or management function 131) may send configuration information 472 to one or more TRPs (such as TRPs 440, 442, or 446). TRP 440 may perform one or more sensing operations based on the configuration information 472, PRS information 407, or a combination thereof. In some implementations, TRP 440 may send a positioning reference signal 474 and receive a reflection 476, which is a reflection of the positioning reference signal 474 from object 422. The TRP may perform one or more measurement operations or calculations based on the positioning reference signal 474, reflection 476, or a combination thereof to generate sensing information 410. TRP 440 may generate sensing information 478 based on the sensing information 410 and send the sensing information 478 to the core network 130 (or MF 131). The core network 130 (or MF 131) may determine a speed 465 based on the sensing information 448.
[0107] As described herein, this disclosure provides techniques for supporting sensing-based billing subscriptions. The described techniques provide processes, information, and signaling for supporting velocity estimation based on sensing information. For example, the techniques described herein enable sensing, such as RF sensing, to estimate the position or velocity 465 of object 422. The techniques described herein enable Doppler measurements indicating a component of the velocity of object 422 to be used to determine the true velocity of object 422. For example, Doppler measurements from multiple TRPs (e.g., 440, 442, 446) can be used to determine the true velocity. Sensing can also be performed to determine AoA information, which can be used to determine the true velocity of object 422. Additionally or alternatively, the Doppler measurement can be used in conjunction with the orientation of object 422 to determine the true velocity of object 422.
[0108] In some implementations, the speed 465 may be determined or estimated based on one or more sensing operations, such as one or more RF sensing operations. One or more sensing operations (such as single-station sensing operations, dual-station sensing operations, or combinations thereof) may be performed to determine the position of object 422, Doppler estimation (e.g., Doppler measurement), or combinations thereof. This document references at least... Figures 5 to 7 Examples of such technologies are further described.
[0109] Reference Figure 5 , Figure 5 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects. Figure 5 Includes the TRP at a location (TX / RX location). Figure 5 It also indicates the possible location of an object (such as object 422). For example, the object may be located at a first position 502, a second position 504, or a third position 506. At each position (e.g., 502, 504, 506), the object may have a velocity vector (e.g., instantaneous velocity).
[0110] The TRP can be configured to perform sensing operations (e.g., RF sensing operations) to determine a Doppler measurement. An estimated velocity of the object can be determined based on this Doppler measurement. This estimated velocity can be the projection of the velocity vector v (instantaneously) relative to the position of the TRP in the radial direction. Since this radial direction is a function of the object's relative position to the TRP, the estimated velocity is also a function of the object's relative position. With respect to the first position 502, the estimated velocity is toward the TRP. With respect to the second position 504, the estimated velocity is zero because the velocity vector is in a direction perpendicular (e.g., tangential) to the radial direction of the TRP. With respect to the third position 506, the estimated velocity is away from the TRP.
[0111] Reference Figure 6 , Figure 6 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects. Figure 6 This includes TRPs 440, 442, and 446, as well as object 422. For example... Figure 6 As shown, each TRP is configured to perform a single-site sensing operation (e.g., a single-site RF sensing operation).
[0112] Object 422 may have a velocity vector Velocity vector It can include components in three dimensions, v. x v y v z , making .
[0113] To determine the velocity vector, one or more ranging measurements are used to determine the location of object 422. If multiple objects exist, the distance measurements across TRPs are correlated, and a location estimate for each object is calculated. For each TRP, the radial direction can be calculated based on the location of that TRP and the location estimate of object 422. For example, the radial direction of TRP 440 is... 1. The radial direction of TRP 442 is 2, and the radial direction of TRP 446 is 3.
[0114] Each TRP can perform sensing operations and can determine an estimated velocity based on a Doppler measurement. For example, TRP 440 can determine a first estimated velocity v1, TRP 442 can determine a second estimated velocity v2, and TRP 446 can determine a third estimated velocity v3. In some specific implementations, each TRP can determine a Doppler measurement and translate that Doppler measurement into a projected velocity. Note that for single-station Doppler measurements:
[0115] ,
[0116] Where f d It is (e.g., the reflection of 476) the Doppler frequency, c is the speed of light, and f is the Doppler frequency. c It is the carrier frequency of the reference signal (e.g., 474).
[0117] In some specific implementations, the estimated velocity of TRP can be considered a noise measurement, making the projected velocity... This is equivalent to estimating the velocity plus some noise from the TRP. For example, TRP 440 can be associated with a first noise n1, TRP 442 with a second noise n2, and TRP 446 with a third noise n3. In some implementations, the noise level of each velocity measurement can be inversely proportional to the signal-to-noise ratio (SNR) of the received reference signal. Therefore, for TRPs 440, 442, and 446, corresponding measurement equations can be generated:
[0118]
[0119]
[0120]
[0121] Each equation includes a noise velocity projection based on Doppler measurements on the right-hand side and a radial vector on the left-hand side.
[0122] The velocity vector can then be solved based on this equation. (Including three components v) x v y v z To determine the velocity 465, such as the true velocity parameter, a least squares (LS) operation or a minimum mean square error (MMSE) operation can be performed. In some implementations, the MMSE operation can be performed if the noise variance is known.
[0123] Reference Figure 7 , Figure 7It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects. Figure 7 This includes TRPs 440 and 442, and object 422. For example... Figure 7 As shown, TRPs 440 and 442 are located at different locations and configured as a TRP pair to perform bi-site sensing operations (e.g., bi-site RF sensing operations). For example, TRP 440 is configured as a transmitter and TRP 442 is configured as a receiver.
[0124] refer to Figure 7 R tx It is the distance from TRP 440 to object 422, and R rx This is the distance from TRP 442 to object 422. Object 422 may have a velocity vector. Velocity vector It can include components in three dimensions, v. x v y v z , making Additionally, the tangent unit vector It can pass through object 422 and the ellipse established based on TRP 440 and 442, and can be in a direction orthogonal to the tangent vector (normal vector). The measurement is a Doppler measurement. In other words, the Doppler measurement will be the true velocity measured relative to the distance R. tx Add distance R rx The sum of these values represents the projection onto the line orthogonal to the tangent of the ellipse. Note that for bistatic Doppler measurements:
[0125]
[0126] Performing bistationary sensing operations with three TRP pairs enables the generation of measurement equations, such as:
[0127]
[0128]
[0129]
[0130] Once the measurement equations are written, the velocity of object 422 can be determined using a process similar to that described in the reference single-station operation. In some specific implementations, a combination of single-station and bi-station sensing operations can be performed to determine the velocity of object 422. For example, a reference... Figure 6 One or more measurement equations and references described Figure 7 One or more measurement equations are described to determine the velocity of object 422.
[0131] Refer again Figure 4 In some implementations, the speed of object 422 may be determined by a network such as core network 130 or by a management function 131 such as sensing management function (SnMF). For example, the network may determine the speed with the assistance of one or more TRPs (such as one or more UEs 115, one or more base stations 105, or a combination thereof). The network may configure a reporting session for a set of TRPs, where TRPs may include individual TRPs or TRP pairs. Each TRP participating in the sensing session may be configured to report distance, angle, Doppler measurement, or phase, or a combination thereof. In some implementations, a TRP may be configured to report Doppler measurements for each multipath delay. Additionally, it should be noted that if the phase of the multipath is reported, the network may calculate the Doppler measurement.
[0132] In some implementations, if the location of the TRP (e.g., the UE) is unknown, the network can determine or calculate the TRP's location. In some implementations, the TRP's location can be determined or coordinated by the LMF.
[0133] The network can calculate the position of object 422 based on multipath delay, angle (e.g., AoA) received from the TRP, or a combination thereof. In some specific implementations, the number of objects in the environment is unknown. Therefore, the network may have to perform processes such as executing data association algorithms to assign one or more measurements to different objects. Thus, before determining the velocity of object 422, the network may first have to determine which measurements are associated with object 422 and its position.
[0134] Based on the position of object 422 and the position of TRP, the network can calculate the velocity measurement direction of TRP (e.g., radial direction) and associate the radial direction of TRP with the Doppler measurements reported by TRP. The network can determine the velocity vector v of object 422 based on the radial directions and Doppler measurements of multiple TRPs (such as three or more TRPs). The network can send an indicator indicating the determined velocity to another device, such as a device requesting velocity information.
[0135] In some implementations, one or more operations described in the reference network (such as core network 130) or management function 131 may be performed by a TRP (such as UE 115). In such implementations, sensing information 478 (e.g., location, measurement, or a combination thereof) may be provided to a specific TRP (such as a specific UE). For example, sensing information 478 may be provided to a specific TRP via a sidelink channel (e.g., between two UEs), or via the network from a first UE using the LPPa / NRPPa protocol. The specific TRP may process the received sensing information 478 to determine velocity 465.
[0136] In some specific implementations, the speed 465 can be determined or estimated based on one or more sensing operations (such as one or more RF sensing operations). For example, one or more sensing operations can be performed to determine AoA. This document references at least... Figures 8 to 10 Examples of such technologies are further described.
[0137] Reference Figure 8 , Figure 8 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects. Figure 8 This includes a TRP (TRP0) and a target (e.g., an object). The TRP (TRP0) may include or correspond to TRP 440. The object may include or correspond to object 422. For example... Figure 8 As shown, objects are illustrated at two different times—for example, the first time T0 and the second time T1.
[0138] TRP can be configured to determine the angle of arrival (AoA), which can be used to determine the velocity of the object. (e.g., actual speed). For illustration, at a first time T0, the TRP may perform a sensing operation. For example, the TRP may transmit a PSR or other reference signal (such as a positioning reference signal 474) and receive a reflection (such as 476). Based on the sensing operation (e.g., the reflection), the TRP may estimate a first distance. and first arrival angle In the second time At that point, TRP sends another PRS (e.g., 474) and estimates the second distance. Second angle of arrival .based on Calculated speed (For example, actual speed). For instance, a closed-form expression can be used to calculate speed. :
[0139]
[0140] In some specific implementations, a single TRP can be deployed in the first instance. Second time Measurements were performed at the location. Although referenced... Figure 8 Two times are described, but in other implementations, a single TRP can perform additional measurements, such as at a third time T2, which can also be used to determine the velocity v. Additionally or alternatively, in other implementations, different or multiple TRPs can be used at the first time. Second time Measurements can be performed at locations where they are combined or in combination. Further velocity estimates (such as velocity v) can be provided by using additional measurements, using multiple TRPs at once, or both.
[0141] Reference Figure 9 , Figure 9 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects. Figure 9 This includes a first TRP (TRP0), a second TRP (TRP1), and a target (e.g., an object). The first TRP (TRP0) may include or correspond to TRP 440, and the second TRP (TRP1) may include or correspond to TRP 442. The object may include or correspond to object 422. Figure 9 As shown, objects are illustrated at two different times—for example, the first time T0 and the second time T1.
[0142] The first TRP can be configured to perform a first sensing operation at a first time T0. For example, the first TRP can send a PRS (such as a positioning reference signal 474) and receive a reflection (such as 476). Based on the sensing operation (e.g., the reflection), the first TRP can estimate a first distance. and first arrival angle .
[0143] Second time At this point, the second TRP can send a PRS (e.g., 474) and estimate the second distance. Second angle of arrival .based on Calculated speed (e.g., actual velocity). In order to calculate the velocity v using the (above) closed expression, the first TRP and the second TRP should be time-synchronized and share the same coordinate system.
[0144] Although reference Figure 9 Two times are described, but in other implementations, the TRP can perform additional measurements, such as at a third time T2, which can also be used to determine the velocity v. In other implementations, different or multiple TRPs can be used at the first time. Second time Measurements can be performed at locations where they are combined. For example, both the first TRP and the second TRP can be measured at the first moment. Second time Measurements are performed at the location. Further velocity estimates (such as velocity v) can be provided by using additional measurements, using multiple TRPs at once, or both.
[0145] Figure 10This is a ladder diagram illustrating an example of velocity estimation based on sensed information according to various aspects of this disclosure. For example... Figure 10 As shown, Figure 10 The ladder diagram system 1000 includes MF 131 and TRP 440. MF 131 and TRP 440 may include one or more components and are configured to perform one or more operations, as referenced. Figures 1 to 4 As described. System 1000 may include or correspond to wireless communication system 100 or 400. Although Figure 10 A single TRP 440 is depicted, but the system 1000 may include more than one TRP.
[0146] refer to Figure 10 During operation of system 1000, at 1002, MF 131 sends an RF sensing (RFS) request. This RFS request may be associated with performing sensing operations to detect an object (such as object 422), determine the velocity of the object, or a combination thereof. The RFS request may include or indicate the object ID, the object's RF signature, or a combination thereof. The object ID, the RF signature, or the combination thereof may include or correspond to object information 409. Although shown as being sent to a single TRP, in other implementations, MF 131 may send the RFS request to multiple TRPs.
[0147] In some implementations, MF 131 may send the RFS request based on or in response to a request such as from an application to detect an object and determine the object's velocity. The application may include a program or software. In some implementations, the application includes the functionality to track or monitor objects or areas. As an illustrative, non-limiting example, the application may be performed by or at a device such as a computer or server, UE 115, base station 105, or TRP 440, 442, 446. In some implementations, the request to determine the object's velocity may be a request to determine the object's true velocity (e.g., not an estimated velocity based on a single Doppler measurement).
[0148] At 1004, TRP 440 sends an Object Detection Indicator (ODI) to MF 131. For example, TRP 440 may send the ODI based on or in response to detecting the RF signature. For illustration, based on the RFS request, TRP 440 may perform a sensing operation and detect the RF signature of the object based on that sensing operation. In some implementations, the ODI may include or indicate the object ID, object detection tag, RSRP level associated with the object, or a combination thereof. Although shown as a single TRP sending the ODI, in other implementations, multiple TRPs, each detecting the RF signature of the object, may send the ODI.
[0149] At 1006, MF 131 selects a set of TRPs and transmits a measurement configuration to each TRP in that set. For example, MF 131 may select the set of TRPs based on received ODIs. In some embodiments, the set of TRPs includes a single TRP. The measurement configuration may include or correspond to configuration information 472, PRS information 407, or a combination thereof. In some embodiments, the measurement configuration includes or indicates the timing or sequencing of measurements to be performed by one or more TRPs in the set. In some embodiments, based on the measurement configuration, TRP 440 may perform one or more sensing operations.
[0150] At 1008, TRP 440 transmits measurement information. For example, this measurement information may include or correspond to sensing information 410 or sensing information 478. In some embodiments, the measurement information includes or indicates a distance value, an AoA measurement, a time value (e.g., a timestamp), or a combination thereof. In some embodiments, the measurement information may not include a time value, and the time value associated with the measurement information may be assumed to be the time associated with the measurement configuration, such as the time when TRP 440 is scheduled or indicated to perform a sensing operation.
[0151] Based on this measurement information, MF 131 can determine the speed of the object. For example, the speed may include or correspond to speed 465. In some specific implementations, MF 131 can calculate the speed (such as the true speed) based on measurements received from multiple TRPs (such as three different TRPs).
[0152] Refer again Figure 4 In some specific implementations, the speed 465 may be determined or estimated based on one or more sensing operations (such as one or more RF sensing operations). For example, the one or more sensing operations may be performed, or the speed 465 may be determined based on the orientation of the object 422. This document refers at least to Figure 11 and Figure 12 Examples of such technologies are further described.
[0153] Reference Figure 11 , Figure 11 It is a conceptual diagram of velocity estimation based on sensing information, supported by one or more aspects. Figure 11 Includes a TRP and a target (e.g., an object). The TRP may include or correspond to TRP 440. The object may include or correspond to object 422.
[0154] The true velocity v of the object can be estimated based on the object's orientation. It should be noted that the AoA relative to the object determined by the TRP is a function of the object's relative position to the TRP. However, the TRP can determine the same AoA for the object when it is in different orientations.
[0155] like Figure 11 As shown, the object is traveling at a velocity v. The TRP can be configured to perform sensing operations (such as RF sensing operations) to determine the estimated velocity based on an estimated Doppler frequency shift associated with the object. When the true velocity is v, the Doppler frequency is an estimated projection of the true velocity, where the estimated velocity (e.g., the projected velocity in the radial direction) is... Based on and object orientation Determine the true speed For example, actual speed. This can be determined based on the following:
[0156] .
[0157] In some specific implementations, the TRP can be configured to determine based on available Doppler frequency shift measurements. Additionally or alternatively, the TRP may determine or receive the orientation of the object. (For example, orientation estimation) Indication. For instance, TRP can perform one or more operations to determine the orientation of an object. (e.g., orientation estimation). For example, the TRP can receive RF signals (such as reflection 476) and can determine the 3D pose of the object based on the RF signals (e.g., 3D pose estimation).
[0158] In some specific implementations, TRP may use machine learning (ML) to determine the 3D pose of the object. For example, TRP may use a pose estimation model or a pose estimation neural network to determine the 3D pose of the object. Additionally or alternatively, TRP may determine the orientation of the object based on its 3D pose (e.g., 3D pose estimation). (For example, orientation estimation). In some specific implementations, TRP can use machine learning (ML) to determine the orientation of objects. For example, TRP can use orientation estimation models or orientation estimation neural networks to determine the orientation of objects. TRP can be based on and object orientation (For example, orientation estimation) to determine velocity.
[0159] In some specific implementations, TRP may include or indicate speed v, ,orientation An indicator, or a combination thereof, is sent to core network 130 or management function 131. This indicator may include or correspond to sensing information 478. Core network 130 or management function 131 may determine a speed (e.g., a final speed), such as speed 465, based on sensing information received from one or more TRPs (e.g., 478). Using information from multiple TRPs may improve the accuracy of the speed determination performed by core network 130 or management function 131. In some specific implementations, the final speed value may be an average speed value, a maximum speed value, a minimum speed value, a median speed value, or a combination thereof.
[0160] Figure 12 This is a ladder diagram illustrating an example of velocity estimation based on sensed information according to various aspects of this disclosure. For example... Figure 12 As shown, Figure 12 The ladder diagram system 1200 includes MF 131 and TRP 440. MF 131 and TRP 440 may include one or more components and are configured to perform one or more operations, as referenced. Figures 1 to 4 As described. System 1200 may include or correspond to wireless communication system 100 or 400. Although Figure 12 A single TRP 440 is depicted, but system 1200 may include more than one TRP.
[0161] refer to Figure 12 During operation of system 1200, at 1202, MF 131 sends an RF sensing (RFS) request. This RFS request may be associated with performing sensing operations to detect an object (such as object 422), determine the velocity of the object, or a combination thereof. The RFS request may include or indicate the object's object ID, the object's RF signature, or a combination thereof. The object ID, the RF signature, or the combination thereof may include or correspond to object information 409. Although shown as being sent to a single TRP, in other implementations, MF 131 may send the RFS request to multiple TRPs.
[0162] In some implementations, MF 131 may send the RFS request based on or in response to a request such as from an application to detect an object and determine the object's velocity. The application may include a program or software. In some implementations, the application includes the functionality to track or monitor objects or areas. As an illustrative, non-limiting example, the application may be performed by or at a device such as a computer or server, UE 115, base station 105, or TRP 440, 442, 446. In some implementations, the request to determine the object's velocity may be a request to determine the object's true velocity (e.g., not an estimated velocity based on a single Doppler measurement).
[0163] At 1204, TRP 440 sends an Object Detection Indicator (ODI) to MF 131. For example, TRP 440 may send the ODI based on or in response to detecting the RF signature. For illustration, based on the RFS request, TRP 440 may perform a sensing operation and detect the RF signature of the object based on that sensing operation. In some implementations, the ODI may include or indicate the object ID, object detection tag, RSRP level associated with the object, or a combination thereof. Although shown as a single TRP sending the ODI, in other implementations, multiple TRPs, each detecting the RF signature of the object, may send the ODI.
[0164] At 1206, MF 131 selects a set of TRPs and transmits a measurement configuration to each TRP in that set. For example, MF 131 may select the set of TRPs based on received ODIs. In some embodiments, the set of TRPs includes a single TRP. The measurement configuration may include or correspond to configuration information 472, PRS information 407, or a combination thereof. In some embodiments, the measurement configuration includes or indicates the timing or sequencing of measurements to be performed by one or more TRPs in the set. Additionally or alternatively, the measurement configuration may include or indicate orientation information, such as orientation information 456. This orientation information may include or indicate a pose estimation model or pose estimation neural network, an orientation estimation model or orientation estimation neural network, or a combination thereof.
[0165] In some implementations, based on this measurement configuration, the TRP 440 may perform one or more sensing operations. Additionally or alternatively, the TRP 440 may perform orientation estimation, determination or estimation of the velocity of an object, or a combination thereof. In some implementations, the velocity determined or estimated by the TRP 440 may be the actual velocity.
[0166] At 1208, TRP 440 sends a speed value, such as an estimated speed, to MF 131. MF 131 may receive one or more speed values (e.g., one or more estimated speed values) and may be configured to calculate a final speed value based on the one or more speed values. The final speed value may include or correspond to speed 465. In some specific implementations, the final speed value may be an average speed value, a maximum speed value, a minimum speed value, a median speed value, or a combination thereof.
[0167] Figure 13 This is a flowchart illustrating an example process 1300 for speed estimation based on sensed information, supporting one or more aspects. The operation of process 1300 may be performed by network entities (such as core network 130, management function 131, UE 115, base station 105, or TRP 440, 442, 446, or as referenced) Figure 16 The network entity described is used to perform this operation. For example, the example operation of process 1300 enables the network entity to support velocity estimation based on sensed information.
[0168] At box 1302, the network entity receives Doppler information and sensing information indicating the distance associated with an object from each of a plurality of TRPs. The plurality of TRPs includes or corresponds to TRPs 440, 442, or 446. The sensing information may include or correspond to sensing information 410 or sensing information 478. In some embodiments, the sensing information from each of the plurality of TRPs includes or indicates an angle. Additionally or alternatively, the Doppler information may include or indicate phase, Doppler measurements, or a combination thereof.
[0169] At box 1304, the network entity determines the velocity of the object based on the sensing information received from the plurality of TRPs. This velocity may include or correspond to velocity 465. The object may include or correspond to object 422.
[0170] In some implementations, the network entity determines the phase indicated by the Doppler information included in the sensing information received from a first TRP out of the plurality of TRPs. The network entity can then calculate the Doppler measurement associated with the first TRP based on this phase.
[0171] In some implementations, the network entity associates different distances from the sensing information from the plurality of TRPs with different objects among a plurality of objects. The plurality of objects includes the object and another object. For example, the plurality of objects may include object 422 or another object. The network entity may determine the location of the object based on a first distance indicated by the sensing information from the plurality of TRPs and associated with the object. Additionally or alternatively, the network entity may determine the location of the other object based on a second distance indicated by the sensing information from the plurality of TRPs and associated with the other object.
[0172] In some implementations, the network entity determines the object's position based on at least one distance indicated by the sensing information from the plurality of TRPs. The network entity may determine the position of each of the plurality of TRPs. The network entity may determine the radial direction of each of the plurality of TRPs based on the position of the TRP and the position of the object. The network entity may associate the radial direction of the TRP with a Doppler measurement based on the Doppler information for each of the plurality of TRPs. In some implementations, the radial direction of the TRP includes the velocity measurement direction of the TRP. In some implementations, to determine the object's velocity, the network entity uses the associated radial direction of each of the plurality of TRPs with the Doppler measurement to perform an LS operation or an MMSE operation. The object's velocity comprises a vector with multiple components.
[0173] In some implementations, the network entity receives a request from an application for the speed of the object. The application may include a program or software. In some implementations, the application includes the functionality to track or monitor objects or areas. As an illustrative, non-limiting example, the application may be executed by or at a device such as a computer or server, UE 115, base station 105, or TRPs 440, 442, 446. The network entity may send configuration information to each of the plurality of TRPs to configure the plurality of TRPs to participate in a sensing session. The configuration information may include or correspond to configuration information 472, PRS information 407, object information, or a combination thereof. In some implementations, the network entity may send a report to the application indicating the speed of the object.
[0174] In some implementations, the network entity sends configuration information to a first TRP among the plurality of TRPs. This configuration information may instruct the first TRP to participate in a sensing session and perform single-site sensing operations. The sensing information received from the first TRP may be based on this single-site sensing operation. Additionally or alternatively, in some implementations, the network entity sends configuration information to a second TRP among the plurality of TRPs. The second TRP may include a TRP pair comprising a sending TRP and a receiving TRP. In some such implementations, the configuration information instructs the second TRP to participate in a sensing session and perform dual-site sensing operations. The sensing information received from the second TRP may be based on this dual-site sensing operation.
[0175] Figure 14This is a flowchart illustrating an example process 1400 that supports speed estimation based on sensed information from one or more aspects. The operation of process 1400 may be performed by network entities (such as core network 130, management function 131, UE 115, base station 105, or TRP 440, 442, 446, or as referenced) Figure 16 The network entity described is used to perform this operation. For example, the example operation of process 1400 enables the network entity to support velocity estimation based on sensed information.
[0176] At box 1402, the network entity sends configuration information to each TRP in the TRP set. This TRP set includes or corresponds to TRPs 440, 442, or 446. The configuration information may include or correspond to configuration information 472, PRS information 407, object information 409, or a combination thereof. The configuration information may include or indicate sensing scheduling information. For example, the sensing scheduling information may include or indicate the timing or sequence in which one or more TRPs perform sensing operations. The TRP set may include a single TRP or multiple TRPs. In implementations where the TRP set includes multiple TRPs, the TRP set may be time-synchronized, share the same coordinate system, or a combination thereof.
[0177] At box 1404, the network entity receives sensing information associated with an object from each TRP in the TRP set. The object may include or correspond to object 422. The sensing information may include or correspond to sensing information 478, sensing information 410, velocity 465, or a combination thereof. In some specific implementations, the sensing information includes or indicates a distance value, angle of arrival, time, or a combination thereof.
[0178] At box 1406, the network entity determines the velocity of the object based on the sensing information received from the TRP set. This velocity may include or correspond to velocity 465.
[0179] In some implementations, the network entity sends a request to one or more TRPs. The request indicates the object ID, the RF signature associated with the object, or a combination thereof. The object ID, the RF signature, or a combination thereof may include or correspond to object information 409. The network entity may receive a response to the request from at least one of the one or more TRPs. The response may indicate the object ID, an object detection indicator, the RSRP level associated with the object, or a combination thereof. The network entity may select the set of TRPs from the one or more TRPs based on the response.
[0180] In some implementations, the TRP set includes a first TRP. To receive the sensing information, the network entity may receive first sensing information from the first TRP. The first sensing information may indicate a first distance value, a first angle of arrival, and a first time. Additionally or alternatively, to receive the sensing information, the network entity may receive second sensing information from the first TRP. The second sensing information may indicate a second distance value, a second angle of arrival, and a second time. The first time is different from the second time.
[0181] In some implementations, the TRP set includes a second TRP. To receive the sensing information, the network entity can receive third sensing information from the second TRP. This third sensing information may indicate a third distance value, a third angle of arrival, and a third time. In some implementations, the third time differs from either the first or the second time. In other implementations, the third time is the same as the first time.
[0182] In some implementations, the network entity receives the first sensing information from the first TRP and the third sensing information from the third TRP. In some such implementations, the third time (indicated by the third sensing information) may be the same as or different from the first time (indicated by the first sensing information).
[0183] Figure 15 This is a flowchart illustrating an example process 1500 that supports speed estimation based on sensed information from one or more aspects. The operation of process 1500 may be performed by network entities (such as core network 130, management function 131, UE 115, base station 105, or TRP 440, 442, 446, or as referenced) Figure 16 The network entity described is used to perform this operation. For example, the example operation of process 1500 enables the network entity to support velocity estimation based on sensed information.
[0184] At box 1502, the network entity sends configuration information to each TRP in the TRP set. This TRP set includes or corresponds to TRPs 440, 442, or 446. The configuration information may include or correspond to configuration information 472, PRS information 407, object information 409, or a combination thereof. The configuration information may indicate a measurement configuration associated with an object and may indicate orientation estimation information. The measurement configuration may include or correspond to configuration information 472, PRS information 407, object information 407, or a combination thereof. The orientation estimation information may include or correspond to orientation information 456. In some implementations, the orientation estimation information may include one or more models. The one or more models include a pose estimation model, an orientation estimation model, or a combination thereof.
[0185] At block 1504, the network entity receives sensing information associated with sensing operations performed based on the measurement configuration from each TRP in the TRP set. This sensing information may include or correspond to transmission information 410, sensing information 478, or velocity 465. The sensing information may indicate the velocity of the object determined based on the orientation estimation information. In some implementations, the network entity determines the final velocity of the object for each TRP in the TRP set based on the velocity indicated by the sensing information received from that TRP.
[0186] In some implementations, the network entity sends a request to one or more TRPs. The request may indicate the object ID, the RF signature associated with the object, or a combination thereof. The object ID, the RF signature, or the combination thereof may include or correspond to object information 409. Additionally or alternatively, the network entity receives a response to the request from at least one of the one or more TRPs. The response may indicate the object ID, an object detection indicator, the RSRP level associated with the object, or a combination thereof. The network entity can then select the set of TRPs from the one or more TRPs based on the response.
[0187] Figure 16 This is a block diagram of an example network entity 1600 supporting speed estimation based on sensed information, according to one or more aspects. Network entity 1600 may include or correspond to core network 130, management function 131, UE 115, base station 105, or TRPs 440, 442, 446. Network entity 1600 may be configured to perform operations, including blocks of procedures 1300, 1400, or 1500. In some specific implementations, network entity 1600 includes references... Figure 1 , Figure 2 or Figure 4 The structure, hardware, and components shown and described for base station 105 or UE 115. As illustrated in the example, network entity 1600 may include controller 240, which operates to execute logical or computer instructions stored in memory 242, and components that control network entity 1600 and provide the characteristics and functionality of network entity 1600. Network entity 1600 transmits and receives signals via wireless radio components 1601a-t and antenna 234a-t under the control of controller 240. Wireless radio components 1601a-t include, as shown in... Figure 2 The various components and hardware illustrated for base station 105 include modulators and demodulators 232a-t, a transmit processor 220, a TX MIMO processor 230, a MIMO detector 236, and a receive processor 238.
[0188] As shown, memory 242 may include configuration information 1602, speed logic 1603, and communication logic 1605. Configuration information 1602 may include or correspond to configuration information 472, PRS information 407, object information 409, or orientation information 456. Speed logic 1603 may be configured to determine the speed of an object, such as speed 465. Communication logic 1605 may be configured to enable communication between network entity 1600 and one or more other devices. Network entity 1600 may receive signals from or send signals to one or more devices, such as base station 105, UE 115, core network 130, management function 131, TRP 440, 442, or 446, or another device.
[0189] Figure 17 This is a flowchart illustrating an example process 1700 that supports speed estimation based on sensing information from one or more aspects. The operation of process 1700 may be performed by a TRP (such as UE 115, base station 105, or TRPs 440, 442, 446, or as referenced). Figure 18 The TRP described is executed. For example, the example operation of process 1700 enables the TRP to support velocity estimation based on sensing information.
[0190] At box 1702, the TRP receives configuration information from a network entity. This network entity may include or correspond to core network 130, management function 131, or another device. The configuration information may include or correspond to configuration information 472, orientation information 456, PRS information 407, or object information 409. The configuration information may indicate a measurement configuration associated with an object and indicate orientation estimation information. The object may include or correspond to object 422. The measurement configuration may include or correspond to PRS information 407 or object information 409. The orientation estimation information may include or correspond to orientation information 456. In some implementations, the orientation estimation information may include one or more models. These one or more models include a pose estimation model, an orientation estimation model, or a combination thereof.
[0191] At box 1704, the TRP sends an indicator to the network entity associated with a sensing operation performed based on the measurement configuration. This indicator may include or correspond to sensing information 410 or sensing information 478. The indicator may indicate the velocity of the object determined based on the orientation estimation information. This velocity may include or correspond to velocity 465.
[0192] In some implementations, the TRP performs the sensing operation based on the measurement configuration. The TRP can determine the velocity of the object based on the sensing operation. In some implementations, the sensing operation may include transmitting a positioning reference signal and receiving a reflection of the positioning reference signal. The positioning reference signal and the reflection may include or correspond to positioning reference signal 474 and reflection 476, respectively. Additionally or alternatively, the TRP can determine the channel frequency response based on the sensing operation (such as based on the reflection). The TRP can determine a 3D pose estimate of the object based on the orientation estimation information and based on the channel frequency response. For example, the 3D pose estimate may be determined based on a pose estimation model or a pose estimation neural network. The TRP can determine an orientation estimate based on the orientation estimation information and based on the 3D pose estimate. For example, the orientation estimate may be determined based on an orientation estimation model or an orientation estimation neural network. The TRP can calculate the velocity of the object based on the orientation estimate.
[0193] In some implementations, the TRP receives a sensing request from the network entity, the sensing request indicating an object ID, an RF signature associated with the object, or a combination thereof. The object ID, the RF signature, or a combination thereof may include or correspond to object information 409. The TRP may detect the object based on the RF signature. Additionally or alternatively, the TRP may send a response to the sensing request based on the detection of the object. The response may include or correspond to sensing information 478. The response may indicate the object ID, an object detection indicator, a Reference Signal Received Power (RSRP) level associated with the object, or a combination thereof.
[0194] Figure 18 This is a block diagram of an example TRP 1800 that supports speed estimation based on sensed information, according to one or more aspects. TRP 1800 may include or correspond to UE 115, base station 105, or TRP 440, 442, 446. TRP 1800 can be configured to perform operations, including the block of process 1700. In some specific implementations, TRP 1800 includes references... Figure 1 or Figure 2 The structure, hardware, and components shown and described in base station 105 or UE 115. As an illustrative example, TRP 1800 may include controller 240 for executing logical or computer instructions stored in memory 242, and components that control TRP 1800 and provide the characteristics and functionality of TRP 1800. TRP 1800 transmits and receives signals via wireless radio components 1801a-t and antenna 234a-t under the control of controller 240. Wireless radio components 1801a-t include as shown in... Figure 2The various components and hardware illustrated for base station 105 include modulators and demodulators 232a-t, a transmit processor 220, a TX MIMO processor 230, a MIMO detector 236, and a receive processor 238. Additionally or alternatively, signals transmitted or received via the wireless radio component 1801a-t may include sensing signals, such as RF sensing signals.
[0195] As shown, memory 242 may include configuration information 1802, measurement information 1803, and communication logic 1805. Configuration information 1802 may include or correspond to configuration information 472, PRS information 407, object information 409, or orientation information 456. Measurement information 1803 may include or correspond to transmission information 410, sensing information 478, or speed 465. Communication logic 1805 may be configured to enable communication between TRP 1800 and one or more other devices. TRP 1800 may receive signals from or send signals to one or more devices, such as base station 105, UE 115, core network 130, management function 131, TRP 440, 442, or 446, or another device.
[0196] Note that this is for reference only. Figures 13 to 15 or Figure 17 The described one or more boxes (or operations) may be combined with one or more boxes (or operations) described in another drawing with reference to the accompanying drawings. For example, Figure 13 One or more boxes (or operations) can be connected with Figure 14 Combine one or more boxes (or operations). As another example, with Figure 13 or Figure 14 One or more associated boxes can be connected with and Figure 15 A combination of one or more associated boxes. As another example, with... Figure 13 , Figure 14 or Figure 15 One or more associated boxes can be connected with and Figure 17 A combination of one or more associated boxes. As another example, with... Figures 13 to 15 or Figure 17 One or more associated boxes can be combined with Figures 1 to 4 , Figure 10 or Figure 12 A combination of one or more related boxes (or operations). Additionally or alternatively, see above for reference. Figures 1 to 4 One or more operations described can be compared with the reference Figure 16 or Figure 18 The described combination of one or more operations.
[0197] In one or more aspects, techniques for supporting velocity estimation based on sensed information may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a first aspect, techniques for supporting velocity estimation based on sensed information may include: receiving Doppler information and sensed information indicating the distance associated with an object from each of a plurality of TRPs. The technique may also include: determining the velocity of the object based on the sensed information received from the plurality of TRPs. In some examples, the technique of the first aspect may be implemented in a method or process. In some other examples, the technique of the first aspect may be implemented in a communication device (which may include a network entity or a component of a network entity). In some examples, the communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon, which, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally or alternatively, the wireless communication device may include an interface (e.g., a communication interface) comprising a transmitter, a receiver, or a combination thereof. Additionally or alternatively, the wireless communication device may include one or more components configured to perform the operations described herein.
[0198] In a second aspect, in conjunction with the first aspect, the sensing information from each of the plurality of TRPs includes an angle.
[0199] In a third aspect, in conjunction with the first or second aspect, the technology also includes: the Doppler information indicating phase, Doppler measurement, or a combination thereof.
[0200] In the fourth aspect, in conjunction with one or more of the first to third aspects, the network entity includes user equipment, network, or management functions.
[0201] In a fifth aspect, in conjunction with one or more of the first to fourth aspects, the technology further includes: determining, based on the sensing information received from a first TRP of the plurality of TRPs, a phase indicated by the Doppler information included in the sensing information received from the first TRP.
[0202] In a sixth aspect, in conjunction with the fifth aspect, the technique also includes: calculating a Doppler measurement associated with the first TRP based on the phase.
[0203] In a seventh aspect, in conjunction with one or more of the first to sixth aspects, the technology further includes: associating different distances of the sensing information from the plurality of TRPs with different objects among a plurality of objects, the plurality of objects including the object and another object.
[0204] In an eighth aspect, in conjunction with the seventh aspect, the technology further includes: determining the location of the object based on a first distance indicated by the sensing information from the plurality of TRPs and associated with the object.
[0205] In a ninth aspect, in conjunction with the eighth aspect, the technology further includes: determining the location of the other object based on a second distance indicated by the sensing information from the plurality of TRPs and associated with the other object.
[0206] In a tenth aspect, in conjunction with one or more of the first to fourth aspects, the technology further includes: determining the location of the object based on at least one distance indicated by the sensing information from the plurality of TRPs.
[0207] In the eleventh aspect, in conjunction with the tenth aspect, the technique also includes: determining the location of each of the plurality of TRPs.
[0208] In a twelfth aspect, in conjunction with the eleventh aspect, the technique further includes: determining the radial direction of each of the plurality of TRPs based on the location of the TRP and the location of the object.
[0209] In a thirteenth aspect, in conjunction with the twelfth aspect, the technique further includes: for each of the plurality of TRPs, associating the radial direction of the TRP with a Doppler measurement based on the Doppler information.
[0210] In the fourteenth aspect, in conjunction with the thirteenth aspect, the radial direction of the TRP includes the velocity measurement direction of the TRP.
[0211] In the fifteenth aspect, in conjunction with the fourteenth aspect, in order to determine the velocity of the object, the technique further includes performing an LS operation or an MMSE operation using radial direction and Doppler measurements associated with each of the plurality of TRPs.
[0212] In the sixteenth aspect, in conjunction with the sixteenth aspect, the velocity of the object comprises a vector having multiple components.
[0213] In the seventeenth aspect, in conjunction with one or more of the first to sixteenth aspects, the technology also includes: receiving a request from the application for the speed of the object.
[0214] In the eighteenth aspect, in conjunction with the seventeenth aspect, the technology further includes: sending configuration information to each of the plurality of TRPs to configure the plurality of TRPs to participate in a sensing session.
[0215] In the nineteenth aspect, in conjunction with the eighteenth aspect, the technology also includes: sending a report to the application indicating the speed of the object.
[0216] In the twentieth aspect, in conjunction with one or more of the first to nineteenth aspects, the technology further includes: sending configuration information to the first TRP of the plurality of TRPs.
[0217] In the twentieth aspect, in conjunction with the twentieth aspect, the configuration information instructs the first TRP to participate in a sensing session and perform single-station sensing operations.
[0218] In the twentieth aspect, in conjunction with the twentieth aspect, the sensing information received from the first TRP is based on the single-station sensing operation.
[0219] In the twentieth aspect, in conjunction with one or more of the first to nineteenth aspects, the technology further includes: sending configuration information to a second TRP among the plurality of TRPs.
[0220] In the twentieth aspect, in conjunction with the twentieth aspect, the second TRP is a TRP pair comprising a sending TRP and a receiving TRP.
[0221] In the twentieth aspect, in conjunction with the twentieth aspect, the configuration information instructs the second TRP to participate in a sensing session and perform dual-station sensing operations.
[0222] In the twentieth aspect, in conjunction with the twentieth aspect, the sensing information received from the second TRP is based on the dual-station sensing operation.
[0223] In one or more aspects, techniques for supporting speed estimation based on sensed information may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a twenty-seventh aspect, techniques for supporting speed estimation based on sensed information may include: sending configuration information to each TRP in a set of TRPs. The configuration information indicates sensed scheduling information. The technique may also include: receiving sensed information associated with an object from each TRP in the set of TRPs. The sensed information indicates a distance value, angle of arrival, and time. The technique may also include: determining the speed of the object based on the sensed information received from the set of TRPs. In some examples, the technique of the twenty-seventh aspect may be implemented in a method or process. In some other examples, the technique of the twenty-seventh aspect may be implemented in a communication device (which may include a network entity or a component of a network entity). In some examples, the communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the communication device. In some examples, the memory device includes a non-transitory computer-readable medium storing program code thereon, which, when executed by a processing unit, is configured to cause a wireless communication device to perform the operations described herein. Additionally or alternatively, the wireless communication device may include an interface (e.g., a communication interface) comprising a transmitter, a receiver, or a combination thereof. Additionally or alternatively, the wireless communication device may include one or more components configured to perform the operations described herein.
[0224] In the twentieth aspect, in conjunction with the twentieth aspect, the technology also includes: sending a request to one or more TRPs.
[0225] In the twenty-ninth aspect, in conjunction with the twenty-eighth aspect, the request indicates the object ID of the object, the RF signature associated with the object, or a combination thereof.
[0226] In the thirtieth aspect, in conjunction with the twenty-eighth or twenty-ninth aspect, the technology further includes: receiving a response to the request from at least one of the one or more TRPs.
[0227] In the thirty-first aspect, in conjunction with the thirtieth aspect, the response indicates the object ID, the object detection indicator, and the RSRP level associated with the object.
[0228] In the thirty-second aspect, in conjunction with the thirty-first aspect, the technology also includes: selecting the set of TRPs from the one or more TRPs based on the response.
[0229] In aspect thirty-three, in conjunction with one or more of aspects twenty-seven through thirty-two, the set of TRPs includes a single TRP, and the network entity includes core network or management functions or a combination thereof.
[0230] In the thirty-fourth aspect, in conjunction with one or more of the twenty-seventh to thirty-second aspects, the set of TRPs includes the first TRP.
[0231] In the thirty-fifth aspect, in conjunction with the thirty-fourth aspect, in order to receive the sensing information, the technology further includes: receiving first sensing information from the first TRP.
[0232] In the thirty-sixth aspect, in conjunction with the thirty-fifth aspect, the first sensing information indicates a first distance value, a first angle of arrival, and a first time.
[0233] In the thirty-seventh aspect, in conjunction with the thirty-sixth aspect, in order to receive the sensing information, the technology further includes: receiving second sensing information from the first TRP.
[0234] In the thirty-eighth aspect, in conjunction with the thirty-seventh aspect, the second sensing information indicates a second distance value, a second angle of arrival, and a second time.
[0235] In the thirty-ninth aspect, in conjunction with the thirty-eighth aspect, the first time is different from the second time.
[0236] In the fortieth aspect, in conjunction with the thirty-eighth or thirty-ninth aspect, the set of TRPs includes a second TRP.
[0237] In the forty-first aspect, in conjunction with the forty-first aspect, in order to receive the sensing information, the technology further includes: receiving third sensing information from the second TRP.
[0238] In aspect forty-two, in conjunction with aspect forty-one, the third sensing information indicates a third distance value, a third angle of arrival, and a third time.
[0239] In aspect 43, in conjunction with aspect 42, the third time is different from the first time or the second time.
[0240] In aspect forty-four, in conjunction with aspect thirty-six, the set of TRPs includes a second TRP.
[0241] In the forty-fifth aspect, in conjunction with the forty-fourth aspect, in order to receive the sensing information, the technology further includes: receiving third sensing information from the second TRP.
[0242] In the forty-sixth aspect, in conjunction with the forty-fifth aspect, the third sensing information indicates a third distance value, a third angle of arrival, and a third time.
[0243] In the forty-seventh aspect, in conjunction with the forty-sixth aspect, the third time is the same as the first time.
[0244] In aspect forty-eight, in conjunction with aspect forty-six, this third time differs from this first time.
[0245] In aspect 49, in conjunction with one or more aspects from aspect 27 to aspect 48, the TRP set is time-synchronized, shares the same coordinate system, or a combination thereof.
[0246] In one or more aspects, techniques for supporting speed estimation based on sensed information may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a fiftieth aspect, techniques for supporting speed estimation based on sensed information may include: sending configuration information to each TRP in a set of TRPs. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The technique may also include: receiving sensed information from each TRP in the set of TRPs associated with a sensing operation performed based on the measurement configuration. The sensed information indicates the speed of the object determined based on the orientation estimation information. In some examples, the technique of the fiftieth aspect may be implemented in a method or process. In some other examples, the technique of the fiftieth aspect may be implemented in a communication device (which may include a network entity or a component of a network entity). In some examples, the communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the communication device. In some examples, the memory device includes a non-transitory computer-readable medium storing program code thereon, which, when executed by a processing unit, is configured to cause a wireless communication device to perform the operations described herein. Additionally or alternatively, the wireless communication device may include an interface (e.g., a communication interface) comprising a transmitter, a receiver, or a combination thereof. Additionally or alternatively, the wireless communication device may include one or more components configured to perform the operations described herein.
[0247] In the fifty-first aspect, in conjunction with the fifty-first aspect, the technique further includes: determining the final velocity of the object for each TRP in the set of TRPs based on the velocity indicated by the sensing information received from the TRP.
[0248] In aspect 52, in conjunction with aspect 50 or 51, the orientation estimation information includes one or more models.
[0249] In aspect 53, in conjunction with aspect 52, the one or more models include a pose estimation model, an orientation estimation model, or a combination thereof.
[0250] In aspect 54, in conjunction with one or more aspects 50 to 53, the technology also includes: sending a request to one or more TRPs.
[0251] In aspect 55, in conjunction with aspect 54, the request indicates the object ID of the object, the RF signature associated with the object, or a combination thereof.
[0252] In aspect 56, in conjunction with aspect 54 or 55, the technology further includes: receiving a response to the request from at least one of the one or more TRPs.
[0253] In aspect 57, in conjunction with aspect 56, the response indicates the object ID, the object detection indicator, and the RSRP level associated with the object.
[0254] In aspect 58, in conjunction with aspect 57, the technology also includes: selecting the set of TRPs from the one or more TRPs based on the response.
[0255] In aspect 59, in conjunction with one or more aspects from aspects 50 to 58, the TRP set includes a single TRP.
[0256] In one or more aspects, techniques for supporting speed estimation based on sensed information may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a sixtieth aspect, techniques for supporting speed estimation based on sensed information may include: receiving configuration information from a network entity. The configuration information indicates a measurement configuration associated with an object and indicates orientation estimation information. The technique may also include: sending to the network entity an indicator associated with a sensing operation performed based on the measurement configuration. The indicator indicates the speed of the object determined based on the orientation estimation information. In some examples, the technique of the sixtieth aspect may be implemented in a method or process. In some other examples, the technique of the sixtieth aspect may be implemented in a wireless communication device (such as a TRP, which may include a UE or a component of a UE, or a base station or a component of a base station). In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium thereon storing program code configured, when executed by a processing unit, to cause a wireless communication device to perform the operations described herein. Additionally or alternatively, the wireless communication device may include an interface (e.g., a wireless communication interface) comprising a transmitter, a receiver, or a combination thereof. Additionally or alternatively, the wireless communication device may include one or more components configured to perform the operations described herein.
[0257] In the sixty-first aspect, in conjunction with the sixtieth aspect, the orientation estimation information includes one or more models.
[0258] In aspect sixty-two, in conjunction with aspect sixty-one, the one or more models include a pose estimation model, an orientation estimation model, or a combination thereof.
[0259] In aspect sixty-three, in conjunction with one or more of aspects sixty to sixty-two, the technology further includes: performing the sensing operation based on the measurement configuration.
[0260] In the sixty-fourth aspect, in conjunction with the sixty-third aspect, the technology also includes: determining the speed of the object based on the sensing operation.
[0261] In aspect sixty-five, and in conjunction with one or more of aspects sixty to sixty-four, the technique further includes: determining the channel frequency response based on the sensing operation.
[0262] In the sixty-sixth aspect, in conjunction with the sixty-fifth aspect, the technique further includes: determining a 3D pose estimate of the object based on the orientation estimation information and based on the channel frequency response.
[0263] In the sixty-seventh aspect, in conjunction with the sixty-sixth aspect, the technique further includes: determining an orientation estimate based on the orientation estimation information and based on the 3D pose estimation.
[0264] In aspect sixty-eight, in conjunction with aspect sixty-seven, the technique further includes: calculating the velocity of the object based on the orientation estimate.
[0265] In aspect sixty-nine, and in conjunction with one or more of aspects sixty to sixty-eight, the technology further includes: receiving a sensing request from the network entity, the sensing request indicating an object ID of the object, an RF signature associated with the object, or a combination thereof.
[0266] In the seventieth aspect, in conjunction with the sixty-ninth aspect, the technology also includes: detecting the object based on the RF signature.
[0267] In the seventy-first aspect, in conjunction with the seventy-second aspect, the technology also includes: sending a response to the sensing request based on the detection of the object.
[0268] In aspect seventy-two, in conjunction with aspect seventy-one, the response indicates the object ID, the object detection indicator, the RSRP level associated with the object, or a combination thereof.
[0269] 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 mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.
[0270] This article is about Figures 1 to 18 The components, functional blocks, and modules described include processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software code, firmware code, and so on, or any combination thereof. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. Furthermore, the features discussed herein can be implemented via dedicated processor circuitry, via executable instructions, or a combination thereof.
[0271] Those skilled in the art will further understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein is merely illustrative, and that components, methods, or interactions of various aspects of this disclosure may be combined or performed in ways other than those illustrated and described herein.
[0272] The various exemplary logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been broadly described in terms of functionality and illustrated in the various exemplary components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0273] Hardware and data processing means for implementing the various exemplary logic units, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. In some embodiments, the processor may 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. In some embodiments, specific processes and methods may be performed by circuitry specific to a given function.
[0274] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.
[0275] If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted through a computer-readable medium. The processes of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that can be implemented to transfer a computer program from one location to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and accessible to a computer. Additionally, any connection may be appropriately referred to as a computer-readable medium. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically reproduce data, while optical discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operation of a method or algorithm may reside as a set of code and instructions or any combination of code and instructions on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.
[0276] Various modifications to the specific embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other specific embodiments without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the specific embodiments shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.
[0277] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positions on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.
[0278] Certain features described in this specification in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as operating in certain combinations and even originally claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.
[0279] Similarly, although operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in the indicated specific order or sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the drawings may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be combined with the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any illustrated operation. In some contexts, multitasking and parallel processing are advantageous. Moreover, the separation of the various system components in the embodiments described above should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other embodiments also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.
[0280] As used herein (including the claims), the term “or” in a list of two or more items means that any one of the listed items may be used alone, or any combination of two or more listed items may be used. For example, if a composition is described as containing component A, B, or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Furthermore, as used herein (including the claims), “or” in a list of items beginning with “at least one of” indicates a separate list, such that a list such as “at least one of A, B, or C” refers to A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these items. The term “substantially” is defined as being substantially, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed specific implementation, the term “substantially” may be used in place of “[percentage]” for the specified content, where the percentage includes 0.1%, 1%, 5% or 10%.
[0281] The prior description of this disclosure is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for wireless communication performed by a network entity, the method comprising: Doppler information and sensing information indicating the distance associated with an object are received from each of the multiple transmit / receive points (TRPs). as well as The speed of the object is determined based on the sensing information received from the plurality of TRPs.
2. The method according to claim 1, wherein: The sensing information from each of the plurality of TRPs includes angles. The Doppler information indicates phase, Doppler measurement, or a combination thereof. The network entities include user equipment, networks, or management functions, or Their combination.
3. The method according to claim 1, further comprising: The phase indicated by the Doppler information included in the sensing information received from the first TRP of the plurality of TRPs is determined based on the sensing information received from the first TRP; as well as The Doppler measurement associated with the first TRP is calculated based on the phase.
4. The method according to claim 1, further comprising: The sensing information from the plurality of TRPs is associated with different distances with different objects among a plurality of objects, the plurality of objects including the object and another object; The location of the object is determined based on a first distance indicated by the sensing information from the plurality of TRPs and associated with the object; as well as The location of the other object is determined based on a second distance indicated by the sensing information from the plurality of TRPs and associated with the other object.
5. The method according to claim 1, further comprising: The location of the object is determined based on at least one distance indicated by the sensing information from the plurality of TRPs; For each of the plurality of TRPs, determine the location of the TRP; as well as The radial direction of a TRP is determined for each of the plurality of TRPs based on the position of the TRP and the position of the object.
6. The method according to claim 5, further comprising: For each of the plurality of TRPs, the radial direction of the TRP is associated with a Doppler measurement based on the Doppler information, and The radial direction of the TRP includes the velocity measurement direction of the TRP.
7. The method according to claim 6, wherein: Determining the velocity of the object includes performing a least squares (LS) operation or a minimum mean square error (MMSE) operation using radial direction and Doppler measurements associated with each of the plurality of TRPs, and The velocity of the object comprises a vector having multiple components.
8. The method according to claim 1, further comprising: Receive a request for the speed of the object from the application; Configuration information is sent to each of the plurality of TRPs to configure the plurality of TRPs to participate in the sensing session; as well as Send a report to the application indicating the speed of the object.
9. The method according to claim 1, further comprising: Send configuration information to the first TRP among the plurality of TRPs. The configuration information indicates that the first TRP should participate in the sensing session and perform single-site sensing operations; and The sensing information received from the first TRP is based on the single-station sensing operation.
10. The method according to claim 1, further comprising: Send configuration information to the second TRP among the plurality of TRPs. The second TRP is a TRP pair that includes a sending TRP and a receiving TRP. The configuration information indicates that the second TRP should participate in the sensing session and perform dual-station sensing operations; and The sensing information received from the second TRP is based on the dual-station sensing operation.
11. A method for wireless communication performed by a network entity, the method comprising: Configuration information, which indicates sensing scheduling information, is sent to each TRP in the set of Transmitting / Receiving Points (TRPs). Receive sensing information associated with the object from each TRP in the TRP set, the sensing information indicating distance value, angle of arrival, and time; as well as The speed of the object is determined based on the sensing information received from the TRP set.
12. The method according to claim 11, further comprising: Send a request to one or more TRPs, the request indicating the object ID of the object, the radio frequency (RF) signature associated with the object, or a combination thereof; Receive a response to the request from at least one of the one or more TRPs, the response indicating the object ID, object detection indicator, and RSRP level associated with the object; as well as The TRP set is selected from the one or more TRPs based on the response.
13. The method according to claim 11, wherein: The TRP set includes a single TRP. The network entity includes core network or management functions, or Their combination.
14. The method of claim 11, wherein: The TRP set includes a first TRP, and Receiving the sensing information includes receiving first sensing information from the first TRP, the first sensing information indicating a first distance value, a first angle of arrival, and a first time.
15. The method of claim 14, wherein: Receiving the sensing information includes receiving second sensing information from the first TRP, the second sensing information indicating a second distance value, a second angle of arrival, and a second time. The first time is different from the second time.
16. The method of claim 15, wherein: The TRP set includes a second TRP. Receiving the sensing information includes receiving third sensing information from the second TRP, the third sensing information indicating a third distance value, a third angle of arrival, and a third time, and The third time is different from the first time or the second time.
17. The method of claim 14, wherein: The TRP set includes a second TRP, and Receiving the sensing information includes receiving third sensing information from the second TRP, the third sensing information indicating a third distance value, a third angle of arrival, and a third time.
18. The method of claim 17, wherein the third time is the same as the first time.
19. The method of claim 17, wherein the third time is different from the first time.
20. The method of claim 11, wherein the TRP set is time-synchronized, shares the same coordinate system, or a combination thereof.
21. A method for wireless communication performed by a network entity, the method comprising: Configuration information is sent to each TRP in the set of Transmitting / Receiving Points (TRPs), the configuration information indicating the measurement configuration associated with the object and indicating orientation estimation information; as well as Sensing information associated with a sensing operation performed based on the measurement configuration is received from each TRP in the TRP set, the sensing information indicating the velocity of the object determined based on the orientation estimation information.
22. The method according to claim 21, further comprising: The final velocity of the object is determined for each TRP in the set of TRPs based on the velocity indicated by the sensing information received from the TRP.
23. The method of claim 21, wherein the orientation estimation information comprises one or more models, the one or more models comprising a pose estimation model, an orientation estimation model, or a combination thereof.
24. The method according to claim 21, further comprising: Send a request to one or more TRPs, the request indicating the object ID of the object, the RF signature associated with the object, or a combination thereof; Receive a response to the request from at least one of the one or more TRPs, the response indicating the object ID, object detection indicator, and reference signal received power (RSRP) level associated with the object; as well as The TRP set is selected from the one or more TRPs based on the response.
25. The method of claim 21, wherein the TRP set comprises a single TRP.
26. A method for wireless communication performed by a transmitting / receiving point (TRP), the method comprising: Receive configuration information from a network entity, the configuration information indicating the measurement configuration associated with the object and indicating orientation estimation information; as well as Send an indicator associated with a sensing operation performed based on the measurement configuration to the network entity, the indicator indicating the velocity of the object determined based on the orientation estimation information.
27. The method of claim 26, wherein the orientation estimation information comprises one or more models, the one or more models comprising a pose estimation model, an orientation estimation model, or a combination thereof.
28. The method according to claim 26, further comprising: The sensing operation is performed based on the measurement configuration; as well as The speed of the object is determined based on the sensing operation.
29. The method according to claim 26, further comprising: The channel frequency response is determined based on the sensing operation; The 3D pose estimation of the object is determined based on the orientation estimation information and the channel frequency response. The orientation estimate is determined based on the orientation estimation information and the 3D pose estimation. as well as The velocity of the object is calculated based on the orientation estimate.
30. The method according to claim 26, further comprising: Receive a sensing request from the network entity, the sensing request indicating the object ID of the object, the radio frequency (RF) signature associated with the object, or a combination thereof; The object is detected based on the RF signature; and A response to the sensing request is sent based on the detection of the object, the response indicating the object ID, the object detection indicator, the reference signal received power (RSRP) level associated with the object, or a combination thereof.
