Radio frequency sensing transmit scheduling

Abstract

A method for establishing or using a resource allocation, the method comprising: receiving, at a UE, a resource allocation indicating a plurality of first resources for non-sensing signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources comprising a first frequency-time combination, each of the second resources comprising a second frequency-time combination; and each of the second resources comprises a second frequency-time combination; and at least one of: covering the resource allocation by transmitting at least one sensing signal using at least one of the plurality of first resources; and transmitting, from the UE to the network entity: a request for a plurality of third resources for sensing signaling, each third resource comprising a third frequency-time combination; and a tolerance indication indicating an ability of the UE to tolerate puncturing of at least one third resource of the plurality of third resources.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of Greek application No. 20230100674, filed on August 16, 2023, entitled “RADIO FREQUENCY SENSING TRANSMISSION SCHEDULING”, which has been assigned to the assignee of this application and whose entire contents are incorporated herein by reference for all purposes. Background Technology

[0003] Wireless communication systems have undergone 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.7G networks), third-generation (3G) high-speed data wireless service with internet capabilities, and fourth-generation (4G) services (e.g., LTE or WiMax). ® This includes fifth-generation (5G) services, etc. Currently, there are many different types of wireless communication systems in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include Advanced Cellular System (AMPS) based on analog cellular networks, as well as 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), and GSM TDMA variants.

[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] As bandwidth allocated to cellular communication systems (5G and 5G+) increases and more use cases are introduced, Joint Communications / RF (Radio Frequency) Sensing (JCS) is becoming increasingly important for cellular systems (e.g., sixth-generation (6G) services). A JCS is an integrated system in which each of one or more signals can be used, for example, to simultaneously perform both wireless communication and radar sensing. In a JCS, time / frequency / space radio resources are allocated to support both objectives (communication and sensing) within the integrated system. JCS can improve the cost efficiency of radar and communication systems. In a radar system, a detection signal is transmitted to a non-cooperative or cooperative target, and useful information (e.g., distance and direction from the signal source to the target object) can be inferred from the signal echo from the target object. In a communication system, information is transmitted (and may be exchanged) between two or more cooperative transceivers. Cooperative transceivers are able to receive signals transmitted by other cooperative transceivers. Non-cooperative transceivers cannot or are unable to receive signals from a particular signal source and / or cannot or are unable to transmit signals that can be processed by the signal source. Summary of the Invention

[0006] An example UE (User Equipment) 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; wherein the one or more processors are configured to receive resource allocations via the one or more transceivers, the resource allocations indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination, and each of the second resources including a second frequency-time combination; wherein: the one or more processors are configured to override the resource allocations to transmit at least one sensing signal using at least one of the plurality of first resources; or the one or more processors are configured to: transmit requests for a plurality of third resources for sensing signal transmission via the one or more transceivers, each third resource including a third frequency-time combination; and transmit tolerance indications via the one or more transceivers, the tolerance indications indicating the UE's ability to tolerate punching in at least one of the plurality of third resources; or combinations thereof.

[0007] An example method for establishing or using a resource allocation, the method comprising: receiving a resource allocation at a UE, the resource allocation indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination and each of the second resources including a second frequency-time combination; and performing at least one of the following: overriding the resource allocation by transmitting at least one sensing signal using at least one of the plurality of first resources; and transmitting from the UE to a network entity: a request for a plurality of third resources for sensing signal transmission, each third resource including a third frequency-time combination; and a tolerance indication indicating the UE's ability to tolerate puncturing at least one of the plurality of third resources.

[0008] Another example UE includes: a component for receiving a resource allocation indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination and each of the second resources including a second frequency-time combination; and at least one of the following: a component for covering the resource allocation by transmitting at least one sensing signal using at least one of the plurality of first resources; and a component for transmitting to a network entity a request for a plurality of third resources for sensing signal transmission, each third resource including a third frequency-time combination; and a tolerance indication indicating the UE's ability to tolerate punching in at least one of the plurality of third resources.

[0009] An example non-transitory processor-readable storage medium includes processor-readable instructions that cause one or more processors of a UE to: receive a resource allocation indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination and each of the second resources including a second frequency-time combination; and at least one of the following: processor-readable instructions that cause one or more processors to overwrite the resource allocation by transmitting at least one sensing signal using at least one of the plurality of first resources; and processor-readable instructions that cause one or more processors to transmit to a network entity: a request for a plurality of third resources for sensing signal transmission, each third resource including a third frequency-time combination; and a tolerance indication indicating the UE's ability to tolerate punching in at least one of the plurality of third resources.

[0010] 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 and configured to: receive a first indication from a UE via the one or more transceivers, the first indication indicating a request for a plurality of first resources for sensing signal transmission, each of the plurality of first resources including a first frequency-time combination; receive a second indication from the UE via the one or more transceivers, the second indication indicating the UE's ability to tolerate puncturing at least one of the plurality of first resources; determine a resource allocation for the UE based on the second indication, the resource allocation indicating a plurality of second resources for non-sensing signal transmission and indicating a plurality of third resources for sensing signal transmission, at least one of the plurality of second resources including a corresponding at least one of the plurality of first resources, each of the plurality of second resources including a second frequency-time combination, and each of the plurality of third resources including a third frequency-time combination; and transmit the resource allocation to the UE via the one or more transceivers.

[0011] An example resource allocation determination method includes: receiving a first indication from a UE at a network entity, the first indication indicating a request for a plurality of first resources for sensing signal transmission, each of the plurality of first resources including a first frequency-time combination; receiving a second indication at the network entity, the second indication indicating the UE's ability to tolerate puncturing at least one of the plurality of first resources; determining, at the network entity and based on the second indication, a resource allocation for the UE, the resource allocation indicating a plurality of first and second resources for non-sensing signal transmission and indicating a plurality of third resources for sensing signal transmission, at least one of the plurality of second resources including a corresponding at least one of the plurality of first resources, each of the plurality of second resources including a second frequency-time combination, and each of the plurality of third resources including a third frequency-time combination; and sending the resource allocation from the network entity to the UE.

[0012] Another example network entity includes: components for receiving a first indication from a UE, the first indication indicating a request for a plurality of first resources for sensing signal transmission, each of the plurality of first resources including a first frequency-time combination; components for receiving a second indication indicating the UE's ability to tolerate puncturing at least one of the plurality of first resources; components for determining resource allocation for the UE based on the second indication, the resource allocation indicating a plurality of first and second resources for non-sensing signal transmission and indicating a plurality of third resources for sensing signal transmission, at least one of the plurality of second resources including a corresponding at least one of the plurality of first resources, each of the plurality of second resources including a second frequency-time combination, and each of the plurality of third resources including a third frequency-time combination; and components for transmitting the resource allocation to the UE.

[0013] 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: receive a first indication from a UE, the first indication indicating a request for a plurality of first resources for sensing signal transmission, each of the plurality of first resources including a first frequency-time combination; receive a second indication indicating that the UE tolerates the ability to punch through at least one of the plurality of first resources; determine, based on the second indication, a resource allocation for the UE, the resource allocation indicating a plurality of first and second resources for non-sensing signal transmission, and indicating a plurality of third resources for sensing signal transmission, at least one of the plurality of second resources including a corresponding at least one of the plurality of first resources, each of the plurality of second resources including a second frequency-time combination, and each of the plurality of third resources including a third frequency-time combination; and send the resource allocation to the UE. Attached Figure Description

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

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

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

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

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

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

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

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

[0022] Figure 9 This is a block diagram of a multi-station sensing system.

[0023] Figure 10 This is a block diagram of another multi-station sensing system.

[0024] Figure 11 It is a flowchart of signals and processes used to determine the distance to and / or the speed of a target object using radio frequency sensing.

[0025] Figure 12 It is a timing diagram of the coverage request sensing signal transmission schedule with a punch-hole sensing cycle.

[0026] Figure 13 It is a timing diagram of coverage signal transmission scheduling with opportunities for coverage non-sensory signal transmission.

[0027] Figure 14 It is a flowchart for establishing or using signal transmission scheduling methods.

[0028] Figure 15 This is a flowchart of the signal transmission scheduling method.

[0029] Figure 16 It is a timing diagram of the signal transmission time slots.

[0030] Figure 17 It is a timing diagram of the sensor signal configuration with a periodic transmission pattern. Detailed Implementation

[0031] This document discusses techniques for determining and / or overriding requested and / or allocated signal transmission resources. For example, a set of requested signal transmission configurations can be overridden to puncture one or more requested opportunities for sensing signal transmission, such that sensing signals are not transmitted on one or more requested sensing signal transmission resources, for example, where the user equipment (UE) uses the requested sensing signal transmission resources to transmit non-sensing signals, or the UE does not use the requested resources to transmit signals. As another example, puncturing one or more resources requested for sensing signal transmission may be subject to one or more conditions. As another example, one or more UEs may provide information to a network entity about the type and level of puncturing of requested sensing signal transmissions that the respective UE can afford. The network entity can use the information from the UE to determine which resources to allocate for sensing signal transmissions from the UE. As another example, the UE (user equipment) may overridden resource allocation (which conforms to a time-domain duplex (TDD) signal transmission configuration) to transmit sensing signals using one or more resources allocated for purposes other than sensing signal transmission. However, other configurations / implementations may also be used.

[0032] The projects and / or techniques described herein can provide one or more of the following capabilities, as well as others not mentioned. Sensing performance criteria can be met even with fewer sensing signal transmission resources allocated than requested. Non-sensing signal transmission can be used instead of requested sensing signal transmission due to a lack of sensing signal transmission acceptable to the user equipment. Sensing performance criteria can be met by performing sensing transmission on resources nominally not permitted for sensing transmission according to one or more conditions. Other capabilities can be provided, and not every specific embodiment of this disclosure is required to provide any, let alone all, of the capabilities discussed.

[0033] 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).

[0034] Radio frequency (RF) sensing is used to determine information about a device's environment. In RF sensing, an RF signal is transmitted by a transmitter, reflected from a target object, and received by a receiver. 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.

[0035] 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 functions 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.

[0036] 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.).

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

[0038] 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 phones, 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.

[0039] 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).

[0040] refer to Figure 1Examples 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 1 Such 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.

[0041] like Figure 1As 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.

[0042] Figure 1Generalized 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.

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

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

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

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

[0047] 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).

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

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

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

[0051] 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).

[0052] 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 divide 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 transmitting 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) protocols 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.

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

