Sensitivity time control signaling

Abstract

A sensing method includes implementing, at a UE, a sensitivity time control profile to change a gain applied over time to a sensing signal received by the UE; and measuring the sensing signal to obtain a sensing signal measurement; wherein the method comprises at least one of: obtaining a sensitivity time control profile based on a sensitivity time control message received by the UE from a network entity; or sending a sensing report from the UE to the network entity, the sensing report indicating that the measurement of the sensing signal and the sensitivity time control have been implemented to obtain the sensing signal measurement.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Patent Application No. 18 / 477,071, filed September 28, 2023, entitled “SENSITIVITY TIME CONTROLSIGNGALING,” which has been assigned to the assignee of this application, and the entire contents of which are incorporated herein by reference for all purposes. Background Technology

[0003] Wireless communication systems have gone through several generations of development, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data wireless service with internet capabilities, and fourth-generation (4G) services (e.g., LTE or WiMax). ® ), and fifth-generation (5G) services (e.g., 5G New Radio (NR), etc.). Currently, there are many different types of wireless communication systems in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog advanced mobile phone systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), Global System for Mobile Access (GSM) TDMA variants, etc.

[0004] The fifth-generation (5G) mobile standard demands higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide tens of megabits per second (Mbps) of data to each of tens of thousands of users, or 1 gigabit per second (Gbps) to dozens of workers on an office floor. To support large-scale sensor deployments, it should support hundreds of thousands of simultaneous connections. Therefore, the spectral efficiency of 5G mobile communications should be significantly improved compared to the current 4G standard. Furthermore, signaling efficiency should be improved, and latency should be significantly reduced compared to the current standard.

[0005] Obtaining the location of a mobile device accessing a wireless network can be used for many applications, including emergency calls, personal navigation, consumer asset tracking, locating friends or family members, etc. Existing positioning methods include those based on measuring radio signals transmitted from various devices or entities, including satellite vehicles (SVs) in wireless networks and terrestrial radio sources such as base stations and access points. Standardization for 5G wireless networks is expected to include support for various positioning methods that can utilize reference signals transmitted by base stations for location determination in a manner similar to how LTE wireless networks currently use Positioning Reference Signals (PRS) and / or Cell-Specific Reference Signals (CRS).

[0006] Radio frequency (RF) sensing is used to determine information about a device's environment. In RF sensing, an RF signal (called the sensing signal) is transmitted by a transmitter, reflected from a target object, and received by a receiver. The sensing signal can be used for sensing and one or more other purposes, such as communication. The received signal can be used to determine characteristics of the target object, such as its location, size, material, movement, etc. RF sensing can be implemented using various technologies such as radar, radio frequency identification (RFID), and / or wireless sensor networks. In RFID technology, RF signals can be used for identification and / or tracking. Tags or transponders containing unique identifiers can use RF signals to communicate with RFID readers. By placing RFID tags on objects, objects can be identified, tracked, and managed. RF sensing can be used in a variety of applications, such as automotive (collision avoidance, autonomous driving, adaptive cruise control, etc.), surveillance and security, object detection, inventory management, drug management, environmental monitoring, etc. Summary of the Invention

[0007] An example UE (User Equipment) includes: one or more memories; one or more transceivers configured to receive a sense signal; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors configured to: implement a sensitivity time control profile to change the gain applied to the sense signal by the one or more transceivers over time; and measure the sense signal to obtain a sense signal measurement; wherein the one or more processors are at least one of: being configured to obtain the sensitivity time control profile based on a sensitivity time control message received from a network entity via the one or more transceivers; or being configured to send a sense report to the network entity via the one or more transceivers, the sense report indicating the measurement of the sense signal and whether sensitivity time control has been implemented to obtain the sense signal measurement.

[0008] An example sensing method includes: implementing a sensitivity time control profile at a UE (User Equipment) to change the gain applied over time to a sensing signal received by the UE; and measuring the sensing signal to obtain a sensing signal measurement; wherein the method includes at least one of: obtaining a sensitivity time control profile based on a sensitivity time control message received by the UE from a network entity; or sending a sensing report from the UE to the network entity indicating that the sensing signal measurement and sensitivity time control have been implemented to obtain the sensing signal measurement.

[0009] Another example UE includes: components for implementing a sensitivity time control profile to change the gain applied over time to a sensing signal received by the UE; and components for measuring the sensing signal to obtain a sensing signal measurement; wherein the UE further includes at least one of: components for obtaining a sensitivity time control profile based on a sensitivity time control message received by the UE from a network entity; or components for sending a sensing report from the UE to the network entity, the sensing report indicating that the sensing signal measurement and sensitivity time control have been implemented to obtain the sensing signal measurement.

[0010] An example non-transitory processor-readable storage medium includes processor-readable instructions that cause one or more processors of a UE (User Equipment) to perform the following operations: implement a sensitivity time control profile to change the gain applied over time to a sensed signal received by the UE; and measure the sensed signal to obtain a sensed signal measurement; wherein the storage medium further includes at least one of the following: processor-readable instructions for causing one or more processors of the UE to obtain a sensitivity time control profile based on a sensitivity time control message received by the UE from a network entity; or processor-readable instructions for causing one or more processors of the UE to send a sensed report from the UE to a network entity, the sensed report indicating that the sensed signal measurement and sensitivity time control have been implemented to obtain the sensed signal measurement.

[0011] An example network entity includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being configured to: determine sensitivity time control configuration information indicating at least one of the following: a sensitivity time control profile, a location-corresponding clutter distribution, or one or more criteria that a UE (User Equipment) must meet to achieve sensitivity time control; and transmit the sensitivity time control configuration information to the UE via the one or more transceivers.

[0012] An example method for supporting sensitivity timing control sensed by a UE (User Equipment) includes: determining sensitivity timing control configuration information at a network entity, the sensitivity timing control configuration information indicating at least one of the following: a sensitivity timing control profile, a location-corresponding clutter distribution, or one or more criteria that the UE must satisfy to achieve sensitivity timing control; and transmitting the sensitivity timing control configuration information from the network entity to the UE via one or more transceivers.

[0013] Another example network entity includes: a component for determining sensitivity time control configuration information, which indicates at least one of the following: a sensitivity time control profile, a location-corresponding clutter distribution, or one or more criteria that a UE (User Equipment) must meet to implement sensitivity time control; and a component for transmitting the sensitivity time control configuration information to the UE via one or more transceivers.

[0014] Another example of a non-transitory processor-readable storage medium includes processor-readable instructions that cause one or more processors of a network entity to perform the following operations: determine sensitivity time control configuration information indicating at least one of the following: a sensitivity time control profile, a location-corresponding clutter distribution, or one or more criteria that a UE (User Equipment) must meet to implement sensitivity time control; and transmit the sensitivity time control configuration information to the UE via one or more transceivers. Attached Figure Description

[0015] Figure 1 This is a simplified diagram of an example wireless communication system.

[0016] Figure 2 yes Figure 1 The diagram shows a block diagram of the components of an example user device.

[0017] Figure 3 yes Figure 1 The diagram shows the components of an example send / receive point.

[0018] Figure 4 yes Figure 1 The diagram shows the components of the example server.

[0019] Figure 5 This is a block diagram of user equipment.

[0020] Figure 6 It is a block diagram of network entities.

[0021] Figure 7 This is a block diagram of a single-station sensing system.

[0022] Figure 8This is a block diagram of a dual-station sensing system.

[0023] Figure 9 This is a block diagram of the sensing signal receiver.

[0024] Figure 10 It is a graph showing the change of gain over time in sensitivity time control.

[0025] Figure 11 It is a signal and processing flowchart used to determine the range and / or speed of a target object using radio frequency sensing with sensitivity time control.

[0026] Figure 12 Is as Figure 11 The example shown is an example of the content of the Sensitivity Time Control (STC) capability message in the STC capability table.

[0027] Figure 13 Is as Figure 11 The example shown is an example of an STC configuration information table, representing an example of an STC configuration information message.

[0028] Figure 14 This is a flowchart of the sensing method.

[0029] Figure 15 This is a flowchart of a method for supporting sensitivity time control of sensing by user equipment. Detailed Implementation

[0030] This document discusses techniques for conveying Sensitivity Time Control (STC) information. For example, the STC capability of a User Equipment (UE) may be requested from and / or provided by the UE. Alternatively, STC configuration information may be requested from and / or provided to the UE by a network entity. The STC configuration information may indicate one or more STC profiles with different gains over time, which are to be implemented by the UE (or other devices receiving sensed signals). The STC configuration information may include information that allows the determination of STC profiles (e.g., that allows the derivation of one or more STC profiles and / or the selection of one or more STC profiles from one or more stored STC profiles). Valid STC profiles (e.g., STC profiles that generate one or more accurate sensed measurements) may be reported, and this information is used to provide STC configuration information to reporting entities and / or one or more other entities. However, other configurations / implementations may also be used.

[0031] The items and / or techniques described herein can provide one or more of the following capabilities, as well as others not mentioned: Improved radio frequency (RF) sensing accuracy (e.g., target detection accuracy, target location determination accuracy, and / or target velocity determination accuracy). Improved RF sensing accuracy for different sensing applications, different sensing environments (e.g., different clutter distributions), and / or different target detection conditions (e.g., short-range targets and long-range targets). Improved quality of received RF sensing by mitigating clutter from nearby sources. Improved efficiency of receiver dynamic range and / or avoidance of situations caused by nearby clutter sources. Dynamic adaptation and configuration of the STC applied at the RF sensing receiver, for example, to provide improved RF sensing quality and performance. Other capabilities can be provided, and not every specific embodiment according to this disclosure is required to provide any, let alone all, of the capabilities discussed.

[0032] The description herein can refer to a sequence of actions to be performed, for example, by elements of a computing device. The various actions described herein can be performed by special-purpose circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of both. The sequence of actions described herein can be embodied in a non-transitory computer-readable medium storing a corresponding set of computer instructions that, when executed, will cause the associated processor to perform the functionality described herein. Therefore, the various examples described herein can be embodied in several different forms, all of which fall within the scope of this disclosure, including the claimed subject matter.

[0033] As used herein, the terms “User Equipment” (UE) and “Base Station” are not specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise indicated. Generally, a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset tracking device, Internet of Things (IoT) device, etc.) used to communicate over a wireless communication network. A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Terminal,” “Mobile Station,” “Mobile Equipment,” or variations thereof. Generally, a UE can communicate with a core network via the RAN, and through the core network, a UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for a UE, such as via wired access networks, WiFi, etc. ® Networks (e.g., based on IEEE (Institute of Electrical and Electronics Engineers) 802.11, etc.).

[0034] Depending on the network in which the base station is deployed, the base station can operate according to one of several RATs when communicating with the UE. Examples of base stations include access points (APs), network nodes, NodeBs, evolved NodeBs (eNBs), or generic NodeBs (gNodeBs, gNBs). Furthermore, in some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions.

[0035] The UE can be represented by any of several types of devices, including but not limited to printed circuit (PC) cards, compact flash memory devices, external or internal modems, wireless or wired telephones, smartphones, tablet devices, consumer asset tracking devices, asset tags, etc. The communication link through which the UE can transmit signals to the RAN is called an uplink channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the RAN can transmit signals to the UE is called a downlink or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" can refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0036] As used herein, depending on the context, the term "cell" or "sector" may correspond to one of a plurality of cells of a base station or to the base station itself. The term "cell" may refer to a logical communication entity used to communicate with a base station (e.g., on a carrier) and may be associated with identifiers to distinguish adjacent cells operating via the same or different carriers (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a carrier may support multiple cells and may be configured with different cell types based on different protocol types that can provide access to different types of devices (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). In some examples, the term "cell" may refer to a portion of the geographic coverage area on which a logical entity operates (e.g., a sector).

[0037] refer to Figure 1 Examples of communication system 100 include UE 105, UE 106, radio access network (RAN) (here, fifth-generation (5G) next-generation (NG) RAN (NG-RAN) 135), 5G core network (5GC) 140, and server 150. UE 105 and / or UE 106 can be, for example, an IoT device, a location tracker device, a cellular phone, a vehicle (e.g., a car, truck, bus, ship, etc.), or another device. 5G network can also be referred to as a new radio (NR) network; NG-RAN 135 can be referred to as 5G RAN or NR RAN; and 5GC 140 can be referred to as NG core network (NGC). Standardization of NG-RAN and 5GC is underway within the 3rd Generation Partnership Project (3GPP). Therefore, NG-RAN 135 and 5GC 140 can follow current or future standards from 3GPP for 5G support. NG-RAN 135 can be another type of RAN, such as 3G RAN, 4G Long Term Evolution (LTE) RAN, etc. UE 106 can be configured and coupled similarly to UE 105 to transmit signals to and / or receive signals from similar other entities in system 100, but for simplicity of the figures, in Figure 1Such signaling is not indicated in this document. Similarly, for simplicity, the discussion focuses on UE 105. Communication system 100 may utilize information from a constellation 185 of satellite spacecraft (SVs) 190, 191, 192, 193 from a satellite positioning system (SPS) such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional SPS (such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Navigation Coverage Service (EGNOS), or the Wide Area Augmentation System (WAAS)). Additional components of communication system 100 are described below. Communication system 100 may include additional or optional components.

[0038] like Figure 1 As shown, NG-RAN 135 includes NR nodeBs (gNB) 110a, 110b and next-generation eNodeB (ng-eNB) 114, and 5GC 140 includes Access and Mobility Management Function (AMF) 115, Session Management Function (SMF) 117, Network Entity 116 (including Sensing Entity 118 and Location Management Function (LMF) 120) and Gateway Mobile Location Center (GMLC) 125. gNBs 110a, 110b and ng-eNB 114 are communicatively coupled to each other, each configured to conduct bidirectional wireless communication with UE 105, and each communicatively coupled to AMF 115 and configured to conduct bidirectional communication with AMF. gNBs 110a, 110b and ng-eNB 114 may be referred to as base stations (BS). AMF 115, SMF 117, Network Entity 116 and GMLC 125 are communicatively coupled to each other, and GMLC is communicatively coupled to external client 130. SMF 117 can be used as the initial contact point for Service Control Function (SCF) (not shown) to create, control, and delete media sessions. Base stations (such as gNB 110a, 110b, and / or ng-eNB 114) can be macrocells (e.g., high-power cellular base stations), small cells (e.g., low-power cellular base stations), or access points (e.g., short-range base stations configured to use short-range technologies such as WiFi). ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® ,Bluetooth ® Low power (BLE), Zigbee ®(e.g., one or more of gNB 110a, 110b and / or ng-eNB 114) can be configured to communicate with UE 105 via multiple carriers. Each of gNB 110a, 110b and / or ng-eNB 114 can provide communication coverage for a corresponding geographic area (e.g., cell). Each cell can be divided into multiple sectors based on the base station antennas.

