Sensing in wireless systems with hybrid radio access technology infrastructure

Abstract

In an aspect, a second radio access technology (RAT) radio access network (RAN) node can receive, from a first RAT sensing management function (SnMF), a RAN node sensing capability request. The RAT RAN node can provide, to the first RAT SnMF, a response to the RAN node sensing capability request, where the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities limited to sensing capabilities that are compatible with the first RAT SnMF.

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 wireless communication performed by a second radio access technology (RAT) radio access network (RAN) node includes: receiving a RAN node sensing capability request from a first RAT sensing management function (SnMF); and providing a response to the first RAT SnMF to the RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

[0008] In one aspect, a method of wireless communication performed by a second radio access technology (RAT) user equipment (UE) includes: receiving a UE sensing capability request from a first RAT sensing management function (SnMF); activating a first RAT user equipment (UE) sensing agent at the second RAT UE in response to receiving the UE sensing capability request; providing a response to the UE sensing capability request to the first RAT SnMF based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF; receiving a UE sensing tunnel configuration indicating a sensing purpose and a virtual first RAT UE identifier; and responding to the UE sensing tunnel configuration using the first RAT UE sensing agent.

[0009] In one aspect, a method of wireless communication performed by a second radio access technology (RAT) sensing management function (SnMF) includes: transmitting a RAN node sensing capability request to a first RAT radio access (RAN) node, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; receiving a RAN node sensing capability response based on the subset of second RAT sensing capabilities from the first RAT RAN node; transmitting a RAN node sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node; and receiving a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier from the first RAT RAN node.

[0010] In one aspect, a method of wireless communication performed by a first Radio Access Technology (RAT) User Equipment (UE) includes: receiving a UE sensing capability request from a second RAT Sensing Management Function (SnMF), wherein the UE sensing capability request is limited to a subset of second RAT UE sensing capabilities compatible with the first RAT UE; providing the second RAT SnMF with a first response to the first RAT UE sensing capability request, wherein the first response is based on the subset of second RAT UE sensing capabilities indicated by the UE sensing capability request; receiving a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF; and providing a second response to the second RAT SnMF based on the UE sensing tunnel configuration.

[0011] In one aspect, a second radio access technology (RAT) radio access network (RAN) node 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: receive a RAN node sensing capability request from a first RAT sensing management function (SnMF) via the one or more transceivers; and provide a response to the first RAT SnMF to the RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

[0012] In one aspect, a second radio access technology (RAT) user equipment (UE) 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: receive a UE sensing capability request from a first RAT sensing management function (SnMF) via the one or more transceivers; activate a first RAT user equipment (UE) sensing agent at the second RAT UE in response to receiving the UE sensing capability request; provide a response to the first RAT SnMF to the first RAT SnMF based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF; receive a UE sensing tunnel configuration indicating a sensing purpose and a virtual first RAT UE identifier via the one or more transceivers; and respond to the UE sensing tunnel configuration using the first RAT UE sensing agent.

[0013] In one aspect, a second radio access technology (RAT) sensing management function (SnMF) 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: transmit a RAN node sensing capability request to a first RAT radio access (RAN) node via the one or more transceivers, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; receive a RAN node sensing capability response based on the subset of second RAT sensing capabilities from the first RAT RAN node via the one or more transceivers; transmit a RAN node sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node via the one or more transceivers; and receive a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier from the first RAT RAN node via the one or more transceivers.

[0014] In one aspect, a first radio access technology (RAT) user equipment (UE) 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: receive a UE sensing capability request from a second RAT sensing management function (SnMF) via the one or more transceivers, wherein the UE sensing capability request is limited to a subset of second RAT UE sensing capabilities compatible with the first RAT UE; provide a first response to the second RAT SnMF to the first RAT UE sensing capability request, wherein the first response is based on the subset of second RAT UE sensing capabilities indicated by the UE sensing capability request; receive a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF via the one or more transceivers; and provide a second response to the second RAT SnMF based on the UE sensing tunnel configuration.

[0015] In one aspect, a second radio access technology (RAT) radio access network (RAN) node includes: components for receiving a RAN node sensing capability request from a first RAT sensing management function (SnMF); and components for providing a response to the first RAT SnMF to the RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

[0016] In one aspect, a second radio access technology (RAT) user equipment (UE) includes: components for receiving a UE sensing capability request from a first RAT sensing management function (SnMF); components for activating a first RAT user equipment (UE) sensing agent at the second RAT UE in response to receiving the UE sensing capability request; components for providing a response to the UE sensing capability request to the first RAT SnMF based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF; components for receiving a UE sensing tunnel configuration indicating a sensing purpose and a virtual first RAT UE identifier; and components for responding to the UE sensing tunnel configuration using the first RAT UE sensing agent.

[0017] In one aspect, a second radio access technology (RAT) sensing management function (SnMF) includes: components for transmitting a RAN node sensing capability request to a first RAT radio access (RAN) node, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; components for receiving a RAN node sensing capability response based on the subset of second RAT sensing capabilities from the first RAT RAN node; components for transmitting a RAN node sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node; and components for receiving a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier from the first RAT RAN node.

[0018] In one aspect, a first radio access technology (RAT) user equipment (UE) includes: components for receiving a UE sensing capability request from a second RAT sensing management function (SnMF), wherein the UE sensing capability request is limited to a subset of second RAT UE sensing capabilities compatible with the first RAT UE; components for providing a first response to the first RAT UE sensing capability request to the second RAT SnMF, wherein the first response is based on the subset of second RAT UE sensing capabilities indicated by the UE sensing capability request; components for receiving a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF; and components for providing a second response to the second RAT SnMF based on the UE sensing tunnel configuration.

[0019] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a second radio access technology (RAT) radio access network (RAN) node, cause the second RAT RAN node to: receive a RAN node sensing capability request from a first RAT sensing management function (SnMF); and provide a response to the first RAT SnMF to the RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

[0020] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a second radio access technology (RAT) user equipment (UE), cause the second RAT UE to: receive a UE sensing capability request from a first RAT sensing management function (SnMF); activate a first RAT user equipment (UE) sensing agent at the second RAT UE in response to receiving the UE sensing capability request; provide a response to the UE sensing capability request to the first RAT SnMF based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF; receive a UE sensing tunnel configuration indicating a sensing purpose and a virtual first RAT UE identifier; and respond to the UE sensing tunnel configuration using the first RAT UE sensing agent.

[0021] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a second Radio Access Technology (RAT) Sensing Management Function (SnMF), cause the second RAT SnMF to: transmit a RAN node sensing capability request to a first RAT Radio Access (RAN) node, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; receive a RAN node sensing capability response based on the subset of second RAT sensing capabilities from the first RAT RAN node; transmit a RAN node sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node; and receive a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier from the first RAT RAN node.

[0022] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a first radio access technology (RAT) user equipment (UE), cause the first RAT UE to: receive a UE sensing capability request from a second RAT sensing management function (SnMF), wherein the UE sensing capability request is limited to a subset of the second RAT UE sensing capabilities compatible with the first RAT UE; provide the second RAT SnMF with a first response to the first RAT UE sensing capability request, wherein the first response is based on the subset of the second RAT UE sensing capabilities indicated by the UE sensing capability request; receive a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF; and provide a second response to the second RAT SnMF based on the UE sensing tunnel configuration.

[0023] 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

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

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

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

[0027] Figure 2B Another example wireless network architecture is shown.

[0028] Figure 2C An example decomposed base station architecture according to various aspects of this disclosure is illustrated.

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

[0030] Figure 3B Possible locations for sensing components are illustrated. These sensing components may be, for example, part of one or more WWAN transceivers, memory, one or more processors, or any combination thereof, or may be independent components.

[0031] Figure 3CPossible locations for sensing components are illustrated. These sensing components may be, for example, part of one or more network transceivers, memory, one or more processors, or any combination thereof, or may be independent components.

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

[0033] It should be noted that, although Figure 4B The example illustrates the use of a downlink RF signal as an RF sensing signal, but uplink or sidelink RF signals can also be used as RF sensing signals.

[0034] Figures 5A to 5F Various example single-site and dual-site sensing use cases according to aspects of this disclosure are illustrated.

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

[0036] Figure 7 This is a table showing some differences between the sensing parameters available in 6G and 5G systems according to various aspects of this disclosure.

[0037] Figure 8 An example deployment is shown in which a 6G radio access network (RAN) node is used as a sensor by a 5G sensing management function (SnMF) according to various aspects of this disclosure.

[0038] Figures 9A to 9D An example deployment scenario is shown in which one of the 6G RAN nodes can be used as a sensor for 5G SnMF according to various aspects of this disclosure.

[0039] Figure 10 An example message flow between 5G SnMF, 5G / 6G core network (CN), and 6G RAN nodes is shown according to various aspects of this disclosure.

[0040] Figure 11 Another example message flow between 5G SnMF, 5G / 6G CN and 6G RAN nodes is shown according to various aspects of this disclosure.

[0041] Figure 12 An example message flow between 5G SnMF, 5G / 6G CN, 5G RAN node and 6G RAN node is shown in accordance with various aspects of this disclosure when 6G RAN node is not visible to 5G SnMF.

[0042] Figure 13A and Figure 13BAn example deployment scenario is illustrated where a 6G UE is deployed in a sensing environment with only 5G components, according to various aspects of this disclosure.

[0043] Figure 14 An example message flow between 5GSnMF, 5G CN, 5G RAN node and 6G UE is shown in a deployment scenario where the 6G UE is visible to the 5G SnMF, according to various aspects of this disclosure.

[0044] Figure 15 An example message flow between 5GSnMF, 5G CN, 5G RAN node and 6G UE is shown in a deployment scenario where the 6G UE is not visible to 5G SnMF, according to various aspects of this disclosure.

[0045] Figure 16 An example message flow between 5GSnMF, 5G CN, 5G RAN node, 5G UE and 6G UE is shown in a deployment scenario where the 6G UE is not visible to 5G SnMF, according to various aspects of this disclosure.

[0046] Figures 17A to 17D An example deployment scenario is shown in which a 5G RAN node can be used as a sensor for 6G SnMF according to various aspects of this disclosure.

[0047] Figure 18 An example message flow between 6G SnMF, 6GCN, 6G RAN node and 5G RAN node is shown in accordance with various aspects of this disclosure when 5G RAN node is not visible to 6G SnMF.

[0048] Figure 19A and Figure 19B An example deployment scenario is shown in which one of the 6G SnMFs is connected to a 5G UE as a sensor without an intermediate 5G RAN node, according to various aspects of this disclosure.