[0054] gNB 110a, 110b, and ng-eNB 114 can communicate with AMF 115; for positioning functions, 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 entities 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 positioning functionality (including the derivation of the location of UE 105) may be performed at UE 105 (e.g., using signal measurements obtained by UE 105 against signals transmitted by radio nodes (such as gNB110a, 110b, and / or ng-eNB 114), and / or auxiliary data provided to UE 105, for example, by LMF 120). AMF 115 may serve as a control node for handling signaling between UE 105 and 5GC 140 and may provide QoS (Quality of Service) streaming and session management. AMF 115 may support the mobility of UE 105 (including cell changes and handover) and may participate in supporting signaling connections with UE 105.

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

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

[0057] 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, which is 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.

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

[0059] 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).

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

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

[0062] 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).

[0063] 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 perform voice, data, location, and other functions). 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) in 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.

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

[0065] Also refer to Figure 2 UE 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 the functions performed by one or more processors among processors 230-234. The description herein may refer to the functions performed by UE 200 as a shorthand for the functions performed by one or more appropriate components of UE 200. 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.

[0066] 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).

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

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

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

[0070] The description herein refers to the functions 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 functions performed by processor 310 as a shorthand for the functions performed by one or more processors included in processor 310. The description herein may refer to the functions performed by TRP 300 as a shorthand for the functions 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 of memory 311. The functionality of processor 310 is discussed more fully below.

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

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

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

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

[0075] 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).

[0076] 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).

[0077] Sensing transmission scheduling and coverage

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

[0079] The description herein may refer to the processor 510 performing a function, 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 a function as a shorthand for one or more appropriate components of the UE 500 (e.g., processor 510 and memory 530) performing that function. The processor 510 (possibly in conjunction with memory 530 and, where appropriate, transceiver 520) may include a capability unit 550 and / or a resource allocation overlay unit 560. The capability unit 550 may be configured to transmit a capability message instructing one or more capabilities of the UE 500 to puncture one or more request sensing signal transmission resources and / or an overlay signal transmission allocation of the UE 500 (e.g., an allocation conforming to time-division duplex scheduling) to use one or more resources allocated for purposes other than sensing signal transmission to transmit sensing signals. If a requested sensing signal transmission resource (e.g., a channel resource (e.g., an OFDM (Orthogonal Frequency Division Multiplexing) resource element or OFDM resource block) requested by the UE for sensing signal transmission) is not used by the UE 500 for sensing signal transmission, that resource is punctured. For example, one or more requested sensing signal transmission resources can be punctured by transmitting or receiving signals (sensing or otherwise) without the UE 500 using the requested but punctured resource, or by the UE 500 using the requested resource to transmit or receive non-sensing signals (e.g., communication signals). The resource allocation overlay unit 560 can be configured to overlay signal transmission allocations (e.g., resources allocated according to Time Division Duplex (TDD) scheduling) to transmit sensing signals using one or more resources allocated for non-sensing signal transmission (e.g., UL communication signal transmission, DL communication signal reception, SL communication signal transmission and / or reception, etc.). While the description herein may focus on TDD, unless otherwise indicated, the description and claims may also apply to other signal transmission configurations. The capability unit 550 and the resource allocation overlay unit 560 are further discussed below, and any of the functions of the capability unit 550 and / or the resource allocation overlay unit 560 may be generally referred to by the processor 510 or by the UE 500, wherein the UE 500 is configured to perform these functions.

[0080] Also refer to Figure 6Network 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 4 Any 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.

[0081] 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 appropriate 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 resource allocation unit 650 and / or sensing unit 660. Resource allocation unit 650 may be configured, for example, to use request and capability information from UE 500 to determine the allocation of channel resources (which may be referred to as communication resources, signal transmission resources, or resources) for UE 500 for sensing signal transmission and for one or more other purposes (e.g., for non-sensing signal transmission and / or for non-sensing signal reception). The allocation of resources for other purposes may include one or more resources requested by UE 500 for sensing signal transmission, and therefore, resources requested for sensing signal transmission may be punched. Each resource includes a frequency-time combination, such as a time / frequency window, for transmitting (receiving or sending) specified signals (e.g., sensing signals, non-sensing signals (e.g., communication signals, control signals, etc.)). Resource allocation unit 650 may also be configured to send signal transmission configurations applicable to multiple UEs to any appropriate entity (e.g., UE 500), for example via a broadcast message. Resource allocation unit 650 may be configured to send resource allocations to UE 500, for example via a unicast message, such as configurations of resources allocated to UE 500 for sensing signal transmission and resources allocated for non-sensing signal transmission. 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. Resource allocation unit 650 and sensing unit 660 are further discussed below, and any functions that can be substantially referred to in processor 610 or substantially referred to in network entity 600 for performing the functions of resource allocation unit 650 and / or sensing unit 660 are described, wherein network entity 600 is configured to perform these functions.

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

[0083] Also refer to Figure 9 and Figure 10 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. Figure 9 and Figure 10 Two examples of a multi-station sensing system based on a dual-station architecture are shown. For example, multi-station sensing system 900 includes a transmitting node 910, a target object 920, and receiving nodes 931, 932, and 933. Transmitting node 910 can transmit an FL signal 912, the target object 920 can backscatter BL signals 921, 922, and 923 based on the FL signal 912, and receiving nodes 931-933 can receive and measure BL signals 921-923 respectively. BL signals 921-923 can be the same signals transmitted in different directions as shown in the figure. As another example, multi-station sensing system 1000 includes transmitting nodes 1010 and 1040, a target object 1020, and receiving nodes 1030 and 1050. Transmitting nodes 1010 and 1040 can transmit FL signals 1012 and 1042 respectively, and the target object 1020 can transmit BL signals 1022 and 1024. BL signal 1022 may be based solely on FL signal 1012, or solely on FL signal 1042, or may be multiple signals, with one signal based on FL signal 1012 and another signal based on FL signal 1042. Similarly, BL signal 1024 may be based solely on FL signal 1012, or solely on FL signal 1042, or may be multiple signals, with one signal based on FL signal 1012 and another signal based on FL signal 1042.

[0084] Various factors can be considered to determine the sensing signal configuration. For example, sensing signal transmission typically has strict requirements in terms of transmission timeline, with little room for deviation from a regular / periodic pattern. Deviations from a regular / periodic pattern are possible, but this increases complexity and therefore processing costs (fees, processing capacity, processing time). When a UE performs monostation sensing transmission on communication resources, transmission can be constrained to occur on a subset of time slots, e.g., as specified / indicated by a TDD (Time Domain Duplex) configuration. For multiple sensing UEs, each with different sensing requirements / timelines, it can be challenging to include all sensing transmissions within the system's allowed sensing time slots. Therefore, punching in sensing transmissions can occur, leading to potentially severe degradation in sensing performance. As discussed herein, additional information from one or more UEs can be provided to network entity 600, enabling network entity 600 to make informed scheduling decisions (e.g., to attempt to mitigate the impact of punched sensing transmissions on a given TDD configuration). As discussed herein, the UE may override the non-sensing signal restrictions imposed by the TDD configuration, and thus transmit sensing signals during the periods indicated by the TDD configuration that will not be used for sensing signal transmission (e.g., will be used for non-sensing signal transmission).

[0085] refer to Figure 16 Communication signal resources can be allocated according to TDD configuration. For example, resources for downlink (DL), uplink (UL), and sidelink (SL) communication can be identified according to TDD configuration. For example, TDD configuration 1600 includes DL time slot 1610, UL time slot 1620, and flexible time slot 1630. A time slot includes a set of symbols (spanning the corresponding time) and a set of subcarriers (spanning the frequency range), which can be dedicated to UL, DL, or SL. TDD configuration identifies which time slots (in frames, e.g., OFDM (Orthogonal Frequency Division Multiplexing) frames) will be used for DL, UL, and SL purposes. A time slot can be dedicated to one purpose, or it can have a subset of symbols for one purpose and another non-overlapping subset of symbols for another purpose. TDD can identify flexible (F) time slots and / or symbols. The UE may not make assumptions about the purpose of the flexible (F) time slots and / or symbols, but network entities may indicate the purpose of the time slots or symbols. TDD Configuration 1600 can be provided to the UE in a semi-static manner (e.g., using RRC signaling), which can be optionally supplemented by dynamic reconfiguration (e.g., using DCI (Downlink Control Information) signaling) that is effective for a short duration.

[0086] refer to Figure 17The sensing signal configuration 1700 for sensing operations includes sensing cycles 1710 and 1720. Each of the sensing cycles 1710 and 1720 has n sensing signal transmissions 17301-1730 corresponding to n sensing beams transmitted by the UE. n Each of the n sensing beam transmissions is a signal transmission using a different beam direction, for example, using beam steering or beamforming to generate an antenna beam with a different direction relative to the antenna generating the beam. For each sensing transmission, there may be transmissions in multiple sensing symbols 1740, here in each of the two sensing time slots 1751, 1752, with a total of seven symbols per beam. In this example, there is a consistent gap of three symbols between each sensing transmission (sensing symbol). Additionally, as in this example, during sensing signal transmissions 17301-1730... n A consistent gap 1760 may exist between them, such that the sensing signal configuration 1700 indicates that the sensing signal is sent from 17301 to 1730. n The periodic pattern.

[0087] Sensing operations are typically associated with a set of requirements. For example, a maximum detection distance (the furthest distance a target object can maintain from the UE while still being detectable) and distance resolution (the closest distance two targets can maintain while still being distinguishable from each other) can be specified. As another example, a maximum detection angle (the field of view (FoV) at which the target object should be detected) and angular resolution (how close two targets can be in angular localization while still being distinguishable from each other) can be specified. As yet another example, a maximum detection velocity (the maximum relative velocity of targets that can be reliably identified) and velocity resolution (how close two targets can be in velocity while still being distinguishable from each other) can be specified. As yet another example, a sensing update rate (the frequency at which the target senses the environment) can be specified. For example, for automotive applications, the update rate is typically once every 100 ms (or less), and there is a trend towards increasing the update rate, for example, to reduce gaps between environmental sensing. To achieve detection up to the desired distance, sensing transmissions typically include multiple "chirps" to achieve sufficient processing (e.g., integration) gain to offset path loss from objects at the maximum distance. The chirped waveform can be OFDM (NR) symbols. For typical field of view and angular resolution (each depending on the sensing application), each sensing cycle includes an angular scan of a sensing beamset with a sufficiently narrow radiation pattern (beamwidth) that spans the FoV when combined. Using simulated beamforming, signals can be sequentially transmitted from the beams and sensed for any target object present within the corresponding beam direction. Velocity information from the target object (which may be referred to as the target) can be extracted via Doppler estimation. For efficient FFT-based implementations, the gap between continuously sensing OFDM symbols should remain constant (i.e., there should be a regular interval between sensing symbols). The size of the gap between sensing symbols can affect velocity resolution, and non-uniform (variable) gap sizes can be used, but this can increase computational complexity. The gap can be zero, allowing symbols to be transmitted continuously (back-to-back). One or more resources (but the description herein may refer to "resources") can be allocated for sensing to achieve one or more sensing performance criteria, such as maximum range, range resolution, maximum velocity, velocity resolution, etc. The symbols in the gaps between sensing transmissions can be used for other purposes (e.g., communication, data reception, data transmission, etc.) or may not be used (e.g., empty symbols).