[0039] Figure 1 Generalized examples of various components are provided, wherein any or all of the components may be appropriately utilized, and each component may be repeated or omitted as needed. Specifically, although a UE 105 is illustrated, many UEs (e.g., hundreds, thousands, millions, etc.) may be utilized in communication system 100. Similarly, communication system 100 may include a larger (or smaller) number of SVs (i.e., more or fewer than the four SVs 190-193 shown), gNBs 110a and 110b, ng-eNB 114, AMF 115, external client 130, and / or other components. The illustrated connections connecting the various components in communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, the components may be rearranged, combined, separated, replaced, and / or omitted according to desired functionality.

[0040] Although Figure 1 A 5G-based network is illustrated, but similar network implementations and configurations can be used for other communication technologies such as 3G, Long Term Evolution (LTE), etc. The specific implementations described herein (for 5G technology and / or for one or more other communication technologies and / or protocols) can be used to transmit (or broadcast) directional synchronization signals, receive and measure directional signals at a UE (e.g., UE 105), and / or provide location assistance to UE 105 (via GMLC 125 or other location servers), and / or calculate the location of UE 105 at a location-capable device (such as UE 105, gNB 110a, 110b, or LMF 120) based on measurement parameters received at UE 105 for such directional transmissions. Gateway Mobile Location Center (GMLC) 125, Location Management Function (LMF) 120, Access and Mobility Management Function (AMF) 115, SMF 117, ng-eNB (eNodeB) 114, and gNB (gNodeB) 110a, 110b are examples and may be replaced by or include various other location server functions and / or base station functions in various implementations.

[0041] System 100 is capable of wireless communication because its components can communicate directly or indirectly (at least sometimes using a wireless connection), for example, via gNB 110a, 110b, ng-eNB 114 and / or 5GC 140 (and / or one or more other devices not shown, such as one or more other transceiver base stations). For indirect communication, the communication can be modified during transmission from one entity to another, for example, by changing the header information of data packets, changing the format, etc. UE 105 may include multiple UEs and may be mobile wireless communication devices, but can communicate wirelessly as well as via wired connections. UE 105 can be any of a variety of devices, such as smartphones, tablets, vehicle-based devices, etc., but these are merely examples, as UE 105 does not need to be any of these configurations, and other configurations of UEs can be used. Other UEs may include wearable devices (e.g., smartwatches, smart jewelry, smart glasses, or head-mounted devices, etc.). Other UEs, whether currently existing or developed in the future, may also be used. In addition, other wireless devices (whether mobile or not) can be implemented within system 100 and can communicate with each other and / or with UE 105, gNB 110a, 110b, ng-eNB 114, 5GC 140, and / or external client 130. For example, such other devices may include Internet of Things (IoT) devices, medical devices, home entertainment and / or automation devices, etc. 5GC 140 can communicate with external client 130 (e.g., a computer system), for example, to allow external client 130 (e.g., via GMLC 125) to request and / or receive location information about UE 105.

[0042] UE 105 or other devices can be configured to communicate in various networks and / or for various purposes and / or using various technologies (e.g., 5G, Wi-Fi). ® Communication, multi-frequency Wi-Fi ® Communication, satellite positioning, and one or more types of communication (e.g., GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), LTE (Long Term Evolution), V2X (vehicle-to-everything communication, e.g., V2P (vehicle-to-pedestrian), V2I (vehicle-to-infrastructure), V2V (vehicle-to-vehicle), etc.), IEEE 802.11p, etc.). V2X communication can be cellular (Cellular-V2X (C-V2X)) and / or WiFi. ®(For example, DSRC (Dedicated Short Range Connection)). System 100 can support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals simultaneously on multiple carriers. Each modulated signal can be a Code Division Multiple Access (CDMA) signal, a Time Division Multiple Access (TDMA) signal, an Orthogonal Frequency Division Multiple Access (OFDMA) signal, a Single Carrier Frequency Division Multiple Access (SC-FDMA) signal, etc. Each modulated signal can be transmitted on different carriers and can carry pilot, overhead information, data, etc. UEs 105 and 106 can communicate with each other via UE-to-UE sidelink (SL) communication by transmitting on one or more sidelink (SL) channels (such as the Physical Sidelink Synchronization Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), or Physical Sidelink Control Channel (PSCCH)). Direct device-to-device communication (without a network) is generally referred to as sidelink communication, without limiting the communication to a specific protocol.

[0043] UE 105 may include and / or may be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location Enabled (SUPL) terminal (SET), or some other name. Furthermore, UE 105 may correspond to a cellular phone, smartphone, laptop computer, tablet device, PDA, consumer asset tracking device, navigation device, Internet of Things (IoT) device, health monitor, security system, smart city sensor, smart meter, wearable tracker, or some other portable or mobile device. Typically, although not mandatory, UE 105 may use one or more Radio Access Technologies (RATs) to support wireless communication, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi, etc. ® (Also known as Wi-Fi) ® ),Bluetooth ® (BT), WiMax (Global Microwave Access) ® 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140), etc. UE 105 can use a Wireless Local Area Network (WLAN) to support wireless communication, which can connect to other networks (e.g., the Internet) using, for example, digital subscriber line (DSL) or packet cable. Using one or more of these RATs allows UE 105 (e.g., via elements of 5GC 140) Figure 1(not shown in the image), or possibly via GMLC 125, to communicate with external client 130 and / or allow external client 130 (e.g., via GMLC 125) to receive location information about UE 105.

[0044] UE 105 may include a single entity or may include multiple entities, such as in a personal area network, where the user may employ audio, video, and / or data I / O (input / output) devices, and / or body sensors, as well as separate wired or wireless modems. An estimate of the location of UE 105 may be referred to as location, location estimate, location fixed, fixed, positioning, location estimation, or location fixed, and may be geographic, providing the location coordinates of UE 105 (e.g., latitude and longitude), which may or may not include an elevation component (e.g., height above sea level; height above ground level, floor level, or basement level, or depth below). Alternatively, the location of UE 105 may be expressed as a municipal location (e.g., a postal address or designation of a point or smaller area within a building, such as a specific room or floor). The location of UE 105 may be represented as an area or volume (geographically or municipally defined) within which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of UE 105 can be represented as a relative location, which includes, for example, distance and direction relative to a known location. This relative location can be represented as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to an origin at a known location, which can be, for example, geographically, municipally, or with reference to a point, area, or volume indicated, for example, on a map, floor plan, or building plan. In the description contained herein, the use of the term "location" can include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and (possibly also) z coordinates are typically solved, and then (if necessary) the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level).

[0045] UE 105 can be configured to communicate with other entities using one or more of a variety of technologies. UE 105 can be configured to indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. D2D P2P links can use any suitable D2D radio access technology (RAT) such as LTE Direct (LTE-D), WiFi, etc. ® Direct connection (WiFi) ® -D), Bluetooth ®Support is provided. One or more UEs in a UE group utilizing D2D communication may be located within the geographic coverage area of ​​a Transmit / Receive Point (TRP) (such as one or more of gNB 110a, 110b and / or ng-eNB 114). Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A UE group communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. The TRP can facilitate the scheduling of resources for D2D communication. In other cases, D2D communication may be performed between UEs without involving the TRP. One or more UEs in a UE group utilizing D2D communication may be located within the geographic coverage area of ​​a TRP. Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A UE group communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. TRP can facilitate the scheduling of resources used for D2D communication. In other cases, D2D communication can be performed between UEs without involving TRP.

[0046] Figure 1 The base stations (BS) in NG-RAN 135 shown include NR Node Bs (referred to as gNB 110a and gNB 110b). Each pair of gNBs 110a and 110b in NG-RAN 135 can be interconnected via one or more other gNBs. Access to the 5G network is provided to UE 105 via wireless communication with one or more of the gNBs 110a and 110b. These gNBs can use 5G to provide wireless communication access to the 5GC 140 on behalf of UE 105. Figure 1 In this context, it is assumed that the serving gNB of UE 105 is gNB 110a, but another gNB (e.g., gNB 110b) may act as the serving gNB or as a secondary gNB to provide additional throughput and bandwidth to UE 105 if UE 105 moves to another location.

[0047] Figure 1The base station (BS) in NG-RAN 135 shown may include ng-eNB 114, also known as Next Generation Evolved Node B. ng-eNB 114 may be connected to one or more of gNBs 110a and 110b in NG-RAN 135 via one or more other gNBs and / or one or more other ng-eNBs. ng-eNB 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to UE 105. One or more of gNBs 110a, 110b and / or ng-eNB 114 may be configured to act as a location-only beacon, which may transmit signals to assist in determining the location of UE 105, but may not receive signals from UE 105 or other UEs.

[0048] gNB 110a, 110b, and / or ng-eNB 114 may each include one or more TRPs. For example, each sector within a cell of the BS may include a TRP, but multiple TRPs may share one or more components (e.g., a shared processor but with separate antennas). System 100 may include only macro TRPs, or system 100 may have different types of TRPs, such as macro TRPs, pico TRPs, and / or femto TRPs. Macro TRPs may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by terminals with service subscriptions. Pico TRPs may cover a relatively small geographic area (e.g., a pico cell) and may allow unrestricted access by terminals with service subscriptions. Femto or home TRPs may cover a relatively small geographic area (e.g., a femto cell) and may allow restricted access by terminals associated with that femto cell (e.g., terminals of users in a home).

[0049] Each of the gNBs 110a, 110b, and / or ng-eNB 114 may include a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the gNB 110b includes RU 111, DU 112, and CU 113. RU 111, DU 112, and CU 113 define the functionality of the gNB 110b. Although the gNB 110b is shown as having a single RU, a single DU, and a single CU, a gNB may include one or more RUs, one or more DUs, and / or one or more CUs. The interface between CU 113 and DU 112 is referred to as the F1 interface. RU 111 is configured to perform digital front-end (DFE) functions (e.g., analog-to-digital conversion, filtering, power amplification, transmit / receive) and digital beamforming, and includes part of the physical (PHY) layer. RU 111 may perform DFE using massive MIMO and may be integrated with one or more antennas of the gNB 110b. DU 112 hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer of gNB 110b. A DU can support one or more cells, and each cell is supported by a single DU. The operation of DU 112 is controlled by CU 113. CU 113 is configured to perform functions for delivering user data, mobility control, radio access network sharing, location, session management, etc., although some functions are only assigned to DU 112. CU 113 hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) of gNB 110b. UE 105 can communicate with CU 113 via the RRC, SDAP, and PDCP layers, with DU 112 via the RLC, MAC, and PHY layers, and with RU 111 via the PHY layer.

[0050] As pointed out, although Figure 1 The diagram depicts nodes configured to communicate according to 5G communication protocols, but nodes configured to communicate according to other communication protocols (such as, for example, LTE or IEEE 802.11x) can also be used. For instance, in an evolved packet system (EPS) providing LTE radio access to UE 105, the RAN may include an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), which may include base stations containing evolved Node Bs (eNBs). The core network for the EPS may include an evolved packet core (EPC). The EPS may include the E-UTRAN plus the EPC, where the E-UTRAN corresponds to... Figure 1 NG-RAN 135 in the figure and EPC corresponds to 5GC 140 in the figure.

[0051] gNB 110a, 110b, and ng-eNB 114 can communicate with AMF 115; for positioning functionality, the AMF communicates with LMF 120. AMF 115 can support the mobility of UE 105 (including cell changes and handover) and can participate in supporting signaling connections with UE 105 and (possibly) data and voice bearers for UE 105. Sensing entity 118 and LMF 120 can communicate directly with UE 105, for example, wirelessly, or directly with gNB 110a, 110b, and / or ng-eNB 114. Sensing entity 118 can support RF sensing operations and process RF sensing requests, for example, by determining and providing sensing signal configurations. LMF 120 can support UE 105 positioning when UE 105 accesses NG-RAN 135, and can support various positioning procedures / methods, such as Auxiliary GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA) (e.g., Downlink (DL) OTDOA or Uplink (UL) OTDOA), Round Trip Time (RTT), Multi-Cell RTT, Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (E-CID), Angle of Arrival (AoA), Angle of Departure (AoD), and / or other positioning methods. LMF 120 can process, for example, location service requests for UE 105 received from AMF 115 or GMLC 125. LMF 120 can connect to AMF 115 and / or GMLC 125. LMF 120 can be referred to by other names, such as Location Manager (LM), Location Function (LF), Commercial LMF (CLMF), or Value-Added LMF (VLMF). The node / system implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobility Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Location Platform (SLP). At least a portion of the location functionality (including the derivation of the location of UE 105) can be performed at UE 105 (e.g., using signal measurements obtained by UE 105 against signals transmitted by radio nodes (such as gNB 110a, 110b and / or ng-eNB 114), and / or auxiliary data provided to UE 105, for example, by LMF 120). AMF 115 can be used as a control node to process signaling between UE 105 and 5GC 140 and can provide QoS (Quality of Service) streaming and session management. AMF 115 can support the mobility of UE 105 (including cell changes and handover) and can participate in supporting signaling connections with UE 105.

[0052] Server 150 (e.g., a cloud server) is configured to obtain location estimates, sensing information, and / or information provided by UE 105 and provide them to external client 130. Server 150 may be configured, for example, to run a microservice / service for obtaining the location estimate of UE 105. Server 150 may, for example (e.g., by sending a location request to it), pull the location estimate from one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113) and / or ng-eNB 114 and / or LMF 120. As another example, one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113) and / or LMF 120 may push the location estimate of UE 105 to server 150.

