Frequency modulated continuous wave (FMCW) for physical uplink control channel (PUCCH) and sensing

Abstract

Systems and techniques for wireless joint communication and sensing are disclosed. For example, a network device can receive from a network entity at least one configuration signal indicating at least one configuration, which includes a Physical Uplink Control Channel (PUCCH) for use with resources for sensing. The network device can output a PUCCH for transmission to a network entity based on the at least one configuration including resources. The network device can transmit sensing signals based on the at least one configuration including resources.

Description

Technical Field

[0001] This disclosure relates in its entirety to Joint Wireless Communications and Sensing (JCS). For example, aspects of this disclosure relate to reusing Frequency Modulated Continuous Wave (FMCW) for Physical Uplink Control Channel (PUCCH) and sensing. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. 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 or one or more network access nodes, each supporting communication for multiple communication devices simultaneously, which may also be referred to as User Equipment (UE). Some wireless communication systems can support communication between UEs, which may involve direct transmission between two or more UEs.

[0003] As greater bandwidth is allocated to wireless cellular communication systems (e.g., including 5G and above) and more use cases are being introduced into cellular communication systems, multiplexing sensing and communication signals for joint communication and sensing can be a fundamental feature of existing or future wireless communication systems to, for example, enhance the overall spectral efficiency of wireless communication networks. Summary of the Invention

[0004] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceived aspects, nor should it be considered to identify key or decisive elements relating to all conceived aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a simplified form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0005] Systems, apparatuses, methods, and computer-readable media for wireless communication and sensing (e.g., reusing FMCW for PUCCH and sensing) are disclosed. According to at least one example, a network device for wireless communication and sensing is provided. The network device includes at least one memory and at least one processor coupled to the at least one memory and configured to: receive from a network entity at least one configuration signal indicating at least one configuration, the at least one configuration including resources for a physical uplink control channel (PUCCH) and resources for sensing; output a PUCCH for transmission to the network entity based on the at least one configuration including resources; and output a sensing signal for transmission based on the at least one configuration including resources.

[0006] In another exemplary example, a method for performing wireless joint communication and sensing at a network device is provided. The method includes: receiving from a network entity at least one configuration signal indicating at least one configuration, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; transmitting the PUCCH to the network entity based on the at least one configuration including the resources; and transmitting a sensing signal based on the at least one configuration including the resources.

[0007] In another exemplary example, a non-transitory computer-readable medium is provided having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to: receive from a network entity at least one configuration signal indicating at least one configuration, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; output the PUCCH for transmission to the network entity based on the at least one configuration including the resources; and output a sensing signal for transmission based on the at least one configuration including the resources.

[0008] In another exemplary example, an apparatus for wireless communication and sensing is provided. The apparatus includes: components for receiving from a network entity at least one configuration signal indicating at least one configuration, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; components for transmitting the PUCCH to the network entity based on the at least one configuration including the resources; and components for transmitting a sensing signal based on the at least one configuration including the resources.

[0009] In another exemplary example, a network entity for wireless communication and sensing is provided. The network entity includes at least one memory and at least one processor coupled to the at least one memory and configured to: output at least one configuration signal indicating at least one configuration for transmission to a network device, the at least one configuration including resources for a Physical Uplink Control Channel (PUCCH); and receive the PUCCH from the network device based on the at least one configuration including the resources.

[0010] In another exemplary example, a method for performing wireless joint communication and sensing at a network device is provided. The method includes: sending to the network device at least one configuration signal indicating at least one configuration, the at least one configuration including a Physical Uplink Control Channel (PUCCH) and resources for sensing; and receiving the PUCCH from the network device based on the at least one configuration including the resources.

[0011] In another exemplary example, a non-transitory computer-readable medium is provided having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to: output at least one configuration signal indicating at least one configuration for transmission to a network device, the at least one configuration including resources for a physical uplink control channel (PUCCH); and receive the PUCCH from the network device based on the at least one configuration including the resources.

[0012] In another exemplary example, an apparatus for wireless communication and sensing is provided. The apparatus includes: components for transmitting to a network device at least one configuration signal indicating at least one configuration, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; and components for receiving the PUCCH from the network device based on the at least one configuration including the resources.

[0013] The aspects generally include, as described substantially with reference to the accompanying drawings and description and illustrated as shown in the drawings and description, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, user gear, wireless communication equipment, and / or processing systems.

[0014] In some aspects, one or more of the network device, apparatus, or other devices described herein are, are part of, and / or include: user equipment (UE), a base station (e.g., a gNodeB (gNB) or an eNodeB (eNB)) or a portion thereof (e.g., a central unit (CU), distributed unit (DU), radio unit (RU), near real-time (near RT) RAN intelligent controller (RIC), or non-real-time (non-RT) RIC of a base station). The UE may be a wearable device, an extended reality (XR) device (e.g., a virtual reality (VR) device, an augmented reality (AR) device, or a mixed reality (MR) device), a head-mounted display (HMD) device, a wireless communication device, a mobile device (e.g., a mobile phone and / or a mobile cell phone and / or a so-called "smartphone" or other mobile device), a camera, a personal computer, a laptop computer, a server computer, a vehicle, or a component of a computing device or vehicle, another device, or a combination thereof. In some aspects, one or more of the network device, apparatus, or other devices may include one or more cameras for capturing one or more images. In some examples, one or more of the network device, apparatus, or other equipment may also include a display for showing one or more images, notifications, and / or other displayable data. In some cases, one or more of the network device, apparatus, or other equipment may include one or more receivers, transmitters, or transceivers for receiving and / or transmitting wireless communications.

[0015] Some aspects include a device having a processor configured to perform one or more operations of any of the methods outlined above. Further aspects include a processing apparatus for use in the apparatus, configured using processor-executable instructions to perform operations of any of the methods outlined above. Further aspects include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon configured to cause the processor of the device to perform operations of any of the methods outlined above. Further aspects include a device having components for performing functions of any of the methods outlined above.

[0016] The features and technical advantages of the examples according to this disclosure have been summarized quite 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 operation) and their associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. The foregoing, as well as other features and aspects, will become more apparent upon reference to the following specification, claims, and appended drawings.

[0017] This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to define the scope of the claimed subject matter. This subject matter should be understood with reference to the appropriate portions of the entire specification, any or all drawings, and each claim. Attached Figure Description

[0018] The exemplary aspects of this application are described in detail below with reference to the following figures: Figure 1 This is a diagram illustrating an example wireless communication system that can be used by the disclosed system and technology for reusing frequency modulated continuous wave (FMCW) for PUCCH and sensing, according to some aspects of this disclosure.

[0019] Figure 2 This is a diagram illustrating an example of a decomposed base station architecture that can be adopted by the disclosed systems and techniques for reusing FMCW for PUCCH and sensing, according to some aspects of this disclosure.

[0020] Figure 3 This is a diagram illustrating an example of a frame structure that can be adopted by the disclosed system and technology for reusing FMCW for PUCCH and sensing, according to some aspects of this disclosure.

[0021] Figure 4 This is a block diagram illustrating examples of computing systems for electronic devices that can be used by systems and technologies disclosed for reusing FMCW for PUCCH and sensing, according to some aspects of this disclosure.

[0022] Figure 5 This is an illustration of an example of a wireless device utilizing radio frequency (RF) single-station sensing technology according to some aspects of this disclosure, which can be used by the systems and techniques disclosed herein to determine one or more characteristics of a target object.

[0023] Figure 6This is an illustration of an example of a receiver utilizing RF dual-station sensing technology with a transmitter, according to some aspects of this disclosure. This receiver can be used by the systems and techniques disclosed herein to determine one or more characteristics of a target object.

[0024] Figure 7 This is an illustration of an example of a receiver utilizing RF dual-station sensing technology with multiple transmitters, according to some aspects of this disclosure. This receiver can be used by the systems and techniques disclosed herein to determine one or more characteristics of a target object.

[0025] Figure 8 This is a diagram illustrating an example geometry for dual-station (or single-station) sensing according to some aspects of this disclosure.

[0026] Figure 9 This is a diagram illustrating bi-station distance sensing according to some aspects of this disclosure.

[0027] Figure 10 This is a diagram illustrating an example of symbol configuration for PUCCH format 1 according to some aspects of this disclosure.

[0028] Figure 11 This is a diagram illustrating examples of different use cases including PUCCH resources according to some aspects of this disclosure.

[0029] Figure 12 This is an illustration of examples of symbols with different slopes for FMCW according to some aspects of this disclosure.

[0030] Figure 13 The diagram illustrates examples of sequences with different symbol-level orthogonal overlay codes (OCCs) according to some aspects of this disclosure.

[0031] Figure 14 This is a diagram illustrating examples of symbols with different cyclic shifts according to some aspects of this disclosure.

[0032] Figure 15 This is an illustration of examples of symbols with different zero-tail lengths according to some aspects of this disclosure.

[0033] Figure 16 This is an illustration of examples of symbols with different triangular chirps according to some aspects of this disclosure.

[0034] Figure 17 This is an illustration of an example system for reusing FMCW for PUCCH and sensing, according to some aspects of this disclosure, where the system is performing single-station sensing.

[0035] Figure 18This is an illustration of an example system for reusing FMCW for PUCCH and sensing according to some aspects of this disclosure, wherein the system is performing dual-station sensing.

[0036] Figure 19 This is a flowchart illustrating an example of a process for reusing FMCW for PUCCH and sensing performed at a network device, according to some aspects of this disclosure.

[0037] Figure 20 This is a flowchart illustrating an example of a process for reusing FMCW for PUCCH and sensing performed at a network entity, according to some aspects of this disclosure.

[0038] Figure 21 This is a diagram illustrating examples of systems for implementing certain aspects of the present disclosure. Detailed Implementation

[0039] Certain aspects of this disclosure are provided below for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Additionally, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure. Some aspects described herein can be applied independently, and some of them can be combined, as will be apparent to those skilled in the art. In the following description, specific details are set forth for illustrative purposes to provide a thorough understanding of various aspects of this application. However, it will be apparent that various aspects can be practiced without these specific details. The figures and descriptions are not intended to be limiting.

[0040] The following description provides only exemplary aspects and is not intended to limit the scope, applicability, or configuration of this disclosure. Rather, the following description of the exemplary aspects will provide those skilled in the art with a description that can be used to implement the exemplary aspects. It should be understood that various changes may be made to the function and arrangement of the elements without departing from the spirit and scope of this application as set forth in the appended claims.

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

[0042] Radar sensing systems use radio frequency (RF) waveforms to perform RF sensing to determine or estimate one or more characteristics of a target object, such as the target object's distance (e.g., to the device performing the RF sensing), angle (e.g., relative to the device performing the RF sensing), and / or velocity. Target objects may include vehicles, obstacles, users, buildings, or other objects. A typical radar system includes at least one transmitter, at least one receiver, and at least one processor. When using a receiver co-located with the transmitter, the radar sensing system can perform monostation sensing. When using a receiver for a first device located away from a transmitter located away from a second device, the radar system can perform bistation sensing. Similarly, when using multiple receivers for multiple devices located away from at least one transmitter located away from at least one device, the radar system can perform multistation sensing.

[0043] During the operation of a radar sensing system, a transmitter sends an electromagnetic (EM) signal in the RF domain toward a target object. The signal is reflected from the target object to generate one or more reflected signals, which provide information or attributes about the target, such as the target object's position and velocity. At least one receiver receives the one or more reflected signals, and at least one processor associated with at least one receiver can use the information from the one or more reflected signals to determine information or attributes of the target object. The target object may also be referred to herein as a target.

[0044] Generally speaking, RF sensing involves monitoring moving targets with different motions (e.g., moving cars or pedestrians, human body movements such as breathing, and / or other micro-motions associated with the target). Measuring the phase change in the signal and indicating motion using Doppler is an important characteristic for sensing targets.

[0045] In some cases, radar sensing signals, which may be referred to as radar reference signals (RS) (such as sensing reference signals (S-RS)), can be designed for and used for sensing purposes. Radar RSs do not contain any communication information. In contrast, communication RSs (such as demodulation reference signals (DMRS)) are typically designed for and used solely for communication purposes, such as estimating channel parameters for communication.

[0046] Cellular communication systems are designed to transmit communication signals on designated communication frequency bands (e.g., 23 GHz, 3.5 GHz, etc. for 5G / NR, 2.2 GHz, etc. for LTE). RF sensing systems are designed to transmit RF sensing signals on designated radar RF frequency bands (e.g., 77 GHz for autonomous driving). In future cellular communication systems, it is likely that spectrum used for communication and sensing will be shared; in such cases, communication and sensing should be considered jointly.

[0047] In some cases, due to the allocation of larger bandwidths for wireless communication systems (including cellular communication systems such as 4G / LTE, 5G / NR and above) and the introduction of more use cases into wireless communication systems, multiplexing (e.g., via time division multiplexing and / or frequency division multiplexing) sensing and communication signals for joint communication and sensing can be a fundamental feature for existing and future wireless communication systems (e.g., 6G). Simultaneously performing wireless communication and radar sensing can provide cost-effective deployment for both radar and communication systems.

[0048] Joint communication and radar sensing can provide mutual performance gains. For example, sensing information such as Doppler measurements can be used to improve the quality of communication links (e.g., sensing-assisted communication). Furthermore, cooperative sensing may be more feasible for wireless communication networks (e.g., communication-assisted sensing).

[0049] For joint communication and radar sensing, a radar system can be employed that transmits detection signals to non-cooperative targets (e.g., objects) and infers useful information contained in the target echo (e.g., signals reflected from detected targets). A communication system capable of exchanging information between two or more cooperating transceivers (e.g., UEs) can also be used. Joint communication and sensing utilizes an integrated system that simultaneously performs both wireless communication and long-range radar sensing, providing cost-effective deployment for both radar and communication systems. Time, frequency, and / or spatial radio resources can be allocated within the integrated system to support both communication and sensing objectives.

[0050] In 5G NR, the Physical Uplink Control Channel (PUCCH) is the uplink physical channel that carries uplink control information (UCI). UCI includes Hybrid Automatic Repeat Request (HARQ) feedback, Channel State Information (CSI), and Scheduling Request (SR). There are five different PUCCH formats, and the format used is determined by the number of bits of information to be carried and the number of symbols assigned. NR PUCCH is flexible in its time and frequency allocation, which allows for support of UEs with limited bandwidth capabilities on NR carriers and allows for efficient use of available resources for coverage and capacity. Network devices (e.g., UEs) can be configured with PUCCH resources for CSI reporting or SR. For UCI transmissions including HARQ-ACK bits, network devices (e.g., UEs) can be configured with up to four PUCCH resource sets based on the UCI size.

[0051] The NR PUCCH design is based on five PUCCH formats. PUCCH formats 0 and 2 (which may be referred to as short PUCCH) use one or two Orthogonal Frequency Division Multiplexing (OFDM) symbols. PUCCH formats 1, 3, and 4 (which may be referred to as long PUCCH) use 4 to 14 OFDM symbols. PUCCH formats 0 and 1 carry one or two bits of UCI payload, while the other formats are used to carry more than two bits of UCI payload. In PUCCH formats 1, 3, and 4, symbols with DMRS are time-division multiplexed with UCI symbols to maintain a low peak-to-average power ratio (PAPR). In PUCCH format 2, DMRS is frequency-multiplexed with the data-carrying subcarrier. When applicable, multi-user multiplexing on the same time and frequency resources is supported only for PUCCH formats 0, 1, and 4 by means of different cyclic shifts or orthogonal code overlays (OCC).

[0052] In current 5G NR PUCCH formats 0 and 1, only one or two bits are carried in the UCI. PUCCH format 0 is a short PUCCH and is based on sequence selection, while PUCCH format 1 is a long PUCCH and has UCI and DMRS time multiplexing. Technologies that allow resources to be used for both PUCCH and sensing (e.g., for joint communication and sensing) may be beneficial.