[0088] Various observations regarding sensing operations can be made. A constant-gap configuration for sensing signal transmissions may exist, such as varying symbols for each beam, beam transmission for each sensing period, and / or a pattern for the sensing period. For each sensing beam, the transmission pattern may have stringent requirements, such as transmitting a sufficient number of symbols to achieve the integral gain, thereby achieving the desired performance, and maintaining the gap between consecutive sensing symbols used for Doppler estimation. Sensing periods may not occur strictly periodically, but using periodic periods can reduce complexity and improve performance. There may be little variation between sensing transmissions to transmit many beams in short sensing periods. Sensing can effectively be another type of transmission besides UL, DL, and SL transmissions, and therefore network entities can identify time slots where sensing is permitted to help achieve the desired sensing performance. To limit interference, sensing transmissions can be restricted to a subset of time slots (e.g., within a frame) as specified / indicated by the TDD configuration. For example, sensing transmissions may be restricted to UL time slots (e.g., if a network entity schedules sensing transmissions) or SL time slots (e.g., if an entity other than the network entity schedules sensing transmissions). As another example, the TDD configuration can specify a dedicated time slot for sensing, in which (theoretically) only sensing transmission can be performed.

[0089] Performing sensing in environments with multiple UEs presents challenges. In scenarios involving multiple UEs performing sensing, each UE has its own sensing requirements (which can specify different sensing transmission timelines for each UE), and ensuring that all sensing transmissions are fully contained within a subset of the allowed sensing time slots can be difficult or even impossible. If the corresponding signaling overhead is acceptable, highly flexible semi-static TDD configurations and dynamic indications for each UE can be used. If sensing transmissions are limited to SL time slots, dynamic TDD configurations may not be supported or even feasible.

[0090] This document discusses techniques for responding to UE operations scheduled to perform sensing transmissions, where the UE expects or even requires more resources than allocated for sensing by network entities, for example, more resources than those consistent with the TDD configuration. For example, based on one or more conditions, the UE may be able to override the allocation of non-sensing resources allocated according to the TDD configuration to perform sensing transmissions not allocated to the UE. As discussed herein, the UE may provide information to the network, which can use this information to make scheduling decisions for sensing transmissions performed by one or more UEs. For example, the UE may be prohibited from sending all requested sensing signals, resulting in one or more sensing transmission gaps, referred to as puncturing, without performing the requested sensing transmissions. During the puncturing duration (e.g., time slot), another function (e.g., DL communication) may be performed or not. The UE may inform the network of its tolerance for reduced sensing transmissions (relative to the requested sensing transmission level), and the network may use this tolerance to allocate resources to the UE according to the TDD configuration for sensing and / or other purposes.

[0091] refer to Figure 11 And further reference Figures 1 to 9 as well as Figure 17 The processing and signaling flow 1100 for scheduling and transmitting sensing signals includes the stages shown. Flow 1100 is an example of interaction between UE 1101, UE 1102, target object 1103, and network entity 1105. UE 1101 and UE 1102 may each be examples 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, sub-stages 1132, 1142, 1144, and / or 1146 may be omitted, but at least one of sub-stages 1132, 1142, and 1144 should be performed. Additionally, the discussion of flow 1100 focuses on punching in sensing signal transmission and covering non-sensing signal transmission with sensing signal transmission, but this discussion may also be applied additionally or alternatively to sensing signal reception. When UE 1101 and UE 1102 initially connect to network entity 1105, network entity 1105 may send TDD configuration to UE 1101 and UE 1102. The TDD configuration is static, and network entity 1105 may send the TDD configuration (e.g., TDD configuration 1600) to UE 1101 and UE 1102 in TDD configuration message 1111 (e.g., in a broadcast transmission).

[0092] At stage 1110, UE 1101 may request sensing resources and may indicate tolerance for puncturing the requested sensing resources. For example, UE 1101 may send a request 1112 for sensing resources used for sensing signal transmission. Request 1112 may be an explicit request for specified resources or may be an implicit request, such as the number of sensing resources or one or more sensing parameters (e.g., latency, accuracy) that may determine the requested sensing resources. UE 1101 may send a capability message 1116 to network entity 1105, which indicates tolerance for puncturing the requested sensing signal resources. Network entity 1105 (e.g., resource allocation unit 650) may transmit request 1112 to UE 1101, requesting puncturing tolerance from UE 1101. For example, message 1116 may be transmitted each time request 1114 is transmitted. As another example, message 1116 may be transmitted only once as part of establishing an initial RRC connection with network entity 1105. Message 1116 may include information that network entity 1105 can use to determine resource allocation, such as non-sensing signal resource allocation and sensing signal resource allocation. For example, message 1116 may include one or more sensing parameters, such as the granularity (type) and level (degree) of puncturing that UE 1101 can tolerate, for example, while still meeting one or more sensing performance criteria. For example, message 1116 may indicate whether UE 1101 can tolerate puncturing of one or more sensing symbols, one or more sensing beams, and / or one or more (partial or all) sensing cycles for which sensing signal resource allocation is requested. As another example, message 1116 may indicate the amount of puncturing that UE 1101 can tolerate, for example, the number or percentage of beams that can be punctured within a sensing cycle. Sensing beams may correspond to one or more time slots of a frame.

[0093] Also refer to Figure 12 The sensing signal transmission mode 1200 includes sensing cycles 1211 and 1212, and each sensing cycle has sensing signal transmission 12201-1220. n Mode 1200 may correspond to the sensing signal resources requested by UE 1101 in request 1112. Capability message 1116 may indicate, for example, that UE 1101 can tolerate puncturing a sensing signal transmission (corresponding to the corresponding sensing beam) in each sensing cycle, or even, as in this example, that UE 1101 can tolerate puncturing the same sensing signal transmission in each sensing cycle, here sensing signal transmission 12202.

[0094] UE 1101 can use message 1116 to indicate the ability to puncture the requested sensing signal allocation, for example, while maintaining desired sensing performance. Depending on what and how much of the requested resources are punctured (e.g., how many symbols, how many beams, how many instances of the same beam, etc.), puncturing the requested sensing signal resources may degrade sensing performance (relative to the entire set of requested sensing resources in use). For example, if the sensing symbols (of a beam) are punctured, the accuracy of maximum distance detection and velocity estimation may be reduced. As another example, if a beam is punctured (where the beam is effectively skipped), angle estimation may be degraded (where interpolation may be used based on the sensed beam direction). As yet another example, if the entire sensing cycle is punctured (or enough transmissions are punctured to invalidate the sensing cycle), degradation may occur when tracking highly dynamic (e.g., automotive) environments. However, UE 1101 may sacrifice some sensing performance due to puncturing. For example, UE 1101 may have an understanding of the environment around UE 1101 (e.g., based on previous measurements), and UE 1101 may determine that a reduction in sensing resolution is acceptable based on that understanding.

[0095] Message 1116 can be sent in any of a variety of ways. For example, message 1116 can be transmitted semi-statically (e.g., via RRC signaling) or dynamically (e.g., as part of UCI (Uplink Control Information) signaling or as part of SR (Schedule Request) signaling and / or associated BSR (Buffer Status Report) signaling). UE 1101 can be configured to send capability message 1116 semi-statically, or can be configured to send capability message 1116 dynamically, or can be configured to send capability message 1116 semi-statically and dynamically. If UE 1101 is configured to send message 1116 dynamically, the transmission of message 1116 can be dynamically triggered by network entity 1105 (e.g., as part of DCI (Downlink Control Information) signaling or MAC-CE (Media Access Control-Control Element) signaling). If UE1101 is configured to periodically send message 1116, the sending of message 1116 may be periodically triggered, for example, based on periodicity shared by multiple UEs or specific to UE 1101.

[0096] Message 1116 may include one or more constraints to allow puncturing (full puncturing, or puncturing at a specific granularity and / or level) of the requested sensing signal assignment. For example, message 1116 may indicate that a sensing beam can be punctured only if the sensing beam immediately preceding and immediately following the punctured sensing beam is not punctured. That is, message 1116 may indicate that a sensing beam can be punctured only if no adjacent sensing beam transmission is punctured.

[0097] At stage 1120, network entity 1105 (e.g., resource allocation unit 650) may determine resource allocation. Network entity 1105 may send resource allocation to UE 1101 in resource allocation message 1124. Network entity 1105 may use information from request 1112 and capability message 1116 to determine resource allocation, for example, to: not exceed the puncturing tolerance indicated by message 1116; comply with any constraints for puncturing indication; and help UE 1101 meet one or more quality of service criteria (e.g., sensing performance criteria), which may be included in request 1112 and / or otherwise known to network entity 1105. Network entity 1105 may know one or more configuration parameters of UE 1101, such as the number of sensing beams that UE 1105 can use, for example, such parameters may be used to determine the number of permissible puncturing based on an indication of the percentage of permissible puncturing. Resource allocation may include non-sensing signal resource allocation and sensing signal resource allocation. Non-sensing signal resource allocation may indicate non-sensing signal resources (e.g., frequency and duration) (or at least resources not used for sensing signal transmission) for transmitting and / or receiving non-sensing signals such as communication signals. Sensing signal resource allocation may indicate resources for transmitting and / or receiving sensing signals. Non-sensing signal resource allocation may puncture one or more resources corresponding to the requested resource set indicated by request 1112. For example, the requested allocation of sensing resources corresponding to configuration 1700 may be punctured by having non-sensing signal resource allocation allocate resources requested for sensing signal transmission for one or more other purposes instead. For example, configuration 1700 may be punctured by having non-sensing signal resource allocation indicate that resources are allocated for non-sensing signal transmissions 1231, 1232 instead of for sensing signal transmission 12202 of each of sensing periods 1211, 1212. In this way, “additional” non-sensing signal transmissions (e.g., communication, data transmissions) may be performed, and “additional” non-sensing signal transmissions may be performed without degrading the UE’s sensing performance beyond an acceptable level. As shown in this example, resources requested for sensing signal transmission 12202 (e.g., SL communication, UL communication, DL communication) can be allocated for either or both of the non-sensing signal transmissions 1231 and 1232. As another example, one or more of the resources requested for sensing signal transmission 12202 may not be allocated at all (empty).