[0049] Figure 20 Example methods of wireless communication that can be performed by a second radio access technology (RAT) radio access network (RAN) node according to various aspects of this disclosure are illustrated.

[0050] Figure 21 An example method of wireless communication that can be performed by a second radio access technology (RAT) user equipment (UE) is shown.

[0051] Figure 22 An example method of wireless communication that can be performed by the second radio access technology (RAT) sensing management function (SnMF) is shown.

[0052] Figure 23An example method of wireless communication that can be performed by a first radio access technology (RAT) user equipment (UE) is shown. Detailed Implementation

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

[0054] The various aspects generally relate to sensing in wireless environments employing different radio access technologies (RATs) with varying sensing capabilities. Some aspects more specifically relate to sensing in hybrid 5G / 6G RAT environments, where a 6G RAT (e.g., a second RAT) has stronger sensing capabilities than a 5G RAT (e.g., a first RAT). Specific aspects of the subject matter described in this disclosure can be implemented to perform sensing operations in various hybrid RAT deployment scenarios.

[0055] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to allow RAT radio access network (RAT) nodes to be used with SnMF of another RAT type (e.g., a RAT with weaker sensing capabilities) in a hybrid RAT sensing environment by providing only a subset of capabilities to the sensing management function (SnMF). In some examples, using a proxy of a given RAT type in a user equipment (UE) to communicate based on the sensing capabilities of a RAT type with weaker sensing capabilities enables the UE to operate in a hybrid sensing environment of different RAT types with different sensing capabilities.

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

[0057] Those skilled in the art will understand that any of the various techniques and skills available 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0093] 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 regulated 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.

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

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

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

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

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

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

[0100] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of 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) that perform 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.

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

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

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

[0104] Each of the units (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 of the units, 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.

[0105] In some aspects, the CU 280 can host one or more higher-level control functions. Such control functions may include RRC, PDCP, Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by 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.

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

[0107] Lower-layer functionality can be implemented by one or more RU 287s. In some deployments, an RU287 controlled by a 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, at least in part based 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 enables the implementation of the DU 285 and CU 280 in cloud-based RAN architectures such as vRAN architectures.

[0108] 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 the 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.

[0109] 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 data collection and actions through an interface such as an E2 interface, connecting one or more CU 280s, one or more DU 285s, or both, and O-eNBs to the near-RT RIC 259.

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

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

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

[0113] In at least some cases, UE 302 and base station 304 each further include one or more short-range radio transceivers 320 and 360, respectively. Short-range radio 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, short-range wireless transceivers 320 and 360 each include: one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively; and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, short-range wireless transceivers 320 and 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.

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

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

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

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

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

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

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

[0121] 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 sensing components 348, 388, and 398. Sensing 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, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other respects, sensing components 348, 388, and 398 may be external to processors 342, 384, and 394 (e.g., as part of a modem processing system, integrated with another processing system, etc.). Alternatively, sensing 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 the modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Possible locations of sensing component 348 are illustrated. The sensing 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 of sensing component 388 are illustrated. The sensing 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 of sensing component 398 are illustrated. The sensing 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.

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

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

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

[0125] 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 the channel estimator can be used to determine the decoding and modulation schemes, as well as for spatial processing. The 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. The transmitter 354 can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0126] 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 streams 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 comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. Symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation point 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.

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

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

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

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

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

[0132] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3CThe document is shown as including 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 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.

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

[0134] 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, sensing components 348, 388 and 398, etc.).

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

[0136] 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 beneficial for use as sensing signals because higher frequencies provide at least more accurate ranging (distance) detection. Possible use cases for RF sensing include: health monitoring use cases, such as heart rate detection, respiratory rate monitoring, etc.; gesture recognition use cases, such as human activity recognition, keystroke detection, sign language recognition, etc.; context information acquisition use cases, such as location detection / tracking, direction finding, ranging estimation, etc.; and automotive sensing use cases, such as intelligent cruise control, collision avoidance, etc. 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 4A and Figure 4B These different types of sensing are illustrated. Specifically, Figure 4A This is illustration 400 illustrating a single-station sensing scenario, and Figure 4B This is illustration 430, illustrating a dual-station sensing scenario. Figure 4A In this configuration, the transmitter (Tx) and receiver (Rx) are co-located in the same sensing device 404 (e.g., a UE). The sensing device 404 transmits one or more RF sensing signals 434 (e.g., uplink or sidelink positioning reference signals (PRS) in the case of a UE), and some of the RF sensing signals 434 are reflected from a target object 406 (e.g., an unmanned aerial vehicle (UAV)). The sensing device 404 can measure various properties of the reflected RF sensing signals 434 (e.g., time of arrival (ToA), angle of arrival (AoA), phase shift, etc.) to determine characteristics of the target object 406 (e.g., size, shape, speed, motion state, etc.). Figure 4B 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 4BAn example is shown using a downlink RF signal as the RF sensing signal 432, but uplink or sidelink RF signals can also be used as the RF sensing signal 432. In the downlink scenario, as shown, the transmitter device 402 is a base station (e.g., a gNB) and the receiver device 408 is a UE (e.g., a mobile phone, a vehicle with V2X capability, a roadside unit (RSU), etc.), while in the uplink scenario, the transmitter device 402 is the UE and the receiver device 408 is the base station. When the transmitter device 402 is the base station and the receiver device 408 is the UE, the sensing is referred to as UE-assisted sensing. In UE-assisted sensing, the location of the receiver device 408 should be known to the network (e.g., via GPS or other UE location methods). See more details in the reference section. Figure 4B Transmitter device 402 sends RF sensing signals 432 and 434 (e.g., Position Reference Signal (PRS)) to receiver device 408, but some of the RF sensing signals 434 are reflected from target object 406. Receiver device 408 (also referred to as a "sensing device") can measure the time of arrival (ToA) of the RF sensing signal 432 received directly from transmitter device 402 and the time of reflection 436 of the RF sensing signal 434 reflected from target object 406. More specifically, as described above, transmitter device (e.g., base station) can send a single RF signal or multiple RF signals to receiver device (e.g., UE). However, due to the propagation characteristics of RF signals through multipath channels, receiver can receive multiple RF signals corresponding to each transmitted RF signal. Each path can 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 time of arrival (ToA) of the RF signal on the site line (LOS) path (i.e., the shortest path between the transmitter and receiver). The subsequent channel tap clustering is considered to have been reflected by the object between the transmitter and receiver, and therefore along a non-LOS (NLOS) path between the transmitter and receiver. Therefore, re-reference... Figure 4BRF sensing signal 432 follows the LOS path between transmitter device 402 and receiver device 408, while RF sensing signal 434 follows the NLOS path between transmitter device 402 and receiver device 408 due to reflection from target object 406. Transmitter device 402 may have transmitted multiple RF sensing signals 432, 434, some of which follow the LOS path and others follow the NLOS path. Alternatively, transmitter device 402 may have transmitted a single RF sensing signal in a sufficiently wide beam, a portion of which follows the LOS path (RF sensing signal 432) and a portion of which follows the NLOS path (RF sensing signal 434). Based on the ToA of the LOS path, the ToA of the NLOS path, and the speed of light, receiver device 408 can determine the distance to the target object. For example, receiver device 408 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 receiver device 408 is capable of receiving beamforming, it can determine the approximate direction to target object 406 as the direction (angle) of the received beam that receives the RF sensing signal following the NLOS path. That is, receiver device 408 can determine the direction to target object 406 as the AoA of the RF sensing signal, where AoA is the angle of the received beam used to receive the RF sensing signal. Receiver device 408 can then optionally report this information to transmitter device 402, the serving base station of the receiver device, an application server associated with the core network, an external client, a third-party application, or another sensing entity. Alternatively, receiver device 408 can report the ToA measurement to transmitter device 402 or other sensing entities (e.g., if receiver device 408 itself does not have the processing capability to perform these calculations), and transmitter device 402 can determine the distance to target object 406 and optionally the direction to that target object. It should be noted that if the RF sensing signal is an uplink RF signal transmitted 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. 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 object. However, performance (e.g., the resolution and maximum values ​​of range, velocity, and angle) can depend on the design of the reference signal.

[0137] Figures 5A to 5F Various example single-site and dual-site sensing use cases according to various aspects of this disclosure are illustrated. Figure 5A The document describes 500 single-station sensing use cases from gNB1 to gNB1. Figure 5BThe document describes a single-station sensing use case 510 for UE1. Figure 5C The document describes a dual-station sensing use case 520 from gNB1 to gNB2. Figure 5D The document describes a dual-site sensing use case 530 from gNB1 to UE1. Figure 5E The document describes a dual-station sensing use case 540 from UE1 to gNB1. Figure 5F The document describes a dual-station sensing use case 550 for UE1 to UE2.

[0138] Figure 6 An example call flow 600 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 6 The sensing process coordinated by the network is illustrated, but the sensing process can be coordinated through the sidelink channel.

[0139] At stage 605, sensing server 670 (e.g., inside or outside the core network) transmits a request for network (NW) information to gNB 622 (e.g., the serving gNB of UE 604). This request may be for a list of UE 604's serving cell and any neighboring cells. At stage 610, gNB 622 transmits the requested information to sensing server 670. At stage 615, sensing server 670 transmits a request for sensing capabilities to UE 604. At stage 620, UE 604 provides its sensing capabilities to sensing server 670.

[0140] At stage 625, the sensing server 670 transmits to the UE 604 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 stage 610. In some cases, Figure 6 The NR-based sensing process illustrated herein 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 both communication and 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.

[0141] At stage 630, the sensing server 670 transmits a request for sensing information to the UE 604. Then, the UE 604 measures the transmitted reference signal and, at stage 635, transmits the measurement or any sensing results determined based on the measurement to the sensing server 670.

[0142] On one hand, communication between UE 604 and sensing server 670 can be conducted via LTE positioning protocol (LPP). Communication between sensing server 670 and gNB can be conducted via NR positioning protocol type A (NRPPa).

[0143] Sensing operations in different Radio Access Technology (RAT) systems (e.g., a first 5G RAT system and a second 6G RAT system) may have several different available operating parameters. For example, 6G RAN nodes and 6G UEs may have stronger and / or more advanced sensing capabilities than 5G RAN nodes and 5G UEs. Additionally, the 6G sensing server (e.g., a sensing management function (SnMF)) should support these advanced sensing capabilities and have stronger processing capabilities than 5G SnMF.

