Calibration of sensing radio frequency measurement information

Abstract

Techniques for sensing calibration are disclosed. In an aspect, a communication device obtains a set of attributes associated with a sensing radio frequency (RF-S) calibration target, obtains measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target, and determines an RF-S calibration compensation set based on the measurement information and the set of attributes. In another aspect, a communication device determines a location of a target object based on a set of RF-S calibration compensations.

Description

Background Technology 1. Technical Field

[0002] All aspects of this disclosure relate to wireless technology.

[0003] 2. Relevant Technical Descriptions

[0004] Wireless communication systems have evolved through many generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), as well as digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), and others.

[0005] The fifth-generation (5G) wireless standard, known as New Radio (NR), delivers higher data transfer speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on Positioning Reference Signals (RS-P), such as downlink, uplink, or sidelink Positioning Reference Signals (PRS)), and other technological enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advancements in the PRS process and technology, and the high-density deployment of 5G, enable high-accuracy positioning based on 5G. Summary of the Invention

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

[0007] In one aspect, a method of operating a communication device includes: obtaining a set of attributes associated with a radio frequency for sensing (RF-S) calibration target; obtaining measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target; and determining an RF-S calibration compensation set based on the measurement information and the set of attributes.

[0008] In one aspect, a method of operating a communication device includes: obtaining a sensing radio frequency (RF-S) calibration compensation set, wherein the RF-S calibration compensation set is based on a set of attributes associated with an RF-S calibration target and first measurement information associated with an RF-S calibration process between a set of wireless sensing nodes and the RF-S calibration target; obtaining second measurement information associated with an RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; and determining the location of the target object based on the second measurement information and the RF-S calibration compensation set.

[0009] In one aspect, a communication device includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: obtain a set of attributes associated with a sensing radio frequency (RF-S) calibration target; obtain measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target; and determine an RF-S calibration compensation set based on the measurement information and the set of attributes.

[0010] In one aspect, a communication device includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: obtain a sensing radio frequency (RF-S) calibration compensation set, wherein the RF-S calibration compensation set is based on a set of attributes associated with an RF-S calibration target and first measurement information associated with an RF-S calibration process between a set of wireless sensing nodes and the RF-S calibration target; obtain second measurement information associated with an RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; and determine the location of the target object based on the second measurement information and the RF-S calibration compensation set.

[0011] In one aspect, a communication device includes: components for obtaining a set of attributes associated with a sensing radio frequency (RF-S) calibration target; components for obtaining measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target; and components for determining an RF-S calibration compensation set based on the measurement information and the set of attributes.

[0012] In one aspect, a communication device includes: components for obtaining a sensing radio frequency (RF-S) calibration compensation set, wherein the RF-S calibration compensation set is based on a set of attributes associated with an RF-S calibration target and first measurement information associated with an RF-S calibration process between a set of wireless sensing nodes and the RF-S calibration target; components for obtaining second measurement information associated with an RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; and components for determining the location of the target object based on the second measurement information and the RF-S calibration compensation set.

[0013] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a communication device, cause the communication device to: obtain a set of attributes associated with a sensing radio frequency (RF-S) calibration target; obtain measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target; and determine an RF-S calibration compensation set based on the measurement information and the set of attributes.

[0014] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a communication device, cause the communication device to: obtain a sensing radio frequency (RF-S) calibration compensation set, wherein the RF-S calibration compensation set is based on a set of attributes associated with an RF-S calibration target and first measurement information associated with an RF-S calibration process between a set of wireless sensing nodes and the RF-S calibration target; obtain second measurement information associated with an RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; and determine the location of the target object based on the second measurement information and the RF-S calibration compensation set.

[0015] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Attached Figure Description

[0016] The accompanying drawings are provided to help describe various aspects of this disclosure, and are provided for illustrative purposes only and not to limit the aspects.

[0017] Figure 1Example wireless communication systems according to various aspects of this disclosure are illustrated.

[0018] Figure 2A , Figure 2B and Figure 2C Example wireless network architectures based on various aspects of this disclosure are illustrated.

[0019] Figure 3A , Figure 3B and Figure 3C It is a simplified block diagram of several examples of components that can be used in user equipment (UE), base stations and network entities and configured to support communications as taught herein.

[0020] Figure 4 This is a diagram illustrating an example frame structure according to various aspects of this disclosure.

[0021] Figure 5A and Figure 5B This is a diagram illustrating example sidelink time slot structures with and without feedback resources according to various aspects of this disclosure.

[0022] Figure 6A and Figure 6B Different types of wireless sensing according to various aspects of this disclosure are illustrated.

[0023] Figure 7 An example call flow is illustrated for a New Radio (NR)-based sensing process in which sensing parameters are configured for network configuration, according to various aspects of this disclosure.

[0024] Figure 8 An exemplary process of communication according to one aspect of this disclosure is illustrated.

[0025] Figure 9 An exemplary process of communication according to one aspect of this disclosure is illustrated.

[0026] Figure 10 Examples of various aspects according to this disclosure are shown respectively. Figures 8 to 9 The specific implementation of the process is illustrated in the example. Detailed Implementation

[0027] Various aspects of this disclosure are provided below in the description of various examples provided for illustrative purposes and in the accompanying drawings. Alternative aspects may be devised without departing from the scope of this disclosure. Additionally, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0028] Various aspects generally involve the calibration of radio frequency (RF-S) measurements for sensing. In RF-S, wireless signals are transmitted from one or more transmitting points and received at one or more receiving points after being reflected by a target. RF-S facilitates many candidate applications, including intruder detection, animal / pedestrian / UAV intrusion detection on highways and railways, rainfall monitoring, flood sensing, autonomous driving, automated ground 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. One of the key challenges in facilitating RF-S in NR is ensuring the correct calibration of TX / RX sensing nodes, including group delay, phase, and amplifiers. In some designs, this requires knowledge of the characteristics of the target being tracked (i.e., a target with known measurements).

[0029] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. Aspects of this disclosure relate to determining a set of RF-S calibration compensations (or offsets) based on measurement information associated with an RF-S calibration process performed against an RF-S calibration target. In one aspect, a set of properties associated with the RF-S calibration target is known and used to determine the set of RF-S calibration compensations. Such aspects can provide various technical advantages, such as improved RF-S accuracy and / or reduced RF-S latency, which in turn can improve various tracking functions, including but not limited to intruder detection, animal / pedestrian / UAV intrusion detection on highways and railways, rainfall monitoring, flood perception, autonomous driving, automated ground vehicle (AGV) detection / tracking / collision avoidance, intelligent parking and assistance, UAV trajectory and tracking, crowd management, sleep / health monitoring, gesture recognition, extended reality (XR) streaming, public safety search and rescue, etc.

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

[0031] Those skilled in the art will understand that any of a variety of different techniques and methods can be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0032] Furthermore, many aspects are described according to a sequence of actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be considered entirely embodied in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of this disclosure can be embodied in a variety of different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0033] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset positioning device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Equipment,” “Mobile Terminal,” “Mobile Station,” or variations thereof. Generally, a UE can communicate with a core network via the RAN, and through the core network, a UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, etc.).

[0034] A base station may operate according to one of several RATs to communicate with the UE, depending on the network in which it is deployed, and may alternatively be referred to as an Access Point (AP), Network Node, Node B, Evolved Node B (eNB), Next Generation eNB (ng-eNB), New Radio (NR) Node B (also referred to as gNB or gNodeB), etc. The base station may primarily be used to support the UE's radio access, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can transmit signals to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can transmit signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

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

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

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

[0038] Figure 1 An example wireless communication system 100 according to various aspects of this disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base station 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell base station may include an eNB and / or an ng-eNB (wherein the wireless communication system 100 corresponds to an LTE network), or a gNB (wherein the wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

[0039] Base station 102 can collectively form a RAN and interface with core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) via backhaul link 122, and interface with one or more location servers 172 (e.g., location management function (LMF) or secure user plane location (SUPL) location platform (SLP)) via core network 170. Location server 172 can be part of core network 170 or can be external to core network 170. Location server 172 can be integrated with base station 102. UE 104 can communicate with location server 172 directly or indirectly. For example, UE 104 can communicate with location server 172 via base station 102 currently serving UE 104. UE 104 can also communicate with location server 172 via another path, such as via application server (not shown), via another network, such as via wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), etc. For signaling purposes, communication between UE 104 and location server 172 can be represented as an indirect connection (e.g., via core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), wherein intermediate nodes (if present) are omitted from the signaling diagram for clarity.

[0040] In addition to other functions, base station 102 may perform functions associated with one or more of the following: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) on backhaul link 134, which may be wired or wireless.

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

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

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

[0044] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a free channel assessment (CCA) or listen-before-talk (LBT) process before communication to determine whether the channel is available.

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

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

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

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

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

[0050] The transmit and receive beams can be spatially correlated. Spatial correlation means that parameters for a second beam (e.g., transmit or receive beam) for a second reference signal can be derived based on information about a first beam (e.g., receive or transmit beam) for a first reference signal. For example, a UE can use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0051] It is important to note that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving the downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this differs from the designation used by the International Telecommunication Union. ® Extremely high frequency (EHF) bands (30 GHz to 300 GHz) are designated as “millimeter wave” bands.

[0053] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have designated the operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0054] In light of the foregoing, unless otherwise specifically stated, it should be understood that, as used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0055] In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by UE 104 / 182 and the cell, where UE 104 / 182 performs an initial Radio Resource Control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. Secondary carriers may contain only the necessary signaling information and signals. For example, since the primary uplink and primary downlink carriers are typically UE-specific, the UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which a base station communicates, the terms "cell," "serving cell," "component carrier," and "carrier frequency" can be used interchangeably.

[0056] For example, still refer to Figure 1One of the frequencies used by macro cell base station 102 can be an anchor carrier (or "PCell"), and the other frequencies used by macro cell base station 102 and / or mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, compared to the data rate obtained by a single 20MHz carrier, two aggregated 20MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40MHz).

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

