Network signaling to facilitate sensing measurements
A framework for configuring radio resources and facilitating sensing measurements in 5G networks addresses the lack of standardized protocols, enabling improved RAN resource control and UE measurement adaptability for enhanced sensing operations.
Patent Information
- Application Number
- PCT/IB2026/054532
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Current 5G networks lack standardized techniques or protocols for configuring network entities to perform and facilitate sensing measurements, which are essential for various use cases such as autonomous driving and 6G networks.
A framework is provided for configuring radio resources and facilitating sensing measurements by UEs, involving methods for receiving sensing measurement requests, determining UE configurations, and reporting measurements, while maintaining transparency and adjusting RAN node settings based on UE capabilities and RRM configurations.
This framework enables better control over RAN radio resources and facilitates improved sensing measurement configurations and reporting across different topologies, enhancing RAN functionality and UE measurement adaptability.
Smart Images

Figure IB2026054532_12112026_PF_FP_ABST
Abstract
Description
[0001] NETWORK SIGNALING TO FACILITATE SENSING MEASUREMENTS TECHNICAL FIELD
[0002] The present disclosure relates generally to wireless networks, and more specifically to signaling techniques and protocols for coordinating sensing measurements in radio access networks (RANs), such as sensing measurements performed by user equipment (UEs).
[0003] BACKGROUND
[0004] The fifth generation (“5G”) of cellular systems has been standardized within the Third-Generation Partnership Project (3 GPP). 5G was developed for maximum flexibility to support various use cases including enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), and device-to-device (D2D). 5G was initially specified in Release 15 (Rel-15) and continues to evolve through subsequent releases.
[0005] 3GPP standards provide various ways for positioning (e.g., determining the position of, locating, and / or determining the location of) user equipment (UEs) operating in 3GPP networks. In general, a positioning node configures a target device (e.g., UE) and / or a radio access network (RAN) node to perform one or more positioning measurements according to one or more positioning methods. For example, positioning measurements can include timing (and / or timing difference) measurements on UE, RAN, and / or satellite transmissions, such as RAN-transmitted positioning reference signals (PRS), The positioning measurements are used by the target device, the RAN node, and / or the positioning node to determine the location of the target device.
[0006] In general, UEs may communicate with a 5G network via a control plane (CP) and a user plane (UP). More specifically, a UE uses signaling radio bearers (SRBs) for CP communications and data radio bearers (DRBs) for UP communications. For example, SRBs may be used to carry various measurements made by a UE. As a more specific example, a UE may transmit positioning measurements using SRB2 and mobility-related measurements using SRB1. SRBs and DRBs differ in how they are configured on the radio interface between UE and 5G radio access network (RAN) as well as operations on the interface between RAN and 5G core network (5GC).
[0007] 3GPP TR 22.837 (vl9.4.0) specifies use cases and requirements for enhancement of the 5G system to provide sensing services that address various verticals and / or applications such as autonomous / assisted driving, vehicle-to-everything (V2X) communications, unmanned aerial vehicles (UAVs), three-dimensional (3D) map reconstruction, smart cities / homes / factories, healthcare, and maritime. In this context, the general goal of sensing is to detect and localize a target that is not necessarily connected to the network, such as a pedestrian, an animal, an object,etc. This integration of sensing into 5G (and later-generation) networks is often referred to as joint communications and sensing (JCAS) or Integrated Sensing and Communication (ISAC).
[0008] Sensing involves the network transmitting radio signals and receiving / measuring versions of those signals that have been reflected by the target (and possibly other surroundings). The transmitting and receiving can be performed by the same node(s) or by different node(s). Processing output of the sensing measurements yields information of the target and its surroundings that the radio signals interacted with, possibly including sources of attenuation, reflection, refraction, etc.
[0009] A sensing request may originate from applications internal or external to the network.
[0010] 3GPP has defined a Sensing Management Function (SeMF) to handle these requests and to trigger the necessary sensing operations in the RAN, including any UEs that have capability to assist with the sensing. SeMF is a logical entity that resides in the RAN (e.g., gNB) or in 5GC (e.g., a NF).
[0011] 3GPP has also defined sensing units (SUs, also called sensing entities) to perform radio signal transmission, reception, and / or measurement for sensing operations in the RAN. SUs can be standalone or integrated with another RAN node (including sharing of antennas). A sensing operation may involve multiple SUs, which are selected and configured by SeMF.
[0012] 3GPP has also defined a sensing processing function (SPF) to receive and process SU measurements to obtain one or more sensing results, which the SPF may provide to an SeMF. The SPF can be a separate entity, integrated in a network node (including SeMF), or distributed over multiple network nodes. Upon receiving results from SPF, the SeMF can provide them to the originator of the corresponding sensing request.
[0013] SUMMARY
[0014] Although sensing is being standardized for 5G networks (e.g., as part of “5G Advanced”), it is also expected that sensing will be a part of future 6G networks. As such, it is expected that sensing will be used for many different use cases in 5G and 6G networks. It is also expected that various types of “sensing function” may be used to control these operations, including but not limited to SPF and SeMF. Currently, however, there are no techniques or protocols specified that would enable a generic sensing function to configure different network entities to perform and / or facilitate sensing measurements, and to obtain the results of such measurements.
[0015] An object of embodiments of the present disclosure is to facilitate control and / or configuration of radio resources used for sensing operations, such as by providing and / or enabling solutions to exemplary problems summarized above and described in more detail below.
[0016] Embodiments include methods (e.g., procedures) performed by a RAN node configured to facilitate sensing measurements by UEs.These exemplary methods include receiving, from a sensing function (SF) in a core network coupled to the RAN, a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a UE to perform the required sensing measurements. These exemplary methods also include determining a UE sensing configuration based on the sensing measurement request. These exemplary methods also include sending the UE sensing configuration to the UE. These exemplary methods also include receiving from the UE a measurement report that includes the required sensing measurements.
[0017] In some embodiments, these exemplary methods also include receiving from the UE an indication of UE sensing capabilities. The UE sensing configuration is determined further based on the UE sensing capabilities. In some embodiments, these exemplary methods also include the following operations:
[0018] • receiving from the UE a transparent container that includes a UE location determined in conjunction with the sensing measurements; and
[0019] • forwarding the transparent container to the SF without decoding or otherwise processing the contents of the transparent container.
[0020] In some of these embodiments, the transparent container is received in the measurement report. In other of these embodiments, the transparent container is received in a different message than the measurement report.
[0021] In some embodiments, these exemplary methods also include sending to the SF a sensing configuration of the RAN node. The sensing measurement request is based on the sensing configuration of the RAN node, and the UE sensing configuration is determined further based on the sensing configuration of the RAN node. In some of these embodiments, the sensing configuration includes or indicates one or more of the following information related to reference signals (RS) transmitted by the RAN node for sensing measurements:
[0022] • type;
[0023] • time and / or frequency resources;
[0024] • carrier frequency;
[0025] • bandwidth or bandwidth combination;
[0026] • pulse duration;
[0027] • pulse periodicity or aperiodic configuration;
[0028] • comb configuration;
[0029] • muting pattern;
[0030] • cyclic prefix (CP) length;
[0031] • sub-carrier spacing (SCS);• number of sensing resources or resource sets; and
[0032] • time offset with respect to a reference time on the RAN node radio interface.
[0033] In some embodiments, these exemplary methods also include performing one or more of the following operations based on the measurement report:
[0034] • adjusting one or more operational settings of the RAN node based on one or more of the sensing measurements included in the measurement report; and
[0035] • forwarding the measurement report to the SF.
[0036] In some embodiments, the UE sensing configuration is determined further based on the UE’s current radio resource management (RRM) configuration. In other embodiments, the RAN node adjusts the UE’s current RRM configuration based on the UE sensing configuration, thereby obtaining an adjusted RRM configuration, which may be sent to the UE.
[0037] In some embodiments, the sensing measurements are based on first RS transmitted by the RAN node and second RS transmitted by a second RAN node. In such embodiments, these exemplary methods also include receiving from the second RAN node one or more observed time differences (OTDs) between the first RS and the second RS. The UE sensing configuration is determined further based on the received OTDs.
[0038] Other embodiments include exemplary methods (e.g., procedures) performed by a SF configured to operate in a core network coupled to a RAN. These embodiments are generally complementary to RAN node embodiments summarized above.
[0039] These exemplary methods include sending to a RAN node a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a UE to perform the required sensing measurements. These exemplary methods also include receiving from the RAN node a measurement report that includes the required sensing measurements performed by the UE.
[0040] In some embodiments, these exemplary methods also include receiving, from the UE via the RAN node, a transparent container that includes a UE location determined in conjunction with the sensing measurements. In some of these embodiments, the transparent container is received in the measurement report. In other of these embodiments, the transparent container is received in a different message than the measurement report.
[0041] In some embodiments, these exemplary methods also include receiving sensing configurations from one or more of the following: the RAN node, and a second RAN node. In such embodiments, the sensing measurement request is based on the received one or more sensing configuration. In some of these embodiments, these exemplary methods also include selecting at least one of the RAN node and the second RAN node to transmit RS for the sensing measurements. The selection is based on one or more of the following:• the sensing configurations of the RAN node and the second RAN node, • respective locations of transmission antenna associated with the RAN node and the second RAN node,
[0042] • a required sensing area, and
[0043] • a geometric dilution of precision (GDOP) requirement.
[0044] Other embodiments include methods (e.g., procedures) performed by a UE configured to support sensing measurements in a RAN. These embodiments are generally complementary to RAN node and SF embodiments summarized above.
[0045] These exemplary methods include receiving, from a RAN node, a UE sensing configuration that includes a list of sensing measurements to be performed. These exemplary methods also include performing the sensing measurements in accordance with the UE sensing configuration. The sensing measurements are performed on RS transmitted by one or more of the following: the RAN node, and a second RAN node. These exemplary methods also include sending to the RAN node a measurement report that includes the sensing measurements performed (or results thereof).
[0046] In some embodiments, these exemplary methods also include sending to the RAN node an indication of UE sensing capabilities. The UE sensing configuration is based on the UE sensing capabilities. In some embodiments, these exemplary method also include the following operations:
[0047] • determining a UE location in conjunction with the sensing measurements; and
[0048] • sending the UE location to a sensing function (SF) in a core network coupled to the RAN, wherein the UE location is sent via the RAN node in a transparent container.
[0049] In some of these embodiments, the transparent container is included with the measurement report. In other of these embodiments, the transparent container is sent in a different message than the measurement report.
[0050] The following features may apply to any of the embodiments summarized above.
[0051] In various embodiments, the sensing measurements include one or more of the following: one or more Doppler-related measurements, one or more carrier phase-related measurements, one or more timing-related measurements, one or more angular-related measurements, velocity, speed, direction, reference signal received power (RSRP), and reference signal received path power (RSRPP).
[0052] In various embodiments, the SF may be any of following: sensing management function (SeMF), sensing control function (SCF), sensing processing function (SPF), location management function (LMF), or access and mobility management function (AMF).Other embodiments, variants, and features of the exemplary methods summarized above are described herein. Other embodiments include UEs (e.g., wireless devices) and RAN nodes (e.g., base stations, eNBs, gNBs, ng-eNBs, CUs, DUs, etc.) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such UEs and RAN nodes to perform operations corresponding to any of the exemplary methods described herein.
[0053] These and other embodiments described herein may provide various benefits and / or advantages. For example, embodiments may provide a common framework for sensing measurement configuration and reporting that is applicable for all sensing topologies involving a UE and at least one RAN node. Moreover, embodiments may enable a UE’s serving RAN node to have better control over its radio resources, based on joint control of sensing measurement configurations and more general UE measurement configurations (e.g., for RRM). This is advantageous relative to conventional solutions that required adaptation by the UE based on sensing measurement configurations provided by the serving RAN node. At a high level, embodiments may facilitate improved RAN radio resource control and / or coexistence between sensing and other RAN functionality.
[0054] These and other objects, features, and advantages of embodiments of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.
[0055] BRIEF DESCRIPTION OF THE DRAWINGS
[0056] Figure 1 shows an exemplary 5G network architecture.
[0057] Figure 2 shows exemplary 5G user plane (UP) and control plane (CP) protocol stacks. Figure 3 shows an exemplary architecture for positioning in 5G networks.
[0058] Figure 4 shows various sensing techniques that can be used in a 5G network to detect and / or localize a target (e.g., pedestrian).
[0059] Figure 5 shows an exemplary architecture for IS AC and positioning in 5G networks. Figure 6 shows an exemplary architecture for ISAC in 5G and / or 6G networks.
[0060] Figure 7 shows a signaling diagram of a sensing procedure according to some embodiments of the present disclosure.
[0061] Figure 8 shows a signaling diagram of a sensing configuration procedure according to some embodiments of the present disclosure.
[0062] Figure 9 shows a signaling diagram of a multi-RAN node sensing procedure according to some embodiments of the present disclosure.Figure 10 shows a flow diagram of an exemplary method (e.g., procedure) for a RAN node, according to various embodiments of the present disclosure.
[0063] Figure 11 shows a flow diagram of an exemplary method (e.g., procedure) for a sensing function, according to various embodiments of the present disclosure.
[0064] Figure 12 shows a flow diagram of an exemplary method (e.g., procedure) for a UE, according to various embodiments of the present disclosure
[0065] Figures 13-14 show two example communication systems according to some embodiments of the present disclosure.
[0066] Figure 15 shows an example wireless device according to some embodiments of the present disclosure.
[0067] Figure 16 shows an example network node according to some embodiments of the present disclosure.
[0068] Figure 17 shows an example virtualization environment in which some embodiments of the present disclosure may be virtualized
[0069] DETAILED DESCRIPTION
[0070] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
[0071] In general, all terms used herein are to be interpreted according to their ordinary meaning to a person of ordinary skill in the relevant technical field, unless a different meaning is expressly defined and / or implied from the context of use. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise or clearly implied from the context of use. The operations of any methods and / or procedures disclosed herein do not have to be performed in the exact order disclosed, unless an operation is explicitly described as following or preceding another operation and / or where it is implicit that an operation must follow or precede another operation. Any feature of any embodiment disclosed herein can apply to any other disclosed embodiment, as appropriate. Likewise, any advantage of any embodiment described herein can apply to any other disclosed embodiment, as appropriate.
[0072] Furthermore, the following terms are used throughout the description given below:
[0073] • Radio Access Node: As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio accessnetwork (RAN) that operates to wirelessly transmit and / or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., gNB in a 5G / NR network or eNB in a LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point (TP), a transmission reception point (TRP), a remote radio unit (RRU or RRH), and a relay node.
[0074] • Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (EMF), or the like.
[0075] • Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Communicating wirelessly can involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information through air. Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”.
[0076] • Network Node: As used herein, a “network node” is any node that is either part of a radio access network (e.g., a radio access node or equivalent term) or of a core network (e.g., a core network node) of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or equipment in the cellular communications network, to enable and / or provide wireless access to the wireless device, and / or to perform other functions (e.g., administration) in the cellular communications network.
[0077] • Base station: As used herein, a “base station” may comprise a physical or a logical node transmitting or controlling the transmission of radio signals, e.g., eNB, gNB, ng-eNB, en- gNB, centralized unit (CU) / distributed unit (DU), transmitting radio network node, transmission point (TP), transmission reception point (TRP), remote radio head (RRH), remote radio unit (RRU), Distributed Antenna System (DAS), relay, etc.• Node: As used herein, the term “node” (without prefix) can be any type of node that can operate in or with a wireless network (including RAN and / or core network), including a radio access node (or equivalent term), core network node, or wireless device. However, the term “node” may be limited to a particular type (e.g., radio access node) based on its specific characteristics in any given context.
[0078] The above definitions are not meant to be exclusive. In other words, various ones of the above terms may be explained and / or described elsewhere in the present disclosure using the same or similar terminology. Nevertheless, to the extent that such other explanations and / or descriptions conflict with the above definitions, the above definitions should control.
[0079] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. Furthermore, although the term “cell” is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.
[0080] Figure 1 shows an exemplary 5G network architecture, consisting of a Next Generation Radio Access Network (NG-RAN, 199) and a 5G Core Network (5GC, 198). As shown in the figure, the NG-RAN can include gNBs (e.g., 110a,b) and ng-eNBs (e.g., 120a, b) that are interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected via NG interfaces to the 5GC, more specifically to access and mobility management functions (AMFs, e.g., 130a,b) via respective NG-C interfaces and to user plane functions (UPFs, e.g., 140a, b) via respective NG-U interfaces. Moreover, the AMFs can communicate with one or more policy control functions (PCFs, e.g., 150a, b) and network exposure functions (NEFs, e.g., 160a,b) in the 5GC.
[0081] The radio technology for the NG-RAN is often referred to as “New Radio” (NR). Each of the gNBs can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. Each of ng-eNBs can support the fourth generation (4G) Long-Term Evolution (LTE) radio interface. Each of the gNBs and ng-eNBs can serve a geographic coverage area including one or more cells (e.g., llla-b and 121a-b). Depending on the cell in which it is located, a user equipment (UE, e.g., 105) can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively. Although Figure 1 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both LTE and NR functionality.
[0082] NG RAN logical nodes (e.g., gNBs HOa-b) may include a Central Unit (CU) and one or more Distributed Units (DUs). CUs are logical nodes that host higher-layer protocols and performvarious gNB functions such controlling the operation of DUs. DUs are decentralized logical nodes that host lower layer protocols and can include, depending on the functional split option, various subsets of the gNB functions. A CU connects to one or more associated DUs over respective Fl logical interfaces. Each CU and DU can include various circuitry needed to perform their respective functions, including processing circuitry, communication interface circuitry (e.g., transceivers), and power supply circuitry.
[0083] Figure 2 shows exemplary 5G user plane (UP) and control plane (CP) protocol stacks between a UE (210), a gNB (220), and an AMF (230), such as those shown in Figure 1. The Physical (PHY), Medium Access Control (MAC), Radio Eink Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP. PDCP provides ciphering / deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP. In addition, PDCP provides header compression and retransmission for UP data.
[0084] On the UP side, Internet protocol (IP) packets arrive to PDCP as service data units (SDUs), and PDCP creates protocol data units (PDUs) to deliver to RLC. The Service Data Adaptation Protocol (SDAP) layer handles quality-of-service (QoS) including mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow identifiers (QFI) in UL and DL packets.
[0085] When each IP packet arrives, PDCP starts a discard timer. When this timer expires, PDCP discards the associated SDU and the corresponding PDU. If the PDU was delivered to RLC, PDCP also indicates the discard to RLC. The RLC layer transfers PDCP PDUs to the MAC through logical channels (LCH). RLC provides error detection / correction, concatenation, segmentation / reassembly, sequence numbering, reordering of data transferred to / from the upper layers. If RLC receives a discard indication from associated with a PDCP PDU, it will discard the corresponding RLC SDU (or any segment thereof) if it has not been sent to lower layers.
[0086] MAC provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (in gNB). PHY provides transport channel services to MAC and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.
[0087] On the CP side, the non-access stratum (NAS) layer between UE and AMF handles UE / gNB authentication, mobility management, and security control. RRC sits below NAS in the UE but terminates in the gNB rather than the AMF. RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN. RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs. Additionally, RRCcontrols addition, modification, and release of carrier aggregation (CA) and dual-connectivity (DC) configurations for UEs, and performs various security functions such as key management.
[0088] After a UE is powered ON it will be in the RRC...IDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC_CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC_IDLE after the connection with the network is released. In RRC..IDLE state, the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers. During DRX active periods (also referred to as “DRX On durations”), an RRC_IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB. An NR UE in RRC...IDLE state is not known to the gNB serving the cell where the UE is camping. However, NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB.
[0089] In addition to providing coverage via cells as in LTE, gNBs also provide coverage via “beams.” In general, a downlink (DL, i.e., network to UE) “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE. In NR, for example, RS can include any of the following: synchronization signal / PBCH block (SSB), channel state information RS (CSI-RS), tertiary reference signals (or any other sync signal), positioning RS (PRS), demodulation RS (DMRS), phase-tracking reference signals (PTRS), etc. In general, SSB is available to all UEs regardless of the state of their connection with the network, while other RS (e.g., CSI-RS, DM-RS, PTRS) are associated with specific UEs that have a network connection.
[0090] Conventionally, UEs measure various DL RS (e.g., SSB, CSI-RS) to obtain link quality measurements and report these measurements to the RAN via RRC messages (e.g., MeasurementReport). For example, the UE may report link quality measurements in terms of RS received power (RSRP), RS received quality (RSRQ), signal-to-interference-and-noise ratio (SINR), etc. The RAN uses these UE measurements for initiating UE mobility procedures such as handover. As such, these measurements are often considered mobility-related.
[0091] Figure 3 shows an exemplary architecture for positioning in 5G networks. NG-RAN (320) can include nodes such as gNBs (e.g., 322) and ng-eNBs (e.g., 321). Each ng-eNB may control one or more transmission points (TPs), such as remote radio heads. Similarly, each gNB may control one or more transmission / reception points (TRPs).
[0092] In addition, the NG-RAN nodes communicate with an AMF (330) in the 5GC via respective NG-C interfaces, while the AMF communicates with a location management function (LMF, 340) via an NLs interface. The LMF supports various functions related to UE positioning, including location determination for a UE, obtaining DL location measurements or a locationestimate from the UE, obtaining UL location measurements from the NG RAN, and obtaining non-UE associated assistance data from the NG RAN.
[0093] In addition, positioning-related communication between UEs (e.g., 210) and NG-RAN nodes occurs via the RRC protocol, while positioning -related communication between NG-RAN nodes and LMF occurs via an NRPPa protocol. Optionally, the LMF can also communicate with an enhanced serving mobile location center (E-SMLC, 350) and a secure user plane location platform (SLP, 360) in an LTE network.
[0094] In a typical operation, the AMF can receive a request for a location service associated with a particular target UE from another entity (e.g., a gateway mobile location center, GMEC), or the AMF can initiate a location service on behalf of a particular target UE (e.g., for an emergency call by the UE). The AMF then sends a location services (LS) request to the LMF. The LMF processes the LS request, which may include transferring assistance data to the target UE to assist with UE-based and / or UE-assisted positioning; and / or positioning of the target UE. The LMF then returns the result of the LS (e.g., a position estimate for the UE and / or an indication of any assistance data transferred to the UE) to the AMF or to another entity (e.g., GMLC) that requested the LS.
[0095] 3GPP TR 22.837 (vl9.4.0) specifies use cases and requirements for enhancement of the 5G system to provide sensing services that address various verticals and / or applications such as autonomous / assisted driving, V2X communications, UAVs, 3D map reconstruction, smart cities / homes / factories, healthcare, and maritime. In this context, the general goal of sensing is to detect and localize a target that is not necessarily connected to the network, such as a pedestrian, an animal, an object, etc. This integration of sensing into 5G (and later-generation) networks is often referred to as joint communications and sensing (JCAS) or Integrated Sensing and Communication (ISAC).
[0096] Sensing involves the network transmitting radio signals and receiving / measuring versions of those signals that have been reflected by the target (and possibly other surroundings). The transmitting and receiving can be performed by the same node(s) or by different node(s). In general, a goal is to detect and localize a non-connected and / or passive target such as a pedestrian, animal, object, etc. However, sensing targets may include connected UEs such that sensing can be used to improve communication-based positioning of such UEs.
[0097] Figure 4 illustrates various sensing techniques that can be used in a 5G network to detect and / or localize a target (e.g., pedestrian). In the upper left, mono-static sensing involves the same node (or antenna) transmitting the sensing signals and receiving / measuring the versions reflected by the target. In the upper right, a first type of bi-static sensing involves a first RAN node transmitting the sensing signals and a second RAN node at a different location receiving / measuring the reflected versions. In the bottom left, a second type of bi-static sensinginvolves a RAN node transmitting the sensing signals and a UE (or SU) at a different location receiving / measuring the reflected versions. In the bottom right, a third type of bi-static sensing involves a UE (or SU) transmitting the sensing signals and a RAN node at a different location receiving / measuring the reflected versions. Although not shown in Figure 4, multi-static sensing involves multiple nodes at different locations transmitting sensing signals and multiple nodes at different locations receiving / measuring the reflected versions.
[0098] In any of these cases, the receiver may perform one or more of the following sensing measurements on the received sensing signals:
[0099] • Timing measurement (e.g., round-trip time, TOA, Rx-Tx time difference, etc.) of the signal (time when signal was sent + time when the reflected signal was received by the sender)
[0100] • Signal strength, signal quality, signal-to-noise ratio, etc.
[0101] • Phase measurement;
[0102] • Channel impulse response, multipath characteristics, power delay profile;
[0103] • Delay spread, Doppler spectra, Doppler spread, Doppler shift, Doppler frequency;
[0104] • Velocity, angle of arrival, angle of departure; and
[0105] • Samples of “raw” radio signal values, e.g., in-phase (I) and quadrature (Q) representation. These various measurements can be processed to obtain information about the target and its surroundings that affected the transmitted sensing signals, including one or more of the following:
[0106] • Characteristics (shape, size, number, etc.) of target and / or obstacles ;
[0107] • Velocity of target and / or obstacles;
[0108] • Weather conditions (e.g., rain);
[0109] • Recognition of objects (e.g., wall, blocker, scatterer, etc.).
[0110] As mentioned above, a sensing target may be a passive object that is unable to communicate with the 5G network but whose presence / position / characteristic needs to be determined. In most cases, the passive object is moving or at least is able to move, such as when the passive object is a vehicle without subscriber identity module (SIM), a person without a UE, an animal, etc. Movement of the passive object enables it to be differentiated from other static objects in the same environment such as walls, buildings, structures, etc.
[0111] A sensing request may originate from applications internal or external to the network.
[0112] 3GPP has defined a Sensing Management Function (SeMF) to handle these requests and to trigger the necessary sensing operations in the RAN, including any UEs that have capability to assist with the sensing. SeMF is a logical entity that can be a separate network entity, integrated in a RAN node (e.g., gNB) or a CN node or function (e.g., LMF, UPF, etc.), or distributed over multiplenetwork nodes. SeMF may be split into CP and UP parts, e.g., SeMF-C and SeMF-U. SeMF may also be split hierarchically in a similar manner as gNBs, e.g., into SeMF-CU and multiple SeMF-DUs.
[0113] 3GPP has also defined SUs (or sensing entities) to perform radio signal transmission, reception, and / or measurement for sensing operations in the RAN. SUs can be standalone or integrated with another UE or RAN node (including sharing of antennas). Multiple SUs with the same or different capabilities may be involved in a sensing session, although not all of these SUs need to use the same radio access technology (RAT). For example, a first SU can receive radio signals for sensing from N1 transmitting SUs in a first RAT (NI=0, 1, 2, ...) and from N2 transmitting SUs a second RAT (N 1 =0. 1, 2, ...). In other words, an SU can be capable of receiving and / or transmitting in multiple different RATs (“muIti-RAT”) with or without being served by any of the multiple RATs.
[0114] SUs involved in a sensing session may need to be selected and / or configured by a controlling entity, such as SeMF, a CN node / function, a RAN node / function, a UE, an SU-CU (controlling one or more SU-DUs), etc. For example, a controlling SeMF may be deployed in the same or different network as all or some of the SUs that provide sensing results for a sensing session. As a more specific example, one or more SUs may be in a 5G network while the associated SeMF is in a 6G network (or vice versa).
[0115] As another operational example, SeMF can be a sensing server that sends to the RAN a request to trigger a sensing session, sensing measurements, etc. The sensing session is configured based at least on sensing task, sensing target information (e.g., object type, weather condition, etc.), and / or sensing area information (e.g., forest, indoor factory, house, area size, etc.). The SeMF may select a set of SUs to perform sensing measurements, which may include RF sensors and non-RF sensors (e.g., cameras, motion sensors, heat sensors, etc.). Example measurements include raw samples, radio measurements, timing measurements, velocity, temperature, sensing event indication such as weather change or motion pattern change, etc.
[0116] 3GPP has also defined a sensing processing function (SPF) to receive and process SU measurements to obtain one or more sensing results, which the SPF may provide to an SeMF. Upon receiving results from SPF, the SeMF can send them to an originator of the corresponding sensing request. SPF may also send the processed sensing result(s) to another function or node.
[0117] SPF may be a separate network entity, integrated in a RAN node (e.g., gNB) or a CN node or function (e.g., SeMF, LMF, etc.), or distributed over multiple network nodes. SPF may be split into CP and UP parts, e.g., SPF-C and SPF-U. SPF may also be split hierarchically in a similar manner as gNBs, e.g., into SPF-CU and multiple SPF-DUs. SPF (or a portion thereof) may even be part of a UE (e.g., a measuring SU) or distributed across multiple UEs.Likewise, SeMF may be implemented in a single node or distributed over multiple nodes (e.g., different nodes hosting SeMFl, SeMF2, etc.). SeMF may also be deployed as part of the network’s control plane (CP) or user plane (UP, also referred to as data plane). SeMF may also be implemented with split or hierarchical functionality, such as an SeMF-CU that controls one or more SeMF-DUs (e.g., like gNBs shown in Figure 1).
[0118] Figure 5 shows an exemplary architecture for IS AC and positioning in 5G networks. In particular, Figure 5 shows an example of how SeMF (530), SPF (540), and SUs (511) defined for sensing operations may be integrated into the exemplary 5G positioning architecture shown in Figure 3. In the ISAC architecture shown in Figure 5, each of gNB (522), ng-eNB (521), and UE (510) includes an optional SU (511, respectively 511a, 511b, and 511c). In addition, SeMF (530) communications with the LMF (550) via a Cl interface, with the AMF (560) via a C2 interface, and with SPF (540) via an 12 interface. In addition, the SPF communicates with NG-RAN (520) via an II interface.
[0119] Although not shown in Figure 5, the ISAC architecture in 5G / NR networks may also include one or more synchronization reference units (SRUs). Each SRU has access to an absolute synchronization source (e.g., GNSS) and can be used as a synchronization source for other nodes. For example, an SRU can be (or be included in) a RAN node (e.g., gNB) or a UE.
[0120] Figure 6 shows an exemplary architecture for ISAC in 5G and / or 6G networks. In this architecture, sensing starts with an application sending a sensing request over the control plane (CP) to a request function, which verifies that the requesting application is authorized before forwarding the request to the correct sensing control function (SCF, 631). This function indirectly configures measurement nodes - including Tx and Rx base stations (BSs) and UEs - and an SPF (632) via CP. After measurements have been performed, results are sent to the SPF (632) via the data plane (DP), which is separate from the UP. Note that CP and DP separation enables building each with the right technology and capacity. Note that the SCF and the SPF are part of the SeMF (630) in this exemplary architecture.
[0121] When a UE is involved in sensing, the UE needs to be connected to the network via a serving BS (e.g., gNB). Even though this serving BS is shown as a separate node in Figure 6, it may be co-located with either the Tx BS or the Rx BS mentioned above.
[0122] In the architecture shown in Figure 6, sensing measurements are sent to the SPF for processing. In most cases the SPF interprets sensing measurements based on applying the geometry of the involved nodes and possible other information about the surroundings, such as a 3D map of terrain and / or structures. The SCF provides this interpretation in a format meaningful to an external receiver, i.e., it answers the “question” in the sensing request. Sensor fusioninformation would also be handled by the SPF. There also may be use cases where raw data, measurements, reported events, etc. are forwarded to an external processing unit.
[0123] Although sensing is being standardized for 5G networks (e.g., as part of “5G Advanced”), it is also expected that sensing will be a part of future 6G networks. Moreover, it is expected that sensing will be used for many different purposes and use cases in 5G and 6G networks. For example, sensing may be used to facilitate determination of most efficient beam projections to be used in the RAN. As another example, sensing may be used for detection and / or continuous tracking of objects. These different use cases may require monostatic sensing, bistatic sensing, multi-static sensing, or even a combination thereof.
[0124] It is also expected that various types of “sensing functions” may be used to control the sensing operations for these various use cases. For example, sensing functions may include sensing-specific NFs such as SPF, SCF, and SeMF, as well as non-sensing-specific NFs such as LMF and AMF. Currently, however, there are no techniques or protocols specified that would enable such sensing functions to configure different network entities - including RAN nodes, UEs, and SUs - to perform and / or facilitate sensing measurements needed for these various use cases.
[0125] Embodiments of the present disclosure address these and other problems, issues, and / or difficulties by novel and inventive techniques for a sensing function to obtain sensing configuration information from RAN nodes and to provide such configuration to other RAN nodes and UEs, along with other related information such as sensing quality-of-service (QoS) requirements, list of measurements, response time requirements, etc. In some embodiments, a UE’s serving RAN node may determine the actual sensing configuration to be provided to the UE, based on the configuration information received from the sensing function. In some embodiments, the serving RAN node may configure the UE with radio bearer(s) that enable the UE to separately provide sensitive information only to the sensing function (e.g., in a container transparent to the intermediate serving RAN node) and non-sensitive information that may be decoded and / or processed by the serving RAN node.
[0126] Embodiments described herein may be applicable to wireless integrated sensing and communication (ISAC) networks, such as in conjunction with 5G and / or 6G networks.
[0127] Embodiments may provide various benefits and / or advantages. For example, embodiments may provide a common framework for sensing measurement configuration and reporting that is applicable for all sensing topologies involving a UE and at least one RAN node. Moreover, embodiments may enable a UE’s serving RAN node to have better control over its radio resources, based on joint control of sensing measurement configurations and more general UE measurement configurations (e.g., for RRM). This is advantageous relative to conventional solutions that required adaptation by the UE based on sensing measurement configurationsprovided by the serving RAN node (e.g., gap request procedure in 5G / NR positioning). At a high level, embodiments may facilitate better RAN radio resource control as well as coexistence between sensing and other RAN functionality.
[0128] In the following description, the term “sensing measurements” may be used to refer to radio measurements configured and performed for a sensing purpose or task, such as to detect, locate, track, recognize, or determine characteristics of a sensing target (defined below). Some example sensing measurements related to Doppler frequency include the following:
[0129] • Doppler estimate: estimate of any Doppler characteristic, e.g., frequency shift, velocity, acceleration, etc.
[0130] • Doppler Frequency, Doppler effect, frequency shift, Doppler shift: change in received signal frequency that a receiver SU observes from signals received via reflections of the presumed sensing target, the change being due to motion of the sensing target, signal transmitter, and / or signal receiver.
[0131] • Micro -Doppler: due to micro-scale (or secondary) movements of a sensing target, such rotating blades of a unmanned aerial vehicle (UAV, e.g., drone), swinging arms of a person walking, etc. These micro-scale movements produce secondary Doppler shifts, referred to as micro-Doppler effects or Jet Engine Modulation (JEM).
[0132] • Doppler Velocity: speed (m / s) at which the signal wave / frequency of a sensing target is received by an SU. Positive value implies object moving towards SU while negative value implies object moving away from SU.
[0133] • Doppler Acceleration: The rate of change of doppler velocity (m / s2).
[0134] Other example sensing measurements include direction or velocity estimation for a sensing target, state for a sensing target, angle of arrival, angle of departure, RS received power (RSRP), RS received path power (RSRPP), carrier phase, carrier phase difference, timing measurements (e.g., RSTD, ToA, Rx-Tx, RTT, etc.), channel impulse response, radar cross section (RCS), etc.
[0135] In the following description, the term “sensing unit” (or SU) may have a meaning according to its definition and / or characteristics in relevant 3GPP specifications. For example, an SU may be a radio node capable of reception and / or transmission of radio signals used for sensing and, in some cases, performing sensing measurements on received radio signals. Example SU radio nodes include UEs, TRPs, TPs, gNBs, etc. An SU may include a sensing TX unit (SU-TX) and / or a sensing RX unit (SU-RX), and may support measurements of signals associated with one or more RATs. Sensing measurements may be performed by an SU-RX, which may use them to obtain a sensing result and / or provide them to another function (e.g., SeMF) for similar purposes. In some cases, SU and SU-RX may be used interchangeably.In the following description, the term “sensing target” may refer to an object of a sensing task or session. A sensing target may be a passive object, an object not connected to a communication network, an object in an idle or inactive state with respect to the communication network, or an object for which connectivity to the communication network is unnecessary for the sensing task or session.
[0136] In the following description, the term “sensing task” may refer to a set of procedures and / or actions used to obtain a sensing result based on sensing measurements of radio signals that have been affected by a sensing target. Example sensing tasks include detection of target presence or absence; target localization; determining or classifying target characteristics such as size, dimensions, material, shape, type (human / non-human / inanimate), age, movement; gesture detection / recognition; determining target state; etc.
[0137] In the following description, the term “target state” (or more simply, “state”) may refer to characteristics of a sensing target such as orientation, speed / velocity (including moving / non-moving), acceleration, movement direction, movement pattern, absolute or relative location (2D / 3D), absolute or relative height, etc. Relative characteristics may be with respect to a reference characteristic (e.g., location or height).
[0138] In the following description, the term “sensing signal” (or “radio signal” used for sensing) may refer to any radio signal transmitted in a communications network that may be configured and / or used for sensing measurements. Sensing signals may be radio signals designed and / or intended specifically for sensing or radio signals designed and / or intended for other purposes but also used for sensing measurements. Example sensing signals may include sensing RS (SeRS), positioning RS (PRS), sensing and positioning RS (SPRS), CSI-RS, SRS, tracking RS (TRS), SSB, synchronization signals, common RS, cell RS (CRS), beam RS, and physical control / data channels (e.g., PRACH, PDSCH, PUSCH, etc.). For example, an SPRS may have the same configuration for sensing measurements and positioning measurements, or different configurations for these two purposes. SPRS characteristics that may differ include sequence, RS type, sequence ID, carrier frequency, bandwidth, periodicity, sub-carrier spacing (SCS), number of transmissions or measurement occasions, number of repetitions, comb size, resource element pattern, time and / or frequency domain, etc.
[0139] In the following description, the term “sensing data” may refer to sensing measurements, raw (unprocessed) sensing data, results of sensing measurement processing, etc.
[0140] Figure 7 shows a signaling diagram of a sensing procedure according to some embodiments of the present disclosure. The procedure is between a UE (710), the UE’s serving RAN node (720), and a sensing function (SF, 730) in a core network (e.g., 5GC) coupled to the RAN. Although the operations shown in Figure 7 are given numerical labels, this is done tofacilitate the following explanation rather than to require or imply any particular operational order, unless expressly stated otherwise.
[0141] Although not shown, as a preparatory operation, the serving RAN node may send the SF a list of sensing measurements that it supports (or are supported by TRPs associated with the serving RAN node). This may be necessary if some types of measurements are not mandatory for all RAN nodes / TRPs. In some variants, the SF may request this information from the serving RAN node.
[0142] In operation 1 , the SF sends a sensing session configuration to the serving RAN node. The sensing session configuration may also be referred to as a sensing measurement request. This configuration may identify the UE as a sensing target and may include a list of sensing measurements required or requested for the sensing session. For example, the list of sensing measurements may include any of the sensing measurements mentioned above. In some embodiments, the configuration may also indicate a granularity or resolution required for one or more of the sensing measurements. This granularity or resolution may be indicated in the appropriate units of a particular sensing measurement (e.g., degrees, m, m / s, Hz, etc.).
[0143] In some embodiments, the configuration may also indicate a response time requirement, e.g., a maximum duration of the sensing measurements and / or a time by which the sensing measurements should be received by the SF or by the serving RAN node. The response time requirement may be configured by the SF based on an expected delay or latency associated with the sensing measurements and / or with an application requirement for the sensing session, and this value is configured based upon latency requirements for the sensing session. The response time requirement may be given in relevant time units (e.g., ms) or as an index to an entry in a predetermined list of response time requirements.
[0144] In some embodiments, the SF may include in the sensing session configuration respective sensing configurations for one or more neighbor RAN nodes. This information may be include, for example, when the UE needs to perform sensing measurements on SeRS transmitted by the neighbor RAN node(s) - or vice versa - during the sensing session. These sensing configuration may include SeRS transmission configurations (for UE sensing measurements) and / or UL RS measurement configurations (for RAN node sensing measurements). As one alternative, the SF may provide this information to the serving RAN node in a separate message from the sensing session configuration. As another alternative, the SF may provide these configurations to the UE directly.
[0145] In operation 2, the serving RAN node determines a UE sensing configuration based on the sensing session configuration received in operation 1 and based on relevant UE capabilities, whichmay have been previously obtained by the serving RAN node. The UE sensing configuration determined by the serving RAN node may include one or more of the following:
[0146] • list of cells, beams, and / or TRPs to be measured,
[0147] • TRP antenna panel configurations, and
[0148] • measurement configuration (including granularity, bandwidth, etc.),
[0149] • SeRS transmission configuration (including any muting),
[0150] • QoS requirements (including response time), and
[0151] • measurement assistance data, e.g., expected location, expected measurement value, expected time difference of arrival (may be used to remove measurement outliers), etc. In some variants, UE sensing configuration may also be based on radio channel conditions between UE and serving RAN node. These may be known by the serving RAN node based on radio resource management (RRM) measurements received from the UE. For example, in poor radio channel conditions, the measurement configuration may need to specify more measurement samples and / or a larger measurement bandwidth.
[0152] In some embodiments, the serving RAN node may also configure or adapt other UE configurations in conjunction with the determined UE sensing configuration. For example, the serving RAN node may adapt one or more of the following UE RRM configurations for coexistence or cooperation with the UE sensing measurements:
[0153] • measurement gap configuration, e.g., measurement gap type (per-UE or per-FR), offset, length, periodicity, timing advance, etc., which enables the UE to receive SeRS during measurement gaps;
[0154] • active bandwidth part (BWP) configuration, e.g., to include SeRS to be measured; and • discontinuous reception (DRX) configuration, e.g., offset, cycle length, On duration, etc., so that the UE is not in DRX Off state during transmission of SeRS to be measured. Embodiments of the present disclosure facilitate these types of adaptations because both the UE sensing (e.g., SeRS measurement) configurations and UE RRM configurations are under control of the serving RAN node. Unlike conventional techniques, embodiments avoid the need to request the UE to perform RRM adaptations, such as for 5G / NR positioning measurements.
[0155] In some embodiments, the serving RAN node may also determine whether UE location is needed in conjunction with the sensing measurements. For example, stationary and operator-deployed UEs (e.g., as SUs) may not need to report their known locations in conjunction with sensing measurements performed. In some variants, if UE location is needed, the serving RAN node may indicate that the UE location can be sent separately from the sensing measurements, as discussed in more detail below.In operation 3, the serving RAN node sends the determined UE sensing configuration to the UE, such as by RRC signaling. In operation 4, the UE sends the serving RAN node a measurement report including the requested sensing measurements, such as via RRC signaling. The measurement report may include any of the sensing measurements mentioned above, in accordance with the sensing configuration and / or the sensing session configuration. In some embodiments, the measurement report may also include an indication of the UE’s antenna configuration (e.g., single antenna or multiple antennas) used for the sensing measurements and / or an estimate of quality and / or accuracy of the sensing measurements.
[0156] Although not shown in Figure 7, the serving RAN node may utilize the reported measurements for its own operational tasks such as beam management (e.g., beam shaping, beam selection), UE mobility management, or radio resource optimization, etc. In some variants, the serving RAN node may forward some or all of the information in the UE’s measurement report to the SF, either in received form or after further processing by the serving RAN node.
[0157] In operation 5, the UE sends its location to the SF via the serving RAN node, but in a sensitive information container that is transparent to the serving RAN node. In other words, the serving RAN node forwards the container to the SF without decoding or otherwise processing it. As an example, the container may be an RRC information element (IE) specified by the following ASN.l data structure:
[0158] UEMeasurementReportForSensing : : = SEQUENCE {
[0159] measurement Report Measurement Rpeort measurementReportForSF OCTET STRING
[0160] }
[0161] Figure 8 shows a signaling diagram of a sensing configuration procedure according to some embodiments of the present disclosure. The procedure in Figure 8 is between a RAN node and a SF in a core network (e.g., 5GC) coupled to the RAN. The SF has information about SeRS utilization in the RAN (e.g., based on the active measurement configurations) and provides this information to the RAN node in an SeRS utilization report. For example, the report may indicate which TRPs are being used for sensing measurements (e.g., have been configured to transmit SeRS for sensing measurements) and optionally which TRPs are not being used for sensing measurements (e.g., have not been configured to transmit SeRS for sensing measurements).
[0162] Figure 9 shows a signaling diagram of another sensing procedure according to other embodiments of the present disclosure. The procedure is between a UE (910), a first RAN node (920) operating as the UE’s serving RAN node, a sensing function (SF, 930) in a core network (e.g., 5GC) coupled to the RAN, and a second RAN node (740) that does not serve the UE. Although the operations shown in Figure 9 are given numerical labels, this is done to facilitate the following explanation rather than to require or imply any particular operational order, unless expressly stated otherwise.In operation 1, both the first and second RAN nodes provide their current sensing configurations to the SF. This may be done via any appropriate interface between the RAN nodes and the SF. The SF may collect this information periodically from the RAN nodes. Alternately, the SF can obtain the sensing configurations for the respective RAN nodes via an operations / administration / maintenance (OAM) function that is coupled to the CN and the RAN. Each RAN node’s sensing configuration may include or indicate one or more of the following information:
[0163] • Reference signal type (e.g., sensing-specific or communication-related);
[0164] • Time and / or frequency resources used;
[0165] • Carrier frequency used (e.g., ARFCN);
[0166] • Bandwidth or bandwidth combination (e.g., for bandwidth aggregation);
[0167] • Pulse duration;
[0168] • Pulse periodicity (or aperiodic / semi-persistent configuration);
[0169] • Comb configuration;
[0170] • Muting pattern (if pre-configured);
[0171] • Cyclic prefix (CP) length;
[0172] • Sub-carrier spacing (SCS);
[0173] • Number of sensing resources or resource sets (e.g., cells, beams, antenna panels, TRPs, etc.); and
[0174] • Time offset with respect to reference time (e.g., SeRS starts with offset of X frames, Y subframes, Z slots, and / or W symbols relative to beginning of SFNO).
[0175] In some variants, the RAN node’s sensing configuration may indicate one or more of the abovelisted information by an index to, or identifier of, a predetermined set of parameters.
[0176] Based on the sensing configurations received, the SF prepares an SeRS muting configuration (or pattern) in order to mitigate interference with required sensing measurements. For example, the SF determines or selects the RAN nodes (or their associated TRPs) that will be involved in a sensing operations, which may be based upon a required sensing area and the known locations of the RAN nodes (specifically their antennas / TRPs). In particular, the RAN nodes (or TRPs) may be selected based on their inclusion in, proximity to, or coverage of the required sensing area. Other selection considerations may include having the measurements performed from various positions that collectively have a relatively small geometric dilution of precision (GDOP).
[0177] Specifically, in operation 2, the SF selects the (non-serving) second RAN node for sensing based on sensing area requirements and / or GDOP considerations. For example, if the sensing areais large, multi-static sensing involving multiple RAN nodes may be needed. The SF prepares a muting configuration for the second RAN node. If the second RAN node provided a muting pattern in operation 1, the SF takes that into account. For example, the SF creates a sensing configuration from TRPs with non-overlapping muting patterns to avoid SeRS being muted in all measured TRPs in the same UE measurement occasion.
[0178] In operation 3a, the SF sends the determined muting configuration to the second RAN node. In operation 3b the SF also sends the neighbor sensing configuration for the second RAN node to the non-selected first RAN node.
[0179] In operation 4, the SF sends a sensing measurement request to the first RAN node, indicating that sensing measurements by the UE are required. The sensing measurement request may identify the requested or required sensing measurements, such as any of the sensing measurements discussed above. The sensing measurement request may also indicate one or more QoS requirements for the sensing measurements, such as the response time mentioned above.
[0180] In operation 5, the first RAN node obtains sensing capabilities of the UE, such as by using request / response signaling. Note that operation 5 may be performed in response to or prior to receiving the sensing measurement request in operation 4. Alternately, the first RAN may obtain the UE’s sensing capabilities from the SF or another NF in the CN (e.g., AMF), if available.
[0181] In operation 6, the first RAN node determines the actual sensing configuration to be used for the requested sensing measurements, based on the information in the sensing measurement request, the neighbor sensing configuration, and the UE sensing capabilities. The determined sensing configuration may include values for any of the parameters in the configuration provided to the SF in operation 1 , such as bandwidth, periodicity, etc.
[0182] In determining the sensing configuration to be used, the first RAN node may also consider any timing misalignment between itself and the second RAN node, since the UE may not be aware of the second RAN node’s timing. Although not shown, the first RAN may need to obtain an observed time difference (OTD) between itself and the second RAN node before configuring UE sensing measurements. In some embodiments, the first and second RAN nodes may exchange information relevant to the sensing measurements via an interface (e.g., Xn) between them. For example, the first and second RAN nodes may send each other information about OTD between their own transmissions and the received transmissions of the other RAN node.
[0183] In operation 7a, the first RAN node sends this sensing configuration to the UE, e.g., via unicast RRC signaling. In some embodiments, the first RAN node may also determine or adapt other UE configurations in conjunction with the determined sensing configuration. For example, the serving RAN node may adapt one or more UE RRM configurations, such as discussed above.In this case, the first RAN node may include or indicate these adapted configurations to the UE along with sensing configuration in operation 7a.
[0184] As an alternative in operation 7a, the first RAN node sends to the UE an indication to use a previously configured sensing configuration. For example, multiple candidate sensing configurations may have been configured previously via RRC, and the first RAN node then sends lower-layer signaling (e.g., MAC CE, Layer-1 DCI, etc.) indicating which of the candidate sensing configurations should be used. As another alternative in operation 7a, the first RAN node transmits the sensing configuration via broadcast SI block (SIB), which may be readable by all UEs in the same cell as the particular UE being configured.
[0185] In operation 7b, the first RAN node informs the SF about the sensing configuration provided to the UE.
[0186] In operation 8, the SF sends an SeRS utilization report to the second (non-serving) RAN node, indicating that the second RAN node should follow the muting configuration received in operation 3a for some predetermined duration or until further indication from the SF. In other words, since measurements of these SeRS are being performed during this interval, the second RAN node may not enter a lower-power mode in which it stops transmitting SeRS.
[0187] In operation 9a, the UE performs the configured sensing measurements and sends them to the first RAN node in a measurement report. The first RAN node forwards at least a portion of the received sensing measurements to the SF in operation 9b. In some variants, the first RAN node may use one or more of the received sensing measurements for its own operational purposes, such as described above. In operation 10, the SF processes the received sensing measurements as needed to determine the desired result (e.g., object detection, object tracking, etc.).
[0188] In operation 11, after the necessary result is determined by the SF, the SF sends SeRS utilization complete (or similarly named) messages to the first and second RAN nodes. Based on these messages, the two RAN nodes release (i.e., stop transmitting in) any SeRS resources used for the sensing session. In operation 12, the first RAN node notifies the UE to release any SeRS resources used for the sensing session. In response, the UE may transition to a non-connected state (e.g., RRC_IDLE, RRC_INACTIVE) and / or perform other operations as needed.
[0189] Various features of the embodiments described above correspond to various operations illustrated in Figures 10-12, which show exemplary methods (e.g., procedures) for a RAN node, a sensing function, and a UE, respectively. In other words, various features of the operations described below correspond to various embodiments described above. Furthermore, the exemplary methods shown in Figures 10-12 can be used cooperatively to provide various benefits, advantages, and / or solutions to problems described herein. Although Figures 10-12 show specific blocks in particular orders, the operations of the exemplary methods can be performed in differentorders than shown and can be combined and / or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.
[0190] In particular, Figure 10 shows an exemplary method (e.g., procedure) for a RAN node configured to facilitate sensing measurements by UEs, according to various embodiments of the present disclosure. The exemplary method can be performed by any appropriate RAN node (e.g., base station, eNB, gNB, CU / DU, 6gNB, etc.) such as described elsewhere herein.
[0191] The exemplary method includes the operations of block 1020, where the RAN node receives, from a sensing function (SF) in a core network coupled to the RAN, a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a UE to perform the required sensing measurements. The exemplary method also includes the operations of block 1040, where the RAN node determines a UE sensing configuration based on the sensing measurement request. The exemplary method also includes the operations of block 1050, where the RAN node sends the UE sensing configuration to the UE. The exemplary method also includes the operations of block 1060, where the RAN node receives from the UE a measurement report that includes the required sensing measurements.
[0192] In some embodiments, the exemplary method also includes the operations of block 1015, where the RAN node receives from the UE an indication of UE sensing capabilities. The UE sensing configuration is determined further based on the UE sensing capabilities. In some embodiments, the exemplary method also includes the following operations, labelled with corresponding block numbers:
[0193] • (1065) receiving from the UE a transparent container that includes a UE location determined in conjunction with the sensing measurements; and
[0194] • (1075) forwarding the transparent container to the SF without decoding or otherwise processing the contents of the transparent container.
[0195] In some of these embodiments, the transparent container is received in the measurement report. In other of these embodiments, the transparent container is received in a different message than the measurement report.
[0196] In some embodiments, the exemplary method also includes the operations of block 1010, where the RAN node sends to the SF a sensing configuration of the RAN node. The sensing measurement request is based on the sensing configuration of the RAN node, and the UE sensing configuration is determined further based on the sensing configuration of the RAN node. In some of these embodiments, the sensing configuration includes or indicates one or more of the following information related to reference signals (RS) transmitted by the RAN node for sensing measurements:
[0197] type;• time and / or frequency resources;
[0198] • carrier frequency;
[0199] • bandwidth or bandwidth combination;
[0200] • pulse duration;
[0201] • pulse periodicity or aperiodic configuration;
[0202] • comb configuration;
[0203] • muting pattern;
[0204] • cyclic prefix (CP) length;
[0205] • sub-carrier spacing (SCS);
[0206] • number of sensing resources or resource sets; and
[0207] • time offset with respect to a reference time on the RAN node radio interface.
[0208] In some variants of these embodiments, the sensing configuration indicates one or more of the information related to RS based on an index to or identifier of a predetermined set of parameters.
[0209] In some embodiments, the sensing measurements are based on reference signals (RS) transmitted by a second RAN node and the exemplary method also includes the operations of block 1025, where the RAN node receives from the SF a sensing configuration for the second RAN node. The UE sensing configuration is determined by the RAN node further based on the sensing configuration for the second RAN node. In some of these embodiments, the UE sensing configuration includes or is sent together with the sensing configuration for the second RAN node.
[0210] In other embodiments, the sensing measurements are based on reference signals (RS) transmitted by the RAN node and the exemplary method also includes the operations of block 1030, where the RAN node receives from the SF a muting configuration for the RS transmitted by the RAN node. The UE sensing configuration is determined by the RAN node further based on the muting configuration.
[0211] In some embodiments, the exemplary method also includes the operations of block 1055, where the RAN node sending the UE sensing configuration to the SF. In some embodiments, the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
[0212] In some embodiments, the exemplary method also includes the operations of block 1070, where the RAN node performs one or more of the following operations based on the measurement report:
[0213] adjusting one or more operational settings of the RAN node based on one or more of the sensing measurements included in the measurement report; and
[0214] forwarding the measurement report to the SF.In some of these embodiments, the one or more operational settings relate to at least one of the following: beam management, mobility management of UEs served by the RAN node, and radio resource optimization. In some of these embodiments, the exemplary method also includes the following operations, labelled with corresponding block numbers:
[0215] • (1080) after forwarding the measurement report to the SF (e.g., in block 1075), receiving from the SF an indication that the sensing measurements have been completed; and • (1090) performing one or more of the following in response to the indication: releasing one or more RAN node resources used to facilitate the sensing measurements, and sending to the UE a further indication to release UE resources used for the sensing measurements. In some embodiments, the UE sensing configuration is determined further based on the UE’s current RRM configuration. In other embodiments, the exemplary method also includes the operations of block 1045, where the RAN node adjusts the UE’s current RRM configuration based on the UE sensing configuration, thereby obtaining an adjusted RRM configuration. In some of these embodiments, the adjusted RRM configuration is sent to the UE together with the UE sensing configuration. In some of these embodiments, one or more of the following parts of the UE’s current RRM configuration are adjusted to obtain the adjusted RRM configuration: measurement gap configuration, active bandwidth part (BWP) configuration, and discontinuous reception (DRX) configuration.
[0216] In some embodiments, the sensing measurements are based on first RS transmitted by the RAN node and second RS transmitted by a second RAN node. In such embodiments, the exemplary method also includes the operations of block 1035, where the RAN node receives from the second RAN node one or more observed time differences (OTDs) between the first RS and the second RS. The UE sensing configuration is determined further based on the received OTDs.
[0217] In some embodiments, the UE sensing configuration includes or indicates one or more of the following:
[0218] • the list of required sensing measurements;
[0219] • list of cells, beams, and / or transmission reception points (TRPs) to be measured;
[0220] • antenna panel configurations for TRPs to be measured;
[0221] • required or requested measurement granularity;
[0222] • required or requested measurement bandwidth;
[0223] • transmission configuration of RS to be measured, including any muting patterns;
[0224] • a measurement duration; and
[0225] • measurement assistance data.
[0226] In some embodiments, the sensing measurements include one or more of the following: one or more Doppler-related measurements, one or more carrier phase-related measurements, oneor more timing-related measurements, one or more angular-related measurements, velocity, speed, direction, reference signal received power (RSRP), and reference signal received path power (RSRPP).
[0227] In some embodiments, the SF is one of the following: sensing management function (SeMF), sensing control function (SCF), sensing processing function (SPF), location management function (LMF), or access and mobility management function (AMF).
[0228] In addition, Figure 11 shows an exemplary method (e.g., procedure) for a sensing function (SF) configured to operate in a core network coupled to a RAN, according to various embodiments of the present disclosure. The exemplary method can be performed by any appropriate sensing function (e.g., SeMF, SCF, SPF, AMF, LMF, etc.) such as described elsewhere herein.
[0229] The exemplary method includes the operations of block 1140, where the SF sends to a RAN node a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a UE to perform the required sensing measurements. The exemplary method also includes the operations of block 1160, where the SF receives from the RAN node a measurement report that includes the required sensing measurements performed by the UE.
[0230] In some embodiments, the exemplary method also includes the operations of block 1170, where the SF receives, from the UE via the RAN node, a transparent container that includes a UE location determined in conjunction with the sensing measurements. In some of these embodiments, the transparent container is received in the measurement report. In other of these embodiments, the transparent container is received in a different message than the measurement report.
[0231] In some embodiments, the exemplary method also includes the operations of block 1110, where the SF receives sensing configurations from one or more of the following: the RAN node, and a second RAN node. In such embodiments, the sensing measurement request is based on the received one or more sensing configuration.
[0232] In some of these embodiments, the exemplary method also includes the operations of block 1115, where the SF selects at least one of the RAN node and the second RAN node to transmit reference signals (RS) for the sensing measurements. The selection is based on one or more of the following:
[0233] • the sensing configurations of the RAN node and the second RAN node,
[0234] • respective locations of transmission antenna associated with the RAN node and the second RAN node,
[0235] • a required sensing area, and
[0236] • a geometric dilution of precision (GDOP) requirement.In some of these embodiments, the exemplary method also includes the following operations for each selected RAN node, labelled with corresponding block numbers:
[0237] • (1120) determining a muting configuration for the RS transmitted by the selected RAN node, wherein the muting configuration is determined based on the sensing configurations for all selected RAN nodes; and
[0238] • (1125) sending the muting configuration to the selected RAN node.
[0239] In some of these embodiments, the RAN node serves the UE and the exemplary method also includes the operations of block 1130, where when the second RAN node is selected and the RAN node is not selected, the SF sends to the RAN node the sensing configuration of the second RAN node.
[0240] In various embodiments, each received sensing configuration includes or indicates any of the information described above in relation to corresponding RAN node embodiments. In some of these embodiments, each received sensing configuration indicates one or more of the information based on an index to or identifier of a predetermined set of parameters.
[0241] In some embodiments, the exemplary method also includes the operations of block 1150, where the SF receives from the RAN node a UE sensing configuration that was determined by the RAN node based on the sensing measurement request. In various embodiments, the UE sensing configuration may include or indicate any of the information described above in relation to corresponding RAN node embodiments.
[0242] In some embodiments, the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
[0243] In some embodiments, the exemplary method also includes the following operations, labelled with corresponding block numbers:
[0244] • (1180) determining a sensing result based on the received measurement report; and • (1190) sending to the RAN node an indication that the required sensing measurements have been completed.
[0245] In various embodiments, the sensing measurements may include any of the sensing measurements described above in relation to corresponding RAN node embodiments. In some embodiments, the SF is one of the following:: SeMF, SCF, SPF, LMF, or AMF.
[0246] In addition, Figure 12 shows an exemplary method (e.g., procedure) for a UE configured to support sensing measurements in a RAN, according to various embodiments of the present disclosure. The exemplary method can be performed by any appropriate UE (e.g., wireless device, SU, etc.) such as described elsewhere herein.
[0247] The exemplary method includes the operations of block 1220, where the UE receives, froma RAN node, a UE sensing configuration that includes a list of sensing measurements to be performed. The exemplary method also includes the operations of block 1230, where the UE performs the sensing measurements in accordance with the UE sensing configuration. The sensing measurements are performed on RS transmitted by one or more of the following: the RAN node, and a second RAN node. The exemplary method also includes the operations of block 1240, where the UE sends to the RAN node a measurement report that includes the sensing measurements performed (or results thereof).
[0248] In some embodiments, the exemplary method also includes the operations of block 1210, where the UE sends to the RAN node an indication of UE sensing capabilities. The UE sensing configuration is based on the UE sensing capabilities. In some embodiments, the exemplary method also includes the following operations, labelled with corresponding block numbers:
[0249] • (1250) determining a UE location in conjunction with the sensing measurements; and • (1260) sending the UE location to a sensing function (SF) in a core network coupled to the RAN, wherein the UE location is sent via the RAN node in a transparent container. In some of these embodiments, the transparent container is included with the measurement report. In other of these embodiments, the transparent container is sent in a different message than the measurement report. In some of these embodiments, the SF is one of the following: SeMF, SCF, SPF, LMF, or AMF.
[0250] In some embodiments, the sensing measurements are performed on RS transmitted by the second RAN node, and the UE sensing configuration includes or is received together with a sensing configuration for the second RAN node. In some embodiments, the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
[0251] In some embodiments, the exemplary method also includes the operations of block 1270, where after sending the measurement report, the UE receives from the RAN node an indication to release UE resources used for the sensing measurements.
[0252] In some embodiments, the UE sensing configuration is based on the UE’s current RRM configuration. In other embodiments, the exemplary method also includes the operations of block 1225, where the UE receives from the RAN node an adjusted RRM configuration that is based on the UE’s current RRM configuration and the UE sensing configuration. In some of these embodiments, the adjusted RRM configuration is received together with the UE sensing configuration. In some of these embodiments, one or more of the following parts of the UE’s current RRM configuration have been adjusted to obtain the adjusted RRM configuration: measurement gap configuration, active BWP configuration, and DRX configuration.
[0253] In various embodiments, the UE sensing configuration may include or indicate any of theinformation described above in relation to corresponding RAN node embodiments. In various embodiments, the sensing measurements may include any of the sensing measurements described above in relation to corresponding RAN node embodiments.
[0254] Although various embodiments are described above in terms of methods, techniques, and / or procedures, the person of ordinary skill will readily comprehend that such methods, techniques, and / or procedures can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, computer program products, etc.
[0255] Figure 13 shows an example communication system 1300 according to some embodiments. In this example, communication system 1300 includes a telecommunication network 1302 that includes an access network 1304 (e.g., RAN) and a core network 1306, which includes one or more core network nodes 1308. Access network 1304 includes one or more access network nodes, such as access network nodes 1310a-b (one or more of which may be generally referred to as network nodes 1310), or any other similar 3GPP access nodes or non-3GPP access points (APs). Some embodiments of the access network 1304 may include more than one access network technology. Access network nodes 1310 of access network 1304 facilitate direct or indirect connection of wireless devices, to the core network 1306 over one or more wireless connections. Such wireless devices may also referred to as user equipment (UEs), with UEs 1312A-D (one or more of which may be generally referred to as UEs 1312) shown by way of example.
[0256] Moreover, such network nodes are not necessarily limited to implementations in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Rather, the network nodes may include disaggregated implementations. For example, in some embodiments, telecommunication network 1302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in telecommunication network 1302 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in telecommunication network 1302, including one or more access network nodes 1310 and / or core network nodes 1308.
[0257] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support aspecification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.
[0258] Access network nodes 1310 facilitate direct or indirect connection of UEs, such as by connecting UEs 1312, to core network 1306 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, communication system 1300 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. Communication system 1300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0259] UEs 1312 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with access network nodes 1310 and other communication devices. Similarly, access network nodes 1310 are arranged, capable, configured, and / or operable to communicate directly or indirectly with UEs 1312 and / or with other network nodes or equipment in telecommunication network 1302 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in telecommunication network 1302.
[0260] More specifically, UEs 1312 may send messages, data, and / or other signals to network nodes 1308, 1310 or other elements of the telecommunications network 1302 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 1308, 1310 may send messages, data, and other signals to UEs 13122, other network nodes 1308, 1310, and other devices in telecommunications network 1302 directly or indirectly. As one specific example, core network node 108 may transmit a particular message to a UE 1312 by transmitting the message to an access network node 1310, which will then transmitthe message to the UE 1312. Similarly, core network node 108 may receive a particular message from a UE 1312 by receiving the message from an access network node 1310 that itself received the message from the UE 1312.
[0261] As shown in Figure 13, core network 1306 connects elements of access network 1304 (e.g., one or more of access network nodes 1310) to one or more host computing systems, such as host 1316. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 1306 may include one or more core network nodes (e.g., 1308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of core network node 1308. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDE), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0262] Host 1316 may be under the ownership or control of a service provider other than an operator or provider of access network 1304 and / or telecommunication network 1302, and may be operated by the service provider or on behalf of the service provider. Host 1316 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0263] As a whole, communication system 1300 of Figure 13 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near FieldCommunication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
[0264] Moreover, communication system 1300 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1300 supporting different standards, protocols, or rule sets. As one example, access network 1304 may contain some access network nodes 1310 that support 3GPP radio access technologies (RAT), such as LTE or NR, while the same (or other) access network nodes 1310 (non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 1302 may support multiple generations of related communication standards (e.g., 3GPP 4G and 5G standards) and, as a result, access network 1304 and / or core network 1306 may support multiple generations of related communication standards. Alternately, telecommunications network 1302 may include multiple access networks 1304 and / or multiple core networks 1306, which support respective generations of standards.
[0265] In some embodiments, telecommunications network 1302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1302. For example, the telecommunications network 1302 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0266] In some examples, one or more of UEs 1312 may be configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to access network 1304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 1304. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN / NR dual connectivity (EN-DC).
[0267] According to the example shown in Figure 13, hub 1314 communicates with access network 1304 to facilitate indirect communication between one or more UEs (e.g., 1312C and / or 1312D) and network nodes (e.g., network node 1310b). In some examples, hub 1314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, hub 1314 may be a broadband router enabling access to core network 1306 for the UEs. As another example, hub 1314 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructionsmay be received from the UEs, access network nodes 1310, or by executable code, script, process, or other instructions in hub 1314.
[0268] As another example, hub 1314 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, hub 1314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, hub 1314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0269] Hub 1314 may have a constant / persistent or intermittent connection to network node 1310b. Hub 1314 may also allow for a different communication scheme and / or schedule between hub 1314 and UEs (e.g., 1312C and / or 1312D), and between hub 1314 and core network 1306. In other examples, hub 1314 is connected to core network 1306 and / or one or more UEs via a wired connection. Moreover, hub 1314 may be configured to connect to an M2M service provider over access network 1304 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with access network nodes 1310 while still connected via hub 1314 via a wired or wireless connection. In some embodiments, hub 1314 may be a dedicated hub -that is, a hub whose primary function is to route communications to / from the UEs from / to network node 1310b . In other embodiments , hub 1314 may be a non-dedicated hub - that is , a device which is capable of operating to route communications between the UEs and network node 1310b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0270] In some embodiments, any of core network nodes 1308 may be configured to perform operations attributed to a SF in various methods or procedures described above, including the exemplary method shown in Figure 10. In some embodiments, any of access network nodes 1310 may be configured to perform operations attributed to a RAN node in various methods or procedures described above, including the exemplary method shown in Figure 11. In some embodiments, any of UEs 1312 may be configured to perform operations attributed to a UE in various methods or procedures described above, including the exemplary method shown in Figure 12.
[0271] Figure 14 shows another example communication system 1400 according to some embodiments. In this example, communication system 1400 includes multiple access points (APs) (e.g., APs 1410A-D) and multiple wireless devices 1412A-E, which may also be referred to in this context as stations (STAs) 1412A-E (or collectively as STAs 1412).Each STA 1412A-E connect through a radio link to one of APs 1410. For example, depending on location or channel conditions experienced by a particular STA, the STA may select an appropriate AP and basic service set (BSS) for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, 5-GHz band, 6-GHz band, 60-GHz band, etc. In the specific example shown, STA 1412A is served by AP 1410A in a first BSS 1420A, STA 1410B-C are served by AP 1410B in a second BSS 1420B, STA 1412D is served by AP 1410C in a third BSS 1420C, and STA 1412E is served by AP 1410D in a fourth BSS 1420D.
[0272] STAs 1412 may be non-AP STAs and correspond to various kinds of wireless devices such as user terminals, mobile or stationary computing devices, smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), smart home devices, printers, multimedia devices, data storage devices, etc.
[0273] As illustrated, APs 1410 may be connected to a data network 1430, enabling each AP to provide data connectivity between STAs 1412 and other entities in data network 1430 (e.g., servers, service providers, data sources, data sinks, user terminals, etc.). Accordingly, a radio link established between a particular STA 1412 and its serving AP 1410 may be used for providing various kinds of services to STA 1412, such as voice, multimedia, data, etc. Such services may be based on applications that are executed on STA 1412 and / or on a device linked to STA 1412.
[0274] In the example shown in Figure 14, data network 1430 includes application service platform 1432, with which application(s) executed on any of STAs 1412 (and / or on one or more other devices linked to STAs 1412) may communicate via the respective radio links between STAs 1412 and their respective serving APs 1410. Such communication may facilitate efficient utilization of the corresponding service(s) at STA 1412.
[0275] In some embodiments, application service platform may be configured to perform operations attributed to a SF in various methods or procedures described above, including the exemplary method shown in Figure 11. In some embodiments, any of APs 1410 may be configured to perform operations attributed to a RAN node in various methods or procedures described above, including the exemplary method shown in Figure 10. In some embodiments, any of STAs 1412 may be configured to perform operations attributed to a UE in various methods or procedures described above, including the exemplary method shown in Figure 12.
[0276] Figure 15 shows an example wireless device 1500 according to some embodiments. Wireless device 1500 may represent any of various examples including, but not limited to, smartphones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), vehicles, vehicle-mounted or vehicle embedded / integrated wireless devices, etc. Other examples include any user equipment (UE) identified by 3GPP, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0277] A wireless device may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a wireless device may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a wireless device may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a wireless device may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0278] Wireless device 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input / output interface 1506, a power source 1508, a memory 1510, a communication interface 1512, and / or one or more other components not explicitly shown. Moreover, certain wireless devices may utilize all or a subset of the components shown in Figure 15. The level of integration between the components may vary from one wireless device to another wireless device, and one or more of the components explicitly shown in Figure 15 may be integrated wholly or partially with other components not explicitly shown. Further, certain wireless devices may contain multiple instances of a particular component (e.g., processors, memories, transceivers, transmitters, receivers, etc.).
[0279] Processing circuitry 1502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in memory 1510. Processing circuitry 1502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), togetherwith appropriate software; or any combination of the above. For example, processing circuitry 1502 may include multiple central processing units (CPUs).
[0280] In the example shown in Figure 15, input / output interface 1506 may be configured to provide interface(s) to input device(s), output device(s), or some combination thereof. Example output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smartcards, etc., or some combination thereof. Example input devices include a touch-(or presence-) sensitive displays, cameras (e.g., digital camera, video camera, web camera, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, smartcards, etc., or some combination thereof.
[0281] As a more specific example, presence-sensitive displays may include a capacitive or resistive touch sensor to sense input from a user. As other more specific examples, sensors may include an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or some combination thereof. In some variants, an output device may use the same interface port (or same port type) as an input device. As an example of these variants, a Universal Serial Bus (USB) port may be used as an input device and an output device.
[0282] In some embodiments, power source 1508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. Power source 1508 may further include power circuitry for delivering power from power source 1508 itself, and / or an external power source, to the various parts of wireless device 1500 via input circuitry or an interface such as an electrical power cable. Power circuitry may perform any formatting, converting, or other modification to the power from power source 1508 to make the power suitable for the respective components of wireless device 1500 to which power is supplied.
[0283] Memory 1510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, memory 1510 includes one or more programs 1514, such as an operating system, web browser application, widgets, a gadget engine, etc. and corresponding data 1516. Memory 1510 may store, for use by wireless device 1500, one or more specific operating systems or combinations thereof.
[0284] Memory 1510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical discdrive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ Memory 1510 may allow wireless device 1500 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in memory 1510, which may be or comprise a device-readable storage medium.
[0285] Processing circuitry 1502 may be configured to communicate with an access network or other network using communication interface 1512. Communication interface 1512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1522. Communication interface 1512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 1518 and / or a receiver 1520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, transmitter 1518 and receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522) and may share circuit components, software, or firmware, or alternatively be implemented separately.
[0286] In the example shown in Figure 15, communication interface 1512 may support and / or provide cellular communication, Wi-Fi communication, UPWAN communication, data communication, voice communication, multimedia communication, short-range communication (e.g., Bluetooth, near-field communication), location-based communication (e.g., use of the global navigation satellite system, GNSS, to determine location), etc., or any combination thereof. Communications may be implemented according to one or more protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), orthogonal frequency division multiplexing or multiple access (OFDM / OFDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0287] In some embodiments, wireless device 1500 may output data captured by its sensors through its communication interface 1512 to a network node via a wireless connection, such asshown in Figures 13-14. In some variants, the wireless connection may be through another wireless device of similar or different type. Output of the captured sensor data may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., an alert is sent when moisture is detected), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0288] In some embodiments, wireless device 1500 may include an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. In some variants, the states of the actuator, motor, or switch may change in response to the received wireless input. For example, the UE may include a motor that adjusts control surfaces or rotors of a unmanned aerial vehicle (UAV, e.g., drone) in flight according to the received input, or adjusts a robotic arm performing a medical procedure according to the received input.
[0289] When in the form of an Internet of Things (loT) device, wireless device 1500 may be used in one or more application domains such as wearable technology, extended industrial application, and healthcare. As some non-limiting example, such an loT device may include (or be embedded in) a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a headmounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, a UAV, and a medical device (e.g., heart rate monitor, remote controlled surgical robot, etc.). When arranged as an loT device, wireless device 1500 may include circuitry and / or software associated with its intended application as well as other components such as described above for more generic embodiments of wireless device 1500.
[0290] As another example loT-related application, wireless device 1500 may include (or be embedded in) a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to other wireless devices and / or to network nodes in a communication network. As a more specific example, wireless device 300 may be an M2M device, which may also be referred to as a machine-type communication (MTC) device in 3GPP vocabulary. Such an M2M device may implement the 3GPP NB-IoT standard. Asanother example loT-related application, wireless device 1500 may be embedded in a vehicle (e.g., passenger car, motorcycle, bus, truck, ship, airplane, etc.) or in other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0291] In practice, any number of wireless devices (e.g., 1500) may be used together in a single use case. For example, a first wireless device may be or be integrated in a UAV and provide the UAV’s speed information (e.g., obtained through a speed sensor) to a second wireless device that is a remote controller operating the UAV. When the user makes changes from the remote controller, the first wireless device may adjust the throttle on the UAV (e.g., by controlling an actuator) to increase or decrease the UAV’s speed. The first and / or the second wireless devices may include more than the specific functionalities described above. For example, a wireless device may include a sensor and an actuator, and handle communication of data for both the sensor and the actuator.
[0292] In some embodiments, wireless device 1500 may be configured to perform operations attributed to a UE in various methods or procedures described above, including the exemplary method shown in Figure 12.
[0293] Figure 16 shows an example network node 1600 according to some embodiments. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (e.g., radio base stations, Node Bs, eNBs, gNBs), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). Network node 1600 may be considered as a type of network equipment (in contrast to user equipment, UE).
[0294] Network nodes may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1600 may be a relay node or a relay donor node controlling a relay. Network node 1600 may include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0295] Other examples of network nodes (such as 1600) include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicastcoordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0296] Network node 1600 includes processing circuitry 1602, memory 1604, communication interface 1606, and power source 1608. Network node 1600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. For example, the specific components shown in Figure 16 may represent or include physical components common to or shared by one or more of the other elements of network node 1600.
[0297] In certain scenarios in which network node 1600 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 1600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1604 for different RATs) and some components may be reused (e.g., one antenna 1610 may be shared by different RATs). Network node 1600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1600, e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID), Bluetooth, etc. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1600.
[0298] Processing circuitry 1602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components (e.g., memory 1604) to provide the functionality of network node 1600.
[0299] In some embodiments, processing circuitry 1602 may include a system on a chip (SOC). In some embodiments, processing circuitry 1602 includes radio frequency (RF) transceiver circuitry 1612 and / or baseband processing circuitry 1614. In some embodiments, RF transceiver circuitry 1612 and / or baseband processing circuitry 1614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1612 and / or baseband processing circuitry 1614 may be on the same chip or set of chips, boards, or units.Memory 1604 may include any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by processing circuitry 1602. Memory 1604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions (collectively denoted computer program 1604A, which may be in the form of a computer program product) capable of being executed by processing circuitry 1602 and utilized by network node 1600. Memory 1604 may be used to store any calculations made by processing circuitry 1602 and / or any data received via communication interface 1606. In some embodiments, processing circuitry 1602 and memory 1604 is integrated.
[0300] Communication interface 1606 may be used for wired or wireless communication of signaling and / or data between network node 1600, an access network, a core network, and / or wireless device(s). As illustrated, communication interface 1606 comprises port(s) / terminal(s) 1616 to send and receive data, for example to and from a network over a wired connection. Communication interface 1606 also includes radio front-end circuitry 1618 that may be coupled to, or in certain embodiments a part of, antenna 1610. Radio front-end circuitry 1618 comprises filters 1620 and amplifiers 1622. Radio front-end circuitry 1618 may be connected to an antenna 1610 and processing circuitry 1602. The radio front-end circuitry may be configured to condition signals communicated between antenna 1610 and processing circuitry 1602. Radio front-end circuitry 1618 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front-end circuitry 1618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1620 and / or amplifiers 1622. The radio signal may then be transmitted via antenna 1610. Similarly, when receiving data, antenna 1610 may collect radio signals which are then converted into digital data by radio front-end circuitry 1618. The digital data may be passed to processing circuitry 1602. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0301] In certain alternative embodiments, network node 1600 does not include separate radio front-end circuitry 1618, instead, processing circuitry 1602 includes radio front-end circuitry and is connected to antenna 1610. Similarly, in some embodiments, all or some of RF transceiver circuitry 1612 is part of communication interface 1606. In still other embodiments,communication interface 1606 includes one or more ports or terminals 1616, radio front-end circuitry 1618, and RF transceiver circuitry 1612, as part of a radio unit (not shown), and communication interface 1606 communicates with baseband processing circuitry 1614, which is part of a digital unit (not shown).
[0302] Antenna 1610 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. Antenna 1610 may be coupled to radio front-end circuitry 1618 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, antenna 1610 is separate from network node 1600 and connectable to network node 1600 through one or more interfaces or ports.
[0303] Antenna 1610, communication interface 1606, and / or processing circuitry 1602 may be configured to perform various receiving and / or obtaining operations described herein as being performed by a network node. Any information, data and / or signals may be received from a wireless device, another network node, and / or any other network equipment. Similarly, antenna 1610, communication interface 1606, and / or processing circuitry 1602 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and / or signals may be transmitted to a wireless device, another network node, and / or any other network equipment.
[0304] Power source 1608 provides power to the various components of network node 1600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1608 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1600 with power for performing the functionality described herein. For example, network node 1600 may be connectable to an external power source (e.g., generator, power grid, electrical outlet, etc.) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of power source 1608. As another example, power source 1608 may include a battery or battery pack that is connected to, or integrated with, power circuitry. Such a battery or battery pack may provide backup power should the external power source fail.
[0305] Embodiments of network node 1600 may include additional components beyond those shown in Figure 16 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1600 may include user interface equipment to allow input of information into network node 1600 and to allow output of information from network node 1600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1600.In some embodiments, network node 1600 may be configured to perform operations attributed to a RAN node in various methods or procedures described above, including the exemplary method shown in Figure 10. In some embodiments, network node 1600 may be configured to perform operations attributed to a sensing function in various methods or procedures described above, including the exemplary method shown in Figure 11. In other words, network node 1600 may be network equipment configured to implement a sensing function.
[0306] Figure 17 shows an example virtualization environment 1700 in which some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1700 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1700 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
[0307] Applications 1702 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1700 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. For example, one or more virtual nodes 1702 may be configured to perform operations attributed to a RAN node in various methods or procedures described above, including the exemplary method shown in Figure 10. As another example, one or more virtual nodes 1702 may be configured to perform operations attributed to a sensing function in various methods or procedures described above, including the exemplary method shown in Figure 11. In other words, virtualization environment 1700 may be network equipment configured to implement a sensing function.
[0308] Hardware 1704 may include processing circuitry, memory that stores software and / or instructions (collectively denoted computer program 1704A, which may be in the form of a computer program product) executable by the processing circuitry, and other hardware devices such as a network interface, input / output interface, etc. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1706 (also referred to ashypervisors or virtual machine monitors (VMMs)), provide VMs 1708A-B (one or more of which may be generally referred to as VMs 1708), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. Virtualization layer 1706 may present a virtual operating platform that appears like networking hardware to the VMs 1708.
[0309] VMs 1708 may include virtual processing resources, virtual memory and / or storage, virtual networking and / or communication interfaces, etc., and may be run by a corresponding virtualization layer 1706. Different instances of a virtual appliance 1702 may be implemented on one or more VMs 1708, in various ways. In this context, hardware virtualization may also be referred to as network function virtualization (NFV), which may be used to consolidate many network equipment types onto commercial off-the-shelf (COTS) hardware such as server hardware, physical switches, physical storage, etc.. Such equipment may be located in data centers, customer premises, etc.
[0310] In the context of NFV, each VM 1708 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each VM 1708, and that part of hardware 1704 which executes the particular VM (e.g., VM-dedicated hardware or hardware shared with other VMs), forms a separate virtual network element. Further in the context of NFV, a virtual network function (NF) may be responsible for handling specific NFs that run in one or more VMs 1708 on top of hardware 1704 and that corresponds to a particular application 1702.
[0311] Hardware 1704 may be implemented in a standalone network node with generic or specific components. Hardware 1704 may implement some functions via virtualization. Alternatively, hardware 1704 may be part of a larger cluster of hardware (e.g., in a data center or customer premises) where many hardware nodes are managed cooperatively by a management and orchestration function 1710, which may oversee lifecycle management (LCM) of applications 1702. In some embodiments, hardware 1704 may be coupled to one or more radio units, each of which may include one or more transmitters and / or one or more receivers and may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1712 which may alternatively be used for communication between hardware nodes and radio units.
[0312] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devisenumerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.
[0313] The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and / or electronic devices and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.
[0314] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
[0315] As described herein, device and / or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and / or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered known to a skilled person.Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
[0316] In addition, certain terms used in the present disclosure, including the specification and drawings, can be used synonymously in certain instances (e.g., “data” and “information”). Although such terms may be used synonymously herein, there can be instances when such terms are not intended to not be used synonymously.
[0317] Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:
[0318] Al. A method for a radio access network (RAN) node configured to facilitate sensing measurements by user equipment (UEs), the method comprising:
[0319] receiving, from a sensing function (SF) in a core network coupled to the RAN, a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a UE to perform the required sensing measurements; determining a UE sensing configuration based on the sensing measurement request; sending the UE sensing configuration to the UE; and
[0320] receiving from the UE a measurement report that includes the required sensing measurements.
[0321] A2. The method of embodiment Al, further comprising receiving from the UE an indication of UE sensing capabilities, wherein the UE sensing configuration is determined further based on the UE sensing capabilities.
[0322] A3. The method of any of embodiments A1-A2, further comprising:
[0323] receiving from the UE a transparent container that includes a UE location determined in conjunction with the sensing measurements; and
[0324] forwarding the transparent container to the SF without decoding or otherwise processing the contents of the transparent container.
[0325] A3 a. The method of embodiment A3, wherein one of the following applies: the transparent container is received in the measurement report, or the transparent container is received in adifferent message than the measurement report.
[0326] A4. The method of any of embodiments Al-A3a, further comprising sending to the SF a sensing configuration of the RAN node, wherein: the sensing measurement request is based on the sensing configuration of the RAN node, and the UE sensing configuration is determined further based on the sensing configuration of the RAN node.
[0327] A4a. The method of embodiment A4, wherein the sensing configuration includes or indicates one or more of the following information related to reference signals (RS) transmitted by the RAN node for sensing measurements:
[0328] type;
[0329] time and / or frequency resources;
[0330] carrier frequency;
[0331] bandwidth or bandwidth combination;
[0332] pulse duration;
[0333] pulse periodicity or aperiodic configuration;
[0334] comb configuration;
[0335] muting pattern;
[0336] cyclic prefix (CP) length;
[0337] sub-carrier spacing (SCS);
[0338] number of sensing resources or resource sets; and
[0339] time offset with respect to a reference time on the RAN node radio interface.
[0340] A4b. The method of embodiment A4a, wherein the sensing configuration indicates one or more of the information related to RS based on an index to or identifier of a predetermined set of parameters.
[0341] A5. The method of any of embodiments Al-A4b, wherein the sensing measurements are based on reference signals (RS) transmitted by a second RAN node, the method further comprises receiving from the SF a sensing configuration for the second RAN node, and the UE sensing configuration is determined further based on the sensing configuration for the second RAN node.
[0342] A5a. The method of embodiment A5, wherein the UE sensing configuration includes or is sent together with the sensing configuration for the second RAN node.A6. The method of any of embodiments Al-A4b, wherein the sensing measurements are based on reference signals (RS) transmitted by the RAN node, the method further comprises receiving from the SF a muting configuration for the RS transmitted by the RAN node, and the UE sensing configuration is determined further based on the muting configuration.
[0343] A7. The method of any of embodiments A1-A6, further comprising sending the UE sensing configuration to the SF.
[0344] A8. The method of any of embodiments A1-A7, wherein the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
[0345] A9. The method of any of embodiments A1-A8, further comprising performing one or more of the following operations based on the measurement report:
[0346] adjusting one or more operational settings of the RAN node based on one or more of the sensing measurements included in the measurement report; and
[0347] forwarding the measurement report to the SF.
[0348] A9a. The method of embodiment A9, wherein the one or more operational settings relate to at least one of the following: beam management, mobility management of UEs served by the RAN node, and radio resource optimization.
[0349] A9b. The method of any of embodiments A9-A9a, further comprising:
[0350] after forwarding the measurement report to the SF, receiving from the SF an indication that the sensing measurements have been completed; and
[0351] performing one or more of the following in response to the indication: releasing one or more RAN node resources used to facilitate the sensing measurements, and sending to the UE a further indication to release UE resources used for the sensing measurements.
[0352] A 10. The method of any of embodiments Al-A9b, wherein one of the following applies: the UE sensing configuration is determined further based on the UE’s current radio resource management (RRM) configuration; orthe method further comprises adjusting the UE’s current RRM configuration based on the UE sensing configuration, thereby obtaining an adjusted RRM configuration.
[0353] A 10a. The method of embodiment A 10, wherein the adjusted RRM configuration is sent to the UE together with the UE sensing configuration.
[0354] A 10b. The method of any of embodiments A 10- A 10a, wherein one or more of the following parts of the UE’s current RRM configuration are adjusted to obtain the adjusted RRM configuration: measurement gap configuration, active bandwidth part (BWP) configuration, and discontinuous reception (DRX) configuration.
[0355] All. The method of any of embodiments Al-AlOb, wherein the UE sensing configuration includes or indicates one or more of the following:
[0356] the list of required sensing measurements;
[0357] list of cells, beams, and / or transmission reception points (TRPs) to be measured; antenna panel configurations for TRPs to be measured;
[0358] required or requested measurement granularity;
[0359] required or requested measurement bandwidth;
[0360] transmission configuration of reference signals (RS) to be measured, including any muting patterns;
[0361] a measurement duration; and
[0362] measurement assistance data.
[0363] A 12. The method of any of embodiments Al -Al 1, wherein the sensing measurements include one or more of the following: one or more Doppler-related measurements, one or more carrier phase-related measurements, one or more timing-related measurements, one or more angular-related measurements, velocity, speed, direction, reference signal received power (RSRP), and reference signal received path power (RSRPP).
[0364] A13. The method of any of embodiments A1-A12, wherein the SF is one of the following: sensing management function (SeMF), sensing control function (SCF), sensing processing function (SPF), location management function (LMF), or access and mobility management function (AMF).
[0365] Bl. A method for a sensing function (SF) configured to operate in a core network coupled toa radio access network (RAN), the method comprising:
[0366] sending to a RAN node a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a user equipment (UE) to perform the required sensing measurements; and
[0367] receiving from the RAN node a measurement report that includes the required sensing measurements performed by the UE.
[0368] B2. The method of embodiment Bl, further comprising receiving, from the UE via the RAN node, a transparent container that includes a UE location determined in conjunction with the sensing measurements.
[0369] B2a. The method of embodiment B2, wherein one of the following applies: the transparent container is received in the measurement report, or the transparent container is received in a different message than the measurement report.
[0370] B3. The method of any of embodiments Bl-B2a, wherein:
[0371] the method further comprises receiving sensing configurations from one or more of the following: the RAN node, and a second RAN node; and
[0372] the sensing measurement request is based on the received one or more sensing configuration.
[0373] B3a. The method of embodiment B3, further comprising selecting at least one of the RAN node and the second RAN node to transmit reference signals (RS) for the sensing measurements, wherein the selection is based on one or more of the following:
[0374] the sensing configurations of the RAN node and the second RAN node,
[0375] respective locations of transmission antenna associated with the RAN node and the second RAN node,
[0376] a required sensing area, and
[0377] a geometric dilution of precision (GDOP) requirement.
[0378] B3b. The method of embodiment B3a, further comprising, for each selected RAN node:
[0379] determining a muting configuration for the RS transmitted by the selected RAN node, wherein the muting configuration is determined based on the sensing configurations for all selected RAN nodes; and
[0380] sending the muting configuration to the selected RAN node.B3c. The method of any of embodiments B3a-B3b, wherein the RAN node serves the UE and the method further comprises, when the second RAN node is selected and the RAN node is not selected, sending to the RAN node the sensing configuration of the second RAN node.
[0381] B3d. The method of any of embodiments B3-B3c, wherein each received sensing configuration includes or indicates one or more of the following information related to reference signals (RS) transmitted by the RAN node from which the sensing configuration is received: type;
[0382] time and / or frequency resources;
[0383] carrier frequency;
[0384] bandwidth or bandwidth combination;
[0385] pulse duration;
[0386] pulse periodicity or aperiodic configuration;
[0387] comb configuration;
[0388] muting pattern;
[0389] cyclic prefix (CP) length;
[0390] sub-carrier spacing (SCS);
[0391] number of sensing resources or resource sets; and
[0392] time offset with respect to a reference time on the RAN node radio interface.
[0393] B3e. The method of embodiment B3d, wherein each received sensing configuration indicates one or more of the information related to RS based on an index to or identifier of a predetermined set of parameters.
[0394] B4. The method of any of embodiments B 1-B3e, further comprising receiving from the RAN node a UE sensing configuration that was determined by the RAN node based on the sensing measurement request.
[0395] B4a. The method of embodiment B4, wherein the UE sensing configuration includes or indicates one or more of the following:
[0396] the list of required sensing measurements;
[0397] list of cells, beams, and / or transmission reception points (TRPs) to be measured; antenna panel configurations for TRPs to be measured;
[0398] required or requested measurement granularity;required or requested measurement bandwidth;
[0399] transmission configuration of reference signals (RS) to be measured, including any muting patterns;
[0400] a measurement duration; and
[0401] measurement assistance data.
[0402] B5. The method of any of embodiments Bl-B4a, wherein the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
[0403] B6. The method of any of embodiments B1-B5, further comprising:
[0404] determining a sensing result based on the received measurement report; and sending to the RAN node an indication that the required sensing measurements have been completed.
[0405] B7. The method of any of embodiments B1-B6, wherein the required sensing measurements include one or more of the following: one or more Doppler-related measurements, one or more carrier phase-related measurements, one or more timing-related measurements, one or more angular-related measurements, velocity, speed, direction, reference signal received power (RSRP), and reference signal received path power (RSRPP).
[0406] B8. The method of any of embodiments B1-B7, wherein the SF is one of the following: sensing management function (SeMF), sensing control function (SCF), sensing processing function (SPF), location management function (LMF), or access and mobility management function (AMF).
[0407] Cl. A method for a user equipment (UE) configured to support sensing measurements in a radio access network (RAN), the method comprising:
[0408] receiving, from a RAN node, a UE sensing configuration that includes a list of sensing measurements to be performed;
[0409] performing the sensing measurements in accordance with the UE sensing configuration, wherein the sensing measurements are performed on reference signals (RS) transmitted by one or more of the following: the RAN node, and a second RAN node; and
[0410] sending to the RAN node a measurement report that includes the sensing measurements.C2. The method of embodiment Cl, further comprising sending to the RAN node an indication of UE sensing capabilities, wherein the UE sensing configuration is based on the UE sensing capabilities.
[0411] C3. The method of any of embodiments C1-C2, further comprising:
[0412] determining a UE location in conjunction with the sensing measurements; and sending the UE location to a sensing function (SF) in a core network coupled to the RAN, wherein the UE location is sent via the RAN node in a transparent container.
[0413] C3a. The method of embodiment C3, wherein one of the following applies: the transparent container is included with the measurement report, or the transparent container is sent in a different message than the measurement report.
[0414] C3b. The method of any of embodiments C3-C3a, wherein the SF is one of the following: sensing management function (SeMF), sensing control function (SCF), sensing processing function (SPF), location management function (LMF), or access and mobility management function (AMF).
[0415] C4. The method of any of embodiments Cl-C3b, wherein the sensing measurements are performed on RS transmitted by the second RAN node, and the UE sensing configuration includes or is received together with a sensing configuration for the second RAN node.
[0416] C5. The method of any of embodiments C1-C4, wherein the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
[0417] C6. The method of any of embodiments C1-C5, further comprising, after sending the measurement report, receiving from the RAN node an indication to release UE resources used for the sensing measurements.
[0418] C7. The method of any of embodiments C1-C6, wherein one of the following applies: the UE sensing configuration is based on the UE’s current radio resource management (RRM) configuration; orthe method further comprises receiving from the RAN node an adjusted RRM configuration that is based on the UE’s current RRM configuration and the UE sensing configuration.
[0419] C7a. The method of embodiment C7, wherein the adjusted RRM configuration is received together with the UE sensing configuration.
[0420] C7b. The method of any of embodiments C7- C7a, wherein one or more of the following parts of the UE’s current RRM configuration have been adjusted to obtain the adjusted RRM configuration: measurement gap configuration, active bandwidth part (BWP) configuration, and discontinuous reception (DRX) configuration.
[0421] C8. The method of any of embodiments Cl-C7b, wherein the UE sensing configuration also includes or indicates one or more of the following:
[0422] list of cells, beams, and / or transmission reception points (TRPs) to be measured; antenna panel configurations for TRPs to be measured;
[0423] required or requested measurement granularity;
[0424] required or requested measurement bandwidth;
[0425] transmission configuration of reference signals (RS) to be measured, including any muting patterns;
[0426] a measurement duration; and
[0427] measurement assistance data.
[0428] C9. The method of any of embodiments C1-C8, wherein the sensing measurements include one or more of the following: one or more Doppler-related measurements, one or more carrier phase-related measurements, one or more timing-related measurements, one or more angular-related measurements, velocity, speed, direction, reference signal received power (RSRP), and reference signal received path power (RSRPP).
[0429] DI. Radio access network (RAN) node configured to facilitate sensing measurements by user equipment (UEs), the RAN node comprising:
[0430] communication interface circuitry configured to communicate with UEs and with a core network coupled to the RAN; and
[0431] processing circuitry operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry areconfigured to perform operations corresponding to the methods of any of embodiments Al -Al 3.
[0432] D2. Radio access network (RAN) node configured to facilitate sensing measurements by user equipment (UEs), the RAN node being further configured to perform operations corresponding to the methods of any of embodiments Al -Al 3.
[0433] D3. Non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured to facilitate sensing measurements by user equipment (UEs), configure the RAN node to perform operations corresponding to the methods of any of embodiments A1-A13.
[0434] D4. Computer program product comprising computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured to facilitate sensing measurements by user equipment (UEs), configure the RAN node to perform operations corresponding to the methods of any of embodiments Al -Al 3.
[0435] El. Network equipment configured to implement a sensing function (SF) operable in a core network coupled to a radio access network (RAN), the network equipment comprising:
[0436] communication interface circuitry configured to communicate with radio access network (RAN) nodes and with user equipment (UEs) via the RAN nodes; and processing circuitry operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to the methods of any of embodiments B 1 -B 8.
[0437] E2. Network equipment configured to implement a sensing function (SF) operable in a core network coupled to a radio access network (RAN), the network equipment being further configured to perform operations corresponding to the methods of any of embodiments B1-B8.
[0438] E3. Non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a sensing function (SF) operable in a core network coupled to a radio access network (RAN), configure the SF to perform operations corresponding to the methods of any of embodiments B1-B8.E4. Computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a sensing function (SF) operable in a core network coupled to a radio access network (RAN), configure the SF to perform operations corresponding to the methods of any of embodiments B1-B8.
[0439] Fl. User equipment (UE) configured to support sensing measurements in a radio access network (RAN), the UE comprising:
[0440] communication interface circuitry configured to communicate with RAN nodes; and processing circuitry operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to the methods of any of embodiments C1-C9.
[0441] F2. User equipment (UE) configured to support sensing measurements in a radio access network (RAN), the UE being further configured to perform operations corresponding to the methods of any of embodiments C1-C9.
[0442] F3. Non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of user equipment (UE) configured to support sensing measurements in a radio access network (RAN), configure the UE to perform operations corresponding to the methods of any of embodiments C1-C9.
[0443] F4. Computer program product comprising computer-executable instructions that, when executed by processing circuitry of user equipment (UE) configured to support sensing measurements in a radio access network (RAN), configure the UE to perform operations corresponding to the methods of any of embodiments C1-C9.
Claims
CLAIMS1. A method for a radio access network, RAN, node configured to facilitate sensing measurements by user equipment, UEs, the method comprising:receiving (1020), from a sensing function, SF, operatively coupled to the RAN, a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a UE to perform the required sensing measurements; determining (1040) a UE sensing configuration based on the sensing measurement request;sending (1050) the UE sensing configuration to the UE; andreceiving (1060) from the UE a measurement report that includes the required sensing measurements.
2. The method of claim 1, further comprising receiving (1015) from the UE an indication of UE sensing capabilities, wherein the UE sensing configuration is determined further based on the UE sensing capabilities.
3. The method of any of claims 1-2, further comprising:receiving (1065) from the UE a transparent container that includes a UE location determined in conjunction with the sensing measurements; andforwarding (1075) the transparent container to the SF without decoding or otherwise processing the contents of the transparent container.
4. The method of claim 3, wherein one of the following applies: the transparent container is received in the measurement report, or the transparent container is received in a different message than the measurement report.
5. The method of any of claims 1-4, further comprising sending (1010) to the SF a sensing configuration of the RAN node, wherein: the sensing measurement request is based on the sensing configuration of the RAN node, and the UE sensing configuration is determined further based on the sensing configuration of the RAN node.
6. The method of claim 5, wherein the sensing configuration includes or indicates one or more of the following information related to reference signals, RS, transmitted by the RAN node for sensing measurements:type;time and / or frequency resources;carrier frequency;bandwidth or bandwidth combination;pulse duration;pulse periodicity or aperiodic configuration;comb configuration;muting pattern;cyclic prefix, CP, length;sub-carrier spacing, SCS;number of sensing resources or resource sets; andtime offset with respect to a reference time on the RAN node radio interface.
7. The method of claim 6, wherein the sensing configuration indicates one or more of the information related to RS based on an index to or identifier of a predetermined set of parameters.
8. The method of any of claims 1-7, wherein:the sensing measurements are based on reference signals, RS, transmitted by a second RAN node;the method further comprises receiving (1025) from the SF a sensing configuration for the second RAN node; andthe UE sensing configuration is determined further based on the sensing configuration for the second RAN node.
9. The method of claim 8, wherein the UE sensing configuration includes or is sent together with the sensing configuration for the second RAN node.
10. The method of any of claims 1-7, wherein:the sensing measurements are based on reference signals, RS, transmitted by the RAN node;the method further comprises receiving (1030) from the SF a muting configuration for the RS transmitted by the RAN node; andthe UE sensing configuration is determined further based on the muting configuration.
11. The method of any of claims 1-10, further comprising sending (1050) the UE sensing configuration to the SF.
12. The method of any of claims 1-11, wherein the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
13. The method of any of claims 1-12, further comprising performing (1070) one or more of the following operations based on the measurement report:adjusting one or more operational settings of the RAN node based on one or more of the sensing measurements included in the measurement report; andforwarding the measurement report to the SF.
14. The method of claim 13, wherein the one or more operational settings relate to at least one of the following: beam management, mobility management of UEs served by the RAN node, and radio resource optimization.
15. The method of any of claims 13-14, further comprising:after forwarding the measurement report to the SF, receiving (1080) from the SF an indication that the sensing measurements have been completed; and performing (1090) one or more of the following in response to the indication: releasing one or more RAN node resources used to facilitate the sensing measurements, and sending to the UE a further indication to release UE resources used for the sensing measurements.
16. The method of any of claims 1-15, wherein one of the following applies:the UE sensing configuration is determined further based on the UE’s current radio resource management, RRM, configuration; orthe method further comprises adjusting (1045) the UE’s current RRM configuration based on the UE sensing configuration, thereby obtaining an adjusted RRM configuration.
17. The method of claim 16, wherein the adjusted RRM configuration is sent to the UE together with the UE sensing configuration.
18. The method of any of claims 16-17, wherein one or more of the following parts of the UE’s current RRM configuration are adjusted to obtain the adjusted RRM configuration: measurement gap configuration; active bandwidth part, BWP, configuration; and discontinuous reception, DRX, configuration.
19. The method of any of claims 1-18, wherein:the sensing measurements are based on first reference signals, RS, transmitted by the RAN node and second RS transmitted by a second RAN node;the method further comprises receiving (1035) from the second RAN node one or more observed time differences, OTDs, between the first RS and the second RS; and the UE sensing configuration is determined further based on the received OTDs.
20. The method of any of claims 1-19, wherein the UE sensing configuration includes or indicates one or more of the following:the list of required sensing measurements;list of cells, beams, and / or transmission reception points, TRPs, to be measured; antenna panel configurations for TRPs to be measured;required or requested measurement granularity;required or requested measurement bandwidth;transmission configuration of reference signals, RS, to be measured, including any muting patterns;a measurement duration; andmeasurement assistance data.
21. The method of any of claims 1-20, wherein the sensing measurements include one or more of the following: one or more Doppler-related measurements; one or more carrier phase-related measurements; one or more timing-related measurements; one or more angular-related measurements; velocity; speed; direction; reference signal received power, RSRP; and reference signal received path power, RSRPP.
22. The method of any of claims 1-21, wherein the SF is one of the following: sensing management function, SeMF; sensing control function, SCF; sensing processing function, SPF; location management function, LMF; or access and mobility management function, AMF.
23. A method for a sensing function, SF, configured to operate with a radio access network, RAN, the method comprising:sending (1140) to a RAN node a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a user equipment, UE, to perform the required sensing measurements; andreceiving (1160) from the RAN node a measurement report that includes the required sensing measurements performed by the UE.
24. The method of claim 23, further comprising receiving (1170), from the UE via the RAN node, a transparent container that includes a UE location determined in conjunction with the sensing measurements.
25. The method of claim 24, wherein one of the following applies: the transparent container is received in the measurement report, or the transparent container is received in a different message than the measurement report.
26. The method of any of claims 23-25, wherein:the method further comprises receiving (1110) sensing configurations from one or more of the following: the RAN node, and a second RAN node; andthe sensing measurement request is based on the received one or more sensing configuration.
27. The method of claim 26, further comprising selecting (1115) at least one of the RAN node and the second RAN node to transmit reference signals, RS, for the sensing measurements, wherein the selection is based on one or more of the following:the sensing configurations of the RAN node and the second RAN node,respective locations of transmission antenna associated with the RAN node and the second RAN node,a required sensing area, anda geometric dilution of precision, GDOP, requirement.
28. The method of claim 27, further comprising, for each selected RAN node:determining (1120) a muting configuration for the RS transmitted by the selected RAN node, wherein the muting configuration is determined based on the sensing configurations for all selected RAN nodes; andsending (1125) the muting configuration to the selected RAN node.
29. The method of any of claims 27-28, wherein the RAN node serves the UE and the method further comprises, when the second RAN node is selected and the RAN node is not selected, sending (1130) to the RAN node the sensing configuration of the second RAN node.
30. The method of any of claims 26-29, wherein each received sensing configuration includes or indicates one or more of the following information related to reference signals, RS, transmitted by the RAN node from which the sensing configuration is received:type;time and / or frequency resources;carrier frequency;bandwidth or bandwidth combination;pulse duration;pulse periodicity or aperiodic configuration;comb configuration;muting pattern;cyclic prefix, CP, length;sub-carrier spacing, SCS;number of sensing resources or resource sets; andtime offset with respect to a reference time on the RAN node radio interface.
31. The method of claim 30, wherein each received sensing configuration indicates one or more of the information related to RS based on an index to or identifier of a predetermined set of parameters.
32. The method of any of claims 23-31, further comprising receiving (1150) from the RAN node a UE sensing configuration that was determined by the RAN node based on the sensing measurement request.
33. The method of claim 32, wherein the UE sensing configuration includes or indicates one or more of the following:the list of required sensing measurements;list of cells, beams, and / or transmission reception points, TRPs, to be measured; antenna panel configurations for TRPs to be measured;required or requested measurement granularity;required or requested measurement bandwidth;transmission configuration of reference signals, RS, to be measured, including any muting patterns;a measurement duration; andmeasurement assistance data.
34. The method of any of claims 23-33, wherein the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
35. The method of any of claims 23-34, further comprising:determining (1180) a sensing result based on the received measurement report; and sending (1190) to the RAN node an indication that the required sensing measurements have been completed.
36. The method of any of claims 23-35, wherein the required sensing measurements include one or more of the following: one or more Doppler-related measurements; one or more carrier phase-related measurements; one or more timing-related measurements; one or more angular-related measurements; velocity; speed; direction; reference signal received power, RSRP; and reference signal received path power, RSRPP.
37. The method of any of claims 23-36, wherein the SF is one of the following: sensing management function, SeMF; sensing control function, SCF; sensing processing function, SPF; location management function, LMF; or access and mobility management function, AMF.
38. A method for a user equipment, UE, configured to support sensing measurements in a radio access network, RAN, the method comprising:receiving (1220), from a RAN node, a UE sensing configuration that includes a list of sensing measurements to be performed;performing (1230) the sensing measurements in accordance with the UE sensing configuration, wherein the sensing measurements are performed on reference signals, RS, transmitted by one or more of the following: the RAN node, and a second RAN node; andsending (1240) to the RAN node a measurement report that includes the sensing measurements.
39. The method of claim 38, further comprising sending (1210) to the RAN node an indication of UE sensing capabilities, wherein the UE sensing configuration is based on the UE sensing capabilities.
40. The method of any of claims 38-39, further comprising:determining (1250) a UE location in conjunction with the sensing measurements; and sending (1260) the UE location to a sensing function, SF, operatively coupled to the RAN, wherein the UE location is sent via the RAN node in a transparent container.
41. The method of claim 40, wherein one of the following applies: the transparent container is included with the measurement report, or the transparent container is sent in a different message than the measurement report.
42. The method of any of claims 40-41, wherein the SF is one of the following: sensing management function, SeMF; sensing control function, SCF; sensing processing function, SPF; location management function, LMF; or access and mobility management function, AMF.
43. The method of any of claims 40-42, wherein the sensing measurements are performed on RS transmitted by the second RAN node, and the UE sensing configuration includes or is received together with a sensing configuration for the second RAN node.
44. The method of any of claims 38-43, wherein the sensing measurement request also includes or indicates one or more of the following: required or requested measurement granularity, and a maximum response time for the sensing measurements.
45. The method of any of claims 38-44, further comprising, after sending (1240) the measurement report, receiving (1270) from the RAN node an indication to release UE resources used for the sensing measurements.
46. The method of any of claims 38-45, wherein one of the following applies:the UE sensing configuration is based on the UE’s current radio resource management, RRM, configuration; orthe method further comprises receiving (1225) from the RAN node an adjusted RRM configuration that is based on the UE’s current RRM configuration and the UE sensing configuration.
47. The method of claim 46, wherein the adjusted RRM configuration is received together with the UE sensing configuration.
48. The method of any of claims 46-47, wherein one or more of the following parts of the UE’s current RRM configuration have been adjusted to obtain the adjusted RRM configuration: measurement gap configuration; active bandwidth part, BWP, configuration; and discontinuous reception, DRX, configuration.
49. The method of any of claims 38-48, wherein the UE sensing configuration also includes or indicates one or more of the following:list of cells, beams, and / or transmission reception points, TRPs, to be measured; antenna panel configurations for TRPs to be measured;required or requested measurement granularity;required or requested measurement bandwidth;transmission configuration of reference signals, RS, to be measured, including any muting patterns;a measurement duration; andmeasurement assistance data.
50. The method of any of claims 38-49, wherein the sensing measurements include one or more of the following: one or more Doppler-related measurements; one or more carrier phase-related measurements; one or more timing-related measurements; one or more angular-related measurements; velocity; speed; direction; reference signal received power, RSRP; and reference signal received path power, RSRPP.
51. Radio access network, RAN, node (220, 521, 522, 720, 920, 1310, 1410, 1600, 1702) configured to facilitate sensing measurements by user equipment, UEs (210, 510, 710, 910, 1312, 1412, 1500), the RAN node comprising communication interface circuitry (1606, 1704) and processing circuitry (1602, 1704) that are operatively coupled and are configured to:receive, from a sensing function, SF (530, 540, 550, 560, 630, 730, 830, 930) operatively coupled to the RAN, a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a UE to perform the required sensing measurements;determine a UE sensing configuration based on the sensing measurement request; send the UE sensing configuration to the UE; andreceive from the UE a measurement report that includes the required sensing measurements.
52. The RAN node of claim 51, wherein the communication interface circuitry and the processing circuitry are further configured to perform operations corresponding to the methods of any of claims 2-22.
53. Radio access network, RAN, node (220, 521, 522, 720, 920, 1310, 1410, 1600, 1702) configured to facilitate sensing measurements by user equipment, UEs (210, 510, 710, 910, 1312, 1412, 1500), the RAN node being further configured to:receive, from a sensing function, SF (530, 540, 550, 560, 630, 730, 830, 930) operatively coupled to the RAN, a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a UE to perform the required sensing measurements;determine a UE sensing configuration based on the sensing measurement request; send the UE sensing configuration to the UE; andreceive from the UE a measurement report that includes the required sensing measurements.
54. The RAN node of claim 53, being further configured to perform operations corresponding to the methods of any of claims 2-22.
55. Non-transitory, computer-readable medium (1604, 1704) storing computer-executable instructions that, when executed by processing circuitry (1602, 1704), cause the method of any of claims 1-22 to be performed by the RAN node (220, 521, 522, 720, 920, 1310, 1410, 1600, 1702) configured to facilitate sensing measurements by UEs (210, 510, 710, 910, 1312, 1412, 1500).
56. Computer program product (1604a, 1704a) comprising computer-executable instructions that, when executed by processing circuitry (1602, 1704), cause the method of any of claims 1-22 to be performed by the RAN node (220, 521, 522, 720, 920, 1310, 1410, 1600, 1702) configured to facilitate sensing measurements by UEs (210, 510, 710, 910, 1312, 1412, 1500).
57. Network equipment (1308, 1432, 1600, 1700) configured to implement a sensing function, SF (530, 540, 550, 560, 630, 730, 830, 930) operatively coupled to a radio access network, RAN (520, 1304), the network equipment comprising communication interface circuitry (1606, 1704) and processing circuitry (1602, 1704) that are operatively coupled and are configured to:send to a RAN node (220, 521, 522, 720, 920, 1310, 1410, 1600, 1702) a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a user equipment, UE (210, 510, 710, 910, 1312, 1412, 1500) to perform the required sensing measurements; and receive from the RAN node a measurement report that includes the required sensing measurements performed by the UE.
58. The network equipment of claim 57, wherein the communication interface circuitry and the processing circuitry are further configured to perform operations corresponding to the methods of any of claims 24-37.
59. Network equipment (1308, 1432, 1600, 1700) configured to implement a sensing function, SF (530, 540, 550, 560, 630, 730, 830, 930) operatively coupled to a radio access network, RAN (520, 1304), the network equipment being further configured to:send to a RAN node (220, 521, 522, 720, 920, 1310, 1410, 1600, 1702) a sensing measurement request that includes or identifies the following: a list of required sensing measurements, and a user equipment, UE (210, 510, 710, 910, 1312, 1412, 1500) to perform the required sensing measurements; and receive from the RAN node a measurement report that includes the required sensing measurements performed by the UE.
60. The network equipment of claim 59, being further configured to perform operations corresponding to the methods of any of claims 24-37.
61. Non-transitory, computer-readable medium (1604, 1704) storing computer-executable instructions that, when executed by processing circuitry (1602, 1704), cause the method of any of claims 23-37 to be performed by the SF (530, 540, 550, 560, 630, 730, 830, 930) configured to operate with the RAN (520, 1304).
62. Computer program product (1604a, 1704a) comprising computer-executable instructions that, when executed by processing circuitry (1602, 1704), cause the method of any of claims 23-37 to be performed by the SF (530, 540, 550, 560, 630, 730, 830, 930) configured to operate with the RAN (520, 1304).
63. User equipment, UE (210, 510, 710, 910, 1312, 1412, 1500) configured to support sensing measurements in a radio access network, RAN (520, 1304, 1420), the UE comprising communication interface circuitry (1512) and processing circuitry (1502) that are operatively coupled and are configured to:receive, from a RAN node (220, 521, 522, 720, 920, 1310, 1410, 1600, 1702), a UE sensing configuration that includes a list of sensing measurements to be performed;perform the sensing measurements in accordance with the UE sensing configuration, wherein the sensing measurements are performed on reference signals, RS, transmitted by one or more of the following: the RAN node, and a second RAN node (940); andsend to the RAN node a measurement report that includes the sensing measurements.
64. The UE of claim 63, wherein the communication interface circuitry and the processing circuitry are further configured to perform operations corresponding to the methods of any of claims 39-50.
65. User equipment, UE (210, 510, 710, 910, 1312, 1412, 1500) configured to support sensing measurements in a radio access network, RAN (520, 1304, 1420), the UE being further configured to:receive, from a RAN node (220, 521, 522, 720, 920, 1310, 1410, 1600, 1702), a UE sensing configuration that includes a list of sensing measurements to be performed;perform the sensing measurements in accordance with the UE sensing configuration, wherein the sensing measurements are performed on reference signals, RS,transmitted by one or more of the following: the RAN node, and a second RAN node (940); andsend to the RAN node a measurement report that includes the sensing measurements.
66. The UE of claim 65, being further configured to perform operations corresponding to the methods of any of claims 39-50.
67. Non-transitory, computer-readable medium (1510) storing computer-executable instructions that, when executed by processing circuitry (1502), cause the method of any of claims 38-50 to be performed by the UE (210, 510, 710, 910, 1312, 1412, 1500) configured to support sensing measurements in the RAN (520, 1304, 1420).
68. Computer program product (1514) comprising computer-executable instructions that, when executed by processing circuitry (1502), cause the method of any of claims 38-50 to be performed by the UE (210, 510, 710, 910, 1312, 1412, 1500) configured to support sensing measurements in the RAN (520, 1304, 1420).
