Signaling and resource allocation for radar sensing using uplink resources

Abstract

Methods, systems, and devices are described for wireless communication. In some examples, a user equipment (UE) can transmit a sensing scheduling request (S-SR) message that requests resources for radar sensing (e.g., as opposed to a SR for wireless communication). In some examples, the UE can transmit a sensing buffer status report (S-BSR) that indicates parameters for one or more objects for radar tracking. The network can grant sensing resources for object tracking, and the UE can transmit a radar sensing waveform via the granted resources. In some examples, the UE can transmit radar sensing parameters via RRC signaling and can receive a configured grant (CG) for radar sensing. In some examples, the UE can receive various RRC configured radar sensing schemes and can activate one of the schemes for radar sensing via a control message.

Description

Cross-references

[0001] This patent application claims the benefit of Greek Patent Application No. 20230100920, filed on November 6, 2023, entitled “SIGNALING ANDRESOURCE ALLOCATION FOR RADAR SENSING USING UPLINK RESOURCES”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following discussion relates to wireless communications, including signaling and resource allocation for radar sensing using uplink resources. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses for signaling and resource allocation for radar sensing using uplink resources. In some examples, a user equipment (UE) may send a Sensing Scheduling Request (S-SR) message requesting resources for radar sensing (e.g., the opposite of an SR for wireless communication). The S-SR may indicate one or more parameters (e.g., key performance indicator (KPI) parameters) and the number of resources (time resources, frequency resources, spatial resources) for a radar scan. Scan resources may be granted, enabling a static scan phase with periodic transmission. In some examples, the UE may send a Sensing BSR (S-BSR) via the Physical Uplink Shared Channel (PUSCH), indicating parameters for one or more objects for radar tracking. The network may then grant sensing resources for object tracking, and the UE may transmit radar sensing waveforms via the granted resources. In some examples, the UE may transmit radar sensing parameters via Radio Resource Control (RRC) signaling and may receive a Configuration Grant (CG) for radar sensing. In some examples, the UE can receive radar sensing schemes with various RRC configurations, each defining different resource sets, periodicity, bandwidth portion (BWP), etc. The UE can activate one of the configurations for radar sensing via control messages, such as Uplink Control Information (UCI) messages or Media Access Control (MAC) Control Element (CE) messages.

[0005] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving control signaling indicating a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning; transmitting the sensing scheduling request message via the first resource, the sensing scheduling request message requesting a resource for transmitting the radar sensing waveform for radar scanning; receiving permission for one or more sensing resources for radar scanning based on transmitting the sensing scheduling request message; and transmitting the radar sensing waveform via the one or more sensing resources.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and at least one memory coupled to the at least one processor. The at least one memory stores instructions executable by the at least one processor to cause the apparatus to: receive control signaling instructing a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning; transmit the sensing scheduling request message via the first resource, the sensing scheduling request message requesting resources for transmitting the radar sensing waveform for radar scanning; receive permission for one or more sensing resources for radar scanning based on transmitting the sensing scheduling request message; and transmit the radar sensing waveform via the one or more sensing resources.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving control signaling instructing a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning; means for transmitting the sensing scheduling request message via the first resource, the sensing scheduling request message requesting the resource for transmitting the radar sensing waveform for radar scanning; means for receiving permission for one or more sensing resources for radar scanning based on transmitting the sensing scheduling request message; and means for transmitting the radar sensing waveform via the one or more sensing resources.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to: receive control signaling indicating a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning; transmit the sensing scheduling request message via the first resource, the sensing scheduling request message requesting resources for transmitting the radar sensing waveform for radar scanning; receive permission for one or more sensing resources for radar scanning based on transmitting the sensing scheduling request message; and transmit the radar sensing waveform via the one or more sensing resources.

[0009] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling instructing a first set of multiple resources for transmitting the sensing scheduling request message and a second set of multiple resources for transmitting a scheduling request message for wireless communication with a wireless device, wherein the scheduling request message may be transmitted via one or more resources in the first set of multiple resources.

[0010] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, via permission to one or more sensing resources, an indication of a time resource comb, a frequency resource comb, bandwidth, a start symbol, an end symbol, periodicity, a beam identifier, or any combination thereof, wherein the radar sensing waveform may be transmitted according to the indication.

[0011] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending indications of one or more parameters for the radar scan via the sensing scheduling request message, the one or more parameters including a threshold field of view, a threshold delay value, a threshold resolution, or any combination thereof, wherein the granting of the sensing resource may be based on the one or more parameters.

[0012] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a sense scheduling request resource message that requests a resource for transmitting the sense scheduling request message, wherein receiving control signaling indicating the first resource for transmitting the sense scheduling request message may be based on transmitting the sense scheduling request resource message.

[0013] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a communication scheduling request message that requests resources for sending an uplink message to a network entity; granting a second permission to receive one or more wireless communication resources for the uplink message based on sending the communication scheduling request message, wherein the one or more sensing resources may be different from the one or more wireless communication resources; and sending the uplink message to the network entity via the one or more wireless communication resources.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the radar sensing waveform includes a detection reference signal or a frequency-modulated continuous waveform.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the sensing scheduling request message may be sent via a physical uplink control channel.

[0016] A method for wireless communication at a UE is described. The method may include: transmitting a sense buffer state report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a specific target object among the one or more target objects; receiving, based on the sense buffer state report, permission for sensing resources that satisfy a first set of parameters in the one or more set of parameters for a first target object among the one or more target objects to be used for radar tracking of the first target object; and transmitting one or more radar sensing waveforms via the sensing resources for radar tracking of the first target object.

[0017] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and at least one memory coupled to the at least one processor. The at least one memory stores instructions executable by the at least one processor to cause the apparatus to: transmit a sense buffer state report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a specific target object among the one or more target objects; receive, based on the sense buffer state report, permission for sensing resources that satisfy a first set of parameters in the one or more set of parameters for radar tracking of a first target object among the one or more target objects; and transmit one or more radar sensing waveforms via the sensing resources for radar tracking of the first target object.

[0018] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for transmitting a sense buffer state report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a specific target object among the one or more target objects; means for receiving, based on the sense buffer state report, permission for sensing resources that satisfy a first set of parameters in the one or more set of parameters for a first target object among the one or more target objects to be used for radar tracking of the first target object; and means for transmitting one or more radar sensing waveforms via the sensing resources for radar tracking of the first target object.

[0019] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to: send a sense buffer state report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a specific target object among the one or more target objects; receive, based on the sense buffer state report, permission for sensing resources that satisfy a first set of parameters in the one or more sets of parameters for a first target object among the one or more target objects to be used for radar tracking of the first target object; and transmit one or more radar sensing waveforms via the sense resources for radar tracking of the first target object.

[0020] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting indications of time resources, frequency resources, bandwidth identifiers, periodicity, frame length, or any combination thereof via the one or more sets of parameters.

[0021] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting spatial quasi-co-location information via one or more sets of parameters, the spatial quasi-co-location information indicating a quasi-co-location relationship with a probe reference signal index or downlink beam.

[0022] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: performing a beam scanning process for radar sensing; and detecting the one or more target objects based on the beam scanning process, wherein sending the sensing buffer status report may be based on the detection.

[0023] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for launching an application associated with target tracking, wherein sending the sensing buffer status report may be based on launching the application.

[0024] Some examples of the methods, apparatuses, and nontransient computer-readable media described herein may also include operations, features, components, or instructions for: receiving control signaling instructing a semi-persistent scheduling that identifies periodic timing for transmitting the sense buffer status report; and detecting the one or more target objects during a radar scan phase prior to a first periodic timing of the semi-persistent scheduling, wherein transmitting the sense buffer status report may be based on the semi-persistent scheduling and the detection.

[0025] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a sense buffer status report resource message that requests resources for sending the sense buffer status report; and receiving control signaling indicating that the first resource for sending the sense buffer status report may be based on sending the sense buffer status report resource message.

[0026] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the sensing buffer status report may be transmitted via a physical uplink shared channel.

[0027] A method for wireless communication at a UE is described. The method may include: transmitting first control signaling indicating one or more sensing parameters for transmitting a radar sensing waveform to perform radar sensing; receiving second control signaling based on the first control signaling indicating the one or more sensing parameters, the second control signaling indicating that the UE is scheduled to transmit the radar sensing waveform via a set of multiple uplink shared channel timings; and transmitting the radar sensing waveform via one or more uplink shared channel timings from the set of multiple uplink shared channel timings according to the one or more sensing parameters.

[0028] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and at least one memory coupled to the at least one processor. The at least one memory stores instructions executable by the at least one processor to cause the apparatus to: transmit first control signaling for transmitting a radar sensing waveform for radar sensing; receive second control signaling based on the first control signaling indicating the one or more sensing parameters, the second control signaling indicating that the UE is scheduled to transmit the radar sensing waveform via a set of multiple uplink shared channel timings; and transmit the radar sensing waveform via one or more uplink shared channel timings from the set of multiple uplink shared channel timings according to the one or more sensing parameters.

[0029] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for transmitting a first control signaling indicating one or more sensing parameters for transmitting a radar sensing waveform for radar sensing; means for receiving a second control signaling based on the first control signaling indicating the one or more sensing parameters, the second control signaling indicating that the UE is scheduled to transmit the radar sensing waveform via a set of multiple uplink shared channel timings; and means for transmitting the radar sensing waveform via one or more uplink shared channel timings from the set of multiple uplink shared channel timings according to the one or more sensing parameters.

[0030] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to: transmit a first control signaling indicating one or more sensing parameters for transmitting a radar sensing waveform for radar sensing; receive a second control signaling based on the first control signaling indicating the one or more sensing parameters, the second control signaling indicating that the UE is scheduled to transmit the radar sensing waveform via a set of multiple uplink shared channel timings; and transmit the radar sensing waveform via one or more uplink shared channel timings from the set of multiple uplink shared channel timings according to the one or more sensing parameters.

[0031] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting an indication of a field of view, an indication of a delay threshold, an indication of a beamwidth, an indication of a number of resources, an indication of a threshold resolution, or any combination thereof, via the one or more sensing parameters, wherein transmitting the radar sensing waveform may be based on a radar scanning process corresponding to the one or more sensing parameters.

[0032] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting an indication of beamwidth, an indication of the number of resources, an indication of threshold range resolution, an indication of threshold velocity resolution, or any combination thereof, via the one or more sensing parameters, wherein transmitting the radar sensing waveform may be based on a radar tracking process corresponding to the one or more sensing parameters.

[0033] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the one or more sensing parameters include a first subset of parameters corresponding to a radar scanning process and a second subset of parameters corresponding to a radar tracking process.

[0034] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first control signaling includes a radio resource control message.

[0035] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the second control signaling includes a radio resource control message that includes configuration permission.

[0036] A method for wireless communication at a UE is described. The method may include: receiving a control signaling indicating a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing; sending a control message including a request to activate a first radar sensing scheme in the set of multiple radar sensing schemes; receiving an acknowledgment message corresponding to the control message; and transmitting a radar sensing waveform via a first resource corresponding to the first radar sensing scheme based on receiving the acknowledgment message.

[0037] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and at least one memory coupled to the at least one processor. The at least one memory stores instructions executable by the at least one processor to cause the apparatus to: receive control signaling indicating a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing; transmit a control message including a request to activate a first radar sensing scheme in the set of multiple radar sensing schemes; receive an acknowledgment message corresponding to the control message; and transmit a radar sensing waveform via a first resource corresponding to the first radar sensing scheme based on receiving the acknowledgment message.