[0058] In some cases, UE 164 and UE 182 may be able to communicate via sidelink. A sidelink-capable UE (SL-UE) can communicate with base station 102 via communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via radio sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). Radio sidelink (or simply "sidelink") is an adaptation of core cellular network (e.g., LTE, NR) standards that allows direct communication between two or more UEs without the need for communication through a base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communication may be located within the geographical coverage area 110 of base station 102. Other SL-UEs in this group may be outside the geographical coverage area 110 of base station 102, or may be unable to receive transmissions from base station 102 for other reasons. In some cases, the groups of SL-UEs communicating via sidelink communication may utilize a one-to-many (1:M) system, where each SL-UE transmits to every other SL-UE in the group. In some cases, base station 102 facilitates the scheduling of resources used for sidelink communication. In other cases, sidelink communication is performed between the individual SL-UEs without involving base station 102.

[0059] On one hand, the sidelink 160 can operate via a wireless communication medium of interest that can be shared with other vehicles and / or infrastructure access points and other RATs for wireless communication. "Medium" can include one or more time, frequency, and / or space communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. On another hand, the medium of interest may correspond to at least a portion of unlicensed frequency bands shared among various RATs. While different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the U.S. Federal Communications Commission (FCC), these systems (particularly those employing small cell access points) have recently extended their operation to unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include various variants of CDMA, TDMA, FDMA, Orthogonal FDMA (OFDMA), Single-Carrier FDMA (SC-FDMA), and so on.

[0060] It should be noted that, although Figure 1 Only two of these UEs are exemplified as SL-UEs (i.e., UE 164 and UE 182), but any UE exemplified can be an SL-UE. Furthermore, although only UE 182 is described as capable of beamforming, any UE exemplified (including UE 164) can be capable of beamforming. When SL-UEs are capable of beamforming, they can beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base station 102, base station 180, small cell 102', access point 150), etc. Therefore, in some cases, UE 164 and UE 182 can utilize beamforming via sidelink 160.

[0061] exist Figure 1 In the example, the UE shown (for simplicity, in) Figure 1Any UE (shown as a single UE 104) can receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one aspect, SV 112 may be part of a satellite positioning system that allows UE 104 to use as an independent source of location information. Satellite positioning systems typically include a system of transmitters (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from the transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. While typically located in SV 112, transmitters may sometimes be located at ground-based control stations, base stations 102, and / or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 in order to derive geographic location information from SV 112.

[0062] In a satellite positioning system, the use of signal 124 can be enhanced by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise made capable of being used with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential correction, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlap Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), GPS-assisted geographic augmentation navigation, or GPS and geographic augmentation navigation system (GAGAN). Therefore, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0063] On one hand, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 connects to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as the modified base station 102 (without a ground antenna) or network nodes in a 5GC. This element, in turn, provides access to other elements in the 5G network and ultimately to entities outside the 5G network, such as internet web servers and other user equipment. Thus, as a replacement or supplement to communication signals from the ground base station 102, UE 104 can receive communication signals (e.g., signal 124) from SV 112.

[0064] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1 In one example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this D2D P2P link), and has a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, D2D P2P links 192 and 194 can utilize any known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct). ® ,Bluetooth ® (etc.) to support.

[0065] Figure 2A An example wireless network architecture 200 is illustrated. For instance, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which work together to form the core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, specifically to user plane functions 212 and control plane functions 214, respectively. In an additional configuration, the ng-eNB 224 can also connect to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the next-generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either or both of the gNBs 222 or ng-eNBs 224 can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0066] Another optional aspect may include a location server 230, which can communicate with the 5GC 210 to provide location assistance to the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204, which may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be located outside the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0067] Figure 2B Another example wireless network architecture 240.5GC 260 is illustrated (which can be used with...). Figure 2AThe 5GC 210 (corresponding to 5GC 210) can be functionally considered as a control plane function provided by the Access and Mobility Management Function (AMF) 264 and a user plane function provided by the User Plane Function (UPF) 262, which work together to form the core network (i.e., 5GC 260). The functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and the Session Management Function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and the Short Message Service Function (SMSF) (not shown), and Secure Anchoring Functionality (SEAF). AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204 and receives an intermediate key established as a result of the UE 204's authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM) authentication, AMF 264 retrieves security material from the AMF. AMF 264 also includes Security Context Management (SCM). The SCM receives a key from the SEAF and uses this key to derive an access network-specific key. AMF 264 functionality also includes location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between NG-RAN 220 and LMF 270, Evolved Packet System (EPS) bearer identifier allocation for EPS interoperability, and UE 204 mobility event notification. Furthermore, AMF 264 also supports non-3GPP... ® (Third Generation Partner Program) Access network functionality.

[0068] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnecting to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., strobing, redirection, traffic steering), lawful eavesdropping (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and delivering and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and location servers (such as SLP 272) on the user plane.

[0069] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, service orientation configuration at UPF 262 for routing services to the correct destination, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0070] Another optional aspect may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each can correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 can support similar functions to LMF 270, but while LMF 270 can communicate with AMF 264, NG-RAN 220, and UE 204 on the control plane (e.g., using interfaces and protocols designed to deliver signaling messages rather than voice or data), SLP 272 can communicate with UE 204 and external clients (e.g., third-party server 274) on the user plane (e.g., using protocols designed to carry voice and / or data, such as Transmit Control Protocol (TCP) and / or IP).

[0071] Another optional aspect may include a third-party server 274, which can communicate with LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimation) of UE 204. Therefore, in some cases, the third-party server 274 may be referred to as a Location Services (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0072] User plane interface 263 and control plane interface 265 connect 5GC 260, and specifically connect UPF 262 and AMF 264 to one or more gNB 222 and / or ng-eNB 224 in NG-RAN 220. The interface between gNB 222 and / or ng-eNB 224 and AMF 264 is referred to as the "N2" interface, while the interface between gNB 222 and / or ng-eNB 224 and UPF 262 is referred to as the "N3" interface. The gNB 222 and / or ng-eNB 224 of NG-RAN 220 can communicate directly with each other via backhaul connection 223, referred to as the "Xn-C" interface. One or more of gNB 222 and / or ng-eNB 224 can communicate with one or more UEs 204 via a radio interface referred to as the "Uu" interface.

[0073] The functionality of the gNB 222 is divided among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically allocated to the gNB-DU 228, including user data delivery, mobility control, radio access network sharing, location, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Media Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of gNB 222 is typically managed by one or more independent gNB-RU 229s, which perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Therefore, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0074] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or components) performing base station functions) can be implemented in aggregated or decomposed architectures. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5GNB, AP, TRP, cells, etc.) can be implemented as aggregated base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations.

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

[0076] Base station type operation or network design can consider the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN) (such as those developed by the O-RAN Alliance), and other similar networks. ® This can be used in proposed network configurations or virtualized radio access networks (vRAN, also known as cloud radio access networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0077] Figure 2C An example disaggregated base station architecture 250 according to various aspects of this disclosure is illustrated. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with the core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 via one or more disaggregated base station units (such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link or a non-real-time (non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) framework 255, or both). CUs 280 may communicate with one or more duplex units (DUs) 285 (e.g., gNB-DU 228) via a corresponding midhaul link (e.g., an F1 interface). DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RU 229) via a corresponding fronthaul link. RU 287 can communicate with the corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, UE 204 can be served by multiple RU 287s simultaneously.

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

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

[0080] DU 285 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 287s. In some aspects, DU 285 may be at least partially based on functional partitioning (such as that provided by the 3rd Generation Partnership Project (3GPP)). ®The DU285 is functionally partitioned to host one or more of the RLC layer, MAC layer, and one or more high-PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some respects, the DU285 may further host one or more low-PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU285 or with control functions hosted by the CU280.

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

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

[0083] The non-RT RIC 257 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 259. The non-RT RIC 257 can be coupled to or communicate with the near-RT RIC 259, such as via an A1 interface. The near-RT RIC 259 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 280s, one or more DU 285s, or both, and O-eNBs to the near-RT RIC 259.

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

[0085] Figure 3A , Figure 3B and Figure 3C Examples are shown that can be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of...). Figure 2A and Figure 2BSeveral example components (represented by corresponding boxes) of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure (such as private networks) depicted herein support the operation as described herein. It should be understood that these components may be implemented in different specific implementations in different types of devices (e.g., in ASICs, in System-on-Chip (SoCs), etc.). The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Furthermore, a given device may contain one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0086] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, which provide components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) for communication via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356 for communication with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) through a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively; and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0087] In at least some cases, UE 302 and base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide access over a wireless communication medium of interest via at least one designated RAT (e.g., Wi-Fi, LTE Direct, Bluetooth). ® ZIGBEE ® Z-WAVE ® Components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) that enable communication between PC5, Dedicated Short-Range Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near Field Communication (NFC), Ultra-Wideband (UWB), etc.) and other network nodes (such as other UEs, access points, base stations, etc.). Short-range transceivers 320 and 360 can be configured in different ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) respectively according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.) respectively. Specifically, the short-range wireless transceiver 320 and short-range wireless transceiver 360 each include: one or more transmitters 324 and 364 respectively for transmitting and encoding signals 328 and 368, and one or more receivers 322 and 362 respectively for receiving and decoding signals 328 and 368. As a specific example, the short-range wireless transceiver 320 and short-range wireless transceiver 360 can be Wi-Fi transceivers, Bluetooth transceivers, etc. ® Transceiver, Zigbee ® and / or Z-WAVE ® Transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0088] In at least some cases, UE 302 and base station 304 also include satellite signal interfaces 330 and 370, each satellite signal interface including one or more satellite signal receivers 332 and 372, and optionally including one or more satellite signal transmitters 334 and 374, respectively. In some cases, base station 304 may be a terrestrial base station that can communicate with a spacecraft (e.g., spacecraft 112) via satellite signal interface 370. In other cases, base station 304 may be a spacecraft (or other non-terrestrial entity) that uses satellite signal interface 370 to communicate with terrestrial networks and / or other spacecraft.