[0053] GMLC 125 can support location requests for UE 105 received from external client 130 via server 150, and can forward such location requests to AMF 115 for forwarding to LMF 120, or can forward the location request directly to LMF 120. A location response from LMF 120 (e.g., containing a location estimate for UE 105) can be returned to GMLC 125 directly or via AMF 115, and GMLC 125 can then return the location response (e.g., containing the location estimate) to external client 130 via server 150. GMLC 125 is shown connected to both AMF 115 and LMF 120, but in some specific implementations it may not be connected to either AMF 115 or LMF 120.

[0054] like Figure 1 As further illustrated, network entity 116 may use the New Radio Positioning Protocol A (which may be referred to as NPPa or NRPPa) to communicate with gNBs 110a, 110b, and / or ng-eNB 114, as defined in 3GPP Technical Specification (TS) 38.455. NRPPa may be the same as, similar to, or an extension of the LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, wherein NRPPa messages are transmitted via AMF 115 between gNB 110a (or gNB 110b) and network entity 116, and / or between ng-eNB 114 and network entity 116. Figure 1As further illustrated, network entity 116 and UE 105 may communicate using the LTE Location Protocol (LPP), which is defined in 3GPP TS 36.355. Network entity 116 and UE 105 may also communicate using a new radio location protocol (which may be referred to as NPP or NRPP), which may be the same as, similar to, or an extension of LPP. Here, LPP and / or NPP messages may be transmitted between UE 105 and network entity 116 via AMF 115 and UE 105's serving gNB 110a, 110b, or serving ng-eNB 114. For example, LPP and / or NPP messages may be transmitted between LMF 120 and AMF 115 using the 5G Location Services Application Protocol (LCS AP), and between AMF 115 and UE 105 using the 5G Non-Access Stratum (NAS) protocol. The LPP and / or NPP protocols can be used to support the location of UE 105 using UE-assisted and / or UE-based location methods (such as A-GNSS, RTK, OTDOA, and / or E-CID). The NRPPa protocol can be used to support the location of UE 105 using network-based location methods (such as E-CID) (e.g., when used in conjunction with measurements obtained by gNB 110a, 110b, or ng-eNB 114) and / or can be used by LMF 120 to obtain location-related information from gNB 110a, 110b, and / or ng-eNB 114, such as defining parameters sent by directional SS or PRS from gNB 110a, 110b, and / or ng-eNB 114. One or more of the network entities 116 can be co-located or integrated with the gNB or TRP, or can be configured to be located away from the gNB and / or TRP and communicate directly or indirectly with the gNB and / or TRP.

[0055] Using a UE-assisted positioning method, UE 105 can obtain location measurements and transmit these measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105. For example, location measurements may include one or more of the following: Received Signal Strength Indication (RSSI), Round-Trip Time (RTT), Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), and / or Reference Signal Received Quality (RSRQ) for gNB 110a, 110b, ng-eNB 114, and / or WLAN AP. Location measurements may additionally or alternatively include measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190-193.

[0056] Using a UE-based positioning method, UE 105 can obtain a location measurement (e.g., which may be the same as or similar to the location measurement of a UE-assisted positioning method) and can calculate the location of UE 105 (e.g., by means of auxiliary data received from a location server (such as LMF 120) or broadcast by gNB 110a, 110b, ng-eNB 114 or other base stations or APs).

[0057] Using a network-based positioning method, one or more base stations (e.g., gNB 110a, 110b and / or ng-eNB 114) or APs can obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, or Time of Arrival (ToA) of signals transmitted by UE 105) and / or can receive measurements obtained by UE 105. One or more base stations or APs can transmit the measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105.

[0058] The information provided to the LMF 120 by the gNB 110a, 110b and / or ng-eNB 114 using NRPPa may include timing and configuration information for directing SS or PRS transmissions, as well as location coordinates. The LMF 120 may provide some or all of this information as supplementary data to the UE 105 in LPP and / or NPP messages via NG-RAN 135 and 5GC140.

[0059] The LPP or NPP message transmitted from network entity 116 to UE 105 can command UE 105 to perform any of a variety of tasks depending on the desired functionality. For example, the LPP or NPP message may contain instructions for UE 105 to obtain measurements of GNSS (or A-GNSS), WLAN, E-CID, and / or OTDOA (or some other positioning method). In the case of E-CID, the LPP or NPP message may command UE 105 to obtain measurements supported by one or more of gNB 110a, 110b, and / or ng-eNB 114 (or by some other type of base station such as eNB or WiFi). ® One or more measurement parameters (e.g., beam ID, beamwidth, average angle, RSRP, RSRQ measurements) of directional signals transmitted within a specific cell supported by the AP. UE 105 can transmit these measurement parameters back to LMF 120 via serving gNB110a (or serving ng-eNB 114) and AMF 115 in an LPP or NPP message (e.g., within a 5G NAS message).

[0060] As noted, while a communication system 100 is described in relation to 5G technology, the communication system 100 can be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) for supporting and interacting with mobile devices (such as UE 105) (e.g., to provide voice, data, location, and other functionalities). In some such implementations, the 5GC 140 can be configured to control different air interfaces. For example, the 5GC 140 can use non-3GPP interoperability functions (N3IWF) within the 5GC 140. Figure 1 (Not shown) Connected to a WLAN. For example, the WLAN may support IEEE 802.11 WiFi for UE 105. ® Access, and may include one or more WiFi networks. ® AP. Here, the N3IWF can connect to the WLAN and other components in the 5GC 140, such as the AMF 115. In some implementations, both the NG-RAN 135 and the 5GC 140 can be replaced by one or more other RANs and one or more other core networks. For example, in EPS, the NG-RAN 135 can be replaced by an E-UTRAN containing eNBs, and the 5GC 140 can be replaced by an EPC containing a Mobility Management Entity (MME) instead of the AMF 115, an E-SMLC instead of the LMF 120, and a GMLC that can be similar to the GMLC 125. In such EPS, the E-SMLC can use LPPa instead of NRPPa to transmit location information to and receive location information from the eNBs in the E-UTRAN, and can use LPP to support the positioning of the UE 105. In these other implementations, the location of UE 105 using directional PRS can be supported in a manner similar to that described herein for 5G networks. The difference lies in the fact that the functions and procedures described herein for gNB 110a, 110b, ng-eNB 114, AMF 115, and LMF 120 can, in some cases, be alternatively applied to other network elements, such as eNBs and WiFi. ® AP, MME, and E-SMLC.

[0061] As noted, in some implementations, positioning functionality can be achieved at least in part using directional SS or PRS beams transmitted by base stations (such as gNB 110a, 110b and / or ng-eNB 114) that are used to determine the location of the UE (e.g., Figure 1 Within the range of UE 105. In some instances, the UE can use directional SS or PRS beams from multiple base stations (such as gNB110a, 110b, ng-eNB 114, etc.) to calculate the UE's location.

[0062] Also refer to Figure 2UE 200 may be an example of one of UEs 105 and 106, and may include a computing platform containing processor 210, a memory 211 containing software (SW) 212, and a transceiver interface 214 for transceivers 215 (which includes wireless transceivers 240 and wired transceivers 250). Processor 210, memory 211, and transceiver interface 214 may be communicatively coupled to each other via bus 220 (which may be configured for, for example, optical communication and / or electrical communication). UE 200 may include one or more devices not shown (e.g., a camera, positioning device, and / or one or more sensors, etc.). Processor 210 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 210 may include multiple processors, including a general-purpose / application processor 230, a digital signal processor (DSP) 231, a modem processor 232, a video processor 233, and / or a sensor processor 234. One or more of processors 230 to 234 may include multiple devices (e.g., multiple processors). For example, sensor processor 234 may include processors for RF (radio frequency) sensing (where one or more transmitted (cellular) wireless signals and reflections are used to identify, map, and / or track objects) and / or ultrasound, etc. Modem processor 232 may support dual SIM / dual connectivity (or even more SIMs). For example, a SIM (Subscriber Identity Module or Subscriber Identification Module) may be used by an Original Equipment Manufacturer (OEM), and another SIM may be used by an end user of UE 200 to obtain connectivity. Memory 211 may be a non-transitory storage medium that may include random access memory (RAM), flash memory, disk memory, and / or read-only memory (ROM), etc. Memory 211 may store software 212, which may be processor-readable, processor-executable software code containing instructions that can be configured to cause processor 210 to perform the various functions described herein when executed. Alternatively, software 212 may not be directly executable by processor 210, but may be configured to cause processor 210 to perform these functions, for example, when compiled and executed. The description herein may refer to processor 210 performing functions, but this includes other specific implementations, such as specific implementations of processor 210 performing software and / or firmware. The description herein may refer to the functions performed by processor 210 as a shorthand for one or more processors 230 to 234 performing functions. The description herein may refer to the functions performed by UE 200 as a shorthand for one or more appropriate components of UE 200 performing functions. Processor 210 may include memory with stored instructions as a supplement to and / or replacement of memory 211. The functionality of processor 210 is discussed more fully below.

[0063] Figure 2 The configuration of UE 200 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, an exemplary configuration of the UE may include one or more of processors 230 to 234 in processor 210, memory 211, and wireless transceiver 240. Other exemplary configurations may include one or more of processors 230 to 234 in processor 210, memory 211, wireless transceiver, and one or more of sensors, user interface, SPS receiver, camera, and / or positioning devices (e.g., for determining the location of UE 200 by means other than satellite signals).

[0064] UE 200 may include a modem processor 232, which may be capable of performing baseband processing on signals received and down-converted by transceiver 215. Modem processor 232 may also perform baseband processing on signals to be up-converted for transmission by transceiver 215. Alternatively or additionally, baseband processing may be performed by general-purpose / application processor 230 and / or DSP 231. However, other configurations may be used to perform baseband processing.

[0065] Transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 240 may include a wireless transmitter 242 and a wireless receiver 244 coupled to antenna 246 for transmitting (e.g., on one or more uplink channels and / or one or more sidelink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more sidelink channels) wireless signals 248 and converting signals from wireless signals 248 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 248. Wireless transmitter 242 includes suitable components (e.g., power amplifiers and digital-to-analog converters). Wireless receiver 244 includes suitable components (e.g., one or more amplifiers, one or more frequency filters, and analog-to-digital converters). Wireless transmitter 242 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 244 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 240 can be configured to transmit signals according to various radio access technologies (RATs) (e.g., with TRP and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ®The new radio can use millimeter wave frequencies and / or frequencies below 6 GHz. Wired transceiver 250 may include a wired transmitter 252 and a wired receiver 254 configured for wired communication, for example, a network interface used to communicate with and receive communications from NG-RAN 135. Wired transmitter 252 may include multiple transmitters, which may be discrete components or combined / integrated components, and / or wired receiver 254 may include multiple receivers, which may be discrete components or combined / integrated components. Wired transceiver 250 may be configured, for example, for optical and / or electrical communication. Transceiver 215 may be communicatively coupled to transceiver interface 214, for example, via optical and / or electrical connections. Transceiver interface 214 may be at least partially integrated with transceiver 215. The wireless transmitter 242, the wireless receiver 244, and / or the antenna 246 may each include multiple transmitters, multiple receivers, and / or multiple antennas for transmitting and / or receiving appropriate signals, respectively.

[0066] Also refer to Figure 3 Examples of TRP 300 for gNB 110a, 110b and / or ng-eNB 114 include a computing platform containing processor 310, a memory 311 containing software (SW) 312, and a transceiver 315. Processor 310, memory 311 and transceiver 315 are communicatively coupled to each other via bus 320 (which may be configured for, for example, optical communication and / or electrical communication). One or more devices in the illustrated apparatus (e.g., wireless transceivers) may be omitted from TRP 300. Processor 310 may include one or more intelligent hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 310 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors and / or sensor processors, such as... Figure 2 (As shown). Memory 311 may be a non-transitory storage medium including random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM). Memory 311 may store software 312, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 310 to perform the various functions described herein when executed. Alternatively, software 312 may not be directly executable by processor 310, but may be configured to cause processor 310 to perform these functions, for example, when compiled and executed.

[0067] The description herein refers to the functionality performed by processor 310, but this includes other specific implementations, such as specific implementations of software and / or firmware performed by processor 310. The description herein may refer to the functionality performed by processor 310 as an abbreviation for the functionality performed by one or more processors contained within processor 310. The description herein may refer to the functionality performed by TRP 300 as an abbreviation for the functionality performed by one or more appropriate components of TRP 300 (and therefore one of gNB 110a, 110b and / or ng-eNB 114), such as processor 310 and memory 311. Processor 310 may include memory with stored instructions as a complement and / or replacement for memory 311. The functionality of processor 310 is discussed more fully below.

[0068] Transceiver 315 may include a wireless transceiver 340 and / or a wired transceiver 350 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 340 may include a wireless transmitter 342 and a wireless receiver 344 coupled to one or more antennas 346 for transmitting (e.g., on one or more uplink channels and / or one or more downlink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more uplink channels) wireless signals 348 and converting signals from wireless signals 348 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 348. Therefore, wireless transmitter 342 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 344 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 340 can be configured to support various radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ®The wired transceiver 350 may include a wired transmitter 352 and a wired receiver 354 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communications to, for example, LMF 120 and / or one or more other network entities. The wired transmitter 352 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 354 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 350 may be configured, for example, for optical communication and / or electrical communication.

[0069] Figure 3 The configuration of TRP 300 shown is illustrative and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, the description herein discusses that TRP 300 may be configured to perform several functions or that the TRP performs several functions, but one or more of these functions may be performed by LMF 120 and / or UE 200 (i.e., LMF 120 and / or UE 200 may be configured to perform one or more of these functions).

[0070] Also refer to Figure 4 Server 400 (LMF 120 may be an example thereof) may include: a computing platform including processor 410, a memory 411 including software (SW) 412, and a transceiver 415. Processor 410, memory 411, and transceiver 415 may be communicatively coupled to each other via bus 420 (which may be configured for, for example, optical communication and / or electrical communication). One or more devices in the illustrated apparatus (e.g., a wireless transceiver) may be omitted from server 400. Processor 410 may include one or more intelligent hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 410 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors, and / or sensor processors, such as… Figure 2(As shown). Memory 411 may be a non-transitory storage medium including random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM). Memory 411 may store software 412, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 410 to perform the various functions described herein when executed. Alternatively, software 412 may not be directly executable by processor 410, but may be configured to cause processor 410 to perform these functions, for example, when compiled and executed. The description herein may refer to processor 410 performing functions, but this includes other specific implementations, such as specific implementations of processor 410 performing software and / or firmware. The description herein may refer to the function performed by processor 410 as an abbreviation for one or more processors included in processor 410 performing functions. The description herein may refer to the function performed by server 400 as an abbreviation for one or more suitable components of server 400 performing functions. Processor 410 may include memory with stored instructions as a supplement to and / or alternative to memory 411. The functionality of processor 410 is discussed more fully below.