[0038] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving control signaling indicating a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing; means for transmitting a control message including a request to activate a first radar sensing scheme in the set of multiple radar sensing schemes; means for receiving an acknowledgment message corresponding to the control message; and means for transmitting a radar sensing waveform via a first resource corresponding to the first radar sensing scheme based on receiving the acknowledgment message.

[0039] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by at least one processor to: receive control signaling indicating a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing; transmit a control message including a request to activate a first radar sensing scheme in the set of multiple radar sensing schemes; receive an acknowledgment message corresponding to the control message; and transmit a radar sensing waveform via a first resource corresponding to the first radar sensing scheme based on receiving the acknowledgment message.

[0040] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving indications of one or more parameters corresponding to each respective set of sensing resources used for radar sensing via the set of multiple radar sensing schemes.

[0041] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, the one or more parameters include time resource combs, frequency resource combs, bandwidth, start symbol, end symbol, periodicity, beam identifier, quasi-co-address indicator or any combination thereof.

[0042] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the control signaling includes radio resource control messages.

[0043] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the control message includes an uplink control information message.

[0044] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the control message includes a Media Access Control (MAC) control element (CE).

[0045] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of the number of cycles for activating the first radar sensing scheme via the control message.

[0046] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling indicating that the second radar sensing scheme may be the default radar sensing scheme.

[0047] In some examples of the methods, apparatuses and nontransitory computer-readable media described herein, a switch from the first radar sensing scheme to the second radar sensing scheme is made based on control signaling indicating that the second radar sensing scheme may be the default radar sensing scheme when a time period associated with the first radar sensing scheme expires, and a second radar sensing waveform is transmitted via a resource corresponding to the second radar sensing scheme based on the switch.

[0048] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving control signaling indicating that the first radar sensing scheme may be the default radar sensing scheme; determining that the UE may not have any radar sensing to perform during a second resource corresponding to the first radar sensing scheme; and sending a control message based on the control signaling indicating that the first radar sensing scheme may be the default radar sensing scheme, the control message instructing the UE not to send a second radar sensing waveform via the second resource corresponding to the first radar sensing scheme.

[0049] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a limitation of the definitions in the claims.

[0050] While aspects and implementations have been described herein by way of example, those skilled in the art will understand that additional specific implementations and use cases can arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, various implementations and / or devices can be produced via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to a use case or application, the applicability of various types of the described innovations is evident. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the implementations protected and described by the claims. For example, the transmission and reception of wireless signals necessarily involve multiple components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) for analog and digital purposes. The aim is that the innovations described herein can be implemented in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with various sizes, shapes, and constructions. Attached Figure Description

[0051] Figure 1 Examples of wireless communication systems supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, are shown.

[0052] Figure 2 Examples of wireless communication systems supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, are shown.

[0053] Figure 3 An example of a JCR system supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown.

[0054] Figure 4 Examples of radar sensing schemes supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, are shown.

[0055] Figure 5An example of a process flow for signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown.

[0056] Figure 6 An example of a process flow for signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown.

[0057] Figure 7 An example of a process flow for signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown.

[0058] Figure 8 An example of a process flow for signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown.

[0059] Figure 9 and Figure 10 A block diagram of an apparatus for signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown.

[0060] Figure 11 A block diagram is shown of a communication manager that supports signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure.

[0061] Figure 12 A diagram is shown of a system including devices for signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure.

[0062] Figures 13 to 16 A flowchart illustrating a method for signaling and resource allocation for radar sensing using uplink resources, illustrative of one or more aspects of this disclosure, is shown. Detailed Implementation

[0063] Some wireless communication systems can support Joint Communications Radar (JCR) systems, in which radar and communication systems share knowledge (e.g., cooperative JCR), or a common transmitter or receiver can be used for both wireless communication functionality and radar functionality (e.g., co-designed JCR). User equipment (UE) supporting JCR can reuse spectrum (e.g., available resources can be used for radar sensing or for wireless communication). However, some wireless communication systems and technologies may only support resource requests for wireless communication resources (e.g., via scheduling requests (SR)) and buffer status reports (BSR). Without such mechanisms defined for SR and BSR signaling for radar sensing or radar object tracking, the JCR system may fail or may not operate efficiently (e.g., if the JCR system cannot effectively or consistently access resources used for radar sensing). This lack of ability to effectively access and use radar sensing resources of the JCR system can lead to inefficient resource use, increased system latency, lack of ability to identify or track objects via radar, and reduced security (e.g., for vehicle UEs that rely on radar for object detection).

[0064] In some examples, the UE may send a Sensing SR (S-SR) message requesting resources for radar sensing (e.g., the opposite of an SR for wireless communication). The S-SR may indicate one or more parameters for a radar scan (e.g., key performance indicator (KPI) parameters) and the number of resources (time resources, frequency resources, spatial resources). Scanning resources can be granted, enabling a static scan phase with periodic transmissions.

[0065] In some examples, the UE may transmit a sensing BSR (S-BSR) via the Physical Uplink Shared Channel (PUSCH), which indicates parameters for one or more objects used for radar tracking. These parameters may include a list of target parameters (resources, QCL information, etc.). The network may then grant sensing resources for object tracking, and the UE may transmit radar sensing waveforms via the granted resources.

[0066] In some examples, the UE can send radar sensing parameters via Radio Resource Control (RRC) signaling and can receive configuration grants (CGs) for radar sensing. The UE can transmit an RRC message indicating KPI requirements for radar sensing and can receive CGs from the network based on this message.

[0067] In some examples, the UE can receive various radar sensing schemes with different RRC configurations, each defining different resource sets, periodicity, BWP, etc. The UE can activate one of the configurations for radar sensing via control messages (e.g., Uplink Control Information (UCI) messages or Media Access Control (MAC) Control Element (CE) messages). The network can send an acknowledgment (ACK) message for the activation message, and the UE can then transmit radar sensing waveforms via the activated configuration resources.

[0068] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to wireless communication systems, JCR systems, radar sensing schemes, and process flows. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to signaling and resource allocation for radar sensing using uplink resources.

[0069] Figure 1 An example of a wireless communication system 100 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0070] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, among other designations. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0071] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0072] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0073] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0074] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0075] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0076] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0077] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0078] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), where the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0079] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0080] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0081] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support signaling and resource allocation for radar sensing using uplink resources as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0082] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0083] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0084] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources that define the physical layer structure used to support communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) that communicates with another device (e.g., directly or via one or more other network entities 105).

[0085] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0086] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0087] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0088] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0089] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0090] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, which may refer to, for example, the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0091] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0092] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0093] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of the control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0094] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the extent of such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping coverage areas 110, etc.

[0095] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed or unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0096] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0097] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0098] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0099] Some UE 115s (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115s may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0100] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0101] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0102] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0103] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0104] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through user plane entities, which provide IP address allocation and other functions. User plane entities may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0105] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0106] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted for transmissions using one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

[0107] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0108] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0109] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0110] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0111] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0112] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0113] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a beam set configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback on beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0114] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weights) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0115] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for communication via logical channels. The MAC layer performs priority handling and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0116] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0117] In some examples, UE 115 may send an S-SR message requesting resources for radar sensing (e.g., the opposite of an SR for wireless communication). The S-SR may indicate one or more parameters (e.g., KPI parameters) and the number of resources (time resources, frequency resources, spatial resources) for a radar scan. Scan resources may be granted, enabling a static scan phase with periodic transmissions.

[0118] In some examples, UE 115 may transmit an S-BSR indicating parameters for one or more objects used for radar tracking via PUSCH. These parameters may include a list of target parameters (resources, QCL information, etc.). The network may then grant sensing resources for object tracking, and the UE may transmit radar sensing waveforms via the granted resources.

[0119] In some examples, UE 115 can send radar sensing parameters via RRC signaling and can receive CGs for radar sensing. UE 115 can transmit RRC messages indicating KPI requirements for radar sensing and can receive CGs from the network based on these messages.

[0120] In some examples, UE 115 can receive radar sensing schemes with various RRC configurations, each defining different resource sets, periodicity, BWP, etc. The UE can activate one of the configurations for radar sensing via control messages (e.g., UCI messages or MAC-CE messages). The network can send an ACK message for the activation message, and UE 115 can then transmit radar sensing waveforms via the resources of the activated configuration.

[0121] Figure 2An example of a wireless communication system 200 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may include one or more UEs 115 (e.g., vehicle UEs, such as UE 115-a, UE 115-b, and UE 115-c), which may be referenced... Figure 1 Examples of the corresponding devices described.

[0122] UE 115 can perform wireless communication with each other (e.g., via sidelink communication resources), can perform wireless communication with one or more network entities 105 (e.g., via a Uu link), or both. UE 115 can also perform radar signaling (e.g., for object detection, object tracking, etc., as described herein). UE 115 (e.g., a vehicle) can sense surrounding objects (e.g., perform radar sensing) for various automotive applications, such as collision avoidance. For example, UE 115-a can perform radar sensing (e.g., within the field of view 205 of a given set of radar sensors or radar sensing antennas). UE 115-a can transmit one or more radar waveforms 210 and can monitor reflected radar waveforms 210 to identify and track objects (e.g., other vehicles, pedestrians, obstacles, traffic patterns, accidents, collisions, etc., such as UE 115). For example, UE 115-a can transmit waveform 210-a and monitor the reflection of waveform 210-a. Based on this, UE 115-a can determine one or more parameters of UE 115-b (e.g., position, velocity, direction, etc.). Similarly, UE 115-a can detect the presence, velocity, direction, etc. of other objects (e.g., UE 115-c based on radar waveform 210-b).

[0123] In some examples, such as reference Figure 3 In more detail, one or more UEs in UE 115 may support a Joint Communications Radar (JCR) process. For example, UE 115-a may support cooperative JCR (e.g., where information is shared between the communication system and the radar system to improve communication and radar performance) or co-designed JCR (e.g., in this case, a common transmitter or receiver is used for both communication and radar functionality). To enable UE-side JCR sensing, uplink resources can be reused for sensing and wireless communication. Uplink resources can be shared between wireless communication mode and radar sensing mode. In some examples, different resources can be allocated to wireless communication and radar sensing respectively, as referenced. Figures 3 to 8 A more detailed description follows. In some examples, the probe reference signal can be used as the sensing waveform 210. In some examples, the same resources can be used for both wireless communication and radar sensing based on a jointly designed waveform (e.g., the same resources can be allocated or selected for either radar sensing or wireless communication).

[0124] As part of the radar sensing process, UE 115 can perform scanning, tracking, or both. In some examples (e.g., single-stage sensing), single-stage sensing transmission (e.g., radar sensing waveform 210) can be triggered on demand to meet the needs of one or more applications (e.g., sensing several target beam directions with low overhead).

[0125] In some examples (e.g., two-stage sensing), UE 115 may perform radar scanning (e.g., across all beam directions, unlike single-stage sensing) and may perform radar tracking on specific identified objects (e.g., via selected beam directions during a tracking phase based on a previous scanning phase). For example, UE 115-a may perform a first phase (e.g., a scanning phase) of two-stage sensing in many or all beam directions to detect the presence of one or more objects (e.g., UE 115-b and UE 115-c). Then, during a second phase (e.g., a tracking phase) of two-stage sensing, UE 115-a may track the identified objects (e.g., UE 115-b and UE 115-c) using specifically selected beams oriented toward the identified objects. The scanning phase (e.g., SCAN) may be used statically or semi-persistently for periodic sensing. In such examples, KPI thresholds may include (e.g., scanning may depend on) large and explicit velocity estimates, long-range radar sensing, and a wide field of view 205, at the expense of one or more parameters (e.g., resulting in low resolution). The tracking phase (e.g., TRACK) can be triggered semi-persistently or dynamically after the scanning phase (e.g., if candidate targets have been identified during the scanning phase).

