Integrated sensing and communication (ISAC) waveform based on a guard interval (GI)

Abstract

In some implementations, a wireless device can perform integrated radio frequency (RF) sensing and communication by receiving, at the wireless device from a configuration node of a wireless network, a guard interval integrated sensing and communication (GI-ISAC) configuration, where the GI-ISAC configuration indicates a set of one or more parameters that describe characteristics of a GI-ISAC waveform to be used by the wireless device for RF sensing, and where the set of one or more parameters that describe characteristics of the GI-ISAC waveform is based at least in part on an orthogonal frequency-division multiplexing (OFDM) communication data symbol used by the wireless network. Further, the wireless device can utilize the wireless device to perform an RF sensing function in accordance with the GI-ISAC configuration.

Description

[0001] Related applications

[0002] This application claims the benefit of U.S. Application No. 18 / 624,473, filed April 2, 2024, entitled “GUARD INTERVAL (GI)-BASEDINTEGRATED SENSING AND COMMUNICATIONS (ISAC) WAVEFORM”, which has been assigned to the assignee of this application and is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates generally to the field of radio frequency (RF) sensing, and more specifically to RF sensing in wireless networks. Background Technology

[0004] RF sensing performed by wireless devices has a wide range of applications, including consumer, industrial, commercial, and others. RF sensing can be used to determine the presence of a target object, determine the location of a target object, and / or track the movement of a target object over time. Cellular networks (e.g., fifth-generation (5G) New Radio (NR) networks) and other types of wireless networks can perform RF sensing using base stations, user equipment (UEs), and / or other wireless devices communicatively coupled to the cellular network as "sensing nodes." Traditional cellular networks operate using an orthogonal frequency division multiplexing (OFDM) communication scheme that utilizes a cyclic prefix (CP), which may be referred to as CP-OFDM. Summary of the Invention

[0005] According to this specification, an example method for performing integrated radio frequency (RF) sensing and communication at a wireless device may include: receiving a guard interval integrated sensing and communication (GI-ISAC) configuration from a configuration node of a wireless network at the wireless device, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by the wireless device for RF sensing, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is based at least in part on orthogonal frequency division multiplexing (OFDM) communication data symbols used by the wireless network. The method may also include utilizing the wireless device to perform RF sensing functionality according to the GI-ISAC configuration.

[0006] According to this specification, an example method for implementing integrated radio frequency (RF) sensing and communication at a configuration node of a wireless network may include: determining a guard interval integrated sensing and communication (GI-ISAC) configuration, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by a wireless device to perform RF sensing functions, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on orthogonal frequency division multiplexing (OFDM) communication data symbols used by the wireless network. The method may further include: transmitting the GI-ISAC configuration to the wireless device.

[0007] According to this specification, an example wireless device may include: one or more transceivers, one or more memories, and one or more processors communicatively coupled to the one or more transceivers and the one or more memories. The one or more processors are configured to receive, at the wireless device, a Guard-Interval Integrated Sensing and Communication (GI-ISAC) configuration from a configuration node of a wireless network, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by the wireless device for RF sensing, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on Orthogonal Frequency Division Multiplexing (OFDM) communication data symbols used by the wireless network. The one or more processors are also configured to perform RF sensing functions using the one or more transceivers according to the GI-ISAC configuration.

[0008] According to this specification, an example configuration node may include: one or more transceivers, one or more memories, and one or more processors communicatively coupled to the one or more transceivers and the one or more memories. The one or more processors are configured to: determine a Guard Interval Integrated Sensing and Communication (GI-ISAC) configuration, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by a wireless device to perform radio frequency (RF) sensing functions, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on Orthogonal Frequency Division Multiplexing (OFDM) communication data symbols used by the wireless network. The one or more processors are further configured to: transmit the GI-ISAC configuration to the wireless device via the one or more transceivers.

[0009] This invention is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used alone to define the scope of the claimed subject matter. This subject matter should be understood with reference to the appropriate portions of this disclosure, any or all of the accompanying drawings, and each claim. The foregoing, as well as other features and examples, will be described in more detail in the following description, claims, and drawings. Attached Figure Description

[0010] Figure 1 This is an example of a positioning / sensing system that, according to the implementation scheme, can use the techniques provided herein to perform (RF) sensing using guard interval integrated sensing and communication (GI-ISAC) waveforms.

[0011] Figure 2 This is a diagram of a fifth-generation (5G) new radio (NR) positioning / sensing system according to the implementation plan.

[0012] Figure 3 This is a diagram illustrating an example of an RF sensing system according to an implementation scheme.

[0013] Figure 4 These are illustrations of different ways of implementing Integrated Sensing and Communication (ISAC) based on some implementation schemes.

[0014] Figure 5 This is a diagram illustrating examples of resource usage for different beams.

[0015] Figure 6 This is an example illustration that provides a comparison between traditional cyclic prefix (CP) based symbols and guard interval (GI) based symbols.

[0016] Figure 7 This is a call flowchart illustrating the process by which a client node can request and receive GI-ISAC measurement information according to some implementation schemes.

[0017] Figure 8 This is a flowchart illustrating an exemplary process for performing integrated radio frequency (RF) sensing and communication according to some implementation schemes.

[0018] Figure 9 This is a flowchart illustrating an exemplary process for supporting integrated radio frequency (RF) sensing and communication according to some implementation schemes.

[0019] Figure 10 This is a block diagram of an implementation scheme for a mobile sensing node.

[0020] Figure 11 This is a block diagram of an implementation scheme for a stationary sensing node.

[0021] Figure 12 It is a block diagram of the implementation scheme of the computer system.

[0022] Similar reference numerals in the various figures indicate similar elements according to certain example embodiments. Furthermore, multiple instances of an element can be indicated by adding a letter or hyphen after the first digit and a second digit. For example, multiple instances of element 110 may be indicated as 110-1, 110-2, 110-3, etc., or 110a, 110b, 110c, etc. When only the first digit is used to refer to such an element, it should be understood that any instance of the element (e.g., element 110 in the previous example would refer to elements 110-1, 110-2, and 110-3, or elements 110a, 110b, and 110c) is acceptable. The figures may be simplified for discussion purposes and may not reflect certain characteristics (e.g., size / dimensions, components, etc.) of embodiments used in real-world applications. Detailed Implementation

[0023] The following description is directed to certain specific implementations for the purpose of describing the innovative aspects of each implementation. However, those skilled in the art will readily recognize that the teachings herein can be applied in many different ways. The specific implementations described can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals according to any communication standard such as any of the following: the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4 standard for ultra-wideband (UWB), the IEEE 802.11 standard (including those identified as Wi-Fi), etc. ® (Technology standards), Bluetooth ® Standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunking Radio (TETRA), Wideband CDMA (W-CDMA), Evolved Data Optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision B, High Rate Packet Data (HRPD), High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolved High Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), Advanced Mobile Phone Systems (AMPS), or other known signals used for communication within wireless, cellular, or Internet of Things (IoT) networks, such as systems utilizing technologies of 3G, 4G, 5G, 6G, or further implementations thereof.

[0024] As used herein, an "RF signal" includes electromagnetic waves that transmit information through the space between a transmitter (or transmitting device) and a receiver (or receiving device). 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 individual RF signals through multiple channels or paths, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal.

[0025] As used herein, the terms “RF sensing,” “passive RF sensing,” and variations thereof refer to the process of detecting one or more objects (which may also be referred to as “targets”) using RF signals transmitted by a transmitting device and received by a receiving device after reflection from an object. In a monostatic configuration, the transmitting device and the receiving device are the same device. In a bistatic configuration, one device transmits RF signals, and another device receives these RF signals reflected from one or more objects. In a multistatic configuration, one or more receiving devices are separate from one or more transmitting devices. As used herein, the term “static” in the terms “monostatic,” “bistatic,” and “multistatic” (or “multi-static”) is intended to conform to historical literature on RF sensing but is not limited to “static” or stationary sensing nodes. As described herein, in some embodiments, the sensing node may be mobile. As described herein, the device performing RF sensing may be referred to as an “RF sensing node” or simply a “sensing node.” In bistatic or multistatic configurations, the transmitting device may be referred to as a "transmitting node," a "Tx sensing node," or a "Tx node," and the receiving device may be referred to as a "receiving node," an "Rx sensing node," or an "Rx node." The sensing node may be referred to as either or both in a monostatic configuration. As described in more detail below, the receiving device may measure these reflected RF signals to determine one or more characteristics of one or more objects, such as position, range, angle, orientation, Doppler, velocity, etc. According to some implementations, RF sensing may be "passive" because neither the receiving device nor the objects themselves need to transmit RF signals for the one or more objects to be detected.

[0026] Additionally, unless otherwise specified, references to “reference signal” and the like may refer to signals used for: the location of a user equipment (UE), the sensing of active and / or passive objects by one or more sensing nodes, or combinations thereof. As described in more detail herein, such signals may include any of a variety of signal types. This may include, but is not limited to, a location reference signal (PRS), a sounding reference signal (SRS), a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or any combination thereof.

[0027] The techniques described herein are applicable to “mmWave” technologies, which typically operate in the 57 GHz–71 GHz range, but may include frequencies ranging from 30 GHz–300 GHz. This includes frequencies used, for example, by the 802.11ad Wi-Fi standard (operating at 60 GHz). That is, some implementations may utilize RF sensing at frequencies outside this range. For example, in some implementations, the 5G NR band (e.g., 28 GHz) may be used. Since RF sensing can be performed in the same band as communication, hardware can be used for both communication and RF sensing. For example, one or more components of the RF sensing system described herein may be included in a wireless modem (e.g., a Wi-Fi or NR modem), a UE (e.g., an extension device), etc. Additionally, the techniques are applicable to RF signals of any pulse type, including compressed pulses (e.g., including Chirp sequences, Golay sequences, Barker sequences, Ipatov sequences, or m-sequences). That is, implementations are not limited to such frequencies and / or pulse types. Additionally, since the RF sensing system may be able to transmit RF signals for communication (e.g., using 802.11 or NR wireless technology), the implementation may utilize channel estimation and / or other communication-related functions to provide RF sensing functionality as described herein. Therefore, the pulse may be the same as the pulse used in at least some aspects.

[0028] As noted, RF sensing can be performed by wireless devices or sensing nodes and has a wide range of applications, including consumer, industrial, commercial, and others. RF sensing can utilize one or more sensing nodes and can be coordinated by a wireless network to detect and / or track or target objects. The ability to perform both RF sensing and communication (referred to as Integrated Sensing and Communication (ISAC) or Joint Sensing and Communication (JSC)) is a capability that standards organizations such as the 3rd Generation Partnership Project (3GPP) hope to support in future generations of cellular networks, such as 5G Advanced, 6G, and beyond. This can help support applications in a wide variety of fields, such as vehicle sensing and automation, unmanned aerial vehicles (UAVs), rail, gesture recognition, and more. Using a single ISAC waveform for both RF sensing and communication can be advantageous for various reasons, including the efficiency gains inherent in hardware and spectrum reuse. However, conventional orthogonal frequency division multiplexing (OFDM) communication schemes using cyclic prefixes (CP) (CP-OFDM) have several disadvantages in supporting RF sensing (described in more detail below).

[0029] The implementation described herein addresses these and other problems by proposing a guard interval (GI)-based ISAC waveform capable of supporting RF sensing and communication, including conventional CP-OFDM for communication. Various aspects generally relate to the field of RF sensing and communication. Some aspects more specifically relate to using GI-ISAC at a sensing node (e.g., a UE) using a guard interval-based integrated sensing and communication (GI-ISAC) configuration, which can be received by a configuration node (e.g., a base station or server) of the wireless network. The GI-ISAC configuration may include one or more parameters describing the characteristics of the GI-ISAC waveform, wherein the one or more parameters may be at least partially based on OFDM communication data symbols used by the wireless network.

[0030] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by utilizing common waveforms for RF sensing and communication, the embodiments can achieve efficiency gains through hardware and spectrum reuse, as noted above. Furthermore, by basing the GI-ISAC waveform on OFDM communication data symbols, the embodiments can help ensure that the GI-ISAC waveform is backward compatible and does not interfere with conventional CP-OFDM communication. These and other advantages will be apparent to those skilled in the art based on the disclosed embodiments detailed below. A discussion of the embodiments is provided following a discussion of the relevant technologies and context / background in which the embodiments can be used.

[0031] Figure 1This is a simplified illustration of a positioning / sensing system 100 according to an embodiment, which may be implemented in conjunction with or as part of a wireless communication system (e.g., a cellular communication network), wherein the mobile device 105, the location / sensing server 160, and / or other components of the positioning / sensing system 100 may use the techniques provided herein to utilize GI-ISAC waveforms. The techniques described herein may be implemented by one or more components of the positioning / sensing system 100; however, the techniques described herein are not limited to such components and may be implemented in other types of systems (not shown). The positioning / sensing system 100 may include: a mobile device 105; one or more satellites 110 (also referred to as spacecraft (SV)) for Global Navigation Satellite System (GNSS) (such as Global Positioning System (GPS), GLONASS, Galileo, or BeiDou) and / or NTN functionality; a base station 120; an access point (AP) 130; a location / sensing server 160; a network 170; and an external client 180. Generally, the positioning / sensing system 100 can estimate the position of the mobile device 105 based on RF signals received and / or transmitted from the mobile device 105 and the known positions of other components that transmit and / or receive RF signals (e.g., GNSS satellite 110, base station 120, AP 130). Additionally or alternatively, wireless devices such as the mobile device 105, base station 120, and satellite 110 (and / or other NTN platforms that may be implemented on aircraft, drones, balloons, etc.) can be used to perform positioning (e.g., positioning of one or more wireless devices) and / or RF sensing (e.g., RF sensing of one or more objects using RF signals transmitted by one or more wireless devices). Regarding... Figure 2 Additional details regarding location estimation / sensing techniques are discussed.

[0032] It should be pointed out that, Figure 1 Only generalized examples of various components are provided, any or all of which can be appropriately utilized, and each component can be repeated as needed. Specifically, although only one mobile device 105 is illustrated, it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) can utilize the positioning / sensing system 100. Similarly, the positioning / sensing system 100 may include a greater number of... Figure 1The illustrated base stations 120 and / or access points 130 may vary. The illustrated connections connecting the various components in the positioning / sensing system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, the components may be rearranged, combined, separated, replaced, and / or omitted depending on desired functionality. In some embodiments, for example, an external client 180 may connect directly to the location / sensing server 160. Those skilled in the art will recognize numerous modifications to the illustrated components.

[0033] Depending on the desired functionality, network 170 may include any of a variety of wireless and / or wired networks. Network 170 may include, for example, any combination of public and / or private networks, local area networks (LANs) and / or wide area networks (WANs). Furthermore, network 170 may utilize one or more wired and / or wireless communication technologies. In some implementations, network 170 may include, for example, cellular or other mobile networks, wireless local area networks (WLANs), wireless wide area networks (WWANs), and / or the Internet. Examples of network 170 include Long Term Evolution (LTE) wireless networks, fifth-generation (5G) wireless networks (also known as New Radio (NR) wireless networks or 5G NR wireless networks), Wi-Fi WLANs, and the Internet. LTE, 5G, and NR are wireless technologies defined or being defined by the Third Generation Partnership Project (3GPP). In LTE, 5G, or other cellular networks, mobile device 105 may be referred to as user equipment (UE). Network 170 may also include more than one network and / or more than one type of network.