[0144] Figure 7 Table 700 illustrates some differences between the sensing parameters available in 6G and 5G systems according to various aspects of this disclosure. As shown in Table 700, the sensing signal waveforms available in each system are different. Currently, 5G sensing is based on OFDM waveforms, and the multiplexing of multiple sensing signals or the multiplexing between sensing signals and communication signals can be TDM, FDM, or CDM. In 6G systems, new sensing signal waveforms can also be applied to provide better sensing performance or trade-offs between sensing and communication (e.g., Frequency Modulated Continuous Wave (FMCW), Orthogonal Time-Frequency Space (OTFS)). Therefore, multiplexing in 6G can also be cyclic shift multiplexing.

[0145] Another difference between 5G and 6G sensing systems lies in their available sensing bandwidth. As shown in the diagram, 5G can support a bandwidth of 100MHz with a single carrier, while 6G can scale up to 1GHz.

[0146] The types of sensing measurement reports available in each RAT also differ. 5G UEs only report radio-based measurements, while 6G UEs can also report video-based measurements.

[0147] Another difference shown in Table 700 is the support for artificial intelligence (AI) models. Such AI models are not supported in 5G systems, but they can be supported in 6G systems to enhance sensing.

[0148] When wireless communication networks migrate from 5G to 6G, the deployment of sensing-related operations by network nodes based on the 6G core network (CN) and 6G sensing management functions (SnMF) can go through several phases. According to various aspects of this disclosure, the deployment of sensing systems is considered in the following phases:

[0149] • Phase 1: Deploy 6G RAN, but do not deploy 6G core network (CN) and 6G SnMF.

[0150] • Phase 1a: Deploy 6G RAN and 6G SnMF, but not 6G CN.

[0151] • Phase 2: Deploy 6G RAN and 6G CN, but not 6G SnMF.

[0152] • Phase 3: Deploy 6G RAN, 6G CN and 6G SnMF.

[0153] According to various aspects of this disclosure, the 6G UE and 6G RAN are connected to the 5G CN and 5G SnMF in Phase 1 and Phase 1A deployments. In Phase 2 deployment, the 6G UE, 6G RAN, and 6G CN communicate with the 5G SnMF. In Phase 3 deployment, the 6G UE, 6G RAN, and 6G CN communicate with the 6G SnMF. Similarly, the 5G UE, 5G RAN, and 5G CN can also communicate with the 6G SnMF.

[0154] Furthermore, there are scenarios where a 6G UE connects to the 5G RAN. When the 6G RAN uses a larger frequency band than the 5G RAN, some areas may only be covered by the 5G RAN. In these areas, if a 6G UE performs a sensing task and reports the sensing results, it can only communicate with the 5G RAN.

[0155] According to various aspects of this disclosure, in certain deployments (e.g., Phase 1 and Phase 2 deployments), the 5G SnMF can communicate with 6G RAN nodes, in which case the 6G RAN nodes are used as sensors for the 5G SnMF. Figure 8An example deployment 800 is shown in which a 6G RAN node 802 is used as a sensor by a 5G SnMF 804, according to aspects of this disclosure. Here, the 6G RAN node 802 communicates with the 5G SnMF 804 via a 5G CN 806 or 6G CN 808. The 6G RAN node 802 may communicate with the 5G SnMF 804 using a 5G sensing agent 810. The 6G RAN node 802 may perform sensing operations on a target object 814, either alone or in conjunction with a 6G UE 812, and communicate the sensing measurements to the 5G SnMF 804. Certain aspects of this disclosure are specifically addressed to deployments in which the sensing operations involve a 6G UE 812.

[0156] According to various aspects of this disclosure, the 6G RAN node 802 may be visible to the 5G SnMF 804 (e.g., directly addressable by the 5G SnMF). In such cases, upon receiving a sensing capability request from the 5G SnMF 804, the 6G RAN node 802 only reports a subset of 6G sensing capabilities compatible with the 5G SnMF 804. After receiving a sensing tunnel configuration message (indicating the sensing purpose and the virtual 5G RAN node ID), the 6G RAN node 802 may activate the 5G sensing agent 810 and use the configured ID in the signaling and data packets used during sensing operations.