[0071] Transceiver 415 may include a wireless transceiver 440 and / or a wired transceiver 450 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 440 may include a wireless transmitter 442 and a wireless receiver 444 coupled to one or more antennas 446 for transmitting (e.g., on one or more downlink channels) and / or receiving (e.g., on one or more uplink channels) wireless signals 448 and converting signals from wireless signals 448 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 448. Therefore, wireless transmitter 442 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 444 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 440 can be configured to support various radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ®The wired transceiver 450 may include a wired transmitter 452 and a wired receiver 454 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communications to, for example, TRP 300 and / or one or more other network entities. The wired transmitter 452 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 454 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 450 may be configured, for example, for optical communication and / or electrical communication.

[0072] The description herein may refer to the functionality performed by processor 410, but this includes other specific implementations, such as specific implementations of software (stored in memory 411) and / or firmware performed by processor 410. The description herein may refer to the functionality performed by server 400 as an abbreviation for the functionality performed by one or more appropriate components of server 400 (e.g., processor 410 and memory 411).

[0073] Figure 4 The configuration of server 400 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, wireless transceiver 440 may be omitted. Furthermore or alternatively, the description herein discusses server 400 being configured to perform certain functions or the server performing certain functions, but one or more of these functions may be performed by TRP 300 and / or UE 200 (i.e., TRP 300 and / or UE 200 may be configured to perform one or more of these functions).

[0074] RF sensing with sensitivity time control

[0075] Also refer to Figure 5 UE 500 includes a processor 510, a transceiver 520, and a memory 530, which are communicatively coupled to each other via a bus 540. Even when referred to in the singular, processor 510 may include one or more processors, transceiver 520 may include one or more transceivers (e.g., one or more transmitters and / or one or more receivers), and memory 530 may include one or more memories. UE 500 may include Figure 5 The components shown. UE 500 may include one or more other components (such as...) Figure 2Any of the components shown) makes UE 200 an example of UE 500. For example, processor 510 may include one or more components of processor 210. Transceiver 520 may include one or more components of transceiver 215, such as wireless transmitter 242 and antenna 246, or wireless receiver 244 and antenna 246, or wireless transmitter 242, wireless receiver 244 and antenna 246. Additionally or alternatively, transceiver 520 may include wired transmitter 252 and / or wired receiver 254. Memory 530 may be configured similarly to memory 211, for example including software having processor-readable instructions configured to cause processor 510 to perform functions.

[0076] The description herein may refer to the processor 510 performing functions, but this includes other specific implementations, such as specific implementations of the processor 510 performing software (stored in memory 530) and / or firmware. The description herein may refer to the UE 500 performing functions as a shorthand for one or more appropriate components of the UE 500 (e.g., processor 510 and memory 530) performing functions. The processor 510 (possibly in conjunction with memory 530 and, where appropriate, transceiver 520) may include a capability unit 550 and / or an RF sensing unit 560. The capability unit 550 may be configured to transmit capability messages instructing the UE 500 to implement one or more capabilities for measuring sensed signals using STC. The RF sensing unit 560 may be configured to request STC configuration information (e.g., one or more STC profiles and / or information that the UE 500 can use to determine (e.g., export or select) the STC profile to be implemented for RF sensing). The capability unit 550 and the RF sensing unit 560 are discussed further below, and any of the functions that may be generally referred to as the processor 510 or the UE 500 as performing the functions of the capability unit 550 and / or the RF sensing unit 560 are described, wherein the UE 500 is configured to perform these functions.

[0077] Also refer to Figure 6 Network entity 600 includes a processor 610, a transceiver 620, and a memory 630, which are communicatively coupled to each other via a bus 640. Network entity 600 may be, for example, a base station, a TRP, a server, etc. Even when mentioned in the singular, network entity 600 may include one or more network entities; processor 610 may include one or more processors; transceiver 620 may include one or more transceivers (e.g., one or more transmitters and / or one or more receivers); and memory 630 may include one or more memories. Network entity 600 may include... Figure 6 The components shown. Network entity 600 may include one or more other components, such as Figure 4Any of the components shown makes server 400 an example of network entity 600. For example, processor 610 may include one or more components of processor 410. Transceiver 620 may include one or more components of transceiver 415. Memory 630 may be configured similarly to memory 411, for example including software having processor-readable instructions configured to cause processor 610 to perform functions. Additionally or alternatively, network entity 600 may include one or more other components, such as Figure 3 Any of the components shown makes TRP 300 an example of network entity 600. For example, processor 610 may include one or more components of processor 310. Transceiver 620 may include one or more components of transceiver 315. Memory 630 may be configured similarly to memory 311, for example including software having processor-readable instructions configured to cause processor 610 to perform functions.

[0078] The description herein may refer to the functionality performed by processor 610, but this includes other specific implementations, such as specific implementations of software (stored in memory 630) and / or firmware performed by processor 610. The description herein may refer to the functionality performed by network entity 600 as an abbreviation for the functionality performed by one or more suitable components of network entity 600 (e.g., processor 610 and memory 630). Processor 610 (possibly in conjunction with memory 630 and, where appropriate, transceiver 620) may include STC unit 650 and / or RF sensing unit 660. STC unit 650 may be configured to determine STC configuration information (e.g., one or more STC profiles and / or information that UE 500 can use to determine (e.g., export or select) the STC profile to be implemented for RF sensing). RF sensing unit 660 (e.g., where network entity 600 is a TRP) may be configured to transmit sensing signals and / or receive and measure sensing signals. STC unit 650 and RF sensing unit 660 are further discussed below, and any functions that may generally be referred to as processor 610 or network entity 600, performing the functions of STC unit 650 and / or RF sensing unit 660, are described, wherein network entity 600 is configured to perform these functions.

[0079] Also refer to Figure 7 and Figure 8 This allows for various configurations of the sensing system, such as single-station or dual-station sensing systems. For example, such as Figure 7As shown, a single-site sensing system 700 includes a transmitting node 710, a target object 720, and a receiving node 730. In this case, the transmitting node 710 and the receiving node 730 are co-located and can be part of a single physical device. The transmitting node 710 can transmit an FL signal 712 (forward link signal), and the target object 720 can backscatter (e.g., reflect) a BL signal 722 (backscattered link signal) based on the incoming signal (i.e., the FL signal 712). The receiving node 730 can receive and measure the BL signal 722. The transmitting (Tx) node or the receiving (Rx) node can be, for example, a UE, TRP, or RAN node. Figure 8 As shown, the bi-station sensing system 800 includes a transmitting node 810, a target object 820, and a receiving node 830. In this case, the transmitting node 810 and the receiving node 830 are non-co-located. The transmitting node 810 can transmit an FL signal 812, the target object 820 can backscatter a BL signal 822 based on the FL signal 812, and the receiving node 830 can receive, measure, and / or decode the BL signal 822.

[0080] The sensing system can be configured as a multi-station sensing system, in which multiple transmitting nodes and / or multiple receiving nodes exist. Within a multi-station sensing system, one or more single-station systems and / or one or more dual-station systems may exist.

[0081] Also refer to Figure 9 The receiving circuit 900 can be used by a receiver in any type of sensing system to receive and process sensing signals for measurement, for example, by one or more processors. The receiving circuit 900 is an example of a receiving circuit and may include, for example, part of a transceiver 520. The receiving circuit 900 includes an RF amplifier 920, an LO 930 (local oscillator), a mixer 940, and an LNA 950 (low-noise amplifier). An incoming sensing signal 910 (e.g., reflected by a target object) may be amplified by the RF amplifier 920. The incoming sensing signal 910 output from the RF amplifier 920 may be mixed with an LO signal from the LO 930 to convert the RF frequency of the sensing signal 910 to an intermediate frequency (IF) signal 942. The IF signal 942 may be amplified by the LNA 950 to generate an IF sensing signal 960, which may be provided to additional circuitry (not shown) for conversion to baseband and further processing (e.g., measurement).