[0053] In some aspects of this disclosure, systems, apparatuses, methods (also referred to as processes), and computer-readable media (collectively referred to herein as "systems and techniques") are described to provide solutions for reusing frequency-modulated continuous wave (FMCW) for PUCCH and sensing. FMCW is a waveform of a transmitted signal that varies continuously at a known rate over a defined time period. These systems and techniques may include using FMCW as a base sequence for PUCCH for wireless communication (e.g., 5G communication, 6G communication, etc.) while also reusing FMCW for sensing purposes. In some aspects, network entities (e.g., base stations or network servers) may configure the same resources for both PUCCH (e.g., PUCCH transmission) and sensing (e.g., monostation sensing or bistation sensing) to network devices (e.g., UEs).

[0054] In one or more examples, during operations for reusing FMCW for PUCCH and sensing, a network device (e.g., a UE) may receive a configuration signal from a network entity (e.g., a base station or network server) indicating a configuration including resources for PUCCH and sensing. The network device may send PUCCH to the network entity based on these resources. The network device may send sensing signals toward an object based on these resources. In one or more examples, these resources may include FMCW. In some examples, FMCW may be used as a base sequence for PUCCH.

[0055] In some examples, during operations for reusing FMCW for PUCCH and sensing, a network entity (e.g., a base station or network server) may send a configuration signal to a network device (e.g., a UE) indicating a configuration that includes resources for PUCCH and sensing. The network entity may then receive PUCCH from the network device based on these resources.

[0056] Additional aspects of this disclosure are described in more detail below.

[0057] As used herein, the terms “User Equipment” (UE) and “Network Entity” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise specified. In general, a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, and / or tracking device, etc.), wearable device (e.g., smartwatch, smart glasses, wearable ring, and / or extended reality (XR) device (such as virtual reality (VR) headset, augmented reality (AR) headset or glasses, or mixed reality (MR) headset)), vehicle (e.g., car, motorcycle, bicycle, etc.), and / or Internet of Things (IoT) device, etc., for a user to communicate over a wireless communication network. A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term "UE" may be interchangeably referred to as "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal," or "UT," "mobile device," "mobile terminal," "mobile station," or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the IEEE 802.11 communication standard), etc.

[0058] Network entities can be implemented in a converged or monolithic base station architecture, or alternatively, in a decomposed base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. A base station (e.g., with a converged / monolithic or decomposed base station architecture) may operate according to one of several RATs communicating with the UE (depending on the network in which it is deployed), and may alternatively be referred to as an access point (AP), network node, NodeB (NB), evolved NodeB (eNB), next-generation eNB (ng-eNB), new radio (NR) NodeB (also known as gNB or gNodeB), etc. The base station may primarily be used to support the UE's radio access, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication links through which a UE can transmit signals to a base station are called uplink (UL) channels (e.g., reverse traffic channels, reverse control channels, access channels, etc.). The communication links through which a base station can transmit signals to a UE are called downlink (DL) or forward link channels (e.g., paging channels, control channels, broadcast channels, or forward traffic channels, etc.). As used herein, the term traffic channel (TCH) can refer to uplink, reverse or downlink, and / or forward traffic channel.

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

[0060] In some specific implementations supporting UE positioning, network entities or base stations may not support the UE's radio access (e.g., may not support data, voice, and / or signaling connections regarding the UE), but instead may transmit reference signals to the UE for measurement, and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

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

[0062] According to various aspects, Figure 1An exemplary wireless communication system 100 is illustrated, which can be adopted by the systems and technologies disclosed herein for reusing FMCW for PUCCH and sensing. The wireless communication system 100 (also referred to as a Wireless Wide Area Network (WWAN)) may include individual base stations 102 and individual UEs 104. In some aspects, base station 102 may also be referred to as a “network entity” or a “network node.” One or more of base stations 102 may be implemented in an aggregated or monolithic base station architecture. Additionally or alternatively, one or more of base stations 102 may be implemented in a decomposed base station architecture and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. Base station 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, a macro cell base station may include an eNB and / or an ng-eNB (where the wireless communication system 100 corresponds to a Long Term Evolution (LTE) network), or a gNB (where the wireless communication system 100 corresponds to an NR network), or a combination of both, and a small cell base station may include femtocells, picocells, microcells, etc.

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

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

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

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

[0067] The wireless communication system 100 may also include a WLAN AP 150 communicating with a WLAN station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a Free Channel Assessment (CCA) or Listen-After-Talk (LBT) process before communication to determine if the channel is available. In some examples, the wireless communication system 100 may include devices (e.g., UEs, etc.) that communicate with one or more UEs 104, base stations 102, APs 150, etc., using ultra-wideband (UWB) spectrum. The UWB spectrum can range from 3.1 GHz to 10.5 GHz.

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

[0069] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with the UE 182. The mmW base station 180 may be implemented in a converged or monolithic base station architecture, or alternatively, in a decomposed base station architecture (e.g., including one or more of a CU, DU, RU, near-RT RIC, or non-RT RIC). Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band can be referred to as millimeter waves. Near-mmW extends down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW and / or near-mmW radio bands has high path loss and relatively short range. mmW base station 180 and UE 182 can utilize beamforming (transmit and / or receive) on mmW communication link 184 to compensate for extremely high path loss and short range. Furthermore, it should be understood that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

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

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

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

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

[0074] It should be noted that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if a network node or entity (e.g., a base station) is forming a downlink beam to transmit a reference signal to the UE, then the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, then the downlink beam is a receive beam for receiving downlink reference signals. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if a network node or entity (e.g., a base station) is forming an uplink beam, then the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, then the uplink beam is an uplink transmit beam.

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

[0076] For example, still refer to Figure 1 One of the frequencies used by macro cell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macro cell base station 102 and / or mmW base station 180 may be secondary carriers ("SCell"). In carrier aggregation, base station 102 and / or UE 104 may use up to [number missing] frequencies per carrier. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz), having up to a total of [number missing] in each direction. Yx MHz ( x(Multiple component carriers) are used for transmission. Component carriers may or may not be adjacent to each other in the spectrum. Carrier allocation may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink). Simultaneous transmission and / or reception on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two aggregated 20MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40MHz) compared to the data rate obtained by a single 20MHz carrier.

[0077] To operate on multiple carrier frequencies, base station 102 and / or UE 104 are equipped with multiple receivers and / or transmitters. For example, UE 104 may have two receivers, namely "Receiver 1" and "Receiver 2", where "Receiver 1" is a multi-band receiver that can be tuned to band "X" or band "Y", while "Receiver 2" is a single-band receiver that can be tuned to only band "Z". In this example, if UE 104 is being served in band "X", then band "X" will be referred to as PCell or active carrier frequency, and "Receiver 1" will need to tune from band "X" to band "Y" (SCell) to measure band "Y" (and vice versa). In contrast, regardless of whether UE 104 is being served in band "X" or band "Y", because "Receiver 2" is separate, UE 104 can measure band "Z" without interrupting service on band "X" or band "Y".

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

[0079] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1In one example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this D2D P2P link), and has a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, any well-known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct (Wi-Fi-D), Bluetooth) can be used. ® (etc.) to support D2D P2P links 192 and 194. As mentioned above, UE 104 and UE 190 can be configured to communicate using sidelink communication. In some cases, sidelink transmission may include requests for feedback from the receiving UE (e.g., Hybrid Automatic Repeat Request (HARQ)).

[0080] Figure 2 This is an illustration of an example of a decomposed base station architecture that can be adopted by the disclosed systems and technologies for reusing FMCW for PUCCH and sensing. The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a NodeB (NB), evolved NB (eNB), NR BS, 5G NB, AP, transmit / receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a decomposed base station.

[0081] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0082] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units in a decomposed base station or decomposed RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0083] As mentioned earlier, Figure 2 A diagram illustrating an example decomposed base station 201 architecture is shown. The decomposed base station 201 architecture may include one or more central units (CUs) 211, which may communicate directly with the core network 223 via a backhaul link, or indirectly with the core network 223 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 227 via an E2 link, or a non-real-time (non-RT) RIC 217 associated with a Service Management and Orchestration (SMO) framework 207, or both. CUs 211 may communicate with one or more distributed units (DUs) 231 via corresponding midhaul links (such as F1 interfaces). DUs 231 may communicate with one or more radio units (RUs) 241 via corresponding fronthaul links. RUs 241 may communicate with corresponding UEs 221 via one or more RF access links. In some implementations, a UE 221 may be served simultaneously by multiple RUs 241.

[0084] Each unit in the cells (i.e., CU 211, DU 231, RU 241, and near-RT RIC 227, non-RT RIC 217, and SMO frame 207) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cells, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive or transmit signals, or both, to one or more other units over a wireless transmission medium.

[0085] In some aspects, CU 211 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 211. CU 211 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, CU 211 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 211 can be implemented to communicate with DU 231 for network control and signaling, as needed.

[0086] DU 231 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 241s. In some aspects, DU 231 may at least partially host one or more of the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 231 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 231 or with control functions hosted by CU 211.

[0087] Lower-layer functionality can be implemented by one or more RU 241s. In some deployments, the RU 241 controlled by the DU 231 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 241 may be implemented to handle over-the-air (OTA) communications with one or more UE 221s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 241 may be controlled by the corresponding DU 231. In some scenarios, this configuration enables the implementation of the DU 231 and CU 211 in cloud-based RAN architectures (such as vRAN architectures).

[0088] SMO framework 207 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 207 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 207 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 291 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 211, DU 231, RU 241, and near-RT RIC 227. In some implementations, SMO framework 207 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 213) via the O1 interface. Additionally, in some implementations, SMO framework 207 can communicate directly with one or more RU 241s via the O1 interface. SMO framework 207 may also include a non-RT RIC 217 configured to support the functionality of SMO framework 207.

[0089] The non-RT RIC 217 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 227. The non-RT RIC 217 can be coupled to or communicate with the near-RT RIC 227, such as via an A1 interface. The near-RT RIC 227 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and action, connecting one or more CUs 211, one or more DUs 231, or both, and an O-eNB 213 to the near-RT RIC 227.

[0090] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 227, the non-RT RIC 217 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 227 and can be received from non-network data sources or network functions at the SMO framework 207 or the non-RT RIC 217. In some examples, the non-RT RIC 217 or the near-RT RIC 227 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 217 may monitor long-term trends and patterns in performance and use AI / ML models to perform corrective actions via the SMO framework 207 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0091] Various radio frame structures can be used to support downlink transmission, uplink transmission, and sidelink transmission between network nodes (e.g., base stations and UEs). Figure 3 Figure 300 illustrates an example of a frame structure that may be employed by the disclosed systems and techniques for reusing FMCW for PUCCH and sensing. Other wireless communication techniques may have different frame structures and / or different channels.

[0092] NR (and LTE) utilize OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option to use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, often referred to as tones, frequency slots, etc. Each subcarrier can be modulated using data. Generally, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing could be 15 kHz, and the minimum resource allocation (resource block) could be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

[0093] LTE supports a single set of parameters (subcarrier spacing, symbol length, etc.). In contrast, NR can support multiple sets of parameters (µ). For example, subcarrier spacings (SCS) of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz or greater can be available. Table 1 below lists some of the different parameters for different NR parameter sets.

[0094]

[0095] Table 1

[0096] In one example, a parameter set of 15kHz is used. Therefore, in the time domain, a 10-millisecond (ms) frame is divided into 10 equal-sized subframes, each 1ms, and each subframe includes one time slot. Figure 3 In this context, time is represented in the horizontal direction (e.g., on the X-axis), where time increases from left to right, while frequency is represented in the vertical direction (e.g., on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0097] A resource grid can be used to represent time slots, each of which includes one or more time-concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. Figure 3 An example of a resource block (RB) 302 is shown. Data or information used for joint communication and sensing can be included in one or more RBs 302. RBs 302 are arranged by placing the time domain on the horizontal (or x) axis and the frequency domain on the vertical (or y) axis. As shown, an RB 302 can be a frequency wide of 180 kHz and a time slot long (where a time slot is 1 millisecond (ms)). In some cases, a time slot may include fourteen symbols (e.g., in time slot configuration 0). RB 302 includes twelve subcarriers (along the y-axis) and fourteen symbols (along the x-axis).

[0098] The intersection of symbols and subcarriers can be referred to as resource element (RE) 304 or tone. Figure 3 RB 302 includes multiple REs, each of which includes a resource element (RE) 304. For example, RE 304 is one subcarrier × one symbol (e.g., an OFDM symbol) and is the smallest discrete part of a subframe. RE 304 includes a single complex value representing data from a physical channel or signal. The number of bits carried by each RE 304 depends on the modulation scheme.

[0099] In some respects, some RE 304s can be used to transmit downlink reference (pilot) signals (DL-RS). DL-RS may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), etc. Figure 3 The resource grid example illustrates an exemplary location (labeled "R") for sending DL-RS on RE 304.

[0100] Figure 4 This is a block diagram illustrating an example of a computing system 470 that may be employed by electronic device 407 for reusing FMCW for PUCCH and sensing systems and technologies disclosed herein. Electronic device 407 is an example of a device that may include hardware and software for connecting and exchanging data with other devices and systems using communication networks, such as 3rd generation partner networks, 5th generation (5G) / New Radio (NR) networks, 4th generation (4G) / Long Term Evolution (LTE) networks, Wi-Fi networks, or other communication networks. For example, electronic device 407 may include or be part of: mobile devices (e.g., mobile phones), wearable devices (e.g., network-connected or smartwatches), extended reality devices (e.g., virtual reality (VR) devices, augmented reality (AR) devices, or mixed reality (MR) devices), personal computers, laptop computers, tablet computers, Internet of Things (IoT) devices, wireless access points, routers, vehicles or components of vehicles, server computers, robotic devices, and / or other devices used by users to communicate on wireless communication networks. In some cases, such as when referring to a device configured to communicate using 5G / NR, 4G / LTE, or other telecommunications standards, device 407 may be referred to as User Equipment (UE). In some cases, such as when referring to a device configured to communicate using Wi-Fi standards, the device may be referred to as a Station (STA).

[0101] The computing system 470 includes software and hardware components that can be electrically coupled or communicatively coupled (or otherwise communicated, as applicable) via a bus 489. For example, the computing system 470 includes one or more processors 484. The one or more processors 484 may include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, dedicated hardware, any combination thereof, and / or other processing devices and / or systems. The bus 489 may be used by the one or more processors 484 to communicate between cores and / or with one or more memory devices 486.

[0102] The computing system 470 may also include one or more memory devices 486, one or more digital signal processors (DSPs) 482, one or more subscriber identity modules (SIMs) 474, one or more modems 476, one or more wireless transceivers 478, one or more antennas 487, one or more input devices 472 (e.g., camera, mouse, keyboard, touchscreen, touchpad, keypad, microphone or microphone array, etc.) and one or more output devices 480 (e.g., display, speaker, printer, etc.).

[0103] One or more wireless transceivers 478 may receive wireless signals (e.g., signal 488) from one or more other devices (such as other user equipment, network devices (e.g., base stations such as evolved Node Bs (eNBs) and / or gNode Bs (gNBs), WiFi access points (APs) such as routers, range extenders) and / or cloud networks, etc.) via antenna 487. In some examples, computing system 470 may include multiple antennas or antenna arrays that facilitate simultaneous transmission and reception functionality. Antenna 487 may be an omnidirectional antenna, enabling the reception and transmission of RF signals from all directions. Wireless signal 488 may be transmitted via a wireless network. The wireless network may be any wireless network, such as a cellular or telecommunications network (e.g., 3G, 4G, 5G, etc.), a wireless local area network (e.g., a Wi-Fi network), or Bluetooth. ™ Networks and / or other networks. In some examples, one or more wireless transceivers 478 may include an RF front end, which includes one or more components such as amplifiers, a mixer for down-converting signals (also known as a signal multiplier), a frequency synthesizer (also known as an oscillator) that supplies signals to the mixer, a baseband filter, an analog-to-digital converter (ADC), one or more power amplifiers, and other components. The RF front end generally handles the selection of the wireless signal 488 and the conversion of the wireless signal to baseband or intermediate frequency, and can convert the RF signal to the digital domain.

[0104] In some cases, computing system 470 may include a decoder-decoder (or CODEC) configured to encode and / or decode data transmitted and / or received using one or more wireless transceivers 478. In some cases, computing system 470 may include an encryption-decryption device or component configured to encrypt and / or decrypt data transmitted and / or received by one or more wireless transceivers 478 (e.g., according to Advanced Encryption Standard (AES) and / or Data Encryption Standard (DES) standards).

