Techniques for transport of sensing measurements in a network

Abstract

Embodiments include methods for a user equipment (UE) configured for sensing and communication in a radio access network (RAN). Such methods include receiving a request to perform sensing measurements associated with one or more sensing services and performing sensing measurements in accordance with the request. Such methods include sending a sensing measurement report that includes results of the sensing measurements. The sensing measurement report is sent via one or more of the following: a sensing processing protocol (SPP) between the UE and a sensing function in a core network coupled to the RAN; and a sensing radio bearer (SeRB) that is terminated at the sensing function or at a RAN node serving the UE. Other embodiments include complementary methods for a RAN node, as well as UEs and RAN nodes configured to perform such methods.

Description

[0001] TECHNIQUES FOR TRANSPORT OF SENSING MEASUREMENTS IN A NETWORK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to wireless networks, and more specifically to techniques for transporting sensing measurements made by user equipment (UEs) and radio access network (RAN) nodes operating in a wireless network (e.g., for integrated sensing and communications).

[0004] BACKGROUND

[0005] The fifth generation (“5G”) of cellular systems has been standardized within the Third- Generation Partnership Project (3GPP). 5G is developed for maximum flexibility to support various use cases including enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device- to-device (D2D), and several others. 5G was initially specified in Release 15 (Rel-15) and continues to evolve through subsequent releases.

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

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

[0008] 3GPP TR 22.837 (v!9.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 (IS AC).

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

[0010] A sensing request may originate from applications internal or external to the network. 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). 3GPP has also defined sensing units (SUs, also called sensing radio units, SRUs) 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.

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

[0012] SUMMARY

[0013] When a UE is involved in sensing operations, it may collect raw sensing measurements and forward those to the network without significant processing at the UE. In some cases, the amount of data in these measurements can be very large - in fact, much larger than conventional UE measurements carried by SRBs. As such, it is unclear whether UE sensing measurements should also be carried by existing SRBs (e.g., SRB1, SRB2) or instead by DRBs. Each of these options may have advantages and disadvantages. New solutions are needed.

[0014] An object of embodiments of the present disclosure is to improve transport of sensing measurements made by UEs in a RAN, such as by providing, enabling, and / or facilitating solutions to exemplary problems summarized above and described in more detail below.

[0015] Embodiments include methods (e.g., procedures) performed by a UE configured for sensing and communication in a RAN.

[0016] These exemplary methods include receiving a request to perform sensing measurements associated with one or more sensing services. These exemplary methods also include performing sensing measurements in accordance with the request and sending a sensing measurement report that includes results of the sensing measurements. The sensing measurement report is sent via one or more of the following: a sensing processing protocol (SPP) between the UE and a sensing function in a core network (CN) coupled to the RAN, and a sensing radio bearer (SeRB) that is terminated at the sensing function or at a RAN node serving the UE.

[0017] Other embodiments include exemplary methods (e.g., procedures) performed by a RAN node configured for sensing and communication with UEs. These embodiments are complementary to UE embodiments summarized above.

[0018] These exemplary methods include sending, to a UE, a request to perform sensing measurements associated with one or more sensing services. These exemplary methods also include receiving, from the UE, a sensing measurement report that includes results of sensing measurements performed in accordance with the request. The sensing measurement report is received via one or more of the following: an SPP between the UE and a sensing function in a CN coupled to the RAN, and an SeRB that is terminated at the sensing function or at the RAN node.

[0019] In some embodiments, these exemplary methods also include sending the results in the sensing measurement report, or information derived therefrom, to the sensing function in the CN. In some of these embodiments, these exemplary methods also include determining whether the results in the sensing measurement report include one or more of the following: raw measurement results, and at least partially processed measurement results.

[0020] Furthermore, when it is determined that the sensing measurement report includes at least partially processed measurement results, the at least partially processed measurement results are sent to the sensing function. Also, when it is determined that the sensing measurement report includes raw measurement results, these exemplary methods also include processing the raw measurement results to derive processed results, with the processed results being sent to the sensing function. In some variants of these embodiments, the raw measurement results are processed by a sensing processing function (SPF) in the RAN node or in another RAN node.

[0021] In some of these embodiments, the sensing function in the CN is one of the following: a sensing processing function (SPF), or a sensing management function (SeMF). In some of these embodiments, the RAN node includes a relay function that translates at least one first protocol layer used to receive the sensing measurement report from the UE to corresponding at least one second protocol layer used to send the results, or the information derived therefrom, to the sensing function in the CN.

[0022] In other of these embodiments, the sensing measurement report is received from the UE via the SeRB terminated in the RAN node and the results in the sensing measurement report, or the information derived therefrom, are sent to the sensing function via the SPP and one of the following as a next-lower protocol layer: hypertext transport protocol (HTTP), or file transfer protocol (FTP).

[0023] Various embodiments summarized above may have additional features, such as summarized below.

[0024] In some embodiments, the SeRB is terminated at the sensing function and the results are included in the sensing measurement report in a format or container that is accessible to the RAN node. In some embodiments, the sensing measurement report is sent / received via the SPP in conjunction with packet data convergence protocol (PDCP) as a next-lower protocol layer. In some of these embodiments, the PDCP includes a configurable size of a sequence number assigned to protocol data units (PDUs) received from the SPP.

[0025] In some embodiments, the sensing measurement report is sent / received via the SPP and the SeRB and the request is received via the SPP. Also, these exemplary methods also include the UE receiving from the RAN node (or the RAN node sending to the UE) via a radio resource control (RRC) protocol, a configuration of the SPP and the SeRB.

[0026] In some of these embodiments, the configuration of the SeRB includes a recoverPDCP field that causes a first protocol layer immediately below SPP to retransmit first PDUs previously submitted to a second protocol layer immediately below the first protocol layer, upon reconfiguration of the SeRB by the RAN. In other of these embodiments, the configuration of the SeRB includes a discardOnPDCP field that causes the first protocol layer to discard the first protocol layer PDUs previously submitted to the second protocol layer, upon reconfiguration of the SeRB by the RAN.

[0027] In some of these embodiments, the configuration of the SeRB includes an indication to apply integrity protection to SPP PDUs submitted to a next-lower protocol layer.

[0028] In some embodiments, the results are raw measurement results and the sensing measurement report is sent / received via a sensing data radio bearer (SeDRB) and / or a first type of SPP message. In other embodiments, the results are processed measurement results and the sensing measurement report is sent / received via a sensing control radio bearer (SeCRB) and / or a second type of SPP message.

[0029] In some embodiments, the sensing measurement report is sent via the SeRB, which is mapped to a first logical channel (LCH) having a transmission priority with one or more of the following characteristics:

[0030] • greater than transmission priorities of one or more second LCHs mapped to data radio bearers (DRBs) used for user plane (UP) communication with the RAN / UE; and

[0031] • lower than transmission priorities of one or more third LCHs mapped to signaling radio bearers (SRBs) used for control plane (CP) communication with the RAN / UE.

[0032] In some of these embodiments, the transmission priority of the first LCH is also lower than transmission priorities of one or more fourth DRBs used for UP communication with the RAN / UE. In some of these embodiments, the first, second, and third LCHs are associated with respective LCH identifiers (IDs), with the respective transmission priorities of the first, second, and third LCHs being inversely related to increasing numerical order of the associated LCH IDs.

[0033] In some of these embodiments, the first LCH is assigned to a first logical channel group (LCG) and the one or more third LCHs are assigned to a second LCG. In other of these embodiments, the first LCH is not assigned to any LCG. In some of these embodiments, the first LCH is a sensing transport channel (STCH), the one or more second LCHs are dedicated transport channels (DTCHs), and the one or more third LCHs are dedicated control channels (DCCHs).

[0034] In some embodiments, the sensing measurement report includes an indication that the results include one or more of the following: raw measurement results, semi-processed measurement results, or fully processed measurement results. In some embodiments, the one or more sensing services include one or more of the following: object detection, spatial mapping, weather monitoring, and unmanned aerial vehicle (UAV) positioning.

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

[0036] These and other embodiments described herein may provide various benefits and / or advantages. For example, by implementing a new radio bearer to carry sensing-related information, embodiments may avoid delay and UE performance degradation that may occur if this sensing-related information is multiplexed with other conventional UE measurements on SRBs. Moreover, embodiments may also avoid certain undesirable characteristics of conventional SRBs, such as the inability to recover PDCP data and the need for reestablishment after handover. Similarly, embodiments may avoid certain undesirable characteristics of conventional DRBs, such as the lack of visibility of DRB content to RAN nodes, which may need the sensing-related information. Furthermore, embodiments enable a flexible RAN-CN interface that facilitates different placements of SPF within a network. 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.

[0037] BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 shows a high-level view of an exemplary 5G network architecture.

[0039] Figure 2 shows an exemplary configuration of 5G user plane (UP) and control plane (CP) protocol stacks.

[0040] Figure 3 shows a high-level architecture for positioning in 5G networks.

[0041] Figure 4 shows various sensing techniques that can be used in a 5G network to detect and / or localize a target (e.g., pedestrian).

[0042] Figure 5 shows a high-level architecture for ISAC and positioning in 5G networks.