[0082] In RF sensing (e.g., as about Figure 7 and 8(As discussed), wireless signals can be transmitted from one or more transmitting points and received at one or more receiving points after being reflected by a target. RF sensing enables many candidate applications, such as intruder detection, animal / pedestrian / UAV (unmanned aerial vehicle) intrusion detection on highways and railways, rainfall monitoring, flood warning, autonomous driving, AGV (Automated Guided Vehicle) detection / tracking / collision avoidance, smart parking and assistance, UAV trajectory and tracking, crowd management, sleep / health monitoring, gesture recognition, XR streaming, public safety search and rescue, etc. The farther away the target object (the target whose position and / or speed are expected to be known), the weaker the echo at the receiver (because signal power is related to R...). 2 Inversely proportional to R, where R is the distance from the transmitter. If the transmitter and receiver are co-located, the received power is proportional to R. (Inversely proportional). Objects other than the target object can be called clutter. Clutter sources at close range / short distance can cause relatively high-power reflections and exceed the receiver's dynamic range, making it impossible for the receiver to detect weaker target echoes at greater distances.

[0083] Also refer to Figure 10The gain of a receiver (such as receiver 900) can be adjusted according to an STC (Sensitivity Time Control) profile (gain varies over time). For example, as shown in graph 1000, RF sensing signal pulse 1010 (which may be part of a pulse train and may be referred to as a chirp) and RF sensing signal pulse 1020 are transmitted at different times separated by pulse / chirp repetition interval 1030. STC gain curve 1040 shows that from time t0 to time t1, the receiver gain (e.g., the combined gain of RF amplifier 920 and LNA 950) is a first gain 1041; from time t1 to time t2, the receiver gain is increasing (here, a linearly increasing gain 1050) to a second gain 1042, and after time t2, it remains at the second gain 1042. The STC profile can be specified according to the start time, stop time, and corresponding gain. For example, the STC gain curve 1040 can be specified by a start time (e.g., time t1), a stop time (e.g., time t2), and one or more indications of the time-varying gain. The time-varying gain can be indicated, for example, by a gain formula, or by formulas for the gain at the start time, the gain at the stop time, and the gain between the start and stop times. The gain formula can be, for example, the gain slope of a linearly varying gain or a logarithmic formula with an indicated scaling parameter, or another formula (e.g., a piecewise indication of discrete gain levels and corresponding time intervals, or a combination of varying gains (e.g., linearly varying gain and logarithmically varying gain, e.g., linearly varying gain in one or more time intervals and logarithmically varying gain in one or more other time intervals)). Other STC profiles can be used. For example, other variations of increasing gain can be used, such as nonlinear gain (e.g., logarithmically increasing gain), such as nonlinearly increasing gain 1060.

[0084] STC can be used to detect targets at relatively long distances, where the gain applied by the receiver to the received signal is adapted in the time domain to avoid exceeding the receiver's dynamic range. STC (also known as scan gain control, amplifier gain time control, and decay time control) can be used to control the receiver gain so that the receiver's dynamic range is appropriately set to detect both short-range and long-range targets. For example, controlling the amplifier gain (before or after the IF stage) can be set low immediately after the sensing signal pulse is sent and then gradually increased over time (e.g., linearly, logarithmically, etc.).

[0085] While STC can help enhance the detection of distant targets, it also presents several challenges and drawbacks. For example, the effectiveness of an STC profile (i.e., the gain that varies over time) can depend on the deployment environment, the application using STC for sensing, and the expected range of the target. Even for the same application, different clutter distributions can exist, leading to different desired STC profiles. Gain that varies linearly over time and gain that varies logarithmically over time are examples of STC profile gain variations, but other gain variations are possible. The desired gain variation can depend on, for example, knowledge of the target distance and clutter distribution. A well-performing STC profile can depend on the clutter distribution and nature and can differ for different applications. A well-performing STC profile (e.g., determining, selecting) one that will provide accurate results may require knowledge of nearby clutter sources and their modeling. Therefore, STC is a good candidate for air traffic control (ATC), where most targets are relatively far / long-range, and short-range objects are not of concern. As another example, STC may lead to the false detection / false identification of nearby targets. As yet another example, using STC for NR RF sensing is challenging. For example, a UE (as a sensing receiver node / entity) can operate in a wide range of environments and with a wide range of clutter settings / options, and depending on the expected target range and the expected clutter type at short range, STC may or may not be recommended. If STC is used, the UE may not know the appropriate STC profile to apply when performing sensing, for example, because clutter information may be extensive and different for different sites.

[0086] As discussed herein, network entities (e.g., LMF or SMF (Sensing Management Function)) can be configured to transmit STC configuration information (e.g., STC-related configuration) to the UE. STC configuration information may include one or more STC profile configurations, such as recommended STC settings for one or more STC profiles for the UE to use in detecting targets. The UE can use one or more recommended STC settings (e.g., of a commanded STC profile or of an STC profile selected by the UE from multiple recommended STC profiles) to perform sensing. The UE can report sensing measurements and sensing results. STC configuration information may include: indications of when the UE should use STC and / or when the UE should not use STC, one or more recommended STC profiles (e.g., gain settings changing over time), and / or information that can be used (e.g., by the UE) to determine STC profile settings (e.g., by selecting from available STC profiles) (e.g., clutter information).

[0087] As discussed herein, the UE may share STC configuration information, such as one or more recommended STC settings, with network entities (e.g., SMF). For example, if the UE determines that one or more STC settings produce accurate sensing results (e.g., sensing results that meet one or more accuracy criteria (e.g., exceeding one or more corresponding accuracy thresholds)), the UE may share the STC settings and one or more corresponding conditions (e.g., the UE's location, clutter distribution corresponding to the UE's location, and / or target type, etc.). The network entity may use the shared STC configuration information to configure the reporting UE to implement STC for RF sensing, for example, by commanding the UE to use one or more of the reported STC settings. Alternatively or concurrently, the network entity may share the shared STC configuration information with one or more UEs other than the reporting UE, and / or may configure one or more UEs other than the reporting UE to use one or more shared STC settings (e.g., corresponding to one or more shared conditions (if any)) to implement STC for RF sensing.

[0088] refer to Figure 11 For further reference Figures 1 to 10 The processing and signaling flow 1100, which uses RF scheduling with STC to determine the range and / or velocity of a target object, includes the stages shown. Flow 1100 is an example of an interaction between UE 1101, target object 1103, and network entity 1105. UE 1101 may be an example of UE 500. Network entity 1105 may be an example of network entity 600. Other flows may be used. For example, one or more stages may be added to flow 1100, one or more stages may be rearranged, and / or one or more stages may be removed from flow 1100. For example, stage 1110 may be omitted. As another example, one or more of messages 1111, 1112, and 1113 may be omitted (e.g., not generated and / or not sent). As another example, sub-stage 1115 may be omitted, for example, based on the fact that message 1113 was not sent. As another example, sensing signals may be sent by a signal source other than UE 1101, in addition to or instead of being sent by UE 1101.

[0089] At stage 1110, the STC capability of UE 1101 may be requested and / or provided to network entity 1105. Network entity 1105 (e.g., STC unit 650) may (e.g., via transceiver 620) send an STC capability request message 1111 to UE 1101. Message 1111 may request UE 1101's capabilities regarding implementing STC, such as whether UE 1101 is configured to implement STC, what STC profile UE 1101 is configured to implement, settings of any STC profile UE 1101 is configured to implement, and one or more conditions corresponding to any STC profile UE 1101 is configured to implement (e.g., frequency, clutter distribution, target distance, etc.). UE 1101 (e.g., capability unit 550) may send an STC capability message 1112 including one or more of the requested STC capabilities and / or one or more other STC capabilities of UE 1101. UE 1101 may send STC Capability Message 1112 in response to STC Capability Request Message 1111 or independently of any request for STC capability of UE 1101 (e.g., in the absence of a request for STC capability or without regard to any received request for STC capability). UE 1101 may send STC Capability Message 1112 as part of an LPP capability exchange procedure or as part of a sensing capability transfer procedure developed for STC capability transfer.

[0090] Also refer to Figure 12STC Capability Table 1200 is an example of the content of STC Capability Message 1112. Table 1200 includes STC Capability Field 1210, STC Profile Available Field 1220, Available STC Profile Field 1230, and Conditional STC Applicability Field 1240. Table 1200 is an example, and other message content may be used (e.g., one or more of fields 1210, 1220, 1230, and 1240 may be omitted, and / or content may have a different format). STC Capability Field 1210 indicates whether UE 1101 is configured to implement STC for RF sensing. STC Profile Available Field 1220 indicates whether UE 1101 has any stored STC profile that UE 1101 can implement for RF sensing. Available STC Profile Field 1230 indicates the STC profile (if any) stored by UE 1101 (e.g., in memory 530). For each STC profile, the indication of the stored profile can be in the form of one or more STC profile settings (e.g., ParamSet1, Paramset2 as shown) and / or in the form of a code corresponding to the STC profile (e.g., STCcode1 as shown), which corresponds to a set of STC settings known to both network entity 1105 and UE 1101. The conditional STC applicability field 1240 indicates whether UE 1101 is configured to selectively apply STC profiles based on one or more conditions (e.g., the frequency, direction (e.g., corresponding to antenna beam and / or antenna beamwidth), received signal polarization, and / or received signal pulse). For example, UE 1101 may have multiple received RF chains and may utilize different STC profiles applied by different chains to process the received signals. As another example, UE 1101 may apply different STC profiles to different pulses of the signal. Any of these examples can be implemented to provide diversity of targets and / or allow the detection of multiple targets, where a single STC profile may be insufficient to detect all targets. One or more conditions indicated by field 1240 may be provided for each available STC profile indicated in field 1230, and / or one or more conditions of the same set indicated in field 1240 (where "set" as used herein includes at least one member) may be provided for multiple STC profiles indicated in field 1230, or the same set of conditions indicated in field 1240 may be provided for all STC profiles indicated in field 1230. Alternatively, field 1240 may generally indicate that UE 1101 can selectively apply an STC profile based on one or more conditions, without specifically indicating each set of conditions corresponding to a particular STC profile.

[0091] Alternatively or concurrently, at stage 1110, STC configuration information may be requested and / or provided to the UE 1101. The UE 1101 (e.g., RF sensing unit 560) may send an STC configuration information request message 1113 to network entity 1105. Message 1113 may request one or more STC profiles and / or STC configuration information, which the UE 1101 may use to determine one or more STC profiles to apply when receiving RF sensing and performing sensing measurements on one or more target objects (e.g., target object 1103). Message 1113 may request information on one or more STC profiles corresponding to one or more criteria (e.g., RF sensing signal band, RF sensing signal polarization, etc.). At sub-stage 1115, network entity 1105 (e.g., STC unit 650 of the SMF) may determine one or more STC profiles to be sent to the UE 1101. Network entity 1104 (e.g., STC unit 650) may generate one or more STC profiles, for example, based on STC profile information reported to network entity 1105 by UE 1101 and / or one or more other UEs, based on one or more clutter distributions near UE 1101 (or between UE and one or more target objects), one or more distances to one or more target objects, and / or one or more STC capabilities indicated by UE 1101 in STC capability message 1112. Network entity 1105 may transmit an STC configuration information message 1116 to UE 1101, which indicates STC configuration information for UE 1101 to use to determine (e.g., derive or select) an STC profile to be implemented for RF sensing of target object 1103. Message 1116 may be transmitted in any of a variety of ways. Network entity 1105 may transmit message 1116, for example, as part of an LPP-assisted data exchange procedure, a location broadcast procedure, and / or a location request procedure. Alternatively or concurrently, network entity 1105 may send message 1116, for example, as part of an auxiliary data provision process developed for RF sensing, an RF sensing broadcast process, and / or an RF sensing request process.

[0092] Also refer to Figure 13 STC configuration information table 1300 is an example of the content of STC configuration information message 1116. Table 1300 includes STC profile indication field 1310, STC consideration field 1320, STC profile consideration field 1330, and STC profile priority rule field 1340. Table 1300 is an example, and other message content may be used (e.g., one or more of fields 1310, 1320, 1330, and 1340 may be omitted, and / or content with different formats may be used).

[0093] STC Profile Indication Field 1310 may indicate one or more recommended STC profiles for UE 1101 to implement STC RF sensing. STC Profile Indication Field 1310 may indicate one or more STC profiles, such as parameter sets and / or decoded profile indications. Decoded profile indications may be well-known (e.g., globally known or network-wide known) codes for STC profiles, or they may be codes specific to a particular UE, such as indicating an STC profile (e.g., STC Profile 1 or STC Profile 2) among a set of STC profiles supported by UE 1101 as indicated by UE 1101. Each STC profile indication may include a corresponding granularity, such as frequency range, direction of received sensed signal (e.g., relative to a global coordinate system), sensed signal pulse / processing repetition interval, sensed signal polarization, etc. The granularity indicates one or more parameters used to implement the STC profile. STC profile indications may also include profile descriptions (e.g., explicitly using one or more sets of parameters, or implicitly using decoded indications, such as profile code numbers corresponding to known parameter sets (including parameter values)). For example, the profile description parameters may include the start time, stop (end) time, and gain change slope of the linear gain STC profile. As another example, the profile description parameters may include the start and end times, as well as scaling, of the logarithmic gain STC profile. As yet another example, the profile description may include a piecewise gain function with different discrete gain values ​​and corresponding time intervals. The STC profile indication field 1310 may indicate that if UE 1101 is capable of applying STC, the recommended STC profile indicated by the STC profile indication field 1310 will be applied according to the command of network entity 1105 or the selection of UE 1101.

[0094] STC Consideration field 1320 may indicate the STC profile that UE 1101 may determine (e.g., derive or select) to implement and / or the information that UE 1101 may determine when to report RF sensing measurements. For example, STC Consideration field 1320 may indicate one or more clutter distributions and / or other information for UE 1101 to use in determining the STC profile to be implemented to sense target object 1103. For example, STC Consideration may indicate one or more characteristics of clutter between UE 1101 and target object 1103, for example, based on the approximate location of UE 1101. STC Consideration may include different ranges (distances) from UE 1101, with a corresponding clutter indication (e.g., clutter reflectivity) for each of the different ranges. STC Consideration may include a probability distribution indicating the short-range clutter radar cross section (RCS). As another example, STC Consideration field 1320 may indicate one or more aspects of measurements that enable STC. For example, the STC consideration field 1320 may indicate periodic reporting (and, if so, the period for reporting), non-periodic reporting (triggered by a reporting request transmitted by network entity 1105 to UE 1101), or event-triggered reporting (and, if so, one or more events for triggering the reporting). If UE 1101 is configured to determine (e.g., export) an STC profile, the STC consideration field 1320 may instruct UE 1101 to use the indicated STC consideration to determine the STC profile to be applied.

[0095] STC profile condition field 1330 may instruct UE 1101 to meet one or more conditions for applying the STC profile to RF sensing. For example, STC profile condition field 1330 may instruct UE 1101 to be located in the geographic area corresponding to the STC profile. Alternatively, STC profile condition field 1330 may instruct the received sensing signal to meet one or more received signal KPI (Key Performance Indicator) thresholds for applying the corresponding STC profile. Example KPI thresholds may include, for example, RSSI threshold, RSRP threshold, SINR (Signal-to-Interference-plus-Noise Ratio) threshold, dynamic range threshold, etc.

[0096] STC profile prioritization rule field 1340 may indicate one or more rules for UE 1101 to prioritize which STC profile among multiple STC profiles is applied to RF sensing. For example, STC prioritization rule field 1340 may indicate which STC profile is used for a specific geographic area (e.g., such as...). Figure 13The ParamSet1 shown is used for Area2). Alternatively, the STC profile condition field 1330 can indicate one or more received signal KPI (Key Performance Indicator) thresholds that the applied STC profile must meet for the received sensed signal. For example, it can indicate the priority of STC profiles corresponding to different KPIs for the same geographic area (e.g., for Area1 where RSSI is higher than RSSI threshold RSSI1, STCcode1 is used, while for Area1 where RSSI is higher than RSSI threshold RSSI2, ParamSet2 is used, as shown). Figure 13 (As shown).

[0097] For further details, please refer to the following: Figure 11 At stage 1120, UE 1101 (e.g., RF sensing unit 560) can determine the STC profile to be implemented for RF sensing. For example, UE 1101 can determine the STC profile to be implemented by reading the commanded STC profile from message 1116. As another example, UE 1101 can determine the STC profile to be implemented by selecting one of a plurality of recommended STC profiles in message 1116, for example, by evaluating clutter information and / or by evaluating prioritization rules and corresponding parameter / condition values ​​(e.g., the area where UE 1101 is located, the KPI of the received signal, etc.). As another example, UE 1101 can determine the STC profile to be implemented by, for example, selecting from a plurality of STC profiles stored in memory 530 based on clutter information and / or based on prioritization rules provided by network entity 1105 or stored in memory 530 and corresponding parameter / condition values. As another example, UE1101 can determine the STC profile to be implemented by deriving the STC profile based on information in message 1116 and / or measured by UE1101 (e.g., clutter distribution information). For example, the gain of the STC profile may be inversely proportional to the expected clutter power reflection, clutter reflectivity, or clutter radar cross-section. The STC profile information stored in memory 530 can be established by any of a variety of entities (e.g., the manufacturer of UE1101 and / or the manufacturer of the RF sensing chip or processor chip). The STC profile information can be established for various conditions (e.g., specific location).

[0098] At stage 1130, UE 1101 may perform sensing signal transmission (e.g., one or more sensing signal transmissions), and UE 1101 and network entity 1105 may perform non-sensing signal transmission (e.g., one or more transmissions and / or one or more receptions). UE 1101 may transmit sensing signal 1134 (and / or another sensing signal source (e.g., another UE, network entity 1105, or another network entity (e.g., gNB, TRP, etc.)) may transmit another sensing signal). Sensing signal transmission may involve implementing the STC profile determined at stage 1120. Reflected sensing signal 1136 (as a reflection of sensing signal 1134 or another sensing signal) may be received by UE 1101.

[0099] At stage 1140, UE 1101 may measure the reflected sensing signal 1136 and may report one or more corresponding measurements and / or processed measurements. At sub-stage 1142, UE 1101 may measure the reflected sensing signal 1136 and may send a measurement report 1144 to network entity 1105, which may include one or more original measurements and / or one or more processed measurements, such as one or more object ranges and / or one or more object directions and / or one or more object velocities. Sensing signal transmission (and reception and measurement) may also occur before determining the STC profile (e.g., as part of evaluating one or more STC profile conditions and / or as part of evaluating STC profile prioritization). Alternatively or additionally, at sub-stage 1146, network entity 1105 (e.g., RF sensing unit 660) may determine one or more target object ranges and / or one or more target object velocities similar to those in sub-stage 1142, for example, based on information in measurement report 1144. Measurement report 1144 may indicate whether an STC profile is applied to determine the reported RF sensing measurement information. Measurement report 1144 may indicate the applied and valid STC profile (e.g., one or more STC settings) (e.g., RF sensing that produces the desired accuracy (e.g., producing one or more RF sensing measurements that meet the desired accuracy (raw measurements and / or processed measurements))). Measurement report 1144 may indicate the validity of the indicated STC profile, for example, indicating one or more KPIs (e.g., measurement accuracy) for RF sensing performed using the indicated STC profile. Measurement report 1144 may indicate one or more conditions (e.g., area, clutter distribution) corresponding to RF sensing with the indicated valid STC profile applied. Network entity 1105 may, for example, use information about the valid STC profile and the conditions for the validity of the STC profile at sub-stage 1115 to determine STC configuration information, such as one or more STC profiles, one or more STC profile conditions, one or more STC prioritization rules, etc. Network entity 1105 may transmit this STC configuration information to UE 1101 and / or another UE for RF sensing when STC is applied. In this way, STC profile information may be crowdsourced by the UE to those UEs and / or other UEs.