[0157] In cases where the 6G RAN node 802 is not visible to the 5G SnMF 804 (e.g., cannot be directly addressed by the 5G SnMF 804), the 5G RAN node ( Figure 8 (Not shown) can function as a “proxy” for the sensing capabilities / location and sensing reports of the 6G RAN node 802 for communication with the 5G SnMF 804. In this case, the 5G RAN node and the 6G RAN node can communicate using a standardized set of messages.

[0158] As noted, when the 6G SnMF is not deployed in an area covered by the 6G RAN node 802, the 6G RAN node 802 can interact with the 5G SnMF 804 (including signaling between the 5G SnMF 804 and the 5G sensing agent 810 in the 6G RAN node 802) to establish a control / data tunnel, report sensing capabilities, receive sensing configurations, and report sensing results. When establishing the sensing-oriented control / data tunnel and the 5G sensing agent 810, the 5G SnMF 804 requests the 6G CN 808 or 5G CN 806 to provide 6G RAN node information (e.g., location, sensing capabilities) of the 6G RAN nodes present in the deployment. The 6G CN 808 or 5G CN 806 provides this information from the 6G RAN node (e.g., 6G RAN node 802) to the 5G SnMF 804. In one aspect, the 5G SnMF 804 selects a 6G RAN node from the indicated information and then configures a sensing-oriented control / data tunnel with that 6G RAN node, with or without 6G CN or 5G CN assistance. When configuration is performed without the assistance of 6G CN 808 or 5G CN 806, the 5G SnMF 804 directly configures the 6G RAN node 802. In another aspect, where configuration occurs with the assistance of 6G CN 808 or 5G CN 806, the 5G SnMF 804 requests assistance from 6G CN 808 or 5G CN 806 by indicating the 6G RAN node identifier (e.g., the node identifier of 6G RAN node 802). Then, 6G CN 808 or 5G CN 806 configures the 6G RAN node 802. During sensing operations, a 6G RAN node transmits a sensing signal, which is then received by the 6G RAN node itself, another 6G RAN node, or a 6G UE. When using a 6G UE, the 6G UE transmits sensing measurement reports to the 6G RAN node.

[0159] When compared to deployments with 6G SnMF (e.g., Phase 1a and Phase 3 deployments), the 6G RAN node 802 may exhibit different behavior (e.g., reporting different sensing capabilities) for receiving sensing tunnel configuration signaling from a 5G SnMF (e.g., Phase 1 and Phase 2 deployments). Therefore, the SnMF indicates its generation number (or equivalent indicator) (e.g., 5G SnMF or 6G SnMF) in its sensing tunnel configuration request. If the 6G RAN node receives sensing tunnel configuration signaling from a 6G SnMF (in Phase 1a and Phase 3), the 6G RAN node may report all sensing capabilities it possesses that are compatible with the 6G SnMF (e.g., recognized by the 6G SnMF) (e.g., full 6G sensing capabilities, including low-band to high-band spectrum capabilities, low to ultra-wideband capabilities, OFDM / FMCW waveform capabilities, hybrid video and radio sensing capabilities, and / or AI-based sensing capabilities).

[0160] If a 6G RAN node receives sensing tunnel configuration signaling from a 5G SnMF (e.g., in Phase 1 and Phase 2 deployments), the 6G RAN can report a subset of 6G sensing capabilities compatible with the 5G SnMF (e.g., partial or subset of 6G sensing capabilities, including low-to-mid-band spectrum capabilities, low-to-high bandwidth capabilities, OFDM waveform capabilities, radio sensing availability, etc.). Upon receiving the configuration message, the 6G RAN node activates its 5G sensing agent. In one aspect, the 5G sensing agent provides the same interface as the 5G RAN node simply by connecting to the 5G SnMF.

[0161] The 5G SnMF or 5G CN can configure a sensing-target virtual 5G RAN node identifier (ID) to the 5G sensing agent in a sensing tunnel configuration message or other messages. In one aspect, the sensing-target virtual 5G RAN node ID is an ID used by the 5G SnMF to distinguish between multiple sensors and the sensing environment.

[0162] Figures 9A to 9D An example deployment scenario is shown in which one of the 6G RAN nodes can be used as a sensor for 5G SnMF according to various aspects of this disclosure. Figure 9A An example deployment scenario 900 is shown, comprising a 5G SnMF 902, a 5G core network 904, a 6G RAN node 906 with a 5G sensing agent 908, and an optional 6G UE 910. In deployment scenario 900, no 6G CN is deployed, and the 6G RAN node 906 is connected to the 5G CN 904 to communicate with the 5G SnMF 902 (as depicted by dashed line 915).

[0163] exist Figure 9BIn this deployment scenario 912, a 5G RAN node 914 is connected to a 6G RAN node 906. In deployment scenario 912, communication between the 5G SnMF 902 and the 6G RAN node 906 occurs via the 5G RAN node 914, as depicted by dashed line 916.

[0164] exist Figure 9C In deployment scenario 918, a 6G CN 920 is connected to a 6G RAN node 906. In deployment scenario 918, communication between the 5G SnMF 902 and the 6G RAN node 906 occurs via the 6G CN 920, as depicted in line 922.

[0165] exist Figure 9D In this deployment scenario 924, a 5G CN 926 is connected to a 6G CN 920. In deployment scenario 924, communication between the 5GSnMF 902 and the 6G RAN node 906 also occurs via the 5G CN 926, as depicted in line 928.

[0166] In deployment scenarios 900 and 918, where the 6G RAN node 906 is connected to the 5G CN 904 or 6G CN 920, the 5GSnMF 902 can be directly or indirectly configured to the sensing tunnel of the 6G RAN node 906. Figure 10 An example message flow 1000 between a 5G SnMF 902, a 5G CN 904, a 6G CN 920, and a 6G RAN node 906 according to various aspects of this disclosure is illustrated. As shown, the 5G SnMF 902 can request sensor capability information from the 5G CN 904 and the 6G CN 920. The 5G / 6G CN obtains the requested sensor information for the 5G SnMF 902 from a 6G RAN node in the sensing environment (e.g., 6G RAN node 906). The 5G CN 904 and the 6G CN 920 provide sensor capability information, including a subset of 6G sensing capabilities possessed by the 6G RAN node 906 that is compatible with the 5G SnMF 902.

[0167] exist Figure 10In this configuration, the 6G RAN node 906 is visible to the 5G SnMF 902. Therefore, the 5G SnMF 902 addresses the 6G RAN node 906 using the sensing-target control / data tunnel configuration. On one hand, the 6G RAN node 906's reception of the sensing-target control / data tunnel configuration activates a 5G sensing agent 908, which provides a response to the sensing-target control / data to the 5G SnMF 902 via 5G CN 904 and 6G CN 920. The 5G SnMF 902 then configures the 6G RAN node 906 using the sensing tasks performed by the 6G RAN node 906. Subsequently, the 6G RAN node 906 relays the sensing results to the 5G SnMF 902.

[0168] Figure 11 Another example message flow 1100 between a 5G SnMF 902, a 5G CN 904, a 6G CN 920, and a 6G RAN node 906 according to various aspects of this disclosure is illustrated. As shown, the 5G SnMF 902 can request sensor capability information from the 5G CN 904 and the 6G CN 920. The 5G CN 904 and the 6G CN 920 obtain the requested sensor information for the 5G SnMF 902 from a 6G RAN node in the sensing environment (e.g., the 6G RAN node 906). The 5G CN 904 and the 6G CN 920 provide sensor capability information, including a subset of 6G sensing capabilities possessed by the 6G RAN node 906 that is compatible with the 5G SnMF 902.

[0169] exist Figure 11 In this scenario, the 6G RAN node 906 is not visible to the 5G SnMF 902. Therefore, the 5G SnMF 902 sends a request to the 5G CN 904 and 6G CN 920 to establish a tunnel to the 6G RAN node 906. The 5G CN 904 and 6G CN 920 then configure a sensing-target control / data tunnel with the 6G RAN node 906, thereby activating the 5G sensing agent 908 at the 6G RAN node 906, which provides responses to the sensing-target control / data to the 5G CN 904 and 6G CN 920. The 5G CN 904 and 6G CN 920 report the results of the tunnel establishment request with the 6G RAN node 906, as determined by the 5G CN 904 and 6G CN 920, to the 5G SnMF 902. The 5G SnMF 902 then configures the 6G RAN node 906 using sensing tasks performed by the 6G RAN node 906. Subsequently, the 6G RAN node 906 transmits the sensing results to the 5G SnMF 902.

[0170] like Figure 9B As shown, in deployment scenario 912, 6G RAN node 906 is connected to 5G RAN node 914. When 6G RAN node 906 is visible to 5G SnMF 902, message sending and receiving between 6G RAN node 906 and 5G SnMF 902 can be performed according to... Figure 10 The process is similar to that shown in the diagram. However, in deployment scenario 912, 5G RAN node 914 forwards / routes messages / packets between 5G CN 904, 6GCN 920, and 6G RAN node 906.

[0171] When the 6G RAN node 906 is not visible to the 5G SnMF 902, the message transmission and reception between the 6G RAN node 906 and the 5G SnMF 902 may differ from [other methods]. Figure 10 The message sending and receiving shown in the image. Figure 12 An example message flow 1200 between 5G SnMF 902, 5G CN 904, 6G CN 920, 5G RAN node 914, and 6G RAN node 906 is illustrated according to various aspects of this disclosure when 6G RAN node 906 is not visible to 5G SnMF 902. In such a case, 5G RAN node 914 can function as a proxy, integrating the location and sensing capabilities of the 6G RAN node for reporting to 5G SnMF 902. Therefore, message passing between 5G RAN node 914 and 6G RAN node 906 can be standardized to integrate 6G RAN nodes into 5G deployment scenarios with 5G RAN nodes.

[0172] exist Figure 12 In this configuration, the 5G SnMF 902 is configured to a sensing tunnel of the 5G RAN node 914, through which sensing tasks are addressed to the 5G RAN node 914. Subsequently, the 5G RAN node 914 (e.g., via the Xn interface) configures and forwards the same sensing task to the 6G RAN node 906. The 6G RAN node 906 (e.g., via the Xn interface) reports its sensing results to the 5G RAN node 914, which then forwards the results to the 5G SnMF 902. Similarly, the signaling between the 6G RAN node 906 and the 5G RAN node 914 can be standardized.

[0173] like Figure 9D As shown in deployment scenario 924, 6G RAN node 906 is connected to 6G CN 920, which in turn is connected to 5G CN 926. In this scenario, message passing between 6G RAN node 906 and 5G SnMF 902 can be similar to... Figure 10The message transmission and reception are shown in the diagram. However, in deployment scenario 924, the 5G CN 926 forwards / routes messages / packets between the 5G SnMF and the 6G CN.

[0174] Figures 9A to 9D The deployment scenario illustrates an optional 6G UE 910 in a sensing environment. When the 6G UE 910 is visible to the 5G SnMF 902, additional messages are exchanged between the 6G UE 910 and the 6G RAN node 906. These additional messages are added based on the messages described in the message exchange between the 6G RAN node 906 and the 5G SnMF 902. In this case, the 5G SnMF 902 can configure a sensing tunnel and assign a sensing-target virtual 5G UE ID to the 6G UE 910. On one hand, the 6G UE 910 activates its own 5G sensing agent, which uses the configured virtual 5G UE ID to conduct signal / data packet communication with the 5G SnMF 902.

[0175] When the 6G UE 910 is not visible to the 5G SnMF 902, the 6G RAN node 906 can act as a proxy by integrating the positioning and sensing capabilities of the 6G UE 910 for reporting to the 5G SnMF 902. On one hand, after receiving the sensing configuration from the 5G SnMF 902, the 6G RAN node 906 can assign sensing tasks to the 6G UE 910, collect and process the sensing results from the 6G UE 910, and then transmit these results to the 5G SnMF 902.

[0176] Figure 13A and Figure 13B An example deployment scenario is illustrated, in which a 6G UE is deployed in a sensing environment with only 5G components, according to various aspects of this disclosure. In each case, the 6G UE operates as a sensor for 5GSnMF without an intermediate 6G RAN node. Figure 13A The deployment scenario 1300 shown includes a 5G SnMF 1302, a 5G CN 1304, a 5G RAN node 1306, and a 6G UE 1308 with a 5G sensing agent 1310. In deployment scenario 1300, the 5G RAN node 1306 communicates directly with the 6G UE 1308. Figure 13B The deployment scenario 1312 shown is similar to deployment scenario 1300, except that the 6G UE 1308 is connected to the 5G UE 1314, which in turn is connected to the 5G RAN node 1306.

[0177] In each deployment scenario 1300 and 1312, the 6G UE 1308 interacts with the 5G SnMF 1302 (including signaling between the 5G SnMF 1302 and the 5G sensing agent 1310 in the 6G UE 1308) to establish a control / data tunnel, report sensing capabilities, receive sensing configurations, and report sensing results. Therefore, control plane channels and user plane channels can be configured between the 6G UE 1308 and the 5G SnMF 1302.

[0178] Figure 14 An example message flow 1400 is illustrated between 5G SnMF 1302, 5G CN 1304, 5G RAN node 1306, and 6G UE 1308 in a deployment scenario 1300 when 6G UE 1308 is visible to 5G SnMF 1302, according to various aspects of this disclosure. In message flow 1400, 5G SnMF 1302 requests sensing capability information from a sensor UE (e.g., 6G UE 1308) in the sensing environment. 6G UE 1308 reports a subset of its 6G sensing capabilities compatible with 5G SnMF 1302 to 5G CN 1304, which forwards the 6G UE's location and sensing capabilities to 5G SnMF 1302.

[0179] In example message flow 1400, 5G SnMF 1302 is configured to configure a control / data tunnel to 6G UE 1308. In one aspect, 5G SnMF 1302 or 5G CN 1304 utilizes a sensing-target virtual 5G UE ID to configure 6G UE 1308. In some cases, the sensing-target virtual 5G UE ID and the sensing-target virtual 5G RAN node ID can be unified into a generic sensing-target virtual 5G sensor ID. Upon receiving a sensing tunnel configuration message (indicating the sensing-target virtual 5G UE ID), 6G UE 1308 can activate its 5G sensing agent 1310 and use the configured ID in subsequent signaling / data packets. In one aspect, the interface functionality provided by 5G sensing agent 1310 with 5G SnMF 1302 can be the same as the interface functionality provided by 5G UE with 5G SnMF 1302.

[0180] Figure 15An example message flow 1500 is illustrated between 5G SnMF 1302, 5G CN 1304, 5G RAN node 1306, and 6G UE 1308 in scenario 1300 when 6G UE 1308 is not visible to 5G SnMF 1302, according to various aspects of this disclosure. In message flow 1500, 5G SnMF 1302 requests sensing capability information of a sensor UE (e.g., 6G UE 1308) in the sensing environment. 6G UE 1308 reports a subset of 6G sensing capabilities compatible with 5G SnMF 1302 to 5G CN 1304, which forwards the 6G UE's location and sensing capabilities to 5G SnMF 1302.

[0181] Since 6G UE 1308 is not visible to 5G SnMF 1302 in message flow 1500, 5G SnMF 1302 sends a request to 5GCN 1304 to establish a tunnel to 6G UE 1308. 5G CN 1304 then configures a sensing-target control / data tunnel with 6G UE 1308, thereby activating the 5G sensing agent 1310 at 6G UE 1308, which provides a response to sensing-target control / data to 5G CN 1304. 5G CN 1304 reports the result of the tunnel establishment request with 6G UE determined by 5G CN 1304 to 5G SnMF 1302. 5G SnMF 1302 then configures 6G UE 1308 using sensing tasks performed by 6G UE 1308. Subsequently, 6G UE 1308 transmits the sensing results to 5G SnMF 902.

[0182] In scenario 1302, 6G UE 1308 communicates with 5G UE 1314. When 6G UE 1308 is visible to 5G SnMF 1302, it can employ... Figure 14 The process shown is similar to message reception and transmission, except that 5G UE 1314 forwards / routes messages / packets between 5G RAN node 1306 and 6G UE 1308.

[0183] Figure 16An example message flow 1600 between 5G SnMF 1302, 5G CN 1304, 5G RAN node 1306, 5G UE 1314, and 6G UE 1308 is illustrated in scenario 1312 when 6G UE 1308 is not visible to 5G SnMF 1302, according to various aspects of this disclosure. In this case, 5G UE 1314 can function as a proxy, integrating the location and sensing capabilities of 6G UE 1308 for reporting to 5G SnMF 1302. Therefore, message passing between 5G UE 1314 and 6G 1308 can be standardized to integrate the 6G UE into 5G deployment scenarios with 5G UEs.

[0184] exist Figure 16 In this configuration, 5G SnMF 1302 is configured to access the sensing tunnel of 5G UE 1314 and to perform sensing tasks addressed to 5G UE 1314. 5G UE 1314 configures / forwards the same sensing task to 6G UE 1308 via sidelink communication. 6G UE 1308 reports the sensing results to 5G UE 1314 via the sidelink, and the 5G UE then transmits the sensing results to 5G SnMF 1302.

[0185] The foregoing aspects of this disclosure can be extended to dual-site sensing scenarios. In a dual-site sensing scenario involving two RAN nodes, the transmitting RAN node or the receiving RAN node can be paired to form a sensing capability. The transmitting or receiving RAN node can report its dual-site sensing capability to the 5G / 6G CN, which forwards this information to the 5G SnMF. The reporting RAN node acts as an anchor for the RAN node payer. If the anchor is a 6G RAN node, the procedures and message transmission described above for the 6G RAN node to operate as a sensor for the 5G SnMF are applicable.

[0186] In a dual-site sensing scenario between a RAN node and a UE, the RAN node and UE are paired to achieve dual-site sensing capability. Typically, the RAN node acts as an anchor point and reports the dual-site sensing capability to the 5G / 6G CN and ultimately to the 5G SnMF. If the anchor point is a 6G RAN node, the process and message transmission described above, in which the 6G RAN node acts as a sensor for the 5G SnMF, are applicable.

[0187] In a dual-site sensing scenario between two UEs, the two UEs are paired to achieve dual-site sensing capability. The transmitting or receiving UE can report this capability to the 5G / 6G RAN, 5G / 6G CN, and ultimately to the 5G SnMF. The reporting UE acts as the anchor point for this UE pair. If the anchor point is a 6G UE, it can employ a method similar to... Figure 16The process shown is similar to the process of sending and receiving messages.

[0188] The foregoing portions of this disclosure have covered a hybrid environment in which 5G SnMF is deployed as a sensing server and 6G components are deployed as sensors. However, there are also hybrid deployment scenarios in which 6G SnMF is deployed as a sensing server and 5G components are deployed as sensors. Figures 17A to 17D An example deployment scenario is shown in which a 5G RAN node can be used as a sensor for 6G SnMF according to various aspects of this disclosure. Figure 17A An example deployment scenario 1700 is shown, including a 6G SnMF 1702, a 6G CN 1704, a 5G RAN node 1706, and an optional 5G UE 1708. In deployment scenario 1700, neither the 5G CN nor the 6G RAN node is deployed. Therefore, the 5G RAN node 1706 is connected to the 6G CN 1704. Figure 17B In the deployment scenario 1710 shown, a 6G 5G RAN node 1712 connected to the 5G RAN node 1706 has been deployed.

[0189] Figure 17C Deployment scenario 1714 is shown, in which the 6G SnMF 1702 is hosted by and / or connected to the 5G CN 1716. The 5G CN 1716 is then connected to the 5G RAN node 1706.

[0190] Figure 17D Deployment scenario 1718 is shown, in which the 6G SnMF 1702 is hosted by and / or connected to the 6G CN 1720. The 6G CN 1720 is then connected to the 5G CN 1716.

[0191] refer to Figure 17B In the deployment scenario 1710 shown, the 5G RAN node 1706 may or may not be visible to the 6G SnMF 1702. When the 5G RAN node 1706 is visible to the 6G SnMF 1702, it can receive a sensing capability information request from the 6G SnMF 1702. After receiving the sensing capability request from the 6G SnMF 1702, the 5G RAN node 1706 reports its sensing capabilities, and the 6G SnMF 1702 should support all of these sensing capabilities. The 6G SnMF 1702 then transmits sensing tasks to the 5G RAN node 1706 based on the capabilities reported by the 5G RAN node 1706.

[0192] Figure 18An example message flow 1800 between 6G SnMF 1702, 6G CN 1704, 6G RAN node 1712, and 5G RAN node 1706 is illustrated according to various aspects of this disclosure when 5G RAN node 1706 is not visible to 6G SnMF 1702. In such a case, 6G RAN node 1712 can function as a proxy, integrating the location and sensing capabilities of 5G RAN node 1706 for reporting to 6G SnMF 1702. Therefore, message passing between 6G RAN node 1712 and 5G RAN node 1706 can be standardized to integrate 5G RAN nodes into 6G deployment scenarios with 6G RAN nodes.

[0193] exist Figure 18 In this configuration, the 6G SnMF 1702 is configured to access the sensing tunnel of the 6G RAN node 1712, through which sensing tasks are addressed to the 6G RAN node 1712. Subsequently, the 6G RAN node 1712 (e.g., via the Xn interface) configures and forwards the same sensing task to the 5G RAN node 1706. The 5G RAN node 1706 (e.g., via the Xn interface) reports its sensing results to the 6G RAN node 1712, which then forwards the results to the 6G SnMF 1702. Similarly, the signaling between the 6G RAN node 1712 and the 5G RAN node 1706 can be standardized.

[0194] Figure 19A and Figure 19B An example deployment scenario is shown where a 6G SnMF, according to various aspects of this disclosure, connects to a 5G UE acting as a sensor without an intermediate 5G RAN node. Figure 19A In this deployment scenario 1900, 6G SnMF 1902, 6G CN 1904, and 6G RAN 1906 are included. 5G UE 1908 is configured as a sensor for the 6G SnMF 1902. Figure 19B In the deployment scenario 1910 shown, 5G UE 1908 and 6G UE 1912 communicate via sidelink.

[0195] In deployment scenario 1910, communication between the 5G UE 1908 and the 6G SnMF 1902 will vary depending on whether the 5G UE 1908 is visible to the 6G SnMF 1902. If the 5G UE 1908 is visible to the 6G SnMF 1902, the 6G SnMF 1902 will configure sensing tasks for the 5G UE based on the sensing capabilities reported by the 5G UE 1908 to the 6G SnMF 1902. Since the 6G SnMF 1902 will have stronger sensing capabilities than those available in the 5G RAT, it will support any sensing capabilities reported by the 5G UE 1908.

[0196] In cases where 5G UE 1908 is not visible to 6G SnMF 1902, 6G UE 1912 integrates the positioning and sensing capabilities of 5G UE 1908 into its own positioning and sensing capabilities and reports these capabilities to 6G SnMF 1902. 6G SnMF 1902 configures the sensing tunnel to the 6G UE and addresses the sensing tasks to the 6G UE. Then, 6G UE 1912 configures / forwards the same sensing task to 5G UE 1908 via a sidelink. 5G UE 1908 reports the sensing results to 6G UE 1912 via the sidelink. 6G UE 1912 then transmits the sensing results to 6G SnMF 1902. During this process, the signaling between 5G UE 1912 and 6G UE 1908 should be standardized.

[0197] Figure 20 An example method 2000 for wireless communication, purportedly performed by a second Radio Access Technology (RAT) Radio Access Network (RAN) node, according to various aspects of this disclosure, is illustrated. In operation 2002, the second RAT RAN receives a RAN node sensing capability request from a first RAT Sensing Management Function (SnMF). In one aspect, operation 2002 may be performed by one or more WWAN transceivers 350, one or more processors 384, a memory 386, and / or sensing components 388, any or all of which may be considered as components for performing the operation.

[0198] At operation 2004, the second RAT RAN provides a response to the first RAT SnMF for a RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of the second RAT sensing capabilities, which is limited to sensing capabilities compatible with the first RAT SnMF. In one aspect, operation 2002 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or sensing components 388, any or all of which may be considered as components for performing the operation.

[0199] It should be understood that the technical advantage of Method 2000 is that it facilitates sensing in deployment scenarios employing hybrid radio access technologies with different sensing capabilities.

[0200] Figure 21 An example method 2100 for wireless communication that can be performed by a second Radio Access Technology (RAT) User Equipment (UE) is illustrated. At operation 2102, the second RAT UE receives a UE sensing capability request from a first RAT Sensing Management Function (SnMF). In one aspect, operation 2102 can be performed by one or more WWAN transceivers 310, one or more processors 342, memory 340, and / or sensing components 342, any or all of which can be considered as components used to perform the operation.

[0201] At operation 2104, the second RAT UE activates the first RAT User Equipment (UE) sensing agent at the second RAT UE in response to receiving a UE sensing capability request. In one aspect, operation 2104 may be performed by one or more WWAN transceivers 310, one or more processors 342, memory 340, and / or sensing components 342, any or all of which may be considered as components for performing the operation.

[0202] At operation 2106, the second RAT UE responds to the first RAT SnMF for a UE sensing capability request based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF. In one aspect, operation 2106 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or sensing components 342, any or all of which may be considered as components for performing the operation.

[0203] At operation 2108, the second RAT UE receives a UE sensing tunnel configuration indicating the sensing purpose and a virtual first RAT UE identifier. In one aspect, operation 2108 may be performed by one or more WWAN transceivers 310, one or more processors 342, memory 340, and / or sensing components 342, any or all of which may be considered as components for performing the operation.

[0204] At operation 2110, the second RAT UE uses the first RAT UE sensing agent in response to the UE sensing tunnel configuration. In one aspect, operation 2110 may be performed by one or more WWAN transceivers 310, one or more processors 342, memory 340 and / or sensing components 342, any or all of which may be considered as components for performing the operation.

[0205] It should be understood that the technical advantage of method 2100 is that it facilitates sensing in deployment scenarios employing hybrid radio access technologies with different sensing capabilities.

[0206] Figure 22 An example method 2200 for wireless communication that can be performed by a second radio access technology (RAT) sensing management function (SnMF) is illustrated. At operation 2202, the second RAT SnMF transmits a RAN node sensing capability request to a first RAT radio access (RAN) node, wherein the RAN node sensing capability request is limited to a subset of the second RAT sensing capabilities, which includes only sensing capabilities compatible with the first RAT RAN node. In one aspect, operation 2202 can be performed by one or more network transceivers 390, one or more processors 394, a memory 396, and / or sensing components 398, any or all of which can be considered as components for performing the operation.

[0207] At operation 2204, the second RAT SnMF receives a RAN node sensing capability response based on a subset of the second RAT sensing capabilities from the first RAT RAN node. In one aspect, operation 2204 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or sensing components 398, any or all of which may be considered as components for performing the operation.

[0208] At operation 2206, the second RAT SnMF transmits a RAN node sensing tunnel configuration indicating the sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node. In one aspect, operation 2206 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or sensing components 398, any or all of which may be considered as components used to perform the operation.

[0209] At operation 2208, the second RAT SnMF receives a RAN node sensing tunnel configuration response from the first RAT RAN node based on the sensing purpose and a virtual first RAT RAN node identifier. In one aspect, operation 2208 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or sensing components 398, any or all of which may be considered as components for performing the operation.

[0210] It should be understood that the technical advantage of method 2200 is that it facilitates sensing in deployment scenarios employing hybrid radio access technologies with different sensing capabilities.

[0211] Figure 23 An example method 2300 for wireless communication that can be performed by a first Radio Access Technology (RAT) User Equipment (UE) is illustrated. At operation 2302, the first RAT UE receives a UE sensing capability request from a second RAT Sensing Management Function (SnMF), wherein the UE sensing capability request is limited to a subset of the second RAT UE's sensing capabilities compatible with the first RAT UE. In one aspect, operation 2302 can be performed by one or more WWAN transceivers 310, one or more processors 332, a memory 340, and / or sensing components 342, any or all of which can be considered as components for performing the operation.

[0212] At operation 2304, the first RAT UE provides a first response to the second RAT SnMF in response to the first RAT UE's sensing capability request, wherein the first response is based on a subset of the second RAT UE's sensing capabilities indicated by the UE's sensing capability request. In one aspect, operation 2304 may be performed by one or more WWAN transceivers 310, one or more processors 342, memory 340, and / or sensing components 342, any or all of which may be considered as components for performing the operation.

[0213] At operation 2306, the first RAT UE receives a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF. In one aspect, operation 2306 may be performed by one or more WWAN transceivers 310, one or more processors 342, memory 340 and / or sensing components 342, any or all of which may be considered as components for performing the operation.

[0214] At operation 2308, the first RAT UE provides a second response to the second RAT SnMF based on the UE sensing tunnel configuration. In one aspect, operation 2308 may be performed by one or more WWAN transceivers 310, one or more processors 342, memory 340 and / or sensing components 342, any or all of which may be considered as components for performing the operation.

[0215] It should be understood that the technical advantage of method 2300 is that it facilitates sensing in deployment scenarios employing hybrid radio access technologies with different sensing capabilities.

[0216] 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 include more features in the example clauses than are expressly 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 expressly include these combinations unless expressly 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.

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

[0218] Clause 1. A method of wireless communication performed by a second radio access technology (RAT) radio access network (RAN) node, the method comprising: receiving a RAN node sensing capability request from a first RAT sensing management function (SnMF); and providing a response to the first RAT SnMF to the RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

[0219] Clause 2. The method described in Clause 1, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0220] Clause 3. The method according to any one of Clauses 1 to 2, wherein: the RAN node sensing capability request is received from the first RAT SnMF via the core network (CN), or received from the first RAT SnMF via the first RAT RAN node; and the response to the RAN node sensing capability request is configured to be provided to the first RAT SnMF via the CN or the first RAT RAN node.