[0034] Base station 120 and access point (AP) 130 are communicatively coupled to network 170. In some implementations, base station 120 may be owned, maintained, and / or operated by a cellular network provider and may employ any of a variety of wireless technologies, as described below. Depending on the technology of network 170, base station 120 may include a Node B, an evolved Node B (eNodeB or eNB), a transceiver base station (BTS), a radio base station (RBS), an NR Node B (gNB), a next-generation eNB (ng-eNB), etc. In the case that network 170 is a 5G network, base station 120, as a gNB or ng-eNB, may be part of a next-generation radio access network (NG-RAN) that can connect to a 5G core network (5GC). Given the Open Radio Access Network (O-RAN) and / or Virtualized Radio Access Network (V-RAN or vRAN) in 5G or later networks, the functionality performed by base station 120 in earlier networks (e.g., 3G and 4G) can be divided into different functional components (e.g., Radio Unit (RU), Distributed Unit (DU), and Central Unit (CU)) and layers (e.g., L1 / L2 / L3), which can be performed on different devices at different locations connected, for example, via fronthaul, midhaul, and backhaul connections. As mentioned herein, a “base station” (or ng-eNB, gNB, etc.) may include any or all of these functional components. For example, AP 130 may include a Wi-Fi AP or Bluetooth. ®An access point (AP) or an AP with cellular capabilities (e.g., 4G LTE and / or 5G NR). Therefore, mobile device 105 can transmit and receive information with network-connected devices (such as location / sensing server 160) via base station 120 accessing network 170 using a first communication link 133. Additionally or alternatively, because AP 130 is also communicatively coupled to network 170, mobile device 105 can communicate with network-connected devices and Internet-connected devices (including location / sensing server 160) using a second communication link 135 or via one or more other mobile devices 145. As used herein, the term "base station" generally refers to a single physical transmitting point or multiple co-located physical transmitting points that may be located at base station 120. A transmit / receive point (TRP) (also referred to as a transmit / receive point) corresponds to this type of transmitting point, and the term "TRP" may be used interchangeably with the terms "gNB," "ng-eNB," and "base station" herein. In some cases, base station 120 may include multiple TRPs—for example, where each TRP is associated with a different antenna or different antenna array of base station 120. As used herein, the transmitting functionality of a TRP may be performed by a transmitting point (TP), and / or the receiving functionality of a TRP may be performed by a receiving point (RP), which may be physically separate from or different from the TP. That is, a TRP may include both a TP and an RP. A physical transmitting point may include the antenna array of base station 120 (e.g., as in a multiple-input multiple-output (MIMO) system and / or in the case of beamforming at the base station). Depending on various aspects of the applicable 5G cellular standard, base station 120 (e.g., gNB) is capable of transmitting different “beams” in different directions and performing “beam scanning,” in which signals are transmitted in different directions (e.g., one after another) within different beams. The term “base station” as used herein may additionally refer to multiple non-co-located physical transmitting points, which 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).

[0035] As noted, satellite 110 can be used to implement NTN functionality, extend communications, positioning, and other potential functionalities of the terrestrial network (e.g., RF sensing). Thus, one or more satellites can be communicatively linked to one or more NTN gateways 150 (also referred to as "gateways," "earth stations," or "ground stations"). NTN gateway 150 can be communicatively linked to base station 120 via link 155. In some embodiments, NTN gateway 150 can act as a DU for base station 120, as previously described. This not only enables mobile device 105 to communicate with network 170 via satellite 110, but also enables network-based positioning, RF sensing, etc.

[0036] Satellite 110 can be utilized in one or more ways. For example, satellite 110 (also referred to as a spacecraft (SV)) can be part of a Global Navigation Satellite System (GNSS) such as Global Positioning System (GPS), GLONASS, Galileo, or BeiDou. Positioning using RF signals from GNSS satellites can include measuring multiple GNSS signals at a GNSS receiver on mobile device 105 to perform code-based and / or carrier-based positioning, which can be highly accurate. Additionally or alternatively, satellite 110 can be used for NTN-based positioning, wherein satellite 110 can functionally operate as a TRP (or TP) of a network (e.g., LTE and / or NR networks) and can be communicatively coupled to network 170. Specifically, reference signals (e.g., PRS) transmitted by satellite 110 for NTN-based positioning can be similar to those transmitted by base station 120 and can be coordinated by network function server 160, which can operate as a location server. In some embodiments, satellite 110 for NTN-based positioning can be different from those satellites used for GNSS-based positioning. In some implementations, NTN nodes may include non-ground vehicles, such as aircraft, balloons, drones, etc., which may supplement or replace NTN satellites. RF sensing may also be performed using NTN satellite 110 and / or other NTN platforms. As described in more detail below, satellites may use JCS symbols in orthogonal frequency division multiplexing (OFDM) waveforms to allow both RF sensing and / or positioning and communication.

[0037] As used herein, the term "cell" generally refers to a logical communication entity used to communicate with base station 120 and may be associated with an identifier (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) used to distinguish adjacent cells operating via the same or different operators. In some examples, a carrier may support multiple cells and may be configured with different cell types based on different protocol types that provide access for different types of devices (e.g., Machine Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocols). In some cases, the term "cell" may refer to a portion of the geographical coverage area (e.g., a sector) on which a logical entity operates.

[0038] Location / sensing server 160 may include servers and / or other computing devices configured to determine the estimated location of mobile device 105 and / or provide data (e.g., “auxiliary data”) to mobile device 105 to facilitate location measurement and / or location determination. According to some embodiments, location / sensing server 160 may include a Home Secure Subscriber Plane Positioning (SUPL) location platform (H-SLP) that supports SUPL subscriber plane (UP) positioning solutions defined by the Open Mobility Alliance (OMA) and can support location services for mobile device 105 based on subscription information for mobile device 105 stored in location / sensing server 160. In some embodiments, location / sensing server 160 may include Discovery SLP (D-SLP) or Emergency SLP (E-SLP). The location / sensing server 160 may also include an enhanced Serving Mobile Location Center (E-SMLC) that uses a control plane (CP) positioning solution to support the positioning of the mobile device 105 for LTE radio access. The location / sensing server 160 may also include a location management function (LMF) that uses a control plane (CP) positioning solution to support the positioning of the mobile device 105 for NR or LTE radio access.

[0039] In the CP positioning solution, from the perspective of network 170, signaling for controlling and managing the location of mobile device 105 can use existing network interfaces and protocols and be exchanged as signaling between the components of network 170 and with mobile device 105. In the UP positioning solution, from the perspective of network 170, signaling for controlling and managing the location of mobile device 105 can be exchanged as data (e.g., data transmitted using Internet Protocol (IP) and / or Transmit Control Protocol (TCP)) between location / sensing server 160 and mobile device 105.

[0040] As previously noted (and discussed in more detail below), the estimated location of mobile device 105 may be based on measurements of RF signals transmitted from and / or received by mobile device 105. Specifically, these measurements provide information about the relative distance and / or angle between mobile device 105 and one or more components in positioning / sensing system 100 (e.g., satellite 110, AP 130, base station 120). The estimated location of mobile device 105 may be estimated geometrically (e.g., using multi-angle measurements and / or multi-point positioning) based on distance (range) and / or angle measurements along with the known location of the one or more components.

[0041] Additionally or alternatively, location / sensing server 160 may be used as a sensing server. The sensing server may be used to coordinate and / or assist in coordinating the sensing of one or more objects (also referred to herein as “targets”) by one or more wireless devices in location / sensing system 100. This may include mobile device 105, base station 120, access point 130, other mobile device 145, satellite 110, or any combination thereof. Wireless devices capable of performing RF sensing may be referred to herein as “sensing nodes.” To perform RF sensing, the sensing server may coordinate a sensing session in which one or more RF sensing nodes may perform RF sensing by transmitting RF signals (e.g., reference signals (RS)) and measuring reflected signals or “echoes” (including reflections of the transmitted RF signals from one or more objects / targets). For example, reflected signals and object / target detection may be determined from channel state information (CSI) received at a receiving device. Sensing may include (i) monostatic sensing using a single device as both a transmitter (of the RF signal) and a receiver (of the reflected signal); (ii) bistatic sensing using a first device as a transmitter and a second device as a receiver; or (iii) multistatic sensing using multiple transmitters and / or multiple receivers. To facilitate sensing (e.g., in a sensing session between one or more sensing nodes), a sensing server may provide data (e.g., “auxiliary data”) to the sensing nodes to facilitate RS transmission and / or measurement, object / target detection, or any combination thereof. Such data may include RS configuration indicating which resources (e.g., time and / or frequency resources) are available (e.g., in a sensing session) for transmitting RS for RF sensing. According to some embodiments, the sensing server may include sensing management functions (SMF or SnMF).

[0042] While ground components (such as AP 130 and base station 120) may be fixed, the implementation is not limited to this. Mobile components may be used. For example, in some implementations, the location of mobile device 105 may be estimated at least in part based on measurements of RF signals 140 transmitted between mobile device 105 and one or more other mobile devices 145 (which may be mobile or fixed). As illustrated, other mobile devices may include, for example, mobile phone 145-1, vehicle 145-2, static communication / positioning device 145-3, or other static and / or mobile devices capable of providing wireless signals for locating mobile device 105, or combinations thereof. The wireless signals from mobile device 145 for locating mobile device 105 may include, for example, Bluetooth. ® (Including Bluetooth Low Energy (BLE)), IEEE 802.11x (e.g., Wi-Fi) ®RF signals such as ultra-wideband (UWB), IEEE 802.15x, or combinations thereof. Mobile device 145 may additionally or alternatively use non-RF wireless signals for positioning of mobile device 105, such as infrared signals or other optical technologies.

[0043] Mobile device 145 may include other UEs communicatively coupled to a cellular network or other mobile network (e.g., network 170). When one or more other mobile devices 145 (including UEs) are used in determining the location of a particular mobile device 105, the mobile device 105 whose location is to be determined may be referred to as the "target UE," and each of the other mobile devices 145 used may be referred to as the "anchor UE." For the location determination of the target UE, the respective location of the one or more anchor UEs may be known and / or determined jointly with the target UE. Direct communication between one or more other mobile devices 145 and mobile device 105 may include sidelinks and / or similar device-to-device (D2D) communication technologies. Sidelinks, as defined by 3GPP, are forms of D2D communication based on cellular LTE and NR standards.

[0044] According to some implementation schemes, when mobile device 105 is included and / or incorporated into a vehicle, one form of D2D communication used by mobile device 105 may include vehicle-to-everything (V2X) communication. V2X is a communication standard for vehicles to exchange information about the traffic environment with relevant entities. V2X may include vehicle-to-vehicle (V2V) communication between vehicles with V2X capability, vehicle-to-infrastructure (V2I) communication between vehicles and infrastructure-based devices (often referred to as roadside units (RSUs)), and vehicle-to-person (V2P) communication between vehicles and nearby people (pedestrians, cyclists, and other road users). Furthermore, V2X can use any of a variety of wireless RF communication technologies. For example, cellular V2X (CV2X) is a form of V2X that uses cellular-based communication, such as LTE (4G), NR (5G), and / or other cellular technologies, in the direct communication mode defined by 3GPP. Figure 1The mobile device 105 illustrated herein may correspond to a component or device on a vehicle, RSU, or other V2X entity used to communicate V2X messages. In embodiments in which V2X is used, static communication / location device 145-3 (which may correspond to an RSU) and / or vehicle 145-2 can therefore communicate with mobile device 105 and can be used to determine the location of mobile device 105 using techniques similar to those used by base station 120 and / or AP 130 (e.g., using polygonal measurement and / or multipoint positioning). It may also be noted that, according to some embodiments, mobile device 145 (which may include V2X devices), base station 120 and / or AP 130 may be used together (e.g., in a WWAN positioning solution) to determine the location of mobile device 105.