[0043] Figure 6 shows a high-level architecture for ISAC in 5G and / or 6G networks.

[0044] Figure 7 shows an exemplary protocol stack, according to some embodiments of the present disclosure.

[0045] Figure 8 shows an exemplary ASN. 1 data structure for a sensing processing protocol (SPP) protocol data unit (PDU), according to some embodiments of the present disclosure.

[0046] Figure 9 shows an exemplary ASN.l data structure for a MeasurementReportSensing message, according to some embodiments of the present disclosure.

[0047] Figure 10 shows exemplary protocol layers between a RAN node and an SeMF or SPF, according to some embodiments of the present disclosure.

[0048] Figure 11 shows exemplary protocol layers between a UE, a RAN node, and an SeMF or SPF, according to some embodiments of the present disclosure.

[0049] Figure 12 shows a flow diagram of an exemplary method (e.g., procedure) for a UE, according to various embodiments of the present disclosure.

[0050] Figure 13 shows a flow diagram of an exemplary method (e.g., procedure) for a RAN node, according to various embodiments of the present disclosure.

[0051] Figure 14 shows a communication system according to some embodiments of the present disclosure.

[0052] Figure 15 shows a UE according to various embodiments of the present disclosure.

[0053] Figure 16 shows a network node according to some embodiments of the present disclosure.

[0054] Figure 17 shows a virtualization environment in which some embodiments of the present disclosure may be virtualized. DETAILED DESCRIPTION

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

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

[0057] Furthermore, the following terms are used throughout the description given below:

[0058] • 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 access network (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.

[0059] • 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), aPDN 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 (LMF), or the like. • 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”.

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

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

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

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

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

[0065] Figure 1 illustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation Radio Access Network (NG-RAN, 199) and a5G 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.

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

[0067] NG RAN logical nodes (e.g., gNBs 1 lOa-b) may include a Central Unit (CU) and one or more Distributed Units (DUs). CUs are logical nodes that host higher-layer protocols and perform various 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.

[0068] Figure 2 shows an exemplary configuration of NR 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 Figures 1-2. The Physical (PHY), Medium Access Control (MAC), Radio Link 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. 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.

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

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

[0071] 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, RRC controls addition, modification, and release of carrier aggregation (CA) and dual-connectivity (DC) configurations for UEs, and performs various security functions such as key management.

[0072] 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 RRCJDLE 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. Each SRB or DRB is associated with one PDCP entity and mapped to a logical channel in lower layers for transmission and reception. SRBs and DRBs differ in how they are configured on the radio interface between UE and NG-RAN as well as operations on the interface between NG- RAN and 5GC. some default configuration for SRBs.

[0073] For example, SRBs carry UE radio configurations associated with a specific RAN node (e.g., gNB) and / or cell. After PDCP entity re-establishment, a UE will discard all stored PDCP SDUs and PDCP PDUs for an SRB. Moreover, the RAN may configure an SRB with a discardOnPDCP flag that causes a UE to also discard stored PDCP PDU / SDUs upon receiving a RRC reconfiguration that does not trigger PDCP entity re-establishment but changes resource configurations. DRBs cannot be configured with a discardOnPDCP flag.

[0074] As another example, the amount of CP data carried on SRBs is relatively small (e.g., compared to UP data carried on DRBs) and must be reliably received. SRBs include some default configurations to facilitate reliable delivery, such as presence of a 32-bit MAC-I (Message Authentication Code for Integrity) field in PDCP PDUs, use of RLC acknowledged mode (AM), etc. These default configurations are not used for DRBs.

[0075] As another example, default configurations for SRB1 and SRB2 are used to reduce size of RRC messages carried by these SRBs, which increases likelihood of successful reception of these RRC messages even in bad radio conditions, which facilitates a UE reaching the correct RRC state during RRC reestablishment and resume procedures. Such default configurations are not used for DRBs.

[0076] As another example, DRBs are configured to carry UP data. In RLC AM, a DRB one can be configured for PDCP recovery (e.g., via recoverPDCP field) so that the data is retransmitted in a target cell after handover from a source cell. SRBs cannot be configured with a recoverPDCP field.

[0077] As another example, RAN nodes (e.g., gNBs) are able to access content of a message (e.g., RRC) from a UE on an SRB and deliver relevant information from the message to the 5GC (e.g., AMF) using NGAP / SCTP protocols. In contrast, each DRB is associated with a QoS flow that is linked to a PDU session anchored at a UPF. As such, the RAN node is unable to access content of UP messages carried on DRBs.

[0078] As mentioned above, UEs transmit measurements to the RAN using SRBs. For example, a UE may transmit positioning measurements using SRB2 and mobility-related measurements using SRB1. Each one of these SRBs is mapped to a logical channel in the lower layer radio protocols, with SRB1 having a higher priority than SRB2 and both having a higher priority than DRBs. In addition, SRB4 is used to carry RRC messages that contain application layer measurement reports. SRB4 has a lower priority than SRB1 and can only be configured by the network after AS security activation.

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

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

[0081] Figure 3 is a block diagram illustrating a high-level architecture for supporting UE positioning in NR 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).

[0082] 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 location estimate from the UE, obtaining UL location measurements from the NG RAN, and obtaining non-UE associated assistance data from the NG RAN.

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

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

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

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

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

[0088] In any of these cases, the receiver may perform one or more of the following sensing measurements on the received sensing signals: • 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)

[0089] • Signal strength, signal quality, signal-to-noise ratio, etc.

[0090] • Phase measurement;

[0091] • Channel impulse response, multipath characteristics, power delay profile;

[0092] • Delay spread, Doppler spectra, Doppler spread, Doppler shift, Doppler frequency;

[0093] • Velocity, angle of arrival, angle of departure; and

[0094] • Samples of “raw” radio signal values, e.g., in-phase (I) and quadrature (Q) representation.

[0095] These various measurements may be processed to obtain information about the target and its surroundings that affected the transmitted sensing signals, including one or more of the following:

[0096] • Characteristics (shape, size, number, etc.) of target and / or obstacles ;

[0097] • Velocity of target and / or obstacles;

[0098] • Weather conditions (e.g., rain);

[0099] • Recognition of objects (e.g., wall, blocker, scatterer, etc.).

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

[0101] A sensing request may originate from applications internal or external to the network. 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 multiple network 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.

[0102] 3GPP has also defined SUs 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). SeMF may be deployed in the same or different communications network as all or some of the SUs that provide the sensing results. For example, one or more SUs may be in a 5G network while the associated SeMF is in a 6G network (or vice versa).

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

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

[0105] 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. SPF may be deployed in the same or different communications network as all or some of the Sus that provide the sensing results. For example, one or more SUs may be in a 5G network while the associated SPF is in a 6G network (or vice versa).

[0106] Figure 5 illustrates a high-level architecture for ISAC and positioning in 5G / NR networks. In particular, Figure 5 illustrates how SeMF, SPF, and SUs 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 via a Cl interface, with the AMF 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.

[0107] 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. Figure 6 shows another high-level 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). This function indirectly configures measurement nodes - including Tx and Rx base stations (BSs) and UEs - and a sensing processing function (SPF) via CP. After measurements have been performed, results are sent to the SPF 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 in this exemplary architecture.

[0108] When a UE is involved in sensing, the UE needs to be connected to the network via a serving BS. Even 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.

[0109] 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 fusion information 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.

[0110] When a UE (or SU) is involved in sensing operations, it may collect raw sensing measurements (e.g., I / Q radio signal samples) and forward those to the network without significant processing at the UE. In some cases, the amount of data in these measurements can be very large - in fact, much larger than conventional UE measurements carried by SRBs. As such, it is unclear whether UE sensing measurements should also be carried by existing SRBs (e.g., SRB1, SRB2) or instead by DRBs. Each of these options may have advantages and disadvantages.

[0111] For example, if these sensing measurements are sent via SRB (e.g., in RRC message), they are either processed by the RRC layer in the receiving RAN node (similar to UE measurement report) or forwarded to the AMF via NAS signaling (similar to positioning data). As noted above, SRBs are given high priority but carry relatively small amounts of data, which generally does not interfere with or delay transmission of other important information. However, when SRBs are used to carry a large amount of data in “raw” sensing measurements, this high-priority transmission of this large amount of data may interfere with or delay transmission of other important information, which may significantly degrade UE performance (e.g., for mobility operations). Further, sensing is expected to come with a large volume of IQ samples for measurements to process. High-priority transmission of this large amount of data may also create bottleneck in the network.

[0112] On the other hand, if these sensing measurements are sent via DRB, they are directly forwarded to the UPF by the receiving RAN node, which has no visibility into the contents. If the sensing measurements are needed by the RAN node, the UPF (or other CN node) must determine this and forward them back to the RAN node, which adds undesirable delay,.

[0113] Embodiments of the present disclosure address these and other problems, issues, and / or difficulties by a novel and inventive sensing radio bearer configuration with properties that are not supported by conventional SRBs and DRBs. These sensing radio bearers may be used exclusively to carry UE sensing-related information such as physical measurements, data generated using artificial intelligence / machine learning (AI / ML) models, etc. Preferably, these sensing radio bearers may be used to carry a large amount of sensing-related information that is obtained by the UE but is unrelated to other UE applications or services that generate UP data.