[0126] In some cases, UE 115-a may send a scheduling request (SR) to dynamically request resources for uplink wireless communication, or it may send a buffer status report (BSR) for resource allocation or reallocation. However, in the absence of a mechanism for requesting resources for radar sensing (e.g., as referenced...), Figure 3 In the case of single-stage or two-stage sensing (described in more detail), UE 115-a may be unable to identify or request resources on which to perform radar sensing, resulting in radar sensing failure, inability to identify collisions or other hazards, reduced vehicle and user safety, and inefficient use of available system resources. Additionally or alternatively, UE 115-a may support a JCR scheme. However, without a mechanism to request resources for radar sensing, the JCR scheme may fail (e.g., or may only successfully utilize radio resources for wireless communication without accessing resources for radar sensing).

[0127] The technology described in this article supports JCR schemes and radar sensing. For example, see references. Figure 5In more detail, for single-stage or two-stage radar sensing, UE 115-a can send a Sensing Scheduling Request (S-SR), which requests resources for radar sensing (e.g., the scan phase for two-stage sensing). In some examples, such as reference... Figure 6 In more detail, UE 115-a can send a Sensing BSR (S-BSR) to request radar resources for the tracking phase of two-phase sensing or for single-phase sensing. In some examples, such as reference... Figure 7 In more detail, UE 115-a can send indications (e.g., via RRC signaling) to network entity 105 for one or more parameters (e.g., KPIs), and can receive control signaling (e.g., RRC signaling) indicating the timing of Physical Uplink Shared Channel (PUSCH) for sensing resources (e.g., for transmitting waveform 210) (e.g., configuration grant (CG)). In some examples, such as reference Figure 8 In more detail, UE 115-a can receive control signaling (e.g., RRC signaling) indicating various schemes (e.g., resource configuration) for radar sensing. UE 115-a can activate one of the indicated schemes via control messages (e.g., UCI messages or MAC-CE messages), and can then transmit radar sensing waveform 210 via the sensing resources of the activated scheme.

[0128] Figure 3 Examples of a JCR system 300 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, are shown. In some examples, the JCR system 300 may implement aspects of wireless communication system 100 and wireless communication system 200, and may include UE 115-d, UE 115-e, UE 115-f, and UE 115-g, which may be examples of UE 115 and may be referenced herein. Figure 1 and Figure 2 They communicate with each other as described. Although described as communication between UE 115, the technology described herein can be implemented by any type or number of devices (e.g., multiple UE 115, IoT devices, base station 105 or any combination thereof, and other examples of wireless devices).

[0129] In some cases, JCR system 305 may support cooperative radar and communication systems. Co-located and cooperative radar and communication systems can support knowledge sharing between the communication and radar systems to improve performance, for example, without changing the core operation of the radar and communication systems. For example, JCR system 305 may include UE 115-d and UE 115-e. UE 115-d may include radar transmitter / receiver 310-a and communication transmitter / receiver 315-a, and UE 115-e may include radar transmitter / receiver 310-b and communication transmitter / receiver 315-b. In some examples, radar transmitter / receiver 310-a may send signaling to radar transmitter / receiver 310-b. Communication transmitter / receiver 315-a may send signaling to communication transmitter / receiver 315-b. In some examples, radar transmitter / receiver 310-a may send signaling to communication transmitter / receiver 315-b. Communication transmitter / receiver 315-a can send signaling to radar transmitter / receiver 310-b. Additionally or alternatively, radar transmitter / receiver 310-a can share knowledge with communication transmitter / receiver 315-a of UE 115-d, and radar transmitter / receiver 310-b can share knowledge with communication transmitter / receiver 315-b of UE 115-e. JCR system 305 can support spectrum reuse and is easily implemented for various UEs 115 (e.g., UE 115-d and UE 115-e).

[0130] In some cases, the JCR system 320 may support a co-design of communication and radar systems. A co-designed communication and radar system may support a common transmitter or receiver that can be used for both communication and radar operations. In such cases, the transmit waveform generation or receiver processing of either or both systems may be modified to support both communication and radar operations. A co-designed communication and radar system may result in hardware and spectrum reuse. For example, the JCR system 320 may include UE 115-f and UE 115-g. UE 115-f may include JCR transmitter / receiver 325-a, and UE 115-g may include JCR transmitter / receiver 325-b. JCR transmitter / receiver 325-a may send signaling to JCR transmitter / receiver 325-b to support both communication and radar operations.

[0131] The technology described in this article supports JCR schemes for wireless communication and radar sensing. For example, see references... Figure 5 In more detail, for single-stage or two-stage radar sensing, UE 115 may send a Sensing Scheduling Request (S-SR), which requests resources for radar sensing (e.g., the scan phase for two-stage sensing). In some examples, such as reference... Figure 6In more detail, UE 115 can send a Sensing BSR (S-BSR) to request radar resources for the tracking phase of two-phase sensing or for single-phase sensing. In some examples, such as reference... Figure 7 In more detail, UE115 may send indications (e.g., via RRC signaling) to network entity 105 for one or more parameters (e.g., KPIs), and may receive control signaling (e.g., RRC signaling) indicating the timing of a Physical Uplink Shared Channel (PUSCH) for sensing resources (e.g., for transmitting waveform 210) (e.g., configuration grant (CG)). In some examples, such as references Figure 8 In more detail, UE 115 may receive control signaling (e.g., RRC signaling) indicating various schemes (e.g., resource configuration) for radar sensing. UE 115 may activate one of the indicated schemes via control messages (e.g., UCI messages or MAC-CE messages), and may then transmit radar sensing waveform 210 via the sensing resources of the activated scheme.

[0132] Figure 4 An example of a radar sensing scheme 400 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. The radar sensing scheme 400 may be implemented by or can be implemented by aspects of wireless communication system 100 or wireless communication system 200. For example, it may be a reference... Figures 1 to 3 The example UE (e.g., UE 115) and network entity (e.g., network entity 105) of the described corresponding device can perform radar sensing according to radar sensing scheme 400. In some examples, UEs supporting radar sensing scheme 400 can support JCR, as referenced Figure 3 As described. The UE can be, for example, a vehicle UE. Automotive scenarios may result in high-density vehicle radar with high resolution and high update rate. During radar sensing, the UE may perform beam scanning (e.g., a reference signal or radar sensing waveform, which may be referred to as a radar frame, may be transmitted via a different beam 410 during each coherent processing interval (CPI)).

[0133] In some examples, such as reference Figure 2As described, the UE can perform single-stage sensing 405. Single-stage sensing 405 (e.g., single-stage uplink sensing) transmission can result in significant communication overhead (e.g., for high-density transportation scenarios). In such examples, the UE can dynamically perform sensing via multiple narrow beams 410 to detect and track objects. For example, the UE can transmit radar waveforms via beam 410-a during CPI 1, via beam 410-b during CPI 2, via beam 410-c during CPI 3, and via beam 410-d during CPI 4. For example, for a bandwidth of 0.5 GHz and a subcarrier spacing (SCS) of 120 kHz, an example CPI (e.g., per beam) could be 5.1 ms (e.g., for...). Changes in speed at GHz ,scope The changes can be (cm). At a refresh rate of 20fps (e.g., for a sensing cycle of 50ms), each beam and each user can use more than 10 percent of the system resources.

[0134] In some examples, such as reference Figure 2 As described, the UE can perform two-stage sensing 415. Two-stage sensing 415 (e.g., two-stage uplink sensing) can include multiple stages (e.g., a scanning stage 420 and a tracking stage 425) that can achieve radar sensing with low signaling overhead. In such examples, the UE can detect the presence of one or more target objects at low resolution (e.g., using coarse beams, such as beam 410-e during CPI 5, beam 410-f in CPI 6, beam 410-g in CPI 7, beam 410-h in CPI 8, and beam 410-i in CPI 9). For example, for a bandwidth of 150 MHz and an SCS of 120 kHz, an example scanning CPI (e.g., per beam) could be 1 ms (e.g., for changes in velocity). ,scope The changes can be For an update rate of 20 fps (e.g., for a sensing period of 50 ms), each beam and each user can utilize more than 10 percent of the system resources. During tracking phase 425, the UE can track objects detected during scanning phase 420. The UE can use finer beams to track objects (e.g., fine target detection can be performed at high resolution). For example, the UE can scan through beam 410-j in CPI 10, beam 410-k in CPI 11, and beam 410-l in CPI 12. For example, for a bandwidth of 0.5 GHz, an example tracking CPI (e.g., per beam) could be 5 ms, with comb-5 decimation in time (e.g., once every fifth symbol), comb-4 decimation in frequency (e.g., once every fourth resource element), and a subcarrier spacing (SCS) of 120 kHz. At a refresh rate of 20fps, two-stage sensing 415 consumes 4.5% of system resources per user and per detected target (e.g., 9% of system resources per user assuming two targets in the field of view). Two-stage sensing can support multi-radar sensing with low overhead over shared uplink communication resources.

[0135] The technology described in this article supports JCR schemes for wireless communication and radar sensing. For example, see references... Figure 5 In more detail, for single-stage sensing 405 or two-stage sensing 415, the UE may send an S-SR requesting resources for radar sensing (e.g., for the scanning phase of two-stage sensing 415). In some examples, such as reference... Figure 6 In more detail, the UE may send an S-BSR to request radar resources for the tracking phase 425 of two-stage sensing 415 or for single-stage sensing 405. In some examples, such as reference... Figure 7 In more detail, the UE can send indications (e.g., via RRC signaling) to network entities for one or more parameters (e.g., KPIs), and can receive control signaling (e.g., RRC signaling) indicating the timing of PUSCH (e.g., CG) for sensing resources (e.g., for transmitting waveform 210). In some examples, such as reference Figure 8 In more detail, the UE may receive control signaling (e.g., RRC signaling) indicating various schemes (e.g., resource configuration) for radar sensing. The UE may activate one of the indicated schemes via a control message (e.g., a UCI message or a MAC-CE message) and then transmit the radar sensing waveform 210 via the sensing resources of the activated scheme.

[0136] Figure 5An example of a process flow 500 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. Process flow 500 may implement aspects of wireless communication system 100, wireless communication system 200, JCR system 300, radar sensing scheme 400, or any combination thereof, or may be implemented by these aspects. For example, process flow 500 may include UE 115-h and network entity 105-a, which may be references... Figures 1 to 4 Examples of the corresponding devices described.