[0221] Clause 4. The method described in Clause 3, wherein: the CN is a first RAT CN; or the CN is a second RATCN.

[0222] Clause 5. The method according to any one of Clauses 1 to 4, the method further comprising: receiving from the first RATSnMF a sensing tunnel configuration indicating the sensing purpose and a virtual first RAT RAN node identifier.

[0223] Clause 6. The method according to Clause 5, wherein: the sensing tunnel configuration is: received directly from the first RAT SnMF; received from the first RAT SnMF via the core network (CN); received from the first RAT SnMF via the first RAT RAN node; or any combination thereof.

[0224] Clause 7. The method described in Clause 6, wherein: the CN is a first RAT CN; or the CN is a second RATCN.

[0225] Clause 8. The method according to any one of Clauses 5 to 7, the method further comprising: activating a first RAT sensing agent at the second RAT RAN node in response to receiving the sensing tunnel configuration; and providing a response to the sensing tunnel configuration to the first RAT SnMF based on the virtual first RAT RAN node identifier using the first RAT sensing agent at the second RAT RAN node.

[0226] Clause 9. The method according to Clause 8, wherein: the response to the sensing tunnel configuration is configured to: be sent directly to the first RAT SnMF; be sent to the core network (CN) for forwarding to the first RAT SnMF; be sent to the first RAT RAN node for forwarding to the first RAT SnMF; or any combination thereof.