[0114] When a RAN node receives sensing-related information from the UE via a sensing radio bearer, the RAN node processes such information and / or delivers the raw or processed sensing- related information to the core network (e.g., SCF, SPF) as needed. Embodiments described herein include various features of this sensing radio bearer and how it integrates into a RAN sensing protocol stack, including the following:

[0115] • Techniques for a UE to provide sensing-related information categorized as raw, semiprocessed or fully processed.

[0116] • Techniques for transport of sensing-related information from RAN node to SPF, in which a RAN node interacts with SPF based on a web-based, client-server arrangement. For example, the RAN node may continuously upload (“push”) the sensing-related information to SPF, the SPF may pull the sensing-related information from the RAN node, or a combination thereof.

[0117] • Techniques for transport of sensing-related information from UE to SPF, in which an intermediate RAN node may perform deep inspection of the sensing-related information received from the UE and perform further processing before sending it to SPF.

[0118] Embodiments described herein may be applicable to wireless integrated sensing and communication (ISAC) networks, such as in conjunction with 5G and / or 6G networks.

[0119] Embodiments may provide various benefits and / or advantages. For example, by implementing a new radio bearer to carry sensing-related information, embodiments may avoid delay and UE performance degradation that may occur if this sensing-related information is multiplexed with other conventional UE measurements on SRBs. Moreover, embodiments may also avoid certain undesirable characteristics of conventional SRBs, such as the inability to recover PDCP data and the need for reestablishment after handover. Similarly, embodiments may avoid certain undesirable characteristics of conventional DRBs, such as the lack of visibility of DRB content to RAN nodes, which may need the sensing-related information. Furthermore, embodiments enable a flexible RAN-CN interface that facilitates different placements of SPF within a network.

[0120] Embodiments of the novel radio bearer will be described below in the context of notable differences from conventional SRBs and DRBs. In the following description, the novel radio bearer will be referred to as a “sensing radio bearer” or “SeRB” for short. However, this name is merely for convenience of description and the novel radio bearer may also be an SRB or a DRB that has the same characteristics as the SeRB described below.

[0121] In some embodiments, a new protocol layer can be used to carry sensing-related information, with the messages of this new protocol layer being carried by SeRB. In the following description, this new protocol layer will be referred to as Sensing Processing Protocol (SPP). Figure 7 shows an exemplary protocol stack, according to some embodiments of the present disclosure. In this exemplary protocol stack, SPP layer is on top of PDCP, e.g., instead of SDAP as shown in Figure 2. However, SPP may also be used over or any similar and / or equivalent lower layer transport protocol used in 5G, 6G, or other networks.

[0122] In some embodiments, SPP may include specific data formats for the sensing-related information that may be accessible to the AS (e.g., RAN node). Alternately or additionally, SPP may include data containers that carry sensing-related information from UE to SeMF and are transparent (or inaccessible) to an intermediate RAN node.

[0123] In some variants, SPP message formats may be defined based on ASN.1 data structures in a similar manner as other 3GPP-specified protocols such as RRC, LPP, etc. Figure 8 shows an exemplary ASN.1 data structure that defines a generic SPP protocol data unit (PDU), according to some embodiments of the present disclosure.

[0124] In some embodiments, the RRC layer is used to configure an SeRB, mechanisms to deliver the data by lower radio layers (e.g., PDCP, RLC), and the resources used for sensing. On the other hand, the SPP layer is used to configure the required sensing measurements (e.g., triggering conditions, reporting frequency, etc.).

[0125] In some embodiments, upon (re)-configuration (e.g., modification) of an SeRB, the transmitting side of the next-lower protocol layer (e.g., PDCP in Figure 7) performs retransmissions of all the lower layer PDUs (e.g., PDCP data PDUs) previously submitted to other lower layers (e.g., RLC in Figure 7). This is useful to avoid PDU loss when a UE is handed over between RAN nodes. In some variants, this behavior may be network-configurable, such as by a recoverPDCP field that is conventionally used for DRBs but not for SRBs. In some variants, recoverPDCP behavior may be used only when SPP data is being carried by lower layer (e.g., RLC) acknowledged mode (AM), since it is not feasible when SPP data is being carried by lower layer (e.g., RLC) unacknowledged mode (UM). In other variants, recoverPDCP behavior is network-configurable based on type of sensing used. For example, the network configures recoverPDCP behavior when UE sensing measurements are valid across multiple cells and / or RAN nodes that serve the UE. Since a UE senses its surrounding environment, its sensing measurements may be applicable across cells such as when sensing reference signals are common within an area. In such case, it is useful to have recoverPDCP behavior for SeRB and not discard sensing measurements upon handover, which is a default action for conventional SRBs.

[0126] In other embodiments, upon (re)-configuration (e.g., a modification) of an SeRB, the transmitting side of the next-lower protocol layer (e.g., PDCP in Figure 7) discards PDCP SDUs along with the corresponding PDCP data PDUs. This is useful when the SeRB and resource configurations for sensing are modified such that unreported sensing measurements are no longer valid and must be discarded. In some variants, this behavior may be network-configurable, such as by a discardOnPDCP field that is conventionally used for SRBs but not for DRBs.

[0127] In some embodiments, the next-lower protocol layer (e.g., PDCP in Figure 7) may use sequence numbers for PDUs and / or SDUs. In some of these embodiments, the number of bits of the sequence number in the next-lower protocol layer is configurable (e.g., 12 bits or 18 bits). Note this parameter is configurable for conventional DRBs but fixed to 12 bits for conventional SRBs.

[0128] In some embodiments, an SeRB may be configured to use integrity protection. In such case, a MAC-I field is included in PDUs to / from the next-lower protocol layer (e.g., PDCP in Figure 7). If integrity protection is not configured, the MAC-I field is not included in these PDUs. This behavior is similar to conventional DRBs, while the MAC-I field is always present for conventional SRBs but contains padding bits set to zero when integrity protection is not configured.

[0129] In some embodiments, an SeRB may be one of two sub-types: sensing control radio bearer (SeCRB) and sensing data radio bearer (SeDRB). Each may have a different configuration and the SeCRB (which may be used to carry processed data, and configuration of such of the sensing) has a higher priority than the SeDRB (which may be used to carry raw data).

[0130] In some embodiments, an SeRB may be configured by the network only after AS security activation.

[0131] In some embodiments, an SeRB is mapped to a default logical channel (LCH) with a predefined ID. The priority of this LCH is lower than the priority of the LCHs for SRBs but higher than the priority of the LCHs for DRBs. For example, the priority may be inversely related to the ID (e.g., lower ID, higher priority). In other embodiments, the priority of this default LCH is configurable by the network. In other embodiments, the priority of this LCH mapped to SeRB is fixed but with a lower priority than some predetermined number (e.g., two) of DRBs, so that higher priority UP data on these DRBs is not stalled by sensing-related information carried by the SeRB.

[0132] In some variants, this LCH mapped to SeRB may be assigned to any logical channel group (LCG) except LCGO, which is reserved for higher-priority SRBs (e.g., SRB1, SRB2, SRB3). In other variants, this LCH mapped to SeRB may not be assigned to any LCG so that the availability of data from this LCH alone (i.e., no other data from other LCHs) does not trigger the UE to request UL resources for transmissions via buffer status report (BSR) or scheduling request (SR).

[0133] In some variants, this LCH is not a conventional dedicated transport channel (DTCH) nor a conventional dedicated control channel (DCCH), but rather a newly defined type with the desirable properties discussed above. For example, this new type may be referred to as a sensing transport channel (STCH).

[0134] In some embodiments, the UE can indicate in the UL report whether the sensing-related information in the measurement report includes raw data, semi-processed data or full processed data. Some illustrative examples are given below.

[0135] As one example, the measurement report may contain only fully processed data indicating that the UE has identified, detected, or sensed an unmanned aerial vehicle (UAV). This information is transmitted using a dedicated SPP message via an SeRB, or via an SeCRB in case of the dual-type SeRB according to certain variants discussed above.

[0136] As another example, when the measurement report contains only raw data, this information is transferred using a different dedicated SPP message via an SeRB or via an SeDRB in case of the dual-type SeRB according to the variants discussed above.

[0137] As another example, when the measurement report contains both raw data and processed data, then the information is transferred using a different dedicated SPP message via an SeRB or via an SeDRB in case of the dual-type SeRB according to the variants discussed above. In some variants, the SPP message may contain separate fields for the raw and processed data. In some variants, a RAN node receiving such a message may transparently send the processed data to SPF but further process the raw data before sending the processed raw data to the SPF.

[0138] Considering the following example use case of an SeRB and SPP, according to some embodiments. In this example, a UE and a RAN are jointly creating a spatial map of an environment surrounding the UE in the RAN’s coverage area. When the UE performs a measurement and detects a deviation in the environment from a current version of the spatial map, it transmits a sensing (or measurement) report to the RAN, which uses the reported information to update its own current version of the spatial map. Multiple UEs in the RAN coverage area may be participating in this mapping of the environment, and when one UE provides a sensing report with an update to the RAN, the RAN can then distribute this update to all other UEs participating in the mapping. In this example, SeRBs and the SPP layer may be used to carry the sensing reports and the synchronization information for the distributed spatial map.