[0137] UE 115-h and network entity 105-a can utilize SR signaling to request scans (e.g., sending a Sensing Scheduling Request (S-SR) message to network entity 105-a to request resources for performing radar sensing scans (such as scan phases of single-stage or two-stage sensing). For example, as referenced Figure 5As described, UE 115-h may request resources from network entity 105-a to transmit sensing waveforms, such as sounding reference signals (SRS) or radar waveforms (such as frequency modulated continuous wave (FMCW)). UE 115-h may send a first SR indication (e.g., a sensing scheduling request) to network entity 105-a to request these resources. UE 115-h may receive an indication (e.g., permission for sensing) from network entity 105-a, and may transmit radar sensing waveforms via one or more sensing resources after receiving the indication (e.g., permission). The one or more sensing resources may be one or more pre-configured resources that implement a static scan phase with periodic transmission having a given resource allocation (e.g., within a resource allocation defined according to a given time and frequency comb, bandwidth, start and end symbols within the period, time periodicity, and beam information such as beamwidth and beam direction). The Sensing Scheduling Request (S-SR) message can also indicate radar KPI requirements to network entity 105-a to request resources for transmitting sensing waveforms at 515. UE 115-h can transmit S-SR messages via dedicated S-SR timings (e.g., for sensing-only SRs, such as SSRs). Network entity 105-a can configure UE 115-h using S-SR resources (e.g., and separate SR resources for wireless communication), and UE 115-h can transmit S-SR messages via resources granted for S-SR messages (e.g., and can transmit and deliver SRs via resources granted for SRs). In some examples, network entity 105-a can configure UE 115-h using a set of resources for SRs and S-SRs, and UE 115-h can transmit SRs or SSRs via any given timing in the SR timing set, depending on the configuration. In some examples, UE 115-h can associate radar transmissions with logical channel indices and transmit using the corresponding SR timing.

[0138] At 505, UE 115-h may (e.g., from network entity 105-b) receive control signaling indicating a first set of resources for transmitting an SSR message used to send a radar sensing waveform for radar scanning. In some examples, the control signaling may indicate a first set of resources for transmitting the SSR message and a second set of resources for transmitting the SSR message for wireless communication with a wireless device (e.g., another UE 115, network entity 105-a, etc.), and at 510, the SSR message may be transmitted via one or more resources in the first set of resources.

[0139] In some examples, UE 115-h may send a message requesting resources for transmitting a sensing scheduling request via it. For example, in some examples, UE 115-h may only have a MAC-CE (e.g., S-SR) at 510, but no other uplink data for transmission. In such examples, UE 115-h may wait for uplink grant (e.g., control signaling at 505). For example, UE 115-h may wait for available configuration grant, but configuration grant may not be available, or such resources may not occur frequently. In such examples, UE 115-h may send a scheduling request to request resources for transmitting a sensing scheduling request at 510. In response, network entity 105-a may send control signaling at 505 indicating dynamic uplink grant. In some examples, UE 115-h may reuse an SR (e.g., S-SR) used for sensing to request resources for other S-SRs. In such examples, an S-SR can be used to request sensing resources, but it can also be used to request resources for transmitting another S-SR. For example, prior to 505, UE 115-h may send a first S-SR requesting resources for transmitting another S-SR. In response, network entity 105-a may send control signaling at 505, granting resources for transmitting a second S-SR at 510. Then, UE 115-h may send a second S-SR requesting resources for sensing at 530. Based on this, permission for sensing may then be received at 520.

[0140] In some examples, the request for uplink permission may include a built-in delay to support the scan phase so that the S-SR can be completed and transmitted after the scan. This delay may be part of the SR configuration signaling. In some examples, one or both of the S-SR or S-BSR described herein may include a timer disablement (e.g., a timer may be started after the transmission of the first request, such as the first S-SR, and the next S-SR may be sent when the timer expires).

[0141] At 510, UE 115-h may send an S-SR message via a first resource requesting resources for transmitting radar sensing waveforms for radar scanning. The S-SR message may include indications of one or more parameters (e.g., KPIs) for radar scanning, such as a threshold field of view (e.g., minimum field of view value), a threshold delay value (e.g., maximum permitted delay duration), a threshold resolution (e.g., minimum resolution value), or any combination thereof. UE 115-h may receive permission for sensing at 520 based at least in part on one or more parameters. The S-SR message may be sent via PUCCH.

[0142] At 515, in some examples, UE 115-h may also send a communication SR that requests resources for sending an uplink message to network entity 105-a. UE 115-h may send the communication SR via a second set of resources allocated for the communication SR as indicated at 505, or via a selection from a set of timings indicated at 505 for both communication SRs and SSRs.

[0143] At 520, UE 115-h may receive permission for one or more sensing resources for radar scanning, at least in part, based on the transmission of an S-SR message at 510. In some examples, permission for sensing may include indications of time resource combs, frequency resource combs, bandwidth, start symbols, end symbols, periodicity, beam identifiers, or any combination thereof for transmitting radar sensing waveforms.

[0144] In some examples, at 525, UE 115-h may receive a second grant for one or more wireless communication resources for uplink messaging, at least in part, based on sending a communication SR message (e.g., from network entity 105-a). The one or more sensing resources may differ from the one or more wireless communication resources used for radar sensing.

[0145] At 530, UE 115-h may transmit one or more radar sensing waveforms via one or more sensing resources granted at 520 (e.g., as referenced). Figure 4 (For a more detailed description). The radar sensing waveform can be SRS or FMCW, etc.

[0146] Figure 6 An example of a process flow 600 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. Process flow 600 may implement aspects of wireless communication system 100, wireless communication system 200, JCR system 300, radar sensing scheme 400, process flow 500, or any combination thereof, or may be implemented by these aspects. For example, process flow 600 may include UE 115-i and network entity 105-b, which may be references... Figures 1 to 5 Examples of the corresponding devices described.

[0147] In some examples, the UE 115-i may send a dedicated report (e.g., a sensing status report, which may be referred to as a sensing BSR (S-BSR)) to request resources for the tracking phase of two-phase sensing or for single-phase sensing. (See reference...) Figure 6According to the described technology, UE 115-i can send a sensing status report (e.g., S-BSR) to network entity 105-b via PUSCH. The S-BSR may include a list of target parameters containing parameters for multiple targets (e.g., those detected during the tracking phase of a two-phase sensing process). K One or more parameter values ​​are required for each target in a target (either a single target or a target for single-stage sensing). Parameters for a target may include time-frequency resources, including frequency combs, bandwidth, start or initial bandwidth, time periodicity, frame length, spatial resources, spatial QCL information corresponding to the time-frequency resources (with SRS index (SRI) or QCL based on beam correspondence with downlink beams) or any combination thereof.

[0148] In one scenario, S-BSR can be dynamically triggered after the scan phase (e.g., in two-stage sensing). The number of items in the target parameter list and the parameters of the items in the list can depend on the targets detected in the scan phase to achieve the tracking phase of two-stage sensing. In some examples, S-BSR can be triggered on demand for single-stage sensing, thereby supporting or addressing aspects of one or more applications or use cases. In such cases, the number of items in the target parameter list and the parameters of the items in the list can depend on the application. For example, in adaptive cruise control applications, the target list can focus on a wide-side beam with time-frequency resources for on-demand range and speed requirements.

[0149] In some examples, S-BSRs can be sent based on a semi-persistent schedule. If any target has been detected, S-BSRs can be periodically activated after each scan phase using semi-persistent PUSCH permission. No SSR is sent when a scan phase indicates that no target is detected.

[0150] In some examples, UE 115-i may receive an indication from network entity 105 for sensing resources used to transmit sensing waveforms (e.g., in response to an S-BSR). UE 115 then transmits on the requested sensing resources after receiving the indication from network entity 105.

[0151] At 620, UE 115-i may send an S-BSR to network entity 105-b. The S-BSR may indicate one or more sets of parameters associated with tracking one or more target objects. Each set of parameters may correspond to a specific target object among the one or more target objects. Parameters for one target object may include time-frequency resources, including frequency combs, bandwidth, start or initial bandwidth, time periodicity, frame length, spatial resources, spatial QCL information corresponding to the time-frequency resources (with an SRS index (SRI) or a QCL based on beam correspondence with downlink beams), or any combination thereof. UE 115-i may send the S-BSR via PUSCH.

[0152] At 625, UE 115-i can receive permission for sensing (e.g., for...). K For each of the target objects (a set of one or more resource subsets), the permission for sensing may include permission for sensing resources that satisfy a first set of one or more parameter sets for a first target object among the one or more target objects, for radar tracking of the first target object at least in part based on S-BSR.

[0153] At 630, UE 115-i can transmit one or more radar sensing waveforms via sensing resources for radar tracking of at least a first target object.

[0154] In some examples, at 610, UE 115-i may detect target objects based on performing a beam scanning process for radar sensing (e.g., a scanning phase of two-stage sensing). In such examples, S-BSR may include parameters for each detected object.

[0155] In some examples, at 615, the UE 115-i can initiate an application associated with target tracking. Initiation of the application can trigger the transmission of the S-BSR. In some examples, the UE 115-i can select different sets of parameters to include in the S-BSR based on the type of application initiated at 615.

[0156] In some examples, at 605, UE 115-i may receive control signaling instructing a semi-persistent scheduling, which identifies the periodic timing for transmitting the S-BSR. UE 115-i may detect one or more target objects during a radar scan phase prior to the first periodic timing of the semi-persistent scheduling, and UE 115-i may transmit the S-BSR at 620 via the first periodic timing.

[0157] In some examples, UE 115-i may send a message requesting resources for transmitting a sensing scheduling request via it. For example, in some examples, UE 115-i may only have a MAC-CE (e.g., S-SR) at 620, but no other uplink data for transmission. In such examples, UE 115-i may wait for uplink grant (e.g., control signaling at 505). For example, UE 115-i may wait for available configuration grant, but configuration grant may not be available, or such resources may not occur frequently. In such examples, UE 115-i may send a scheduling request to request resources for transmitting an S-BSR at 620. In response, network entity 105-b may send control signaling at 605 indicating dynamic uplink grant. In some examples, UE 115-i may reuse an SR (e.g., S-BSR) used for sensing to request resources for other S-BSRs. In such examples, an S-BSR can be used to request sensing resources, but it can also be used to request resources for sending another S-BSR. For example, prior to 605, UE 115-i can send a first S-BSR or a dedicated SR that requests resources for sending another S-BSR. In response, network entity 105-b can send control signaling at 605 that grants resources for sending the S-BSR at 620.

[0158] In some examples, the request for uplink permission may include a built-in delay to support the scan phase so that the S-BSR can be completed and transmitted after the scan. This delay may be part of the SR configuration signaling. In some examples, one or both of the S-SR or S-BSR described herein may include a timer disablement (e.g., a timer may be started after the transmission of the first request, such as the first S-BSR, and the next S-BSR may be sent when the timer expires).

[0159] Figure 7 An example of a process flow 700 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. Process flow 700 may implement aspects of wireless communication system 100, wireless communication system 200, JCR system 300, radar sensing scheme 400, process flow 500, process flow 600, or any combination thereof, or may be implemented by these aspects. For example, process flow 700 may include UE 115-j and network entity 105-c, which may be references... Figures 1 to 6 Examples of the corresponding devices described.

[0160] For reference Figure 7As described, UE 115-j can send indications of one or more sensing KPI requirements to network entity 105-c via RRC signaling and can receive CGs for sensing resources. For the scanning phase of two-phase sensing, UE 115-j can request parameters such as a wider field of view (FOV) with corresponding delay values ​​(e.g., a wider beam for wider coverage, utilizing fewer SRS resources, thus scanning the entire area with fewer beams). UE 115-j can also request lower range resolution and smaller bandwidth for efficient resource utilization. In some examples, UE 115-j can request lower velocity resolution and a shorter time duration for the detection reference signal (SRS) used for candidate target identification.

[0161] In some examples, UE 115-j may send indications of KPI requirements for the tracking phase used in two-stage sensing. UE 115-j may request a narrower beam pointing at the target for better tracking, and a larger bandwidth for better range resolution, or a larger repetition for better velocity resolution, or both.

[0162] In some cases, UE 115-j may send indications of KPI values ​​for both the scan and tracking phases together or in separate messages. Additionally or alternatively, UE 115-j may send KPI values ​​for single-phase sensing.

[0163] At 705, UE 115-j may send a first control signaling (e.g., RRC signaling) indicating one or more sensing parameters (e.g., KPIs) for transmitting radar sensing waveforms to perform radar sensing. The sensing parameters may include indications of field of view, delay thresholds, beamwidth, number of resources, threshold resolution, or any combination thereof. The transmission of the radar sensing waveforms is at least partially based on a radar tracking procedure corresponding to one or more sensing parameters. In some examples, the sensing parameters may include a first subset of parameters corresponding to a radar scanning procedure and a second subset of parameters corresponding to a radar tracking procedure.

[0164] At 710, UE 115-j may (e.g., from network entity 105-c) receive a second control signaling (e.g., RRC signaling) that instructs UE 115-j to be scheduled to transmit radar sensing waveforms via one or more uplink shared channel timings in the uplink shared channel timing set (e.g., CG indicating multiple periodic PUSCH timings).

[0165] At 715, UE 115-j can transmit one or more radar sensing waveforms via one or more PUSCH timings based on sensing parameters.

[0166] Figure 8 An example of a process flow 800 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. Process flow 800 may implement aspects of wireless communication system 100, wireless communication system 200, JCR system 300, radar sensing scheme 400, process flow 500, process flow 600, process flow 700, or any combination thereof, or may be implemented by these aspects. For example, process flow 800 may include UE 115-k network entities 105-d, which may be references... Figures 1 to 7 Examples of the corresponding devices described.

[0167] In some examples, such as reference Figure 8 The described sensing resources support the activation of RRC configuration. Network entity 105-d can configure different sensing resources for UE 115-k via RRC signaling. For example, network entity 105-d can indicate multiple sets of resources with different periodicity, different modes, or different sets or subsets of resources. For example, each configuration (e.g., each scheme) of one or more resources may include one or more of the following: time and frequency comb, bandwidth, start and end symbols within a period, time periodicity, beam information such as beamwidth and beam direction, SPS duration (e.g., temporal duration), spatial QCL information, or any combination thereof.

[0168] UE 115-k can send control messages (e.g., UCI messages or MAC-CE messages) that include a request to activate one of the RRC configurations. In some cases, UE 115-k can use UCI messages or MAC-CE messages to indicate the number of cycles to activate a given configuration. Alternatively, a configuration may be kept active by default, and UE 115 can indicate that it will not use the current cycle.

[0169] At 805, network entity 105-d may receive control signaling (e.g., RRC signaling) indicating multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources used for radar sensing. UE 115-k may receive, via control signaling, one or more parameters indicating a corresponding set of sensing resources taught for radar sensing. These parameters may include one or more of the following: time resource comb, frequency resource comb, bandwidth, start symbol, end symbol, periodicity, beam identifier, quasi-co-location indicator, or any combination thereof.

[0170] At 810, UE 115-k may send a control message (e.g., a UCI message or a MAC-CE message) that includes a request to activate a first radar sensing scheme among a plurality of radar sensing schemes. The control message may include an indication of the number of cycles for activating the first radar sensing scheme.

[0171] At 815, UE 115-k can receive an acknowledgment (ACK) message corresponding to a control message (e.g., indicating that network entity 105-d has received a UCI message or a MAC-CE message).

[0172] At 820, UE 115-k may transmit one or more radar sensing waveforms via at least a first resource corresponding to a first radar sensing scheme activated by a control message.

[0173] In some examples, UE 115-k may receive control signaling (e.g., at 805, or via separate control signaling) indicating that the second radar sensing scheme is the default radar sensing scheme. In such examples, after transmitting radar sensing waveforms at 820 and when the time period associated with the first radar sensing scheme expires, UE 115-k may switch from the first radar sensing scheme to the second radar sensing scheme and may transmit additional sensing waveforms via resources of the second radar sensing scheme (e.g., the default scheme).

[0174] In some examples, UE 115-k may receive control signaling (e.g., at 805, or via separate control signaling) indicating that the first radar sensing scheme is the default radar sensing scheme. UE 115-k may determine that it does not have any additional radar sensing to perform during the second resource corresponding to the first radar sensing scheme, and may (e.g., to network entity 105-d) send a control message instructing the UE not to transmit the second radar sensing waveform via the second resource corresponding to the first radar sensing scheme.

[0175] Figure 9 A block diagram 900 is shown of an apparatus 905 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure. Apparatus 905 may be an example of various aspects of UE 115 as described herein. Apparatus 905 may include a receiver 910, a transmitter 915, and a communications manager 920. Apparatus 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0176] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with signaling and resource allocation for radar sensing using uplink resources). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0177] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to signaling and resource allocation for radar sensing using uplink resources). In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0178] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of signaling and resource allocation for radar sensing using uplink resources as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0179] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). This hardware may include a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0180] Additionally or alternatively, in some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0181] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0182] According to the examples disclosed herein, the communication manager 920 can support wireless communication at the UE. For example, the communication manager 920 can, is configured to, or is operable to support components for receiving control signaling instructing a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning. The communication manager 920 can, is configured to, or is operable to support components for transmitting a sensing scheduling request message via a first resource requesting a resource for transmitting a radar sensing waveform for radar scanning. The communication manager 920 can, is configured to, or is operable to support components for receiving permission for one or more sensing resources for radar scanning based on the transmission of the sensing scheduling request message. The communication manager 920 can, is configured to, or is operable to support components for transmitting a radar sensing waveform via one or more sensing resources.