[0100] Network entity 1105 (e.g., sensing unit 660) may transmit one or more determined ranges and / or one or more determined speeds. For example, network entity 1105 may transmit ranges and / or speeds to UE 1101, to another UE, to another network entity, etc.

[0101] refer to Figure 14 And further reference Figures 1 to 13The sensing method 1400 includes the stages shown. However, method 1400 is merely an example and not a limitation. Method 1400 can be modified, for example, by adding, removing, rearranging, combining, performing one or more stages concurrently, and / or splitting one or more individual stages into multiple stages.

[0102] At stage 1410, method 1400 includes implementing a sensitivity time control profile at the UE to change the gain applied over time to the sensed signal received by the UE. For example, at sub-stage 1142, the RF sensing unit 560 of UE 1101 may implement STC (e.g., as shown in the image) on the sensed signal 1136. Figure 10 The sensor profile shown is illustrated. The processor 510 (which may be combined with memory 530 and transceiver 520 (e.g., wireless receiver 244 (e.g., receiver 900) and antenna 246)) may include components for implementing the STC profile.

[0103] At stage 1420, method 1400 includes measuring a sensing signal to obtain a sensing signal measurement. For example, at sub-stage 1142, the RF sensing unit 560 of UE 1101 may measure the sensing signal 1136 with STC applied. Processor 510 (possibly combined with memory 530) may include components for measuring the sensing signal.

[0104] Method 1400 includes optional phases 1430 and / or 1440. Optionally, at phase 1430, method 1400 includes obtaining a sensitivity time control profile based on a sensitivity time control message received by the UE from a network entity. For example, UE 1101 (e.g., RF sensing unit 560) may receive an STC profile in an STC configuration information message 1116, or may select an STC profile based on information in message 1116 (e.g., priority information and / or condition information), or may derive a profile based on information in message 1116 (e.g., clutter information and / or condition information). Processor 510 (possibly combined with memory 530 and transceiver 520 (e.g., radio receiver 244 and antenna 246)) may include components for obtaining the STC profile based on the STC message. Optionally, at phase 1440, method 1400 includes sending a sensing report from the UE to the network entity, the sensing report indicating that a sensed signal has been measured and that sensitivity time control has been implemented to obtain the sensed signal measurement. For example, at sub-stage 1142, UE 1101 (e.g., RF sensing unit 560) may send a measurement report 1144 indicating RF sensing measurements (e.g., one or more RF sensing measurements) and indicating (explicitly or implicitly, e.g., by indicating the applied STC profile)) that an STC is used to obtain the RF sensing measurements. Processor 510 (possibly in conjunction with memory 530 and transceiver 520 (e.g., wireless transmitter 242 and antenna 246)) may include components for sending the sensing report.

[0105] Specific implementations of method 1400 may include one or more of the following features. In an example implementation, method 1400 includes obtaining a sensitivity time control profile based on a sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control. For example, the STC message may include an STC profile (e.g., in field 1310), a clutter distribution (e.g., in field 1320), and / or one or more conditions (e.g., in field 1330). In another example implementation, the sensitivity time control message indicates one or more criteria that the UE must satisfy to achieve sensitivity time control, and the one or more criteria that the UE must satisfy to achieve sensitivity time control include at least one of the following: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal. For example, an STC message may include one or more criteria for an STC profile (e.g., the region of the UE location, the sensed signal RSSI, the sensed signal RSRP, the sensed signal SINR, the sensed signal dynamic range, etc.) (e.g., in field 1330). In another example implementation, a sensitivity time control message indicates a sensitivity time control profile and includes at least one of the following: a sensed signal frequency range for the sensitivity time control profile, a sensed signal angle range for the sensitivity time control profile, a sensed signal pulse configuration for the sensitivity time control profile, or a sensed signal polarization for the sensitivity time control profile. For example, an STC message may include granular parameters for the STC profile (e.g., in field 1310). In another example implementation, the sensitivity time control profile is a first sensitivity time control profile, and the sensitivity time control message indicates the first sensitivity time control profile and a second time control profile, and indicates priority information, wherein implementing the first sensitivity time control profile includes implementing the first sensitivity time control profile based on the priority information.

[0106] Additionally or alternatively, specific implementations of method 1400 may include one or more of the following features. In an example implementation, method 1400 includes sending a sensing report to a network entity, wherein the sensing report indicates that a sensitivity timing control profile has been implemented by the UE to obtain sensing signal measurements, and indicates one or more conditions corresponding to the implementation of the sensitivity timing control profile. For example, the sensing report may include one or more KPIs indicating quality sensing signal measurements, and the conditions may include frequency, UE location, and / or clutter distribution of the UE location. In another example implementation, method 1400 further includes sending a capability message from the UE to the network entity, the capability message indicating that the UE implements a first capability of sensitivity timing control to obtain sensing signal measurements. For example, UE 1101 (e.g., capability unit 550) may send an STC capability message indicating the capability of implementing STC. For example, the indication may be an explicit indication (e.g., in field 1210) and / or an implicit indication (e.g., an indication that one or more STC profiles are available (e.g., in field 1220) and / or an indication of one or more available STC profiles (e.g., in field 1230)). Processor 510 (possibly in conjunction with memory 530 and transceiver 520 (e.g., wireless transmitter 242 and antenna 246)) may include components for transmitting capability messages. In another example implementation, the capability message instructs the UE to implement a second capability based on at least one of the following: sensing signal frequency, sensing signal direction, sensing signal polarization, or sensing signal pulse configuration. For example, the capability message may include one or more parameters as shown in field 1240.

[0107] refer to Figure 15 And further reference Figures 1 to 13 Method 1500 for supporting sensitivity time control by a UE includes the stages shown. However, method 1500 is merely an example and not a limitation. Method 1500 can be modified, for example, by adding, removing, rearranging, combining, performing one or more stages concurrently, and / or splitting one or more individual stages into multiple stages.

[0108] At stage 1510, method 1500 includes determining sensitivity timing control configuration information at a network entity, the sensitivity timing control configuration information indicating at least one of the following: a sensitivity timing control profile, a location-corresponding clutter distribution, or one or more criteria that the UE must satisfy to achieve sensitivity timing control. For example, at sub-stage 1115, network entity 1105 (e.g., STC unit 650) may determine STC configuration information including an STC profile, clutter distribution, and / or one or more conditions for achieving the STC profile. Processor 610 (possibly in conjunction with memory 630, and possibly in conjunction with transceiver 620 (e.g., radio receiver 444 and antenna 446, and / or wired receiver 454, or radio receiver 344 and antenna 346, and / or wired receiver 354)) may include components for determining the STC configuration information.

[0109] At stage 1520, method 1500 includes transmitting sensitivity timing control configuration information from a network entity to a UE via one or more transceivers. For example, at sub-stage 1115, network entity 1105 (e.g., STC unit 650) may transmit an STC configuration information message 1116 to UE 1101. Processor 610 (possibly in conjunction with memory 630, and possibly in conjunction with transceiver 620 (e.g., wireless transmitter 442 and antenna 446, and / or wired transmitter 452, or wireless transmitter 342 and antenna 346, and / or wired transmitter 352)) may include components for transmitting the STC configuration information.

[0110] Specific implementations of method 1500 may include one or more of the following features. In an example implementation, the sensitivity time control configuration information indicates one or more criteria that the UE must satisfy to achieve sensitivity time control, and the one or more criteria that the UE must satisfy to achieve sensitivity time control include at least one of the following: region, signal strength of a sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal. For example, the STC configuration information message may include one or more conditions indicated in field 1330. In another example implementation, the sensitivity time control configuration information indicates a sensitivity time control profile and includes at least one of the following: a sensed signal frequency range for the sensitivity time control profile, a sensed signal angle range for the sensitivity time control profile, a sensed signal pulse configuration for the sensitivity time control profile, or a sensed signal polarization for the sensitivity time control profile. For example, the STC configuration information message may include an STC profile and one or more granular parameters for the STC profile, such as those shown in field 1310. In another example implementation, the sensitivity time control profile is a first sensitivity time control profile, wherein the sensitivity time control configuration information indicates the first sensitivity time control profile and a second time control profile and indicates priority information indicating how to determine which of the first sensitivity time control profile and the second time control profile is used by the UE to measure sensed signals. For example, the STC configuration message may include multiple STC profiles and information for determining the priority of the STC profiles, such as, for example, as shown in field 1340 of Table 1300. In another example implementation, method 1500 further includes receiving a sensitivity time control report from a second UE by a network entity, the sensitivity time control report indicating a sensitivity time control profile and one or more operating conditions corresponding to the sensitivity time control profile, and method 1500 further includes at least one of the following: sending sensitivity time control configuration information indicating a sensitivity time control profile from the network entity to the first UE based on the first UE satisfying one or more operating conditions; or sending sensitivity time control configuration information indicating a sensitivity time control profile and one or more operating conditions corresponding to the sensitivity time control profile from the network entity to the first UE. For example, network entity 1105 (e.g., STC unit 650) may receive measurement report 1144 from UE 1101, which indicates the STC profile used by UE 1101 to measure RF sensing signals and one or more operating conditions (e.g., the location of UE 1101, clutter distribution during sensing, etc.).Network entity 1105 (e.g., STC unit 650) may send an STC configuration information message 1116 having an STC profile from report 1144 to UE 1101 (and / or another UE 1101) based on the fulfillment of operating conditions (e.g., UE 1101 is in the area indicated in report 1144). Alternatively or additionally, network entity 1105 (e.g., STC unit 650) may send an STC configuration information message 1116 having an STC profile from report 1144 and operating conditions to UE 1101 and / or another UE, for example, such that UE 1101 and / or the other UE may determine to use the indicated STC profile when the operating conditions are met (e.g., when UE 1101 is in the indicated area). The processor 610 (possibly in conjunction with memory 630, and possibly in conjunction with transceiver 620 (e.g., wireless transmitter 442 and antenna 446, and / or wired transmitter 452, or wireless transmitter 342 and antenna 346, and / or wired transmitter 352)) may include components for transmitting sensitivity time control configuration information indicating a sensitivity time control profile, and / or may include components for transmitting sensitivity time control configuration information indicating a sensitivity time control profile and one or more operating conditions corresponding to the sensitivity time control profile.

[0111] Specific implementation examples

[0112] Specific implementation examples are provided in the following numbered clauses.

[0113] Clause 1. A UE (User Equipment), said UE (User Equipment) comprising:

[0114] One or more memory units;

[0115] One or more transceivers, the one or more transceivers being configured to receive sensing signals; and

[0116] One or more processors, communicatively coupled to one or more memories and one or more transceivers, are configured to:

[0117] Implement a sensitivity time control profile to change the gain applied to the sensed signal by the one or more transceivers over time; and

[0118] Measure the sensing signal to obtain a sensing signal measurement;

[0119] The one or more processors mentioned are at least one of the following:

[0120] Configured to obtain the sensitivity time control profile based on sensitivity time control messages received from a network entity via the one or more transceivers; or

[0121] Configured to send a sensing report to the network entity via the one or more transceivers, the sensing report indicating whether the measurement of the sensing signal and sensitivity time control have been implemented to obtain the sensing signal measurement.

[0122] Clause 2. The UE of claim 1, wherein the one or more processors are configured to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control.

[0123] Clause 3. The UE of claim 2, wherein the one or more processors are configured to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message instructs the UE to satisfy the one or more criteria for sensitivity time control, and wherein the one or more criteria for sensitivity time control to be satisfied by the UE include at least one of the following: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference plus noise ratio of the sensed signal, or dynamic range of the sensed signal.

[0124] Clause 4. The UE of claim 2, wherein the one or more processors are configured to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the sensitivity time control profile and includes at least one of: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

[0125] Clause 5. The UE of claim 2, wherein the sensitivity timing control profile is a first sensitivity timing control profile, wherein the one or more processors are configured to obtain the sensitivity timing control profile based on the sensitivity timing control message, wherein the sensitivity timing control message indicates the first sensitivity timing control profile and a second timing control profile and indicates priority information, and wherein the one or more processors are configured to determine the implementation of the first sensitivity timing control profile based on the priority information.

[0126] Clause 6. The UE of claim 1, wherein the one or more processors are configured to send the sensing report to the network entity, wherein the sensing report indicates that the sensitivity time control profile has been implemented by the one or more processors to obtain the sensing signal measurement, and indicates one or more conditions corresponding to the implementation of the sensitivity time control profile.

[0127] Clause 7. The UE of claim 1, wherein the one or more processors are further configured to send a capability message to the network entity via the one or more transceivers, the capability message instructing the UE to implement sensitivity timing control to obtain a first capability for sensing signal measurement.

[0128] Clause 8. The UE of claim 7, wherein the capability message indicates that the UE implements a second capability of a different sensitivity time control profile based on at least one of: sensing signal frequency, sensing signal direction, sensing signal polarization, or sensing signal pulse configuration.

[0129] Clause 9. A sensing method, the sensing method comprising:

[0130] Implement a sensitivity time control profile at the UE (User Equipment) to change the gain applied over time to the sensed signal received by the UE; and

[0131] Measure the sensing signal to obtain a sensing signal measurement;

[0132] The method described herein includes at least one of the following:

[0133] The sensitivity time control configuration file is obtained based on the sensitivity time control message received by the UE from the network entity; or

[0134] The UE sends a sensing report to the network entity, the sensing report indicating that the measurement of the sensing signal and sensitivity time control have been implemented to obtain the sensing signal measurement.

[0135] Clause 10. The sensing method of claim 9, wherein the method includes obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control.

[0136] Clause 11. The sensing method of claim 10, wherein the method includes obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message instructs the UE to satisfy one or more criteria for achieving sensitivity time control, and wherein the one or more criteria for achieving sensitivity time control include at least one of: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