[0045] The estimated location of mobile device 105 can be used in various applications, such as to assist the user of mobile device 105 in direction finding or navigation, or to assist (e.g., associated with external client 180) another user in locating mobile device 105. "Location" is also referred to herein as "location estimation," "estimated location," "position," "azimuth," "azimuth estimation," "azimuth fixed," "estimated azimuth," "location fixed," or "fixed." The process of determining location may be referred to as "location determination," "location determination," etc. The location of mobile device 105 may include the absolute location of mobile device 105 (e.g., latitude and longitude and possible altitude) or the relative location of mobile device 105 (e.g., expressed as a distance north or south, east or west, and possibly above or below from another known fixed location (including, for example, the location of base station 120 or AP 130) or another location (such as the location of mobile device 105 at a known previous time, or the location of mobile device 145 (e.g., another UE) at a known previous time)). Location can be specified as a geodetic location including coordinates, which can be absolute (e.g., latitude, longitude, and optional altitude), relative (e.g., relative to a known absolute location), or local (e.g., X, Y, and optional Z coordinates according to a coordinate system defined relative to a local area (such as a factory, warehouse, university campus, shopping mall, stadium, or conference center). Location may alternatively be a municipal location and may then include one or more of the following: street address (e.g., including the name or label of country, state, county, city, road, and / or street, and / or road or street number) and / or labels or names of places, buildings, parts of buildings, floors of buildings, and / or rooms within buildings. Location may also include indications of uncertainty or error, such as the level of error expected for the location and the possible vertical distance, or an indication of the area or volume (e.g., a circle or ellipse) within which the mobile device 105 is expected to be located at a certain confidence level (e.g., 95% confidence).

[0046] External client 180 may be a web server or remote application that has some association with mobile device 105 (e.g., accessible by the user of mobile device 105), or it may be a server, application, or computer system that provides location services to one or more other users, including obtaining and providing the location of mobile device 105 (e.g., to enable services such as finding friends or relatives or locating children or pets). Additionally or alternatively, external client 180 may obtain the location of mobile device 105 and provide it to emergency service providers, government agencies, etc.

[0047] As previously noted, the example positioning / sensing system 100 can be implemented using wireless communication networks, such as LTE-based or 5G NR-based networks or future 6G networks. Figure 2 A diagram of a 5G NR positioning / sensing system 200 is shown, illustrating an implementation of a positioning / sensing system (e.g., positioning / sensing system 100) in 5G NR. The 5G NR positioning / sensing system 200 can be configured to achieve wireless communication and determine UE 205 (which may correspond to...) using an access node. Figure 1 The access nodes may include NR NodeBs (gNBs) 210-1 and 210-2 (collectively referred to herein as gNB 210), ng-eNB 214, and / or WLAN 216, which may use RF signaling to communicate, implement one or more positioning methods, and / or perform RF sensing. gNB 210 and / or ng-eNB 214 may be compatible with mobile devices 105. Figure 1 Corresponding to base station 120, and WLAN 216 can be connected to... Figure 1 One or more access points 130 correspond to this. Optionally, the 5G NR positioning / sensing system 200 may be additionally configured to determine the location of the UE 205 using an LMF 220 (which may correspond to a location / sensing server 160) to implement one or more positioning methods. The SnMF 221 may coordinate RF sensing performed by the 5G NR positioning / sensing system 200. Here, the 5G NR positioning / sensing system 200 includes the UE 205 and components of a 5G NR network, including a next-generation (NG) radio access network (RAN) (NG-RAN) 235 and a 5G core network (5G CN) 240. The 5G network may also be referred to as an NR network; the NG-RAN 235 may be referred to as a 5G RAN or NR RAN; and the 5G CN 240 may be referred to as an NG core network. Additional components of the 5G NR positioning / sensing system 200 are described below. The 5G NR positioning / sensing system 200 may include additional or optional components.

[0048] The 5G NR positioning / sensing system 200 can further utilize information from satellite 110. As previously indicated, satellite 110 may include GNSS satellites from GNSS systems such as Global Positioning / Sensing System (GPS) or similar systems (e.g., GLONASS, Galileo, BeiDou, Indian Regional Navigation Satellite System (IRNSS)). Alternatively or additionally, satellite 110 may include NTN satellites. NTN satellites may be in Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Geostationary Earth Orbit (GEO), or some other type of orbit. NTN satellites may be communicatively coupled to LMF 220 and operatively used as TRP (or TP) in NG-RAN 235. Therefore, satellite 110 may communicate with one or more gNBs 210 via one or more NTN gateways 150. According to some embodiments, NTN gateway 150 may operate as a DU of gNB 210, in which case communication between NTN gateway 150 and CU of gNB 210 may occur via F interface 218 between DU and CU.

[0049] It should be pointed out that, Figure 2 This is only a generalized illustration of the various components, any or all of which may be appropriately utilized, and each component may be repeated or omitted as needed. Specifically, although only one UE 205 is illustrated, it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the 5G NR positioning / sensing system 200. Similarly, the 5G NR positioning / sensing system 200 may include more (or fewer) numbers of satellites 110, gNB 210, ng-eNB 214, wireless local area network (WLAN) 216, access and mobility management functions (AMF) 215, external clients 230, and / or other components. The illustrated connections connecting the various components in the 5G NR positioning / sensing system 200 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, the components may be rearranged, combined, separated, replaced, and / or omitted according to desired functionality.

[0050] UE 205 may include and / or be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location Enabled (SUPL) terminal (SET), or some other name. Furthermore, UE 205 may correspond to a cellular phone, smartphone, laptop, tablet, personal data assistant (PDA), navigation device, Internet of Things (IoT) device, or some other portable or mobile device. Typically, although not required, UE 205 may support one or more Radio Access Technologies (RATs) such as GSM, CDMA, W-CDMA, LTE, High Rate Packet Data (HRPD), IEEE 802.11 Wi-Fi. ® Bluetooth, WiMAX global microwave access interoperability ™ Wireless communication such as 5G NR (e.g., using NG-RAN 235 and 5GCN 240). UE 205 can also support wireless communication using WLAN 216, which is similar to one or more RATs, and as previously mentioned for... Figure 1 (As indicated) can connect to other networks, such as the Internet. Using one or more of these RATs allows UE 205 (e.g., via...) Figure 2 The 5G CN 240 (not shown) may communicate with external client 230 via Gateway Mobile Location Center (GMLC) 225 and / or allow external client 230 (e.g., via GMLC 225) to receive location information about UE 205. When implemented in or communicatively coupled to a 5G NR network, Figure 2 The external client 230 can correspond to Figure 1 External client 180.

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

[0052] Figure 2 The base station shown in NG-RAN 235 can correspond to Figure 1 The base station 120 in the NG-RAN 235 may include gNB 210. Pairs of gNB 210 in the NG-RAN 235 may be connected to each other (e.g., as shown in the image). Figure 2 The connection may be direct or indirect via another gNB 210. The communication interface between the base stations (gNB 210 and / or ng-eNB 214) may be referred to as the Xn interface 237. Access to the 5G network is provided to the UE 205 via wireless communication between the UE 205 and one or more gNBs 210. This wireless communication may use 5G NR to provide wireless communication access to the 5G CN 240 on behalf of the UE 205. The radio interface between the base station (gNB 210 and / or ng-eNB 214) and the UE 205 may be referred to as the Uu interface 239. 5G NR radio access may also be referred to as NR radio access or 5G radio access. Figure 2In this context, it is assumed that the serving gNB of UE 205 is gNB 210-1, but other gNBs (e.g., gNB 210-2) may act as serving gNBs or as secondary gNBs to provide additional throughput and bandwidth to UE 205 if UE 205 moves to another location.

[0053] Figure 2 The base stations in the NG-RAN 235 shown may additionally or alternatively include a next-generation evolved Node B (also referred to as an ng-eNB) 214. The ng-eNB 214 may be connected (e.g., directly or indirectly via other gNBs 210 and / or other ng-eNBs) to one or more gNBs 210 in the NG-RAN 235. The ng-eNB 214 may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UE 205. Figure 2 Some gNBs 210 (e.g., gNB 210-2) and / or ng-eNBs 214 can be configured to act as location-only beacons. These location-only beacons can transmit signals (e.g., a location reference signal (PRS)) and / or broadcast auxiliary data to assist the positioning of UE 205, but may not receive signals from UE 205 or other UEs. Some gNBs 210 (e.g., gNB 210-2 and / or another gNB not shown) and / or ng-eNBs 214 can be configured to act as detection-only nodes. These detection-only nodes can scan for signals containing, for example, PRS data, auxiliary data, or other location data. Such detection-only nodes may not transmit signals or data to the UE, but may transmit signals or data (involving, for example, PRS, auxiliary data, or other location data) to other network entities (e.g., one or more components of the 5G CN 240, external client 230, or controller), which may receive and store the data or use the data to locate at least UE 205. It should be noted that, although Figure 2 Only one ng-eNB 214 is shown, but some implementations may include multiple ng-eNB 214s. Base stations (e.g., gNB 210 and / or ng-eNB 214) may communicate directly with each other via the Xn communication interface. Additionally or alternatively, base stations may communicate directly or indirectly with other components of the 5G NR positioning / sensing system 200, such as LMF 220 and AMF 215.

[0054] The 5G NR positioning / sensing system 200 may also include one or more WLANs 216, which can connect to the non-3GPP interoperability function (N3IWF) 250 in the 5G CN 240 (e.g., in the case of untrusted WLAN 216). For example, WLAN 216 may support IEEE 802.11 Wi-Fi access for UE 205 and may include one or more Wi-Fi APs (e.g., Figure 1 (AP 130). Here, N3IWF 250 can connect to other components in 5G CN 240, such as AMF 215. In some implementations, WLAN 216 may support another RAT, such as Bluetooth. N3IWF 250 may provide support for secure access of UE 205 to other components in 5G CN 240 and / or may support interoperability between one or more protocols used by WLAN 216 and UE 205 and one or more protocols used by other components of 5G CN 240 such as AMF 215. For example, N3IWF 250 may support IPSec tunnel establishment with UE 205, termination of IKEv2 / IPSec protocol with UE 205, termination of N2 and N3 interfaces to 5G CN 240 for control plane and user plane respectively, and relay of uplink (UL) and downlink (DL) control plane non-access stratum (NAS) signaling across N1 interface between UE 205 and AMF 215. In some other implementations, WLAN 216 can be directly connected to components in 5G CN 240 (e.g., such as...). Figure 2 The dashed line in the diagram shows AMF 215) and it does not go through N3IWF250. For example, a direct connection between WLAN 216 and 5GCN 240 can occur if WLAN 216 is a trusted WLAN to 5GCN 240, and a Trusted WLAN Interoperability (TWIF) function that can be an internal component of WLAN 216 can be used. Figure 2 (Not shown in the image) to achieve this. It should be noted that, although Figure 2 Only one WLAN 216 is shown, but some implementations may include multiple WLAN 216s.

[0055] The access node may include any of a variety of network entities that enable communication between UE 205 and AMF 215. As noted, this may include gNB 210, ng-eNB 214, WLAN 216 and / or other types of cellular base stations, and may also include NTN satellite 110. However, the access node providing the functionality described herein may additionally or alternatively include entities that enable communication with Figure 2An entity that communicates with any of the various RATs not illustrated herein (which may include non-cellular technologies). Therefore, as used in the embodiments described below, the term "access node" may include, but is not limited to, gNB 210, ng-eNB 214, WLAN 216, or NTN satellite 110.

[0056] In some implementations, access nodes such as gNB 210, ng-eNB 214, WLAN 216, or NTN satellite 110, or combinations thereof (alone or in combination with other components of the 5G NR positioning / sensing system 200), can be configured to, in response to a request for location information received from LMF 220, obtain location measurements of uplink (UL) signals received from UE 205 and / or obtain DL location measurements obtained by UE 205 for downlink (DL) signals received by UE 205 from one or more access nodes. As noted, although Figure 2 The description depicts access nodes (gNB 210, ng-eNB 214, WLAN 216, and NTN satellite 110) configured to communicate according to 5G NR, LTE, and Wi-Fi communication protocols, respectively. However, access nodes configured to communicate according to other communication protocols can be used, such as, for example, a Node B using the Wideband Code Division Multiple Access (WCDMA) protocol for Universal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (UTRAN), an eNB using the LTE protocol for Evolved UTRAN (E-UTRAN), or a Bluetooth Node using the Bluetooth protocol for WLAN. ® Beacon. For example, in a 4G evolved packet system (EPS) providing LTE radio access to UE 205, the RAN may include an E-UTRAN, which may include base stations containing eNBs supporting LTE radio access. The core network for the EPS may include an evolved packet core (EPC). The EPS may then include an E-UTRAN plus an EPC, where... Figure 2 In this context, E-UTRAN corresponds to NG-RAN 235 and EPC corresponds to 5GCN 240. The methods and techniques described herein for obtaining the municipal location of UE 205 are applicable to other networks of this type.

[0057] gNB 210 and ng-eNB 214 can communicate with AMF 215, which in turn communicates with LMF 220 for positioning functionality. AMF 215 can support the mobility of UE 205, including cell changes and handovers from the access node of a first RAT (e.g., gNB 210, ng-eNB 214, WLAN 216, or NTN satellite 110) to the access node of a second RAT. AMF 215 can also participate in supporting signaling connections to UE 205 and, where possible, data and voice bearers for UE 205. The LMF 220 supports the use of the CP positioning solution to locate UE 205 when UE 205 accesses NG-RAN 235 or WLAN 216, and supports positioning procedures and methods, including UE-assisted / UE-based and / or network-based procedures / methods, such as assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA) (which may be referred to as Time Difference of Arrival (TDOA) in NR), Frequency Difference of Arrival (FDOA), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), Angle of Arrival (AoA), Angle of Departure (AoD), WLAN positioning, Round-Trip Propagation Delay (RTT), Multi-Cell RTT, and / or other positioning procedures and methods. The LMF 220 can also handle location service requests for UE 205 received, for example, from AMF 215 or GMLC 225. The LMF 220 can connect to AMF 215 and / or GMLC 225. In some implementations, networks such as 5GCN 240 may additionally or alternatively implement other types of location support modules, such as an evolved Serving Mobility Location Center (E-SMLC) or a SUPL Location Platform (SLP). It should be noted that in some implementations, at least a portion of the location functionality (including determining the location of UE 205) may be performed at UE 205 (e.g., by measuring downlink PRS (DL-PRS) signals transmitted by radio nodes such as gNB 210, ng-eNB 214, WLAN 216, or NTN satellite 110 and / or using auxiliary data, for example, provided to UE 205 by LMF 220).

[0058] Gateway Mobile Location Center (GMLC) 225 can support location requests for UE 205 received from external client 230 and can forward such location requests to AMF 215 for forwarding to LMF 220. Location responses from LMF 220 (e.g., containing location estimates for UE 205) can similarly be returned to GMLC 225 directly or via AMF 215, and GMLC 225 can then return the location response (e.g., containing location estimates) to external client 230.

[0059] Network Open Function (NEF) 245 may be included in 5GCN 240. NEF 245 can support the secure opening of capabilities and events concerning 5GCN 240 and UE 205 to external client 230. These capabilities and events may then be referred to as Access Functions (AF) and enable the secure provisioning of information from external client 230 to 5GCN 240. NEF 245 may connect to AMF 215 and / or GMLC 225 for the purpose of obtaining the location of UE 205 (e.g., municipal location) and providing that location to external client 230.

[0060] like Figure 2 As further illustrated, the LMF 220 can communicate with the gNB 210 and / or the ng-eNB 214 using NR Location Protocol Annex (NRPPa) as defined in 3GPP Technical Specification (TS) 38.455. NRPPa messages can be transmitted between the gNB 210 and the LMF 220 and / or between the ng-eNB 214 and the LMF 220 via the AMF 215. Figure 2As further illustrated, LMF 220 and UE 205 can communicate using the LTE Positioning Protocol (LPP) as defined in 3GPP TS 37.355. Here, LPP messages can be transmitted between UE 205 and LMF 220 via AMF 215 and the serving gNB 210-1 or serving ng-eNB 214 for UE 205. For example, LPP messages can be transmitted between LMF 220 and AMF 215 using service-based operation messages (e.g., based on Hypertext Transfer Protocol (HTTP)), and the 5G NAS protocol can be used to transmit LPP messages between AMF 215 and UE 205. The LPP protocol can be used to support the positioning of UE 205 using UE-assisted and / or UE-based positioning methods such as A-GNSS, RTK, TDOA, multi-cell RTT, AoD, and / or ECID. The NRPPa protocol can be used to support the location of UE 205 using network-based location methods such as ECID, AoA, and uplink TDOA (UL-TDOA) and / or can be used by LMF220 to obtain location-related information from gNB 210 and / or ng-eNB 214, such as defining parameters sent by DL-PRS from gNB 210 and / or ng-eNB 214.

[0061] When UE 205 accesses WLAN 216, LMF 220 can use NRPPa and / or LPP to obtain the location of UE 205 in a manner similar to that described just for UE 205 accessing gNB 210 or ng-eNB 214. Therefore, NRPPa messages can be transmitted between WLAN 216 and LMF 220 via AMF 215 and N3IWF 250 to support network-based location and / or other location information transmission of UE 205 from WLAN 216 to LMF 220. Alternatively, NRPPa messages can be transmitted between N3IWF 250 and LMF 220 via AMF 215 to support network-based location of UE 205 based on location-related information and / or location measurements transmitted from N3IWF 250 to LMF 220 using NRPPa, which is known or accessible to N3IWF 250. Similarly, LPP and / or LPP messages can be transmitted between UE 205 and LMF 220 via AMF 215, N3IWF 250 and UE 205’s serving WLAN 216 to support UE-assisted or UE-based positioning of UE 205 by LMF 220.