[0183] Additionally or alternatively, according to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be capable of, configured to, or operable to support components for transmitting a sense buffer status report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a corresponding target object among the one or more target objects. The communication manager 920 may be capable of, configured to, or operable to support components for receiving, based on the sense buffer status report, approval of sense resources that satisfy a first set of parameters in one or more sets of parameters for a first target object among the one or more target objects for radar tracking of the first target object. The communication manager 920 may be capable of, configured to, or operable to support components for transmitting one or more radar sensing waveforms via sense resources for radar tracking of the first target object.

[0184] Additionally or alternatively, according to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be capable of, configured to, or operable to support components for transmitting first control signaling indicating one or more sensing parameters for transmitting radar sensing waveforms for radar sensing. The communication manager 920 may be capable of, configured to, or operable to support components for receiving second control signaling based on the first control signaling indicating one or more sensing parameters, the second control signaling instructing the UE to be scheduled to transmit radar sensing waveforms via a set of multiple uplink shared channel timings. The communication manager 920 may be capable of, configured to, or operable to support components for transmitting radar sensing waveforms via one or more uplink shared channel timings from a set of multiple uplink shared channel timings based on one or more sensing parameters.

[0185] Additionally or alternatively, according to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be capable of, configured to, or operable to support components for receiving control signaling indicative of a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing. The communication manager 920 may be capable of, configured to, or operable to support components for transmitting a control message including a request to activate a first radar sensing scheme in the set of multiple radar sensing schemes. The communication manager 920 may be capable of, configured to, or operable to support components for receiving an acknowledgment message corresponding to the control message. The communication manager 920 may be capable of, configured to, or operable to support components for transmitting a radar sensing waveform via a first resource corresponding to the first radar sensing scheme based on the receipt of the acknowledgment message.

[0186] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., a processor that controls receiver 910, transmitter 915, communication manager 920, or any combination thereof or otherwise coupled to them) can support radar sensing techniques for achieving improved efficiency of the JCR system, more efficient use of communication resources, reduced latency, and improved user experience.

[0187] Figure 10 A block diagram 1000 of an apparatus 1005 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. Apparatus 1005 may be an example of aspects of apparatus 905 or UE 115 as described herein. Apparatus 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Apparatus 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0188] Receiver 1010 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to signaling and resource allocation for radar sensing using uplink resources). The information may be passed to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of antennas.

[0189] Transmitter 1015 may provide components for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to signaling and resource allocation for radar sensing using uplink resources). In some examples, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0190] Device 1005 or its various components may be examples of parts used to perform various aspects of signaling and resource allocation for radar sensing using uplink resources as described herein. For example, communication manager 1020 may include SSR manager 1025, sensing permission manager 1030, radar sensing waveform manager 1035, S-BSR manager 1040, control signaling manager 1045, radar sensing scheme manager 1050, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0191] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at the UE. The SSR manager 1025 is capable of, configured to, or operable to support components for receiving control signaling instructing a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning. The SSR manager 1025 is capable of, configured to, or operable to support components for transmitting a sensing scheduling request message via a first resource requesting a resource for transmitting a radar sensing waveform for radar scanning. The sensing permission manager 1030 is capable of, configured to, or operable to support components for receiving permission for one or more sensing resources for radar scanning based on the transmission of a sensing scheduling request message. The radar sensing waveform manager 1035 is capable of, configured to, or operable to support components for transmitting a radar sensing waveform via one or more sensing resources.

[0192] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. The S-BSR manager 1040 is capable of, configured to, or operable to support components for transmitting a sense buffer status report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a specific target object among the one or more target objects. The sense grant manager 1030 is capable of, configured to, or operable to support components for receiving, based on the sense buffer status report, grant of permission to sense resources that satisfy a first set of parameters among one or more sets of parameters for a first target object among the one or more target objects for radar tracking of the first target object. The radar sense waveform manager 1035 is capable of, configured to, or operable to support components for transmitting one or more radar sense waveforms via sense resources for radar tracking of the first target object.

[0193] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. The control signaling manager 1045 is capable of, configured to, or operable to support components for transmitting a first control signaling indicating one or more sensing parameters for transmitting radar sensing waveforms for radar sensing. The control signaling manager 1045 is capable of, configured to, or operable to support components for receiving a second control signaling based on the first control signaling indicating one or more sensing parameters, the second control signaling instructing the UE to be scheduled to transmit radar sensing waveforms via a set of multiple uplink shared channel timings. The radar sensing waveform manager 1035 is capable of, configured to, or operable to support components for transmitting radar sensing waveforms based on one or more sensing parameters via one or more uplink shared channel timings from a set of multiple uplink shared channel timings.

[0194] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. The radar sensing scheme manager 1050 is capable of, configured to, or operable to support components for receiving control signaling indicating a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing. The radar sensing scheme manager 1050 is capable of, configured to, or operable to support components for transmitting a control message including a request to activate a first radar sensing scheme in the set of multiple radar sensing schemes. The radar sensing waveform manager 1035 is capable of, configured to, or operable to support components for receiving an acknowledgment message corresponding to the control message. The radar sensing waveform manager 1035 is capable of, configured to, or operable to support components for transmitting a radar sensing waveform via a first resource corresponding to the first radar sensing scheme based on the received acknowledgment message.

[0195] Figure 11 A block diagram 1100 is shown of a communication manager 1120 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of signaling and resource allocation for radar sensing using uplink resources as described herein. For example, the communication manager 1120 may include an SSR manager 1125, a sensing permission manager 1130, a radar sensing waveform manager 1135, an S-BSR manager 1140, a control signaling manager 1145, a radar sensing scheme manager 1150, an SR manager 1155, an uplink message manager 1160, an application manager 1165, a timing manager 1170, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0196] According to the examples disclosed herein, the communication manager 1120 can support wireless communication at the UE. The SSR manager 1125 is capable of, configured to, or operable to support components for receiving control signaling instructing a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning. In some examples, the SSR manager 1125 is capable of, configured to, or operable to support components for transmitting a sensing scheduling request message via a first resource requesting a resource for transmitting a radar sensing waveform for radar scanning. The sensing permission manager 1130 is capable of, configured to, or operable to support components for receiving permission for one or more sensing resources for radar scanning based on the transmission of a sensing scheduling request message. The radar sensing waveform manager 1135 is capable of, configured to, or operable to support components for transmitting a radar sensing waveform via one or more sensing resources.

[0197] In some examples, the SSR manager 1125 is capable of, configured to, or operable to support components for receiving control signaling for a first set of multiple resources indicating for sending a sensing scheduling request message and a second set of multiple resources indicating for sending a scheduling request message for wireless communication with a wireless device, wherein the scheduling request message is sent via one or more resources in the first set of multiple resources.