[0089] Satellite signal receivers 332 and 372 can be connected to one or more antennas 336 and 376, respectively, and can provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. When satellite signal receivers 332 and 372 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 can be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS) signals, etc. When satellite signal receivers 332 and 372 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 332 and 372 can include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 332 and 372 may request appropriate information and operations from other systems, and in at least some cases, use measurements obtained by any suitable satellite positioning system algorithm to perform calculations to determine the locations of UE 302 and base station 304, respectively.

[0090] Optional satellite signal transmitters 334 and 374 (when present) can be connected to one or more antennas 336 and 376, respectively, and can be provided with components for transmitting satellite positioning / communication signals 338 and 378, respectively. When satellite signal transmitter 374 is a satellite positioning system transmitter, the satellite positioning / communication signal 378 can be a GPS signal, GLONASS signal, etc. ® Signals include Galileo signals, BeiDou signals, NAVIC signals, and QZSS signals. When satellite signal transmitters 334 and 374 are NTN transmitters, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal transmitters 334 and 374 can include any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. Satellite signal transmitters 334 and 374 can request appropriate information and operations from other systems.

[0091] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, which provide components (e.g., transmitting components, receiving components, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. Similarly, network entity 306 may use one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0092] Transceivers can be configured to communicate via wired or wireless links. A transceiver (whether wired or wireless) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some embodiments, the transceiver may be an integrated device (e.g., implementing transmitter and receiver circuitry in a single device), in some embodiments it may include separate transmitter and receiver circuitry, or in other embodiments it may be implemented in a different manner. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceiver 380 and network transceiver 390 in some embodiments) may be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform transmit beamforming, as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter and receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that the corresponding device may perform only receive or only transmit at a given time, rather than both receive and transmit simultaneously. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

[0093] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some specific embodiments, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some specific embodiments) may generally be described as "transceiver," "at least one transceiver," or "one or more transceivers." Therefore, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication performed. For example, backhaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0094] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operation disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 342, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 342, 384, and 394 may provide components for processing, such as components for determining, components for calculating, components for receiving, components for transmitting, components for indicating, etc. In one aspect, processors 342, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0095] UE 302, base station 304, and network entity 306 each include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Therefore, memories 340, 386, and 396 can provide components for storage, retrieval, maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may each include RF-S calibration components 348, 388, and 398. RF-S calibration components 348, 388, and 398 may be hardware circuitry that is part of or coupled to processors 342, 384, and 394, respectively, which, when executed, enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other respects, RF-S calibration components 348, 388, and 398 may be external to processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, RF-S calibration components 348, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 342, 384, and 394 (or a modem processing system, another processing system, etc.), cause UE 302, base station 304, and network entity 306 to perform the functions described herein. Figure 3A Possible locations for the RF-S calibration component 348 are illustrated. The RF-S calibration component may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 342, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for the RF-S calibration component 388 are illustrated. The RF-S calibration component may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for the RF-S calibration component 398 are illustrated. The RF-S calibration component may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a standalone component.

[0096] UE 302 may include one or more sensors 344 coupled to one or more processors 342 to provide components for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal interfaces 330. By way of example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate positioning in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0097] In addition, UE 302 includes a user interface 346 that provides components for providing instructions to a user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touchscreen, microphone, etc.). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0098] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more processors 384 can implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority processing, and logical channel priority ordering.

[0099] Transmitter 354 and receiver 352 implement Layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator can be used to determine the decoding and modulation scheme, as well as for spatial processing. These channel estimates can be derived from a reference signal transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas 356. Transmitter 354 can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0100] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 342. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. Then, data and control signals are provided to one or more processors 342, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0101] In the downlink, one or more processors 342 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the core network. One or more processors 342 are also responsible for error detection.

[0102] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, one or more processors 342 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority processing, and logical channel priority ordering.

[0103] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0104] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to one or more processors 384.

[0105] In the uplink, one or more processors 384 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from UE 302. IP packets from one or more processors 384 can be provided to the core network. One or more processors 384 are also responsible for error detection.

[0106] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3CThe example shown herein includes various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionalities in different designs. In particular, Figures 3A to 3C Various components are optional in alternative configurations, and various aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In certain cases, specific implementations of UE 302 may omit the WWAN transceiver 310 (e.g., wearable devices, tablets, personal computers (PCs), or laptops may have Wi-Fi and / or Bluetooth). ® The short-range wireless transceiver 320 can be omitted (e.g., cellular only), or the satellite signal interface 330 can be omitted, or the sensor 344 can be omitted, etc. In another example, in Figure 3B In certain cases, specific implementations of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite signal interface 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0107] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 308, 382, ​​and 392, respectively. In one aspect, data buses 308, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, in cases where different logical entities are embodied in the same device (e.g., gNB and location server functionality integrated into the same base station 304), data buses 308, 382, ​​and 392 can provide communication between these different logical entities.

[0108] Figure 3A , Figure 3B and Figure 3C The components can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components can be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or combine at least one memory component for storing information or executable code used by the circuit to provide that functionality. For example, some or all of the functionalities represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionalities represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Moreover, some or all of the functionalities represented by blocks 390 to 398 may be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it should be understood that such operations, actions and / or functions can actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 342, 384, 394, transceivers 310, 320, 350 and 360, memory 340, 386 and 396, RF-S calibration components 348, 388 and 398, etc.).

[0109] In some designs, network entity 306 may be implemented as a core network component. In other designs, network entity 306 may operate differently from the network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, network entity 306 may be a component of a private network that can be configured to communicate with UE 302 via base station 304 or independently of base station 304 (e.g., via a non-cellular communication link such as Wi-Fi).

[0110] Various frame structures can be used to support downlink and uplink transmission between network nodes (e.g., base stations and UEs). Figure 4 Figure 400 illustrates an example frame structure according to various aspects of this disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

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

[0112] LTE supports a single set of parameters (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR can support multiple sets of parameters (µ), for example, subcarrier spacings of 15kHz (µ=0), 30kHz (µ=1), 60kHz (µ=2), 120kHz (µ=3), and 240kHz (µ=4) or larger can be available. Within each subcarrier spacing, there are 14 symbols per time slot. For a 15kHz SCS (µ=0), there is one time slot per subframe, 10 time slots per frame, a time slot duration of 1 millisecond (ms), a symbol duration of 66.7 microseconds (µs), and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 30kHz SCS (µ=1), there are two time slots per subframe, 20 time slots per frame, a time slot duration of 0.5ms, a symbol duration of 33.3µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 60kHz SCS (µ=2), there are four time slots per subframe, 40 time slots per frame, a time slot duration of 0.25ms, a symbol duration of 16.7µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 120kHz SCS (µ=3), there are eight time slots per subframe, 80 time slots per frame, a time slot duration of 0.125ms, a symbol duration of 8.33µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 240kHz SCS (µ=4), there are 16 time slots per subframe, 160 time slots per frame, a time slot duration of 0.0625ms, a symbol duration of 4.17µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size.

[0113] exist Figure 4 In the example, a parameter set of 15kHz is used. Therefore, in the time domain, a 10ms frame is divided into 10 equal-sized subframes, each 1ms long, and each subframe includes one time slot. Figure 4 In the diagram, time is represented horizontally (on the X-axis), with time increasing from left to right, while frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0114] A resource grid can be used to represent time slots, each of which includes one or more time-concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE corresponds to a symbol length in the time domain and a subcarrier in the frequency domain. Figure 4In the parameter set, for a normal cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0115] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 4 An example location (labeled "R") of an RE carrying a reference signal is shown.

[0116] Sidelink communication occurs within transmit or receive resource pools. In the frequency domain, the smallest unit of resource allocation is a subchannel (e.g., a set of consecutive PRBs in the frequency domain). In the time domain, resource allocation is performed within a time slot interval. However, some time slots are unavailable for sidelinks, and some time slots contain feedback resources. Furthermore, sidelink resources can be (pre-)configured to occupy fewer than 14 symbols in a time slot.

[0117] Configure sidelink resources at the Radio Resource Control (RRC) layer. RRC configuration can be pre-configured (e.g., pre-loaded on the UE) or configured (e.g., from the serving base station).

[0118] The NR side link supports Hybrid Automatic Repeat Request (HARQ) retransmission. Figure 5A This is a diagram 500 illustrating an example time slot structure without feedback resources based on various aspects of this disclosure. Figure 5A In the example, time is represented horizontally and frequency vertically. In the time domain, the length of each block is one Orthogonal Frequency Division Multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel. Currently, the (pre-)configured subchannel size can be selected from a set of {10, 15, 20, 25, 50, 75, 100} Physical Resource Blocks (PRBs).

[0119] For sidelink time slots, the first symbol is a repetition of the previous symbol and is used for automatic gain control (AGC) settings. This is in Figure 5A This is illustrated using vertical and horizontal hashing. For example... Figure 5AAs shown, for sidelinks, the Physical Sidelink Control Channel (PSCCH) and the Physical Sidelink Shared Channel (PSSCH) are transmitted in the same time slot. Similar to the Physical Downlink Control Channel (PDCCH), the PSCCH carries control information about sidelink resource allocation and a description of the sidelink data sent to the UE. Likewise, similar to the Physical Downlink Shared Channel (PDSCH), the PSSCH carries the UE's user data. Figure 5A In the example, the PSCCH occupies half the bandwidth of the subchannel and only takes up three symbols. Finally, the gap symbol appears after the PSSCH.

[0120] Figure 5B This is a diagram 550 illustrating an example time-slot structure with feedback resources based on various aspects of this disclosure. Figure 5B In the example, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel.