[0139] Figure 9 shows an exemplary ASN.l data structure for a MeasurementReportSensing message, according to some embodiments of the present disclosure. This exemplary message is used for a UE to send fully processed, semi-processed, and unprocessed (or raw) sensing-related information via an SeRB. It may also be sent via RLC AM using a sensing transport channel (STCH), which could be a newly defined logical channel type with higher priority than any other DTCH.

[0140] In some embodiments, the CN may send the RAN a request for a UE to participate in sensing measurements that indicates one or more QoS flows (or related parameters) for a sensing service associated with the sensing measurements. In some embodiments, the CN may provide the RAN with a list of QoS flows associated with respective sensing services such as detection, tracking, weather monitoring, UAV positioning, etc.

[0141] In some embodiments, the RAN may perform mapping of sensing QoS flows to SeRBs based on the sensing processing capacity of the sensing system, which may include or be related to any of the following aspects:

[0142] • Processing capacity of data plane pipeline, which may be indicated by a maximum number of SeRBs that can be configured and processed.

[0143] • Type of sensing request. For instance, if a sensing request is for both detection and tracking services, each associated with a corresponding QoS flow, then the RAN can multiplex both QoS flows into a single SeRB. On the other hand, if a sensing request is for both weather monitoring and UAV detection services, then the RAN can map the two corresponding QoS flows to different SeRBs.

[0144] • Radio conditions.

[0145] • Other services being (or expected to be) used, e.g., communication-related applications.

[0146] In some embodiments, the RAN determines whether to send sensing-related information carried by an SeRB to the CN via CP, UP, or DP. This determination may be based on one or more of the following:

[0147] • CN function that will use or consume the sensing-related information;

[0148] • configuration or indication by the CN; and

[0149] • type of data in the sensing-related information, e.g., raw data is sent via DP. In some embodiments, sensing-related information carried by an SeRB may be processed by one or multiple SPFs within the DP. The number and configuration of SPFs in the DP may be determined by the RAN based on the capacity, volume, and / or content of the SeRB. For example, if an SeRB contains raw data, the RAN configures three (3) SPFs (e.g., 1-3) in the DP for processing this raw data carried by the SeRB. The raw data may be sent to SPF1, which returns its processing results to become input for processing at SPF2, which returns its processing results to become input for processing at SPF3. In this manner, the RAN may dynamically configure the SPF processing pipeline.

[0150] In some embodiments, SPF processing is performed in the RAN. In such case, the SeMF may be split between RAN and CN. For example, a final sensing result determined by the RAN- based SPF may be signaled to the CN-based SeMF via a dedicated interface.

[0151] In some embodiments, data plane signaling is based on a new interface between RAN and CN (e.g., SeMF) for SeRB data transmission. In some embodiments, SeRB signaling for sensing is based on a dedicated procedure between the RAN and CN that hosts the SeMF.

[0152] In some embodiments, sensing-related information carried by an SeRB may be sent to the CN via mapping to a corresponding data plane tunnel (e.g., GTP-U tunnel) that is destined for another CN function (e.g., SeMF) for final processing. In this arrangement, there is no SDAP layer (as in Figure 2) and no SDAP header by default in both UL and DL.

[0153] In other embodiments, sensing-related information carried by an SeRB may be relayed by the RAN (e.g., NG-RAN) to the CN (e.g., 5GC) by mapping the data to a specific channel in the RAN-CN interface. For example, some embodiments may be based on a “data plane ingestion” architecture within the RAN.

[0154] Figure 10 shows exemplary protocol layers between a RAN node (1020) and an SeMF or SPF (1030), according to other embodiments of the present disclosure. In this example, the SPP layer (1040) carries sensing-related information generated by the RAN node and is on top of an HTTP / 2 web-based interface and either transport layer security (TLS) or IPSec. Additionally, transmission control protocol (TCP) is used to provide a retransmission mechanism for reliability. Any appropriate layer-2 (L2) and layer-1 (LI) protocols may be used beneath the Internet Protocol (IP) layer.

[0155] In other embodiments, it is possible to use a file transfer protocol (FTP) client-server paradigm in which the RAN node acts as data source holder (or server) and SPF (as client) continuously pulls data from the RAN node via FTP. In some embodiments, the push (or pull) periodicity may be configured to be the same as the UE’s measurement reporting periodicity.

[0156] Figure 11 shows exemplary protocol layers between a UE (1110), a RAN node (1120), and an SeMF or SPF (1130), according to other embodiments of the present disclosure. In this example, the UE protocol layers are identical to those shown in Figure 7 while the SeMF / SPF protocol layers are identical to those shown in Figure 10. However, the intermediate RAN node acts as a relay between the UE and the SeMF / SPF, mapping various UE protocol layers to corresponding SeMF / SPF protocol layers (and vice versa). For example, the RAN node maps PDCP to TCP / TLS and vice versa. Moreover, the RAN node also checks SeRB / SPP content (e.g., in RRC layer) and if there are any unprocessed data from UE, the RAN node may process the raw data before sending the processed data to the SeMF / SPF.

[0157] Various features of the embodiments described above correspond to various operations illustrated in Figures 12-13, which show exemplary methods (e.g., procedures) for a UE and a RAN node, respectively. In other words, various features of the operations described below correspond to various embodiments described above. Furthermore, the exemplary methods shown in Figures 12-13 can be used cooperatively to provide various benefits, advantages, and / or solutions to problems described herein. Although Figures 12-13 show specific blocks in particular orders, the operations of the exemplary methods can be performed in different orders 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.

[0158] In particular, Figure 12 shows an exemplary method (e.g., procedure) for a UE configured for sensing and communication 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.

[0159] The exemplary method includes the operations of block 1220, where the UE receives a request to perform sensing measurements associated with one or more sensing services. The exemplary method also includes the operations of block 1230, where the UE performs sensing measurements in accordance with the request. The exemplary method also includes the operations of block 1240, where the UE sends a sensing measurement report that includes results of the sensing measurements. The sensing measurement report is sent via one or more of the following: a sensing processing protocol (SPP) between the UE and a sensing function in a core network (CN) coupled to the RAN, and a sensing radio bearer (SeRB) that is terminated at the sensing function or at a RAN node serving the UE.

[0160] In some embodiments, the SeRB is terminated at the sensing function and the results are included in the sensing measurement report in a format or container that is accessible to the RAN node. In some embodiments, the sensing measurement report is sent via the SPP in conjunction with PDCP as a next-lower protocol layer. Figure 7 shows an example of these embodiments. In some of these embodiments, the PDCP includes a configurable size of a sequence number assigned to PDUs received from the SPP. In some embodiments, the sensing measurement report is sent (e.g., in block 1240) via the SPP and the SeRB and the request is received via the SPP (e.g., in block 1220). Also, the exemplary method also includes the operations of block 1210, where the UE receives, from the RAN node via a radio resource control (RRC) protocol, a configuration of the SPP and the SeRB.

[0161] In some of these embodiments, the configuration of the SeRB includes a recoverPDCP field that causes a first protocol layer immediately below SPP to retransmit first PDUs previously submitted to a second protocol layer immediately below the first protocol layer, upon reconfiguration of the SeRB by the RAN. In other of these embodiments, the configuration of the SeRB includes a discardOnPDCP field that causes the first protocol layer to discard the first protocol layer PDUs previously submitted to the second protocol layer, upon reconfiguration of the SeRB by the RAN.

[0162] In some of these embodiments, the configuration of the SeRB includes an indication to apply integrity protection to SPP PDUs submitted to a next-lower protocol layer.

[0163] In some embodiments, the results are raw measurement results and the sensing measurement report is sent via a sensing data radio bearer (SeDRB) and / or a first type of SPP message. In other embodiments, the results are processed measurement results and the sensing measurement report is sent via a sensing control radio bearer (SeCRB) and / or a second type of SPP message.

[0164] In some embodiments, the sensing measurement report is sent via the SeRB, which is mapped to a first LCH having a transmission priority with one or more of the following characteristics:

[0165] • greater than transmission priorities of one or more second LCHs mapped to data radio bearers (DRBs) used for user plane (UP) communication with the RAN; and

[0166] • lower than transmission priorities of one or more third LCHs mapped to signaling radio bearers (SRBs) used for control plane (CP) communication with the RAN.

[0167] In some of these embodiments, the transmission priority of the first LCH is also lower than transmission priorities of one or more fourth DRBs used for UP communication with the RAN. In some of these embodiments, the first, second, and third LCHs are associated with respective LCH identifiers (IDs), with the respective transmission priorities of the first, second, and third LCHs being inversely related to increasing numerical order of the associated LCH IDs.

[0168] In some of these embodiments, the first LCH is assigned to a first logical channel group (LCG) and the one or more third LCHs are assigned to a second LCG. In other of these embodiments, the first LCH is not assigned to any LCG. In some of these embodiments, the first LCH is a sensing transport channel (STCH), the one or more second LCHs are dedicated transport channels (DTCHs), and the one or more third LCHs are dedicated control channels (DCCHs). In some embodiments, the sensing measurement report includes an indication that the results include one or more of the following: raw measurement results, semi-processed measurement results, or fully processed measurement results. Figure 9 shows an example of these embodiments. In some embodiments, the one or more sensing services include one or more of the following: object detection, spatial mapping, weather monitoring, and UAV positioning.