[0227] Clause 10. The method according to any one of Clauses 5 to 9, the method further comprising: transmitting a first RAT UE sensing configuration to a second RAT user equipment (UE) based on the sensing tunnel configuration received by the second RAT RAN node; and receiving sensing measurements from the second RAT UE based on the first RAT UE sensing configuration.

[0228] Clause 11. A method of wireless communication performed by a second Radio Access Technology (RAT) User Equipment (UE), the method comprising: receiving a UE sensing capability request from a first RAT Sensing Management Function (SnMF); activating a first RAT User Equipment (UE) sensing agent at the second RAT UE in response to receiving the UE sensing capability request; providing a response to the UE sensing capability request to the first RAT SnMF based on a subset of second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF; receiving a UE sensing tunnel configuration indicating a sensing purpose and a virtual first RAT UE identifier; and responding to the UE sensing tunnel configuration using the first RAT UE sensing agent.

[0229] Clause 12. The method described in Clause 11, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0230] Clause 13. The method according to any one of Clauses 11 to 12, wherein: the UE sensing capability request is received via a first RAT radio access network (RAN) node; and the response to the UE sensing capability request is configured to be forwarded via the first RAT RAN node to the first RAT SnMF.

[0231] Clause 14. The method according to any one of Clauses 11 to 13, wherein: the UE sensing capability request is received via a first RAT UE; and the response to the UE sensing capability request is configured to be forwarded via the first RAT UE to the first RAT SnMF.

[0232] Clause 15. A method of wireless communication performed by a second radio access technology (RAT) sensing management function (SnMF), the method comprising: transmitting a RAN node sensing capability request to a first RAT radio access (RAN) node, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; receiving a RAN node sensing capability response based on the subset of second RAT sensing capabilities from the first RAT RAN node; transmitting a RAN node sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node; and receiving a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier from the first RAT RAN node.

[0233] Clause 16. The method according to Clause 15, wherein: the RAN node sensing capability request is configured to be forwarded to the first RAT RAN node via a first RAT core network (CN), a second RAT CN, a second RAT RAN node, or any combination thereof.

[0234] Clause 17. A method of wireless communication performed by a first Radio Access Technology (RAT) User Equipment (UE), the method comprising: receiving a UE sensing capability request from a second RAT Sensing Management Function (SnMF), wherein the UE sensing capability request is limited to a subset of second RAT UE sensing capabilities compatible with the first RAT UE; providing a first response to the second RAT SnMF in response to the first RAT UE sensing capability request, wherein the first response is based on the subset of second RAT UE sensing capabilities indicated by the UE sensing capability request; receiving a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF; and providing a second response to the second RAT SnMF based on the UE sensing tunnel configuration.

[0235] Clause 18. The method described in accordance with Clause 17, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0236] Clause 19. The method according to any one of Clauses 17 to 18, wherein: the first RAT UE sensing capability request is received from the second RAT SnMF via a second RAT radio access network (RAN) node; the first response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node; the sensing tunnel configuration is received from the second RAT SnMF via the second RAT RAN node; and the second response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node.

[0237] Clause 20. The method according to any one of Clauses 17 to 19, wherein: the first RAT UE sensing capability request is received from the second RAT SnMF via the second RAT UE; the first response is configured to be forwarded to the second RAT SnMF via the second RAT UE; the sensing tunnel configuration is received from the second RAT SnMF via the second RAT UE; and the second response is configured to be forwarded to the second RAT SnMF via the second RAT UE.

[0238] Clause 21. A second Radio Access Technology (RAT) Radio Access Network (RAN) node, the second Radio Access Technology (RAT) Radio Access Network (RAN) node 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: receive a RAN node sensing capability request from a first RAT Sensing Management Function (SnMF) via the one or more transceivers; and provide a response to the first RAT SnMF to the RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

[0239] Clause 22. The second RAT RAN as described in Clause 21, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0240] Clause 23. A second RAT RAN according to any one of Clauses 21 to 22, wherein: the RAN node sensing capability request is received from the first RAT SnMF via the core network (CN) or via the first RAT RAN node from the first RAT SnMF; and the response to the RAN node sensing capability request is configured to be provided to the first RAT SnMF via the CN or the first RAT RAN node.

[0241] Clause 24. The second RAT RAN as described in Clause 23, wherein: the CN is a first RAT CN; or the CN is a second RAT CN.

[0242] Clause 25. A second RAT RAN according to any one of Clauses 21 to 24, wherein the one or more processors are further configured individually or in combination to receive, via the one or more transceivers, a sensing tunnel configuration indicating the sensing purpose and a virtual first RAT RAN node identifier from the first RAT SnMF.

[0243] Clause 26. The second RAT RAN as described in Clause 25, wherein: the sensing tunnel configuration is: received directly from the first RAT SnMF; received from the first RAT SnMF via the core network (CN); received from the first RAT SnMF via the first RAT RAN node; or any combination thereof.

[0244] Clause 27. The second RAT RAN as described in Clause 26, wherein: the CN is a first RAT CN; or the CN is a second RAT CN.

[0245] Clause 28. A second RAT RAN according to any one of Clauses 25 to 27, wherein the one or more processors are further configured individually or in combination to: activate a first RAT sensing agent at the second RAT RAN node in response to receiving the sensing tunnel configuration; and provide a response to the sensing tunnel configuration to the first RAT SnMF based on the virtual first RAT RAN node identifier using the first RAT sensing agent at the second RAT RAN node.

[0246] Clause 29. The second RAT RAN as described in Clause 28, wherein: the response to the sensing tunnel configuration is configured to: be sent directly to the first RAT SnMF; be sent to the core network (CN) for forwarding to the first RAT SnMF; be sent to the first RAT RAN node for forwarding to the first RAT SnMF; or any combination thereof.

[0247] Clause 30. The second RAT RAN according to any one of Clauses 25 to 29, wherein the one or more processors are further configured individually or in combination to: transmit a first RAT UE sensing configuration to a second RAT user equipment (UE) via the one or more transceivers based on the sensing tunnel configuration received by the second RAT RAN node; and receive sensing measurements from the second RAT UE via the one or more transceivers based on the first RAT UE sensing configuration.

[0248] Clause 31. A second Radio Access Technology (RAT) User Equipment (UE), the second RAT User Equipment (UE) 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: receive a UE sensing capability request from a first RAT Sensing Management Function (SnMF) via the one or more transceivers; activate a first RAT User Equipment (UE) sensing agent at the second RAT UE in response to receiving the UE sensing capability request; provide a response to the UE sensing capability request to the first RAT SnMF based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF; receive a UE sensing tunnel configuration indicating a sensing purpose and a virtual first RAT UE identifier via the one or more transceivers; and respond to the UE sensing tunnel configuration using the first RAT UE sensing agent.

[0249] Clause 32. The second RAT UE as described in Clause 31, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0250] Clause 33. A second RAT UE according to any one of Clauses 31 to 32, wherein: the UE sensing capability request is received via a first RAT radio access network (RAN) node; and the response to the UE sensing capability request is configured to be forwarded via the first RAT RAN node to the first RAT SnMF.