[0121] Figure 5B The illustrated time slot structure and Figure 5A The illustrated time slot structures are similar, but the difference is... Figure 5B The illustrated time slot structure includes feedback resources. Specifically, the last two symbols of the time slot are dedicated to the Physical Side Link Feedback Channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol used for AGC setup. In addition to the gap symbol following the PSFCH, there is a gap symbol after the two PSFCH symbols. Currently, the resources used for the PSFCH can be configured using a periodicity selected from the set of {0, 1, 2, 4} time slots.

[0122] Wireless communication signals transmitted between the UE and the base station (e.g., radio frequency (RF) signals configured to carry orthogonal frequency division multiplexing (OFDM) symbols according to wireless communication standards such as LTE, NR, etc.) can be used for environmental sensing (also known as "RF sensing" or "radar"). Environmental sensing using wireless communication signals can be considered as consumer-grade radar with advanced detection capabilities, enabling contactless / device-free interaction with devices / systems, etc. Wireless communication signals can be cellular communication signals, such as LTE or NR signals, WLAN signals such as Wi-Fi signals, etc. As a specific example, wireless communication signals can be OFDM waveforms as utilized in LTE and NR. High-frequency communication signals, such as millimeter-wave (mmW) RF signals, are particularly advantageous for use as sensing signals because higher frequencies provide at least more accurate ranging (distance) detection.

[0123] Potential uses for RF sensing include: health monitoring, such as heart rate detection and respiratory rate monitoring; gesture recognition, such as human activity recognition, keystroke detection, and sign language recognition; context information acquisition, such as location detection / tracking, direction finding, and distance estimation; and automotive sensing, such as intelligent cruise control and collision avoidance.

[0124] There are different types of sensing, including single-station sensing (also known as "active sensing") and dual-station sensing (also known as "passive sensing"). Figure 6A and Figure 6B These different types of sensing are illustrated. Specifically, Figure 6A This is illustration 600 illustrating a single-station sensing scenario, and Figure 6B This is illustration 630, illustrating a dual-station sensing scenario. Figure 6A In this configuration, the transmitter (Tx) and receiver (Rx) are co-located in the same sensing device 604 (e.g., a UE). The sensing device 604 transmits one or more RF sensing signals 634 (e.g., uplink or sidelink positioning reference signals (PRS) in the case of a UE), and some of the RF sensing signals 634 are reflected from a target object 606. The sensing device 604 can measure various properties of the reflected RF sensing signals 634 (e.g., time of arrival (ToA), angle of arrival (AoA), phase shift, etc.) to determine the characteristics of the target object 606 (e.g., size, shape, speed, motion state, etc.).

[0125] exist Figure 6B In this architecture, the transmitter (Tx) and receiver (Rx) are not co-located; that is, they are separate devices (e.g., the UE and the base station). It should be noted that although... Figure 6B The example illustrates the use of a downlink RF signal as the RF sensing signal 632, but uplink or sidelink RF signals can also be used as the RF sensing signal 632. In the downlink scenario, as shown in the figure, the transmitter is the base station and the receiver is the UE, while in the uplink scenario, the transmitter is the UE and the receiver is the base station.

[0126] For more detailed information, please refer to [link / reference]. Figure 6B Transmitter device 602 sends RF sensing signals 632 and 634 (e.g., positioning reference signal (PRS)) to sensing device 604, but some of the RF sensing signal 634 is reflected from the target object 606. Sensing device 604 (also referred to as "sensing device") can measure the time of arrival (ToA) of the RF sensing signal 632 received directly from the transmitter device and the time of reflection 636 of the RF sensing signal 634 reflected from the target object 606.

[0127] More specifically, as described above, a transmitter device (e.g., a base station) may transmit a single RF signal or multiple RF signals to a sensing device (e.g., a UE). However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple RF signals corresponding to each transmitted RF signal. Each path may be associated with a cluster of one or more channel taps. Typically, the time when the receiver detects the first channel tap cluster is considered to be the ToA of the RF signal on the site line (LOS) path (i.e., the shortest path between the transmitter and receiver). Subsequent channel tap clusters are considered to have been reflected by objects between the transmitter and receiver, and therefore have been along a non-LOS (NLOS) path between the transmitter and receiver.

[0128] Therefore, return to the reference. Figure 6B RF sensing signal 632 follows the LOS path between transmitter device 602 and sensing device 604, while RF sensing signal 634 follows the NLOS path between transmitter device 602 and sensing device 604 due to reflection from target object 606. Transmitter device 602 may have transmitted multiple RF sensing signals 632 and 634, some of which follow the LOS path and others follow the NLOS path. Alternatively, transmitter device 602 may have transmitted a single RF sensing signal in a sufficiently wide beam, a portion of which follows the LOS path (RF sensing signal 632) and a portion of which follows the NLOS path (RF sensing signal 634).

[0129] Based on the ToA of the LOS path, the ToA of the NLOS path, and the speed of light, sensing device 604 can determine the distance to a target object. For example, sensing device 604 can calculate the distance to the target object as the difference between the ToA of the LOS path and the ToA of the NLOS path multiplied by the speed of light. Furthermore, if sensing device 604 is capable of receiving beamforming, it can determine the approximate direction to the target object as the direction (angle) of the receiving beam that receives the RF sensing signal following the NLOS path. That is, sensing device 604 can determine the direction to the target object as the angle of arrival (AoA) of the RF sensing signal, which is the angle of the receiving beam used to receive the RF sensing signal. Sensing device 604 can then optionally report this information to transmitter device 602, its serving base station, application server associated with the core network, external client, third-party application, or some other sensing entity. Alternatively, the sensing device 604 may report the ToA measurement to the transmitter device 602 or other sensing entity (e.g., if the sensing device 604 itself does not have the processing capability to perform the calculation), and the transmitter device 602 may determine the distance to the target object 606 and optionally determine the direction to the target object.

[0130] It should be noted that if the RF sensing signal is an uplink RF signal sent by the UE to the base station, the base station will perform object detection based on the uplink RF signal, just as the UE does based on the downlink RF signal.

[0131] Similar to conventional radar, wireless communication-based sensing signals can be used to estimate the range (distance), velocity (Doppler), and angle (AoA) of a target. However, performance (e.g., resolution and maximum values ​​of range, velocity, and angle) can depend on the design of the reference signal.

[0132] Figure 7 An example call flow 700 is illustrated, illustrating an NR-based sensing process (e.g., a dual-site sensing process) for configuring sensing parameters in a network, according to various aspects of this disclosure. Although Figure 7 The example illustrates a network-coordinated sensing process, but this sensing process can be coordinated via a sidelink channel.

[0133] At stage 705, the sensing server 770 (e.g., inside or outside the core network) transmits a request for network (NW) information to the gNB 722 (e.g., the serving gNB of UE 704). This request may be for a list of the serving cell and any neighboring cells of UE 704. At stage 710, the gNB 722 transmits the requested information to the sensing server 770. At stage 715, the sensing server 770 transmits a request for sensing capabilities to UE 704. At stage 720, UE 704 provides its sensing capabilities to the sensing server 770.

[0134] At phase 725, the sensing server 770 transmits to the UE 704 a configuration indicating one or more reference signal (RS) resources to be transmitted for sensing. The reference signal resources may be transmitted by the serving cell and / or neighboring cells identified at phase 710. In some cases, Figure 7 The illustrated NR-based sensing process can be a sensing-only process or a Joint Communication and Sensing (JCS) process. In the case of a sensing-only process, the reference signal resource can be a reference signal resource specifically configured for sensing purposes. In the case of a JCS process, the reference signal resource can be a reference signal resource used for communication, which can also be used for sensing purposes. Alternatively, the reference signal resource used for sensing can be multiplexed with the reference signal resource used for communication (e.g., time-division multiplexing). For example, the reference signal resource used for communication can be an orthogonal frequency division multiplexing (OFDM) waveform, while the reference signal resource used for sensing can be a frequency modulated continuous wave (FMCW) waveform.

[0135] At stage 730, the sensing server 770 sends a request for sensing information to the UE 704. Then, the UE 704 measures the transmitted reference signal and, at stage 735, transmits the measurement or any sensing results determined based on the measurement to the sensing server 770.

[0136] On one hand, communication between the UE 704 and the sensing server 770 can be conducted via the LTE Positioning Protocol (LPP). Communication between the sensing server 770 and the gNB can be conducted via the NR Positioning Protocol Type A (NRPPa).

[0137] As described above, in sensing RF (RF-S), wireless signals are transmitted from one or more transmitting points and received at one or more receiving points after being reflected by a target. RF-S facilitates many candidate applications, including intruder detection, animal / pedestrian / UAV intrusion detection on highways and railways, rainfall monitoring, flood sensing, autonomous driving, automated ground 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.

[0138] One of the key challenges in facilitating RF-S in NR is ensuring proper calibration of the TX / RX sensing nodes, including group delay, phase, and amplifiers. In some designs, this requires knowledge of the characteristics of the target being tracked (i.e., a target with known measurements).

[0139] Various aspects of this disclosure relate to determining an RF-S calibration compensation (or offset) set based on measurement information associated with an RF-S calibration process performed against an RF-S calibration target. In one aspect, a set of attributes associated with the RF-S calibration target is known and used to determine the RF-S calibration compensation set. Such aspects can provide various technical advantages, such as improved RF-S accuracy and / or reduced RF-S latency, which in turn can improve various tracking functions, including but not limited to intruder detection, animal / pedestrian / UAV intrusion detection on highways and railways, rainfall monitoring, flood perception, autonomous driving, automated ground vehicle (AGV) detection / tracking / collision avoidance, intelligent parking and assistance, UAV trajectory and tracking, crowd management, sleep / health monitoring, gesture recognition, extended reality (XR) streaming, public safety search and rescue, etc.