[0169] In addition, Figure 13 shows an exemplary method (e.g., procedure) for a RAN node configured for sensing and communication with 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, etc.) such as described elsewhere herein.

[0170] The exemplary method includes the operations of block 1320, where the RAN node sends, to a UE, a request to perform sensing measurements associated with one or more sensing services. The exemplary method also includes the operations of block 1330, where the RAN node receives, from the UE, a sensing measurement report that includes results of sensing measurements performed in accordance with the request. The sensing measurement report is received via one or more of the following: an SPP between the UE and a sensing function in a CN coupled to the RAN, and an SeRB that is terminated at the sensing function or at the RAN node.

[0171] In some embodiments, the SeRB is terminated at the sensing function and the results are included in the sensing measurement report in a format or container that is accessible to the RAN node. In some embodiments, the sensing measurement report is received via the SPP in conjunction with PDCP as a next-lower protocol layer. Figure 7 shows an example of these embodiments. In some of these embodiments, the PDCP includes a configurable size of a sequence number assigned to PDUs received from the SPP.

[0172] In some embodiments, the sensing measurement report is received (e.g., in block 1330) via the SPP and the SeRB and the request is sent via the SPP (e.g., in block 1320). Also, the exemplary method also includes the operations of block 1310, where the RAN node sends, to the UE via an RRC protocol, a configuration of the SPP and the SeRB.

[0173] In some of these embodiments, the configuration of the SeRB includes a recoverPDCP field that causes a first protocol layer immediately below SPP to retransmit first protocol layer PDUs previously submitted to a second protocol layer immediately below the first protocol layer, upon reconfiguration of the SeRB by the RAN. In other of these embodiments, the configuration of the SeRB includes a discardOnPDCP field that causes the first protocol layer to discard the first protocol layer PDUs previously submitted to the second protocol layer, upon reconfiguration of the SeRB by the RAN.

[0174] In some of these embodiments, the configuration of the SeRB includes an indication to apply integrity protection to SPP PDUs submitted to a next-lower protocol layer. In some embodiments, the results are raw measurement results and the sensing measurement report is received via a sensing data radio bearer (SeDRB) and / or a first type of SPP message. In other embodiments, the results are processed measurement results and the sensing measurement report is received via a sensing control radio bearer (SeCRB) and / or a second type of SPP message.

[0175] In some embodiments, the sensing measurement report is received via the SeRB, which is mapped to a first LCH having a transmission priority with one or more of the following characteristics:

[0176] • greater than transmission priorities of one or more second LCHs mapped to DRBs used for UP communication with the RAN; and

[0177] • lower than transmission priorities of one or more third LCHs mapped to SRBs used for CP communication with the RAN.

[0178] In some of these embodiments, the transmission priority of the first LCH is also lower than transmission priorities of one or more fourth DRBs used for UP communication with the RAN. In some of these embodiments, the first, second, and third LCHs are associated with respective LCH IDs, with the respective transmission priorities of the first, second, and third LCHs being inversely related to increasing numerical order of the associated LCH IDs.

[0179] In some of these embodiments, the first LCH is assigned to a first LCG and the one or more third LCHs are assigned to a second LCG. In other of these embodiments, the first LCH is not assigned to any LCG. In some of these embodiments, the first LCH is a sensing transport channel (STCH), the one or more second LCHs are dedicated transport channels (DTCHs), and the one or more third LCHs are dedicated control channels (DCCHs).

[0180] In some embodiments, the sensing measurement report includes an indication that the results include one or more of the following: raw measurement results, semi-processed measurement results, or fully processed measurement results. Figure 9 shows an example of these embodiments, In some embodiments, the one or more sensing services include one or more of the following: object detection, spatial mapping, weather monitoring, and unmanned aerial vehicle (UAV) positioning.

[0181] In some embodiments, the exemplary method also includes the operations of block 1360, where the RAN node sends the results in the sensing measurement report, or information derived therefrom, to a sensing function in the CN. In some of these embodiments, the exemplary method also includes the operations of block 1340, where the RAN node determines whether the results in the sensing measurement report include one or more of the following: raw measurement results, and at least partially processed measurement results. Furthermore, when it is determined that the sensing measurement report includes at least partially processed measurement results, the at least partially processed measurement results are sent to the sensing function in the CN in block 1360. Also, when it is determined that the sensing measurement report includes raw measurement results, the exemplary method also includes the operations of block 1350, where the RAN node processes the raw measurement results to derive processed results, with the processed results being sent to the sensing function in block 1360. In some variants of these embodiments, the raw measurement results are processed in block 1350 by a sensing processing function (SPF) in the RAN node or in another RAN node (e.g., initiated by the RAN node).

[0182] In some of these embodiments, the sensing function in the CN is one of the following: a sensing processing function (SPF), or a sensing management function (SeMF). In some of these embodiments, the RAN node includes a relay function that translates at least one first protocol layer used to receive the sensing measurement report from the UE to corresponding at least one second protocol layer used to send the results, or the information derived therefrom, to the sensing function in the CN. Figure 11 shows an example of these embodiments.

[0183] In other of these embodiments, the sensing measurement report is received from the UE via the SeRB terminated in the RAN node and the results in the sensing measurement report, or the information derived therefrom, are sent to the sensing function via the SPP and one of the following as a next-lower protocol layer: hypertext transport protocol (HTTP), or file transfer protocol (FTP). Figure 10 shows an example of these embodiments.

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

[0185] Figure 14 shows an example of a communication system 1400 in accordance with some embodiments. In this example, communication system 1400 includes a telecommunication network 1402 that includes an access network 1404 (e.g., RAN) and a core network 1406, which includes one or more core network nodes 1408. Access network 1404 includes one or more access network nodes, such as network nodes 1410a-b (one or more of which may be referred to as network nodes 1410), or any other similar 3GPP access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, telecommunication network 1402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in telecommunication network 1402 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 1402, including one or more network nodes 1410 and / or core network nodes 1408.

[0186] 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. , r App), or any combination thereof (the adj ective “open” designating support of an ORAN specification). The network node may support a specification 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 O-2 interface defined by the O-RAN Alliance or comparable technologies. Network nodes 1410 facilitate direct or indirect connection of UEs, such as by connecting UEs 1412a-d (one or more of which may be referred to as UEs 1412) to core network 1406 over one or more wireless connections.

[0187] 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 1400 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 1400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar system.

[0188] UEs 1412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network nodes 1410 and other communication devices. Similarly, network nodes 1410 are arranged, capable, configured, and / or operable to communicate directly or indirectly with UEs 1412 and / or with other network nodes or equipment in telecommunication network 1402 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in telecommunication network 1402.

[0189] In the depicted example, core network 1406 connects network nodes 1410 to one or more hosts, such as host 1416. 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 1406 includes one or more core network nodes (e.g., 1408) 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 applicable to the corresponding components of core network node 1408. 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 (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0190] Host 1416 may be under the ownership or control of a service provider other than an operator or provider of access network 1404 and / or telecommunication network 1402, and may be operated by the service provider or on behalf of the service provider. Host 1416 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.

[0191] As a whole, communication system 1400 of Figure 14 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 Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. In some examples, telecommunication network 1402 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunication network 1402 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 1402. For example, telecommunication network 1402 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.

[0192] In some examples, UEs 1412 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to access network 1404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 1404. 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 (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0193] In some embodiments, any of UEs 1412 may be configured to perform operations attributed to a UE in various embodiments described above, including the exemplary method shown in Figure 12. Likewise, in some embodiments, any network nodes 1410 may be configured to perform operations attributed to a RAN node in various embodiments described above, including the exemplary method shown in Figure 13.

[0194] In the example, hub 1414 communicates with access network 1404 to facilitate indirect communication between one or more UEs (e.g., 1412c and / or 1412d) and network nodes (e.g., 1410b). In some examples, hub 1414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, hub 1414 may be a broadband router enabling access to core network 1406 for the UEs. As another example, hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1410, or by executable code, script, process, or other instructions in hub 1414. As another example, hub 1414 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 1414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, hub 1414 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0195] Hub 1414 may have a constant / persistent or intermittent connection to network node 1410b. Hub 1414 may also allow for a different communication scheme and / or schedule between hub 1414 and UEs (e.g., 1412c and / or 1412d), and between hub 1414 and core network 1406. In other examples, hub 1414 is connected to core network 1406 and / or one or more UEs via a wired connection. Moreover, hub 1414 may be configured to connect to an M2M service provider over access network 1404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with network nodes 1410 while still connected via hub 1414 via a wired or wireless connection. In some embodiments, hub 1414 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to network node 1410b. In other embodiments, hub 1414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1410b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0196] Figure 15 shows a UE 1500 in accordance with some embodiments. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any 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.

[0197] A UE 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 UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE 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 UE 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).

[0198] UE 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 any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 15. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0199] 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), together with appropriate software; or any combination of the above. For example, processing circuitry 1502 may include multiple central processing units (CPUs).