[0198] In some examples, the sensing grant manager 1130 is capable of, configured to, or able to operate to support components for receiving indications of time resource combs, frequency resource combs, bandwidth, start symbols, end symbols, periodicity, beam identifiers, or any combination thereof via grants to one or more sensing resources, wherein radar sensing waveforms are transmitted according to such indications.

[0199] In some examples, the SSR manager 1125 is capable of, configured to, or operable to support components for sending indications of one or more parameters for a radar scan via a sensing scheduling request message, including a threshold field of view, a threshold delay value, a threshold resolution, or any combination thereof, wherein permission for sensing resources is based on the one or more parameters.

[0200] In some examples, the SSR manager 1125 is capable of, configured to, or able to operate to support components for sending a sense scheduling request resource message that requests a resource for sending the sense scheduling request message, wherein receiving control signaling indicating a first resource for sending the sense scheduling request message is at least partially based on sending the sense scheduling request resource message.

[0201] In some examples, the SR manager 1155 is capable of, configured to, or operable to support components for sending a communication scheduling request message that requests resources for sending uplink messages to a network entity. In some examples, the uplink message manager 1160 is capable of, configured to, or operable to support components for receiving a second grant of permission for one or more wireless communication resources for uplink messages based on sending a communication scheduling request message, wherein the one or more sensing resources are different from the one or more wireless communication resources. In some examples, the uplink message manager 1160 is capable of, configured to, or operable to support components for sending uplink messages to a network entity via one or more wireless communication resources.

[0202] In some examples, the radar sensing waveform includes a detection reference signal or a frequency-modulated continuous waveform.

[0203] In some examples, the sense scheduling request message is sent via the physical uplink control channel.

[0204] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. The S-BSR manager 1140 is capable of, configured to, or operable to support components for transmitting a sense buffer status report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a specific target object among the one or more target objects. In some examples, the sense grant manager 1130 is capable of, configured to, or operable to support components for receiving, based on the sense buffer status report, grant of permission to sense resources that satisfy a first set of parameters in one or more sets of parameters for a first target object among the one or more target objects for radar tracking of the first target object. In some examples, the radar sense waveform manager 1135 is capable of, configured to, or operable to support components for transmitting one or more radar sense waveforms via sense resources for radar tracking of the first target object.

[0205] In some examples, the S-BSR manager 1140 is capable of, configured to, or able to operate to support components for sending indications of time resources, frequency resources, bandwidth identifiers, periodicity, frame length, or any combination thereof via one or more sets of parameters.

[0206] In some examples, the S-BSR manager 1140 is capable of, configured to, or operable to support components for transmitting spatial quasi-co-location information via one or more sets of parameters, the spatial quasi-co-location information indicating a quasi-co-location relationship with a probe reference signal index or downlink beam.

[0207] In some examples, the radar sensing waveform manager 1135 is capable of, configured to, or operable to support components for performing a beam scanning process for radar sensing. In some examples, the radar sensing waveform manager 1135 is capable of, configured to, or operable to support components for detecting one or more target objects based on the beam scanning process, wherein a sensing buffer status report is sent based on the detection.

[0208] In some examples, the application manager 1165 is capable of, configured to, or able to operate to support components for launching applications associated with target tracking, wherein a sense buffer status report is sent based on the launch of the application.

[0209] In some examples, the S-BSR manager 1140 is capable of, configured to, or operable to support components for receiving control signaling indicative of a semi-persistent scheduling, which identifies periodic timing for transmitting sense buffer status reports. In some examples, the S-BSR manager 1140 is capable of, configured to, or operable to support components for detecting one or more target objects during a radar scan phase prior to a first periodic timing of the semi-persistent scheduling, wherein the transmission of the sense buffer status report is based on the semi-persistent scheduling and the detection.

[0210] In some examples, the S-BSR manager 1140 is capable of, configured to, or able to operate to support components for: sending a sense buffer status report resource message that requests resources for sending a sense buffer status report; and receiving control signaling indicative of a first resource for sending a sense buffer status report based on the send sense buffer status report resource message.

[0211] In some examples, the sense buffer status report is sent via the physical uplink shared channel.

[0212] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. The control signaling manager 1145 is capable of, configured to, or operable to support components for transmitting a first control signaling instruction for transmitting a radar sensing waveform for radar sensing. In some examples, the control signaling manager 1145 is capable of, configured to, or operable to support components for receiving a second control signaling based on the first control signaling instructing one or more sensing parameters, the second control signaling instructing the UE to be scheduled to transmit the radar sensing waveform via a set of multiple uplink shared channel timings. In some examples, the radar sensing waveform manager 1135 is capable of, configured to, or operable to support components for transmitting the radar sensing waveform based on one or more sensing parameters via one or more uplink shared channel timings from a set of multiple uplink shared channel timings.

[0213] In some examples, the control signaling manager 1145 is capable of, configured to, or able to operate to support components for transmitting indications of field of view, delay thresholds, beamwidth, number of resources, threshold resolution, or any combination thereof via one or more sensing parameters, wherein the transmitted radar sensing waveform is based on a radar scanning process corresponding to one or more sensing parameters.

[0214] In some examples, the control signaling manager 1145 is capable of, configured to, or able to operate to support components for transmitting indications of beamwidth, number of resources, threshold range resolution, threshold velocity resolution, or any combination thereof via one or more sensing parameters, wherein the transmitted radar sensing waveform is based on a radar tracking process corresponding to one or more sensing parameters.

[0215] In some examples, one or more sensing parameters include a first subset of parameters corresponding to the radar scanning process and a second subset of parameters corresponding to the radar tracking process.

[0216] In some examples, the first control signaling includes a radio resource control message.

[0217] In some examples, the second control signaling includes a radio resource control message that includes configuration permission.

[0218] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. The radar sensing scheme manager 1150 is capable of, configured to, or operable to support components for receiving control signaling indicating a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing. In some examples, the radar sensing scheme manager 1150 is capable of, configured to, or operable to support components for transmitting a control message including a request to activate a first radar sensing scheme in the set of multiple radar sensing schemes. In some examples, the radar sensing waveform manager 1135 is capable of, configured to, or operable to support components for receiving an acknowledgment message corresponding to the control message. In some examples, the radar sensing waveform manager 1135 is capable of, configured to, or operable to support components for transmitting a radar sensing waveform via a first resource corresponding to the first radar sensing scheme based on the receipt of the acknowledgment message.

[0219] In some examples, the radar sensing scheme manager 1150 is capable of, configured to, or operable to support components for receiving indications of one or more parameters corresponding to each respective set of sensing resources used for radar sensing via a set of multiple radar sensing schemes. In some examples, the one or more parameters include time resource combs, frequency resource combs, bandwidth, start symbol, end symbol, periodicity, beam identifier, quasi-co-location indicator, or any combination thereof. In some examples, control signaling includes radio resource control messages. In some examples, control messages include uplink control information messages. In some examples, control messages include MAC control elements (CEs).

[0220] In some examples, the timing manager 1170 is capable of, configured to, or operable to support components for sending an indication of the number of cycles for activating a first radar sensing scheme via control messages.

[0221] In some examples, the radar sensing scheme manager 1150 is capable of, configured to, or able to operate to support components for receiving control signaling indicating that a second radar sensing scheme is the default radar sensing scheme.

[0222] In some examples, the radar sensing scheme manager 1150 is capable of, configured to, or operable to support components for switching from the first radar sensing scheme to the second radar sensing scheme when a time period associated with the first radar sensing scheme expires, based at least in part on control signaling indicating that the second radar sensing scheme is the default radar sensing scheme. In some examples, the radar sensing scheme manager 1150 is capable of, configured to, or operable to support components for transmitting a second radar sensing waveform based on a switch via resources corresponding to the second radar sensing scheme.

[0223] In some examples, the radar sensing scheme manager 1150 is capable of, configured to, or operable to support components for receiving control signaling indicating that a first radar sensing scheme is the default radar sensing scheme. In some examples, the radar sensing scheme manager 1150 is capable of, configured to, or operable to support components for determining that the UE does not have any radar sensing to perform during a second resource corresponding to the first radar sensing scheme. In some examples, the radar sensing scheme manager 1150 is capable of, configured to, or operable to support components for sending a control message based on control signaling indicating that the first radar sensing scheme is the default radar sensing scheme, the control message instructing the UE not to send a second radar sensing waveform via the second resource corresponding to the first radar sensing scheme.

[0224] Figure 12A diagram of a system 1200 including device 1205 supporting signaling and resource allocation for radar sensing using uplink resources, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or UE 115 as described herein, or a component including such devices. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1245).

[0225] I / O controller 1210 manages the input and output signals of device 1205. I / O controller 1210 can also manage peripheral devices not integrated into device 1205. In some cases, I / O controller 1210 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1210 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, it may be another known operating system. Additionally or alternatively, the I / O controller 1210 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1210 may be implemented as part of a processor such as processor 1240. In some cases, a user may interact with device 1205 via the I / O controller 1210 or via hardware components controlled by the I / O controller 1210.

[0226] In some cases, device 1205 may include a single antenna 1225. However, in other cases, device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1215 may communicate bidirectionally via one or more antennas 1225 as described herein, or via a wired or wireless link. For example, transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1215 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1225 for transmission; and demodulating packets received from one or more antennas 1225. Transceiver 1215, or transceiver 1215 and one or more antennas 1225, may be an example of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof as described herein.

[0227] Memory 1230 may include random access memory (RAM) and read-only memory (ROM). Memory 1230 may store computer-readable, computer-executable code 1235, including instructions that, when executed by processor 1240, cause device 1205 to perform the various functions described herein. Code 1235 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1235 may not be directly executable by processor 1240, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, memory 1230 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0228] Processor 1240 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks supporting signaling and resource allocation for radar sensing using uplink resources). For example, device 1205 or components of device 1205 may include processor 1240 and memory 1230 coupled to or coupled to processor 1240, processor 1240 and memory 1230 being configured to perform the various functions described herein.

[0229] According to the examples disclosed herein, the communication manager 1220 can support wireless communication at the UE. For example, the communication manager 1220 is capable of, configured to, or operable to support components for receiving control signaling for a first resource used to transmit a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning. The communication manager 1220 is capable of, configured to, or operable to support components for transmitting a sensing scheduling request message via a first resource requesting a resource for transmitting a radar sensing waveform for radar scanning. The communication manager 1220 is capable of, configured to, or operable to support components for receiving permission for one or more sensing resources for radar scanning based on the transmission of the sensing scheduling request message. The communication manager 1220 is capable of, configured to, or operable to support components for transmitting a radar sensing waveform via one or more sensing resources.

[0230] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1220 may support wireless communication at the UE. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for transmitting a sense buffer status report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a corresponding target object among the one or more target objects. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving, based on the sense buffer status report, approval of sense resources that satisfy a first set of parameters in one or more sets of parameters for a first target object among the one or more target objects for radar tracking of the first target object. The communication manager 1220 may be capable of, configured to, or operable to support components for transmitting one or more radar sensing waveforms via sense resources for radar tracking of the first target object.

[0231] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1220 may support wireless communication at the UE. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for transmitting first control signaling indicating one or more sensing parameters for transmitting radar sensing waveforms for radar sensing. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving second control signaling based on the first control signaling indicating one or more sensing parameters, the second control signaling instructing the UE to be scheduled to transmit radar sensing waveforms via a set of multiple uplink shared channel timings. The communication manager 1220 may be capable of, configured to, or operable to support components for transmitting radar sensing waveforms via one or more uplink shared channel timings from a set of multiple uplink shared channel timings based on one or more sensing parameters.