[0062] Using a UE-based positioning method, UE 205 can obtain a location measurement (e.g., which may be the same as or similar to the location measurement of a UE-assisted positioning method), and can further calculate the location of UE 205 (e.g., with the aid of auxiliary data received from a location server such as LMF 220, SLP or broadcast by gNB 210, ng-eNB 214 or WLAN 216).

[0063] Using a network-based positioning method, one or more base stations (e.g., gNB 210 and / or ng-eNB 214), one or more APs (e.g., in WLAN 216), or N3IWF 250 can obtain location measurements (e.g., RSSI, RTT, RSRP, RSRQ, AoA, or TOA) of signals transmitted by UE 205, and / or can receive measurements obtained by UE 205 or by APs in WLAN 216 in the case of N3IWF 250, and can transmit these measurements to a location server (e.g., LMF 220) for calculating a location estimate for UE 205.

[0064] The positioning of UE 205 can also be classified as UL-based, DL-based, or DL-UL-based based on the type of signal used for positioning. For example, if positioning is based solely on signals received at UE 205 (e.g., from a base station or other UE), the positioning can be classified as DL-based. On the other hand, if positioning is based solely on signals transmitted by UE 205 (which may be received by, for example, a base station or other UE), the positioning can be classified as UL-based. DL-UL-based positioning includes positioning based on signals transmitted and received by UE 205, such as RTT-based positioning. Side-link (SL)-assisted positioning includes signals transmitted between UE 205 and one or more other UEs. According to some embodiments, UL, DL, or DL-UL positioning as described herein may enable SL signaling to be used as a supplement to or replacement of SL, DL, or DL-UL signaling.

[0065] Depending on the positioning type (e.g., UL-based, DL-based, or DL-UL-based), the types of reference signals used may differ. For example, for DL-based positioning, these signals may include PRS (e.g., DL-PRS transmitted by the base station or SL-PRS transmitted by other UEs), which can be used for TDOA measurement, AoD measurement, and RTT measurement. Other reference signals that can be used for positioning (UL, DL, or DL-UL) may include probe reference signals (SRS), channel state information reference signals (CSI-RS), synchronization signals (e.g., synchronization signal block (SSB) synchronization signal (SS)), physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), physical sidelink shared channel (PSSCH), demodulation reference signals (DMRS), etc. Furthermore, reference signals may be transmitted in Tx beams and / or received in Rx beams (e.g., using beamforming techniques), which can affect angle measurements such as AoD and / or AoA.

[0066] The principles described above regarding positioning can be broadly extended to RF sensing. That is, RF sensing can be UE-based (e.g., originating from the UE) and / or UE-assisted (e.g., originating from a non-UE entity), and can involve UL signals, DL signals, or both. However, RF sensing can differ from positioning in various ways. For example, as previously noted and described in more detail below, RF sensing can involve the use of specific RF sensing signals and / or ISAC signals. Furthermore, as described above, RF sensing can be performed in a monostatic, bistatic, or multistatic manner, where the RF sensing nodes include a UE (e.g., UE 205) and / or one or more access nodes (e.g., gNB 210, ng-eNB 214, WLAN 216, NTN satellite 110, or any combination thereof). The following section discusses… Figure 3 It describes various aspects of RF sensing in more detail.

[0067] Figure 3 This is a diagram illustrating an RF sensing system 305 and examples of associated terminology. As used herein, the terms “waveform” and “sequence” and their derivatives are used interchangeably to refer to an RF signal generated by the transmitter of the RF sensing system and received by the receiver of the RF sensing system for object detection. “Pulse” and its derivatives are generally referred to herein as a waveform comprising a sequence or complementary sequence pair transmitted and received to generate a channel impulse response (CIR). The RF sensing system 305 may include a standalone device or may be integrated into a larger electronic device (e.g., the UE disclosed herein) (such as a mobile phone, base station / access node, satellite, or another type of sensing node as described herein). (Example components of such electronic devices are shown in...) Figures 10 to 12 (As illustrated below, and discussed in detail.) It can be pointed out that, although Figure 3 The example RF sensing system 305 is illustrated as a monobase configuration, but the implementation is not limited to this. As noted elsewhere herein, an RF sensing node may be configured to perform RF sensing in a monobase, bibase, or multibase configuration, or any combination thereof (e.g., depending on the specific instance). Therefore, the components of the RF sensing system 305 within the RF sensing node can vary. For example, an RF sensing node that performs only transmission or only reception during RF sensing may include only the corresponding components associated with transmission or reception. Similarly, the implementation may vary depending on the desired functionality.

[0068] about Figure 3 The RF sensing system 305 in the diagram is functional in that it can detect the distance, orientation, and / or velocity of an object 310 by generating a series of transmitted RF signals 312 (including one or more pulses). Some of these transmitted RF signals 312 are reflected from the object 310, and these reflected RF signals 314 (or “echoes”) are then processed by the RF sensing system 305 using beamforming (BF) and digital signal processing (DSP) techniques to determine the position (azimuth, elevation, velocity (e.g., from Doppler measurements)) and range of the object relative to the RF sensing system 305. CFAR may be part of this processing but may not necessarily be used in every instance or “moment” of performing RF sensing.

[0069] To achieve RF sensing, the RF sensing system 305 may include a processing unit 315, a memory 317, a multiplexer (mux) 320, a Tx processing circuit 325, and an Rx processing circuit 330. (The RF sensing system 305 may include additional components not illustrated, such as a power supply, user interface, or electronic interface). However, it will be noted that these components of the RF sensing system 305 may be rearranged or otherwise changed in alternative embodiments, depending on the desired functionality. Furthermore, as used herein, the term "transmitting circuit" or "Tx circuit" refers to any circuitry used to create and / or transmit the transmitted RF signal 312. Similarly, the term "receiving circuit" or "Rx circuit" refers to any circuitry used to detect and / or process the reflected RF signal 314. Therefore, "transmitting circuit" and "receiving circuit" may include not only the Tx processing circuit 325 and the Rx processing circuit 330, respectively, but may also include the mux 320 and the processing unit 315. In some embodiments, the processing unit may constitute at least a part of a modem and / or wireless communication interface. In some implementations, more than one processing unit may be used to perform the functions of the processing unit 315 described herein.

[0070] The Tx processing circuit 325 and Rx circuit 330 may include sub-components for generating and detecting RF signals, respectively. As those skilled in the art will appreciate, the Tx processing circuit 325 may therefore include a pulse generator, a digital-to-analog converter (DAC), a mixer (for up-mixing the signal to the transmission frequency), one or more amplifiers (for powering the transmission via the Tx antenna array 335), etc. The Rx processing circuit 330 may have similar hardware for processing the detected RF signal. Specifically, the Rx processing circuit 330 may include an amplifier (for amplifying the signal received via the Rx antenna 340), a mixer for down-converting the received signal from the transmission frequency, an analog-to-digital converter (ADC) for digitizing the received signal, and a pulse correlator for providing a matched filter for the pulse generated by the Tx processing circuit 325. Thus, the Rx processing circuit 330 may use the correlator output as a CIR, which may be processed by the processing unit 315 (or other circuitry). The processing of the CIR may include object detection, range, rate, or direction of arrival (DoA) estimation.

[0071] Beamforming is further achieved by Tx antenna array 335 and Rx antenna array 340. Each antenna array 335, 340 includes multiple antenna elements. It can be noted that, although... Figure 3 Antenna arrays 335 and 340 include two-dimensional arrays, but implementations are not limited thereto. The array may simply include multiple antenna elements along a single dimension that provides spatial cancellation between the Tx and Rx sides of the RF sensing system 305. As those skilled in the art will appreciate, in addition to various environmental factors, the relative positions of the Tx and Rx sides can also affect the manner in which spatial cancellation can be performed.

[0072] It should be noted that the nature of the transmitted RF signal 312 can vary depending on the technology used. The technology presented herein is generally applicable to “mmWave” technology, which typically operates in the 57 GHz–71 GHz range, but may include frequencies ranging from 30 GHz to 300 GHz. This includes frequencies used, for example, by the 802.11ad Wi-Fi standard (operating at 60 GHz). That is, some implementations may utilize RF signals at frequencies outside this range. For example, in some implementations, the 5 GHz band (e.g., 28 GHz) may be used.

[0073] Because RF sensing can be performed in the same frequency band as communication (e.g., cellular and / or WLAN communication), the hardware can be used for both communication and RF sensing, as previously noted. For example, Figure 3One or more components of the illustrated RF sensing system 305 may be included in a wireless modem (e.g., Wi-Fi, 5G, or other modems). Additionally, the technique is applicable to RF signals of any pulse type, including compressed pulses (e.g., including Chirp sequences, Golay sequences, Barker sequences, Ipatov sequences, or m-sequences). That is, the implementation is not limited to such frequencies and / or pulse types. Additionally, because the RF sensing system may be able to transmit RF signals for communication (e.g., using 802.11 communication technology), the implementation may utilize channel estimation used in communication to perform the RF sensing as provided herein. Therefore, the pulse may be the same as the pulse used for channel estimation in communication.

[0074] As noted, the RF sensing system 305 can be integrated into an electronic device (e.g., mobile device 105 and / or UE 205) into which RF sensing is desired. For example, the RF sensing system 305 capable of performing RF sensing can be part of the communication hardware in a modern mobile phone. Other devices may also utilize the techniques provided herein. These devices may include, for example, other mobile devices (e.g., tablets, portable media players, laptops, wearable devices, other electronic devices (e.g., security devices, in-vehicle systems, dedicated or specialized RF sensing devices)), wireless nodes of communication networks (e.g., access nodes, such as base stations and / or satellites), etc. That is, the electronic devices (e.g., RF sensing nodes) into which the RF sensing system 305 can be integrated are not limited to such devices.

[0075] In RF sensing, wireless signals can be transmitted from one or more transmitting points and received at one or more receiving points after being reflected by a target. RF sensing enables numerous candidate applications, including intruder detection, animal / pedestrian / UAV intrusion detection on highways and railways, rainfall monitoring, flood sensing, autonomous driving, Automated Guided Vehicle (AGV) detection / tracking / collision avoidance, smart parking and assistance, UAV trajectory and tracking, crowd management, sleep / health monitoring, gesture recognition, extended reality (XR) streaming, public safety, search and rescue, and more. Furthermore, RF sensing is expected to be incorporated into wireless standards such as 5G and therefore can be implemented in cellular networks in the future.

[0076] As previously noted, future generations of cellular networks (e.g., 5G Advanced, 6G, etc.) are planned to support ISAC to enable the UE to perform both RF sensing and communication. ISAC can be implemented in two ways, such as... Figure 4 exemplified.