[0098] Figure 12The illustrated punch resource allocation is an example, and any number of alternative resource allocations can be used / determined. For example, the same requested resources used for sensing signal transmission do not need to be punched in every (or even multiple) sensing cycles. As another example, different numbers of requested resources used for sensing signal transmission can be punched in different sensing cycles. As another example, different numbers of sensing cycles can be configured for the resource allocation (e.g., one sensing cycle, three sensing cycles, etc.). As another example, another number of punches can occur (e.g., multiple punches in a single sensing cycle). Other resource allocations may also be used.

[0099] Due to the heavy load of sensing transmissions from multiple UEs, network entity 1105 (e.g., gNB) may not dynamically allocate sensing resources at the granularity of sensing slots / symbols, sensing beams, and / or sensing periods. Network entity 1105 may, for example, provide configuration authorization (CG) for periodic sensing transmissions. The CG period can be defined on logical slots because all transmission resources used (e.g., slots) may not be periodic (e.g., slots within a group may be periodic). Figure 16 (e.g., DL slot 1610 shown), but groups of slots of the same kind (e.g., DL slots) may not be periodic. As another example, network entity 1105 (e.g., gNB) may defer the allocation of sensing signal resources to the UE, where the UE competes for sensing resources on a resource pool (similar to mode 2 in a sidelink). In either case, UE 1101 may not be able to identify sensing resources that can accommodate a request for sensing signal transmission. For this reason and / or one or more other possible reasons (e.g., to meet one or more sensing performance criteria), UE 1101 may need to override sensing signal resource allocation to perform sensing signal transmission on one or more unused resources and / or on one or more resources nominally used for another (non-sensing) purpose. For example, if the sensing transmission direction (beam) is unlikely to interfere with (e.g., align) the TRP uplink receive direction (beam), a sensing transmission permitted to be performed on the SL slot may be permitted to “leak” on the UL slot.

[0100] At stage 1130, UE 1101 may perform sensing signal transmission (e.g., one or more sensing signal transmissions), and UE 1101, UE 1102, and network entity 1105 may perform non-sensing signal transmission (e.g., one or more transmissions and / or one or more receptions). Sensing signal transmission may involve overriding the resource allocation in resource allocation message 1124 received from network entity 1105. UE 1101 may participate in non-sensing signal transmission and / or sensing signal transmission based on the resource allocation received from network entity 1105 in resource allocation message 1124. For example, UE 1101 may attempt to transmit sensing signals using only the resources allocated for sensing signal transmission, while satisfying one or more sensing signal performance criteria.

[0101] Also refer to Figure 13 UE 1101 can determine to override the resource allocation received in resource allocation message 1124 to perform one or more sensing transmissions using one or more resources not allocated for sensing signal transmission. As another example, UE 1101 can be configured (e.g., via dedicated RRC signaling to UE 1101) to override resource allocations. Figure 13 As shown, UE 1101 may, for example, determine coverage resource allocation 1300 and use non-sensing signal resources 1311, 1312 for sensing signal transmission 1321, 1322, for example, to meet one or more sensing performance criteria. For example, UE 1101 may use resources not allocated for sensing (e.g., allocated for one or more non-sensing purposes or not allocated for any purpose (e.g., empty resources)) to transmit one or more sensing signals 1134, for example, including sensing signal transmission 1321, 1322. In this way, sensing performance can be improved, for example, even if a predetermined number of sensing signal transmission opportunities do not meet such sensing signal performance criteria, the sensing performance criteria can still be met.

[0102] UE 1101 (e.g., resource allocation overriding unit 560) can be configured to overwrite (non-sensing signal) resource allocation based on satisfying one or more conditions to perform sensing signal transmission on non-sensing signal resources. These conditions can be statically and / or dynamically configured (e.g., static configuration can be changed through dynamic configuration). Network entity 1105 can provide a dynamic configuration of the conditions to be satisfied, for example, to prevent the UE from using too many resources. UE 1101 can be configured, for example, to overwrite resource allocation only if the composition of the non-sensing resources used is less than a specified percentage of all resources used for sensing transmission. The amount of resources used for sensing transmission can be a statically or dynamically specified number of resources in terms of frequency (e.g., the number of physical resource blocks (PRBs) or sub-channels) and time (e.g., the number of time slots), and can be determined by measurements near the time when sensing signal transmission is requested. As another example, UE 1101 can be configured to overwrite resource allocation only if the non-sensing resources used are less than a specified percentage of all non-sensing resources within a pre-configured resource window. For example, coverage may be allowed only if the amount of non-sensing UL resources used is less than Y% of all non-sensing UL resources within a specified time window of resource allocation. The value of Y may be pre-configured (e.g., statically configured) and may depend on the resource type (e.g., UL, DL, SL, etc.). The value of Y may be measured in a time window near the time when sensing signal transmission is requested. As another example, UE 1101 may be configured to cover resource allocation only if UE 1101 is unaware of any transmissions scheduled to be performed on any non-sensing resources intended for sensing signal transmission. For example, if sensing resources are allowed only on a subset of SL resources, and UE 1101 needs to utilize SL resources that are nominally not allowed to be sensed, UE 1101 may check whether these specific resources have been indicated (“reserved”) by one or more other UEs for future transmissions by other UEs, and not cover resource allocations for any resources that have already been reserved. As another example, UE 1101 may be configured to cover resource allocation only if sensing signal transmissions on non-sensing resources satisfy one or more constraints on maximum transmit power, maximum transmit bandwidth, and / or beam direction. Maximum power (or bandwidth) constraints can be used to transmit sensing signals at a transmission power (or bandwidth) that does not exceed the maximum transmission power (or bandwidth) of the non-sensing signal. For example, if the resource to be used is a UL resource, constraints on beam direction can, for example, help ensure that a beam different from the beam used for UL communication is used for transmitting sensing signals. As another example, UE 1101 can be configured to override resource allocation only if the number of previous sensing cycles experiencing puncturing within a pre-configured time window exceeds a threshold.A sensing period can be defined as “punctured” if the number and / or percentage of punctured sensing transmissions exceed a threshold. The number of punctured sensing periods can be determined near the time of the desired coverage of the resource allocation. As another example, UE 1101 can be configured to cover a resource allocation only if the priority of sensing signal transmissions using non-sensing resources exceeds a threshold. This helps ensure that resource allocations are covered only for important events (e.g., an impending collision of a car). Priority can be determined, for example, by the application of UE 1101 (e.g., an autonomous driving application). As another example, UE 1101 can be configured to cover a resource allocation only if the non-sensing resources used are Mode 2 SL resources and the measured CBR (Channel Busy Rate) of the resource pool corresponding to these resources is below a threshold. As another example, UE 1101 can be configured to cover a resource allocation only if the duty cycle of the sensing operation is below a first threshold or above a second threshold. The duty cycle can be defined as the number of sensing periods per unit time (e.g., a frame) or the number of sensing symbols per unit time, and the duty cycle definition can be configured statically or dynamically. Duty cycle can be a measure of the frequency at which sensing transmissions are performed. UE 1101 can be configured to override resource allocation only if two or more of the constraints above are in effect.

[0103] For further details, please refer to the following: Figure 11 At stage 1130, a sensing signal 1134 (which may include more than one sensing signal) may be transmitted by UE 1101 and reflected from target object 1103 as a reflected sensing signal 1136. UE 1101 and / or UE 1102 may receive the reflected sensing signal 1136.

[0104] At phase 1140, UE 1101 and / or UE 1102 may measure the reflection sensing signal 1136 and may report one or more corresponding measurements and / or processed measurements. At sub-phase 1142, UE 1101 may measure the reflection sensing signal 1136 and may send a measurement report 1143 to network entity 1105, which may include one or more raw measurements and / or one or more processed measurements, such as one or more object distances and / or one or more object directions and / or one or more object velocities. At sub-phase 1144, UE 1102 may measure the reflection sensing signal 1136 and may send a measurement report 1145 to network entity 1105, which may include one or more raw measurements and / or one or more processed measurements, such as one or more object distances and / or one or more object directions and / or one or more object velocities. Alternatively, at sub-stage 1146, network entity 1105 (e.g., sensing unit 660) may determine, for example, the distance and / or velocity of one or more target objects similar to those in sub-stages 1142 and / or 1144, based on information in measurement reports 1143 and / or 1145. Network entity 1105 (e.g., sensing unit 660) may transmit one or more determined distances and / or one or more determined velocities to another entity (e.g., to UE 1102 in distance / velocity report 1147 and / or to UE 1101 in distance / velocity report 1148).

[0105] refer to Figure 14 And further reference Figures 1 to 13 as well as Figure 17 Method 1400 for establishing or using resource allocation includes the phases 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 phases concurrently, and / or splitting one or more individual phases into multiple phases.

[0106] At stage 1410, method 1400 includes receiving a resource allocation at the UE, the resource allocation indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination, and each of the second resources including a second frequency-time combination. For example, at stage 1120, UE 1101 may receive a resource allocation from network entity 1105 in resource allocation message 1124. The resource allocation may include resources allocated for sensing signal transmission (e.g., Figure 12 The sensing signal shown is sent from 12201 to 1220. n Excluding the sensing signal transmission 12202, or Figure 13 The sensing signal resources 1331, 1332 shown) and the resources for non-sensing signal transmission (e.g., Figure 12 The non-sensor signal shown is sent as 1231, 1232, or Figure 13 The non-sensing signal resources 1311, 1312, 1341, and 1342 are shown. The processor 510 (possibly in conjunction with memory 530 and transceiver 520 (e.g., wireless receiver 244 and antenna 246)) may include components for allocating the receiving resources.

[0107] At stage 1420, method 1400 includes at least one of the following operations: covering resource allocation by transmitting at least one sensing signal using at least one of a plurality of first resources; and transmitting from the UE to the network entity: a request for a plurality of third resources for sensing signal transmission, each third resource including a third frequency-time combination; and a tolerance indication indicating the UE's ability to tolerate puncturing at least one of the plurality of third resources. UE 1101 may, for example, use at least one resource allocated for non-sensing signal transmission to transmit sensing signal 1134 at stage 1130, for example, using non-sensing signal resources 1311, 1312 to perform sensing signal transmission 1321, 1322. Processor 510 (possibly in conjunction with memory 530 and transceiver 520 (e.g., wireless transmitter 242 and antenna 246)) may include components for covering resource allocation. Alternatively or additionally, at stage 1110, UE 1101 may send a request 1112 for sensing resources and / or may send a capability message 1116 indicating (e.g., sensing cycle 1211 or sensing signal configuration 1700, etc.) an acceptable puncturing of the requested sensing signal resources. Capability message 1116 may include a tolerance indication, i.e., indicating (identifying and / or indicating) that UE 1101 will find acceptable puncturing. Network entity 1105 may use this information to allocate (e.g., at stage 1120) one or more non-sensing signal resources instead of requesting sensing signal resources. Processor 510 (possibly in conjunction with memory 530 and transceiver 520 (e.g., wireless transmitter 242 and antenna 246)) may include components for transmitting requests and tolerance indications for multiple third resources.

[0108] Specific implementations of method 1400 may include one or more of the following features. In one example implementation, the tolerance indicator indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c). In another example implementation, the tolerance indicator indicates the amount of puncturing of a periodic sensing signal transmission pattern that the UE can tolerate. In yet another example implementation, the tolerance indicator indicates at least one conditional constraint on the UE's tolerance for puncturing of periodic sensing signal transmission patterns. For example, the constraint could be that neither the nearest beam before the punctured beam nor the next beam after the punctured beam can be punctured.