[0200] In the example, input / output interface 1506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into UE 1500. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0201] 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 UE 1500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of power source 1508. 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 UE 1500 to which power is supplied. 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 application programs 1514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1516. Memory 1510 may store, for use by UE 1500, any of a variety of various operating systems or combinations of operating systems.

[0202] 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 disc drive, 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 UE 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.

[0203] 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 UE 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.

[0204] In the illustrated embodiment, communication functions of communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0205] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output 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., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0206] As another example, a UE comprises 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 response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0207] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is 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 head-mounted 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, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to UE 1500 shown in Figure 15.

[0208] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0209] In some embodiments, UE 1500 may be configured to perform operations attributed to a UE in various embodiments described above, including the exemplary method shown in Figure 12.

[0210] Figure 16 shows a network node 1600 in accordance with 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).

[0211] Base stations 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. A base station may be a relay node or a relay donor node controlling a relay. A network node may also 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).

[0212] Other examples of network nodes 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 / multicast coordination 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). 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. 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 memory 1604 for different RATs) and some components may be reused (e.g., a same 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, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1600.

[0213] 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 network node 1600 components, such as memory 1604, to provide network node 1600 functionality.

[0214] In some embodiments, processing circuitry 1602 includes a system on a chip (SOC). In some embodiments, processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614. In some embodiments, RF transceiver circuitry 1612 and 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 baseband processing circuitry 1614 may be on the same chip or set of chips, boards, or units.

[0215] Memory 1604 may comprise 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.

[0216] Communication interface 1606 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. 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 frontend 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 UEs 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.

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

[0218] 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 an interface or port.

[0219] Antenna 1610, communication interface 1606, and / or processing circuitry 1602 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, 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 the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0220] 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., the power grid, an electricity outlet) 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 a further example, power source 1608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

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

[0222] In some embodiments, network node 1600 may be configured to perform operations attributed to a RAN node in various embodiments described above, including the exemplary method shown in Figure 13.

[0223] Figure 17 is a block diagram illustrating a virtualization environment 1700 in which functions implemented by 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 0-2 interface.

[0224] 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, a virtual node 1702 may be configured to perform operations attributed to a RAN node in various embodiments described above, including the exemplary method shown in Figure 13.