[0232] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1220 may support wireless communication at the UE. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for receiving control signaling indicative of a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing. The communication manager 1220 may be capable of, configured to, or operable to support components for transmitting a control message including a request to activate a first radar sensing scheme in the set of multiple radar sensing schemes. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving an acknowledgment message corresponding to the control message. The communication manager 1220 may be capable of, configured to, or operable to support components for transmitting a radar sensing waveform via a first resource corresponding to the first radar sensing scheme based on the receipt of the acknowledgment message.

[0233] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support radar sensing techniques for achieving improved efficiency of the JCR system, more efficient utilization of communication resources, improved radar sensing, reduced latency, and improved user experience.

[0234] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by processor 1240, memory 1230, code 1235, or any combination thereof. For example, code 1235 may include instructions executable by processor 1240 to cause device 1205 to perform various aspects of signaling and resource allocation for radar sensing using uplink resources as described herein, or processor 1240 and memory 1230 may be otherwise configured to perform or support such operations.

[0235] Figure 13 A flowchart illustrating a method 1300 for signaling and resource allocation for radar sensing using uplink resources, illustrative of various aspects of this disclosure, is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be implemented by, as referenced... Figures 1 to 12 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally or alternatively, the wireless UE may use dedicated hardware to perform aspects of the described functions.

[0236] At 1305, the method may include: receiving control signaling indicating a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning. The operation of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference needed]. Figure 11 The described SSR manager 1125 is executed.

[0237] At 1310, the method may include: sending a sensing scheduling request message via a first resource, the sensing scheduling request message requesting a resource for sending radar sensing waveforms for radar scanning. The operation of 1310 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 11 The described SSR manager 1125 is executed.

[0238] At 1315, the method may include: receiving permission for one or more sensing resources for radar scanning based on sending a sensing scheduling request message. The operation of 1315 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to [reference needed]. Figure 11The described sensing permission manager 1130 is executed.

[0239] At 1320, the method may include: transmitting a radar sensing waveform via one or more sensing resources. The operation of 1320 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1320 may be provided by reference to [reference needed]. Figure 11 The radar sensing waveform manager 1135 described is executed.

[0240] Figure 14 A flowchart illustrating a method 1400 for signaling and resource allocation for radar sensing using uplink resources, illustrative of various aspects of this disclosure, is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be implemented by, as referenced... Figures 1 to 12 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally or alternatively, the wireless UE may use dedicated hardware to perform aspects of the described functions.

[0241] At 1405, the method may include: sending a sense buffer state report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a corresponding target object among the one or more target objects. The operation of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 11 The S-BSR manager 1140 described is executed.

[0242] At 1410, the method may include: receiving, based on a sensing buffer state report, a criterion for sensing resources that satisfy a first set of parameters in one or more parameter sets for a first target object among one or more target objects, for radar tracking of the first target object. The operation of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference needed]. Figure 11 The described sensing permission manager 1130 is executed.

[0243] At 1415, the method may include: transmitting one or more radar sensing waveforms via sensing resources for radar tracking of a first target object. The operation of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be derived from references... Figure 11 The radar sensing waveform manager 1135 described is executed.

[0244] Figure 15A flowchart illustrating a method 1500 for signaling and resource allocation for radar sensing using uplink resources, illustrative of various aspects of this disclosure, is shown. Operation of method 1500 may be implemented by a UE or its components as described herein. For example, operation of method 1500 may be implemented by, as referenced... Figures 1 to 12 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally or alternatively, the wireless UE may use dedicated hardware to perform aspects of the described functions.

[0245] At 1505, the method may include: sending first control signaling indicating one or more sensing parameters for transmitting a radar sensing waveform to perform radar sensing. The operation of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to... Figure 11 The control signaling manager 1145 described is executed.

[0246] At 1510, the method may include: receiving second control signaling based on first control signaling indicating one or more sensing parameters, the second control signaling instructing the UE to be scheduled to transmit a radar sensing waveform via a set of multiple uplink shared channel timings. Operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be provided by reference to [reference needed]. Figure 11 The control signaling manager 1145 described is executed.

[0247] At 1515, the method may include: transmitting a radar sensing waveform based on one or more sensing parameters via one or more uplink shared channel timings from a set of multiple uplink shared channel timings. The operation of 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to [reference needed]. Figure 11 The radar sensing waveform manager 1135 described is executed.

[0248] Figure 16 A flowchart illustrating a method 1600 for signaling and resource allocation for radar sensing using uplink resources, illustrative of various aspects of this disclosure, is shown. Operation of method 1600 may be implemented by a UE or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 12 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally or alternatively, the wireless UE may use dedicated hardware to perform aspects of the described functions.

[0249] At 1605, the method may include: receiving control signaling indicating a set of multiple radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing. The operation of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 11 The described radar sensing scheme manager 1150 is executed.

[0250] At 1610, the method may include: sending a control message including a request to activate a first radar sensing scheme in a set of multiple radar sensing schemes. The operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to... Figure 11 The described radar sensing scheme manager 1150 is executed.

[0251] At 1615, the method may include: receiving an acknowledgment message corresponding to a control message. The operation of 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 11 The radar sensing waveform manager 1135 described is executed.

[0252] At 1620, the method may include: transmitting a radar sensing waveform via a first resource corresponding to a first radar sensing scheme based on the receipt of an acknowledgment message. The operation of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1620 may be derived from references... Figure 11 The radar sensing waveform manager 1135 described is executed.

[0253] The following provides an overview of the various aspects of this disclosure:

[0254] Aspect 1: A method for performing wireless communication at a UE, the method comprising: receiving control signaling indicating a first resource for transmitting a sensing scheduling request message for transmitting a radar sensing waveform for radar scanning; transmitting the sensing scheduling request message via the first resource, the sensing scheduling request message requesting resources for transmitting the radar sensing waveform for radar scanning; receiving permission for one or more sensing resources for radar scanning based at least in part on transmitting the sensing scheduling request message; and transmitting the radar sensing waveform via the one or more sensing resources.

[0255] Aspect 2: According to the method of aspect 1, the method further includes: receiving control signaling indicating a first plurality of resources for sending the sensing scheduling request message and a second plurality of resources for sending a scheduling request message for wireless communication with a wireless device, wherein the scheduling request message is sent via one or more of the first plurality of resources.

[0256] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: receiving an indication of a time resource comb, a frequency resource comb, a bandwidth, a start symbol, an end symbol, a periodicity, a beam identifier, or any combination thereof via the permission granted to one or more sensing resources, wherein the radar sensing waveform is transmitted according to the indication.

[0257] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: sending an indication of one or more parameters for the radar scan via the sensing scheduling request message, the one or more parameters including a threshold field of view, a threshold delay value, a threshold resolution, or any combination thereof, wherein the granting of the sensing resources is based at least in part on the one or more parameters.

[0258] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: sending a sensing scheduling request resource message, the sensing scheduling request resource message requesting a resource for sending the sensing scheduling request message, wherein receiving control signaling indicating the first resource for sending the sensing scheduling request message is at least in part based on sending the sensing scheduling request resource message.

[0259] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: sending a communication scheduling request message, the communication scheduling request message requesting resources for sending an uplink message to a network entity; receiving, at least in part, a second grant for one or more wireless communication resources for the uplink message based on sending the communication scheduling request message, wherein the one or more sensing resources are different from the one or more wireless communication resources; and sending the uplink message to the network entity via the one or more wireless communication resources.

[0260] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the radar sensing waveform includes a detection reference signal or a frequency-modulated continuous waveform.

[0261] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the sensing scheduling request message is sent via a physical uplink control channel.

[0262] Aspect 9: A method for wireless communication at a UE, the method comprising: transmitting a sense buffer state report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a corresponding target object among the one or more target objects; receiving, at least in part, based on the sense buffer state report, permission for sensing resources that satisfy a first set of parameters in the one or more sets of parameters for a first target object among the one or more target objects to perform radar tracking of the first target object; and transmitting one or more radar sensing waveforms via the sensing resources for radar tracking of the first target object.

[0263] Aspect 10: The method according to aspect 9, the method further comprising: sending an indication of time resources, frequency resources, bandwidth identifiers, periodicity, frame length, or any combination thereof via the one or more parameter sets.

[0264] Aspect 11: The method according to any one of Aspects 9 to 10, the method further comprising: transmitting spatial quasi-co-location information via the one or more parameter sets, the spatial quasi-co-location information indicating a quasi-co-location relationship with a probe reference signal index or a downlink beam.

[0265] Aspect 12: The method according to any one of Aspects 9 to 11, the method further comprising: performing a beam scanning process for radar sensing; and detecting the one or more target objects at least in part based on the beam scanning process, wherein the sensing buffer status report is sent at least in part based on the detection.

[0266] Aspect 13: The method according to any one of Aspects 9 to 12, the method further comprising: launching an application associated with target tracking, wherein sending the sensing buffer status report is at least in part based on launching the application.

[0267] Aspect 14: The method according to any one of Aspects 9 to 13, the method further comprising: receiving control signaling instructing a semi-persistent scheduling, the semi-persistent scheduling identifying a periodic timing for transmitting the sense buffer status report; and detecting the one or more target objects during a radar scanning phase prior to a first periodic timing of the semi-persistent scheduling, wherein transmitting the sense buffer status report is based at least in part on the semi-persistent scheduling and the detection.

[0268] Aspect 15: The method according to any one of Aspects 9 to 14, the method further comprising: sending a sense buffer status report resource message, the sense buffer status report resource message requesting resources for sending the sense buffer status report; and receiving control signaling indicating a first resource for sending the sense buffer status report, at least in part based on sending the sense buffer status report resource message.

[0269] Aspect 16: The method according to any one of Aspects 9 to 15, wherein the sensing buffer status report is transmitted via a physical uplink shared channel.

[0270] Aspect 17: A method for wireless communication at a UE, the method comprising: transmitting first control signaling indicating one or more sensing parameters for transmitting a radar sensing waveform for radar sensing; receiving second control signaling at least in part based on the first control signaling indicating the one or more sensing parameters, the second control signaling indicating that the UE is scheduled to transmit the radar sensing waveform via a plurality of uplink shared channel timings; and transmitting the radar sensing waveform via one or more of the plurality of uplink shared channel timings according to the one or more sensing parameters.

[0271] Aspect 18: The method according to aspect 17, the method further comprising: transmitting an indication of field of view, an indication of a delay threshold, an indication of beamwidth, an indication of the number of resources, an indication of threshold resolution, or any combination thereof via the one or more sensing parameters, wherein transmitting the radar sensing waveform is at least partially based on a radar scanning process corresponding to the one or more sensing parameters.

[0272] Aspect 19: The method according to any one of Aspects 17 to 18, the method further comprising: transmitting an indication of beamwidth, an indication of the number of resources, an indication of threshold range resolution, an indication of threshold velocity resolution, or any combination thereof via the one or more sensing parameters, wherein transmitting the radar sensing waveform is at least partially based on a radar tracking process corresponding to the one or more sensing parameters.

[0273] Aspect 20: The method according to any one of aspects 17 to 19, wherein the one or more sensing parameters include a first subset of parameters corresponding to a radar scanning process and a second subset of parameters corresponding to a radar tracking process.

[0274] Aspect 21: The method according to any one of Aspects 17 to 20, wherein the first control signaling includes a radio resource control message.

[0275] Aspect 22: The method according to any one of Aspects 17 to 21, wherein the second control signaling includes a radio resource control message, the radio resource control message including configuration permission.