[0109] Additionally or alternatively, implementations of method 1400 may include one or more of the following features. In one example implementation, method 1400 includes at least one of the following operations: semi-statically transmitting a tolerance indication; or dynamically transmitting a tolerance indication. For example, UE 1101 may transmit a capability message 1116 when establishing or reconfiguring an RRC connection between UE 1101 and network entity 1105, wherein the indicated tolerance remains valid until the RRC connection is reconfigured or re-established. As another example, UE 1101 may transmit the capability message 1116 aperiodically in response to a trigger (e.g., request 1114). Processor 510 (possibly in conjunction with memory 530 and transceiver 520 (e.g., radio transmitter 242, radio receiver 244, and antenna 246)) may include components for semi-statically transmitting the tolerance indication and / or components for dynamically transmitting the tolerance indication. In another example implementation, the UE is a specific UE among a plurality of UEs, and method 1400 includes transmitting at least one sensing signal using at least one of a plurality of first resources based on a first sidelink resource pool configuration applicable to the plurality of UEs or based on a second sidelink resource pool configuration particularly applicable to the specific UE. For example, UE 1101 may transmit sensing signals over a duration scheduled for non-sensing signal transmission based on UE 1101’s “global” SL resource pool or a dedicated SL resource pool.

[0110] Additionally or alternatively, implementations of method 1400 may include one or more of the following features. In one example implementation, method 1400 includes transmitting at least one sensing signal using at least one of a plurality of first resources based on: (1) a first number of the plurality of first resources used for transmitting the sensing signal is less than a first threshold amount; or (2) a second number of a subset of a particular type of signal transmission of the plurality of first resources used for transmitting the sensing signal is less than a second threshold amount; or (3) the UE is unaware of any signal transmission to be performed using at least one of the plurality of first resources; or (4) the transmission of at least one sensing signal is within a maximum transmission power corresponding to at least one of the plurality of first resources, or within a maximum transmission power corresponding to at least one of the plurality of first resources. Within the maximum bandwidth corresponding to at least one first resource, or in the acceptable beam direction corresponding to at least one of the plurality of first resources, or any combination of both or more thereof; or (5) the third number of sensing periods punched within a specified time duration exceeds a third threshold amount; or (6) the priority of at least one sensing signal exceeds a coverage threshold; or (7) at least one of the plurality of first resources corresponds to a mode 2 side link, and the channel busy rate corresponding to at least one of the plurality of first resources is less than a fourth threshold amount; or (8) the duty cycle of the sensing operation is determined to be below or above a duty cycle threshold; or (9) any combination of both or more of (1) to (8). For example, UE1101 may transmit sensing signals using one or more resources allocated for non-sensing signal transmission based on a first number of resources allocated for non-sensing signal transmission being less than a first threshold amount, and based on a second number of a subset of signal transmissions of a specific type of resource allocated for non-sensing signal transmission being less than a second threshold amount.

[0111] refer to Figure 15 And further reference Figures 1 to 13 as well as Figure 17 Resource allocation determination method 1500 includes the stages shown. However, method 1500 is merely an example and not limiting. Method 1500 may 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. Method 1500 may include at least a portion of a method for determining the distance and / or velocity of each of one or more target objects using RF sensing.

[0112] At stage 1510, method 1500 includes receiving a first indication from the UE at a network entity, the first indication indicating a request for a plurality of first resources for sensing signal transmission, each of the plurality of first resources including a first frequency-time combination. For example, at stage 1110 in request 1112, network entity 1105 may receive implicit and / or explicit requests for sensing signal transmission resources. Processor 610 (possibly in conjunction with memory 630, and in conjunction with transceiver 620 (e.g., wireless receiver 444 and antenna 446, and / or wired receiver 454, or wireless receiver 344 and antenna 346 and / or wired receiver 354)) may include components for receiving the first indication.

[0113] At stage 1520, method 1500 includes receiving a second indication at a network entity, the second indication instructing the UE to tolerate the capability to puncture at least one of a plurality of first resources. For example, at stage 1110, network entity 1105 may receive a capability message 1116 instructing UE 1101 to tolerate puncturing of requested sensing signal resources. Processor 610 (possibly in conjunction with memory 630, and in conjunction with transceiver 620 (e.g., wireless receiver 444 and antenna 446, and / or wired receiver 454, or wireless receiver 344 and antenna 346 and / or wired receiver 354)) may include components for receiving the second indication.

[0114] At stage 1530, method 1500 includes determining resource allocation at the network entity and based on a second indication, which indicates a plurality of second resources for non-sensing signal transmission and a plurality of third resources for sensing signal transmission. At least one of the plurality of second resources includes a corresponding at least one of a plurality of first resources, each of the plurality of second resources includes a second frequency-time combination, and each of the plurality of third resources includes a third frequency-time combination. For example, at stage 1120, UE 1105 (e.g., resource allocation unit 650) may determine the resource allocation (of sensing signal resources and non-sensing signal resources) based on acceptable puncturing of a requested sensing signal resource indicated in capability message 1116 (e.g., sensing period 1211, sensing period 1212, or sensing signal configuration 1700, etc.). The determined resource allocation may include sensing signal transmission resources (e.g., for sensing signal transmission 12201-1220). n Excluding sensing signal transmission 12202, where resources for non-sensing signal transmission 1231, 1232 are allocated to resources originally intended for sensing signal transmission 12202 in sensing cycles 1211, 1212. Processor 610 (possibly in conjunction with memory 630) may include components for determining resource allocation.

[0115] At stage 1540, method 1500 includes sending a resource allocation from a network entity to a UE. For example, at stage 1120, UE 1105 may send a resource allocation message 1124 to UE 1101. Processor 610 (possibly in conjunction with memory 630, or 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 sending the resource allocation.

[0116] Specific implementations of method 1500 may include one or more of the following features. In one example implementation, the second indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c). For example, network entity 1105 may schedule puncturing of one or more sensing symbols, one or more sensing beams, and / or one or more sensing periods based on capability message 1116, which indicates the tolerance of UE 1101 for one or more such puncturing types. Network entity 1105 may not schedule puncturing types not indicated by message 1116 as acceptable for UE 1101 to perform puncturing. In another example implementation, the second indication indicates the amount of puncturing of at least one of a plurality of first resources that the UE can tolerate. For example, network entity 1105 may schedule puncturing not more than the indicated amount of puncturing of the requested sensing signal resource that the UE can tolerate. In another example implementation, the second indication specifies at least one conditional constraint on the tolerance of the UE to puncture at least one of a plurality of first resources. For example, network entity 1105 may schedule only puncturing that satisfies one or more conditional constraints (if any) indicated by capability message 1116. For example, the constraint may be, and network entity 1105 may determine resource allocation such that neither the nearest beam before the punctured beam nor the next beam after the punctured beam is punctured.

[0117] Specific implementation examples

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

[0119] Clause 1. A UE (User Equipment), said UE (User Equipment) comprising: One or more memory units; One or more transceivers; and One or more processors, the one or more processors being communicatively coupled to the one or more memories and the one or more transceivers; The one or more processors are configured to receive resource allocations via the one or more transceivers, the resource allocations indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination, and each of the second resources including a second frequency-time combination; in: The one or more processors are configured to override the resource allocation to use at least one of the plurality of first resources to transmit at least one sensing signal; or The one or more processors are configured to: Requests for a plurality of third resources for transmitting sensing signals are transmitted via the one or more transceivers, each third resource including a third frequency-time combination; and A tolerance indication is transmitted via the one or more transceivers, the tolerance indication indicating the UE's ability to tolerate puncturing at least one of the plurality of third resources; or Their combination.

[0120] Clause 2. The UE as described in Clause 1, wherein the tolerance indication indicates whether the UE is configured to tolerate punching of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing cycles; or (d) any combination of two or more of (a), (b) or (c).

[0121] Clause 3. The UE as described in Clause 1, wherein the tolerance indicator indicates the amount of punching in the periodic sensing signal transmission pattern that the UE can tolerate.

[0122] Clause 4. The UE as described in Clause 1, wherein the tolerance indication indicates at least one conditional constraint on the UE's ability to tolerate punching of the periodic sensing signal transmission pattern.

[0123] Clause 5. The UE as described in Clause 1, wherein the one or more processors: Configured to transmit the tolerance indication semi-statically; or Configured to dynamically transmit the tolerance indication; or The tolerance indication is configured to be transmitted semi-statically or dynamically.

[0124] Clause 6. The UE as described in Clause 1, wherein the UE is a particular UE among a plurality of UEs, and wherein the one or more processors are configured to transmit the at least one sensing signal using at least one of the plurality of first resources based on a first sidelink resource pool configuration applicable to the plurality of UEs or based on a second sidelink resource pool configuration particularly applicable to the particular UE.

[0125] Clause 7. The UE according to Clause 1, wherein the one or more processors are configured to transmit the at least one sensing signal using at least one of the plurality of first resources based on: (1) The first quantity of the plurality of first resources used for transmitting the sensing signal is less than a first threshold quantity; or (2) The second quantity of a subset of specific types of signal transmissions of the plurality of first resources used for sensing signal transmission is less than a second threshold quantity; or (3) The UE is unaware of any signal transmission to be performed using at least one of the plurality of first resources; or (4) The at least one sensing signal is transmitted within a maximum transmission power corresponding to the at least one of the plurality of first resources, or within a maximum bandwidth corresponding to the at least one of the plurality of first resources, or in an acceptable beam direction corresponding to the at least one of the plurality of first resources, or any combination of both or more thereof; or (5) The third number of sensing cycles that are punched within the specified time period exceeds the third threshold amount; or (6) The priority of at least one sensing signal exceeds the coverage threshold; or (7) At least one of the plurality of first resources corresponds to a mode 2 side link, and the channel busy rate corresponding to at least one of the plurality of first resources is lower than a fourth threshold; or (8) The one or more processors determine that the duty cycle of the sensing operation is lower than or higher than the duty cycle threshold; or Any combination of two or more of (9)(1) to (8).