[0140] Figure 8 An exemplary process 800 of communication according to one aspect of this disclosure is illustrated. Figure 8The process 800 is performed by the communication device. In some designs, the communication device may correspond to a network component (e.g., a gNB / BS 304 or an O-RAN component, or a remote location server such as network entity 306). In other designs, the communication device may correspond to a UE such as UE 302 (e.g., a sidelink anchor UE or a sidelink server UE). In scenarios where the communication device is integrated with another device (e.g., a UE, gNB, location server, etc.), any reference to any Rx / Tx operation between the communication device and the device integrated with the communication device may correspond to information transmission between different logical components of the device via a data bus, etc.

[0141] refer to Figure 8 At 810, communication devices (e.g., receivers 312, 322, 352, or 362, network transceivers 380 or 390, data buses 308, 382, ​​or 392, etc.) acquire a set of attributes associated with the sensing radio frequency (RF-S) calibration target. In some designs, components used to acquire the set of attributes at 810 include... Figures 3A to 3C Receivers 312, 322, 352, or 362; network transceivers 380 or 390; data buses 308, 382, ​​or 392, etc.

[0142] refer to Figure 8 At 820, communication devices (e.g., receivers 312, 322, 352, or 362, network transceivers 380 or 390, data buses 308, 382, ​​or 392, etc.) acquire measurement information associated with the RF-S calibration process between the first set of wireless sensing nodes and the RF-S calibration target. In some designs, components used to acquire the measurement information at 820 include... Figures 3A to 3C Receivers 312, 322, 352, or 362; network transceivers 380 or 390; data buses 308, 382, ​​or 392, etc.

[0143] refer to Figure 8 At point 830, the communication device (e.g., RF-S calibration component 348, 388, or 398, processor 342, 384, or 394, etc.) determines the RF-S calibration compensation set based on measurement information and a set of attributes. In some designs, the components used to perform the determination at point 830 include... Figures 3A to 3C RF-S calibration components 348, 388, or 398, processors 342, 384, or 394, etc.

[0144] refer to Figure 8 In some designs, the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node that does not belong to the set of wireless sensing nodes.

[0145] refer to Figure 8 In some designs, the first set of wireless sensing nodes includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0146] refer to Figure 8 In some designs, the communication device also sends an RF-S calibration compensation set to a second set of wireless sensing nodes. In one scenario, the first set and the second set of wireless sensing nodes at least partially overlap. In another scenario, the first set and the second set of wireless sensing nodes do not overlap.

[0147] refer to Figure 8 In some designs, the attribute set includes, for example:

[0148] • The location of the RF-S calibration target, or

[0149] • The shape of the RF-S calibration target, or

[0150] • The size of the RF-S calibration target, or

[0151] • The material composition of the outer surface of the RF-S calibration target, or

[0152] • The orientation of the RF-S calibration target, or

[0153] •RF-S calibration of the target's mobility status, or

[0154] • The speed of the RF-S calibration target, or

[0155] • RF-S calibration target trajectory, or

[0156] • Timing error information associated with the transmitter in the RF-S calibration process, or

[0157] • Any combination of them.

[0158] refer to Figure 8 In some designs, the RF-S calibration compensation set is also based on at least one location of at least one wireless sensing node from a first set of wireless sensing nodes.

[0159] refer to Figure 8 In some designs, at least one attribute from the attribute set is associated with the validity period specifying when that at least one attribute is allowed to be used for RF-S calibration compensation determination.

[0160] refer to Figure 8 In some designs, the attribute set is received via auxiliary data, or via auxiliary information signaling, or via broadcast, or any combination thereof.

[0161] refer to Figure 8 In some designs, the communication device further sends an RF-S calibration target attribute request, and the attribute set is received in response to the RF-S calibration target attribute request.

[0162] refer to Figure 8 In some designs, the set of attributes is obtained in association with the capability exchange of the RF-S calibration target's registration process with the communication device.

[0163] refer to Figure 8 In some designs, the RF-S calibration process is single-station and the first set of wireless sensing nodes includes a single wireless sensing node, or the RF-S calibration process is dual-station and the first set of wireless sensing nodes includes multiple wireless sensing nodes.

[0164] Figure 9 An exemplary process 900 of communication according to one aspect of this disclosure is illustrated. Figure 9 The process 900 is performed by the communication device. In some designs, the communication device may correspond to a network component (e.g., a gNB / BS 304 or an O-RAN component, or a remote location server such as network entity 306). In other designs, the communication device may correspond to a UE such as UE 302 (e.g., a sidelink anchor UE or a sidelink server UE). In scenarios where the communication device is integrated with another device (e.g., a UE, gNB, location server, etc.), any reference to any Rx / Tx operation between the communication device and the device integrated with the communication device may correspond to information transmission between different logical components of the device via a data bus, etc.

[0165] refer to Figure 9 At 910, the communication device (e.g., receiver 312 or 322 or 352 or 362, network transceiver 380 or 390, data bus 308 or 382 or 392, etc.) obtains a sensing radio frequency (RF-S) calibration compensation set. In one aspect, the RF-S calibration compensation set is based on a set of attributes associated with the RF-S calibration target and first measurement information associated with the RF-S calibration process between the set of wireless sensing nodes and the RF-S calibration target. For example, the RF-S calibration compensation set obtained at 910 may correspond to... Figure 8 The determined RF-S calibration compensation set is 830. In some designs, components used to obtain the RF-S calibration compensation set of 910 include... Figures 3A to 3C Receivers 312, 322, 352, or 362; network transceivers 380 or 390; data buses 308, 382, ​​or 392, etc.

[0166] refer to Figure 9At 920, a communication device (e.g., receiver 312 or 322 or 352 or 362, network transceiver 380 or 390, data bus 308 or 382 or 392, etc.) acquires second measurement information associated with the RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target. In some designs, the components for acquiring the second measurement information at 920 include Figures 3A to 3C Receivers 312, 322, 352, or 362; network transceivers 380 or 390; data buses 308, 382, ​​or 392, etc.

[0167] refer to Figure 9 At 930, the communication device (e.g., RF-S calibration component 348, 388, or 398, processor 342, 384, or 394, etc.) determines the location of the target object based on the second measurement information and the RF-S calibration compensation set. In some designs, the components used to perform the determination at 930 include Figures 3A to 3C RF-S calibration components 348, 388, or 398, processors 342, 384, or 394, etc.

[0168] refer to Figure 9 In some designs, the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node that does not belong to the set of wireless sensing nodes.

[0169] refer to Figure 9 In some designs, the wireless sensing node set includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0170] refer to Figure 9 In some designs, at least one wireless sensing node includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0171] refer to Figure 9 In some designs, the attribute set includes, for example:

[0172] • The location of the RF-S calibration target, or

[0173] • The shape of the RF-S calibration target, or

[0174] • The size of the RF-S calibration target, or

[0175] • The material composition of the outer surface of the RF-S calibration target, or

[0176] • The orientation of the RF-S calibration target, or

[0177] •RF-S calibration of the target's mobility status, or

[0178] • The speed of the RF-S calibration target, or

[0179] • RF-S calibration target trajectory, or

[0180] • Timing error information associated with the transmitter in the RF-S calibration process, or

[0181] • Any combination of them.

[0182] refer to Figure 9 In some designs, the RF-S calibration compensation set is also based on at least one location of at least one wireless sensing node from the set of wireless sensing nodes.

[0183] refer to Figure 9 In some designs, at least one attribute from the attribute set is associated with the validity period specifying when that at least one attribute is allowed to be used for RF-S calibration compensation determination.

[0184] refer to Figure 9 In some designs, the RF-S calibration process is single-station and the wireless sensing node set includes a single wireless sensing node, or the RF-S calibration process is dual-station and the wireless sensing node set includes multiple wireless sensing nodes.

[0185] refer to Figure 9 In some designs, the RF-S process is single-station and at least one wireless sensing node includes a single wireless sensing node, or the RF-S process is dual-station and at least one wireless sensing node includes multiple wireless sensing nodes.

[0186] refer to Figures 8 to 9 In a specific example where the set of attributes includes timing error information associated with the transmitter in an RF-S calibration process (e.g., dual-site or single-site RF-S operation), the timing error information may include RF group delay (e.g., delay of a specific RF chain at the transmitter) and / or desynchronization error. In the dual-site sensing example, it is assumed that the transmitter corresponds to TRP or UE1 (hereinafter referred to as TRP / UE1), and UE2 is the receiver. Assuming that the timing error at TRP / UE1 is known, it may be helpful for UE2 to know the timing error at TRP / UE1 if UE2 needs to estimate calibration compensation at UE2's Rx RF chain. A sensing server (e.g., LMF / SnMF) may provide these timing errors along with the attributes of the calibration target to UE2. On the other hand, if the location of TRP / UE1 is provided to UE2, UE2 may estimate the total calibration (i.e., sum calibration) of the link from TRP / UE1 to UE2.

[0187] refer to Figures 8 to 9In a specific example, a target with a known shape and location (e.g., an RF-S calibration target) can be installed, and a sensing node (e.g., a UE or TRP) can utilize these known targets to obtain calibration settings. Once calibrated, the sensing node (or other sensing nodes that have obtained calibration settings) can sense new targets. Alternatively, a mobile network operator can install a calibration target at a known location and share its location and shape attributes with the sensing node (and the sensing node location—if available) (e.g., a pole-mounted target). Examples of calibration targets (targets with simple shapes) include, for example, metal spheres, metal plates, dihedrals, trihedrals, etc.

[0188] In a specific example, execution Figure 8 The communication equipment used in the process may correspond to a sensing server (e.g., LMF or Sensing Management Function (SnMF)) that transmits RF-S calibration compensation sets to the UE and / or TRP via auxiliary data. Such aspects can provide various technical advantages, such as calibration of sensing nodes (e.g., UE, TRP, etc.) and enhanced sensing performance (i.e., accuracy, latency, etc.).