[0137] Clause 12. The sensing method of claim 10, wherein the method includes obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the sensitivity time control profile and includes at least one of: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

[0138] Clause 13. The sensing method of claim 10, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the method includes obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the first sensitivity time control profile and a second time control profile and indicates priority information, and wherein implementing the first sensitivity time control profile includes implementing the first sensitivity time control profile based on the priority information.

[0139] Clause 14. The sensing method of claim 9, wherein the method includes sending the sensing report to the network entity, wherein the sensing report indicates that the sensitivity time control profile has been implemented by the UE to obtain the sensing signal measurement, and indicates one or more conditions corresponding to the implementation of the sensitivity time control profile.

[0140] Clause 15. The sensing method of claim 9, further comprising sending a capability message from the UE to the network entity, the capability message instructing the UE to implement sensitivity time control to obtain a first capability for sensing signal measurement.

[0141] Clause 16. The sensing method of claim 15, wherein the capability message instructs the UE to implement a second capability of a different sensitivity time control profile based on at least one of: sensing signal frequency, sensing signal direction, sensing signal polarization, or sensing signal pulse configuration.

[0142] Clause 17. A UE (User Equipment), said UE comprising:

[0143] Components for implementing sensitivity time control profiles to change the gain applied over time to the sensing signal received by the UE; and

[0144] A component used to measure the sensing signal to obtain the sensing signal measurement;

[0145] The UE further includes at least one of the following:

[0146] A component for obtaining the sensitivity time control profile based on the sensitivity time control message received by the UE from the network entity; or

[0147] A component for sending a sensing report from the UE to the network entity, the sensing report indicating that the measurement of the sensing signal and sensitivity time control have been implemented to obtain the sensing signal measurement.

[0148] Clause 18. The UE of claim 17, wherein the UE includes the means for obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control.

[0149] Clause 19. The UE of claim 18, wherein the UE includes the component for obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message instructs the UE to satisfy one or more criteria for sensitivity time control, and wherein the one or more criteria for sensitivity time control to be satisfied by the UE include at least one of the following: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference plus noise ratio of the sensed signal, or dynamic range of the sensed signal.

[0150] Clause 20. The UE of claim 18, wherein the UE includes the component for obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the sensitivity time control profile and includes at least one of: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

[0151] Clause 21. The UE of claim 18, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the UE includes the means for obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the first sensitivity time control profile and a second time control profile and indicates priority information, and wherein the means for implementing the first sensitivity time control profile includes means for implementing the first sensitivity time control profile based on the priority information.

[0152] Clause 22. The UE of claim 17, wherein the UE includes the component for sending the sensing report to the network entity, wherein the sensing report indicates that the sensitivity time control profile has been implemented by the UE to obtain the sensing signal measurement, and indicates one or more conditions corresponding to the implementation of the sensitivity time control profile.

[0153] Clause 23. The UE of claim 17, further comprising a component for sending a capability message to the network entity, the capability message instructing the UE to implement sensitivity time control to obtain a first capability for sensing signal measurement.

[0154] Clause 24. The UE of claim 23, wherein the capability message indicates that the UE implements a second capability of a different sensitivity time control profile based on at least one of: sensing signal frequency, sensing signal direction, sensing signal polarization, or sensing signal pulse configuration.

[0155] Clause 25. A non-transitory processor-readable storage medium, the non-transitory processor-readable storage medium comprising processor-readable instructions that cause one or more processors of a UE (User Equipment) to perform the following operations:

[0156] Implement a sensitivity time control profile to change the gain applied over time to the sensing signal received by the UE; and

[0157] Measure the sensing signal to obtain a sensing signal measurement;

[0158] The storage medium further includes at least one of the following:

[0159] Processor-readable instructions for enabling one or more processors of the UE to obtain the sensitivity time control profile based on a sensitivity time control message received by the UE from a network entity; or

[0160] Processor-readable instructions for causing one or more processors of the UE to send a sensing report from the UE to the network entity, the sensing report indicating that the measurement of the sensing signal and sensitivity timing control have been implemented to obtain the sensing signal measurement.

[0161] Clause 26. The non-transitory processor-readable storage medium of claim 25, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for enabling one or more processors of the UE to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control.

[0162] Clause 27. The non-transitory processor-readable storage medium of claim 26, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for enabling one or more processors of the UE to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message instructs the UE to implement one or more criteria to satisfy the sensitivity time control, and wherein the one or more criteria to satisfy the sensitivity time control include at least one of the following: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

[0163] Clause 28. The non-transitory processor-readable storage medium of claim 26, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for causing one or more processors of the UE to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the sensitivity time control profile and includes at least one of: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

[0164] Clause 29. The non-transitory processor-readable storage medium of claim 26, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for causing one or more processors of the UE to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the first sensitivity time control profile and a second time control profile and indicates priority information, and wherein the processor-readable instructions for causing one or more processors of the UE to implement the first sensitivity time control profile include processor-readable instructions for causing one or more processors of the UE to implement the first sensitivity time control profile based on the priority information.

[0165] Clause 30. The non-transitory processor-readable storage medium of claim 25, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for causing one or more processors of the UE to send the sensing report to the network entity, wherein the sensing report indicates that the sensitivity time control profile has been implemented by the UE to obtain the sensing signal measurement, and indicates one or more conditions corresponding to the implementation of the sensitivity time control profile.

[0166] Clause 31. The non-transitory processor-readable storage medium of claim 25, the non-transitory processor-readable storage medium further comprising processor-readable instructions for causing one or more processors of the UE to send a capability message to the network entity, the capability message instructing the UE to implement sensitivity timing control to obtain a first capability for sensing signal measurement.

[0167] Clause 32. The non-transitory processor-readable storage medium of claim 31, wherein the capability message indicates that the UE implements a second capability of a different sensitivity time control profile based on at least one of: sensing signal frequency, sensing signal direction, sensing signal polarization, or sensing signal pulse configuration.

[0168] Clause 33. A network entity, said network entity comprising:

[0169] One or more memory units;

[0170] One or more transceivers; and

[0171] One or more processors, communicatively coupled to one or more memories and one or more transceivers, are configured to:

[0172] Determine sensitivity time control configuration information, which indicates at least one of the following: a sensitivity time control profile, a location-corresponding clutter distribution, or one or more criteria that the UE (User Equipment) must meet to achieve sensitivity time control; and

[0173] The sensitivity time control configuration information is sent to the UE via the one or more transceivers.

[0174] Clause 34. The network entity of claim 33, wherein the sensitivity time control configuration information indicates that the UE must satisfy one or more criteria to achieve sensitivity time control, and wherein the one or more criteria that the UE must satisfy to achieve sensitivity time control include at least one of the following: region, signal strength of a sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

[0175] Clause 35. The network entity of claim 33, wherein the sensitivity time control configuration information indicates the sensitivity time control profile and includes at least one of the following: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

[0176] Clause 36. The network entity of claim 33, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the sensitivity time control configuration information indicates the first sensitivity time control profile and a second time control profile and indicates priority information, the priority information indicating how to determine which of the first sensitivity time control profile and the second time control profile is used by the UE to measure the sense signal.

[0177] Clause 37. The network entity of claim 33, wherein the UE is a first UE, wherein:

[0178] The one or more processors are further configured to receive a sensitivity time control report from a second UE via the one or more transceivers, the sensitivity time control report indicating the sensitivity time control profile and one or more operating conditions corresponding to the sensitivity time control profile; and

[0179] The one or more processors are at least one of the following:

[0180] Configured to send sensitivity time control configuration information, indicating the sensitivity time control configuration file, to the first UE via the one or more transceivers based on the first UE satisfying the one or more operating conditions; or

[0181] The device is configured to send the sensitivity time control configuration information to the first UE via the one or more transceivers, the sensitivity time control configuration information indicating the sensitivity time control profile and the one or more operating conditions corresponding to the sensitivity time control profile.

[0182] Clause 38. A method for supporting sensitivity time control sensed by a UE (User Equipment), the method comprising:

[0183] Sensitivity time control configuration information is determined at the network entity, the sensitivity time control configuration information indicating at least one of the following: a sensitivity time control profile, a location-corresponding clutter distribution, or one or more criteria that the UE must satisfy to implement sensitivity time control; and

[0184] The sensitivity time control configuration information is sent from the network entity to the UE via one or more transceivers.

[0185] Clause 39. The method of claim 38, wherein the sensitivity time control configuration information indicates that the UE must satisfy one or more criteria to achieve sensitivity time control, and wherein the one or more criteria that the UE must satisfy to achieve sensitivity time control include at least one of the following: region, signal strength of a sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

[0186] Clause 40. The method of claim 38, wherein the sensitivity time control configuration information indicates the sensitivity time control profile and includes at least one of the following: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

[0187] Clause 41. The method of claim 38, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the sensitivity time control configuration information indicates the first sensitivity time control profile and a second time control profile and indicates priority information, the priority information indicating how to determine which of the first sensitivity time control profile and the second time control profile is used by the UE to measure the sense signal.

[0188] Clause 42. The method of claim 38, wherein the UE is a first UE, wherein:

[0189] The method further includes: the network entity receiving a sensitivity time control report from a second UE, the sensitivity time control report indicating the sensitivity time control profile and one or more operating conditions corresponding to the sensitivity time control profile; and

[0190] The method further includes at least one of the following:

[0191] The network entity sends sensitivity time control configuration information, indicating the sensitivity time control configuration file, to the first UE based on the first UE satisfying one or more of the operating conditions; or

[0192] The network entity sends the sensitivity time control configuration information to the first UE, the sensitivity time control configuration information indicating the sensitivity time control configuration file and one or more operating conditions corresponding to the sensitivity time control configuration file.

[0193] Clause 43. A network entity, said network entity comprising:

[0194] Components for determining sensitivity time control configuration information, said sensitivity time control configuration information indicating at least one of the following: a sensitivity time control profile, a location-corresponding clutter distribution, or one or more criteria that the UE (User Equipment) must meet to achieve sensitivity time control; and

[0195] A component for transmitting the sensitivity time control configuration information to the UE via one or more transceivers.

[0196] Clause 44. The network entity of claim 43, wherein the sensitivity time control configuration information indicates that the UE must satisfy one or more criteria to achieve sensitivity time control, and wherein the one or more criteria that the UE must satisfy to achieve sensitivity time control include at least one of the following: region, signal strength of a sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

[0197] Clause 45. The network entity of claim 43, wherein the sensitivity time control configuration information indicates the sensitivity time control profile and includes at least one of the following: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

[0198] Clause 46. The network entity of claim 43, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the sensitivity time control configuration information indicates the first sensitivity time control profile and a second time control profile and indicates priority information, the priority information indicating how to determine which of the first sensitivity time control profile and the second time control profile is used by the UE to measure the sense signal.

[0199] Clause 47. The network entity of claim 43, wherein the UE is a first UE, wherein:

[0200] The network entity includes components for receiving a sensitivity time control report from a second UE, the sensitivity time control report indicating the sensitivity time control profile and one or more operating conditions corresponding to the sensitivity time control profile; and

[0201] The network entity further includes at least one of the following:

[0202] A component for sending sensitivity time control configuration information indicating the sensitivity time control configuration file to the first UE based on the first UE satisfying one or more operating conditions; or

[0203] A component for sending the sensitivity time control configuration information to the first UE, the sensitivity time control configuration information indicating the sensitivity time control configuration file and one or more operating conditions corresponding to the sensitivity time control configuration file.

[0204] Clause 48. A non-transitory processor-readable storage medium, the non-transitory processor-readable storage medium comprising processor-readable instructions that cause one or more processors of a network entity to perform the following operations:

[0205] Determine sensitivity time control configuration information, which indicates at least one of the following: a sensitivity time control profile, a location-corresponding clutter distribution, or one or more criteria that the UE (User Equipment) must meet to achieve sensitivity time control; and

[0206] The sensitivity time control configuration information is sent to the UE via one or more transceivers.

[0207] Clause 49. The non-transitory processor-readable storage medium of claim 48, wherein the sensitivity timing control configuration information indicates that the UE must satisfy one or more criteria to achieve sensitivity timing control, and wherein the one or more criteria that the UE must satisfy to achieve sensitivity timing control include at least one of the following: region, signal strength of a sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

[0208] Clause 50. The non-transitory processor-readable storage medium of claim 48, wherein the sensitivity time control configuration information indicates the sensitivity time control profile and includes at least one of: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

[0209] Clause 51. The non-transitory processor-readable storage medium of claim 48, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the sensitivity time control configuration information indicates the first sensitivity time control profile and a second time control profile and indicates priority information, the priority information indicating how to determine which of the first sensitivity time control profile and the second time control profile is used by the UE to measure the sense signal.

[0210] Clause 52. A non-transitory processor-readable storage medium as described in Clause 48, wherein the UE is a first UE, wherein:

[0211] The non-transient processor-readable storage medium further includes processor-readable instructions for enabling one or more processors of the network entity to receive a sensitivity time control report from the second UE, the sensitivity time control report indicating the sensitivity time control profile and one or more operating conditions corresponding to the sensitivity time control profile; and

[0212] The non-transitory processor-readable storage medium further includes at least one of the following:

[0213] The one or more processors of the network entity are configured to send a processor-readable instruction to the first UE, indicating the sensitivity time control configuration information of the sensitivity time control profile, based on the first UE satisfying the one or more operating conditions; or

[0214] This is used to cause one or more processors of the network entity to send the sensitivity time control configuration information to the first UE, the sensitivity time control configuration information indicating the sensitivity time control profile and the one or more operating conditions corresponding to the sensitivity time control profile.

[0215] Other considerations

[0216] Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software and computers, the functions described above can be implemented using software, hardware, firmware, hardwiring, or any combination thereof executed by a processor. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0217] As used herein, the singular forms “a,” “an,” and “the” also include the plural forms, unless the context clearly indicates otherwise. Thus, references to a device in the singular form included in the claims (e.g., “device,” “the / said device”) include at least one of such devices (i.e., one or more) (e.g., “processor” includes at least one processor (e.g., one processor, two processors, etc.), “the / said processor” includes at least one processor, “memory” includes at least one memory, “the / said memory” includes at least one memory, etc.). The phrases “at least one” and “one or more” are used interchangeably, and such that the object referred to by “at least one” and the object referred to by “one or more” include embodiments having one referred object and embodiments having multiple referred objects. For example, “at least one processor” and “one or more processors” each include embodiments having one processor and embodiments having multiple processors.