[0105] One or more SIMs 474 may each securely store an International Mobile Subscriber Identity (IMSI) number and associated key assigned to a user of electronic device 407. The IMSI and key can be used to identify and authenticate the subscriber when accessing a network provided by a network service provider or operator associated with one or more SIMs 474. One or more modems 476 may modulate one or more signals to encode information to be transmitted using one or more wireless transceivers 478. One or more modems 476 may also demodulate signals received by one or more wireless transceivers 478 to decode the transmitted information. In some examples, one or more modems 476 may include a WiFi modem, a 4G (or LTE) modem, a 5G (or NR) modem, and / or other types of modems. One or more modems 476 and one or more wireless transceivers 478 may be used to transmit data from one or more SIMs 474.

[0106] The computing system 470 may also include one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 486) (and / or communicate with them), which may include, but are not limited to, local and / or network-accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as RAM and / or ROM), which may be programmable, flash-updatable, and / or the like. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems and / or database structures.

[0107] In various aspects, functionality may be stored in memory device 486 as one or more computer program products (e.g., instructions or code) and executed by one or more processors 484 and / or one or more DSPs 482. Computing system 470 may also include software elements (e.g., residing within one or more memory devices 486) including, for example, operating systems, device drivers, executable libraries, and / or other code, such as one or more application programs, which may include computer programs implementing the functionality provided by various aspects, and / or may be designed to implement methods and / or configure systems as described herein.

[0108] In some aspects, electronic device 407 may include components for performing the operations described herein. These components may include one or more components of computing system 470. For example, components for performing the operations described herein may include one or more of input device 472, SIM 474, modem 476, wireless transceiver 478, output device 480, DSP 482, processor 484, memory device 486, and / or antenna 487.

[0109] In some aspects, electronic device 407 may include components for providing joint communication and sensing, as well as components for reusing FMCW for PUCCH and sensing. In some examples, any or all of these components may include one or more wireless transceivers 478, one or more modems 476, one or more processors 484, one or more DSPs 482, one or more memory devices 486, any combination thereof, or other components of electronic device 407.

[0110] Figure 5 This is an illustration of an example of a wireless device 500 utilizing RF monostation sensing technology to determine one or more characteristics (e.g., position, rate or velocity, heading, etc.) of a target object 502. Specifically, Figure 5 This is an illustration of an example of a wireless device 500 (e.g., a transmitting / receiving sensing node) that utilizes RF sensing technology (e.g., single-site sensing) to perform one or more functions, such as detecting the presence and location of a target 502 (e.g., an object, a user, or a vehicle), which is illustrated in the figure as a vehicle.

[0111] In some examples, the wireless device 500 may be a mobile phone, tablet computer, wearable device, vehicle, extended reality (XR) device, computing device, or component of a vehicle, or other device including at least one RF interface (e.g., Figure 4 Device 407). In some examples, wireless device 500 may be a user device (e.g., for...). Figure 4 Electronic devices (407) that provide connectivity, such as base stations (e.g., gNB, eNB, etc.), wireless access points (APs), or other devices that include at least one RF interface.

[0112] In some aspects, the wireless device 500 may include one or more components for transmitting RF signals. The wireless device 500 may include at least one processor 522 for generating digital signals or waveforms. The wireless device 500 may also include a digital-to-analog converter (DAC) 504 capable of receiving digital signals or waveforms from the processor 522 (e.g., a microprocessor) and converting those digital signals or waveforms into analog waveforms. Analog signals, as the output of the DAC 504, may be provided to the RF transmitter 506 for transmission. The RF transmitter 506 may be a Wi-Fi transmitter, a 5G / NR transmitter, or a Bluetooth transmitter. ™ A transmitter or any other transmitter capable of transmitting RF signals.

[0113] RF transmitter 506 may be coupled to one or more transmitting antennas, such as Tx antenna 512. In some examples, transmitting (Tx) antenna 512 may be an omnidirectional antenna capable of transmitting RF signals in all directions. For example, Tx antenna 512 may be an omnidirectional Wi-Fi antenna capable of radiating Wi-Fi signals in a 360-degree radiation pattern (e.g., 2.4 GHz, 5 GHz, 6 GHz, etc.). In another example, Tx antenna 512 may be a directional antenna that transmits RF signals in a specific direction.

[0114] In some examples, the wireless device 500 may also include one or more components for receiving RF signals. For example, the receiver array in the wireless device 500 may include one or more receiving antennas, such as a receive (Rx) antenna 514. In some examples, the Rx antenna 514 may be an omnidirectional antenna capable of receiving RF signals from multiple directions. In other examples, the Rx antenna 514 may be a directional antenna configured to receive signals from a specific direction. In further examples, the Tx antenna 512 and / or the Rx antenna 514 may include multiple antennas (e.g., elements) configured as an antenna array (e.g., a phased antenna array).

[0115] The wireless device 500 may also include an RF receiver 510 coupled to the Rx antenna 514. The RF receiver 510 may include features for receiving signals such as Wi-Fi and Bluetooth. ™ One or more hardware components that represent an RF waveform, such as a signal, a 5G / NR signal, or any other RF signal. The output of the RF receiver 510 can be coupled to an analog-to-digital converter (ADC) 508. The ADC 508 can be configured to convert the received analog RF waveform into a digital waveform. The digital waveform, as the output of the ADC 508, can be provided to a processor 522 for processing. The processor 522 (e.g., a digital signal processor (DSP)) can be configured to process the digital waveform.

[0116] In one example, wireless device 500 may implement RF sensing technology, such as monostation sensing technology, by transmitting a Tx waveform 516 from Tx antenna 512. Although Tx waveform 516 is illustrated as a single line, in some cases, Tx waveform 516 may be transmitted in all directions by omnidirectional Tx antenna 512. In one example, Tx waveform 516 may be a Wi-Fi waveform transmitted by a Wi-Fi transmitter in wireless device 500. In some cases, Tx waveform 516 may correspond to a Wi-Fi waveform transmitted simultaneously or nearly simultaneously with a Wi-Fi data communication signal or a Wi-Fi control function signal (e.g., beacon transmission). In some examples, Tx waveform 516 may be transmitted using the same or similar frequency resources as the Wi-Fi data communication signal or the Wi-Fi control function signal (e.g., beacon transmission). In some aspects, Tx waveform 516 may correspond to a Wi-Fi waveform transmitted separately from the Wi-Fi data communication signal and / or the Wi-Fi control signal (e.g., Tx waveform 516 may be transmitted at different times and / or using different frequency resources).

[0117] In some examples, the Tx waveform 516 may correspond to a 5G NR waveform transmitted simultaneously or nearly simultaneously with the 5G NR data communication signal or the 5G NR control function signal. In some examples, the Tx waveform 516 may be transmitted using the same or similar frequency resources as the 5G NR data communication signal or the 5G NR control function signal. In some aspects, the Tx waveform 516 may correspond to a 5G NR waveform transmitted separately from the 5G NR data communication signal and / or the 5G NR control signal (e.g., the Tx waveform 516 may be transmitted at different times and / or using different frequency resources).

[0118] In some respects, one or more parameters associated with the Tx waveform 516 can be modified, which can be used to increase or decrease the RF sensing resolution. These parameters may include frequency, bandwidth, number of spatial streams, number of antennas configured to transmit the Tx waveform 516, number of antennas configured to receive reflected RF signals (e.g., Rx waveform 518) corresponding to the Tx waveform 516, number of spatial links (e.g., the number of spatial streams multiplied by the number of antennas configured to receive RF signals), sampling rate, or any combination thereof. The transmitted waveform (e.g., Tx waveform 516) and the received waveform (e.g., Rx waveform 518) may include one or more RF sensing signals, which are also referred to as radar reference signals (RS).

[0119] In another example, the Tx waveform 516 can be implemented as a sequence with perfect or near-perfect autocorrelation properties. For example, the Tx waveform 516 may include a single-carrier Zadoff sequence or may include symbols similar to those in Orthogonal Frequency Division Multiplexing (OFDM) Long Training Field (LTF) symbols. In some cases, the Tx waveform 516 may include a chirped signal, such as that used in frequency-modulated continuous wave (FM-CW) radar systems. In some configurations, the chirped signal may include a signal in which the signal frequency increases and / or decreases periodically in a linear and / or exponential manner.

[0120] In some aspects, the wireless device 500 can implement RF sensing technology by performing alternating transmit and receive functions (e.g., performing half-duplex operation). For example, the wireless device 500 can alternately enable its RF transmitter 506 to transmit a Tx waveform 516 when the RF receiver 510 is not enabled to receive (i.e., not receiving), and enable its RF receiver 510 to receive an Rx waveform 518 when the RF transmitter 506 is not enabled to transmit (i.e., not transmitting). When the wireless device 500 performs half-duplex operation, the wireless device 500 can transmit the Tx waveform 516, which can be a radar RS (e.g., a sensing signal).

[0121] In other respects, the wireless device 500 can implement RF sensing technology by performing concurrent transmit and receive functions (e.g., performing subband or full-band full-duplex operation). For example, the wireless device 500 can enable its RF receiver 510 to receive while its RF transmitter 506 is enabled to transmit a Tx waveform 516, or nearly simultaneously. When the wireless device 500 performs full-duplex operation (e.g., subband full-duplex or full-band full-duplex), the wireless device 500 can transmit the Tx waveform 516, which can be a radar RS (e.g., a sensing signal).

[0122] In some examples, the sequence or pattern included in the Tx waveform 516 may be transmitted repeatedly, such that the sequence is transmitted a specific number of times or for a specific duration. In some examples, if the RF receiver 510 is enabled after the RF transmitter 506, the repeated pattern in the transmission of the Tx waveform 516 can be used to avoid missing the reception of any reflected signals. In one example implementation, the Tx waveform 516 may include a sequence of length L that is transmitted two or more times, which may allow the RF receiver 510 to be enabled for a time less than or equal to L in order to receive reflections corresponding to the entire sequence without losing any information.

[0123] By implementing alternating or simultaneous transmit and receive functionality (e.g., half-duplex or full-duplex operation), wireless device 500 can receive signals corresponding to Tx waveform 516. For example, wireless device 500 can receive signals reflected from objects or people within the range of Tx waveform 516, such as Rx waveform 518 reflected from target 502. Wireless device 500 can also receive leaky signals (e.g., Tx leaky signal 520) coupled directly from Tx antenna 512 to Rx antenna 514 without reflection from any object. For example, the leaky signal may include signals transmitted from the transmitter antenna (e.g., Tx antenna 512) on the wireless device to the receiver antenna (e.g., Rx antenna 514) on the wireless device without reflection from any object. In some cases, Rx waveform 518 may include multiple sequences corresponding to multiple copies of the sequence included in Tx waveform 516. In some examples, wireless device 500 may combine multiple sequences received by RF receiver 510 to improve signal-to-noise ratio (SNR).

[0124] The wireless device 500 can also implement RF sensing technology by acquiring RF sensing data associated with each of the received signals corresponding to the Tx waveform 516. In some examples, the RF sensing data may include channel state information (CSI) data associated with the direct path of the Tx waveform 516 (e.g., leaky signal 520) and data associated with the reflection path corresponding to the Tx waveform 516 (e.g., Rx waveform 518).

[0125] In some aspects, RF sensing data (e.g., CSI data) may include information that can be used to determine how an RF signal (e.g., Tx waveform 516) propagates from RF transmitter 506 to RF receiver 510. RF sensing data may include data corresponding to the effects on the transmitted RF signal due to scattering, decay, and / or power attenuation with distance, or any combination thereof. In some examples, RF sensing data may include imaginary and real data (e.g., I / Q components) corresponding to each tone in the frequency domain over a specific bandwidth.

[0126] In some examples, the RF sensing data can be used by processor 522 to calculate the distance and angle of arrival corresponding to the reflected waveform (such as Rx waveform 518). In other examples, the RF sensing data can also be used to detect motion, determine location, detect changes in location or motion patterns, or any combination thereof. In some cases, the distance and angle of arrival of the reflected signal can be used to identify the size, location, movement, and / or orientation of a target in the surrounding environment (e.g., target 502) in order to detect the presence / proximity of the target.

[0127] The processor 522 of the wireless device 500 can calculate the distance and angle of arrival corresponding to the reflected waveform (e.g., the distance and angle of arrival corresponding to the Rx waveform 518) by utilizing signal processing, machine learning algorithms, any other suitable techniques, or any combination thereof. In other examples, the wireless device 500 can send or transmit RF sensing data to at least one processor of another computing device, such as a server or base station, which can perform calculations to obtain the distance and angle of arrival corresponding to the Rx waveform 518 or other reflected waveforms.

[0128] In one example, the distance of Rx waveform 518 can be calculated by measuring the time difference from receiving the leaked signal to receiving the reflected signal. For example, wireless device 500 can determine a baseline distance based on a zero difference between the time wireless device 500 transmits Tx waveform 516 and the time it receives the leaked signal 520 (e.g., propagation delay). The processor 522 of wireless device 500 can then determine the distance associated with Rx waveform 518 based on the difference between the time wireless device 500 transmits Tx waveform 516 and the time it receives Rx waveform 518 (e.g., time of flight, also known as round-trip time (RTT)), and can then adjust that distance according to the propagation delay associated with the leaked signal 520. By doing so, the processor 522 of wireless device 500 can determine the distance traveled by Rx waveform 518, which can be used to determine the presence and movement of a target (e.g., target 502) that caused the reflection.

[0129] In another example, the processor 522 can calculate the angle of arrival of the Rx waveform 518 by measuring the time difference of arrival of the Rx waveform 518 between the individual elements of the receiving antenna array (such as antenna 514). In some examples, the time difference of arrival can be calculated by measuring the difference in the received phase at each element in the receiving antenna array.

[0130] In some cases, the distance and angle of arrival of the Rx waveform 518 can be used by the processor 522 to determine the distance between the wireless device 500 and the target 502, as well as the location of the target 502 relative to the wireless device 500. The distance and angle of arrival of the Rx waveform 518 can also be used to determine the presence, movement, approach, identity, or any combination thereof of the target 502. For example, the processor 522 of the wireless device 500 can use the calculated distance and angle of arrival corresponding to the Rx waveform 518 to determine that the target 502 is moving toward the wireless device 500.

[0131] As mentioned above, wireless device 500 may include mobile devices (e.g., IoT devices, smartphones, laptops, tablets, etc.) or other types of devices. In some examples, wireless device 500 may be configured to acquire device location data and device orientation data, as well as RF sensing data. In some cases, device location data and device orientation data can be used to determine or adjust the distance and angle of arrival of reflected signals (such as Rx waveform 518). For example, when target 502 (e.g., a vehicle) moves toward wireless device 500 during an RF sensing process, the wireless device may be positioned on the ground facing the sky. In this case, wireless device 500 can use its location data and orientation data, along with the RF sensing data, to determine the direction in which target 502 is moving.

[0132] In some examples, wireless device 500 may use techniques including RTT measurement, Time of Arrival (TOA) measurement, Time Difference of Arrival (TDOA) measurement, passive positioning measurement, Angle of Arrival (AOA) measurement, Angle of Departure (AoD) measurement, Received Signal Strength Indicator (RSSI) measurement, CSI data, any other suitable technique, or any combination thereof, to collect device location data. In other examples, device orientation data may be obtained from electronic sensors on wireless device 500, such as gyroscopes, accelerometers, compasses, magnetometers, barometers, any other suitable sensors, or any combination thereof.

[0133] Figure 6 This is an illustration of an example of a receiver 604 with a transmitter 600 that utilizes RF bistatic sensing technology to determine one or more characteristics (e.g., position, rate or speed, heading, etc.) of an object 602. For example, the receiver 604 can use RF bistatic sensing to detect the presence and location of the target 602 (e.g., an object, a user, or a vehicle). Figure 6 The example is illustrated in the form of a means of transportation. In one example, receiver 604 could take the form of a base station such as a gNB.