[0189] Figure 10 Examples of various aspects according to this disclosure are shown respectively. Figures 8 to 9 The process is illustrated in examples of 800 to 900, with specific implementation details of 1000. Figure 10 In this configuration, an RF-S calibration target 1010 is mounted on a street lamp 1020. A first sensing node (gNB1) sends RF-S signals 1030 to the RF-S calibration target 1010 and measures the reflections 1040 of those RF-S signals to obtain measurement information for generating RF-S calibration compensation. A second sensing node (UE1) also sends RF-S signals 1050 to the RF-S calibration target 1010 and measures the reflections 1060 of those RF-S signals to obtain measurement information for generating RF-S calibration compensation. The RF-S calibration compensation can be derived locally (e.g., at UE1 and / or gNB1) or remotely (e.g., at an LMF or SnMF).

[0190] refer to Figures 8 to 9In a specific example, a network entity (e.g., an LMF or SnMF) registers calibration targets for known attributes (e.g., shape, size, location, material type, and velocity—if any). In one aspect, a wireless device or sensing node (e.g., a UE / TRP) may transmit an indication of the calibration target for the known attributes (e.g., shape, size, location, material type, and velocity—if any) to the network entity. In another aspect, the wireless device or sensing node (e.g., a UE or gNB / TRP) receives a calibration target configuration from the network entity (e.g., an LMF or SnMF), and based on the calibration target configuration, the wireless device obtains measurements of the sensed reference signal (RS) and derives calibration compensation; the wireless device uses the derived calibration compensation for future measurements and shares the derived compensation and / or future measurements with the network entity.

[0191] refer to Figures 8 to 9 In a specific example, the calibration target configuration includes the following target attributes:

[0192] • Target location

[0193] • The shape of the target

[0194] • Target size

[0195] • Target material type

[0196] • Goal orientation

[0197] • The target's speed (if it is moving)

[0198] refer to Figures 8 to 9 In a specific example, the calibration target configuration includes wireless device (i.e., sensing node) attributes, such as the location of the wireless device.

[0199] refer to Figures 8 to 9 In a specific example, the calibration target configures the attributes of the second wireless device (i.e., the sensing node), such as the location of the second wireless device that transmits the sensing RS signal (if different from the first wireless device).

[0200] refer to Figures 8 to 9 In a specific example, the calibration target configuration includes validity timing; for example, the calibration target attribute is available within a time period / time range.

[0201] refer to Figures 8 to 9 In certain examples, the calibration target configuration can be transmitted based on a request from a wireless device. In one aspect, auxiliary data / information signaling (e.g., LPP auxiliary data, NRPPa auxiliary information) can be used to transmit the calibration target configuration. In another aspect, the calibration target configuration can be transmitted as a broadcast message (e.g., posSIB, senseSIB).

[0202] refer to Figures 8 to 9 In a specific example, the calibration target configuration can be transmitted based on a request from a wireless device (i.e., a sensing node). In one aspect, auxiliary data / information signaling (e.g., LPP auxiliary data, NRPPa auxiliary information) can be used to transmit the calibration target configuration. In another aspect, the calibration target configuration can be transmitted as a broadcast message (e.g., posSIB, senseSIB). In yet another aspect, the UE / TRP can register the calibration target with the LMF using capability exchange (e.g., LPP capability exchange or NRPPa TRP information exchange).

[0203] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to have more features than those explicitly mentioned in each clause. Rather, the various aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the following clauses should be regarded accordingly as incorporated into the description, where each clause may serve as a separate example. Although each dependent clause may refer in the clause to a specific combination with one of the other clauses, the aspect of that dependent clause is not limited to that specific combination. It should be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clause, or combinations of any feature with other dependent and independent clauses. The various aspects disclosed herein explicitly include these combinations unless explicitly stated or readily inferred that a particular combination is not intended for use (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

[0204] Specific implementation examples are described in the following numbered clauses:

[0205] Clause 1. A method of operating a communication device, the method comprising: obtaining a set of attributes associated with a sensing radio frequency (RF-S) calibration target; obtaining measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target; and determining an RF-S calibration compensation set based on the measurement information and the set of attributes.

[0206] Clause 2. The method according to Clause 1, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

[0207] Clause 3. The method according to any one of Clauses 1 to 2, wherein the first set of wireless sensing nodes includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0208] Clause 4. The method according to any one of Clauses 1 to 3, the method further comprising: sending the RF-S calibration compensation set to a second set of wireless sensing nodes.

[0209] Clause 5. The method according to Clause 4, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes at least partially overlap.

[0210] Clause 6. The method according to any one of Clauses 4 to 5, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes do not overlap.

[0211] Clause 7. The method according to any one of Clauses 1 to 6, wherein the set of attributes includes: the location of the RF-S calibration target, or the shape of the RF-S calibration target, or the size of the RF-S calibration target, or the material composition of the outer surface of the RF-S calibration target, or the orientation of the RF-S calibration target, or the mobility state of the RF-S calibration target, or the velocity of the RF-S calibration target, or the trajectory of the RF-S calibration target, or timing error information associated with the transmitter of the RF-S calibration process, or any combination thereof.

[0212] Clause 8. The method according to any one of Clauses 1 to 7, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the first set of wireless sensing nodes.

[0213] Clause 9. The method according to any one of Clauses 1 to 8, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

[0214] Clause 10. The method according to any one of Clauses 1 to 9, wherein the set of attributes is received via auxiliary data, or wherein the set of attributes is received via auxiliary information signaling, or wherein the set of attributes is received via broadcast, or any combination thereof.

[0215] Clause 11. The method according to any one of Clauses 1 to 10, the method further comprising: sending an RF-S calibration target attribute request, wherein the set of attributes is received in response to the RF-S calibration target attribute request.

[0216] Clause 12. The method according to any one of Clauses 1 to 11, wherein the set of attributes is obtained in association with the capability exchange of the RF-S calibration target’s registration process with the communication device.

[0217] Clause 13. The method according to any one of Clauses 1 to 12, wherein the RF-S calibration process is single-station and the first set of wireless sensing nodes comprises a single wireless sensing node, or wherein the RF-S calibration process is dual-station and the first set of wireless sensing nodes comprises multiple wireless sensing nodes.

[0218] Clause 14. A method of operating a communication device, the method comprising: obtaining a sensing radio frequency (RF-S) calibration compensation set, wherein the RF-S calibration compensation set is based on a set of attributes associated with an RF-S calibration target and first measurement information associated with an RF-S calibration process between a set of wireless sensing nodes and the RF-S calibration target; obtaining second measurement information associated with an RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; and determining the location of the target object based on the second measurement information and the RF-S calibration compensation set.

[0219] Clause 15. The method according to Clause 14, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

[0220] Clause 16. The method according to any one of Clauses 14 to 15, wherein the wireless sensing node set includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0221] Clause 17. The method according to any one of Clauses 14 to 16, wherein the at least one wireless sensing node comprises one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0222] Clause 18. The method according to any one of Clauses 14 to 17, wherein the set of attributes includes: the location of the RF-S calibration target, or the shape of the RF-S calibration target, or the size of the RF-S calibration target, or the material composition of the outer surface of the RF-S calibration target, or the orientation of the RF-S calibration target, or the mobility state of the RF-S calibration target, or the velocity of the RF-S calibration target, or the trajectory of the RF-S calibration target, or timing error information associated with the transmitter of the RF-S calibration process, or any combination thereof.

[0223] Clause 19. The method according to any one of Clauses 14 to 18, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the set of wireless sensing nodes.

[0224] Clause 20. The method according to any one of Clauses 14 to 19, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

[0225] Clause 21. The method according to any one of Clauses 14 to 20, wherein the RF-S calibration process is single-station and the wireless sensing node set comprises a single wireless sensing node, or wherein the RF-S calibration process is dual-station and the wireless sensing node set comprises multiple wireless sensing nodes.

[0226] Clause 22. The method according to any one of Clauses 14 to 21, wherein the RF-S process is single-station and the at least one wireless sensing node comprises a single wireless sensing node, or wherein the RF-S process is dual-station and the at least one wireless sensing node comprises multiple wireless sensing nodes.

[0227] Clause 23. A communication device comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: obtain a set of attributes associated with a radio frequency (RF-S) calibration target for sensing; obtain measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target; and determine an RF-S calibration compensation set based on the measurement information and the set of attributes.

[0228] Clause 24. The communication device as described in Clause 23, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

[0229] Clause 25. The communication device according to any one of Clauses 23 to 24, wherein the first set of wireless sensing nodes includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0230] Clause 26. The communication device according to any one of Clauses 23 to 25, wherein the one or more processors are further configured individually or in combination to transmit the RF-S calibration compensation set to a second set of wireless sensing nodes via the one or more transceivers.

[0231] Clause 27. The communication device according to Clause 26, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes at least partially overlap.

[0232] Clause 28. The communication device according to any one of Clauses 26 to 27, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes do not overlap.

[0233] Clause 29. A communication device according to any one of Clauses 23 to 28, wherein the set of attributes includes: the location of the RF-S calibration target, or the shape of the RF-S calibration target, or the size of the RF-S calibration target, or the material composition of the outer surface of the RF-S calibration target, or the orientation of the RF-S calibration target, or the mobility state of the RF-S calibration target, or the speed of the RF-S calibration target, or the trajectory of the RF-S calibration target, or timing error information associated with the transmitter of the RF-S calibration process, or any combination thereof.

[0234] Clause 30. The communication device according to any one of Clauses 23 to 29, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the first set of wireless sensing nodes.

[0235] Clause 31. A communication device according to any one of Clauses 23 to 30, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

[0236] Clause 32. A communication device pursuant to any one of Clauses 23 to 31, wherein the set of attributes is received via auxiliary data, or wherein the set of attributes is received via auxiliary information signaling, or wherein the set of attributes is received via broadcast, or any combination thereof.