[0218] As used herein, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0219] Furthermore, as used herein, the "or" (possibly followed by "at least one of" or "one or more of") used in the item enumeration indicates a disjunctive enumeration such that an enumeration of, for example, "at least one of A, B, or C," or an enumeration of "one or more of A, B, or C," or an enumeration of "A or B or C" represents A or B or C or AB (A and B) or AC (A and C) or BC (B and C) or ABC (i.e., A and B and C), or a combination having more than one feature (e.g., AA, AAB, ABBC, etc.). Therefore, a statement that an item (e.g., a processor) is configured to perform a function relating to at least one of A or B, or a statement that an item is configured to perform function A or function B, indicates that the item can be configured to perform a function relating to A, or can be configured to perform a function relating to B, or can be configured to perform a function relating to both A and B. For example, the phrase "a processor configured to measure at least one of A or B" or "a processor configured to measure A or measure B" means that the processor can be configured to measure A (and may or may not be configured to measure B), or can be configured to measure B (and may or may not be configured to measure A), or can be configured to measure both A and B (and can be configured to select which of A and B or measure both). Similarly, a description of a component for measuring at least one of A or B includes: a component for measuring A (which may or may not be able to measure B), or a component for measuring B (which may or may not be configured to measure A), or a component for measuring A and B (which may be able to select which of A and B or measure both). As another example, a description of an item (e.g., a processor) being configured to perform at least one of function X or function Y means that the item can be configured to perform function X, or can be configured to perform function Y, or can be configured to perform both functions X and Y. For example, the phrase "processor configured to measure at least one of X or Y" means that the processor can be configured to measure X (and may or may not be configured to measure Y), or can be configured to measure Y (and may or may not be configured to measure X), or can be configured to measure both X and Y (and can be configured to select which of X and Y or measure both).

[0220] As used herein, unless otherwise stated, a description of a function or operation as “based on” an item or condition means that the function or operation is based on the described item or condition and may be based on one or more items and / or conditions other than the described item or condition.

[0221] Substantial changes can be made depending on specific requirements. For example, custom hardware may be used, and / or specific elements may be implemented in the hardware, in software executed by the processor (including portable software such as applets), or both. Furthermore, connections to other computing devices, such as network input / output devices, may be employed. Unless otherwise specified, components shown in the figures and / or discussed herein that are connected or communicate with each other (functionally or otherwise) are communicatively coupled. That is, these components may be connected directly or indirectly to enable communication between them.

[0222] The systems and devices discussed above are examples. Various configurations may appropriately omit, substitute, or add various processes or components. For example, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of a configuration may be combined in a similar manner. Furthermore, technology is constantly evolving, and therefore many elements are examples and do not limit the scope of this disclosure or the claims.

[0223] A wireless communication system is a system in which communication is transmitted wirelessly between wireless communication devices, that is, through the propagation of electromagnetic waves and / or sound waves through the atmosphere rather than through wires or other physical connections. A wireless communication system (also called a wireless communication system or wireless communication network) may not transmit all communication wirelessly, but is configured to allow at least some communication to be transmitted wirelessly. Furthermore, the term "wireless communication device" or similar terms do not require the device to be functionally exclusive or even primarily used for communication, do not require that communication using the wireless communication device be exclusive or even primarily wireless, and do not require that the device be a mobile device, but rather indicate that the device includes wireless communication capabilities (one-way or two-way), for example, including at least one radio component (each radio component being part of a transmitter, receiver, or transceiver) for wireless communication.

[0224] Specific details are provided in this description to offer a thorough understanding of the example configurations, including specific implementations. However, the configurations can be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail to avoid obscuring these configurations. The description herein provides example configurations and does not limit the scope, applicability, or configuration of the claims. Rather, the preceding description of the configurations provides a description for implementing the described techniques. Various changes can be made to the function and arrangement of the elements.

[0225] As used herein, the terms “processor-readable medium,” “machine-readable medium,” and “computer-readable medium” refer to any medium that participates in providing data that enables a machine to operate in a particular manner. Using a computing platform, various processor-readable media may involve providing instructions / code to a processor for execution, and / or may be used to store and / or carry such instructions / code (e.g., as signals). In many specific implementations, processor-readable media are physical and / or tangible storage media. Such media can take many forms, including but not limited to non-volatile and volatile media. Non-volatile media include, for example, optical discs and / or magnetic disks. Volatile media include, but are not limited to, dynamic memory.

[0226] Having described several example configurations, various modifications, alternative constructions, and equivalents can be used. For example, the above elements can be components of a larger system, where other rules may take precedence over or otherwise modify the application of this disclosure. Furthermore, several operations may be performed before, during, or after considering the above elements. Accordingly, the above description does not limit the scope of the claims.

[0227] Unless otherwise indicated, the terms "about" and / or "approximately" as used herein when referring to measurable values ​​(such as quantities, durations of time, etc.) cover variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, as appropriate in the context of the systems, devices, circuits, methods, and other specific embodiments described herein. Similarly, unless otherwise indicated, the term "substantially" as used herein when referring to measurable values ​​(such as quantities, durations of time, physical properties (such as frequencies), etc.) also covers variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, as appropriate in the context of the systems, devices, circuits, methods, and other specific embodiments described herein.

[0228] A statement that a value exceeds (or is greater than or higher than) a first threshold is equivalent to a statement that a value meets or exceeds a second threshold slightly greater than the first threshold. For example, in the resolution of the computing system, the second threshold is one value higher than the first threshold. A statement that a value is less than the first threshold (or within or below the first threshold) is equivalent to a statement that a value is less than or equal to a second threshold slightly lower than the first threshold. For example, in the resolution of the computing system, the second threshold is one value lower than the first threshold.

Claims

1. A UE (User Equipment), the UE comprising: One or more memory units; One or more transceivers, the one or more transceivers being configured to receive sensing signals; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, are configured to: Implement a sensitivity time control profile to change the gain applied to the sensed signal by the one or more transceivers over time; and Measure the sensing signal to obtain a sensing signal measurement; The one or more processors mentioned are at least one of the following: Configured to obtain the sensitivity time control profile based on sensitivity time control messages received from a network entity via the one or more transceivers; or Configured to send a sensing report to the network entity via the one or more transceivers, the sensing report indicating whether the measurement of the sensing signal and sensitivity time control have been implemented to obtain the sensing signal measurement.

2. The UE of claim 1, wherein the one or more processors are configured to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control.

3. The UE of claim 2, wherein the one or more processors are configured to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message instructs the UE to satisfy the one or more criteria for achieving sensitivity time control, and wherein the one or more criteria for achieving sensitivity time control include at least one of the following: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

4. The UE of claim 2, wherein the one or more processors are configured to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the sensitivity time control profile and includes at least one of the following: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

5. The UE of claim 2, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the one or more processors are configured to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the first sensitivity time control profile and a second time control profile and indicates priority information, and wherein the one or more processors are configured to determine the implementation of the first sensitivity time control profile based on the priority information.

6. The UE of claim 1, wherein the one or more processors are configured to send the sensing report to the network entity, wherein the sensing report indicates that the sensitivity time control profile has been implemented by the one or more processors to obtain the sensing signal measurement, and indicates one or more conditions corresponding to the implementation of the sensitivity time control profile.

7. The UE of claim 1, wherein the one or more processors are further configured to send a capability message to the network entity via the one or more transceivers, the capability message instructing the UE to implement sensitivity timing control to obtain a first capability for sensing signal measurement.

8. The UE of claim 7, wherein the capability message indicates that the UE implements a second capability of a different sensitivity time control profile based on at least one of the following: sensing signal frequency, sensing signal direction, sensing signal polarization, or sensing signal pulse configuration.

9. A sensing method, the sensing method comprising: Implement a sensitivity time control profile at the UE (User Equipment) to change the gain applied over time to the sensing signal received by the UE; as well as Measure the sensing signal to obtain a sensing signal measurement; The method described herein includes at least one of the following: The sensitivity time control configuration file is obtained based on the sensitivity time control message received by the UE from the network entity; or The UE sends a sensing report to the network entity, the sensing report indicating that the measurement of the sensing signal and sensitivity time control have been implemented to obtain the sensing signal measurement.

10. The sensing method of claim 9, wherein the method includes obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control.

11. The sensing method of claim 10, wherein the method includes obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message instructs the UE to satisfy one or more criteria for achieving sensitivity time control, and wherein the one or more criteria for achieving sensitivity time control include at least one of the following: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

12. The sensing method of claim 10, wherein the method includes obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the sensitivity time control profile and includes at least one of: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

13. The sensing method of claim 10, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the method includes obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the first sensitivity time control profile and a second time control profile and indicates priority information, and wherein implementing the first sensitivity time control profile includes implementing the first sensitivity time control profile based on the priority information.

14. The sensing method of claim 9, wherein the method includes sending the sensing report to the network entity, wherein the sensing report indicates that the sensitivity time control profile has been implemented by the UE to obtain the sensing signal measurement, and indicates one or more conditions corresponding to the implementation of the sensitivity time control profile.

15. The sensing method of claim 9, further comprising sending a capability message from the UE to the network entity, the capability message instructing the UE to implement sensitivity time control to obtain a first capability for sensing signal measurement.

16. The sensing method of claim 15, wherein the capability message instructs the UE to implement a second capability of a different sensitivity time control profile based on at least one of: sensing signal frequency, sensing signal direction, sensing signal polarization, or sensing signal pulse configuration.

17. A UE (User Equipment), the UE comprising: A component for implementing a sensitivity time control profile to change the gain applied over time to the sensing signal received by the UE; and A component used to measure the sensing signal to obtain the sensing signal measurement; The UE further includes at least one of the following: A component for obtaining the sensitivity time control profile based on the sensitivity time control message received by the UE from the network entity; or A component for sending a sensing report from the UE to the network entity, the sensing report indicating that the measurement of the sensing signal and sensitivity time control have been implemented to obtain the sensing signal measurement.

18. The UE of claim 17, wherein the UE includes the means for obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control.

19. The UE of claim 18, wherein the UE includes the component for obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message instructs the UE to satisfy one or more criteria for achieving sensitivity time control, and wherein the one or more criteria for achieving sensitivity time control include at least one of: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

20. The UE of claim 18, wherein the UE includes the means for obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the sensitivity time control profile and includes at least one of: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

21. The UE of claim 18, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the UE includes the means for obtaining the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the first sensitivity time control profile and a second time control profile and indicates priority information, and wherein the means for implementing the first sensitivity time control profile includes means for implementing the first sensitivity time control profile based on the priority information.

22. The UE of claim 17, wherein the UE includes the means for sending the sensing report to the network entity, wherein the sensing report indicates that the sensitivity time control profile has been implemented by the UE to obtain the sensing signal measurement, and indicates one or more conditions corresponding to the implementation of the sensitivity time control profile.

23. The UE of claim 17, further comprising a component for sending a capability message to the network entity, the capability message instructing the UE to implement sensitivity time control to obtain a first capability for sensing signal measurement.

24. The UE of claim 23, wherein the capability message indicates that the UE implements a second capability of a different sensitivity time control profile based on at least one of: sensing signal frequency, sensing signal direction, sensing signal polarization, or sensing signal pulse configuration.

25. A non-transitory processor-readable storage medium, the non-transitory processor-readable storage medium comprising processor-readable instructions that cause one or more processors of a UE (User Equipment) to perform the following operations: Implement a sensitivity time control profile to change the gain applied over time to the sensing signal received by the UE; and Measure the sensing signal to obtain a sensing signal measurement; The storage medium further includes at least one of the following: Processor-readable instructions for enabling one or more processors of the UE to obtain the sensitivity time control profile based on a sensitivity time control message received by the UE from a network entity; or Processor-readable instructions for causing one or more processors of the UE to send a sensing report from the UE to the network entity, the sensing report indicating that the measurement of the sensing signal and sensitivity timing control have been implemented to obtain the sensing signal measurement.

26. The non-transitory processor-readable storage medium of claim 25, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for enabling one or more processors of the UE to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates at least one of the following: the sensitivity time control profile, a clutter distribution corresponding to the location of the UE, or one or more criteria that the UE must satisfy to achieve sensitivity time control.

27. The non-transitory processor-readable storage medium of claim 26, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for enabling one or more processors of the UE to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message instructs the UE to satisfy one or more criteria for achieving sensitivity time control, and wherein the one or more criteria for achieving sensitivity time control include at least one of the following: region, signal strength of the sensed signal, signal-to-noise ratio of the sensed signal, signal-to-interference-plus-noise ratio of the sensed signal, or dynamic range of the sensed signal.

28. The non-transitory processor-readable storage medium of claim 26, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for causing one or more processors of the UE to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the sensitivity time control profile and includes at least one of: a sensing signal frequency range for the sensitivity time control profile, a sensing signal angle range for the sensitivity time control profile, a sensing signal pulse configuration for the sensitivity time control profile, or a sensing signal polarization for the sensitivity time control profile.

29. The non-transitory processor-readable storage medium of claim 26, wherein the sensitivity time control profile is a first sensitivity time control profile, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for causing one or more processors of the UE to obtain the sensitivity time control profile based on the sensitivity time control message, wherein the sensitivity time control message indicates the first sensitivity time control profile and a second time control profile and indicates priority information, and wherein the processor-readable instructions for causing one or more processors of the UE to implement the first sensitivity time control profile include processor-readable instructions for causing one or more processors of the UE to implement the first sensitivity time control profile based on the priority information.

30. The non-transitory processor-readable storage medium of claim 25, wherein the non-transitory processor-readable storage medium includes processor-readable instructions for causing one or more processors of the UE to send the sensing report to the network entity, wherein the sensing report indicates that the sensitivity time control profile has been implemented by the UE to obtain the sensing signal measurement, and indicates one or more conditions corresponding to the implementation of the sensitivity time control profile.

Images