[0126] Clause 8. A method for establishing or using resource allocation, said method comprising: The resource allocation is received at the UE (User Equipment), the resource allocation indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination, and each of the second resources including a second frequency-time combination; and Perform at least one of the following: The resource allocation is covered by transmitting at least one sensing signal using at least one of the plurality of first resources; and The UE transmits to the network entity: a request for a plurality of third resources for transmitting sensing signals, each third resource including a third frequency-time combination; and a tolerance indication indicating the UE's ability to tolerate punching in at least one of the plurality of third resources.

[0127] Clause 9. The method according to Clause 8, wherein the tolerance indication indicates whether the UE is configured to tolerate punching of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing cycles; or (d) any combination of two or more of (a), (b) or (c).

[0128] Clause 10. The method according to Clause 8, wherein the tolerance indication indicates the amount of punching of the periodic sensing signal transmission pattern that the UE can tolerate.

[0129] Clause 11. The method according to Clause 8, wherein the tolerance indication indicates at least one conditional constraint on the UE's ability to tolerate punching of the periodic sensing signal transmission pattern.

[0130] Clause 12. The method described in Clause 8 further comprises at least one of the following: Semi-static transmission of the tolerance indication; and The tolerance indication is transmitted dynamically.

[0131] Clause 13. The method according to Clause 8, wherein the UE is a particular UE among a plurality of UEs, and wherein the method includes transmitting the at least one sensing signal using at least one of the plurality of first resources based on a first sidelink resource pool configuration applicable to the plurality of UEs or based on a second sidelink resource pool configuration particularly applicable to the particular UE.

[0132] Clause 14. The method according to Clause 8, wherein the method includes transmitting the at least one sensing signal using at least one of the plurality of first resources based on: (1) The first quantity of the plurality of first resources used for transmitting the sensing signal is less than a first threshold quantity; or (2) The second quantity of a subset of specific types of signal transmissions of the plurality of first resources used for sensing signal transmission is less than a second threshold quantity; or (3) The UE is unaware of any signal transmission to be performed using at least one of the plurality of first resources; or (4) The at least one sensing signal is transmitted within a maximum transmission power corresponding to the at least one of the plurality of first resources, or within a maximum bandwidth corresponding to the at least one of the plurality of first resources, or in an acceptable beam direction corresponding to the at least one of the plurality of first resources, or any combination of both or more thereof; or (5) The third number of sensing cycles that are punched within the specified time period exceeds the third threshold amount; or (6) The priority of at least one sensing signal exceeds the coverage threshold; or (7) At least one of the plurality of first resources corresponds to a mode 2 side link, and the channel busy rate corresponding to at least one of the plurality of first resources is lower than a fourth threshold; or (8) The duty cycle of the sensing operation is determined to be below or above the duty cycle threshold; or Any combination of two or more of (9)(1) to (8).

[0133] Clause 15. A UE (User Equipment), said UE (User Equipment) comprising: A component for receiving the resource allocation, the resource allocation indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination, and each of the second resources including a second frequency-time combination; and At least one of the following: A component for covering the resource allocation by transmitting at least one sensing signal using at least one of the plurality of first resources; and Components for transmitting the following to a network entity: a request for a plurality of third resources for transmitting sensing signals, each third resource including a third frequency-time combination; and a tolerance indication indicating the UE's ability to tolerate punching in at least one of the plurality of third resources.

[0134] Clause 16. The UE as described in Clause 15, wherein the tolerance indication indicates whether the UE is configured to tolerate punching of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing cycles; or (d) any combination of two or more of (a), (b) or (c).

[0135] Clause 17. The UE as described in Clause 15, wherein the tolerance indication indicates the amount of punching in the periodic sensing signal transmission pattern that the UE can tolerate.

[0136] Clause 18. The UE as described in Clause 15, wherein the tolerance indication indicates at least one conditional constraint on the UE's ability to tolerate punching of the periodic sensing signal transmission pattern.

[0137] Clause 19. The UE as described in Clause 15 further includes at least one of the following: Components for semi-static transmission of the tolerance indication; and A component used to dynamically transmit the tolerance indication.

[0138] Clause 20. The UE as described in Clause 15, wherein the UE is a particular UE among a plurality of UEs, and wherein the UE includes components for transmitting the at least one sensing signal using at least one of the plurality of first resources based on a first sidelink resource pool configuration applicable to the plurality of UEs or based on a second sidelink resource pool configuration particularly applicable to the particular UE.

[0139] Clause 21. The UE according to Clause 15, the UE further comprising components for transmitting the at least one sensing signal using at least one of the plurality of first resources based on: (1) The first quantity of the plurality of first resources used for transmitting the sensing signal is less than a first threshold quantity; or (2) The second quantity of a subset of specific types of signal transmissions of the plurality of first resources used for sensing signal transmission is less than a second threshold quantity; or (3) The UE is unaware of any signal transmission to be performed using at least one of the plurality of first resources; or (4) The at least one sensing signal is transmitted within a maximum transmission power corresponding to the at least one of the plurality of first resources, or within a maximum bandwidth corresponding to the at least one of the plurality of first resources, or in an acceptable beam direction corresponding to the at least one of the plurality of first resources, or any combination of both or more thereof; or (5) The third number of sensing cycles that are punched within the specified time period exceeds the third threshold amount; or (6) The priority of at least one sensing signal exceeds the coverage threshold; or (7) At least one of the plurality of first resources corresponds to a mode 2 side link, and the channel busy rate corresponding to at least one of the plurality of first resources is lower than a fourth threshold; or (8) The duty cycle of the sensing operation is determined to be below or above the duty cycle threshold; or Any combination of two or more of (9)(1) to (8).

[0140] Clause 22. 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: Receive resource allocation, the resource allocation indicating a plurality of first resources for non-sensory signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources including a first frequency-time combination, and each of the second resources including a second frequency-time combination; and At least one of the following: The one or more processors cause the processors to overwrite processor-readable instructions allocated by the resource allocation by sending at least one sensing signal using at least one of the plurality of first resources; and The processor or processor may transmit to a network entity a processor-readable instruction for: a request for a plurality of third resources for sensing signal transmission, each third resource including a third frequency-time combination; and a tolerance indication indicating that the UE tolerates the ability to punch holes in at least one of the plurality of third resources.

[0141] Clause 23. The non-transitory processor-readable storage medium as described in Clause 22, wherein the tolerance indication indicates whether the UE is configured to tolerate punching of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing cycles; or (d) any combination of two or more of (a), (b) or (c).

[0142] Clause 24. The non-transitory processor-readable storage medium as described in Clause 22, wherein the tolerance indication indicates the amount of punching of the periodic sensing signal transmission pattern that the UE can tolerate.

[0143] Clause 25. The non-transitory processor-readable storage medium as described in Clause 22, wherein the tolerance indication indicates at least one conditional constraint on the UE's ability to tolerate puncturing of the periodic sensing signal transmission pattern.

[0144] Clause 26. The non-transitory processor-readable storage medium as described in Clause 22, further comprising at least one of the following: Cause the one or more processors to semi-statically transmit processor-readable instructions containing the tolerance indication; and The one or more processors are enabled to dynamically transmit processor-readable instructions that indicate the tolerance.

[0145] Clause 27. The non-transitory processor-readable storage medium according to Clause 22, wherein the UE is a particular UE among a plurality of UEs, and wherein the non-transitory processor-readable storage medium includes processor-readable instructions that cause the one or more processors to transmit the at least one sensing signal using at least one of the plurality of first resources based on a first sidelink resource pool configuration applicable to the plurality of UEs or based on a second sidelink resource pool configuration particularly applicable to the particular UE.

[0146] Clause 28. The non-transitory processor-readable storage medium according to Clause 22, the non-transitory processor-readable storage medium further comprising processor-readable instructions that cause the one or more processors to transmit the at least one sensing signal using at least one of the plurality of first resources based on: (1) The first quantity of the plurality of first resources used for transmitting the sensing signal is less than a first threshold quantity; or (2) The second quantity of a subset of specific types of signal transmissions of the plurality of first resources used for sensing signal transmission is less than a second threshold quantity; or (3) The UE is unaware of any signal transmission to be performed using at least one of the plurality of first resources; or (4) The at least one sensing signal is transmitted within a maximum transmission power corresponding to the at least one of the plurality of first resources, or within a maximum bandwidth corresponding to the at least one of the plurality of first resources, or in an acceptable beam direction corresponding to the at least one of the plurality of first resources, or any combination of both or more thereof; or (5) The third number of sensing cycles that are punched within the specified time period exceeds the third threshold amount; or (6) The priority of at least one sensing signal exceeds the coverage threshold; or (7) At least one of the plurality of first resources corresponds to a mode 2 side link, and the channel busy rate corresponding to at least one of the plurality of first resources is lower than a fourth threshold; or (8) The duty cycle of the sensing operation is determined to be below or above the duty cycle threshold; or Any combination of two or more of (9)(1) to (8).

[0147] Clause 29. A network entity, said network entity comprising: One or more memory units; One or more transceivers; and One or more processors, which are communicatively coupled to the one or more memories and the one or more transceivers and are configured to: A first indication is received from the UE (User Equipment) via the one or more transceivers, the first indication indicating a request for a plurality of first resources for transmitting sensing signals, each of the plurality of first resources including a first frequency-time combination; The UE receives a second indication via the one or more transceivers, the second indication indicating that the UE tolerates the ability to punch at least one of the plurality of first resources; Based on the second indication, a resource allocation for the UE is determined, the resource allocation indicating a plurality of second resources for non-sensory signal transmission and a plurality of third resources for sensing signal transmission, at least one of the plurality of second resources comprising a corresponding at least one of the plurality of first resources, each of the plurality of second resources comprising a second frequency-time combination, and each of the plurality of third resources comprising a third frequency-time combination; and The resource allocation is sent to the UE via the one or more transceivers.

[0148] Clause 30. A network entity pursuant to Clause 29, wherein the second indication indicates whether the UE is configured to tolerate punching of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing cycles; or (d) any combination of two or more of (a), (b) or (c).

[0149] Clause 31. The network entity as described in Clause 29, wherein the second indication indicates the amount of puncturing of at least one of the plurality of first resources that the UE can tolerate.

[0150] Clause 32. The network entity as described in Clause 29, wherein the second indication indicates at least one conditional constraint on the UE's ability to tolerate puncturing at least one of the plurality of first resources.