[0237] Clause 33. The communication device according to any one of Clauses 23 to 32, wherein the one or more processors are further configured individually or in combination to: transmit an RF-S calibration target attribute request via the one or more transceivers, wherein the set of attributes is received in response to the RF-S calibration target attribute request.

[0238] Clause 34. A communication device pursuant to any one of Clauses 23 to 33, wherein the set of attributes is obtained in connection with the capability exchange of the RF-S calibration target’s registration process with the communication device.

[0239] Clause 35. The communication device according to any one of Clauses 23 to 34, wherein the RF-S calibration process is single-station and the first set of wireless sensing nodes comprises a single wireless sensing node, or wherein the RF-S calibration process is dual-station and the first set of wireless sensing nodes comprises multiple wireless sensing nodes.

[0240] Clause 36. A communication device comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: obtain a sensing radio frequency (RF-S) calibration compensation set, wherein the RF-S calibration compensation set is based on a set of attributes associated with an RF-S calibration target and first measurement information associated with an RF-S calibration process between a set of wireless sensing nodes and the RF-S calibration target; obtain second measurement information associated with an RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; and determine the location of the target object based on the second measurement information and the RF-S calibration compensation set.

[0241] Clause 37. The communication device as described in Clause 36, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

[0242] Clause 38. A communication device according to any one of Clauses 36 to 37, wherein the set of wireless sensing nodes includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0243] Clause 39. The communication device according to any one of Clauses 36 to 38, wherein the at least one wireless sensing node comprises one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0244] Clause 40. A communication device according to any one of Clauses 36 to 39, wherein the set of attributes includes: the location of the RF-S calibration target, or the shape of the RF-S calibration target, or the size of the RF-S calibration target, or the material composition of the outer surface of the RF-S calibration target, or the orientation of the RF-S calibration target, or the mobility state of the RF-S calibration target, or the speed of the RF-S calibration target, or the trajectory of the RF-S calibration target, or timing error information associated with the transmitter of the RF-S calibration process, or any combination thereof.

[0245] Clause 41. The communication device according to any one of Clauses 36 to 40, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the set of wireless sensing nodes.

[0246] Clause 42. A communication device according to any one of Clauses 36 to 41, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

[0247] Clause 43. The communication device according to any one of Clauses 36 to 42, wherein the RF-S calibration process is single-station and the wireless sensing node set comprises a single wireless sensing node, or wherein the RF-S calibration process is dual-station and the wireless sensing node set comprises multiple wireless sensing nodes.

[0248] Clause 44. A communication device according to any one of Clauses 36 to 43, wherein the RF-S process is single-station and the at least one wireless sensing node comprises a single wireless sensing node, or wherein the RF-S process is dual-station and the at least one wireless sensing node comprises multiple wireless sensing nodes.

[0249] Clause 45. A communication device comprising: components for obtaining a set of attributes associated with a sensing radio frequency (RF-S) calibration target; components for obtaining measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target; and components for determining an RF-S calibration compensation set based on the measurement information and the set of attributes.

[0250] Clause 46. The communication device as described in Clause 45, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

[0251] Clause 47. The communication device according to any one of Clauses 45 to 46, wherein the first set of wireless sensing nodes includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0252] Clause 48. The communication device according to any one of Clauses 45 to 47, the communication device further comprising: a component for transmitting the RF-S calibration compensation set to a second set of wireless sensing nodes.

[0253] Clause 49. The communication device according to Clause 48, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes at least partially overlap.

[0254] Clause 50. The communication device according to any one of Clauses 48 to 49, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes do not overlap.

[0255] Clause 51. A communication device according to any one of Clauses 45 to 50, wherein the set of attributes includes: the location of the RF-S calibration target, or the shape of the RF-S calibration target, or the size of the RF-S calibration target, or the material composition of the outer surface of the RF-S calibration target, or the orientation of the RF-S calibration target, or the mobility state of the RF-S calibration target, or the speed of the RF-S calibration target, or the trajectory of the RF-S calibration target, or timing error information associated with the transmitter of the RF-S calibration process, or any combination thereof.

[0256] Clause 52. The communication device according to any one of Clauses 45 to 51, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the first set of wireless sensing nodes.

[0257] Clause 53. A communication device according to any one of Clauses 45 to 52, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

[0258] Clause 54. A communication device pursuant to any one of Clauses 45 to 53, wherein the set of attributes is received via auxiliary data, or the set of attributes is received via auxiliary information signaling, or the set of attributes is received via broadcast, or any combination thereof.

[0259] Clause 55. The communication device according to any one of Clauses 45 to 54, the communication device further comprising: a component for transmitting an RF-S calibration target attribute request, wherein the attribute set is received in response to the RF-S calibration target attribute request.

[0260] Clause 56. A communication device pursuant to any one of Clauses 45 to 55, wherein the set of attributes is obtained in connection with the capability exchange of the RF-S calibration target’s registration process with the communication device.

[0261] Clause 57. The communication device according to any one of Clauses 45 to 56, wherein the RF-S calibration process is single-station and the first set of wireless sensing nodes comprises a single wireless sensing node, or wherein the RF-S calibration process is dual-station and the first set of wireless sensing nodes comprises multiple wireless sensing nodes.

[0262] Clause 58. A communication device comprising: means for obtaining a sensing radio frequency (RF-S) calibration compensation set, wherein the RF-S calibration compensation set is based on a set of attributes associated with an RF-S calibration target and first measurement information associated with an RF-S calibration process between a set of wireless sensing nodes and the RF-S calibration target; means for obtaining second measurement information associated with an RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; and means for determining the location of the target object based on the second measurement information and the RF-S calibration compensation set.

[0263] Clause 59. The communication device as described in Clause 58, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

[0264] Clause 60. The communication device according to any one of Clauses 58 to 59, wherein the set of wireless sensing nodes includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0265] Clause 61. The communication device according to any one of Clauses 58 to 60, wherein the at least one wireless sensing node comprises one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0266] Clause 62. A communication device according to any one of Clauses 58 to 61, wherein the set of attributes includes: the location of the RF-S calibration target, or the shape of the RF-S calibration target, or the size of the RF-S calibration target, or the material composition of the outer surface of the RF-S calibration target, or the orientation of the RF-S calibration target, or the mobility state of the RF-S calibration target, or the speed of the RF-S calibration target, or the trajectory of the RF-S calibration target, or timing error information associated with the transmitter of the RF-S calibration process, or any combination thereof.

[0267] Clause 63. The communication device according to any one of Clauses 58 to 62, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the set of wireless sensing nodes.

[0268] Clause 64. A communication device according to any one of Clauses 58 to 63, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

[0269] Clause 65. A communication device according to any one of Clauses 58 to 64, wherein the RF-S calibration process is single-station and the wireless sensing node set comprises a single wireless sensing node, or wherein the RF-S calibration process is dual-station and the wireless sensing node set comprises multiple wireless sensing nodes.

[0270] Clause 66. A communication device according to any one of Clauses 58 to 65, wherein the RF-S process is single-station and the at least one wireless sensing node comprises a single wireless sensing node, or wherein the RF-S process is dual-station and the at least one wireless sensing node comprises multiple wireless sensing nodes.

[0271] Clause 67. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a communication device, cause the communication device to: obtain a set of attributes associated with a sensing radio frequency (RF-S) calibration target; obtain measurement information associated with an RF-S calibration process between a first set of wireless sensing nodes and the RF-S calibration target; and determine an RF-S calibration compensation set based on the measurement information and the set of attributes.

[0272] Clause 68. The non-transitory computer-readable medium pursuant to Clause 67, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

[0273] Clause 69. A non-transitory computer-readable medium according to any one of Clauses 67 to 68, wherein the first set of wireless sensing nodes includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0274] Clause 70. A non-transitory computer-readable medium according to any one of Clauses 67 to 69, the non-transitory computer-readable medium further comprising computer-executable instructions that, when executed by the communication device, cause the communication device to: transmit the RF-S calibration compensation set to a second set of wireless sensing nodes.

[0275] Clause 71. The non-transitory computer-readable medium as described in Clause 70, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes at least partially overlap.

[0276] Clause 72. A non-transitory computer-readable medium according to any one of Clauses 70 to 71, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes do not overlap.

[0277] Clause 73. A non-transitory computer-readable medium according to any one of Clauses 67 to 72, wherein the set of attributes includes: the location of the RF-S calibration target, or the shape of the RF-S calibration target, or the size of the RF-S calibration target, or the material composition of the outer surface of the RF-S calibration target, or the orientation of the RF-S calibration target, or the mobility state of the RF-S calibration target, or the velocity of the RF-S calibration target, or the trajectory of the RF-S calibration target, or timing error information associated with the transmitter of the RF-S calibration process, or any combination thereof.

[0278] Clause 74. A non-transitory computer-readable medium according to any one of Clauses 67 to 73, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the first set of wireless sensing nodes.

[0279] Clause 75. A non-transitory computer-readable medium according to any one of Clauses 67 to 74, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is permitted for use in RF-S calibration compensation determination.

[0280] Clause 76. A non-transitory computer-readable medium pursuant to any one of Clauses 67 to 75, wherein the set of attributes is received via auxiliary data, or wherein the set of attributes is received via auxiliary information signaling, or wherein the set of attributes is received via broadcast, or any combination thereof.

[0281] Clause 77. The non-transitory computer-readable medium according to any one of Clauses 67 to 76, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the communication device, cause the communication device to: send an RF-S calibration target attribute request, wherein the set of attributes is received in response to the RF-S calibration target attribute request.

[0282] Clause 78. A non-transitory computer-readable medium pursuant to any one of Clauses 67 to 77, wherein the set of attributes is obtained in connection with the capability exchange of the RF-S calibration target’s registration process with the communication device.