[0134] Figure 6 The bistatic radar system includes a transmitter 600 (e.g., a transmitting sensing node) and a receiver 604 (e.g., a receiving sensing node), the transmitter being depicted in the figure as a base station (e.g., a gNB), the transmitter and the receiver being separated at a distance equivalent to the expected target distance. Figure 5 Compared to a single-site system, Figure 6 In a bistatic radar system, the transmitter 600 and receiver 604 are located far apart from each other. Conversely, a monostatic radar includes transmitters (e.g., co-located transmitters) that are located at the same location as each other. Figure 5 The wireless device 500 includes an RF transmitter 506 and a receiver (e.g., Figure 5The radar system (e.g., the RF receiver 510 of the wireless device 500) Figure 5 (system).

[0135] Bistatic radar (or more generally, multistatic radar with more than one receiver) has the advantage over monostatic radar in that it can collect radar echoes reflected from the scene at an angle different from the angle of the transmitted pulse. This may be of concern to some applications (e.g., transportation applications, scenes with multiple objects, military applications, etc.) where targets can reflect the transmitted energy in many directions (e.g., where targets are specifically designed to reflect in many directions), which minimizes the energy reflected back to the transmitter. It should be noted that in one or more examples, a monostatic system can coexist with a multistatic radar system, such as when the transmitter also has a co-located receiver.

[0136] In some examples, Figure 6 The transmitter 600 and / or receiver 604 may be a mobile phone, tablet computer, wearable device, vehicle, or other device including at least one RF interface (e.g., Figure 4 Device 407). In some examples, transmitter 600 and / or receiver 604 may be user equipment (e.g., device 407). Figure 4 IoT devices (407) provide connectivity, such as base stations (e.g., gNB, eNB, etc.), wireless access points (APs), or other devices that include at least one RF interface.

[0137] In some aspects, transmitter 600 may include one or more components for transmitting RF signals. Transmitter 600 may include at least one processor capable of determining the signals to be transmitted (e.g., determining the waveforms of these signals). Figure 5 At least one processor 522). Transmitter 600 may also include an RF transmitter (e.g., for transmitting a Tx signal including a Tx waveform 616) for transmitting a Tx signal including a Tx waveform 616. Figure 5 RF transmitter 506). The RF transmitter can be a transmitter configured to transmit cellular signals or telecommunications signals (e.g., a transmitter configured to transmit 5G / NR signals, 4G / LTE signals, or other cellular / telecommunications signals), a Wi-Fi transmitter, or a Bluetooth transmitter. ™ Transmitters, any combination thereof, or any other transmitter capable of transmitting RF signals.