[0276] Aspect 23: A method for wireless communication at a UE, the method comprising: receiving control signaling indicating a plurality of radar sensing schemes, each radar sensing scheme corresponding to a corresponding set of sensing resources for radar sensing; transmitting a control message including a request to activate a first radar sensing scheme among the plurality of radar sensing schemes; receiving an acknowledgment message corresponding to the control message; and transmitting a radar sensing waveform via a first resource corresponding to the first radar sensing scheme, at least in part based on receiving the acknowledgment message.

[0277] Aspect 24: According to the method of aspect 23, the method further includes: receiving, via the plurality of radar sensing schemes, an indication of one or more parameters corresponding to each respective set of sensing resources used for radar sensing.

[0278] Aspect 25: The method according to aspect 24, wherein the one or more parameters include time resource combs, frequency resource combs, bandwidth, start symbol, end symbol, periodicity, beam identifier, quasi-co-location indicator, or any combination thereof.

[0279] Aspect 26: The method according to any one of Aspects 23 to 25, wherein the control signaling includes a radio resource control message.

[0280] Aspect 27: The method according to any one of Aspects 23 to 26, wherein the control message includes an uplink control information message.

[0281] Aspect 28: The method according to any one of Aspects 23 to 27, wherein the control message includes a MAC control element (CE).

[0282] Aspect 29: The method according to any one of aspects 23 to 28, the method further comprising: sending an indication of the number of cycles for activating the first radar sensing scheme via the control message.

[0283] Aspect 30: The method according to any one of aspects 23 to 29, the method further comprising: receiving control signaling indicating that a second radar sensing scheme is a default radar sensing scheme.

[0284] Aspect 31: The method according to aspect 30, the method further comprising: switching from the first radar sensing scheme to the second radar sensing scheme when a time period associated with the first radar sensing scheme expires, based at least in part on the control signaling indicating that the second radar sensing scheme is the default radar sensing scheme; and transmitting a second radar sensing waveform via a resource corresponding to the second radar sensing scheme, based at least in part on the switching.

[0285] Aspect 32: The method according to any one of Aspects 23 to 31, the method further comprising: receiving control signaling indicating that the first radar sensing scheme is a default radar sensing scheme; determining that the UE has no radar sensing to perform during a second resource corresponding to the first radar sensing scheme; and sending a control message based at least in part on the control signaling indicating that the first radar sensing scheme is the default radar sensing scheme, the control message indicating that the UE will not send a second radar sensing waveform via the second resource corresponding to the first radar sensing scheme.

[0286] Aspect 33: An apparatus for wireless communication at a UE, the apparatus comprising: at least one processor; and at least one memory coupled to the at least one processor; the at least one memory storing instructions executable by the at least one processor to cause the apparatus to perform a method according to any one of aspects 1 to 8.

[0287] Aspect 34: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 8.

[0288] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 8.

[0289] Aspect 36: An apparatus for wireless communication at a UE, the apparatus comprising: at least one processor; and at least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the apparatus to perform a method according to any one of aspects 9 to 16.

[0290] Aspect 37: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 9 to 16.

[0291] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform the method according to any one of aspects 9 to 16.

[0292] Aspect 39: An apparatus for wireless communication at a UE, the apparatus comprising: at least one processor; and at least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the apparatus to perform a method according to any one of aspects 17 to 22.

[0293] Aspect 40: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 17 to 22.

[0294] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform the method according to any one of aspects 17 to 22.

[0295] Aspect 42: An apparatus for wireless communication at a UE, the apparatus comprising: at least one processor; and at least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the apparatus to perform a method according to any one of aspects 23 to 32.

[0296] Aspect 43: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 23 to 32.

[0297] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication at a UE, said code including instructions executable by a processor to perform the method according to any one of aspects 23 to 32.

[0298] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0299] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0300] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0301] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration).

[0302] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0303] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, while optical discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0304] As used herein (including in the claims), the word "or" used in an enumeration of items (e.g., an enumeration of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0305] As used herein (including in the claims), the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, a “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced by the article “a” using the terms “the” or “the” refer to any or all of the one or more components. For example, a component introduced by the article “a” should be understood to mean “one or more components,” and subsequent references to “the component” in a claim should be understood to be equivalent to references to “at least one of one or more components.”

[0306] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0307] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0308] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0309] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one processor; and At least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the device to: Receive control signaling for a first resource to send a sensing scheduling request message, the sensing scheduling request message being used to send a radar sensing waveform for radar scanning; A sensing scheduling request message is sent via the first resource, the sensing scheduling request message requesting a resource for sending the radar sensing waveform for radar scanning; At least in part, permission for one or more sensing resources for radar scanning is received based on sending the aforementioned sensing scheduling request message; as well as The radar sensing waveform is transmitted via the one or more sensing resources.

2. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The control signaling is received to indicate a first plurality of resources for sending the sensing scheduling request message and a second plurality of resources for sending a scheduling request message for wireless communication with a wireless device, wherein the scheduling request message is sent via one or more of the first plurality of resources.

3. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The radar sensing waveform is transmitted according to the permission granted to one or more sensing resources, thereby receiving an indication of a time resource comb, a frequency resource comb, a bandwidth, a start symbol, an end symbol, a periodicity, a beam identifier, or any combination thereof.

4. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The sensor scheduling request message is used to send an indication of one or more parameters for the radar scan, including a threshold field of view, a threshold delay value, a threshold resolution, or any combination thereof, wherein the granting of the sensing resources is based at least in part on the one or more parameters.

5. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Sending a sensing scheduling request resource message, the sensing scheduling request resource message requesting a resource for sending the sensing scheduling request message, wherein receiving control signaling indicating the first resource for sending the sensing scheduling request message is at least in part based on sending the sensing scheduling request resource message.

6. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Send a communication scheduling request message, the communication scheduling request message requesting resources for sending uplink messages to network entities; At least in part, receiving a second grant for one or more wireless communication resources for the uplink message is based on sending the communication scheduling request message, wherein the one or more sensing resources are different from the one or more wireless communication resources; as well as The uplink message is sent to the network entity via one or more wireless communication resources.

7. The apparatus of claim 1, wherein the radar sensing waveform includes a detection reference signal or a frequency-modulated continuous waveform.

8. The apparatus of claim 1, wherein the sensing scheduling request message is transmitted via a physical uplink control channel.

9. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one processor; and At least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the device to: Send a sense buffer status report indicating one or more sets of parameters associated with tracking one or more target objects, each set of parameters corresponding to a specific target object among the one or more target objects; At least in part based on the sensing buffer status report, the accreditation of sensing resources that satisfy a first set of parameters in one or more parameter sets for a first target object among the one or more target objects is used for radar tracking of the first target object; as well as One or more radar sensing waveforms are transmitted via the sensing resources for radar tracking of the first target object.

10. The apparatus of claim 9, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Indications for time resources, frequency resources, bandwidth identifiers, periodicity, frame length, or any combination thereof are sent via the one or more sets of parameters.

11. The apparatus of claim 9, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Spatial quasi-co-location information is transmitted via the one or more parameter sets, the spatial quasi-co-location information indicating a quasi-co-location relationship with a probe reference signal index or downlink beam.

12. The apparatus of claim 9, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Perform beam scanning for radar sensing; and The detection of the one or more target objects is based at least in part on the beam scanning process, wherein the sending of the sensing buffer status report is based at least in part on the detection.

13. The apparatus of claim 9, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Launch an application associated with target tracking, wherein sending the sense buffer status report is based at least in part on launching the application.

14. The apparatus of claim 9, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Receive control signaling indicating semi-persistent scheduling, wherein the semi-persistent scheduling identifier is used for periodic timing of sending the sense buffer status report; and The one or more target objects are detected during a radar scan phase prior to the first periodic timing of the semi-persistent scheduling, wherein the sensing buffer status report is sent based at least in part on the semi-persistent scheduling and the detection.

15. The apparatus of claim 9, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Sending a sense buffer status report resource message, the sense buffer status report resource message requesting resources for sending the sense buffer status report; and The control signaling indicating a first resource for sending the sense buffer status report is received, at least in part, based on sending the sense buffer status report resource message.

16. The apparatus of claim 9, wherein the sensing buffer status report is transmitted via a physical uplink shared channel.

17. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one processor; and At least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the device to: A first control signaling instruction is sent to transmit radar sensing waveforms for radar sensing of one or more sensing parameters; The second control signaling is received at least in part based on the first control signaling indicating the one or more sensing parameters, the second control signaling indicating that the UE is scheduled to transmit the radar sensing waveform via multiple uplink shared channel timings; as well as The radar sensing waveform is transmitted based on one or more sensing parameters via one or more uplink shared channel timings among the plurality of uplink shared channel timings.

18. The apparatus of claim 17, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The radar sensing waveform is transmitted via one or more sensing parameters to indicate the field of view, the delay threshold, the beamwidth, the number of resources, the threshold resolution, or any combination thereof, wherein the transmission of the radar sensing waveform is based at least in part on a radar scanning process corresponding to one or more sensing parameters.

19. The apparatus of claim 17, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The radar sensing waveform is transmitted via one or more sensing parameters to indicate a beamwidth, a number of resources, a threshold range resolution, a threshold velocity resolution, or any combination thereof, wherein the transmission of the radar sensing waveform is at least partially based on a radar tracking process corresponding to the one or more sensing parameters.

20. The apparatus of claim 17, wherein the one or more sensing parameters comprise a first subset of parameters corresponding to a radar scanning process and a second subset of parameters corresponding to a radar tracking process.

21. The apparatus of claim 17, wherein the first control signaling includes a radio resource control message.

22. The apparatus of claim 17, wherein the second control signaling includes a radio resource control message, the radio resource control message including configuration permission.

23. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one processor; and At least one memory coupled to the at least one processor, the at least one memory storing instructions executable by the at least one processor to cause the device to: Receive control signaling indicating multiple radar sensing schemes, each radar sensing scheme corresponding to a set of sensing resources for radar sensing; Send a control message, the control message including a request to activate a first radar sensing scheme among the plurality of radar sensing schemes; Receive an acknowledgment message corresponding to the control message; as well as The radar sensing waveform is transmitted via a first resource corresponding to the first radar sensing scheme, at least in part based on the receipt of the confirmation message.

24. The apparatus of claim 23, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Instructions for one or more parameters corresponding to each respective set of sensing resources used for radar sensing are received via the plurality of radar sensing schemes.

25. The apparatus of claim 24, wherein the one or more parameters include time resource combs, frequency resource combs, bandwidth, start symbol, end symbol, periodicity, beam identifier, quasi-co-location indicator, or any combination thereof.

26. The apparatus of claim 23, wherein the control signaling includes radio resource control messages.

27. The apparatus of claim 23, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The control message is used to send an indication of the number of cycles for activating the first radar sensing scheme.

28. The apparatus of claim 23, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Receive control signaling indicating that the second radar sensing scheme is the default radar sensing scheme.

29. The apparatus of claim 28, wherein the instructions are further executable by the at least one processor to cause the apparatus to: The switching from the first radar sensing scheme to the second radar sensing scheme is based at least in part on the control signaling indicating that the second radar sensing scheme is the default radar sensing scheme when the time period associated with the first radar sensing scheme expires; and The second radar sensing waveform is transmitted via resources corresponding to the second radar sensing scheme, at least in part based on the switching.

30. The apparatus of claim 23, wherein the instructions are further executable by the at least one processor to cause the apparatus to: Receive control signaling indicating that the first radar sensing scheme is the default radar sensing scheme; It is determined that the UE has no radar sensing to perform during the second resource period corresponding to the first radar sensing scheme; as well as Control messages are sent at least in part based on control signaling indicating that the first radar sensing scheme is the default radar sensing scheme, the control messages instructing the UE not to send the second radar sensing waveform via the second resource corresponding to the first radar sensing scheme.

Images