[0251] Clause 34. A second RAT UE according to any one of Clauses 31 to 33, wherein: the UE sensing capability request is received via a first RAT UE; and the response to the UE sensing capability request is configured to be forwarded via the first RAT UE to the first RAT SnMF.

[0252] Clause 35. A second radio access technology (RAT) sensing management function (SnMF), the second radio access technology (RAT) sensing management function (SnMF) 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: transmit a RAN node sensing capability request to a first RAT radio access (RAN) node via the one or more transceivers, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; receive a RAN node sensing capability response based on the subset of second RAT sensing capabilities from the first RAT RAN node via the one or more transceivers; transmit a RAN node sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node via the one or more transceivers; and receive a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier from the first RAT RAN node via the one or more transceivers.

[0253] Clause 36. The second RAT SnMF as described in Clause 35, wherein: the RAN node sensing capability request is configured to be forwarded to the first RAT RAN node via the first RAT core network (CN), the second RAT CN, the second RAT RAN node, or any combination thereof.

[0254] Clause 37. A first Radio Access Technology (RAT) User Equipment (UE), the first RAT User Equipment (UE) comprising: one or more memories; one or more transceivers; and one or more processors, the one or more processors being communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receive a UE sensing capability request from a second RAT Sensing Management Function (SnMF) via the one or more transceivers, wherein the UE sensing capability request is limited to a subset of second RAT UE sensing capabilities compatible with the first RAT UE; provide a first response to the second RAT SnMF in response to the first RAT UE sensing capability request, wherein the first response is based on the subset of second RAT UE sensing capabilities indicated by the UE sensing capability request; receive a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF via the one or more transceivers; and provide a second response to the second RAT SnMF based on the UE sensing tunnel configuration.

[0255] Clause 38. The first RAT UE as described in Clause 37, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0256] Clause 39. A first RAT UE according to any one of Clauses 37 to 38, wherein: the first RAT UE sensing capability request is received from the second RAT SnMF via a second RAT radio access network (RAN) node; the first response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node; the sensing tunnel configuration is received from the second RAT SnMF via the second RAT RAN node; and the second response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node.

[0257] Clause 40. A first RAT UE according to any one of Clauses 37 to 39, wherein: the first RAT UE sensing capability request is received from the second RAT SnMF via the second RAT UE; the first response is configured to be forwarded to the second RAT SnMF via the second RAT UE; the sensing tunnel configuration is received from the second RAT SnMF via the second RAT UE; and the second response is configured to be forwarded to the second RAT SnMF via the second RAT UE.

[0258] Clause 41. A second radio access technology (RAT) radio access network (RAN) node, the second radio access technology (RAT) radio access network (RAN) node comprising: means for receiving a RAN node sensing capability request from a first RAT sensing management function (SnMF); and means for providing a response to the first RAT SnMF to the RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

[0259] Clause 42. The second RAT RAN as described in Clause 41, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0260] Clause 43. A second RAT RAN according to any one of Clauses 41 to 42, wherein: the RAN node sensing capability request is received from the first RAT SnMF via the core network (CN) or via the first RAT RAN node from the first RAT SnMF; and the response to the RAN node sensing capability request is configured to be provided to the first RAT SnMF via the CN or the first RAT RAN node.

[0261] Clause 44. The second RAT RAN as described in Clause 43, wherein: the CN is a first RAT CN; or the CN is a second RAT CN.

[0262] Clause 45. The second RAT RAN according to any one of Clauses 41 to 44, the second RAT RAN further comprising: a component for receiving a sensing tunnel configuration indicating the sensing purpose and a virtual first RAT RAN node identifier from the first RAT SnMF.

[0263] Clause 46. The second RAT RAN as described in Clause 45, wherein: the sensing tunnel configuration is: received directly from the first RAT SnMF; received from the first RAT SnMF via the core network (CN); received from the first RAT SnMF via the first RAT RAN node; or any combination thereof.

[0264] Clause 47. The second RAT RAN as described in Clause 46, wherein: the CN is a first RAT CN; or the CN is a second RAT CN.

[0265] Clause 48. The second RAT RAN according to any one of Clauses 45 to 47, the second RAT RAN further comprising: means for activating a first RAT sensing agent at the second RAT RAN node in response to receiving the sensing tunnel configuration; and means for providing a response to the sensing tunnel configuration to the first RAT SnMF based on the virtual first RAT RAN node identifier using the first RAT sensing agent at the second RAT RAN node.

[0266] Clause 49. The second RAT RAN as described in Clause 48, wherein: the response to the sensing tunnel configuration is configured to: be sent directly to the first RAT SnMF; be sent to the core network (CN) for forwarding to the first RAT SnMF; be sent to the first RAT RAN node for forwarding to the first RAT SnMF; or any combination thereof.

[0267] Clause 50. The second RAT RAN according to any one of Clauses 45 to 49, the second RAT RAN further comprising: components for transmitting a first RAT UE sensing configuration to a second RAT user equipment (UE) based on the sensing tunnel configuration received by the second RAT RAN node; and components for receiving sensing measurements from the second RAT UE based on the first RAT UE sensing configuration.

[0268] Clause 51. A second Radio Access Technology (RAT) User Equipment (UE), the second RAT User Equipment (UE) comprising: means for receiving a UE sensing capability request from a first RAT Sensing Management Function (SnMF); means for activating a first RAT User Equipment (UE) sensing agent at the second RAT UE in response to receiving the UE sensing capability request; means for providing a response to the UE sensing capability request to the first RAT SnMF based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF; means for receiving a UE sensing tunnel configuration indicating a sensing purpose and a virtual first RAT UE identifier; and means for responding to the UE sensing tunnel configuration using the first RAT UE sensing agent.

[0269] Clause 52. The second RAT UE as described in Clause 51, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0270] Clause 53. A second RAT UE according to any one of Clauses 51 to 52, wherein: the UE sensing capability request is received via a first RAT radio access network (RAN) node; and the response to the UE sensing capability request is configured to be forwarded to the first RAT SnMF via the first RAT RAN node.

[0271] Clause 54. A second RAT UE according to any one of Clauses 51 to 53, wherein: the UE sensing capability request is received via a first RAT UE; and the response to the UE sensing capability request is configured to be forwarded via the first RAT UE to the first RAT SnMF.

[0272] Clause 55. A second radio access technology (RAT) sensing management function (SnMF), the second radio access technology (RAT) sensing management function (SnMF) comprising: means for transmitting a RAN node sensing capability request to a first RAT radio access (RAN) node, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; means for receiving from the first RAT RAN node a RAN node sensing capability response based on the subset of second RAT sensing capabilities; means for transmitting to the first RAT RAN node a RAN node sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier; and means for receiving from the first RAT RAN node a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier.

[0273] Clause 56. The second RAT SnMF as described in Clause 55, wherein: the RAN node sensing capability request is configured to be forwarded to the first RAT RAN node via the first RAT core network (CN), the second RAT CN, the second RAT RAN node, or any combination thereof.

[0274] Clause 57. A first Radio Access Technology (RAT) User Equipment (UE), the first RAT User Equipment (UE) comprising: means for receiving a UE sensing capability request from a second RAT Sensing Management Function (SnMF), wherein the UE sensing capability request is limited to a subset of second RAT UE sensing capabilities compatible with the first RAT UE; means for providing a first response to the second RAT SnMF in response to the first RAT UE sensing capability request, wherein the first response is based on the subset of second RAT UE sensing capabilities indicated by the UE sensing capability request; means for receiving a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF; and means for providing a second response to the second RAT SnMF based on the UE sensing tunnel configuration.

[0275] Clause 58. The first RAT UE as described in Clause 57, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0276] Clause 59. A first RAT UE according to any one of Clauses 57 to 58, wherein: the first RAT UE sensing capability request is received from the second RAT SnMF via a second RAT radio access network (RAN) node; the first response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node; the sensing tunnel configuration is received from the second RAT SnMF via the second RAT RAN node; and the second response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node.

[0277] Clause 60. A first RAT UE according to any one of Clauses 57 to 59, wherein: the first RAT UE sensing capability request is received from the second RAT SnMF via the second RAT UE; the first response is configured to be forwarded to the second RAT SnMF via the second RAT UE; the sensing tunnel configuration is received from the second RAT SnMF via the second RAT UE; and the second response is configured to be forwarded to the second RAT SnMF via the second RAT UE.

[0278] Clause 61. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a second Radio Access Technology (RAT) Radio Access Network (RAN) node, cause the second RAT RAN node to: receive a RAN node sensing capability request from a first RAT Sensing Management Function (SnMF); and provide a response to the first RAT SnMF to the RAN node sensing capability request, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

[0279] Clause 62. The non-transitory computer-readable medium as described in Clause 61, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0280] Clause 63. A non-transitory computer-readable medium according to any one of Clauses 61 to 62, wherein: the RAN node sensing capability request is received from the first RAT SnMF via the core network (CN) or via the first RAT RAN node; and the response to the RAN node sensing capability request is configured to be provided to the first RAT SnMF via the CN or the first RAT RAN node.

[0281] Clause 64. A non-transitory computer-readable medium as described in Clause 63, wherein: the CN is a first RAT CN; or the CN is a second RAT CN.

[0282] Clause 65. The non-transitory computer-readable medium according to any one of Clauses 61 to 64, the non-transitory computer-readable medium further comprising computer-executable instructions that, when executed by the second RAT RAN node, cause the second RAT RAN node to: receive from the first RAT SnMF a sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier.

[0283] Clause 66. The non-transitory computer-readable medium as described in Clause 65, wherein: the sensing tunnel configuration is: received directly from the first RAT SnMF; received from the first RAT SnMF via the core network (CN); received from the first RAT SnMF via the first RAT RAN node; or any combination thereof.

[0284] Clause 67. A non-transitory computer-readable medium as described in Clause 66, wherein: the CN is a first RAT CN; or the CN is a second RAT CN.

[0285] Clause 68. A non-transitory computer-readable medium according to any one of Clauses 65 to 67, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the second RAT RAN node, cause the second RAT RAN node to: activate a first RAT sensing agent at the second RAT RAN node in response to receiving the sensing tunnel configuration; and provide a response to the sensing tunnel configuration to the first RAT SnMF based on the virtual first RAT RAN node identifier using the first RAT sensing agent at the second RAT RAN node.

[0286] Clause 69. The non-transitory computer-readable medium as described in Clause 68, wherein: the response to the sensing tunnel configuration is configured to: be sent directly to the first RAT SnMF; be sent to the core network (CN) for forwarding to the first RAT SnMF; be sent to the first RAT RAN node for forwarding to the first RAT SnMF; or any combination thereof.