[0151] Clause 33. A method for determining resource allocation, the method comprising: At the network entity, a first indication is received from the UE (User Equipment), the first indication indicating a request for a plurality of first resources for transmitting sensing signals, each of the plurality of first resources including a first frequency-time combination; A second instruction is received at the network entity, the second instruction indicating that the UE tolerates the ability to punch a hole in at least one of the plurality of first resources; At the network entity and based on the second indication, a resource allocation for the UE is determined, the resource allocation indicating a plurality of first and second resources for non-sensory signal transmission and a plurality of third resources for sensing signal transmission, at least one of the plurality of second resources comprising a corresponding at least one of the plurality of first resources, each of the plurality of second resources comprising a second frequency-time combination, and each of the plurality of third resources comprising a third frequency-time combination; and The resource allocation is sent from the network entity to the UE.

[0152] Clause 34. The signal transmission scheduling method according to Clause 33, wherein the second indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing cycles; or (d) any combination of two or more of (a), (b) or (c).

[0153] Clause 35. The signal transmission scheduling method according to Clause 33, wherein the second indication indicates the amount of puncturing of at least one of the plurality of first resources that the UE can tolerate.

[0154] Clause 36. The signal transmission scheduling method according to Clause 33, wherein the second indication indicates at least one conditional constraint on the UE's ability to tolerate puncturing of at least one of the plurality of first resources.

[0155] Clause 37. A network entity, said network entity comprising: A component for receiving a first indication from a UE (User Equipment), the first indication indicating a request for a plurality of first resources for transmitting sensing signals, each of the plurality of first resources including a first frequency-time combination; A component for receiving a second instruction, the second instruction indicating that the UE tolerates the ability to punch through at least one of the plurality of first resources; A component for determining resource allocation for the UE based on the second indication, the resource allocation indicating a plurality of first and second resources for non-sensory signal transmission and a plurality of third resources for sensing signal transmission, at least one of the plurality of second resources comprising a corresponding at least one of the plurality of first resources, each of the plurality of second resources comprising a second frequency-time combination, and each of the plurality of third resources comprising a third frequency-time combination; and A component used to send the resource allocation to the UE.

[0156] Clause 38. A network entity pursuant to Clause 37, wherein the second indication indicates whether the UE is configured to tolerate punching of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing cycles; or (d) any combination of two or more of (a), (b) or (c).

[0157] Clause 39. The network entity as described in Clause 37, wherein the second indication indicates the amount of puncturing of at least one of the plurality of first resources that the UE can tolerate.

[0158] Clause 40. A network entity pursuant to Clause 37, wherein the second indication indicates at least one conditional constraint on the UE's ability to tolerate puncturing of at least one of the plurality of first resources.

[0159] Clause 41. 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: Receive a first indication from the UE (User Equipment), the first indication indicating a request for a plurality of first resources for transmitting sensing signals, each of the plurality of first resources including a first frequency-time combination; Receive a second instruction, the second instruction indicating that the UE tolerates the ability to punch a hole in at least one of the plurality of first resources; Based on the second indication, a resource allocation for the UE is determined, the resource allocation indicating a plurality of first and second resources for non-sensory signal transmission and a plurality of third resources for sensing signal transmission, at least one of the plurality of second resources comprising a corresponding at least one of the plurality of first resources, each of the plurality of second resources comprising a second frequency-time combination, and each of the plurality of third resources comprising a third frequency-time combination; and The resource allocation is sent to the UE.

[0160] Clause 42. The non-transitory processor-readable storage medium pursuant to Clause 41, wherein the second indication indicates whether the UE is configured to tolerate punching of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing cycles; or (d) any combination of two or more of (a), (b) or (c).

[0161] Clause 43. The non-transitory processor-readable storage medium as described in Clause 41, wherein the second indication indicates the amount of perforation of at least one of the plurality of first resources that the UE can tolerate.

[0162] Clause 44. The non-transitory processor-readable storage medium as described in Clause 41, wherein the second indication indicates at least one conditional constraint on the UE's ability to tolerate puncturing at least one of the plurality of first resources.

[0163] Other considerations

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

[0165] As used herein, the singular forms “a,” “an,” and “the” also include the plural forms, unless the context clearly indicates otherwise. Thus, a device referred to in the singular form (e.g., “device,” “the device”), included in the claims, includes one or more of such devices (e.g., “processor” includes one or more processors, “the processor” includes one or more processors, “memory” includes one or more memories, “the memory” includes one or more memories, etc.). The phrase “one or more” refers to both embodiments having one referred object and embodiments having multiple referred objects. For example, “one or more processors” includes embodiments having one processor and embodiments having multiple processors.

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

[0167] 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).

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

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

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

[0171] 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 that the device's function be exclusively or even primarily for communication, do not require that communication using the wireless communication device be exclusively 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.

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

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

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

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

[0176] 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 (user equipment) comprising: 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; wherein the one or more processors are configured to receive, via the one or more transceivers, a resource allocation indicating a plurality of first resources for non-sensing signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources comprising a first frequency-time combination and each of the second resources comprising a second frequency-time combination; wherein: the one or more processors are configured to override the resource allocation to transmit at least one sensing signal using at least one of the plurality of first resources; or the one or more processors are configured to: transmit, via the one or more transceivers, a request for a plurality of third resources for sensing signal transmission, each third resource comprising a third frequency-time combination; and transmit, via the one or more transceivers, a tolerance indication indicating a capability of the UE to tolerate puncturing of at least one of the plurality of third resources; or a combination thereof.

2. The UE of claim 1, wherein the tolerance indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c).

3. The UE of claim 1, wherein the tolerance indication indicates an amount of puncturing of a periodic sensing signal transmission pattern that the UE is capable of tolerating.

4. The UE of claim 1, wherein the tolerance indication indicates at least one conditional constraint on the capability of the UE to tolerate puncturing of the periodic sensing signal transmission pattern.

5. The UE of claim 1, wherein the one or more processors are: configured to transmit the tolerance indication semi-statically; or configured to transmit the tolerance indication dynamically; or configured to transmit the tolerance indication semi-statically or dynamically.

6. The UE of claim 1, wherein the UE is a particular UE of a plurality of UEs, and wherein the one or more processors are configured to transmit the at least one sensing signal using at least one of the plurality of first resources based on a first sidelink resource pool configuration applicable to the plurality of UEs or based on a second sidelink resource pool configuration particular to the particular UE.

7. The UE of claim 1, wherein the one or more processors are configured to transmit the at least one sensing signal using at least one of the plurality of first resources based on: (1) a first number of the plurality of first resources for sensing signal transmission being less than a first threshold amount; or (2) a second number of a subset of the particular type of signal transmissions of the plurality of first resources used for sensing signal transmissions is less than a second threshold amount; or (3) the UE is unaware of any signal transmission that is to be performed using the at least one first resource of the plurality of first resources; or (4) the transmission of the at least one sensing signal is within a maximum transmit power corresponding to the at least one first resource of the plurality of first resources, or within a maximum bandwidth corresponding to the at least one first resource of the plurality of first resources, or in an acceptable beam direction corresponding to the at least one first resource of the plurality of first resources, or any combination of two or more of them; or (5) a third number of sensing periods that are punctured within a specified time duration exceeds a third threshold amount; or (6) a priority of the at least one sensing signal exceeds a coverage threshold; or (7) the at least one first resource of the plurality of first resources corresponds to a mode 2 sidelink, and a channel busy ratio corresponding to the at least one first resource of the plurality of first resources is below a fourth threshold amount; or (8) a duty cycle of a sensing operation determined by the one or more processors is below a duty cycle threshold or above the duty cycle threshold; or (9) any combination of two or more of (1) to (8).

8. A method for establishing or using a resource allocation, the method comprising: receiving, at a UE (user equipment), the resource allocation, the resource allocation indicating a plurality of first resources for non-sensing signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources comprising a first frequency-time combination and each of the second resources comprising a second frequency-time combination; and performing at least one of: covering the resource allocation by transmitting at least one sensing signal using at least one first resource of the plurality of first resources; and transmitting, from the UE to a network entity, a request for a plurality of third resources for sensing signal transmission, each third resource comprising a third frequency-time combination; and a tolerance indication indicating a capability of the UE to tolerate puncturing of at least one third resource of the plurality of third resources.

9. The method of claim 8, wherein the tolerance indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c).

10. The method of claim 8, wherein the tolerance indication indicates an amount of puncturing of a periodic sensing signal transmission pattern that the UE is capable of tolerating.

11. The method of claim 8, wherein the tolerance indication indicates at least one conditional constraint on the capability of the UE to tolerate puncturing of the periodic sensing signal transmission pattern.

12. The method of claim 8, further comprising at least one of: transmitting the tolerance indication semi-statically; and transmitting the tolerance indication dynamically.

13. The method of claim 8, wherein the UE is a particular UE of a plurality of UEs, and wherein the method comprises transmitting the at least one sensing signal using at least one first resource of the plurality of first resources based on a first sidelink resource pool configuration that applies to the plurality of UEs or based on a second sidelink resource pool configuration that particularly applies to the particular UE.

14. The method of claim 8, wherein the method comprises transmitting the at least one sensing signal using at least one first resource of the plurality of first resources based on: (1) a first number of the plurality of first resources for sensing signal transmission being less than a first threshold amount; or (2) a second number of a subset of the particular type of signal transmissions of the plurality of first resources used for sensing signal transmissions is less than a second threshold amount; or (3) the UE being unaware of any signal transmission to be performed using the at least one first resource of the plurality of first resources; or (4) the transmission of the at least one sensing signal being within a maximum transmission power corresponding to the at least one first resource of the plurality of first resources, or within a maximum bandwidth corresponding to the at least one first resource of the plurality of first resources, or in an acceptable beam direction corresponding to the at least one first resource of the plurality of first resources, or any combination of two or more of them; or (5) a third number of sensing periods punctured within a specified time duration exceeding a third threshold amount; or (6) a priority of the at least one sensing signal exceeding a coverage threshold; or (7) the at least one first resource of the plurality of first resources corresponding to a mode 2 sidelink, and a channel busy ratio corresponding to the at least one first resource of the plurality of first resources being below a fourth threshold amount; or (8) a duty cycle of sensing operations being determined to be below a duty cycle threshold or above the duty cycle threshold; or (9) any combination of two or more of (1) through (8).

15. A UE (user equipment), the UE (user equipment) comprising: means for receiving a resource allocation, the resource allocation indicating a plurality of first resources for non-sensing signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources comprising a first frequency-time combination and each of the second resources comprising a second frequency-time combination; and at least one of: means for covering the resource allocation by transmitting at least one sensing signal using at least one first resource of the plurality of first resources; and means for transmitting, to a network entity, a request for a plurality of third resources for sensing signal transmission, each third resource comprising a third frequency-time combination; and a margin indication indicating a capability of the UE to tolerate puncturing of at least one third resource of the plurality of third resources.