[0283] Clause 79. A non-transitory computer-readable medium according to any one of Clauses 67 to 78, wherein the RF-S calibration process is single-station and the first set of wireless sensing nodes comprises a single wireless sensing node, or wherein the RF-S calibration process is dual-station and the first set of wireless sensing nodes comprises multiple wireless sensing nodes.

[0284] Clause 80. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a communication device, cause the communication device to: obtain a sensing radio frequency (RF-S) calibration compensation set, wherein the RF-S calibration compensation set is based on a set of attributes associated with an RF-S calibration target and first measurement information associated with an RF-S calibration process between a set of wireless sensing nodes and the RF-S calibration target; obtain second measurement information associated with an RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; and determine the location of the target object based on the second measurement information and the RF-S calibration compensation set.

[0285] Clause 81. The non-transitory computer-readable medium as described in Clause 80, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

[0286] Clause 82. A non-transitory computer-readable medium according to any one of Clauses 80 to 81, wherein the wireless sensing node set includes one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0287] Clause 83. A non-transitory computer-readable medium according to any one of Clauses 80 to 82, wherein the at least one wireless sensing node comprises one or more user equipment (UE), one or more wireless network components, or a combination thereof.

[0288] Clause 84. A non-transitory computer-readable medium according to any one of Clauses 80 to 83, wherein the set of attributes includes: the location of the RF-S calibration target, or the shape of the RF-S calibration target, or the size of the RF-S calibration target, or the material composition of the outer surface of the RF-S calibration target, or the orientation of the RF-S calibration target, or the mobility state of the RF-S calibration target, or the velocity of the RF-S calibration target, or the trajectory of the RF-S calibration target, or timing error information associated with the transmitter of the RF-S calibration process, or any combination thereof.

[0289] Clause 85. A non-transitory computer-readable medium according to any one of Clauses 80 to 84, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the set of wireless sensing nodes.

[0290] Clause 86. A non-transitory computer-readable medium according to any one of Clauses 80 to 85, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is permitted for RF-S calibration compensation determination.

[0291] Clause 87. A non-transitory computer-readable medium according to any one of Clauses 80 to 86, wherein the RF-S calibration process is single-station and the wireless sensing node set comprises a single wireless sensing node, or wherein the RF-S calibration process is dual-station and the wireless sensing node set comprises multiple wireless sensing nodes.

[0292] Clause 88. A nontransitory computer-readable medium according to any one of Clauses 80 to 87, wherein the RF-S process is single-station and the at least one wireless sensing node comprises a single wireless sensing node, or wherein the RF-S process is dual-station and the at least one wireless sensing node comprises a plurality of wireless sensing nodes.

[0293] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

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

[0295] The various exemplary logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0296] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Example storage media are coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside as discrete components in the user terminal.

[0297] In one or more examples, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, which includes any medium that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of a medium. As used herein, disks and optical discs include: compact optical discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0298] While the foregoing disclosure illustrates exemplary aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. For example, the functions, steps, and / or actions of the method claims according to aspects of this disclosure described herein need not be performed in any particular order. Furthermore, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly stated otherwise. Additionally, as used herein, the terms “set,” “group,” etc., are intended to include one or more of the stated elements. Furthermore, as used herein, the terms “having,” “comprising,” “including,” etc., do not exclude the presence of one or more additional elements (e.g., element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise expressly stated (e.g., if used in conjunction with “any” or “only one”), or these alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Additionally, although components, functions, actions, and instructions may be described or claimed in the singular, plural forms may also be considered unless expressly stated as limited to the singular. Therefore, as used herein, the articles “a,” “an,” “the,” and “the” are intended to include one or more of the described elements. Furthermore, as used herein, the terms “at least one” and “one or more” include “one” component, function, action, or instruction that performs or is capable of performing the described or claimed functionality, and also include “two or more” components, functions, actions, or instructions that perform or are capable of performing the described or claimed functionality in combination.

Claims

1. A method for operating a communication device, the method comprising: Obtain the set of attributes associated with the radio frequency (RF-S) calibration target for sensing; Obtain measurement information associated with the RF-S calibration process between the first set of wireless sensing nodes and the RF-S calibration target; as well as The RF-S calibration compensation set is determined based on the measurement information and the attribute set.

2. The method of claim 1, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

3. The method of claim 1, wherein the first set of wireless sensing nodes comprises one or more user equipment (UE), one or more wireless network components, or a combination thereof.

4. The method according to claim 1, further comprising: The RF-S calibration compensation set is sent to the second set of wireless sensing nodes.

5. The method of claim 4, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes at least partially overlap.

6. The method of claim 4, wherein the first set of wireless sensing nodes and the second set of wireless sensing nodes do not overlap.

7. The method according to claim 1, wherein the attribute set comprises: The location of the RF-S calibration target, or The shape of the RF-S calibration target, or The size of the RF-S calibration target, or The material composition of the outer surface of the RF-S calibration target, or The orientation of the RF-S calibration target, or The mobility status of the RF-S calibration target, or The speed of the RF-S calibration target, or The trajectory of the RF-S calibration target, or Timing error information associated with the transmitter in the RF-S calibration process, or Any combination of them.

8. The method of claim 1, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the first set of wireless sensing nodes.

9. The method of claim 1, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

10. The method according to claim 1, The set of attributes mentioned above is received via auxiliary data, or The set of attributes mentioned above is received via auxiliary information signaling, or The set of attributes mentioned above is received via broadcast, or Any combination of them.

11. The method according to claim 1, further comprising: Send RF-S calibration target property request, The set of attributes is received in response to the RF-S calibration target attribute request.

12. The method of claim 1, wherein the set of attributes is obtained in association with the capability exchange of the RF-S calibration target’s registration process with the communication device.

13. The method according to claim 1, The RF-S calibration process is single-station, and the first set of wireless sensing nodes includes a single wireless sensing node, or The RF-S calibration process is bistationary, and the first set of wireless sensing nodes includes multiple wireless sensing nodes.

14. A method of operating a communication device, the method comprising: A sensing radio frequency (RF-S) calibration compensation set is obtained, wherein the RF-S calibration compensation set is based on a set of attributes associated with the RF-S calibration target and first measurement information associated with the RF-S calibration process between the set of wireless sensing nodes and the RF-S calibration target; Obtain second measurement information associated with the RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; as well as The location of the target object is determined based on the second measurement information and the RF-S calibration compensation set.

15. The method of claim 14, wherein the communication device corresponds to a network component or a first wireless sensing node from a set of wireless sensing nodes or a second wireless sensing node not belonging to the set of wireless sensing nodes.

16. The method of claim 14, wherein the wireless sensing node set comprises one or more user equipment (UE), one or more wireless network components, or a combination thereof.

17. The method of claim 14, wherein the at least one wireless sensing node comprises one or more user equipment (UE), one or more wireless network components, or a combination thereof.

18. The method of claim 14, wherein the set of attributes comprises: The location of the RF-S calibration target, or The shape of the RF-S calibration target, or The size of the RF-S calibration target, or The material composition of the outer surface of the RF-S calibration target, or The orientation of the RF-S calibration target, or The mobility status of the RF-S calibration target, or The speed of the RF-S calibration target, or The trajectory of the RF-S calibration target, or Timing error information associated with the transmitter in the RF-S calibration process, or Any combination of them.

19. The method of claim 14, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the set of wireless sensing nodes.

20. The method of claim 14, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

21. The method according to claim 14, The RF-S calibration process is single-station, and the wireless sensing node set includes a single wireless sensing node, or The RF-S calibration process is bi-station, and the wireless sensing node set includes multiple wireless sensing nodes.

22. The method according to claim 14, The RF-S process is single-station, and the at least one wireless sensing node comprises a single wireless sensing node, or The RF-S process is dual-station, and the at least one wireless sensing node includes multiple wireless sensing nodes.

23. A communication device, the communication device comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: Obtain the set of attributes associated with the radio frequency (RF-S) calibration target for sensing; Obtain measurement information associated with the RF-S calibration process between the first set of wireless sensing nodes and the RF-S calibration target; as well as The RF-S calibration compensation set is determined based on the measurement information and the attribute set.

24. The communication device according to claim 23, wherein the set of attributes includes: The location of the RF-S calibration target, or The shape of the RF-S calibration target, or The size of the RF-S calibration target, or The material composition of the outer surface of the RF-S calibration target, or The orientation of the RF-S calibration target, or The mobility status of the RF-S calibration target, or The speed of the RF-S calibration target, or The trajectory of the RF-S calibration target, or Timing error information associated with the transmitter in the RF-S calibration process, or Any combination of them.

25. The communication device of claim 23, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the first set of wireless sensing nodes.

26. The communication device of claim 23, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

27. A communication device, the communication device comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: A sensing radio frequency (RF-S) calibration compensation set is obtained, wherein the RF-S calibration compensation set is based on a set of attributes associated with the RF-S calibration target and first measurement information associated with the RF-S calibration process between the set of wireless sensing nodes and the RF-S calibration target; Obtain second measurement information associated with the RF-S process between at least one wireless sensing node and a target object different from the RF-S calibration target; as well as The location of the target object is determined based on the second measurement information and the RF-S calibration compensation set.

28. The communication device according to claim 27, wherein the set of attributes includes: The location of the RF-S calibration target, or The shape of the RF-S calibration target, or The size of the RF-S calibration target, or The material composition of the outer surface of the RF-S calibration target, or The orientation of the RF-S calibration target, or The mobility status of the RF-S calibration target, or The speed of the RF-S calibration target, or The trajectory of the RF-S calibration target, or Timing error information associated with the transmitter in the RF-S calibration process, or Any combination of them.

29. The communication device of claim 27, wherein the RF-S calibration compensation set is further based on at least one location of at least one wireless sensing node from the set of wireless sensing nodes.

30. The communication device of claim 27, wherein at least one attribute from the set of attributes is associated with a validity period specifying when the at least one attribute is allowed to be used for RF-S calibration compensation determination.

Images