[0225] Hardware 1704 includes 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 hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1708a-b (one or more of which may be 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.

[0226] VMs 1708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1706. Different embodiments of the instance of a virtual appliance 1702 may be implemented on one or more of VMs 1708, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. 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 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1708 on top of the hardware 1704 and corresponds to the application 1702.

[0227] 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., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration function 1710, which, among others, oversees lifecycle management of applications 1702. In some embodiments, hardware 1704 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that 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.

[0228] 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 devise numerous 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.

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

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

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

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

[0233] In addition, certain terms used in the present disclosure, including the specification and drawings, may be used synonymously in certain instances (e.g., “data” and “information”). Although such terms may be used synonymously herein, there may be instances when such terms are not intended to not be used synonymously.

[0234] Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:

[0235] Al. A method for a user equipment (UE) configured for sensing and communication in a radio access network (RAN), the method comprising: receiving, from a RAN node, a request to perform sensing measurements associated with one or more sensing services; performing sensing measurements in accordance with the request; and sending, to the RAN node, a sensing measurement report that includes results of the sensing measurements, wherein the sensing measurement report is sent via one or more of the following: a sensing processing protocol (SPP), and a sensing radio bearer (SeRB) that is terminated at the RAN node or at a sensing function in a core network (CN) coupled to the RAN.

[0236] A2. The method of embodiment Al, wherein the SeRB is terminated at the sensing function and the results are included in the sensing measurement report in a format or container that is accessible to the RAN node.

[0237] A3. The method of any of embodiments A1-A2, wherein the sensing measurement report is sent via the SPP in conjunction with packet data convergence protocol (PDCP) as a next-lower protocol layer.

[0238] A3a. The method of embodiment A3, wherein the PDCP includes a configurable size of a sequence number assigned to protocol data units (PDUs) received from the SPP.

[0239] A4. The method of any of embodiments Al-A3a, wherein the sensing measurement report is sent via the SPP and the SeRB, the request is received via the SPP, and the method further comprises receiving, from the RAN node via a radio resource control (RRC) protocol, a configuration of the SPP and the SeRB.

[0240] A4a. The method of embodiment A4, wherein the configuration of the SeRB includes one of the following: a recoverPDCP field that causes a first protocol layer immediately below SPP to retransmit first protocol layer protocol data units (PDUs) previously submitted to a second protocol layer immediately below the first protocol layer, upon reconfiguration of the SeRB by the RAN; or a discardOnPDCP field that causes the first protocol layer to discard the first protocol layer PDUs previously submitted to the second protocol layer, upon reconfiguration of the SeRB by the RAN.

[0241] A4b. The method of embodiment A4, wherein the configuration of the SeRB includes an indication to apply integrity protection to SPP protocol data units (PDUs) submitted to a next- lower protocol layer.

[0242] A5. The method of any of embodiments Al-A4b, wherein one of the following applies: the results are raw measurement results and the sensing measurement report is sent via one or more of the following: a sensing data radio bearer (SeDRB), and a first type of SPP message; or the results are processed measurement results and the sensing measurement report is sent via one or more of the following: a sensing control radio bearer (SeCRB), and a second type of SPP message.

[0243] A6. The method of any of embodiments A1-A5, wherein the sensing measurement report is sent via the SeRB, which is mapped to a first logical channel (LCH) having a transmission priority with one or more of the following characteristics: greater than transmission priorities of one or more second LCHs mapped to data radio bearers (DRBs) used for user plane (UP) communication with the RAN; and lower than transmission priorities of one or more third LCHs mapped to signaling radio bearers (SRBs) used for control plane (CP) communication with the RAN.

[0244] A6a. The method of embodiment A6, wherein the transmission priority of the first LCH is also lower than transmission priorities of one or more fourth DRBs used for UP communication with the RAN.

[0245] A6b. The method of embodiment A6, wherein the first, second, and third LCHs are associated with respective LCH identifiers (IDs), with the respective transmission priorities of the first, second, and third LCHs being inversely related to increasing numerical order of the associated LCH IDs.

[0246] A6c. The method of embodiment A6, wherein one of the following applies: the first LCH is assigned to a first logical channel group (LCG) and the one or more third LCHs are assigned to a second LCG; or the first LCH is not assigned to any LCG. A6d. The method of embodiment A6, wherein the first LCH is a sensing transport channel (STCH), the one or more second LCHs are dedicated transport channels (DTCHs), and the one or more third LCHs are dedicated control channels (DCCHs).

[0247] A7. The method of any of embodiments Al-A6d, wherein the sensing measurement report includes an indication that the results include one or more of the following: raw measurement results, semi-processed measurement results, or fully processed measurement results.

[0248] A8. The method of any of embodiments A1-A7, wherein the one or more sensing services include one or more of the following: object detection, spatial mapping, weather monitoring, and unmanned aerial vehicle (UAV) positioning.

[0249] Bl . A method for a radio access network (RAN) node configured for sensing and communication with user equipment (UEs), the method comprising: sending, to a UE, a request to perform sensing measurements associated with one or more sensing services; and receiving, from the UE, a sensing measurement report that includes results of sensing measurements performed in accordance with the request, wherein the sensing measurement report is received via one or more of the following: a sensing processing protocol (SPP), and a sensing radio bearer (SeRB) that is terminated at the RAN node or at a sensing function in a core network (CN) coupled to the RAN.

[0250] B2. The method of embodiment Bl, wherein the SeRB is terminated at the sensing function and the results are included in the sensing measurement report in a format or container that is accessible to the RAN node.

[0251] B3. The method of any of embodiments B1-B2, wherein the sensing measurement report is received via the SPP in conjunction with packet data convergence protocol (PDCP) as a next- lower protocol layer.

[0252] B3a. The method of embodiment B3, wherein the PDCP includes a configurable size of a sequence number assigned to protocol data units (PDUs) received from the SPP. B4. The method of any of embodiments Bl-B3a, wherein the sensing measurement report is received via the SPP and the SeRB, the request is sent via the SPP, and the method further comprises sending, to the UE via a radio resource control (RRC) protocol, a configuration of the SPP and the SeRB.

[0253] B4a. The method of embodiment B4, wherein the configuration of the SeRB includes one of the following: a recoverPDCP field that causes a first protocol layer immediately below SPP to retransmit first protocol layer protocol data units (PDUs) previously submitted to a second protocol layer immediately below the first protocol layer, upon reconfiguration of the SeRB by the RAN; or a discardOnPDCP field that causes the first protocol layer to discard the first protocol layer PDUs previously submitted to the second protocol layer, upon reconfiguration of the SeRB by the RAN.

[0254] B4b. The method of embodiment B4, wherein the configuration of the SeRB includes an indication to apply integrity protection to SPP protocol data units (PDUs) submitted to a next- lower protocol layer.

[0255] B5. The method of any of embodiments Bl-B4b, wherein one of the following applies: the results are raw measurement results and the sensing measurement report is received via one or more of the following: a sensing data radio bearer (SeDRB), and a first type of SPP message; or the results are processed measurement results and the sensing measurement report is received via one or more of the following: a sensing control radio bearer (SeCRB), and a second type of SPP message.

[0256] B6. The method of any of embodiments B1-B5, wherein the sensing measurement report is received via the SeRB, which is mapped to a first logical channel (LCH) having a transmission priority with one or more of the following characteristics: greater than transmission priorities of one or more second LCHs mapped to data radio bearers (DRBs) used for user plane (UP) communication with the UE; and lower than transmission priorities of one or more third LCHs mapped to signaling radio bearers (SRBs) used for control plane (CP) communication with the UE. B6a. The method of embodiment B6, wherein the transmission priority of the first LCH is also lower than transmission priorities of one or more fourth DRBs used for UP communication with the UE.

[0257] B6b. The method of embodiment B6, wherein the first, second, and third LCHs are associated with respective LCH identifiers (IDs), with the respective transmission priorities of the first, second, and third LCHs being inversely related to increasing numerical order of the associated LCH IDs.

[0258] B6c. The method of embodiment B6, wherein one of the following applies: the first LCH is assigned to a first logical channel group (LCG) and the one or more third LCHs are assigned to a second LCG; or the first LCH is not assigned to any LCG.

[0259] B6d. The method of embodiment B6, wherein the first LCH is a sensing transport channel (STCH), the one or more second LCHs are dedicated transport channels (DTCHs), and the one or more third LCHs are dedicated control channels (DCCHs).

[0260] B7. The method of any of embodiments Bl-B6d, wherein the sensing measurement report includes an indication that the results include one or more of the following: raw measurement results, semi-processed measurement results, or fully processed measurement results.

[0261] B8. The method of any of embodiments B1-B7, wherein the one or more sensing services include one or more of the following: object detection, spatial mapping, weather monitoring, and unmanned aerial vehicle (UAV) positioning.

[0262] B9. The method of any of embodiments B1-B8, further comprising sending the results in the sensing measurement report, or information derived therefrom, to a sensing function in the CN.

[0263] B9a. The method of embodiment B9, further comprising determining whether the results in the sensing measurement report include one or more of the following: raw measurement results, and at least partially processed measurement results, wherein: when it is determined that the sensing measurement report includes at least partially processed measurement results, the at least partially processed measurement results are sent to the sensing function in the CN; and when it is determined that the sensing measurement report includes raw measurement results, the method further comprises processing the raw measurement results to derive processed results, wherein the processed results are sent to the sensing function in the CN.

[0264] B9b. The method of B9a, wherein the raw measurement results are processed by a sensing processing function (SPF) in the RAN node or in another RAN node.

[0265] B9c. The method of any of embodiments B9-B9b, wherein the sensing function in the CN is one of the following: a sensing processing function (SPF), or a sensing processing function (SPF).

[0266] B9d. The method of any of embodiments B9-B9c, wherein the RAN node includes a relay function that translates at least one first protocol layer used to receive the sensing measurement report from the UE to corresponding at least one second protocol layer used to send the results, or the information derived therefrom, to the sensing function in the CN.

[0267] Cl . User equipment (UE) configured for sensing and communication in a radio access network (RAN), the UE comprising: 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 A1-A8.

[0268] C2. User equipment (UE) configured for sensing and communication in a radio access network (RAN), the UE being further configured to perform operations corresponding to the methods of any of embodiments A1-A8.

[0269] C3. Non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of user equipment (UE) configured for sensing and communication in a radio access network (RAN), configure the UE to perform operations corresponding to the methods of any of embodiments A1-A8. C4. Computer program product comprising computer-executable instructions that, when executed by processing circuitry of user equipment (UE) configured for sensing and communication in a radio access network (RAN), configure the UE to perform operations corresponding to the methods of any of embodiments A1-A8.

[0270] DI. Radio access network (RAN) node configured for sensing and communication with user equipment (UEs), the RAN node comprising: communication interface circuitry configured to communicate with UEs and with a core network (CN) coupled to the RAN; 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 Bl-B9d.

[0271] D2. Radio access network (RAN) node configured for sensing and communication with user equipment (UEs), the RAN node being further configured to perform operations corresponding to the methods of any of embodiments Bl-B9d.

[0272] D3. Non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured for sensing and communication with user equipment (UEs), configure the RAN node to perform operations corresponding to the methods of any of embodiments Bl-B9d.

[0273] D4. Computer program product comprising computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured for sensing and communication with user equipment (UEs), configure the RAN node to perform operations corresponding to the methods of any of embodiments Bl-B9d.

Claims

CLAIMS1. A method for a user equipment, UE, configured for sensing and communication in a radio access network, RAN, the method comprising: receiving (1220) a request to perform sensing measurements associated with one or more sensing services; performing (1230) sensing measurements in accordance with the request; and sending (1240) a sensing measurement report that includes results of the sensing measurements, wherein the sensing measurement report is sent via one or more of the following: a sensing processing protocol, SPP, between the UE and a sensing function in a core network, CN, coupled to the RAN; and a sensing radio bearer, SeRB, that is terminated at the sensing function or at a RAN node serving the UE.

2. The method of claim 1, wherein the SeRB is terminated at the sensing function and the results are included in the sensing measurement report in a format or container that is accessible to the RAN node.

3. The method of any of claims 1-2, wherein the sensing measurement report is sent via the SPP in conjunction with packet data convergence protocol, PDCP, as a next-lower protocol layer.

4. The method of claim 3, wherein the PDCP includes a configurable size of a sequence number assigned to protocol data units, PDUs, received from the SPP.

5. The method of any of claims 1-4, wherein: the sensing measurement report is sent via the SPP and the SeRB; the request is received via the SPP; and the method further comprises receiving (1210), from the RAN node via a radio resource control, RRC, protocol, a configuration of the SPP and the SeRB.

6. The method of claim 5, wherein the configuration of the SeRB includes one of the following:a recoverPDCP field that causes a first protocol layer immediately below SPP to retransmit first protocol layer protocol data units, PDUs, previously submitted to a second protocol layer immediately below the first protocol layer, upon reconfiguration of the SeRB by the RAN; or a discardOnPDCP field that causes the first protocol layer to discard the first protocol layer PDUs previously submitted to the second protocol layer, upon reconfiguration of the SeRB by the RAN.

7. The method of claim 5, wherein the configuration of the SeRB includes an indication to apply integrity protection to SPP protocol data units, PDUs, submitted to a next-lower protocol layer.

8. The method of any of claims 1-7, wherein one of the following applies: the results are raw measurement results and the sensing measurement report is sent via one or more of the following: a sensing data radio bearer, SeDRB, and a first type of SPP message; or the results are processed measurement results and the sensing measurement report is sent via one or more of the following: a sensing control radio bearer, SeCRB, and a second type of SPP message.

9. The method of any of claims 1-7, wherein the sensing measurement report is sent via the SeRB, which is mapped to a first logical channel, LCH, having a transmission priority with one or more of the following characteristics: greater than transmission priorities of one or more second LCHs mapped to data radio bearers, DRBs, used for user plane, UP, communication with the RAN; and lower than transmission priorities of one or more third LCHs mapped to signaling radio bearers, SRBs, used for control plane, CP, communication with the RAN.

10. The method of claim 9, wherein the transmission priority of the first LCH is also lower than transmission priorities of one or more fourth DRBs used for UP communication with the RAN.

11. The method of claim 9, wherein the first, second, and third LCHs are associated with respective LCH identifiers, IDs, with the respective transmission priorities of the first, second, and third LCHs being inversely related to increasing numerical order of the associated LCH IDs.

12. The method of claim 9, wherein one of the following applies: the first LCH is assigned to a first logical channel group, LCG, and the one or more third LCHs are assigned to a second LCG; or the first LCH is not assigned to any LCG.

13. The method of claim 9, wherein the first LCH is a sensing transport channel, STCH, the one or more second LCHs are dedicated transport channels, DTCHs, and the one or more third LCHs are dedicated control channels, DCCHs.

14. The method of any of claims 1-13, wherein the sensing measurement report includes an indication that the results include one or more of the following: raw measurement results, semiprocessed measurement results, or fully processed measurement results.

15. The method of any of claims 1-14, wherein the one or more sensing services include one or more of the following: object detection, spatial mapping, weather monitoring, and unmanned aerial vehicle, UAV, positioning.

16. A method for a radio access network, RAN, node configured for sensing and communication with user equipment, UEs, the method comprising: sending (1320), to a UE, a request to perform sensing measurements associated with one or more sensing services; and receiving (1330), from the UE, a sensing measurement report that includes results of sensing measurements performed in accordance with the request, wherein the sensing measurement report is received via one or more of the following: a sensing processing protocol, SPP, between the UE and a sensing function in a core network, CN, coupled to the RAN; and a sensing radio bearer, SeRB, that is terminated at the SF or at the RAN node.

17. The method of claim 16, wherein the SeRB is terminated at the sensing function and the results are included in the sensing measurement report in a format or container that is accessible to the RAN node.

18. The method of any of claims 16-17, wherein the sensing measurement report is received via the SPP in conjunction with packet data convergence protocol, PDCP, as a next-lower protocol layer.

19. The method of claim 18, wherein the PDCP includes a configurable size of a sequence number assigned to protocol data units, PDUs, received from the SPP.

20. The method of any of claims 16-19, wherein: the sensing measurement report is received via the SPP and the SeRB; the request is sent via the SPP; and the method further comprises sending (1310), to the UE via a radio resource control, RRC, protocol, a configuration of the SPP and the SeRB.

21. The method of claim 20, wherein the configuration of the SeRB includes one of the following: a recoverPDCP field that causes a first protocol layer immediately below SPP to retransmit first protocol layer protocol data units, PDUs, previously submitted to a second protocol layer immediately below the first protocol layer, upon reconfiguration of the SeRB by the RAN; or a discardOnPDCP field that causes the first protocol layer to discard the first protocol layer PDUs previously submitted to the second protocol layer, upon reconfiguration of the SeRB by the RAN.

22. The method of claim 20, wherein the configuration of the SeRB includes an indication to apply integrity protection to SPP protocol data units, PDUs, submitted to a next-lower protocol layer.

23. The method of any of claims 16-22, wherein one of the following applies: the results are raw measurement results and the sensing measurement report is received via one or more of the following: a sensing data radio bearer, SeDRB, and a first type of SPP message; or the results are processed measurement results and the sensing measurement report is received via one or more of the following: a sensing control radio bearer, SeCRB, and a second type of SPP message.

24. The method of any of claims 16-23, wherein the sensing measurement report is received via the SeRB, which is mapped to a first logical channel, LCH, having a transmission priority with one or more of the following characteristics: greater than transmission priorities of one or more second LCHs mapped to data radio bearers, DRBs, used for user plane, UP, communication with the UE; and lower than transmission priorities of one or more third LCHs mapped to signaling radio bearers, SRBs, used for control plane, CP, communication with the UE.

25. The method of claim 24, wherein the transmission priority of the first LCH is also lower than transmission priorities of one or more fourth DRBs used for UP communication with the UE.

26. The method of claim 24, wherein the first, second, and third LCHs are associated with respective LCH identifiers, IDs, with the respective transmission priorities of the first, second, and third LCHs being inversely related to increasing numerical order of the associated LCH IDs.

27. The method of claim 24, wherein one of the following applies: the first LCH is assigned to a first logical channel group, LCG, and the one or more third LCHs are assigned to a second LCG; or the first LCH is not assigned to any LCG.

28. The method of claim 24, wherein the first LCH is a sensing transport channel, STCH, the one or more second LCHs are dedicated transport channels, DTCHs, and the one or more third LCHs are dedicated control channels, DCCHs.

29. The method of any of claims 16-28, wherein the sensing measurement report includes an indication that the results include one or more of the following: raw measurement results, semiprocessed measurement results, or fully processed measurement results.

30. The method of any of claims 16-29, wherein the one or more sensing services include one or more of the following: object detection, spatial mapping, weather monitoring, and unmanned aerial vehicle, UAV, positioning.

31. The method of any of claims 16-30, further comprising sending the results in the sensing measurement report, or information derived therefrom, to the sensing function in the CN.

32. The method of claim 31, further comprising determining whether the results in the sensing measurement report include one or more of the following: raw measurement results, and at least partially processed measurement results, wherein: when it is determined that the sensing measurement report includes at least partially processed measurement results, the at least partially processed measurement results are sent to the sensing function in the CN; and when it is determined that the sensing measurement report includes raw measurement results, the method further comprises processing the raw measurement results to derive processed results, wherein the processed results are sent to the sensing function in the CN.

33. The method of 32, wherein the raw measurement results are processed by a sensing processing function, SPF, in the RAN node or in another RAN node.

34. The method of any of claims 31-33, wherein the sensing function in the CN is one of the following: a sensing processing function, SPF, or a sensing management function, SeMF.

35. The method of any of claims 31-34, wherein the RAN node includes a relay function that translates at least one first protocol layer used to receive the sensing measurement report from the UE to corresponding at least one second protocol layer used to send the results, or the information derived therefrom, to the sensing function in the CN.

36. The method of any of claims 31-35, wherein: the sensing measurement report is received from the UE via the SeRB terminated in the RAN node; and the results in the sensing measurement report, or the information derived therefrom, are sent to the sensing function in the CN via the SPP and one of the following as a next-lower protocol layer: hypertext transport protocol, HTTP, or file transfer protocol, FTP.

37. User equipment, UE (210, 510, 1110, 1412, 1500) configured for sensing and communication in a radio access network, RAN (520, 1404), the UE comprising: communication interface circuitry (1512) configured to communicate with RAN nodes (220, 521, 522, 1020, 1120, 1410, 1600, 1702); andprocessing circuitry (1502) operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to: receive a request to perform sensing measurements associated with one or more sensing services; perform sensing measurements in accordance with the request; and send a sensing measurement report that includes results of the sensing measurements, wherein the sensing measurement report is sent via one or more of the following: a sensing processing protocol, SPP, between the UE and a sensing function (530, 540, 1030, 1130) in a core network, CN (1406) coupled to the RAN, and a sensing radio bearer, SeRB, that is terminated at the SF or at a RAN node serving the UE.

38. The UE of claim 37, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to the methods of any of claims 2-15.

39. User equipment, UE (210, 510, 1110, 1412, 1500) configured for sensing and communication in a radio access network, RAN (520, 1404), the UE being further configured to: receive a request to perform sensing measurements associated with one or more sensing services; perform sensing measurements in accordance with the request; and send a sensing measurement report that includes results of the sensing measurements, wherein the sensing measurement report is sent via one or more of the following: a sensing processing protocol, SPP, between the UE and a sensing function (530,540, 1030, 1130) in a core network, CN (1406) coupled to the RAN; and a sensing radio bearer, SeRB, that is terminated at the SF or at a RAN node (220,521, 522, 1020, 1120, 1410, 1600, 1702) serving the UE.

40. The UE of claim 39, being further configured to perform operations corresponding to the methods of any of claims 2-15.

41. Non-transitory, computer-readable medium (1510) storing computer-executable instructions that, when executed by processing circuitry (1502) of user equipment, UE (210, 510, 1110, 1412, 1500) configured for sensing and communication in a radio access network, RAN (520, 1404), configure the UE to perform operations corresponding to the methods of any of claims 1-15.

42. Computer program product (1514) comprising computer-executable instructions that, when executed by processing circuitry (1502) of user equipment, UE (210, 510, 1110, 1412, 1500) configured for sensing and communication in a radio access network, RAN (520, 1404), configure the UE to perform operations corresponding to the methods of any of claims 1-15.

43. Radio access network, RAN, node (220, 521, 522, 1020, 1120, 1410, 1600, 1702) configured for sensing and communication with user equipment, UEs (210, 510, 1110, 1412, 1500), the RAN node comprising: communication interface circuitry (1606, 1704) configured to communicate with UEs and with a core network, CN (1406) coupled to the RAN (520, 1404); and processing circuitry (1602, 1704) operatively coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to: send, to a UE, a request to perform sensing measurements associated with one or more sensing services; and receive, from the UE, a sensing measurement report that includes results of sensing measurements performed in accordance with the request, wherein the sensing measurement report is received via one or more of the following: a sensing processing protocol, SPP, between the UE and a sensing function (530, 540, 1030, 1130) in a core network, CN (1406) coupled to the RAN; and a sensing radio bearer, SeRB, that is terminated at the SF or at the RAN node.

44. The RAN node of claim 43, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to the methods of any of claims 17-36.

45. Radio access network, RAN, node (220, 521, 522, 1020, 1120, 1410, 1600, 1702) configured for sensing and communication with user equipment, UEs (210, 510, 1110, 1412, 1500), the RAN node being further configured to: send, to a UE, a request to perform sensing measurements associated with one or more sensing services; and receive, from the UE, a sensing measurement report that includes results of sensing measurements performed in accordance with the request, wherein the sensing measurement report is received via one or more of the following: a sensing processing protocol, SPP, between the UE and a sensing function (530, 540, 1030, 1130) in a core network, CN (1406) coupled to the RAN (520, 1404); and a sensing radio bearer, SeRB, that is terminated at the SF or at the RAN node.

46. The RAN node of claim D453, being further configured to perform operations corresponding to the methods of any of claims 17-36.

47. Non-transitory, computer-readable medium (1604, 1704) storing computer-executable instructions that, when executed by processing circuitry (1602, 1704) of a radio access network, RAN, node (220, 521, 522, 1020, 1120, 1410, 1600, 1702) configured for sensing and communication with user equipment, UEs (210, 510, 1110, 1412, 1500), configure the RAN node to perform operations corresponding to the methods of any of claims 16-36.

48. Computer program product (1604a, 1704a) comprising computer-executable instructions that, when executed by processing circuitry (1602, 1704) of a radio access network, RAN, node (220, 521, 522, 1020, 1120, 1410, 1600, 1702) configured for sensing and communication with user equipment, UEs (210, 510, 1110, 1412, 1500), configure the RAN node to perform operations corresponding to the methods of any of claims 16-36.

Images