[0077] Figure 4This is an illustration of different ways of implementing ISAC according to some implementation schemes. First illustration 400 shows a specific implementation of a co-located and cooperative radar and communication system. Here, Node 1 and Node 2 represent a specific implementation of ISAC for wireless nodes in a wireless network. In a cellular network (such as a 5G network), Node 1 and Node 2 may represent, for example, a UE, a base station, or other wireless device. As illustrated, the nodes may use RF sensing components (e.g., Figure 3 The RF sensing system 305 performs RF sensing and may further communicate using a communication component. As further illustrated, the RF sensing and communication components may be separate but can communicate with each other. Therefore, using separate components in this manner may require coordination between components, additional circuitry, etc.

[0078] Figure 410 illustrates a second embodiment of a co-design with communication and RF sensing systems. That is, in this embodiment, one or more transmitters, receivers, and / or a common set of transmitters can be used for both communication and RF sensing functionalities. This embodiment may require significant modifications to the transmission waveform generation or receiver processing of either or both of the RF sensing and / or communication circuitry. In other words, using this co-design embodiment offers the advantages described above, such as efficiency gains in hardware and spectrum reuse.

[0079] However, the use of conventional waveform CP-OFDM for communications may not be a suitable solution for specific ISAC implementations. When the delay spread exceeds the CP length or the velocity exceeds the subcarrier spacing (STS), CP-OFDM suffers from signal energy loss and inter-symbol interference (ISI) and inter-carrier interference (ICI) effects for sensing detection / estimation. For example, RF sensing requirements for automotive applications may require a sensing range of 300m, good velocity resolution, and a large maximum velocity detection. However, relatively short CP durations may not be suitable for these requirements. Furthermore, dedicated reference signals for RF sensing may incur significant overhead for velocity estimation due to the large time integration required to achieve high-speed resolution requirements. The integration of CP-OFDM data with such reference signals may further necessitate substantial hardware complexity and large memory due to this integration requirement.

[0080] For example, CP-OFDM for single-level sensing suffers from considerable overhead and latency issues that may be incompatible with the requirements of various applications, such as automotive applications. For instance, single-level symbol-based sensing can be performed within a 5ms duration (corresponding to 40 time slots under a 120kHz subcarrier spacing (SCS)) to provide continuous sensing with a wide bandwidth of 400MHz for each beam. At an update rate of 20 frames per second (fps), this consumes a significant amount of system resources, up to 5% per beam and user. When considering the desired field of view (FoV) that some applications (e.g., automotive) might require (e.g., across nine beams), up to 45% of system resources can be utilized within 45ms. This resource expenditure places a significant burden on communication capabilities, inducing high latency that affects the timely transmission of communication data and potentially disrupting communication auxiliary functionalities such as beam management and synchronization.

[0081] Figure 5 This is a diagram illustrating examples of resource usage for different beams. Here, different beams (darkened) are used for RF sensing at different times. The Coherent Processing Interval (CPI) 510 defines the time span within which RF signals are processed (e.g., for creating a single data frame). The configuration of CPI 510 (e.g., the number of symbols included, and / or duration) can affect the determination of the velocity and range resolution of the detected object. For example, a single CPI may consist of numerous slots / symbols under a specific subcarrier interval, which indicates the fineness with which RF sensing can distinguish between different objects in terms of distance and relative rate. As noted above, in the context of single-stage sensing, CPI 510 can involve continuous monitoring periods with wide bandwidth, thus consuming a significant portion of system resources for each beam, such as... Figure 5 As shown. This high consumption, especially when considering multiple beams over a short period, can lead to a significant system burden.

[0082] Additionally, CP is an extra overhead for RF sensing and communication and may have limited benefits. For example, CP may only achieve the benefits of circular convolution when the range spread is less than the delay, and CP can also introduce discontinuities. Furthermore, CP may not be "tuned" to the needs of a particular RF sensing application. For example, if the range spread is much smaller than CP, it may result in poor throughput. On the other hand, if the range spread is much larger than CP, it may result in signal energy loss and interference. Ultimately, using CP in RF sensing may limit speed estimation to relatively high signal-to-noise ratio (SNR) but with poor resolution.

[0083] Guard Interval (GI) offers significantly greater flexibility than CP. Because the length of the GI may not be fixed, it can adapt to different range extensions. Furthermore, it provides relatively low communication overhead. (The following section discusses...) Figure 6 An additional comparison between GI and CP is described. Considering these advantages, the implementation scheme presented herein incorporates GI-based ISAC waveforms to accommodate various sensing requirements, including some very stringent ones. More specifically, the implementation scheme described herein describes various aspects of GI-ISAC, including GI mode and GI-ISAC waveform configuration parameters, GI-ISAC call flow with Tx parameter configuration transmission and Rx processing auxiliary information, sensing speed and range information using GI-ISAC waveforms, and interference management and handling. These and other aspects are described in more detail below.

[0084] Figure 6 A comparison is provided between conventional CP-based symbols (e.g., CP-OFDM) and GI-based symbols (e.g., GI-ISAC) according to examples. First Figure 600 illustrates a conventional CP-based time slot having CP-based symbols including CP 605 and data 610. In conventional CP-OFDM, data 610 may include OFDM symbols. Furthermore, a time slot may include 14 OFDM symbols, each OFDM symbol having a corresponding CP. As noted herein, the CP used for a symbol (e.g., including CP 605) may have a fixed or static length.

[0085] Figure 650 illustrates an example GI-based time slot according to an implementation scheme. Similar to CP-based symbols, GI-based symbols consist of GI 655 (instead of CP) and data 660. In this example, GI 655 follows data 660, although this may not always be the case, as described in further detail below. Furthermore, the duration of GI 655 is variable. According to some implementations, it may be desirable to maintain a static total GI-based symbol length, thus extending GI 655 may shorten data 660, and vice versa. Additional details regarding GI-based symbols and specific GI-ISACs are provided below.

[0086] In practice, wireless devices such as UEs, base stations, or other sensing nodes capable of communication can transmit a set of symbols including both CP-OFDM communication data symbols and GI-ISAC symbols. The parameters defining GI-ISAC (e.g., parameters of the GI-ISAC waveform codebook, which may be provided by the configuration device in the GI-ISAC configuration, as described in more detail below) may depend on the parameters of the OFDM communication used for CP-OFDM communication. This helps to minimize any impact on CP-OFDM communication when using GI-ISAC for RF sensing.

[0087] In one example, the GI-ISAC configuration may define the GI pattern for the Coherent Processing Interval (CPI). This may include, for example, a CPI comprising one or more consecutive time slots or micro-time slots, a CPI dependent on the carrier frequency, a CPI dependent on sensing quality of service (QOS) requirements (e.g., velocity estimation accuracy, range, etc.), or a combination thereof. Additionally or alternatively, the GI-ISAC configuration may define the GI content within the CPI, such as zeros, CPs, or at least a portion of the sensing reference sequence. According to some embodiments, the GI-ISAC configuration may additionally or alternatively indicate the location of the GI (within the CPI), such as which symbol(s) and / or whether the GI is located at the head (start) or tail (and) of the CPI. Additionally or alternatively, the GI-ISAC configuration may indicate the GI duration. According to some embodiments, this duration may apply to all locations within the CPI where the GI exists. In some embodiments, different durations may be applied to different GIs.

[0088] Using GI-ISAC in this manner enables RF sensing and compatibility with CP-OFDM communication. For example, an ISAC symbol may include an OFDM data sequence or a sensing symbol. In the case of a sensing symbol, the sensing symbol may be a linearly modulated (LFM) or nonlinearly modulated (NLFM) waveform, the parameters of which depend on the CP-OFDM configuration, such as bandwidth (e.g., LFM and / or NLFM bandwidth) and symbol duration (e.g., the LFM / NLFM chirp duration may be equal to or vary with the symbol duration). Additionally or alternatively, an ISAC symbol may include communication data centered on RF sensing, such as phase-decoded LFM.

[0089] The configuration of GI-ISAC can be determined and / or provided to one or more sensing nodes by a configuration node, which can operate as a centralized controller to coordinate the use of GI-ISAC by one or more sensing nodes. This is described below. Figure 7 The document provides an example of how this can be done.

[0090] Figure 7This is a call flowchart 700 illustrating an example process according to some implementations, through which a client node 705 can request and receive GI-ISAC measurement information obtained during RF sensing using GI-ISAC. Here, the process using GI-ISAC is coordinated by a configuration node 710 and performed by "helper" nodes 715 and 720. The client node 705 may include any device, such as a UE, communicatively coupled to the configuration node 710. As noted above, the configuration node 710 may include a centralized controller, such as a server (e.g., SnMF) or a base station (e.g., a main anchor gNB). The configuration node 710 may coordinate the GI-ISAC operation of one or more helper Tx nodes 715 and / or one or more helper Rx nodes 720. Helper nodes 715 and 720 may include adjacent sensing nodes (e.g., UEs and / or base stations that are close enough to transmit / receive RF signals between each other) that can be used for GI-ISAC communication and / or RF sensing. It should be noted that although the helper Tx node 715 and the helper Rx node 720 are illustrated as separate nodes, the implementation is not limited thereto. According to some implementations, one or more helper nodes may be used that perform the roles of both Tx node and Rx node (e.g., operating in a single-base configuration or a dual-base configuration in which nodes both transmit and receive). It should also be noted that, according to some implementations, the process of Figure 700 may be incorporated into another configuration process, such as a process for RF sensing. In such implementations, capabilities, configuration, and / or other such information may be communicated along with other information used to perform the RF sensing process.

[0091] As illustrated by arrows 725 and 730, the process may begin with configuration node 710 receiving a capability report from adjacent helper nodes 715 and 720, showing supported GIA Tx and Rx configuration modes. More specifically, helper Tx node 715 may indicate its capabilities regarding the transmission of GI-ISAC waveforms (e.g., support for GI-ISAC, constraints regarding supported GI lengths, and / or other parameters, etc.). According to some embodiments, the capability report provided at arrows 725 and 730 may be in response to a request from configuration node 710 to helper nodes 715 and 720 (…). Figure 7(Not shown in the diagram). According to some implementations, such requests and / or capability reports provided at arrows 725 and 730 may be in response to one or more triggers. One example trigger may include a helper node (e.g., helper node 715 or 720) transmitting a capability report when it enters the coverage area of ​​a centralized controller (e.g., configuration node 710) and establishes a link with the centralized controller, thereby notifying the centralized controller that the helper node is available to assist sensing functionality. In another example, the centralized controller (e.g., configuration node 710) may transmit a "help" request (e.g., as needed or periodically) to a potential helper node (e.g., a nearby UE), thereby requesting a capability report and possible sensing assistance.

[0092] According to some implementations, adjacent helper nodes 715 and 720 may provide additional information to configuration node 710. This may include, for example, location information of helper nodes 715 and 720. Location information may, for example, allow configuration node 710 to know which nodes are near client node 705 for purposes of GI-ISAC operation (e.g., using GI-ISAC for sensing and / or communication). Additionally or alternatively, configuration node 710 may use other means to obtain location information of one or more of helper nodes 715 and 720.

[0093] As illustrated by arrow 735, client node 705 may provide a request for GI-ISAC operation to configuration node 710. This request may be triggered, for example, by an application or function performed by client node 705 requesting RF sensing. Additionally or alternatively, the request at arrow 735 may be triggered by a request from another device (including a network node) for client node 705 to perform RF sensing. The request at arrow 735 may include application-dependent information, such as requested or required QoS metrics. For example, in an implementation where client node 705 may include or be incorporated into a vehicle, the requested or required speed resolution and / or maximum (and / or minimum) range may be indicated to accommodate automotive applications (e.g., autonomous driving, driver assistance, etc.) performed at client node 705.

[0094] As shown in box 740, configuration node 710 can then determine the GI-ISAC configuration, which can be based at least in part on the information received in the GI-ISAC request at arrow 735. For example, as noted above, the GI-ISAC request may include a request for or a desired QoS metric. Configuration node 710 can then determine the appropriate GI-ISAC to accommodate that metric. As previously noted, the GI-ISAC configuration can also be determined based on OFDM (e.g., CP-OFDM) information used by helper nodes 715 and 720. For example, in some instances, the GI-ISAC frame length (including GI and ISAC data) may conform to the CP-OFDM frame length (including CP and OFDM data), thereby enabling CP-OFDM transmission within the GI-ISAC waveform.

[0095] As indicated by arrow 745, configuration node 710 can then provide GI Tx configuration to helper Tx node 715, which reflects the GI-ISAC determined at block 740. More specifically, the GI Tx configuration enables Tx node 715 to transmit signals according to the GI-ISAC waveform determined by configuration node 710 at block 740, thereby enabling ISAC RF sensing and / or communication. Similarly, configuration node 710 can transmit GI Rx processing assistance information to helper Rx node 720, as indicated by arrow 750. This information enables helper Rx node 720 to process RF sensing and / or communication signals received using the GI-ISAC waveform. The GI-ISAC configuration information provided to helper nodes 715 and 720 at arrows 745 and 750 may include the GI mode (for CPI) and / or GI-ISAC waveform configuration parameters described above.

[0096] As previously noted, it is possible that only a portion of the assisting Tx node 715 and / or assisting Rx node 720 providing capability reports at arrows 725 and 730 may include neighboring nodes capable of obtaining RF sensing information in response to the GI-ISAC request at arrow 735. Therefore, the configuration information provided by configuration node 710 at arrows 745 and 750 may be provided to a subset of the assisting Tx node 715 and assisting Rx node 720. (If this is the case, only the subset will be executed.) Figure 7 Operations 755 and 760 are shown.

[0097] At box 755, helper Tx node 715 and helper Rx node 720 perform GI-ISAC RF measurements based on the configuration information received at arrows 745 and 750. That is, helper nodes 715 and 720 can perform the RF sensing process using the GI-ISAC waveform indicated in the configuration information received at arrows 745 and 750. In some aspects, helper nodes 715 and 720 can be considered to operate in GI-ISAC mode, during which the RF sensing operation at box 755 is performed. Due to the ISAC functionality of the GI-ISAC waveform, helper nodes 715 and 720 can also communicate (e.g., with each other) while in GI-ISAC mode.

[0098] As indicated by arrow 760, the helper Rx node 720 can then provide a GI-ISAC measurement report to the configuration node 710, which indicates the GI-ISAC measurement performed at box 755. More specifically, these measurement reports from each of the helper Rx nodes in the helper Rx nodes 720 can indicate RF sensing measurements performed by each of the helper Rx nodes in the helper Rx nodes 720, which can indicate the presence of one or more detected objects using RF sensing, and may also include information about one or more objects (e.g., location, velocity, size, etc.). These measurement reports can be compiled and / or summarized by the configuration node 710, which can then provide a corresponding compiled / summarized GI-ISAC measurement report to the client node 705, as indicated by arrow 765.

[0099] It can be noted that in some configurations, client node 705 and / or configuration node 710 may include wireless devices capable of operating in a GI-ISAC configuration. If client node 705 has such capabilities, it can provide capability reports, receive GI-ISAC configuration information, and perform GI-ISAC RF measurements (e.g., as a Tx node and / or Rx node) in a manner similar to the processes described above with respect to helper nodes 715 and 720. If configuration node 710 has such capabilities (e.g., including a base station), it can participate in the execution of GI-ISAC RF measurements as a Tx node and / or Rx node. (Expected) Figure 7 Other variations of the examples illustrated may depend on the type of device / node that is capable of having GI-ISAC functionality and can be used to participate in performing GI-ISAC RF measurements.

[0100] Figure 7Various aspects of the process enable the flexible use of GI-ISAC in a variety of applications. For example, in one case, the ISAC QoS for sensing (provided by client node 705 to configuration node 710 at arrow 735) may include speed estimation key performance indicators (KPIs), such as speed resolution and maximum definite range. According to some embodiments, the GI-ISAC configuration determined at box 740 may include a CPI determined based on a set of available CPI configuration settings from the codebook for speed and range KPIs. According to some embodiments, the GI-ISAC waveform can be used for range / speed estimation for short-range sensing when communicating with another communicating Rx node (e.g., in...). Figure 7 (Executed at box 755). According to some implementations, the GI mode used by the GI-ISAC configuration may include a sensing reference sequence with good correlation properties, the duration of which is suitable for supporting good target SNR and low overhead to communication ratio. According to some implementations, the GI may be adapted based on range requirements to support long-range radar sensing. In such instances, the GI may be selected as zero, and its duration may be tuned based on range requirements.

[0101] GI-ISAC waveforms can be flexibly adapted to other types of functionality. For example, ISAC symbols may also include RF sensing-centric communication data, such as phase-decoded LFM or NLFM, which have a constant GI duration for each symbol within the CPI. The GI may include, for example, zero, and / or may include a constant partial sequence that, when combined with the remaining symbol portions, achieves a sensing waveform with well-correlated properties.

[0102] In some implementations, the ISAC symbol of the GI-ISAC waveform may include a sensing symbol whose parameters may depend on the CP-OFDM configuration, such as an LFM or NLFM waveform. For example, an NLFM signal may be described by the following equation for its instantaneous frequency: (Equation 1) This represents a mixture of LFM and NLFM waveforms. Parameters in this equation include, for example, the LFM bandwidth. and NLFM bandwidth It can be selected to ensure that the allocated resource bandwidth (e.g., N resource elements (REs)) is used, and that the sensing symbols are aligned with CP-OFDM. Furthermore, the NLFM signal may include multiple symbols with time elapsed ( (One CP-OFDM symbol).

[0103] It can also be noted that configuration node 710 can provide GI-ISAC configuration information to nodes for purposes other than performing RF sensing to provide GI-ISAC measurement reports to client node 705 (as indicated by the operations at box 755 and arrows 760 and 765). For example, it can be used for interference cancellation. According to some embodiments, configuration node 710 can provide GI-ISAC configuration information to other nodes operating in ISAC mode ( Figure 7 (Not shown in the image) provides a GI configuration mode (provided at arrow 745 for assisting Tx node 715) for improved interference cancellation. For legacy nodes using CP-OFDM ( Figure 7 (Not shown in the image), configuration node 710 can provide instructions for handling interference from the GI-ISAC waveform. A legacy node may, for example, treat the GI-ISAC waveform as noise with a variance that can be provided by configuration node 710.

[0104] Figure 8 This is a flowchart of a method 800 for performing integrated RF sensing and communication according to an implementation scheme. Method 800 can be performed by a wireless device such as a sensing node (e.g., a UE or base station of a wireless network) as described herein. Aspects of method 800 can be integrated with… Figure 7 The illustrated help nodes 715 and / or 720 correspond to each other in functionality. The operation of method 800 can be performed by software and / or hardware components of the sensing node, and examples of such components are described below. Figure 10 and Figure 11 Example in.

[0105] At box 810, the functionality includes receiving GI-ISAC configuration from a configuration node of the wireless network at the wireless device, wherein the GI-ISAC configuration indicates a set of one or more parameters describing characteristics of a GI-ISAC waveform to be used by the wireless device for RF sensing, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on OFDM communication data symbols used by the wireless network. As noted herein, the parameters may describe frequency (e.g., bandwidth) or timing (e.g., symbol) characteristics that may be based on OFDM (e.g., CP-OFDM) communication data symbols. Figure 7 The functionality at arrows 745 and / or 750 corresponds to that.

[0106] According to some implementations, a set of one or more parameters describing the characteristics of a GI-ISAC waveform defines the GI mode of the GI-ISAC waveform. As noted in the implementations described herein, the GI mode may include a coherent processing interval (CPI), GI content within a CPI, one or more GI locations within a CPI, the duration of the GI, or any combination thereof. In some implementations where the GI mode includes a CPI, the CPI includes one or more consecutive time slots / micro-time slots, the CPI is determined at least partially based on a carrier frequency, the CPI is determined at least partially based on a sensed quality of service (QoS) metric, or any combination thereof. In such implementations, the CPI may be determined at least partially based on a sensed QoS metric. Furthermore, the sensed QoS metric may include velocity resolution, maximum range, or both. Additionally or alternatively, the GI mode may include GI content within a CPI. In such implementations, the GI content may include only zero, CP, or at least a portion of a sensed reference sequence.

[0107] As noted herein, the GI-ISAC waveform may be combined with an OFDM (e.g., CP-OFDM) waveform. Therefore, according to some embodiments of method 800, the GI-ISAC waveform may include ISAC symbols that comprise OFDM data sequences or sensing symbols. In such embodiments, the ISAC symbols may include sensing symbols, wherein the sensing symbols may include LFM or NLFM waveforms whose characteristics depend on the CP-OFDM configuration.

[0108] As described in the embodiments herein, some embodiments may allow GI-ISAC configuration to be based at least in part on capability information provided by the wireless device. For example, some embodiments may include transmitting a capability report prior to receiving the GI-ISAC configuration, the capability report indicating one or more capabilities of the wireless device for generating GI-ISAC waveforms to perform RF sensing functions.

[0109] Components and / or structures used to perform functionality at block 810 may include bus 1005, one or more processors 1010, digital signal processor (DSP) 1020, wireless communication interface 1030 (which may include RF sensing system 1035), one or more memories 1060, and / or other components of motion sensing node 1000, such as Figure 10 As illustrated and described below. Additionally or alternatively, components and / or structures for performing functionality at block 810 may include bus 1105, one or more processors 1110, DSP 1120, wireless communication interface 1130 (which may include RF sensing system 1135), one or more memories 1060, and / or other components of the stationary sensing node 1100, such as... Figure 11 The examples and descriptions below.

[0110] The functionality at box 820 includes performing RF sensing functions using a wireless device according to a GI-ISAC configuration. The functionality at box 920 can be, for example... Figure 7 This corresponds to functional block 755. The manner in which the RF sensing function is performed can vary depending on whether the wireless device is transmitting or receiving an RF sensing signal (or both). For example, in some embodiments, performing the RF sensing function may include: transmitting an RF signal with a GI-ISAC waveform, receiving an RF signal with a GI-ISAC waveform, or both. According to some embodiments, performing the RF sensing function may include: receiving an RF signal with a GI-ISAC waveform, performing a measurement on the received RF signal, and transmitting a report indicating the measurement to a configuration node.

[0111] Components and / or structures used to perform functionality at block 820 may include bus 1005, one or more processors 1010, digital signal processor (DSP) 1020, wireless communication interface 1030 (which may include RF sensing system 1035), one or more memories 1060, and / or other components of motion sensing node 1000, such as Figure 10 As illustrated and described below, additionally or alternatively, components and / or structures for performing functionality at block 820 may include bus 1105, one or more processors 1110, DSP 1120, wireless communication interface 1130 (which may include RF sensing system 1135), one or more memories 1060, and / or other components of the stationary sensing node 1100, such as... Figure 11 The examples and descriptions below.

[0112] Figure 9 This is a flowchart of a method 900 for integrating RF sensing and communication according to an implementation scheme. Method 900 can be performed by a configuration node (such as a base station or server (or other centralized controller) of a wireless network), as described herein. Aspects of method 900 can be integrated with... Figure 7 The illustrated configuration node 710 corresponds to this functionality. The operation of method 900 can be performed by software and / or hardware components of a computing device, and examples of such components are described below. Figure 12 Example in.

[0113] At box 910, the functionality includes determining a GI-ISAC configuration, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by a wireless device to perform RF sensing functions, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on OFDM communication data symbols used by the wireless network. Similarly, the parameters may describe frequency (e.g., bandwidth) or timing (e.g., symbol) characteristics that may be based on OFDM (e.g., CP-OFDM) communication data symbols. Figure 7 The functionality at position 740 corresponds to that of the box.

[0114] According to some implementations, a set of one or more parameters describing the characteristics of a GI-ISAC waveform defines the GI mode of the GI-ISAC waveform. As noted in the implementations described herein, the GI mode may include a coherent processing interval (CPI), GI content within a CPI, one or more GI locations within a CPI, the duration of the GI, or any combination thereof. In some implementations where the GI mode includes a CPI, the CPI includes one or more consecutive time slots / micro-time slots, the CPI is determined at least partially based on a carrier frequency, the CPI is determined at least partially based on a sensed quality of service (QoS) metric, or any combination thereof. In such implementations, the CPI may be determined at least partially based on a sensed QoS metric. Furthermore, the sensed QoS metric may include velocity resolution, maximum range, or both. Additionally or alternatively, the GI mode may include GI content within a CPI. In such implementations, the GI content may include only zero, CP, or at least a portion of a sensed reference sequence.

[0115] As noted herein, the GI-ISAC waveform may be combined with an OFDM (e.g., CP-OFDM) waveform. Therefore, according to some embodiments of method 900, the GI-ISAC waveform may include ISAC symbols that comprise OFDM data sequences or sensing symbols. In such embodiments, the ISAC symbols may include sensing symbols, wherein the sensing symbols may include LFM or NLFM waveforms whose characteristics depend on the CP-OFDM configuration.

[0116] As described in the embodiments herein, some embodiments may allow GI-ISAC configuration to be based at least in part on capability information provided by the wireless device. For example, some embodiments may include receiving a capability report at the configuration node prior to receiving the GI-ISAC configuration. This capability report indicates one or more capabilities of the wireless device for generating GI-ISAC waveforms to perform RF sensing functions, wherein a set of one or more parameters describing the characteristics of the GI-ISAC waveforms is further based at least in part on one or more capabilities of the wireless device for generating the GI-ISAC waveforms. This functionality may be related to… Figure 7 The functionality indicated by arrows 725 and / or 730 corresponds to that of the arrows.

[0117] Components and / or structures used to perform functionality at frame 910 may include bus 1205, one or more processors 1210, one or more storage devices 1225, communication subsystem 1230 (which may include wireless communication interface 1233), one or more memories 1235, and / or other components using system 1200, such as Figure 12 The examples and descriptions below.

[0118] The functionality at box 920 includes performing RF sensing functions using a wireless device according to a GI-ISAC configuration. The functionality at box 920 can be, for example... Figure 7 This corresponds to functional block 755. The manner in which the RF sensing function is performed can vary depending on whether the wireless device is transmitting or receiving an RF sensing signal (or both). For example, in some embodiments, performing the RF sensing function may include: transmitting an RF signal with a GI-ISAC waveform, receiving an RF signal with a GI-ISAC waveform, or both. According to some embodiments, performing the RF sensing function may include: receiving an RF signal with a GI-ISAC waveform, performing a measurement on the received RF signal, and transmitting a report indicating the measurement to a configuration node.

[0119] Components and / or structures used to perform functionality at frame 910 may include bus 1205, one or more processors 1210, one or more storage devices 1225, communication subsystem 1230 (which may include wireless communication interface 1233), one or more memories 1235, and / or other components using system 1200, such as Figure 12 The examples and descriptions below.

[0120] Figure 10 This is a block diagram of an embodiment of the mobile sensing node 1000 that can be utilized as described herein. For example, the mobile sensing node 1000 may correspond to a mobile device (e.g., Figure 1 Mobile device 105), UE (e.g., Figure 2UE 205), nodes (e.g., Figure 4 Node 1 and / or 2, Figure 7 Client nodes 705, helper nodes 715 and / or 720, etc., as described herein. Furthermore, as described below, the motion sensing node 1000 may implement an RF sensing system 1035, which may correspond to the above-described... Figure 3 The described RF sensing system 305. Furthermore, according to some embodiments, in some scenarios, the mobile sensing node 1000 can be used as a configuration node or device as described herein. Therefore, the mobile sensing node 1000 may be able to perform some or all of the functionalities described herein regarding sensing nodes and / or configuration nodes. It should be noted that... Figure 10 This is intended only to provide generalized examples of various components, any or all of which may be utilized as appropriate.

[0121] The motion sensing node 1000 is shown as including hardware elements electrically coupled (or otherwise communicable) via a bus 1005. The hardware elements may include a processor 1010, which may include, but is not limited to, one or more general-purpose processors (e.g., application processors), one or more special-purpose processors (such as digital signal processor (DSP) chips, graphics accelerator processors, application-specific integrated circuits (ASICs), etc.), and / or other processing structures or components. The processor 1010 may include one or more processing units, which may be housed in a single integrated circuit (IC) or multiple ICs. Figure 10 As shown, depending on the desired functionality, some implementations may have a separate DSP 1020. Wireless communication-based location determination and / or other determinations may be provided in the processor 1010 and / or the wireless communication interface 1030 (discussed below). The motion sensing node 1000 may also include: one or more input devices 1070, which may include, but are not limited to, one or more keyboards, touchscreens, touchpads, microphones, buttons, dials, switches, etc.; and one or more output devices 1015, which may include, but are not limited to, one or more displays (e.g., touchscreens), light-emitting diodes (LEDs), speakers, etc.

[0122] The mobile sensing node 1000 may also include a wireless communication interface 1030, which may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication device and / or a chipset (such as Bluetooth). ®The wireless communication interface (such as devices, IEEE 802.11 devices, IEEE 802.15.4 devices, Wi-Fi devices, WiMAX devices, WAN devices, and / or various cellular devices, etc.) enables the mobile sensing node 1000 to communicate and / or perform positioning with other devices relative to WLAN and / or cellular technologies, as described in the above embodiments. The wireless communication interface 1030 may permit the communication (e.g., sending and receiving) of data and signaling with NG-RAN nodes of the network, such as via eNB, gNB, ng-eNB, access points, NTN satellites, various base stations, TRPs and / or other access node types, and / or other network components, computer systems, and / or any other electronic devices communicatively coupled to a TRP, as described herein. Communication may be performed via one or more wireless communication antennas 1032 that transmit and / or receive wireless signals 1034. According to some embodiments, the wireless communication antennas 1032 may include multiple discrete antennas, antenna arrays, or any combination thereof. Antenna 1032 may be able to transmit and receive wireless signals using beams (e.g., Tx beams and Rx beams). Beamforming may be performed using digital and / or analog beamforming techniques with appropriate digital and / or analog circuitry. Wireless communication interface 1030 may include such circuitry.

[0123] As noted above, the mobile sensing node 1000 can implement the RF sensing system 1035. The RF sensing system 1035 may include the features described above. Figure 3 The described hardware and / or software components. For example... Figure 10 As illustrated and noted above, part or all of the RF sensing system 1035 may be implemented within the wireless communication interface 1030, which may utilize certain components for both communication and RF sensing. However, the implementation is not limited to this. Alternative implementations may include some or all of the RF sensing system within the RF sensing system 1035, separate from the wireless communication interface 1030 (e.g., where RF sensing may utilize a different frequency and / or different hardware / software components than the wireless communication interface 1030).

[0124] Depending on the desired functionality, the wireless communication interface 1030 may include separate receivers and transmitters, or any combination of transceivers, transmitters, and / or receivers, to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers (such as wireless devices and access points) as well as NTN satellites. The mobile sensing node 1000 can communicate with various data networks, which may include a variety of network types. For example, the WWAN may be a CDMA network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single Carrier Frequency Division Multiple Access (SC-FDMA) network, a WiMAX (IEEE 802.16) network, etc. A CDMA network may implement one or more RATs, such as CDMA2000. ® WCDMA, etc. CDMA2000 ® This includes IS-95, IS-2000, and / or IS-856 standards. TDMA networks can implement GSM, Digital Advanced Mobile Telephone Systems (D-AMPS), or some other RAT. OFDMA networks can employ LTE, Advanced LTE, 5G NR, etc. 5G NR, LTE, Advanced LTE, GSM, and WCDMA are described in documents from 3GPP. CDMA2000 ® This is described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) can also be an IEEE 802.11x network, while a wireless personal area network (WPAN) can be a Bluetooth network, IEEE 802.15x, or some other type of network. The technologies described herein can also be used in any combination of WWAN, WLAN, and / or WPAN.

[0125] The motion sensing node 1000 may also include a sensor 1040. The sensor 1040 may include, but is not limited to, one or more inertial sensors and / or other sensors (e.g., accelerometers, gyroscopes, cameras, magnetometers, altimeters, microphones, proximity sensors, light sensors, barometers, etc.), some of which can be used to obtain positioning-related measurements and / or other information. As noted above, according to some embodiments, the sensor 1040 may be used, for example, to determine the velocity of the motion sensing node, which may be reported to a configuration device.

[0126] An embodiment of the motion sensing node 1000 may further include a Global Navigation Satellite System (GNSS) receiver 1080, which is capable of receiving signals 1084 from one or more GNSS satellites using an antenna 1082 (which may be the same as antenna 1032). Positioning based on GNSS signal measurements may be used to supplement and / or incorporate the techniques described herein. The GNSS receiver 1080 may use conventional techniques to extract the positioning of the motion sensing node 1000 from GNSS satellites of GNSS systems such as Global Positioning System (GPS), Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) covering Japan, IRNSS covering India, BeiDou Navigation Satellite System (BDS), etc. In addition, the GNSS receiver 1080 can be used with various augmentation systems, such as satellite-based augmentation systems (SBAS), which can be associated with or otherwise enabled to be used with one or more global and / or regional navigation satellite systems, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Coverage Service (EGNOS), the Multifunctional Satellite Augmentation System (MSAS), and the Geographic Augmentation Navigation System (GAGAN).

[0127] It can be pointed out that, although in Figure 10 The GNSS receiver 1080 is illustrated as various components, but implementations are not limited thereto. As used herein, the term "GNSS receiver" may include hardware and / or software components configured to acquire GNSS measurements (measurements from GNSS satellites). Thus, in some implementations, the GNSS receiver may include (as software) a measurement engine executed by one or more processors, such as processor 1010, DSP 1020, and / or a processor within wireless communication interface 1030 (e.g., in a modem). The GNSS receiver may also optionally include a positioning engine that can use GNSS measurements from the measurement engine to determine the GNSS receiver's location using an extended Kalman filter (EKF), weighted least squares (WLS), particle filters, etc. The positioning engine may also be executed by one or more processors, such as processor 1010 or DSP 1020.

[0128] The mobile sensing node 1000 may also include a memory 1060 and / or communicate with that memory. The memory 1060 may include, but is not limited to, local and / or network-accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices such as random access memory (RAM) and / or read-only memory (ROM), which may be programmable, flash-updatable, etc. Such storage devices can be configured to implement any suitable data repository, including but not limited to various file systems, database structures, etc.

[0129] The memory 1060 of the motion sensing node 1000 may also include software elements ( Figure 10 (Not shown in the text) These software elements include operating systems, device drivers, executable libraries, and / or other code (such as one or more applications). These software elements may include computer programs provided by various embodiments and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more processes described with respect to the methods discussed above may be implemented as code and / or instructions in memory 1060 executable by motion sensing node 1000 (and / or processor 1010 or DSP 1020 within motion sensing node 1000). Then, in some embodiments, such code and / or instructions may be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0130] Figure 11 This is a block diagram of an embodiment of the stationary sensing node 1100 that can be utilized as described herein. For example, the stationary sensing node 1100 may correspond to a base station or an access node (e.g., Figure 1 Base station 100 and / or Figure 2 Access nodes 210, 214 and 216), nodes (e.g., Figure 4 Node 1 and / or 2, Figure 7 Client node 705, configuration node 710, help node 715 and / or 720, etc., as described herein. Furthermore, as described below, the stationary sensing node 1100 can implement an RF sensing system 1135, which can correspond to the above-described... Figure 3 The described RF sensing system 305. Furthermore, according to some embodiments, in some scenarios, the stationary sensing node 1100 can be used as a configuration node or device as described herein. Therefore, the stationary sensing node 1100 may be able to perform some or all of the functionalities described herein regarding sensing nodes and / or configuration nodes. It should be noted that... Figure 11This is intended only to provide generalized illustrations of various components, any or all of which may be utilized as appropriate. In some embodiments, the stationary sensing node 1100 may correspond to a gNB, ng-eNB, and / or (more generally) a TRP and / or a base station, as previously noted. In some cases, the stationary sensing node 1100 may include multiple TRPs (e.g., each TRP is associated with a different antenna or different antenna array (e.g., 1132) of the stationary sensing node 1100). As used herein, the transmitting functionality of a TRP may be performed using a transmitting point (TP), and / or the receiving functionality of a TRP may be performed by a receiving point (RP), which may be physically separate from or different from the TP. That is, a TRP may include both a TP and an RP.

[0131] Given the Open Radio Access Network (O-RAN) and / or Virtualized Radio Access Network (V-RAN or vRAN) in 5G or later networks, the functionality performed by the stationary sensing node 1100 in earlier generation networks (e.g., 3G and 4G) can be divided into different functional components (e.g., Radio Unit (RU), Distributed Unit (DU), and Central Unit (CU)) and layers (e.g., L1 / L2 / L3). These functional components can be performed on different devices at different locations connected, for example, via fronthaul, midhaul, and backhaul connections. As mentioned herein, a “base station” (or ng-eNB, gNB, etc.) may include any or all of these functional components. The functionality of these functional components can be determined by… Figure 11 One or more of the illustrated hardware and / or software components are used to perform this action.

[0132] The stationary sensing node 1100 is shown as including hardware elements electrically coupled (or otherwise communicable) via bus 1105. The hardware elements may include processor 1110, which may include, but is not limited to, one or more general-purpose processors, one or more special-purpose processors (such as digital signal processor (DSP) chips, graphics accelerator processors, application-specific integrated circuits (ASICs), etc.) and / or other processing structures or components. Figure 11 As shown, depending on the desired functionality, some implementations may have a separate DSP 1120. According to some implementations, wireless communication-based location determination and / or other determinations may be provided in the processor 1110 and / or the wireless communication interface 1130 (discussed below). The stationary sensing node 1100 may also include: one or more input devices, which may include, but are not limited to, a keyboard, display, mouse, microphone, buttons, dials, switches, etc.; and one or more output devices, which may include, but are not limited to, a display, light-emitting diodes (LEDs), speakers, etc.

[0133] The stationary sensing node 1100 may also include a wireless communication interface 1130, which may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication device and / or a chipset (such as Bluetooth). ® The wireless communication interface 1130 allows the stationary sensing node 1100 to communicate as described herein, including devices such as IEEE 802.11 devices, IEEE 802.15.4 devices, Wi-Fi devices, WiMAX devices, and cellular communication facilities. The wireless communication interface 1130 permits the transmission (e.g., sending and receiving) of data and signaling to the UE, other base stations / TRPs (e.g., eNB, gNB, and ng-eNB), and / or other network components, computer systems, and / or other electronic devices described herein. Communication may be performed via one or more wireless communication antennas 1132 that transmit and / or receive wireless signals 1134. According to some embodiments, the one or more wireless communication antennas 1132 may include one or more antenna arrays capable of beamforming.

[0134] As noted above, the stationary sensing node 1100 can implement the RF sensing system 1135. The RF sensing system 1135 may include the features described above. Figure 3 The described hardware and / or software components. For example... Figure 11 As illustrated and noted above, part or all of the RF sensing system 1135 may be implemented within the wireless communication interface 1130, which may utilize certain components for both communication and RF sensing. However, the implementation is not limited thereto. Alternative implementations may include some or all of the RF sensing system within the RF sensing system 1135, separate from the wireless communication interface 1130 (e.g., where RF sensing may utilize a different frequency and / or different hardware / software components than the wireless communication interface 1130).

[0135] The stationary sensing node 1100 may also include a network interface 1180, which may include support for wired communication technologies. The network interface 1180 may include a modem, network interface card (NIC), chipset, etc. The network interface 1180 may include one or more input and / or output communication interfaces to allow data exchange with networks, communication network servers, computer systems, and / or any other electronic devices described herein.

[0136] In many embodiments, the stationary sensing node 1100 may also include a memory 1160. The memory 1160 may include, but is not limited to, local and / or network-accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices such as random access memory (RAM) and / or read-only memory (ROM), which may be programmable, flash-updatable, etc. Such storage devices can be configured to implement any suitable data repository, including but not limited to various file systems, database structures, etc.

[0137] The memory 1160 of the stationary sensing node 1100 may also include software elements ( Figure 11 (Not shown in the text) These software elements include operating systems, device drivers, executable libraries, and / or other code (such as one or more applications). These software elements may include computer programs provided by various embodiments and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more processes described with respect to the methods discussed above may be implemented as code and / or instructions in memory 1160 executable by the stationary sensing node 1100 (and / or the processor 1110 or DSP 1120 within the stationary sensing node 1100). Then, in some embodiments, such code and / or instructions may be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0138] Figure 12 This is a block diagram of an embodiment of computer system 1200, which may be used, wholly or partially, to provide the functionality of one or more components and / or devices as described in the embodiments herein. Computer system 1200 may be utilized within and / or executed by a server (e.g., a location server / LMF or a sensing server / SnMF) or a base station / TRP (e.g., a gNB), which may execute configuration nodes (e.g., ...) as described herein. Figure 7 The configuration node 710) has the following functions. It should be noted that... Figure 12 This is intended only to provide generalized examples of various components, any or all of which may be utilized as appropriate. Therefore, Figure 12 This broadly illustrates how individual system components can be implemented in a relatively separate or relatively more integrated manner. Furthermore, it can be pointed out that... Figure 12 The illustrated components can be located in a single device and / or distributed among various networked devices, which may be located in different geographical locations.

[0139] Computer system 1200 is shown as including hardware elements electrically coupled (or otherwise communicated via bus 1205). The hardware elements may include processor 1210, which may include, but is not limited to, one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing chips, graphics accelerators, etc.), and / or other processing architectures, configured to perform one or more of the methods described herein. Computer system 1200 may also include one or more input devices 1215, which may include, but is not limited to, a mouse, keyboard, camera, microphone, etc.; and one or more output devices 1220, which may include, but is not limited to, display devices, printers, etc.

[0140] Computer system 1200 may also include one or more non-transitory storage devices 1225 (and / or communicate with said one or more non-transitory storage devices), which may include, but are not limited to, local and / or network-accessible storage devices, and / or may include, but are not limited to, disk drives, drive arrays, optical storage devices, solid-state storage devices such as random access memory (RAM) and / or read-only memory (ROM), which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any suitable data repository, including but not limited to various file systems, database structures, etc. Such data repositories may include databases and / or other data structures for storing and managing messages and / or other information to be transmitted via a hub to one or more devices, as described herein.

[0141] Computer system 1200 may also include a communication subsystem 1230, which may include wireless communication technologies managed and controlled by wireless communication interface 1233, as well as wired technologies (such as Ethernet, coaxial communication, Universal Serial Bus (USB), etc.). Wireless communication interface 1233 may include one or more wireless transceivers capable of transmitting and receiving wireless signals 1255 (e.g., signals according to 5G NR or LTE) via wireless antenna 1250. Therefore, communication subsystem 1230 may include modems, network interface cards (wireless or wired), infrared communication devices, wireless communication devices, and / or chipsets, enabling computer system 1200 to communicate with any device (including UE, base station and / or other transmit / receive point (TRP), satellite, and / or any other electronic device described herein) on any or all of the communication networks described herein. Therefore, communication subsystem 1230 can be used to receive and transmit data as described in the embodiments herein.

[0142] In many embodiments, the computer system 1200 will also include working memory 1235, which may include RAM or ROM devices as described above. Software elements shown as residing within working memory 1235 may include operating system 1240, device drivers, executable libraries, and / or other code (such as one or more applications 1245), which may include computer programs provided by various embodiments and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more processes described with respect to the methods discussed above may be implemented as code and / or instructions executable by a computer (and / or a processor within a computer); then, in one aspect, such code and / or instructions may be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0143] The collection of these instructions and / or code may be stored on a non-transitory computer-readable storage medium (such as storage device 1225 described above). In some cases, the storage medium may be incorporated into a computer system such as computer system 1200. In other embodiments, the storage medium may be separate from the computer system (e.g., a removable medium, such as an optical disc), and / or may be provided in an installation package such that the storage medium can be used to program, configure, and / or adapt a general-purpose computer containing the instructions / code. These instructions may take the form of executable code that can be executed by computer system 1200, and / or may take the form of source and / or installable code that, when compiled and / or installed on computer system 1200 (e.g., using any of a variety of commonly available compilers, installers, compression / decompression utilities, etc.), takes the form of executable code.

[0144] It will be apparent to those skilled in the art that basic modifications can be made to suit specific requirements. For example, custom hardware can also be used, and / or specific elements can be implemented in hardware, software (including portable software such as applets), or both. Furthermore, connections to other computing devices, such as network input / output devices, can be employed.

[0145] Referring to the accompanying drawings, components that may include memory may include non-transitory machine-readable media. As used herein, the terms "machine-readable media" and "computer-readable media" refer to any storage medium that participates in providing data that enables a machine to operate in a particular manner. In the embodiments provided above, various machine-readable media may be involved in providing instructions / code to a processor and / or other devices for execution. Additionally or alternatively, machine-readable media may be used to store and / or carry such instructions / code. In many specific embodiments, computer-readable media are physical and / or tangible storage media. Such media may take many forms, including but not limited to non-volatile and volatile media. Common forms of computer-readable media include, for example: magnetic and / or optical media, any other physical media with a hole pattern, RAM, programmable ROM (PROM), erasable PROM (EPROM), FLASH-EPROM, any other memory chip or memory cartridge, or any other medium from which a computer can read instructions and / or code.

[0146] The methods, systems, and apparatus discussed herein are examples. Various embodiments may omit, substitute, or add various processes or components as appropriate. For example, features described for some embodiments may be combined in various other embodiments. Different aspects and elements of embodiments may be combined in a similar manner. The various components in the accompanying drawings provided herein may be embodied in hardware and / or software. Furthermore, technology evolves, and therefore many elements are examples that do not limit the scope of this disclosure to those particular examples.

[0147] It has been proven convenient to sometimes refer to such signals as bits, information, values, elements, symbols, characters, variables, items, numbers, numerical symbols, etc., primarily for common use. However, it should be understood that all such terms or similar terms should be associated with appropriate physical quantities and are merely convenient labels. Unless otherwise specifically stated, it is as apparent from the above discussion that throughout this specification, discussions using terms such as “processing,” “calculating,” “determining,” “identifying,” “ascertaining,” “identifying,” “associating,” “measuring,” and “executing” refer to the actions or processes of a specific device such as a dedicated computer or similar dedicated electronic computing device. Therefore, in the context of this specification, a dedicated computer or similar dedicated electronic computing device is capable of manipulating or transforming signals, generally referred to as physical, electronic, electrical, or magnetic quantities in the memory, registers, or other information storage devices, transmitting devices, or display devices of the dedicated computer or similar dedicated electronic computing device.

[0148] As used herein, the terms “and” and “or” may include a variety of meanings, which are also contemplated, at least in part, depending on the context in which such terms are used. Generally, “or,” when used in relation to a list such as A, B, or C, is intended to mean A, B, and C (in the inclusive sense) and A, B, or C (in the exclusive sense). Furthermore, as used herein, the term “one or more” can be used to describe any feature, structure, or characteristic in the singular form, or to describe some combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example, and the claimed subject matter is not limited to this example. Additionally, the term “at least one of…” when used in relation to a list such as A, B, or C can be interpreted as meaning any combination of A, B, and / or C, such as A, AB, AA, AAB, AABBCCC, etc.

[0149] Several embodiments have been described, and various modifications, alternative constructions, and equivalents may be used without departing from the scope of this disclosure. For example, the above elements may be components of a larger system, where other rules may take precedence over the application of various embodiments or otherwise modify the application of various embodiments. Furthermore, multiple steps may be performed before, during, or after considering the above elements. Therefore, the above description does not limit the scope of this disclosure.

[0150] In view of this specification, various embodiments may include different combinations of features. Specific examples of embodiments are described in the following numbered clauses: Clause 1: A method for performing integrated radio frequency (RF) sensing and communication at a wireless device, the method comprising: receiving, at the wireless device, a guard interval integrated sensing and communication (GI-ISAC) configuration from a configuration node of a wireless network, wherein the GI-ISAC configuration indicates a set of one or more parameters describing characteristics of a GI-ISAC waveform to be used by the wireless device for RF sensing, wherein the set of one or more parameters describing characteristics of the GI-ISAC waveform is at least partially based on orthogonal frequency division multiplexing (OFDM) communication data symbols used by the wireless network; and utilizing the wireless device to perform RF sensing functionality according to the GI-ISAC configuration.

[0151] Clause 2: The method according to Clause 1, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform defines a guard interval (GI) mode of the GI-ISAC waveform, wherein the GI mode includes: coherent processing interval (CPI), GI content within the CPI, one or more GI positions within the CPI, duration of the GI, or any combination thereof.

[0152] Clause 3: The method according to Clause 2, wherein the GI mode includes the CPI, and wherein: the CPI includes one or more consecutive time slots / micro time slots, the CPI is determined at least in part based on the carrier frequency, the CPI is determined at least in part based on a sensed quality of service (QoS) metric, or any combination thereof.

[0153] Clause 4: The method according to any one of Clauses 2 to 3, wherein the CPI is determined at least in part based on the sensed QoS metric, and wherein the sensed QoS metric includes: speed resolution, maximum range, or both.

[0154] Clause 5: The method according to any one of Clauses 2 to 4, wherein the GI mode includes the GI content within the CPI, and wherein the GI content includes: only zero, cyclic prefix (CP), or at least a portion of the sensing reference sequence.

[0155] Clause 6: The method according to any one of Clauses 2 to 5, wherein the GI-ISAC waveform includes an Integrated Sensing and Communication (ISAC) symbol, which includes an OFDM data sequence or a sensing symbol.

[0156] Clause 7: The method described in Clause 6, wherein the ISAC symbol includes the sensing symbol, the sensing symbol including a linear frequency modulation (LFM) waveform or a nonlinear frequency modulation (NLFM) waveform whose characteristics depend on the CP-OFDM configuration.

[0157] Clause 8: The method according to any one of Clauses 1 to 7 further comprises: transmitting a capability report prior to receiving the GI-ISAC configuration, the capability report indicating one or more capabilities of the wireless device for generating the GI-ISAC waveform to perform the RF sensing function.

[0158] Clause 9: The method according to any one of Clauses 1 to 8, wherein performing the RF sensing function includes: transmitting an RF signal having the GI-ISAC waveform, receiving an RF signal having the GI-ISAC waveform, or both.

[0159] Clause 10: The method according to Clause 9, wherein performing the RF sensing function includes: receiving the RF signal having the GI-ISAC waveform; performing a measurement of the received RF signal; and transmitting a report indicating the measurement to the configuration node.

[0160] Clause 11: The method according to any one of Clauses 1 to 10, wherein the wireless device includes user equipment (UE) or a base station.

[0161] Clause 12: A method for implementing integrated radio frequency (RF) sensing and communication at a configuration node of a wireless network, the method comprising: determining a guard interval integrated sensing and communication (GI-ISAC) configuration, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by a wireless device to perform RF sensing functions, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on orthogonal frequency division multiplexing (OFDM) communication data symbols used by the wireless network; and transmitting the GI-ISAC configuration to the wireless device.

[0162] Clause 13: The method according to Clause 12, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform defines a guard interval (GI) mode of the GI-ISAC waveform, wherein the GI mode includes: coherent processing interval (CPI), GI content within the CPI, one or more GI positions within the CPI, duration of the GI, or any combination thereof.

[0163] Clause 14: The method according to Clause 13, wherein the GI mode includes the CPI, and wherein: the CPI includes one or more consecutive time slots / micro-time slots, the CPI is determined at least in part based on the carrier frequency, the CPI is determined at least in part based on a sensed quality of service (QoS) metric, or any combination thereof.

[0164] Clause 15: The method according to any one of Clauses 13 to 14, wherein the CPI is determined at least in part based on the sensed QoS metric, and wherein the sensed QoS metric includes: speed resolution, maximum range, or both.

[0165] Clause 16: The method according to any one of Clauses 13 to 15, wherein the GI mode includes the GI content within the CPI, and wherein the GI content includes: only zero, cyclic prefix (CP), or at least a portion of the sensing reference sequence.

[0166] Clause 17: The method according to any one of Clauses 12 to 16, wherein the GI-ISAC waveform includes an Integrated Sensing and Communication (ISAC) symbol, which includes an OFDM data sequence or a sensing symbol.

[0167] Clause 18: The method according to Clause 17, wherein the ISAC symbol includes the sensing symbol, the sensing symbol including a linear frequency modulation (LFM) waveform or a nonlinear frequency modulation (NLFM) waveform whose characteristics depend on the CP-OFDM configuration.

[0168] Clause 19: The method according to any one of Clauses 12 to 18, further comprising: receiving a capability report at the configuration node before determining the GI-ISAC configuration, the capability report indicating one or more capabilities of the wireless device for generating the GI-ISAC waveform to perform the RF sensing function, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is further based at least in part on the one or more capabilities of the wireless device for generating the GI-ISAC waveform.

[0169] Clause 20: The method according to any one of Clauses 12 to 19, wherein the configuration node includes a base station or server of the wireless network.

[0170] Clause 21: A wireless device for performing integrated radio frequency (RF) sensing and communication, the wireless device comprising: one or more transceivers; one or more memories; and one or more processors communicatively coupled to the one or more transceivers and the one or more memories, the one or more processors being configured to: receive, at the wireless device, a guard interval integrated sensing and communication (GI-ISAC) configuration from a configuration node of a wireless network, wherein the GI-ISAC configuration indicates a set of one or more parameters describing characteristics of a GI-ISAC waveform to be used by the wireless device for RF sensing, wherein the set of one or more parameters describing characteristics of the GI-ISAC waveform is at least partially based on orthogonal frequency division multiplexing (OFDM) communication data symbols used by the wireless network; and perform RF sensing functions using the one or more transceivers according to the GI-ISAC configuration.

[0171] Clause 22: A wireless device pursuant to Clause 21, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform defines a guard interval (GI) mode of the GI-ISAC waveform, wherein the GI mode includes: a coherent processing interval (CPI), GI content within a CPI, one or more GI locations within a CPI, the duration of a GI, or any combination thereof.

[0172] Clause 23: A wireless device pursuant to any one of Clauses 21 or 22, wherein the GI-ISAC waveform includes an Integrated Sensing and Communication (ISAC) symbol, which includes an OFDM data sequence or a sensing symbol.

[0173] Clause 24: A wireless device pursuant to any one of Clauses 21 to 23, wherein the one or more processors are configured to: transmit a capability report prior to receiving the GI-ISAC configuration, the capability report indicating one or more capabilities of the wireless device for generating the GI-ISAC waveform to perform the RF sensing function.

[0174] Clause 25: A wireless device according to any one of Clauses 21 to 24, wherein, in order to perform the RF sensing function, the one or more processors are configured to: transmit an RF signal having the GI-ISAC waveform, receive an RF signal having the GI-ISAC waveform, or both.

[0175] Clause 26: A wireless device pursuant to any one of Clauses 21 to 25, wherein the wireless device includes a user equipment (UE) or a base station.

[0176] Clause 27: A configuration node for a wireless network, the configuration node comprising: one or more transceivers; one or more memories; and one or more processors, the one or more processors being communicatively coupled to the one or more transceivers and the one or more memories, the one or more processors being configured to: determine a Guard Interval Integrated Sensing and Communication (GI-ISAC) configuration, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by a wireless device to perform radio frequency (RF) sensing functions, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on Orthogonal Frequency Division Multiplexing (OFDM) communication data symbols used by the wireless network; and transmit the GI-ISAC configuration to the wireless device via the one or more transceivers.

[0177] Clause 28: The configuration node as described in Clause 27, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform defines the guard interval (GI) mode of the GI-ISAC waveform, wherein the GI mode includes: coherent processing interval (CPI), GI content within the CPI, one or more GI positions within the CPI, duration of the GI, or any combination thereof.

[0178] Clause 29: A configuration node according to any one of Clauses 27 or 28, wherein the one or more processors are further configured to: receive a capability report at the configuration node before determining the GI-ISAC configuration, the capability report indicating one or more capabilities of the wireless device for generating the GI-ISAC waveform to perform the RF sensing function, wherein the one or more processors are further configured to: cause the set of one or more parameters describing the characteristics of the GI-ISAC waveform to be at least partially based on the one or more capabilities of the wireless device for generating the GI-ISAC waveform.

[0179] Clause 30: A configuration node pursuant to any one of Clauses 27 to 29, wherein the configuration node includes a base station or server of the wireless network.

[0180] Clause 31: An apparatus having components for performing the method according to any one of Clauses 1 to 20.

[0181] Clause 32: A non-transitory computer-readable medium storing instructions, said instructions including code for performing a method according to any one of Clauses 1 to 20.

Claims

1. A method for performing integrated radio frequency (RF) sensing and communication at a wireless device, the method comprising: At the wireless device, a Guard Interval Integrated Sensing and Communication (GI-ISAC) configuration is received from a configuration node of the wireless network, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by the wireless device for RF sensing, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on Orthogonal Frequency Division Multiplexing (OFDM) communication data symbols used by the wireless network. as well as The wireless device performs RF sensing functions according to the GI-ISAC configuration.

2. The method of claim 1, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform defines a guard interval (GI) mode of the GI-ISAC waveform, wherein the GI mode includes: Coherence Processing Interval (CPI) GI content within CPI One or more GI locations within CPI The duration of GI, or Any combination of them.

3. The method of claim 2, wherein the GI mode includes the CPI, and wherein: The CPI includes one or more continuous time slots / micro time slots. The CPI is determined at least in part based on the carrier frequency. The CPI is determined at least in part based on a sensed quality of service (QoS) metric, or Any combination of them.

4. The method of claim 3, wherein the CPI is determined at least in part based on the sensed QoS metric, and wherein the sensed QoS metric comprises: Speed ​​resolution, Maximum range, or Both.

5. The method of claim 2, wherein the GI mode includes the GI content within the CPI, and wherein the GI content includes: Only zero, Cyclic prefix (CP), or Sensing at least a portion of the reference sequence.

6. The method of claim 1, wherein the GI-ISAC waveform includes an Integrated Sensing and Communication (ISAC) symbol, the Integrated Sensing and Communication (ISAC) symbol including an OFDM data sequence or a sensing symbol.

7. The method of claim 6, wherein the ISAC symbol includes the sensing symbol, the sensing symbol including a linear frequency modulation (LFM) waveform or a nonlinear frequency modulation (NLFM) waveform whose characteristics depend on the CP-OFDM configuration.

8. The method according to claim 1, further comprising: Before receiving the GI-ISAC configuration, a capability report is transmitted, which indicates one or more capabilities of the wireless device for generating the GI-ISAC waveform to perform the RF sensing function.

9. The method of claim 1, wherein performing the RF sensing function comprises: Sending an RF signal with the GI-ISAC waveform, receiving an RF signal with the GI-ISAC waveform, or both.

10. The method of claim 9, wherein performing the RF sensing function comprises: Receive the RF signal having the GI-ISAC waveform; Perform measurements on the received RF signals; as well as A report instructing the measurement is transmitted to the configuration node.

11. The method of claim 1, wherein the wireless device comprises a user equipment (UE) or a base station.

12. A method for implementing integrated radio frequency (RF) sensing and communication at a configuration node in a wireless network, the method comprising: Determine a Guard Interval Integrated Sensing and Communication (GI-ISAC) configuration, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by a wireless device to perform RF sensing functions, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on orthogonal frequency division multiplexing (OFDM) communication data symbols used by the wireless network; as well as The GI-ISAC configuration is transmitted to the wireless device.

13. The method of claim 12, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform defines a guard interval (GI) mode of the GI-ISAC waveform, wherein the GI mode includes: Coherence Processing Interval (CPI) GI content within CPI One or more GI locations within CPI The duration of GI, or Any combination of them.

14. The method of claim 13, wherein the GI mode includes the CPI, and wherein: The CPI includes one or more continuous time slots / micro time slots. The CPI is determined at least in part based on the carrier frequency. The CPI is determined at least in part based on a sensed quality of service (QoS) metric, or Any combination of them.

15. The method of claim 14, wherein the CPI is determined at least in part based on the sensed QoS metric, and wherein the sensed QoS metric comprises: Speed ​​resolution, Maximum range, or Both.

16. The method of claim 13, wherein the GI mode includes the GI content within the CPI, and wherein the GI content includes: Only zero, Cyclic prefix (CP), or Sensing at least a portion of the reference sequence.

17. The method of claim 12, wherein the GI-ISAC waveform includes an Integrated Sensing and Communication (ISAC) symbol, the Integrated Sensing and Communication (ISAC) symbol including an OFDM data sequence or a sensing symbol.

18. The method of claim 17, wherein: The ISAC symbol includes the sensing symbol, which includes a linear frequency modulation (LFM) waveform or a nonlinear frequency modulation (NLFM) waveform whose characteristics depend on the CP-OFDM configuration.

19. The method according to claim 12, further comprising: Before determining the GI-ISAC configuration, a capability report is received at the configuration node. The capability report indicates one or more capabilities of the wireless device for generating the GI-ISAC waveform to perform the RF sensing function, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is further based at least in part on the one or more capabilities of the wireless device for generating the GI-ISAC waveform.

20. The method of claim 12, wherein the configuration node includes a base station or server of the wireless network.

21. A wireless device for performing integrated radio frequency (RF) sensing and communication, the wireless device comprising: One or more transceivers; One or more memory units; and One or more processors, said one or more processors being communicatively coupled to said one or more transceivers and said one or more memories, said one or more processors being configured to: At the wireless device, a Guard Interval Integrated Sensing and Communication (GI-ISAC) configuration is received from a configuration node of the wireless network, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by the wireless device for RF sensing, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on Orthogonal Frequency Division Multiplexing (OFDM) communication data symbols used by the wireless network. as well as The RF sensing function is performed using one or more transceivers according to the GI-ISAC configuration.

22. The wireless device of claim 21, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform defines a guard interval (GI) mode of the GI-ISAC waveform, wherein the GI mode includes: Coherence Processing Interval (CPI) GI content within CPI One or more GI locations within CPI The duration of GI, or Any combination of them.

23. The wireless device of claim 21, wherein the GI-ISAC waveform includes an Integrated Sensing and Communication (ISAC) symbol, the Integrated Sensing and Communication (ISAC) symbol including an OFDM data sequence or a sensing symbol.

24. The wireless device of claim 21, wherein the one or more processors are configured to: transmit a capability report prior to receiving the GI-ISAC configuration, the capability report indicating one or more capabilities of the wireless device for generating the GI-ISAC waveform to perform the RF sensing function.

25. The wireless device of claim 21, wherein, in order to perform the RF sensing function, the one or more processors are configured to: transmit an RF signal having the GI-ISAC waveform, receive an RF signal having the GI-ISAC waveform, or both.

26. The wireless device of claim 21, wherein the wireless device comprises a user equipment (UE) or a base station.

27. A configuration node for a wireless network, the configuration node comprising: One or more transceivers; One or more memory units; and One or more processors, said one or more processors being communicatively coupled to said one or more transceivers and said one or more memories, said one or more processors being configured to: Determine a guard interval integrated sensing and communication (GI-ISAC) configuration, wherein the GI-ISAC configuration indicates a set of one or more parameters describing the characteristics of a GI-ISAC waveform to be used by a wireless device to perform radio frequency (RF) sensing functions, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform is at least partially based on orthogonal frequency division multiplexing (OFDM) communication data symbols used by the wireless network; as well as The GI-ISAC configuration is transmitted to the wireless device via the one or more transceivers.

28. The configuration node of claim 27, wherein the set of one or more parameters describing the characteristics of the GI-ISAC waveform defines a guard interval (GI) mode of the GI-ISAC waveform, wherein the GI mode includes: Coherence Processing Interval (CPI) GI content within CPI One or more GI locations within CPI The duration of GI, or Any combination of them.

29. The configuration node of claim 27, wherein the one or more processors are further configured to: receive a capability report at the configuration node before determining the GI-ISAC configuration, the capability report indicating one or more capabilities of the wireless device for generating the GI-ISAC waveform to perform the RF sensing function, wherein the one or more processors are further configured to: cause the set of one or more parameters describing the characteristics of the GI-ISAC waveform to be at least partially based on the one or more capabilities of the wireless device for generating the GI-ISAC waveform.

30. The configuration node of claim 27, wherein the configuration node includes a base station or server of the wireless network.

Images