[0138] The RF transmitter can be coupled to one or more transmit antennas, such as a Tx antenna (e.g., Figure 5(TX antenna 512). In some examples, the Tx antenna may be an omnidirectional antenna capable of transmitting RF signals in all directions, or a directional antenna capable of transmitting RF signals in a specific direction. In some examples, the Tx antenna may include multiple antennas (e.g., elements) configured as an antenna array.

[0139] Receiver 604 may include one or more components for receiving RF signals. For example, receiver 604 may include one or more receiving antennas, such as an Rx antenna (e.g., Figure 5 (Rx antenna 514). In some examples, the Rx antenna may be an omnidirectional antenna capable of receiving RF signals from multiple directions, or a directional antenna configured to receive signals from a specific direction. In other examples, the Rx antenna may include multiple antennas (e.g., elements) configured as an antenna array.

[0140] Receiver 604 may also include an RF receiver coupled to the Rx antenna (e.g., Figure 5 The RF receiver 510 may include a device for receiving RF waveforms (such as Wi-Fi signals, Bluetooth signals, etc.). ™ One or more hardware components (RF signals, 5G / NR signals, or any other RF signals). The output of the RF receiver may be coupled to at least one processor (e.g., Figure 5 At least one processor 522). The processor may be configured to process the received waveform (e.g., Rx waveform 618).

[0141] In one or more examples, transmitter 600 can implement RF sensing techniques, such as bistatic sensing, by transmitting a Tx waveform 616 from a Tx antenna. It should be noted that although the Tx waveform 616 is illustrated as a single line, in some cases, the Tx waveform 616 can be transmitted in all directions by an omnidirectional Tx antenna.

[0142] In one or more aspects, one or more parameters associated with the Tx waveform 616 may be used to increase or decrease the RF sensing resolution. These parameters may include frequency, bandwidth, number of spatial streams, number of antennas configured to transmit the Tx waveform 616, number of antennas configured to receive reflected RF signals (e.g., Rx waveform 618) corresponding to the Tx waveform 616, number of spatial links (e.g., the number of spatial streams multiplied by the number of antennas configured to receive RF signals), sampling rate, or any combination thereof. The transmitted waveform (e.g., Tx waveform 616) and the received waveform (e.g., Rx waveform 618) may include one or more radar RF sensing signals (also referred to as RF sensing RS).

[0143] During operation, receiver 604 (e.g., operating as a receiving sensing node) may receive a signal corresponding to Tx waveform 616 transmitted by transmitter 600 (e.g., operating as a transmitting sensing node). For example, receiver 604 may receive a signal reflected from an object or person within the range of Tx waveform 616, such as Rx waveform 618 reflected from target 602. In some cases, Rx waveform 618 may include multiple sequences corresponding to multiple copies of the sequence included in Tx waveform 616. In some examples, receiver 604 may combine the received multiple sequences to improve SNR.

[0144] In some examples, at least one processor within receiver 604 can use RF sensing data to calculate distance, angle of arrival, or other characteristics corresponding to a reflected waveform (such as Rx waveform 618). In other examples, RF sensing data can also be used to detect motion, determine location, detect changes in location or motion patterns, or any combination thereof. In some cases, the distance and angle of arrival of the reflected signal can be used to identify the size, location, movement, and / or orientation of a target in the surrounding environment (e.g., target 602) in order to detect the presence / proximity of the target.

[0145] The processor of receiver 604 can calculate the distance and angle of arrival corresponding to the reflected waveform (e.g., the distance and angle of arrival corresponding to Rx waveform 618) by using signal processing, machine learning algorithms, any other suitable techniques, or any combination thereof. In other examples, receiver 604 can send or transmit RF sensing data to at least one processor of another computing device, such as a server, which can perform calculations to obtain the distance and angle of arrival corresponding to Rx waveform 618 or other reflected waveforms.

[0146] In one or more examples, the angle of arrival of the Rx waveform 618 can be calculated by the processor of the receiver 604 by measuring the time difference of arrival of the Rx waveform 618 between the individual elements of the receiving antenna array of the receiver 604. In some examples, the time difference of arrival can be calculated by measuring the difference in the received phase at each element in the receiving antenna array.

[0147] In some cases, the distance and angle of arrival of the Rx waveform 618 can be used by the processor of receiver 604 to determine the distance between receiver 604 and target 602, as well as the positioning of target 602 relative to receiver 604. The distance and angle of arrival of the Rx waveform 618 can also be used to determine the presence, movement, proximity, identity, or any combination thereof of target 602. For example, the processor of receiver 604 can use the calculated distance and angle of arrival corresponding to the Rx waveform 618 to determine that target 602 is moving toward receiver 604.

[0148] Figure 7 This is an illustration of an example of a receiver 704 in the form of a smartphone utilizing RF bistatic sensing technology with multiple transmitters (including transmitter 700a, transmitter 700b, and transmitter 700c). This receiver can be used to determine one or more characteristics (e.g., position, speed or rate, heading, etc.) of a target 702 object. For example, receiver 704 can use RF bistatic sensing to detect the presence and location of target 702 (e.g., an object, a user, or a vehicle). Target 702 is in Figure 7 The text describes objects that do not have communication capabilities (which may be referred to as deviceless objects), such as people, vehicles (e.g., vehicles that do not have the ability to send and receive messages, such as using C-V2X or DSRC protocols), or other deviceless objects. Figure 7 The bistatic radar system is similar to Figure 6 The difference is that the bistatic radar system... Figure 7 The bistatic radar system has multiple transmitters: 700a, 700b, and 700c. Figure 6 The bistatic radar system has only one transmitter 600.

[0149] Figure 7 The bistatic radar system includes multiple transmitters 700a, 700b, 700c (e.g., transmitting sensing nodes), which are exemplified as base stations. Figure 7 The bistatic radar system also includes a receiver 704 (e.g., a receiving sensing node) depicted in the form of a smartphone. The distance between each of the transmitters 700a, 700b, and 700c and the receiver 704 is comparable to the expected distance to the target 702. Similar to... Figure 6 The dual-station system Figure 7 The transmitters 700a, 700b, 700c and receiver 704 of the bistatic radar system are positioned far apart from each other.

[0150] In one or more examples, transmitters 700a, 700b, 700c and / or receiver 704 may each be a mobile phone, tablet computer, wearable device, vehicle (e.g., a vehicle configured to transmit and receive communications according to C-V2X, DSRC or other communication protocols) or other device including at least one RF interface (e.g., Figure 4 Device 407). In some examples, transmitters 700a, 700b, 700c and / or receiver 704 may each be user equipment (e.g., Figure 4 IoT devices (407) provide connectivity, such as base stations (e.g., gNB, eNB, etc.), wireless access points (APs), or other devices that include at least one RF interface.

[0151] Transmitters 700a, 700b, and 700c may include one or more components for transmitting RF signals. Each of transmitters 700a, 700b, and 700c may include at least one processor capable of determining the signal to be transmitted (e.g., determining the waveform of the signal). Figure 5 The processor 522). Each of the transmitters 700a, 700b, and 700c may further include an RF transmitter (e.g., for transmitting Tx signals including Tx waveforms 716a, 716b, 716c, 720a, 720b, and 720c) for transmitting Tx signals including Tx waveforms 716a, 716b, 716c, 720a, 720b, and 720c. Figure 5 The RF transmitter 506. In one or more examples, Tx waveforms 716a, 716b, and 716c are RF sensing signals, and Tx waveforms 720a, 720b, and 720c are communication signals. In one or more examples, Tx waveforms 720a, 720b, and 720c are communication signals that can be used to schedule transmitters (e.g., transmitters 700a, 700b, and 700c) and receivers (e.g., receiver 704) to perform RF sensing of a target (e.g., target 702) to obtain location information about the target. The RF transmitter can be a transmitter configured to transmit cellular or telecommunication signals (e.g., a transmitter configured to transmit 5G / NR signals, 4G / LTE signals, or other cellular / telecommunication signals, etc.), a Wi-Fi transmitter, or a Bluetooth transmitter. ™ Transmitters, any combination thereof, or any other transmitter capable of transmitting RF signals.

[0152] The RF transmitter can be coupled to one or more transmit antennas, such as a Tx antenna (e.g., Figure 5 (TX antenna 512). In one or more examples, the Tx antenna may be an omnidirectional antenna capable of transmitting RF signals in all directions, or a directional antenna capable of transmitting RF signals in a specific direction. The Tx antenna may include multiple antennas (e.g., elements) configured as an antenna array.

[0153] Figure 7 The receiver 704 may include one or more components for receiving RF signals. For example, the receiver 704 may include one or more receiving antennas, such as an Rx antenna (e.g., Figure 5 The Rx antenna 514. In one or more examples, the Rx antenna may be an omnidirectional antenna capable of receiving RF signals from multiple directions, or a directional antenna configured to receive signals from a specific direction. In some examples, the Rx antenna may include multiple antennas (e.g., elements) configured as an antenna array (e.g., a phased antenna array).

[0154] Receiver 704 may also include an RF receiver coupled to the Rx antenna (e.g., Figure 5The RF receiver 510 may include a device for receiving RF waveforms (such as Wi-Fi signals, Bluetooth signals, etc.). ™ One or more hardware components (RF signals, 5G / NR signals, or any other RF signals). The output of the RF receiver can be coupled to at least one processor (e.g., Figure 5 The processor 522). The processor can be configured to process the received waveform (e.g., Rx waveform 718, which is a reflected (echo) RF sensing signal).

[0155] In some examples, transmitters 700a, 700b, and 700c can implement RF sensing techniques (e.g., bistatic sensing techniques) by transmitting Tx waveforms 716a, 716b, and 716c (e.g., radar sensing signals) from a Tx antenna associated with each of transmitters 700a, 700b, and 700c. Although Tx waveforms 716a, 716b, and 716c are illustrated as single lines, in some cases, Tx waveforms 716a, 716b, and 716c can be transmitted in all directions (e.g., via an omnidirectional Tx antenna associated with each of transmitters 700a, 700b, and 700c).

[0156] In one or more aspects, one or more parameters associated with the Tx waveforms 716a, 716b, 716c can be used to increase or decrease the RF sensing resolution. These parameters may include, but are not limited to, frequency, bandwidth, number of spatial streams, number of antennas configured to transmit the Tx waveforms 716a, 716b, 716c, number of antennas configured to receive reflected (echo) RF signals (e.g., Rx waveform 718) corresponding to each of the Tx waveforms 716a, 716b, 716c, number of spatial links (e.g., the number of spatial streams multiplied by the number of antennas configured to receive RF signals), sampling rate, or any combination thereof. The transmitted waveforms (e.g., Tx waveforms 716a, 716b, 716c) and the received waveforms (e.g., Rx waveform 718) may include one or more radar RF sensing signals (also referred to as RF sensing RS). It should be noted that, although Figure 7 Only one reflected sensing signal is shown (e.g., Rx waveform 718), but it should be understood that a separate reflected (echo) sensing signal will be generated by each sensing signal reflected from the target 702 (e.g., Tx waveforms 716a, 716b, 716c).

[0157] exist Figure 7During system operation, receiver 704 (e.g., operating as a receiving sensing node) can receive signals corresponding to Tx waveforms 716a, 716b, 716c transmitted by transmitters 700a, 700b, 700c (e.g., each operating as a transmitting sensing node). Receiver 704 can receive signals reflected from objects or people within the range of Tx waveforms 716a, 716b, 716c, such as Rx waveform 718 reflected from target 702. In one or more examples, Rx waveform 718 may include multiple sequences corresponding to multiple copies of the sequences included in their corresponding Tx waveforms 716a, 716b, 716c. In some examples, receiver 704 may combine the received multiple sequences to improve SNR.

[0158] In some examples, the RF sensing data can be used by at least one processor within receiver 704 to calculate distance, angle of arrival (AOA), TDOA, angle of departure (AoD), or other characteristics corresponding to the reflected waveform (e.g., Rx waveform 718). In other examples, the RF sensing data can also be used to detect motion, determine location, detect changes in location or motion patterns, or any combination thereof. In one or more examples, the distance and angle of arrival of the reflected signal can be used to identify the size, location, movement, and / or orientation of a target (e.g., target 702) in order to detect the presence / proximity of the target.

[0159] The processor of receiver 704 can calculate the distance and angle of arrival corresponding to the reflected waveform (e.g., the distance and angle of arrival corresponding to Rx waveform 718) by using signal processing, machine learning algorithms, any other suitable techniques, or any combination thereof. In one or more examples, receiver 704 can send or transmit RF sensing data to at least one processor of another computing device, such as a server, which can perform calculations to obtain the distance and angle of arrival corresponding to Rx waveform 718 or other reflected waveforms (not shown).

[0160] In one or more examples, the processor of receiver 704 can calculate the angle of arrival (AOA) of the Rx waveform 718 by measuring the time difference of arrival (TDOA) of the Rx waveform 718 between the individual elements of the receiving antenna array of receiver 704. In some examples, the TDOA can be calculated by measuring the difference in received phase at each element in the receiving antenna array. In one exemplary example, to determine the TDOA, the processor can use one of the elements of the receiving antenna array as a reference to determine the time difference of arrival of the Rx waveform 718 to the receiving antenna array element. The time difference is proportional to the distance difference.

[0161] In some cases, the processor of receiver 704 can use the distance, AOA, TDOA, other measurement information (e.g., AoD, etc.) from Rx waveform 718, or any combination thereof, to determine the distance between receiver 704 and target 702, and to determine the location of target 702 relative to receiver 704. In one example, the processor can use distance, AOA, and / or TDOA information as input to apply multi-point localization or other location-based algorithms to determine the location of target 702 (e.g., 3D location). In other examples, the processor can use the distance, AOA, and / or TDOA from Rx waveform 718 to determine the presence, movement (e.g., speed or rate, heading or direction or movement, etc.), proximity, identity, any combination thereof, or other characteristics of target 702. For example, the processor of receiver 704 can use the distance, AOA, and / or TDOA corresponding to Rx waveform 718 to determine that the target is moving toward receiver 704.

[0162] Figure 8 This is a diagram illustrating the geometry used for dual-station (or single-station) sensing. Figure 8 The bistatic radar north reference coordinate system in two dimensions is shown. Specifically, Figure 8 The coordinate system and parameters for bistatic radar operation are shown, defined in a plane (referred to as the bistatic plane) encompassing transmitter 800, receiver 804, and target 802. A bistatic triangle lies within the bistatic plane. Transmitter 800, target 802, and receiver 804 are shown relative to each other. Transmitter 800 and receiver 804 are separated by a baseline distance L. An extended baseline is defined as extending the baseline distance L beyond transmitter 800 or receiver 804. Target 802 and transmitter 800 are separated by a distance R. T Furthermore, the target 802 and receiver 804 are separated by a distance R. R .

[0163] Angle θ T and θ R These are the transmitter's observation angle 800° and the receiver's observation angle 804°, respectively. These observation angles are considered positive when measured clockwise from North (N). Angle θ T and θ R Also known as the angle of arrival (AOA) or line-of-sight (LOS). Bistatic angle (β) is the angle between the transmitter 800, target 802, and receiver 804 in a radar system. Specifically, the bistatic angle is the angle between the transmitter 800 and the receiver 804, with the vertex located at the target 802. The bistatic angle equals the observation angle of the transmitter 800 minus the observation angle θ of the receiver 804. R (For example, β = θ) T - θ R ).

[0164] When the bistatic angle is exactly zero (0°), the radar is considered a monostatic radar; when the bistatic angle is close to zero, the radar is considered a pseudo-monostatic radar; and when the bistatic angle is close to 180 degrees, the radar is considered a forward-scattering radar. Otherwise, the radar is only considered and referred to as a bistatic radar. The bistatic angle (β) can be used to determine the radar cross-section of a target.

[0165] Figure 9 This is a diagram illustrating an example of bistationary range 910 in bistationary sensing. In this diagram, a radar transmitter (Tx) 900, a target 902, and a receiver (Rx) 904 are shown relative to each other. Transmitter 900 and receiver 904 are separated by a baseline distance L, target 902 is separated by a distance Rtx from transmitter 900, and target 902 is separated by a distance Rrx from receiver 904.

[0166] The bistatic distance 910 (shown as an ellipse) refers to the measured distance made by a radar having a separate transmitter 900 and a receiver 904 (e.g., the transmitter 900 and receiver 904 are positioned far apart from each other). Receiver 904 measures the time of arrival from when transmitter 900 transmits a signal to when receiver 904 receives a signal from transmitter 900 via target 902. The bistatic distance 910 defines an ellipse of constant bistatic distance, called an isometric profile, on which target 902 lies, with its focus centered on transmitter 900 and receiver 904. If the distance of target 902 from receiver 904 is Rrx, the distance from target 902 to transmitter 900 is Rtx, and receiver 904 and transmitter 900 are separated by a distance L, then the bistatic distance is equal to Rrx + Rtx - L. It should be noted that the motion of target 902 causes a rate of change in the bistatic distance, which results in a bistatic Doppler shift.

[0167] Typically, a constant bistation distance is used to draw an ellipse, with transmitter 900 and receiver 904 positioned as foci. The bistation equidistant profile is the location where the ground cuts the ellipse. When the ground is flat, this intercept forms an ellipse (e.g., bistation distance 910). Note that these ellipses are not centered at a mirror point unless the two platforms have equal height.

[0168] As previously mentioned, in 5G NR, PUCCH is the uplink physical channel carrying UCI. UCI includes HARQ feedback, CSI, and SR. There are five different formats for PUCCH. The use of a particular PUCCH format is determined by how many bits of information should be carried and how many symbols are assigned. NR PUCCH is flexible in its time and frequency allocation. This flexibility allows UEs with smaller bandwidth capabilities to be supported in NR carriers and allows for efficient use of available resources for coverage and capacity. Network devices (e.g., UEs) can be configured with PUCCH resources for CSI reporting or SR. For UCI transmission including HARQ-ACK bits, network devices (e.g., UEs) can be configured with up to four PUCCH resource sets based on the UCI size.

[0169] The NR PUCCH design is based on five PUCCH formats (e.g., PUCCH formats 0, 1, 2, 3, and 4). PUCCH formats 0 and 2 (e.g., referred to as short PUCCH) use one or two OFDM symbols. PUCCH formats 1, 3, and 4 (e.g., referred to as long PUCCH) can use 4 to 14 OFDM symbols. PUCCH formats 0 and 1 carry one or two bits of UCI payload, while the other PUCCH formats are used to carry more than two bits of UCI payload. In PUCCH formats 1, 3, and 4, symbols with DMRS are time-division multiplexed with UCI symbols to maintain a low peak-to-average power ratio (PAPR). In PUCCH format 2, DMRS is frequency-multiplexed with the data-carrying subcarrier. When applicable, multi-user multiplexing on the same time and frequency resources is supported only for PUCCH formats 0, 1, and 4 by means of different cyclic shifts or OCC.

[0170] In the current 5G NR PUCCH formats 0 and 1, the UCI carries only one or two bits. PUCCH format 0 is a short PUCCH and is based on sequence selection. PUCCH format 1 is a long PUCCH and has UCI and DMRS time multiplexing.

[0171] Figure 10 An example of PUCCH format 1 is shown. Specifically, Figure 10 This is a diagram illustrating an example of symbol configuration 1000 for PUCCH format 1. Figure 10In the diagram, symbol configuration 1000 is shown as comprising a total of N OFDM symbols 1010. The N OFDM symbols 1010 include N / 2 DMRS OFDM symbols 1020 and N / 2 UCI OFDM symbols 1030. In symbol configuration 1000, DMRS OFDM symbols 1020 and UCI OFDM symbols 1030 alternate with each other. Each DMRS OFDM symbol 1020 includes a sequence (S1), and each UCI OFDM symbol 1030 includes a sequence (S1) multiplied by bits (b). In PUCCH format 1, DMRS OFDM symbols 1020 and UCI OFDM symbols 1030 are time-division multiplexed to achieve low PAPR.

[0172] As previously mentioned, technologies that allow resources to be used for both PUCCH and sensing (e.g., for joint communication and sensing) can be useful. In one or more aspects, these systems and technologies provide solutions for reusing FMCW for both PUCCH and sensing. In one or more examples, a solution for reusing FMCW for PUCCH and sensing can utilize FMCW as the base sequence of PUCCH for wireless communication (e.g., for 5G communication, 6G communication, etc.) while also reusing FMCW for sensing purposes. In some examples, network entities (e.g., base stations or network servers) can configure the same resources (e.g., including FMCW) to network devices (e.g., UEs) for both PUCCH (e.g., PUCCH transmission) and sensing (e.g., mono-site sensing or bi-site sensing).

[0173] In one or more aspects, network entities (such as base stations or network servers) can configure network devices (such as UEs) to use the same resources for both PUCCH and sensing. This configuration can be semi-persistent or dynamic.

[0174] In one or more examples, there may be two types of periodic PUCCH resources configured for network devices (e.g., UEs). Figure 11 Example use cases including different types of PUCCH resources are shown. Specifically, Figure 11 Figure 1100 illustrates examples of different use cases including PUCCH resources (e.g., use case 1 1110 and use case 2 1120). Different types of PUCCH resources may include wideband PUCCH resources 1130 and narrowband PUCCH resources 1140. Wideband PUCCH resources 1130 can be used for both UCI purposes and sensing purposes to allow for more efficient resource utilization. Narrowband PUCCH resources 1120 can be used for UCI that uses legacy sequences (e.g., utilizes legacy schemes and is backward compatible).

[0175] exist Figure 11In use case 1 1110, the period for FMCW transmission used for sensing and the period for PUCCH transmission can be the same. For example, these periods can be the same because all resources in these resources are wideband PUCCH resources 1130. Therefore, FMCW can be transmitted for all of these resources used for sensing. In some examples, use case 1 1110 may be applicable when the period for FMCW transmission used for sensing is shorter than the period for PUCCH transmission, in which case some wideband resources are used only for sensing. In use case 2 1120, the period for FMCW transmission used for sensing (e.g., the period between wideband PUCCH resources 1130) is longer than the period for PUCCH transmission (e.g., the period between narrowband PUCCH resources 1140).

[0176] In one or more examples, a network device (e.g., a UE) may be configured with a semi-persistent narrowband PUCCH resource configuration, while a wideband PUCCH resource may be dynamically configured to override the narrowband PUCCH resource timing. In some examples, a network device (e.g., a UE) may be configured with a semi-persistent wideband PUCCH resource configuration, while a narrowband PUCCH resource may be dynamically configured to be truncated at the wideband PUCCH resource timing.

[0177] In one or more aspects, FMCW can be used as a base sequence for broadband PUCCH resources (e.g., it can be used for both UCI and sensing PUCCH transmissions). In some aspects, FMCWs with different slopes can be used for different base sequences. Thus, each FMCW can have a slope associated with a particular base sequence. Figure 12 Examples of FMCWs with different slopes are shown. Specifically, Figure 12 This is a diagram illustrating example 1200 with symbols 1210, 1220, and 1230 configured as FMCWs, each with a different slope. S 0 , Sm and Sn ).exist Figure 12 In the middle, the symbol 1210 (e.g.) Tsym ) is a slope S 0 FMCW. Symbol 1220 (e.g.) Tsym ) is equal to 0.5 S 0 slope Sm FMCW. Symbol 1230 (e.g.) Tsym ) is equal to 2 S 0 slope SnThe FMCW. In one or more examples, for a 1-bit UCI, the slope can be ( S 0 , S 1 For a 2-bit UCI, the slope can be ( S 0 , S 1 , S 2 , S 3 The slope can be defined as the occupied frequency bandwidth divided by the occupied time.

[0178] In some respects, FMCWs with different sign levels of OCC can be used for different base sequences. Thus, each FMCW can have a sign level of OCC associated with a specific base sequence. Figure 13 This is a diagram illustrating example 1300 of different symbol-level OCC sequences (e.g., OCC sequence 01310 and OCC sequence 11320). Figure 13 In the sequence, sequence 0 1310 includes the bit sequence 1, 1, 1, 1, ..., and sequence 1 1320 includes the bit sequence 1, -1, 1, -1, 1, -1, ... The sequences shown (e.g., sequence 0 1310 and sequence 1 1320) are used for PUCCH format 1, where each sequence (e.g., sequence 0 1310 and sequence 1 1320) includes a total of 14 symbols 1330.

[0179] In one or more aspects, FMCWs with different cyclic shifts can be used with different base sequences. Thus, each FMCW can have a cyclic shift associated with a particular base sequence. Figure 14 This is a diagram illustrating example 1400 with different cyclic shifts for symbols 1410 and 1420. Figure 14 In the diagram, symbol 1410 is shown as having a zero-cycle shift, and symbol 1420 is shown as having an equal-zero-cycle shift. Tsym / 2 circular shift.

[0180] In one or more examples, for a 1-bit UCI, the slope can be ( S 0 , S 1 For a 2-bit UCI, the slope can be ( S 0 , S 1 , S 2 , S 3There may already be some timing advance (TA) information at the network device (e.g., UE) side. The network device (e.g., UE) can apply TA to send broadband FMCW for both broadband PUCCH and sensing. Thus, delay spread can be controlled.

[0181] In some respects, FMCWs with different zero-tail lengths can be used for different base sequences. Thus, each FMCW can have a zero-tail length associated with a particular base sequence. Figure 15 This is an illustration of example 1500, which illustrates symbols 1510, 1520, 1530, and 1540 with different zero-tail lengths. Figure 15 In this example, symbol 1510 is shown as having no zero-tailed length. The second portion of each of symbols 1520, 1530, and 1540 is shown as having a zero-tailed length (e.g., no content (zero) is transmitted in the zero-tailed length portion of these symbols 1520, 1530, and 1540). The zero-tailed length will each represent a different bit in the UCI. In one or more examples, the zero-tailed length for a 1-bit UCI can be ( t 0 ,t 1 ), or for a 2-bit UCI it could be ( t 0 , t 1 , t 2 , t 3 ).

[0182] In one or more aspects, FMCWs with different triangular chirps can be used with different base sequences. Thus, each FMCW can have a triangular chirp associated with a particular base sequence. Figure 16 This is an illustration of example 1600, which shows symbols 1610, 1620, 1630, and 1640 with different triangular chirps. Figure 16 In the diagram, each of the symbols 1610, 1620, 1630, and 1640 illustrates a different chirping pattern.

[0183] In one or more examples, a network device (e.g., a UE) may (e.g., report to a network entity) which base sequence method(s) it supports (e.g., FMCW with different slopes, FMCW with different symbol-level OCC, FMCW with different cyclic shifts, FMCW with different tail lengths, and / or FMCW with different triangle chirps) for both wideband PUCCH and sensing. For example, the network device (e.g., a UE) may (e.g., via capability signals) transmit (e.g., send) capability information that may include capability reports or messages indicating one or more base sequence methods (e.g., FMCW with different slopes, FMCW with different symbol-level OCC, FMCW with different cyclic shifts, FMCW with different tail lengths, and / or FMCW with different triangle chirps) supported by the network device for PUCCH and sensing.

[0184] In some examples, network entities (such as base stations or network servers) can configure network devices (such as UEs) to use specific base sequence methods that should be used for both broadband PUCCH and sensing.

[0185] Figure 17 and Figure 18 Examples of systems 1700 and 1800 are shown for two different use cases of reusing FMCW for both PUCCH and sensing. Specifically, Figure 17 This is a diagram illustrating an example of a system 1700 used for reusing FMCW for PUCCH and sensing, where system 1700 is performing single-station sensing. Figure 17 In this embodiment, system 1700 is shown as including network device 1720 in the form of a UE (e.g., such as a smartphone). Network device 1720 (e.g., UE) can operate as radar Tx and radar Rx for sensing purposes (e.g., for single-site sensing). Figure 17 The diagram also shows network entities 1710 in the form of base stations (e.g., gNBs or parts of gNBs, such as CUs, DUs, RUs, near-RT RICs, non-RT RICs, etc.).

[0186] System 1700 may include, for example Figure 17 The system 1700 may include more or fewer network devices and / or network entities as shown. Figure 17The examples illustrate different types of network devices (e.g., vehicles) and / or network entities (e.g., web servers). In one or more examples, network device 1720 and network entity 1710 may each be equipped with heterogeneous capabilities, which may include, but are not limited to, 4G / 5G cellular connectivity, GPS capabilities, camera capabilities, radar capabilities, and / or LiDAR capabilities. Network device 1720 and network entity 1710 may be able to perform wireless communication with each other via communication signals.

[0187] In some examples, network device 1720 may be able to send and receive some type of sensing signal (e.g., S-RS) (e.g., camera, RF sensing signal, optical sensing signal, etc.). In some cases, network device 1720 may send and receive sensing signals (e.g., S-RS) for use in detecting nearby targets (e.g., target 1730 in the form of a vehicle) using one or more sensors. In some cases, network device 1720 may detect nearby targets based on one or more images or frames captured using one or more cameras.

[0188] A network device 1720 (e.g., a UE) that can operate as both radar Tx and radar Rx can perform RF sensing (e.g., monostation sensing) of at least one target (e.g., target 1730) to obtain RF sensing measurements of the target (e.g., Doppler measurement, RTT measurement, TOA measurement, and / or TDOA measurement). For sensing purposes, the RF sensing measurements of the target (e.g., target 1730) can be used (e.g., by at least one processor of at least one network device in network device 1720) to determine one or more characteristics of the target (e.g., target 1730) (e.g., rate, position, range, movement, heading, size, and / or other characteristics).

[0189] During operation of system 1700, such as when performing single-site sensing of a target (e.g., target 1730), network entity 1710 (e.g., gNB) may transmit (e.g., send) configuration signal 1740 to network device 1720 (e.g., UE). Configuration signal 1740 may include configurations that include resources for PUCCH and for sensing both. These resources may include FMCW. FMCW may be used as a base sequence for PUCCH.

[0190] After receiving configuration signal 1740, network device 1720 (e.g., UE) can encode the UCI payload using the base sequence configured by network entity 1710 (e.g., gNB). Network device 1720 (e.g., UE) can transmit (e.g., send) PUCCH 1750 to network entity 1710 (e.g., gNB) based on the resources in configuration signal 1740.

[0191] After network entity 1710 (e.g., gNB) receives PUCCH 1750, network entity 1710 (e.g., gNB) can use incoherent PUCCH detection to detect which base sequence was transmitted by network device 1720 (e.g., UE). Network device 1720 (e.g., UE) can perform monostation sensing by transmitting (e.g., sending) sensing signal 1760 towards target 1730 based on resources. Sensing signal 1760 can be reflected from target 1730 to generate reflected signal 1770 radiated in the direction returning towards network device 1720 (e.g., UE). Network device 1720 (e.g., UE) can then receive reflected signal 1770.

[0192] After network device 1720 (e.g., UE) receives reflected signal 1770, network device 1720 (e.g., UE) can obtain measurements of the received reflected signal 1770 (e.g., Doppler measurement, RTT measurement, TOA measurement, and / or TDOA measurement). At least one processor of network device 1720 (e.g., UE) Figure 21 The processor 2110 can then determine or calculate the characteristics of the target (e.g., target 1730) by using sensing measurements (e.g., Doppler measurement, RTT measurement, TOA measurement and / or TDOA measurement) from the received reflected signal 1770.

[0193] In one or more examples, network entity 1710 (e.g., gNB) may detect a base sequence in parallel (e.g., simultaneously) with network device 1720 (e.g., UE) while performing single-site sensing.

[0194] Figure 18 This is a diagram illustrating an example of a system 1800 used for reusing FMCW for PUCCH and sensing, where system 1800 is performing dual-station sensing. Figure 18 In this embodiment, system 1800 is shown as including network device 1820 in the form of a UE (e.g., such as a smartphone). Network device 1820 (e.g., UE) can operate as a radar Tx for sensing purposes (e.g., for bi-station sensing). Figure 18 The diagram also shows a network entity 1810 in the form of a base station (e.g., a gNB or a part of a gNB, such as a CU, DU, RU, near-RT TRIC, non-RT RIC, etc.). The network entity 1810 (e.g., a gNB) can operate as a radar Rx for sensing purposes (e.g., for bi-station sensing).

[0195] System 1800 may include, for example Figure 18 The system 1800 may include more or fewer network devices and / or network entities as shown. Figure 18The examples illustrate different types of network devices (e.g., vehicles) and / or network entities (e.g., web servers). In some examples, network device 1820 and network entity 1810 may each be equipped with heterogeneous capabilities, which may include, but are not limited to, 4G / 5G cellular connectivity, GPS capabilities, camera capabilities, radar capabilities, and / or LiDAR capabilities. Network device 1820 and network entity 1810 may be able to perform wireless communication with each other via communication signals.

[0196] In one or more examples, network device 1820 may be able to transmit some type of sensing signal (e.g., S-RS) (e.g., camera, RF sensing signal, optical sensing signal, etc.). In some cases, network device 1820 may transmit sensing signals (e.g., S-RS) for detecting nearby targets (e.g., target 1830 in the form of a vehicle). Network entity 1810 may be able to receive some type of sensing signal (e.g., S-RS) (e.g., camera, RF sensing signal, optical sensing signal, etc.). In some cases, network entity 1810 may receive sensing signals (e.g., S-RS) for detecting nearby targets (e.g., target 1830 in the form of a vehicle) using one or more sensors. In some cases, network entity 1810 may detect nearby targets based on one or more images or frames captured using one or more cameras.

[0197] A network device 1820 (e.g., a UE) that can operate as a radar Tx can perform RF sensing (e.g., bistatic sensing) of at least one target (e.g., target 1830). A network entity 1810 (e.g., a gNB) that can operate as a radar Rx can perform RF sensing (e.g., bistatic sensing) of at least one target (e.g., target 1830) to obtain RF sensing measurements of the target (e.g., target 1830) (e.g., Doppler measurement, RTT measurement, TOA measurement, and / or TDOA measurement). For sensing purposes, the RF sensing measurements of the target (e.g., target 1830) can be used (e.g., by at least one processor of at least one network entity in network entity 1810) to determine one or more characteristics of the target (e.g., target 1830) (e.g., rate, position, range, movement, heading, size, and / or other characteristics).

[0198] During operation of system 1800, such as when performing bi-site sensing of a target (e.g., target 1830), network entity 1810 (e.g., gNB) may transmit (e.g., send) configuration signal 1840 to network device 1820 (e.g., UE). Configuration signal 1840 may include configurations including resources for PUCCH and for sensing both. These resources may include FMCW that can be used as a base sequence for PUCCH.

[0199] After receiving configuration signal 1840, network device 1820 (e.g., UE) can encode the UCI payload using the base sequence configured by network entity 1810 (e.g., gNB). Network device 1820 (e.g., UE) can transmit (e.g., send) PUCCH 1850 to network entity 1810 (e.g., gNB) based on the resources in configuration signal 1840.

[0200] After network entity 1810 (e.g., gNB) receives PUCCH 1850, network entity 1810 (e.g., gNB) can use incoherent PUCCH detection to detect which base sequence was transmitted by network device 1820 (e.g., UE). Network device 1820 (e.g., UE) can perform bi-site sensing by transmitting (e.g., sending) sensing signal 1860 towards target 1830 based on resources. Sensing signal 1860 can be reflected from target 1830 to generate reflected signal 1870 radiated in the direction towards network entity 1810 (e.g., gNB). Network entity 1810 (e.g., gNB) can then receive reflected signal 1870.

[0201] After network entity 1810 (e.g., gNB) receives reflected signal 1870, network entity 1810 (e.g., gNB) can obtain measurements of the received reflected signal 1870 (e.g., Doppler measurement, RTT measurement, TOA measurement, and / or TDOA measurement). At least one processor of network entity 1810 (e.g., gNB) Figure 21 The processor 2110 can then determine or calculate the characteristics of the target (e.g., target 1830) by using sensing measurements (e.g., Doppler measurement, RTT measurement, TOA measurement and / or TDOA measurement) from the received reflected signal 1870.

[0202] In one or more examples, network entity 1810 (e.g., gNB) may detect the base sequence before network entity 1810 (e.g., gNB) is performing bisite sensing based on the base sequence associated with the detected UCI payload. Network entity 1810 (e.g., gNB) will need to know the base sequence sent by network device 1820 (e.g., UE) in order for network entity 1810 (e.g., gNB) to perform bisite sensing.

[0203] In some aspects, one or more multiplexing techniques can be implemented for multi-UE scenarios (corresponding to multi-user scenarios), such as one or more time-division multiplexing (TDM) techniques, one or more frequency-division multiplexing (FDM) techniques, using different slopes, using different symbol-level OCCs, any combination thereof, and / or other multiplexing techniques. In an illustrative example, intra-symbol TDM can be implemented. For intra-symbol TDM, each UE can be configured with more than [a certain number of] [unclear text - possibly related to a specific feature or feature]. The slope (or set of slopes), where ,and n Corresponding to the number of UEs. For example, the symbol length or the duration of a symbol can be divided into multiple parts, and ( n Each UE will use only one portion of the total number of symbols (out of UEs). Additionally or alternatively, in another exemplary example, symbol-level TDM may be performed. For symbol-level TDM, each UE can be configured with... 1 symbol, of which N It is the total number of symbols, and n Corresponding to the number of UEs. In this example, ( n Each UE will use (out of UEs) in total N (Different symbols within a symbol). In some cases, when performing TDM (e.g., intra-symbol TDM and / or symbol-level TDM), time-domain repetition can be disabled (e.g., ...). Figure 12 The one shown has equal to 2 S 0 slope Sn The symbol 1230).

[0204] Additionally or alternatively, in another exemplary example, FDM may be implemented. For example, each UE may be configured with less than The slope (or set of slopes). In this example, the total bandwidth is divided into... n Parts (of which) n Again, corresponding to the number of UEs), and each of the n UEs will use a portion of the bandwidth ( n (One of the parts) n Each of the sections corresponds to a different frequency resource (e.g., subcarrier) of available bandwidth. In some cases, when FDM is performed, frequency domain repetition occurs (e.g., such as...). Figure 13 The frequency domain repetition shown can be disabled (e.g., because different frequency resources will be used by different UEs or by different UEs).

[0205] Additionally or alternatively, in another exemplary example, different slopes can be used by different UEs. For example, each UE can be configured with and can use different (e.g., non-overlapping) slopes (or sets of slopes). For example, a first UE (UE1) can use a first set of slopes S0, S1, S2, and S3, and a second UE (UE2) can use a second set of slopes S4, S5, S6, and S7, wherein the first set of slopes is different from the second set of slopes (and does not overlap with the second set of slopes).

[0206] Additionally or alternatively, in another exemplary example, different symbol-level OCCs can be used by different UEs. For example, each UE can be configured with a different symbol-level OCC (e.g., Figure 13 (The different symbol-level OCC sequences shown). In one example, the first UE can be configured and can use... Figure 13 The OCC sequence 0 1310, and the second UE can be configured with and can be used Figure 13 The OCC sequence is 0 1320.

[0207] Figure 19 This is a flowchart illustrating an example of a process 1900 for reusing FMCW for PUCCH and sensing. Process 1900 can be performed by a network device (e.g., Figure 17 Network device 1720 and / or Figure 18 The network device 1820, which in some cases may be a UE, or is executed by components or systems of the network device (e.g., one or more chipsets, one or more processors (such as one or more CPUs, DSPs, NPUs, NSPs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, etc.), ML systems (such as neural network models), any combination thereof, and / or other components or systems). The operation of process 2000 may be implemented on one or more processors (e.g., Figure 21 Software components that execute and run on the processor 2110 or other processor. Furthermore, the network device may be enabled to transmit and / or receive signals in process 1900, for example, via one or more antennas and / or one or more transceivers (e.g., wireless transceivers).

[0208] At box 1910, a network device (or a component thereof, such as a transceiver) may receive from a network entity at least one configuration signal indicating at least one configuration, which includes resources for a physical uplink control channel (PUCCH) and for sensing. In some aspects, the at least one configuration is a semi-persistent configuration or a dynamic configuration. In some cases, the network entity is a base station, a network server, or other type of network entity.

[0209] In some aspects, the at least one configuration signal is a configuration signal indicating configurations including those for the PUCCH and for sensing resources. In such aspects, a network device (or a component thereof, such as a transceiver) may receive a configuration signal indicating configurations including those for the PUCCH and for sensing resources.

[0210] In some cases, the at least one configuration signal includes a first configuration signal indicating a first configuration including resources for PUCCH, and a second configuration signal indicating a second configuration including resources for sensing. In such cases, a network device (or a component thereof, such as a transceiver) may receive the first configuration signal indicating a first configuration including resources for PUCCH, and may receive the second configuration signal indicating a second configuration including resources for sensing.

[0211] At box 1920, a network device (or a component thereof, such as a transceiver) may transmit (or output for transmission) a PUCCH to a network entity based on at least one configuration including resources. In some cases, the network device (or a component thereof) may use Frequency Modulated Continuous Wave (FMCW) to transmit resources. In some aspects, as described herein, FMCW may be used as a base sequence for the PUCCH. In some examples, the network device (or a component thereof) may encode uplink control information (UCI) based on the base sequence. In some cases, the FMCW has a slope associated with the base sequence (e.g., as shown in the diagram). Figures 12 to 16 (As shown in the diagram). Additionally or alternatively, in some aspects, the FMCW has a symbol-level orthogonal covering code (OCC) associated with the base sequence (e.g., as shown in the diagram). Figure 13 (As shown in the diagram). Additionally or alternatively, in some examples, the FMCW has a cyclic shift associated with the base sequence (e.g., as shown in the diagram). Figure 14 (As shown in the diagram). Additionally or alternatively, in some cases, the FMCW has a zero-tail length associated with the base sequence (e.g., as shown in the diagram). Figure 15 (As shown in the diagram). Additionally or alternatively, in some aspects, the FMCW has a triangular chirp associated with the base sequence (e.g., as shown in the diagram). Figure 16 (as shown in the image).

[0212] At box 1930, a network device (or a component thereof, such as a transceiver) may transmit (or output a sensing signal for transmission) based on at least one configuration including resources. In some aspects, the network device (or a component thereof, such as a transceiver) may receive a reflected signal generated from a sensing signal reflected from an object.

[0213] In some cases, network devices (or components thereof, such as transceivers) may send (or output to network entities) information indicating the capabilities of one or more base sequence methods supported by the network device for PUCCH and sensing.

[0214] Figure 20 This is a flowchart illustrating an example of a process 2000 for reusing FMCW for PUCCH and sensing. Process 2000 can be performed by a network entity (e.g., Figure 17 Network entity 1710 and / or Figure 18 The operation of process 2000 can be performed by network entity 1810, base stations of other network entities, network servers, or by components or systems of the device (e.g., chipsets). The operation of process 2000 can be implemented on one or more processors (e.g., Figure 21 Software components that execute and run on the processor 2110 or other processor. Furthermore, the device may be enabled to transmit and / or receive signals in process 2000, for example, via one or more antennas and / or one or more transceivers (e.g., wireless transceivers).

[0215] At box 2010, a network entity (or its components, such as a transceiver) may send (or output for transmission) at least one configuration signal to a network device indicating at least one configuration, which includes resources for the Physical Uplink Control Channel (PUCCH) and for sensing. In some cases, the at least one configuration is a semi-persistent configuration or a dynamic configuration. In some cases, the network device is a UE.

[0216] At box 2020, a network entity (or a component thereof, such as a transceiver) may receive a PUCCH from a network device based on at least one configuration including resources. In some cases, the network device (or a component thereof) may use frequency modulated continuous wave (FMCW) to receive resources. In some aspects, as described herein, FMCW may be used as a base sequence for the PUCCH. In some examples, the network device (or a component thereof) may encode uplink control information (UCI) based on the base sequence. In some cases, the FMCW has a slope associated with the base sequence (e.g., as shown in the diagram). Figures 12 to 16 (As shown in the diagram). Additionally or alternatively, in some aspects, the FMCW has a symbol-level orthogonal covering code (OCC) associated with the base sequence (e.g., as shown in the diagram). Figure 13 (As shown in the diagram). Additionally or alternatively, in some examples, the FMCW has a cyclic shift associated with the base sequence (e.g., as shown in the diagram). Figure 14 (As shown in the diagram). Additionally or alternatively, in some cases, the FMCW has a zero-tail length associated with the base sequence (e.g., as shown in the diagram). Figure 15 (As shown in the diagram). Additionally or alternatively, in some aspects, the FMCW has a triangular chirp associated with the base sequence (e.g., as shown in the diagram). Figure 16 (as shown in the image).

[0217] In some respects, a network entity (or its components, such as a transceiver) may receive reflected signals generated from sensing signals reflected from an object, where the sensing signals are based on the resource.

[0218] In some respects, a network device (or a component thereof) may receive information from the network device indicating the capability of one or more base sequence methods supported by the network device for PUCCH and sensing.

[0219] In some aspects, the at least one configuration signal is a configuration signal indicating configurations including those for the PUCCH and for sensing resources. In such aspects, a network device (or a component thereof, such as a transceiver) may transmit (or output for transmission) a configuration signal indicating configurations including those for the PUCCH and for sensing resources.

[0220] In some cases, the at least one configuration signal includes a first configuration signal indicating a first configuration including resources for PUCCH, and a second configuration signal indicating a second configuration including resources for sensing. In such cases, the network device (or a component thereof, such as a transceiver) may transmit the first configuration signal indicating a first configuration including resources for PUCCH, and may transmit the second configuration signal indicating a second configuration including resources for sensing.

[0221] In some examples, processes 1900 and 2000 may be executed by one or more computing devices or apparatuses. In some exemplary examples, process 1900 may be executed by... Figure 17 Network equipment 1720, Figure 18 Network device 1820 and / or one or more computing devices or systems (e.g., Figure 21 The process 2000 can be executed by a computing system 2100. In one or more exemplary examples, the process 2000 may be executed by... Figure 17 Network Entity 1710 Figure 18 Network entity 1810 and / or one or more computing devices or systems (e.g. Figure 21 The computing device or apparatus may be used to perform the steps of process 1900 and / or process 2000. In some cases, such computing device or apparatus may include a processor, microprocessor, microcomputer or other component of the device configured to perform the steps of process 1900 and / or process 2000. Such computing device may further include a network interface configured to communicate data.

[0222] Components that enable the implementation of a computing device in a circuit. For example, a component may include electronic circuitry or other electronic hardware, and / or may be implemented using electronic circuitry or other electronic hardware, which may include one or more programmable electronic circuits (e.g., a microprocessor, graphics processing unit (GPU), digital signal processor (DSP), central processing unit (CPU), and / or other suitable electronic circuitry), and / or may include computer software, firmware, or any combination thereof for performing the various operations described herein, and / or may be implemented using computer software, firmware, or any combination thereof for performing the various operations described herein. The computing device may also include a display (as an example of an output device or as a supplement to an output device), a network interface configured to communicate and / or receive data, any combination thereof, and / or other components. The network interface may be configured to communicate and / or receive Internet Protocol (IP)-based data or other types of data.

[0223] Processes 1900 and 2000 are each illustrated as logic flowcharts, whose operations represent sequences of operations that can be implemented by hardware, computer instructions, or combinations thereof. In the context of computer instructions, each operation represents a computer-executable instruction stored on one or more computer-readable storage media that performs the described operation when executed by one or more processors. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc., that perform a specific function or implement a specific data type. The order in which the operations are described is not intended to be construed as limiting, and any number of described operations can be combined in any order and / or in parallel to implement the process.

[0224] Additionally, processes 1900 and 2000 can be executed under the control of one or more computer systems configured with executable instructions, and can be implemented in hardware as code (e.g., executable instructions, one or more computer programs, or one or more applications) that executes jointly on one or more processors, or a combination thereof. As noted above, the code can be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising multiple instructions executable by one or more processors. The computer-readable or machine-readable storage medium can be non-transitory.

[0225] Figure 21 This is a block diagram illustrating an example of a computing system 2100 that can be employed by the disclosed system for reusing FMCW for PUCCH and sensing. Specifically, Figure 21An example of computing system 2100 is illustrated. This computing system can be any computing device, such as constituting an internal computing system, a remote computing system, a camera, or any component thereof, wherein the components of the system communicate with each other using connection 2105. Connection 2105 can be a physical connection using a bus, or a direct connection to processor 2110, such as in a chipset architecture. Connection 2105 can also be a virtual connection, a networking connection, or a logical connection.

[0226] In some aspects, computing system 2100 is a distributed system, wherein the functions described herein can be distributed within a data center, multiple data centers, a peer-to-peer network, etc. In some aspects, one or more system components described represent a plurality of such components that each perform a function described for some or all of the functions. In some aspects, components can be physical or virtual devices.

[0227] Example system 2100 includes at least one processing unit (CPU or processor) 2110 and a connection 2105 that communicatively couples various system components, including system memories 2115 such as read-only memory (ROM) 2120 and random access memory (RAM) 2125, to processor 2110. Computing system 2100 may include a cache 2112 of high-speed memory that is directly connected to, closely proximate to, or integrated into processor 2110.

[0228] Processor 2110 may include any general-purpose processor and hardware or software services, such as services 2132, 2134, and 2136 stored in storage device 2130, which are configured to control processor 2110 and dedicated processors in which software instructions are incorporated into the actual processor design. Processor 2110 may be a substantially completely independent computing system, including multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

[0229] To enable user interaction, the computing system 2100 includes an input device 2145 that can represent any number of input mechanisms, such as a microphone for voice, a touch-sensitive screen for gesture or graphic input, a keyboard, a mouse, motion input, voice input, etc. The computing system 2100 may also include an output device 2135 that can be one or more of a plurality of output mechanisms. In some instances, a multi-mode system allows the user to provide multiple types of input / output to communicate with the computing system 2100.

[0230] The computing system 2100 may include a communication interface 2140, which typically controls and manages user input and system output. The communication interface may perform or facilitate the receiving and / or transmitting of wired or wireless communications using wired and / or wireless transceivers, including utilizing audio jacks / plugs, microphone jacks / plugs, Universal Serial Bus (USB) ports / plugs, Apple... ™ Lightning ™ Ports / plugs, Ethernet ports / plugs, fiber optic ports / plugs, dedicated wired ports / plugs, 3G, 4G, 5G and / or other cellular data network wireless signal transmission, Bluetooth ™ Wireless signal transmission, Bluetooth ™ Low-power (BLE) wireless signal transmission, IBEACON ™ Wireless signal transmission, radio frequency identification (RFID) wireless signal transmission, near field communication (NFC) wireless signal transmission, dedicated short range communication (DSRC) wireless signal transmission, 802.11 Wi-Fi wireless signal transmission, wireless local area network (WLAN) signal transmission, visible light communication (VLC), microwave access global interoperability (WiMAX), infrared (IR) wireless signal transmission, public switched telephone network (PSTN) signal transmission, integrated services digital network (ISDN) signal transmission, self-organizing network signal transmission, radio wave signal transmission, microwave signal transmission, infrared signal transmission, visible light signal transmission, ultraviolet light signal transmission, wireless signal transmission along the electromagnetic spectrum, or those communications in some combination thereof.

[0231] The communication interface 2140 may also include one or more ranging sensors (e.g., LIDAR sensors, laser rangefinders, RF radars, ultrasonic sensors, and infrared (IR) sensors) configured to collect data and provide measurements to the processor 2110, wherein the processor 2110 may be configured to perform determinations and calculations required to obtain various measurements for the one or more ranging sensors. In some examples, measurements may include time of flight, wavelength, azimuth, elevation, distance, linear rate, and / or angular rate, or any combination thereof. The communication interface 2140 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers used to determine the location of the computing system 2100 based on one or more signals received from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the U.S. GPS, the Russian GLONASS, the Chinese BeiDou Navigation Satellite System (BDS), and the European Galileo GNSS. There are no limitations on operation on any particular hardware arrangement, and therefore the basic features here can be easily replaced to obtain improved hardware or firmware arrangements as they are developed.

[0232] Storage device 2130 may be a non-volatile and / or non-transitory and / or computer-readable storage device, and may be a hard disk or other type of computer-readable medium capable of storing data accessible by a computer, such as magnetic tape, flash memory cards, solid-state storage devices, digital versatile discs, cartridges, floppy disks, hard disks, magnetic tapes, magnetic stripes, any other magnetic storage media, flash memory, memristor memory, any other solid-state storage, CD-ROM, rewritable CD, digital video disc (DVD), Blu-ray Disc (BDD), holographic disc, another optical medium, secure digital (SD) card, micro-secure digital (microSD) card, Memory Stick. ®Cards, smart card chips, EMV chips, Subscriber Identity Module (SIM) cards, mini / micro / nano / micro SIM cards, another integrated circuit (IC) chip / card, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash EPROM, cache memory (e.g., layer 1 (L1) cache, layer 2 (L2) cache, layer 3 (L3) cache, layer 4 (L4) cache, layer 5 (L5) cache or other (L#) cache), resistive random access memory (RRAM / ReRAM), phase change memory (PCM), spin-transfer torque RAM (STT-RAM), another memory chip or cassette and / or combinations thereof.

[0233] Storage device 2130 may include software services, servers, services, etc., which enable the system to perform functions when the code defining such software is executed by processor 2110. In some aspects, hardware services performing specific functions may include software components for performing functions stored in a computer-readable medium connected to necessary hardware components such as processor 2110, connection 2105, output device 2135, etc. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions and / or data. Computer-readable media may include non-transitory media in which data can be stored and which does not include carrier waves and / or transient electronic signals propagating wirelessly or over a wired connection. Examples of non-transitory media may include, but are not limited to, magnetic disks or magnetic tapes, optical storage media such as compact discs (CDs) or digital versatile discs (DVDs), flash memory, memory, or memory devices. Computer-readable media may store code and / or machine-executable instructions thereon, which may represent procedures, functions, subroutines, programs, routines, subroutines, modules, software packages, classes, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or hardware circuitry by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc., may be passed, forwarded, or transmitted via any suitable means, including memory sharing, message passing, token passing, network transmission, etc.

[0234] Specific details have been provided in the foregoing description to offer a thorough understanding of the aspects and examples presented herein, but those skilled in the art will recognize that this application is not limited thereto. Therefore, although illustrative aspects of this application have been described in detail herein, it is to be understood that the various inventive concepts may be embodied and employed in various other ways, and the appended claims are not intended to be construed as including these variations unless limited by prior art. The various features and aspects of the applications described above may be used individually or in combination. Furthermore, without departing from the broader scope of this specification, aspects may be used in any number of environments and applications beyond those described herein. Therefore, the specification and drawings should be considered illustrative rather than restrictive. For illustrative purposes, the methods are described in a particular order. It should be understood that, in alternative aspects, the methods may be performed in a different order than described.

[0235] For clarity, in some instances, this technology may be presented as comprising individual functional blocks, which include devices, device components, steps, or routines embodied in a method, either in software or a combination of hardware and software. Additional components may be used in addition to those shown in the figures and / or described herein. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form to avoid obscuring these aspects in unnecessary detail. In other cases, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the aspects.

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

[0237] Various aspects described above can be presented as processes or methods, depicted as flowcharts, diagrams, data flow graphs, structure diagrams, or block diagrams. Although flowcharts can describe operations as sequential processes, many operations within an operation can be executed in parallel or concurrently. Furthermore, the order of operations can be rearranged. A process terminates when its operations are completed, but a process may have additional steps not included in the accompanying diagrams. A process can correspond to a method, function, procedure, subroutine, subroutine, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function or the main function.

[0238] The processes and methods described in the examples above can be implemented using stored computer-executable instructions or computer-executable instructions otherwise obtainable from a computer-readable medium. Such instructions may include, for example, instructions and data that configure a general-purpose computer, special-purpose computer, or processing device to perform a function or group of functions. The portion may be accessible via a network of the computer resources used. The computer-executable instructions may be, for example, binary, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that can be used to store the instructions, the information used, and / or information created during the methods according to the described examples include disks or optical discs, flash memory, USB devices with non-volatile memory, networked storage devices, etc.

[0239] In some respects, computer-readable storage devices, media, and memories may include cables or wireless signals containing bit streams, etc. However, when referred to, non-transitory computer-readable storage media explicitly exclude media such as energy, carrier signals, electromagnetic waves, and the signals themselves.

[0240] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may, in some cases, be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0241] The various exemplary logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or performed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and may take any form factor of various form factors. When implemented in software, firmware, middleware, or microcode, program code or code segments (e.g., computer program products) for performing necessary tasks may be stored in a computer-readable or machine-readable medium. A processor may perform the necessary tasks. Examples of form factors include: laptop computers, smartphones, mobile phones, tablet devices, or other small form factor personal computers, personal digital assistants, rack-mount devices, self-contained devices, etc. The functionality described herein may also be embodied in peripheral devices or interlocking cards. By further example, such functionality may also be implemented on circuit boards of different chips or different processes executed on a single device.

[0242] Instructions, media for transmitting such instructions, computing resources for executing them, and other structures for supporting such computing resources are example components for providing the functionality described in this disclosure.

[0243] The techniques described herein can also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques can be implemented in any of a variety of devices, such as general-purpose computers, wireless communication devices (mobile phones), or integrated circuit devices with multiple uses, including applications in wireless communication devices (mobile phones) and other devices. Any feature described as a module or component can be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques can be implemented at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, perform one or more of the methods, algorithms, and / or operations described above. The computer-readable data storage medium can form part of a computer program product, which may include packaging material. The computer-readable medium may include memory or data storage media, such as random access memory (RAM) (such as synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, etc. Additionally or alternatively, the technology may be implemented at least in part by a computer-readable communication medium that carries or conveys program code in the form of instructions or data structures that can be accessed, read and / or executed by a computer, such as propagated signals or waves.

[0244] The program code can be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Such processors can be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor; however, in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Therefore, as used herein, the term "processor" may refer to any of the foregoing structures, any combination of the foregoing structures, or any other structure or means suitable for implementing the techniques described herein.

[0245] Those skilled in the art will understand that, without departing from the scope of this description, the less than (“<”) and greater than (“>”) symbols or terms used herein may be replaced with less than or equal to (“>”) respectively. ") and greater than or equal to (" The symbol ) is used instead.

[0246] When a component is described as being “configured” to perform certain operations, such configuration can be achieved, for example, by designing electronic circuits or other hardware to perform the operations, by programming programmable electronic circuits (e.g., microprocessors or other suitable electronic circuits) to perform the operations, or any combination thereof.

[0247] The phrase “coupled to” or “communicatively coupled to” means that any component is physically connected directly or indirectly to another component, and / or that any component is in communication with another component directly or indirectly (e.g., connected to that other component via a wired or wireless connection and / or other suitable communication interface).

[0248] The claim language or other language that states "at least one of" and / or "one or more of" in a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, the claim language that states "at least one of A and B" or "at least one of A or B" means A, B, or A and B. In another example, the claim language that states "at least one of A, B, and C" or "at least one of A, B, or C" means A, B, C, or A and B, or A and C, or B and C, A and B and C, or any repetition is information or data (e.g., A and A, B and B, C and C, A and A and B, etc.), or any other ordering, repetition, or combination of A, B, and C. The language "at least one of" and / or "one or more of" in a set does not limit the set to the items listed in the set. For example, the language of a claim stating "at least one of A and B" or "at least one of A or B" may refer to A, B, or A and B, and may additionally include items not listed in the set of A and B. The phrases "at least one" and "one or more" are used interchangeably herein.

[0249] Claims using phrases such as "at least one processor, at least one processor is configured to," "at least one processor is configured to," "one or more processors, one or more processors are configured to," or other languages ​​indicate that one or more processors (in any combination) are capable of performing associated operations. For example, a claim using the phrase "at least one processor, the at least one processor is configured to: X, Y, and Z" means that a single processor can be used to perform operations X, Y, and Z; or that multiple processors are each assigned a specific subset of tasks to perform operations X, Y, and Z, such that the multiple processors together perform X, Y, and Z; or that a group of multiple processors work together to perform operations X, Y, and Z. In another example, a claim using the phrase "at least one processor, the at least one processor is configured to: X, Y, and Z" could mean that any single processor can perform only a subset of operations X, Y, and Z.

[0250] When referring to one or more elements that perform functions (e.g., steps of a method), one element may perform all functions, or more than one element may jointly perform these functions. When more than one element jointly performs these functions, each function does not need to be performed by every single element (e.g., different functions may be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements may perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform functions, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions.

[0251] When referring to an entity that performs or is configured to perform functions (e.g., steps of a method) (e.g., any entity or device described herein), the entity may be configured to cause one or more elements (individually or collectively) to perform those functions. One or more components of the entity may include at least one memory, at least one processor, at least one communication interface, another component configured to perform one or more of those functions, and / or any combination thereof. When referring to an entity that performs functions, the entity may be configured to cause one component to perform all functions, or to cause more than one component to perform those functions collectively. When the entity is configured to cause more than one component to perform those functions collectively, each function does not need to be performed by every single component (e.g., different functions may be performed by different components), and / or each function does not need to be performed by only one component as a whole (e.g., different components may perform different sub-functions of a function).

[0252] The various exemplary logic blocks, modules, engines, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, firmware, or combinations thereof. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, engines, modules, circuits, and steps have been broadly described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this application.

[0253] The techniques described herein can also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques can be implemented in any of a variety of devices, such as general-purpose computers, wireless communication devices (mobile phones), or integrated circuit devices with multiple uses, including applications in wireless communication devices (mobile phones) and other devices. Any feature described as an engine, module, or component can be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, these techniques can be implemented at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, perform one or more of the methods described above. The computer-readable data storage medium can form part of a computer program product, which may include packaging material. The computer-readable medium may include memory or data storage media, such as random access memory (RAM) (such as synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, etc. Additionally or alternatively, the technology may be implemented at least in part by a computer-readable communication medium that carries or conveys program code in the form of instructions or data structures that can be accessed, read and / or executed by a computer, such as propagated signals or waves.

[0254] The program code can be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Such processors can be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor; however, in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Therefore, as used herein, the term "processor" may refer to any of the foregoing structures, any combination of the foregoing structures, or any other structure or means suitable for implementing the techniques described herein. Furthermore, in some aspects, the functionality described herein may be provided within dedicated software or hardware modules configured for encoding and decoding, or incorporated into a combined video encoder-decoder (CODEC).

[0255] The exemplary aspects of this disclosure include: Aspect 1. A network device for wireless communication and sensing, the network device comprising: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and configured to: receive from a network entity at least one configuration signal indicating at least one configuration, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; output the PUCCH for transmission to the network entity based on the at least one configuration including the resources; and output a sensing signal for transmission based on the at least one configuration including the resources.

[0256] Aspect 2. The network device according to aspect 1, wherein the resource is transmitted using frequency modulated continuous wave (FMCW).

[0257] Aspect 3. The network device according to aspect 2, wherein the FMCW is used as a base sequence for the PUCCH.

[0258] Aspect 4. The network device according to aspect 3, wherein the FMCW has a slope associated with the base sequence.

[0259] Aspect 5. The network device according to any one of Aspects 3 or 4, wherein the FMCW has a symbol-level orthogonal overlay code (OCC) associated with the base sequence.

[0260] Aspect 6. The network device according to any one of Aspects 3 to 5, wherein the FMCW has a cyclic shift associated with the base sequence.

[0261] Aspect 7. The network device according to any one of Aspects 3 to 6, wherein the FMCW has a zero-tail length associated with the base sequence.

[0262] Aspect 8. The network device according to any one of Aspects 3 to 7, wherein the FMCW has a triangular chirp associated with the base sequence.

[0263] Aspect 9. The network device according to any one of Aspects 3 to 8, wherein the at least one processor is configured to encode uplink control information (UCI) based on the base sequence.

[0264] Aspect 10. The network device according to any one of Aspects 1 to 9, wherein the at least one processor is configured to output capability information indicating one or more base sequence methods for PUCCH and sensing supported by the network device for transmission to the network entity.

[0265] Aspect 11. The network device according to any one of Aspects 1 to 10, wherein the at least one configuration is a semi-persistent configuration or a dynamic configuration.

[0266] Aspect 12. The network device according to any one of aspects 1 to 11, wherein the at least one processor is configured to receive a reflected signal generated by the sensing signal reflected from an object.

[0267] Aspect 13. The network device according to any one of Aspects 1 to 12, wherein the network device is a user equipment (UE).

[0268] Aspect 14. The network device according to any one of Aspects 1 to 13, wherein the network entity is one of a base station or a network server.

[0269] Aspect 15. The network device according to any one of Aspects 1 to 14, wherein, in order to receive the at least one configuration signal, the at least one processor is configured to receive a configuration signal indicating configuration, the configuration including for the PUCCH and for the sensed resources.

[0270] Aspect 16. The network device according to any one of Aspects 1 to 15, wherein, in order to receive the at least one configuration signal, the at least one processor is configured to: receive a first configuration signal indicating a first configuration, the first configuration including the resources for the PUCCH; and receive a second configuration signal indicating a second configuration, the second configuration including the resources for the sensing.

[0271] Aspect 17. A network entity for wireless communication and sensing, the network entity comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to: output at least one configuration signal indicating at least one configuration for transmission to a network device, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; and receive the PUCCH from the network device based on the at least one configuration including the resources.

[0272] Aspect 18. The network entity according to aspect 17, wherein the at least one processor is configured to receive a reflected signal generated by a sensing signal reflected from an object, wherein the sensing signal is based on the resource.

[0273] Aspect 19. The network entity according to any one of Aspects 17 or 18, wherein the resource is received via Frequency Modulated Continuous Wave (FMCW).

[0274] Aspect 20. The network entity according to aspect 19, wherein the FMCW is used as a base sequence for the PUCCH.

[0275] Aspect 21. The network entity according to aspect 20, wherein the FMCW has a slope associated with the base sequence.

[0276] Aspect 22. The network entity according to any one of Aspects 20 or 21, wherein the FMCW has a symbol-level orthogonal cover code (OCC) associated with the base sequence.

[0277] Aspect 23. The network entity according to any one of Aspects 20 to 22, wherein the FMCW has a cyclic shift associated with the base sequence.

[0278] Aspect 24. The network entity according to any one of Aspects 20 to 23, wherein the FMCW has a zero-tail length associated with the base sequence.

[0279] Aspect 25. The network entity according to any one of Aspects 20 to 24, wherein the FMCW has a triangular chirp associated with the base sequence.

[0280] Aspect 26. The network entity according to any one of Aspects 17 to 25, wherein the at least one processor is configured to receive from the network device capability information indicating one or more base sequence methods for PUCCH and sensing supported by the network device.

[0281] Aspect 27. The network entity according to any one of Aspects 17 to 26, wherein the at least one configuration is a semi-persistent configuration or a dynamic configuration.

[0282] Aspect 28. The network entity according to any one of Aspects 17 to 27, wherein the network device is a user equipment (UE).

[0283] Aspect 29. The network entity according to any one of Aspects 17 to 28, wherein the network entity is one of a base station or a network server.

[0284] Aspect 30. The network entity according to any one of Aspects 17 to 29, wherein, in order to output the at least one configuration signal, the at least one processor is configured to output a configuration signal indicating a configuration, the configuration including for the PUCCH and for the sensed resources.

[0285] Aspect 31. The network entity according to any one of Aspects 17 to 30, wherein, in order to output the at least one configuration signal, the at least one processor is configured to: output a first configuration signal indicating a first configuration, the first configuration including the resources for the PUCCH; and output a second configuration signal indicating a second configuration, the second configuration including the resources for the sensing.

[0286] Aspect 32. A method for wireless communication and sensing at a network device, the method comprising: receiving from a network entity at least one configuration signal indicating at least one configuration, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; transmitting the PUCCH to the network entity based on the at least one configuration including the resources; and transmitting a sensing signal based on the at least one configuration including the resources.

[0287] Aspect 33. The method according to aspect 32, wherein the resource is transmitted using frequency modulated continuous wave (FMCW).

[0288] Aspect 34. The method according to aspect 33, wherein the FMCW is used as a base sequence for the PUCCH.

[0289] Aspect 35. The method according to aspect 34, wherein the FMCW has a slope associated with the base sequence.

[0290] Aspect 36. The method according to any one of Aspects 34 or 35, wherein the FMCW has a symbol-level orthogonal cover code (OCC) associated with the base sequence.

[0291] Aspect 37. The method according to any one of Aspects 34 to 36, wherein the FMCW has a cyclic shift associated with the base sequence.

[0292] Aspect 38. The method according to any one of Aspects 34 to 37, wherein the FMCW has a zero-tail length associated with the base sequence.

[0293] Aspect 39. The method according to any one of Aspects 34 to 38, wherein the FMCW has a triangular chirp associated with the base sequence.

[0294] Aspect 40. The method according to any one of Aspects 34 to 39, the method further comprising encoding uplink control information (UCI) by the network device based on the base sequence.

[0295] Aspect 41. The method according to any one of aspects 32 to 40, the method further comprising sending to the network entity capability information indicating one or more base sequence methods for PUCCH and sensing supported by the network device.

[0296] Aspect 42. The method according to any one of aspects 32 to 41, wherein the at least one configuration is a semi-persistent configuration or a dynamic configuration.

[0297] Aspect 43. The method according to any one of aspects 32 to 42, the method further comprising receiving a reflected signal generated by the sensing signal reflected from the object.

[0298] Aspect 44. The method according to any one of Aspects 32 to 43, wherein the network device is a user equipment (UE).

[0299] Aspect 45. The method according to any one of Aspects 32 to 44, wherein the network entity is one of a base station or a network server.

[0300] Aspect 46. The method according to any one of aspects 32 to 45, wherein receiving the at least one configuration signal includes receiving a configuration signal indicating configuration, the configuration including for the PUCCH and for the sensing of the resource.

[0301] Aspect 47. The method according to any one of Aspects 32 to 46, wherein receiving the at least one configuration signal comprises: receiving a first configuration signal indicating a first configuration, the first configuration including the resources for the PUCCH; and receiving a second configuration signal indicating a second configuration, the second configuration including the resources for the sensing.

[0302] Aspect 48. A method for wireless communication and sensing at a network entity, the method comprising: sending to a network device at least one configuration signal indicating at least one configuration, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; and receiving the PUCCH from the network device based on the at least one configuration including the resources.

[0303] Aspect 49. The method according to aspect 48, the method further comprising receiving a reflected signal generated by a sensing signal reflected from an object, wherein the sensing signal is based on the resource.

[0304] Aspect 50. The method according to any one of Aspects 48 or 49, wherein the resource is received via frequency modulated continuous wave (FMCW).

[0305] Aspect 51. The method according to aspect 50, wherein the FMCW is used as a base sequence for the PUCCH.

[0306] Aspect 52. The method according to aspect 51, wherein the FMCW has a slope associated with the base sequence.

[0307] Aspect 53. The method according to any one of Aspects 51 or 52, wherein the FMCW has a symbol-level orthogonal overlay code (OCC) associated with the base sequence.

[0308] Aspect 54. The method according to any one of aspects 51 to 53, wherein the FMCW has a cyclic shift associated with the base sequence.

[0309] Aspect 55. The method according to any one of Aspects 51 to 54, wherein the FMCW has a zero-tail length associated with the base sequence.

[0310] Aspect 56. The method according to any one of aspects 51 to 55, wherein the FMCW has a triangular chirp associated with the base sequence.

[0311] Aspect 57. The method according to any one of aspects 48 to 56, the method further comprising receiving from the network device capability information indicating one or more base sequence methods for PUCCH and sensing supported by the network device.

[0312] Aspect 58. The method according to any one of aspects 48 to 57, wherein the at least one configuration is a semi-persistent configuration or a dynamic configuration.

[0313] Aspect 59. The method according to any one of Aspects 48 to 58, wherein the network device is a user equipment (UE).

[0314] Aspect 60. The method according to any one of Aspects 48 to 59, wherein the network entity is one of a base station or a network server.

[0315] Aspect 61. The method according to any one of aspects 48 to 60, wherein sending the at least one configuration signal includes sending a configuration signal indicating configuration, the configuration including for the PUCCH and for the sensing of the resource.

[0316] Aspect 62. The method according to any one of aspects 48 to 61, wherein sending the at least one configuration signal comprises: sending a first configuration signal indicating a first configuration, the first configuration including the resources for the PUCCH; and sending a second configuration signal indicating a second configuration, the second configuration including the resources for the sensing.

[0317] Aspect 63. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by one or more processors, cause the one or more processors to perform any one of aspects 32 to 47.

[0318] Aspect 64. An apparatus for wireless communication and sensing, the apparatus comprising one or more components for performing operations according to any one of aspects 32 to 47.

[0319] Aspect 65. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by one or more processors, cause the one or more processors to perform any one of aspects 48 to 62.

[0320] Aspect 66. An apparatus for wireless communication and sensing, the apparatus comprising one or more components for performing operations according to any one of aspects 48 to 62.

[0321] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein an element referred to in the singular is not intended to mean "one and only one," but rather "one or more" unless specifically stated otherwise.

Claims

1. A network device for wireless communication and sensing, the network device comprising: At least one memory; and At least one processor, the at least one processor being coupled to the at least one memory and being configured to: Receive at least one configuration signal from a network entity indicating at least one configuration, said at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; The PUCCH is output based on at least one configuration including the resources for transmission to the network entity; and The sensing signal is output for transmission based on the at least one configuration including the resources.

2. The network device of claim 1, wherein the resource is transmitted using frequency modulated continuous wave (FMCW).

3. The network device according to claim 2, wherein the FMCW is used as a base sequence for the PUCCH.

4. The network device of claim 3, wherein the FMCW has a slope associated with the base sequence.

5. The network device of claim 3, wherein the FMCW has a symbol-level orthogonal overlay code (OCC) associated with the base sequence.

6. The network device of claim 3, wherein the FMCW has a cyclic shift associated with the base sequence.

7. The network device of claim 3, wherein the FMCW has a zero-tail length associated with the base sequence.

8. The network device of claim 3, wherein the FMCW has a triangular chirp associated with the base sequence.

9. The network device of claim 3, wherein the at least one processor is configured to encode uplink control information (UCI) based on the base sequence.

10. The network device of claim 1, wherein the at least one processor is configured to output capability information indicating one or more base sequence methods for PUCCH and sensing supported by the network device for transmission to the network entity.

11. The network device of claim 1, wherein the at least one configuration is a semi-persistent configuration or a dynamic configuration.

12. The network device of claim 1, wherein the at least one processor is configured to receive a reflected signal generated by the sensing signal reflected from an object.

13. The network device of claim 1, wherein the network device is a user equipment (UE).

14. The network device according to claim 1, wherein the network entity is either a base station or a network server.

15. The network device of claim 1, wherein, in order to receive the at least one configuration signal, the at least one processor is configured to receive a configuration signal indicating configuration, the configuration including for the PUCCH and for the sensed resources.

16. The network device of claim 1, wherein, in order to receive the at least one configuration signal, the at least one processor is configured to: Receive a first configuration signal indicating a first configuration, the first configuration including the resources for the PUCCH; and Receive a second configuration signal indicating a second configuration, the second configuration including the resources for the sensing.

17. A network entity for wireless communication and sensing, the network entity comprising: At least one memory; and At least one processor, the at least one processor being coupled to the at least one memory and being configured to: The output indicates at least one configuration signal for transmission to a network device, said at least one configuration including resources for the Physical Uplink Control Channel (PUCCH) and for sensing; and The PUCCH is received from the network device based on at least one configuration including the resources.

18. The network entity of claim 17, wherein the at least one processor is configured to receive a reflected signal generated from a sensing signal reflected from an object, wherein the sensing signal is based on the resource.

19. The network entity of claim 17, wherein the resource is received via frequency modulated continuous wave (FMCW).

20. The network entity of claim 19, wherein the FMCW is used as a base sequence for the PUCCH.

21. The network entity of claim 20, wherein the FMCW has at least one of the following: a slope associated with the base sequence, a symbol-level orthogonal cover code (OCC) associated with the base sequence, a cyclic shift associated with the base sequence, a zero-tail length associated with the base sequence, or a triangular chirp associated with the base sequence.

22. The network entity of claim 17, wherein the at least one processor is configured to receive from the network device capability information indicating one or more base sequence methods supported by the network device for PUCCH and sensing.

23. The network entity of claim 17, wherein the at least one configuration is a semi-persistent configuration or a dynamic configuration.

24. The network entity of claim 17, wherein the network device is a user equipment (UE).

25. The network entity of claim 17, wherein, in order to output the at least one configuration signal, the at least one processor is configured to output a configuration signal indicating a configuration, the configuration including for the PUCCH and for the sensed resources.

26. The network entity of claim 17, wherein, in order to output the at least one configuration signal, the at least one processor is configured to: Output a first configuration signal indicating a first configuration, the first configuration including the resources for the PUCCH; and The output indicates a second configuration signal, which includes the resources used for the sensing.

27. A method for wireless communication at a network device, the method comprising: The network device receives from the network entity at least one configuration signal indicating at least one configuration, the at least one configuration including a physical uplink control channel (PUCCH) and resources for sensing; The network device sends the PUCCH to the network entity based on at least one configuration including the resources. as well as The network device transmits sensing signals based on at least one configuration including the resources.

28. The method of claim 27, wherein the resource is transmitted using frequency modulated continuous wave (FMCW).

29. A method for conducting wireless communication at a network entity, the method comprising: The network entity sends at least one configuration signal to the network device indicating at least one configuration, the at least one configuration including resources for the Physical Uplink Control Channel (PUCCH) and for sensing. as well as The network entity receives the PUCCH from the network device based on at least one configuration including the resources.

30. The method of claim 29, wherein the resource is received via frequency modulated continuous wave (FMCW).

Images