16. The UE of claim 15, wherein the tolerance indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c).

17. The UE of claim 15, wherein the tolerance indication indicates an amount of puncturing of a periodic sensing signal transmission pattern that the UE can tolerate.

18. The UE of claim 15, wherein the tolerance indication indicates at least one conditional constraint on the UE’s ability to tolerate puncturing of the periodic sensing signal transmission pattern.

19. The UE of claim 15, the UE further comprising at least one of: means for semi-statically transmitting the tolerance indication; and means for dynamically transmitting the tolerance indication.

20. The UE of claim 15, wherein the UE is a particular UE of a plurality of UEs, and wherein the UE comprises means for transmitting the at least one sensing signal using at least one first resource of the plurality of first resources based on a first sidelink resource pool configuration that applies to the plurality of UEs or based on a second sidelink resource pool configuration that particularly applies to the particular UE.

21. The UE of claim 15, the UE further comprising means for transmitting the at least one sensing signal using at least one first resource of the plurality of first resources based on: (1) a first number of the plurality of first resources for sensing signal transmission being less than a first threshold amount; or (2) a second number of a subset of the particular type of signal transmissions of the plurality of first resources used for sensing signal transmissions is less than a second threshold amount; or (3) the UE being unaware of any signal transmission to be performed using the at least one first resource of the plurality of first resources; or (4) a transmission of the at least one sensing signal being within a maximum transmission power corresponding to the at least one first resource of the plurality of first resources, or within a maximum bandwidth corresponding to the at least one first resource of the plurality of first resources, or within an acceptable beam direction corresponding to the at least one first resource of the plurality of first resources, or any combination of two or more of them; or (5) a third number of sensing periods punctured within a specified time duration exceeding a third threshold amount; or (6) a priority of the at least one sensing signal exceeding a coverage threshold; or (7) the at least one first resource of the plurality of first resources corresponding to a mode 2 sidelink, and a channel busy ratio corresponding to the at least one first resource of the plurality of first resources being below a fourth threshold amount; or (8) a duty cycle of a sensing operation being determined to be below a duty cycle threshold or above the duty cycle threshold; or (9) any combination of two or more of (1) through (8).

22. A non-transitory processor-readable storage medium comprising processor-readable instructions to cause one or more processors of a UE (user equipment) to: receiving a resource allocation, the resource allocation indicating a plurality of first resources for non-sensing signal transmission and a plurality of second resources for sensing signal transmission, each of the first resources comprising a first frequency-time combination and each of the second resources comprising a second frequency-time combination; and at least one of the following: processor-readable instructions that cause the one or more processors to transmit, using at least one of the plurality of first resources, at least one sensing signal to cover the resource allocation; and processor-readable instructions that cause the one or more processors to transmit, to a network entity, a request for a plurality of third resources for sensing signal transmission, each third resource comprising a third frequency-time combination, and a tolerance indication indicating a capability of the UE to tolerate puncturing of at least one of the plurality of third resources.

23. The non-transitory processor-readable storage medium of claim 22, wherein the tolerance indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c).

24. The non-transitory processor-readable storage medium of claim 22, wherein the tolerance indication indicates an amount of puncturing of a periodic sensing signal transmission pattern that the UE is capable of tolerating.

25. The non-transitory processor-readable storage medium of claim 22, wherein the tolerance indication indicates at least one conditional constraint on the capability of the UE to tolerate puncturing of the periodic sensing signal transmission pattern.

26. The non-transitory processor-readable storage medium of claim 22, further comprising at least one of the following: processor-readable instructions that cause the one or more processors to semi-statically transmit the tolerance indication; and processor-readable instructions that cause the one or more processors to dynamically transmit the tolerance indication.

27. The non-transitory processor-readable storage medium of claim 22, wherein the UE is a particular UE of a plurality of UEs, and wherein the non-transitory processor-readable storage medium comprises processor-readable instructions that cause the one or more processors to transmit the at least one sensing signal using at least one of the plurality of first resources based on a first sidelink resource pool configuration that applies to the plurality of UEs or based on a second sidelink resource pool configuration that particularly applies to the particular UE.

28. The non-transitory processor-readable storage medium of claim 22, further comprising processor-readable instructions that cause the one or more processors to transmit the at least one sensing signal using at least one of the plurality of first resources based on at least one of the following: (1) a first quantity of the plurality of first resources for sensing signal transmission is less than a first threshold quantity; or (2) a second number of a subset of the particular type of signal transmissions of the plurality of first resources used for sensing signal transmissions is less than a second threshold amount; or (3) the UE is unaware of any signal transmission to be performed using the at least one of the plurality of first resources; or (4) the transmission of the at least one sensing signal is within a maximum transmit power corresponding to the at least one first resource of the plurality of first resources, or within a maximum bandwidth corresponding to the at least one first resource of the plurality of first resources, or in an acceptable beam direction corresponding to the at least one first resource of the plurality of first resources, or any combination of two or more of them; or (5) a third number of sensing periods punctured within a specified time duration exceeds a third threshold amount; or (6) a priority of the at least one sensing signal exceeds a coverage threshold; or (7) the at least one first resource of the plurality of first resources corresponds to a mode 2 sidelink, and a channel busy ratio corresponding to the at least one first resource of the plurality of first resources is below a fourth threshold amount; or (8) a duty cycle of sensing operations is determined to be below a duty cycle threshold or above the duty cycle threshold; or (9) any combination of two or more of (1) to (8).

29. A network entity, the network entity comprising: 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 and configured to: receive, from a UE (user equipment) via the one or more transceivers, a first indication indicating a request for a plurality of first resources for sensing signal transmission, each first resource of the plurality of first resources comprising a first frequency-time combination; receive, from the UE via the one or more transceivers, a second indication indicating a capability of the UE to tolerate puncturing of at least one first resource of the plurality of first resources; determine, based on the second indication, a resource allocation for the UE, the resource allocation indicating a plurality of second resources for non-sensing signal transmission, and indicating a plurality of third resources for sensing signal transmission, at least one second resource of the plurality of second resources comprising a corresponding at least one first resource of the plurality of first resources, each second resource of the plurality of second resources comprising a second frequency-time combination, and each third resource of the plurality of third resources comprising a third frequency-time combination; and transmit, to the UE via the one or more transceivers, the resource allocation.

30. The network entity of claim 29, wherein the second indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c).

31. The network entity of claim 29, wherein the second indication indicates an amount of puncturing of the at least one first resource of the plurality of first resources that the UE is capable of tolerating.

32. The network entity of claim 29, wherein the second indication indicates at least one conditional constraint on the capability of the UE to tolerate puncturing of the at least one of the first plurality of resources.

33. A resource allocation determination method, the resource allocation determination method comprising: receiving, at a network entity from a UE (user equipment), a first indication, the first indication indicating a request for a first plurality of resources for sensing signal transmission, each of the first plurality of resources comprising a first frequency-time combination; receiving, at the network entity, a second indication, the second indication indicating a capability of the UE to tolerate puncturing of at least one of the first plurality of resources; determining, at the network entity and based on the second indication, a resource allocation for the UE, the resource allocation indicating a second plurality of resources for non-sensing signal transmission, and indicating a third plurality of resources for sensing signal transmission, at least one of the second plurality of resources comprising a corresponding at least one of the first plurality of resources, each of the second plurality of resources comprising a second frequency-time combination, and each of the third plurality of resources comprising a third frequency-time combination; and transmitting, from the network entity to the UE, the resource allocation.

34. The signal transmission scheduling method of claim 33, wherein the second indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c).

35. The signal transmission scheduling method of claim 33, wherein the second indication indicates an amount of puncturing of the at least one of the first plurality of resources that the UE is capable of tolerating.

36. The signal transmission scheduling method of claim 33, wherein the second indication indicates at least one conditional constraint on the capability of the UE to tolerate puncturing of the at least one of the first plurality of resources.

37. A network entity, the network entity comprising: means for receiving, from a UE (user equipment), a first indication, the first indication indicating a request for a first plurality of resources for sensing signal transmission, each of the first plurality of resources comprising a first frequency-time combination; means for receiving a second indication, the second indication indicating a capability of the UE to tolerate puncturing of at least one of the first plurality of resources; means for determining, based on the second indication, a resource allocation for the UE, the resource allocation indicating a plurality of second resources for non-sensing signal transmissions, and indicating a plurality of third resources for sensing signal transmissions, at least one second resource of the plurality of second resources comprising a corresponding at least one first resource of the plurality of first resources, each second resource of the plurality of second resources comprising a second frequency-time combination, and each third resource of the plurality of third resources comprising a third frequency-time combination; and means for transmitting, to the UE, the resource allocation.

38. The network entity of claim 37, wherein the second indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c).

39. The network entity of claim 37, wherein the second indication indicates an amount of puncturing of the at least one first resource of the plurality of first resources that the UE can tolerate.

40. The network entity of claim 37, wherein the second indication indicates at least one conditional constraint on the capability of the UE to tolerate puncturing of the at least one first resource of the plurality of first resources.

41. A non-transitory processor-readable storage medium comprising processor-readable instructions to cause one or more processors of a network entity to: receive, from a UE (user equipment), a first indication indicating a request for a plurality of first resources for sensing signal transmissions, each first resource of the plurality of first resources comprising a first frequency-time combination; receive a second indication indicating a capability of the UE to tolerate puncturing of at least one first resource of the plurality of first resources; determine, based on the second indication, a resource allocation for the UE, the resource allocation indicating a plurality of second resources for non-sensing signal transmissions, and indicating a plurality of third resources for sensing signal transmissions, at least one second resource of the plurality of second resources comprising a corresponding at least one first resource of the plurality of first resources, each second resource of the plurality of second resources comprising a second frequency-time combination, and each third resource of the plurality of third resources comprising a third frequency-time combination; and transmit, to the UE, the resource allocation.

42. The non-transitory processor-readable storage medium of claim 41, wherein the second indication indicates whether the UE is configured to tolerate puncturing of: (a) one or more sensing symbols; or (b) one or more sensing beams; or (c) one or more sensing periods; or (d) any combination of two or more of (a), (b), or (c).

43. The non-transitory processor-readable storage medium of claim 41, wherein the second indication indicates an amount of puncturing of the at least one of the first plurality of resources that the UE can tolerate.

44. The non-transitory processor-readable storage medium of claim 41, wherein the second indication indicates at least one conditional constraint on the capability of the UE to tolerate puncturing of the at least one of the first plurality of resources.

Images