[0287] Clause 70. A non-transitory computer-readable medium according to any one of Clauses 65 to 69, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the second RAT RAN node, cause the second RAT RAN node to: transmit a first RAT UE sensing configuration to the second RAT User Equipment (UE) based on the sensing tunnel configuration received by the second RAT RAN node; and receive sensing measurements from the second RAT UE based on the first RAT UE sensing configuration.

[0288] Clause 71. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a second Radio Access Technology (RAT) User Equipment (UE), cause the second RAT UE to: receive a UE sensing capability request from a first RAT Sensing Management Function (SnMF); activate a first RAT User Equipment (UE) sensing agent at the second RAT UE in response to receiving the UE sensing capability request; provide a response to the UE sensing capability request to the first RAT SnMF based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF; receive a UE sensing tunnel configuration indicating a sensing purpose and a virtual first RAT UE identifier; and respond to the UE sensing tunnel configuration using the first RAT UE sensing agent.

[0289] Clause 72. The non-transitory computer-readable medium as described in Clause 71, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0290] Clause 73. A non-transitory computer-readable medium according to any one of Clauses 71 to 72, wherein: the UE sensing capability request is received via a first RAT radio access network (RAN) node; and the response to the UE sensing capability request is configured to be forwarded via the first RAT RAN node to the first RAT SnMF.

[0291] Clause 74. A non-transitory computer-readable medium according to any one of Clauses 71 to 73, wherein: the UE sensing capability request is received via a first RAT UE; and the response to the UE sensing capability request is configured to be forwarded via the first RAT UE to the first RAT SnMF.

[0292] Clause 75. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a second Radio Access Technology (RAT) Sensing Management Function (SnMF), cause the second RAT SnMF to: transmit a RAN node sensing capability request to a first RAT Radio Access (RAN) node, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; receive a RAN node sensing capability response based on the subset of second RAT sensing capabilities from the first RAT RAN node; transmit a RAN node sensing tunnel configuration indicating a sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node; and receive a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier from the first RAT RAN node.

[0293] Clause 76. The non-transitory computer-readable medium as described in Clause 75, wherein: the RAN node sensing capability request is configured to be forwarded to the first RAT RAN node via a first RAT core network (CN), a second RAT CN, a second RAT RAN node, or any combination thereof.

[0294] Clause 77. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a first radio access technology (RAT) user equipment (UE), cause the first RAT UE to: receive a UE sensing capability request from a second RAT sensing management function (SnMF), wherein the UE sensing capability request is limited to a subset of sensing capabilities of the second RAT UE compatible with the first RAT UE; provide a first response to the second RAT SnMF in response to the first RAT UE sensing capability request, wherein the first response is based on the subset of sensing capabilities of the second RAT UE indicated by the UE sensing capability request; receive a UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF; and provide a second response to the second RAT SnMF based on the UE sensing tunnel configuration.

[0295] Clause 78. The non-transitory computer-readable medium as described in Clause 77, wherein: the first RAT is a fifth-generation (5G) radio access technology; and the second RAT is a sixth-generation (6G) radio access technology.

[0296] Clause 79. A non-transitory computer-readable medium according to any one of Clauses 77 to 78, wherein: the first RAT UE sensing capability request is received from the second RAT SnMF via a second RAT radio access network (RAN) node; the first response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node; the sensing tunnel configuration is received from the second RAT SnMF via the second RAT RAN node; and the second response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node.

[0297] Clause 80. A non-transitory computer-readable medium according to any one of Clauses 77 to 79, wherein: the first RAT UE sensing capability request is received from the second RAT SnMF via the second RAT UE; the first response is configured to be forwarded to the second RAT SnMF via the second RAT UE; the sensing tunnel configuration is received from the second RAT SnMF via the second RAT UE; and the second response is configured to be forwarded to the second RAT SnMF via the second RAT UE.

[0298] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and arts. 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.

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

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

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

[0302] 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, including 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 devices, disk storage devices 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.

[0303] 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 expressly 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 second radio access technology (RAT) radio access network (RAN) node, the second radio access technology (RAT) radio access network (RAN) node 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: Receive RAN node sensing capability requests from the first RAT sensing management function (SnMF) via the one or more transceivers; and A response to the RAN node sensing capability request is provided to the first RAT SnMF, wherein the response to the RAN node sensing capability request is based on a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities being limited to sensing capabilities compatible with the first RAT SnMF.

2. The second RAT RAN according to claim 1, wherein: The first RAT is fifth-generation (5G) radio access technology; and The second RAT is the sixth generation (6G) radio access technology.

3. The second RAT RAN according to claim 1, wherein: The RAN node sensing capability request is Received from the first RAT SnMF via the core network (CN), or Received from the first RAT SnMF via the first RAT RAN node; and The response to the RAN node's sensing capability request is configured to be provided to the first RATSnMF via the following: The CN, or The first RAT RAN node.

4. The second RAT RAN according to claim 3, wherein: The CN is the first RAT CN; or The CN is the second RAT CN.

5. The second RAT RAN of claim 1, wherein the one or more processors are further configured individually or in combination to: The sensing tunnel configuration, indicating the sensing purpose and the virtual first RATRAN node identifier, is received from the first RAT SnMF via the one or more transceivers.

6. The second RAT RAN according to claim 5, wherein: The sensing tunnel configuration is Received directly from the first RAT SnMF; Received from the first RAT SnMF via the core network (CN); Received from the first RAT SnMF via the first RAT RAN node; Or any combination thereof.

7. The second RAT RAN according to claim 6, wherein: The CN is the first RAT CN; or The CN is the second RAT CN.

8. The second RAT RAN of claim 5, wherein the one or more processors are further configured individually or in combination to: In response to receiving the sensing tunnel configuration, the first RAT sensing agent at the second RAT RAN node is activated; and Using the first RAT sensing agent at the second RAT RAN node, a response to the sensing tunnel configuration is provided to the first RAT SnMF based on the virtual first RAT RAN node identifier.

9. The second RAT RAN according to claim 8, wherein: The response to the sensing tunnel configuration is configured for Send directly to the first RAT SnMF; Send to the core network (CN) for forwarding to the first RAT SnMF; Send to the first RAT RAN node for forwarding to the first RAT SnMF; or Any combination of them.

10. The second RAT RAN of claim 5, wherein the one or more processors are further configured individually or in combination to: Based on the sensing tunnel configuration received by the second RAT RAN node, transmit the first RAT UE sensing configuration to the second RAT User Equipment (UE) via the one or more transceivers; and Based on the first RAT UE sensing configuration, sensing measurements are received from the second RAT UE via the one or more transceivers.

11. A second radio access technology (RAT) user equipment (UE), the second radio access technology (RAT) user equipment (UE) 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: Receive UE sensing capability requests from the first RAT sensing management function (SnMF) via the one or more transceivers; In response to receiving the UE sensing capability request, activate the first RAT user equipment (UE) sensing agent at the second RAT UE; The response to the UE sensing capability request is provided to the first RATSnMF based on a subset of the second RAT UE sensing capabilities determined by the first RAT UE sensing agent, wherein the subset of the second RAT UE sensing capabilities includes only sensing capabilities compatible with the first RAT SnMF. Receive UE sensing tunnel configuration indicating sensing purpose and virtual first RAT UE identifier via the one or more transceivers; as well as The first RAT UE sensing agent is used to respond to the UE sensing tunnel configuration.

12. The second RAT UE according to claim 11, wherein: The first RAT is fifth-generation (5G) radio access technology; and The second RAT is the sixth generation (6G) radio access technology.

13. The second RAT UE according to claim 11, wherein: The UE sensing capability request is received via the first RAT radio access network (RAN) node; and The response to the UE's sensing capability request is configured to be forwarded to the first RAT SnMF via the first RAT RAN node.

14. The second RAT UE according to claim 11, wherein: The UE sensing capability request is received via the first RAT UE; and The response to the UE's sensing capability request is configured to be forwarded to the first RAT SnMF via the first RAT UE.

15. A second radio access technology (RAT) sensing management function (SnMF), the second radio access technology (RAT) sensing management function (SnMF) 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 RAN node sensing capability request is transmitted to a first RAT radio access (RAN) node via the one or more transceivers, wherein the RAN node sensing capability request is limited to a subset of second RAT sensing capabilities, the subset of second RAT sensing capabilities including only sensing capabilities compatible with the first RAT RAN node; Receive RAN node sensing capability responses based on the subset of second RAT sensing capabilities from the first RAT RAN node via the one or more transceivers; Transmit a RAN node sensing tunnel configuration indicating the sensing purpose and a virtual first RAT RAN node identifier to the first RAT RAN node via the one or more transceivers; as well as Receive a RAN node sensing tunnel configuration response based on the sensing purpose and the virtual first RAT RAN node identifier from the first RAT RAN node via the one or more transceivers.

16. The second RAT SnMF according to claim 15, wherein: The RAN node sensing capability request is configured to be forwarded to the first RAT RAN node via the following: First RAT Core Network (CN) Second RAT CN, The second RAT RAN node, or Any combination of them.

17. A first radio access technology (RAT) user equipment (UE), the first radio access technology (RAT) user equipment (UE) 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: The UE sensing capability request is received from the second RAT sensing management function (SnMF) via the one or more transceivers, wherein the UE sensing capability request is limited to a subset of the second RAT UE sensing capabilities that are compatible with the first RAT UE; Provide the second RAT SnMF with a first response to the first RAT UE sensing capability request, wherein the first response is based on the subset of the second RAT UE sensing capabilities indicated by the UE sensing capability request; Receive UE sensing tunnel configuration compatible with the first RAT UE from the second RAT SnMF via the one or more transceivers; as well as The second response is provided to the second RAT SnMF based on the UE sensing tunnel configuration.

18. The first RAT UE according to claim 17, wherein: The first RAT is fifth-generation (5G) radio access technology; and The second RAT is the sixth generation (6G) radio access technology.

19. The first RAT UE according to claim 17, wherein: The first RAT UE sensing capability request is received from the second RAT SnMF via the second RAT radio access network (RAN) node; The first response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node; The UE sensing tunnel configuration is received from the second RAT SnMF via the second RAT RAN node; and The second response is configured to be forwarded to the second RAT SnMF via the second RAT RAN node.

20. The first RAT UE according to claim 17, wherein: The first RAT UE sensing capability request is received from the second RAT SnMF via the second RAT UE; The first response is configured to be forwarded to the second RAT SnMF via the second RAT UE; The UE sensing tunnel configuration is received from the second RAT SnMF via the second RAT UE; and The second response is configured to be forwarded to the second RAT SnMF via the second RAT UE.

Images