Reporting of sensing measurement data from a ran node

Abstract

A method comprising: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between the RAN node and a sensing data processing unit; configuring the RAN node for the sensing data session in response to receiving the request; associating the sensing data session with a sensing data reporting function of the RAN node to provide the sensing data for the transmission to the sensing data processing unit, wherein the sensing data is collected by the RAN node.

Description

[0001] REPORTING OF SENSING MEASUREMENT DATA FROM A RAN NODE

[0002] Technical Field

[0003] Various example embodiments of this disclosure relate to sensing data, and more specifically (but not exclusively) to reporting of sensing data.

[0004] Abbreviations

[0005] 3GPP 3rdGeneration Partnership Project

[0006] 5G / 6G / 7G 5th, 6th, 7thGeneration 5GC 5G Core Network

[0007] AF Application Function

[0008] AGV Automated Guided Vehicle

[0009] AMF Access Mobility Function

[0010] AMR Autonomous Mobile Robots

[0011] AN Access Network

[0012] BS Base Station

[0013] CN Core Network

[0014] DL Downlink

[0015] EIRP Effective Isotropic Radiated Power eNB evolved NodeB

[0016] F-TEID Fully Qualified TEID

[0017] FQDN Fully Qualified Domain Name

[0018] GMLC Gateway Mobile Location Centre gNB next generation NodeB

[0019] GPRS General Packet Radio Service

[0020] GTP-ll GPRS Tunneling Protocol - User Plane

[0021] ID Identifier

[0022] IP Internet Protocol

[0023] ISAC Integrated Sensing and Communication

[0024] LAN Local Area Network

[0025] LCS Location Service

[0026] LMF Location Management Function

[0027] MEC Multi-access Edge Computing

[0028] NEF Network Exposure Function

[0029] NF Network Function

[0030] NG-RAN Next Generation RAN NLOS Non-Line of Sight

[0031] NPN Non-Public Network

[0032] NR New Radio

[0033] NRF Network Repository Function

[0034] OAM Operations and Administration Management

[0035] PDR Packet Detection Rules

[0036] PLMN Public Land Mobile Network

[0037] QoS Quality of Service

[0038] RAN Radio Access Network

[0039] RAN RF Radio Access Network Repository Function

[0040] RF Radio Frequency

[0041] Rx Reception

[0042] SBA Service-Based Architecture

[0043] SBI Service-Based Interface

[0044] SDU Service Data Unit

[0045] SeMF Sensing Management Function

[0046] SMF Session Management Function

[0047] S-PDU Sensing Packing Data Unit

[0048] TA Tracking Area

[0049] TEID Tunnel Endpoint Identifier

[0050] TOS Type of Service

[0051] Tx Transmission

[0052] UAV Unmanned Aerial Vehicle

[0053] UE User Equipment

[0054] UL Uplink

[0055] UP User Plane

[0056] UPF User Plane Function

[0057] WAN Wide Area network

[0058] WLAN Wireless Local Area network

[0059] Interfaces

[0060] N3 Interface between the (R)AN and the UPF.

[0061] N4 Interface between the SMF and the UPF

[0062] N6 Demarcation point for traffic between the UPF and a Data Network.

[0063] N9 Interface between two UPFs (e.g., intermediate UPF and UPF session anchor) Background

[0064] A communication system can be seen as a facility that enables communication sessions between two or more entities, such as communication devices, base stations and / or other nodes by providing carriers between the various entities involved in the communications path.

[0065] The communication system may be a wireless communication system. Examples of wireless systems comprise PLMNs operating based on radio standards (such as, those provided by 3GPP), satellite based communication systems and different wireless local networks. A wireless local network may, for example, be implemented as a WLAN. The wireless systems can typically be divided into cells, and are therefore often referred to as cellular systems.

[0066] The communication system and associated devices typically operate in accordance with a given standard or specification, which sets forth what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and / or parameters which shall be used for the connection are also typically defined. An example of a set of standards are the so-called 5G standards.

[0067] Summary

[0068] Various example embodiments of the disclosure aim at addressing at least part of the issue and / or problems and drawbacks either explicitly described herein or otherwise apparent to a person skilled in the relevant arts to provide methods, apparatuses and computer programs by which mechanisms and / or procedures for the sensing of data, and the reporting of the sensing of data can be improved.

[0069] Various example embodiments will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various example embodiments, nor are they intended to be used to otherwise limit the scope of the disclosure. Other features, aspects and elements of the various example embodiments will be readily apparent to a person skilled in the art in view of the disclosure.

[0070] According to a first aspect, there is provided an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between a RAN node and a sensing data processing unit; configuring the RAN node for the sensing data session in response to receiving the request; and associating the sensing data session with a sensing data reporting function of the RAN node to provide the sensing data for the transmission to the sensing data processing unit, wherein the RAN node is configured to collect the sensing data.

[0071] The request may not comprise any identifier of a terminal.

[0072] The request may not comprise any context information of a terminal.

[0073] The request to set up the sensing data session may comprise at least one of:

[0074] - addressing information of the sensing data processing unit;

[0075] - information on the sensing data to be transmitted in the sensing data session;

[0076] - an identifier of the sensing data session; or

[0077] - QoS information for the sensing data session.

[0078] The addressing information of the sensing data processing unit may comprise at least one of:

[0079] - an FQDN of the sensing data processing unit;

[0080] - one or more combinations of IP addresses and ports of the sensing data processing unit for the sensing data session;

[0081] - a fully qualified GTP-u tunnel identifier for the sensing data session; or

[0082] - a uniform resource locator for the sensing data session on the sensing data processing unit.

[0083] The fully qualified tunnel identifier for the sensing data session may correspond to one of:

[0084] - a fully qualified tunnel identifier configured to identify resources at the sensing data processing unit; or

[0085] - a fully qualified tunnel identifier configured to identify resources at a sensing data forwarding function for forwarding traffic between the RAN node and the sensing data processing unit.

[0086] The information on the sensing data to be transmitted in the sensing data session may comprise at least one of:

[0087] - an identifier of a sensing session for configuring and / or controlling the RAN node to obtain the sensing data;

[0088] - information on a trigger radio signal sent to trigger sensing for obtaining the sensing data; - information on the first radio signal measured by the RAN node to obtain the sensing data;

[0089] - information on at least one radio parameter of the first radio signal and / or the trigger radio signal, such as time and / or frequency of the respective radio signal; or

[0090] - information on the periodicity and / or duration to send the trigger radio signal and / or to measure the first radio signal.

[0091] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: causing the RAN node to generate the sensing data.

[0092] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: receiving the first radio signal on at least a radio resource assigned to a sensing procedure; and generating the sensing data based on the first radio signal received on the at least one resource assigned to the sensing procedure.

[0093] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform, based the received information on which radio signal to measure, the generating the sensing data without demodulating the first radio signal, or the generating the sensing data after demodulating the first radio signal.

[0094] The sensing data may not comprise any user data received from a terminal in communication with the RAN node.

[0095] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: causing the RAN node to transmit the sensing data in the sensing data session.

[0096] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: the transmitting the sensing data in packets, wherein a header of each of the packets indicates that the respective packet includes at least a portion of the sensing data for the sensing procedure. The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: responding to the request to set up the sensing data session with addressing information allocated to the sensing data session.

[0097] The response to the request to set up the sensing data session may comprise at least one of:

[0098] - an FQDN of the sensing data reporting function;

[0099] - one or more combinations of IP addresses and ports of the sensing data reporting function for the sensing data session;

[0100] - a fully qualified GTP-u tunnel identifier for the sensing data session at the sensing data reporting function; or

[0101] - a uniform resource locator for the sensing data session on the RAN node.

[0102] The response to the request to set up the sensing data session may not comprise a fully qualified GTP-u tunnel identifier for the sensing data session at the sensing data reporting function in the access network when the request to set up the sensing data session does not comprise a fully qualified GTP-u tunnel identifier.

[0103] The collected sensing data may be obtained by a sensing procedure from characteristics of a first radio signal measured by the RAN node.

[0104] According to a second aspect, there is provided an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform: obtaining addressing information of a sensing data processing unit for a sensing data session for receiving sensing data from a RAN node; and generating and transmitting a first request configured to request the RAN node to set up the sensing data session.

[0105] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: generating and transmitting a second request configured to request the sensing data processing unit to set up the sensing data session and to provide, in response, the addressing information for the sensing data session.

[0106] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: generating and transmitting a request configured to request a sensing data forwarding function to set up a sensing data session for transmitting the sensing data between the RAN node and the sensing data processing unit.

[0107] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: selecting one or more RAN nodes; and transmitting the first request directly to each of the one or more RAN nodes.

[0108] None of the first request and the second request, if any, may comprise any identifier of a terminal.

[0109] None of the first request and the second request, if any, may comprise any context information of a terminal.

[0110] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: the obtaining the addressing information at the sensing data processing unit for the sensing data session by receiving the addressing information from the sensing data processing unit.

[0111] According to a third aspect, there is provided an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform: receiving an original request configured to request a sensing data forwarding function and a RAN node to set up a sensing data session for transmitting sensing data from the RAN node to the sensing data forwarding function in the sensing data session; transmitting a first request configured to request the sensing data forwarding function to set up the sensing data session; and transmitting a second request configured to request the RAN node to set up the sensing data session.

[0112] The sensing data forwarding function may comprise a user plane function.

[0113] The first request may additionally request the user plane function to forward the sensing data from the user plane function to a sensing data processing unit. The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: the transmitting the first request directly to the sensing data forwarding function; and the transmitting the second request directly to the RAN node.

[0114] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform selecting one or more RAN nodes; the transmitting the second request to each of the one or more RAN nodes.

[0115] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: receiving the original request from a sensing data management function.

[0116] None of the original request, the first request, and the second request may comprise any identifier of a terminal.

[0117] None of the original request, the first request, and the second request may comprise any context information of a terminal.

[0118] According to a fourth aspect, there is provided an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform: receiving, at a sensing data processing unit, from a sensing data management function or a session management function, a request to set up a sensing data session for receiving sensing data for a session; configuring the sensing data processing unit for the sensing data session in response to receiving the request; and causing the sensing data processing unit to process the sensing data received in the sensing data session.

[0119] The instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: providing, in a response to the request, an address at the sensing data processing unit for receiving the sensing data in the sensing data session.

[0120] The said addressing information may comprise at least one of:

[0121] - an FQDN of the sensing data processing unit; - one or more combinations of IP addresses and ports of the sensing data processing unit for the sensing data session;

[0122] - a fully qualified GTP-u tunnel identifier at the sensing data processing unit for the sensing data session; and

[0123] - a uniform resource locator for the sensing data session on the sensing data processing unit.

[0124] The sensing data may comprise characteristics of a received electromagnetic signal; and the instructions, when executed by the one or more processors, may further cause the apparatus at least to perform: the processing the sensing data comprises determining at least one of a location, a speed, a velocity, a shape, a material, or a dimension of an object, based on characteristics of a received electromagnetic signal comprised in the sensing data.

[0125] The characteristics may comprise at least one of: a received power, a delay, an angle of arrival, or a Doppler shift of the received electromagnetic signal.

[0126] According to a fifth aspect, there is provided an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between a sensing data forwarding function and a RAN node; configuring the sensing data forwarding function for the sensing data session in response to receiving the request; and causing the sensing data forwarding function to forward sensing data received in the sensing data session to a sensing data processing unit.

[0127] The request may not comprise any identifier of a terminal.

[0128] The request may not comprise any context information of a terminal.

[0129] The sensing data forwarding function may comprise a user plane function.

[0130] The instructions, when executed by the one or more processors, may further cause the apparatus to: refrain from (e.g., not perform) forwarding data comprised in the packet from the sensing data forwarding function to the sensing data processing unit if the packet does not comprise the indication that the packet comprises at least a portion of the sensing data.

[0131] According to a sixth aspect, there is provided a method comprising: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between the RAN node and a sensing data processing unit; configuring the RAN node for the sensing data session in response to receiving the request; and associating the sensing data session with a sensing data reporting function of the RAN node to provide the sensing data for the transmission to the sensing data processing unit, wherein the sensing data is collected by the RAN node.

[0132] The request may not comprise any identifier of a terminal.

[0133] The request may not comprise any context information of a terminal.

[0134] The request to set up the sensing data session may comprise at least one of:

[0135] - addressing information of the sensing data processing unit;

[0136] - information on the sensing data to be transmitted in the sensing data session;

[0137] - an identifier of the sensing data session; or

[0138] - QoS information for the sensing data session.

[0139] The addressing information of the sensing data processing unit may comprise at least one of:

[0140] - an FQDN of the sensing data processing unit;

[0141] - one or more combinations of IP addresses and ports of the sensing data processing unit for the sensing data session;

[0142] - a fully qualified GTP-u tunnel identifier for the sensing data session; or

[0143] - a uniform resource locator for the sensing data session on the sensing data processing unit.

[0144] The fully qualified tunnel identifier for the sensing data session may correspond to one of:

[0145] - a fully qualified tunnel identifier configured to identify resources at the sensing data processing unit: or a fully qualified tunnel identifier configured to identify resources at a sensing data forwarding function for forwarding traffic between the RAN node and the sensing data processing unit.

[0146] The information on the sensing data to be transmitted in the sensing data session may comprise at least one of:

[0147] - an identifier of a sensing session for configuring and / or controlling the RAN node to obtain the sensing data;

[0148] - information on a trigger radio signal sent to trigger sensing for obtaining the sensing data;

[0149] - information on the first radio signal measured by the RAN node to obtain the sensing data;

[0150] - information on at least one radio parameter of the first radio signal and / or the trigger radio signal, such as time and / or frequency of the respective radio signal; or

[0151] - information on the periodicity and / or duration to send the trigger radio signal and / or to measure the first radio signal.

[0152] The method may further comprise: causing the RAN node to generate the sensing data.

[0153] The method may further comprise: receiving the first radio signal on at least a radio resource assigned to a sensing procedure; and generating the sensing data based on the first radio signal received on the at least one resource assigned to the sensing procedure.

[0154] Based the received information on which radio signal to measure: the generating the sensing data may be performed without demodulating the first radio signal, or the generating the sensing data is performed after demodulating the first radio signal.

[0155] The sensing data may not comprise any user data received from a terminal in communication with the RAN node.

[0156] The method may further comprise: causing the RAN node to transmit the sensing data in the sensing data session. The transmitting the sensing data may be performed in packets, wherein a header of each of the packets indicates that the respective packet includes at least a portion of the sensing data for the sensing procedure.

[0157] The method may further comprise: responding to the request to set up the sensing data session with addressing information allocated to the sensing data session.

[0158] The response to the request to set up the sensing data session may comprise at least one of: an FQDN of the sensing data reporting function; one or more combinations of IP addresses and ports of the sensing data reporting function for the sensing data session; a fully qualified GTP-u tunnel identifier for the sensing data session at the sensing data reporting function; or a uniform resource locator for the sensing data session on the RAN node.

[0159] The response to the request to set up the sensing data session may not comprise a fully qualified GTP-u tunnel identifier for the sensing data session at the sensing data reporting function in the access network when the request to set up the sensing data session does not comprise a fully qualified GTP-u tunnel identifier.

[0160] The collected sensing data may be obtained by a sensing procedure from characteristics of a first radio signal measured by the RAN node.

[0161] According to a seventh aspect, there is provided a method comprising: obtaining addressing information of a sensing data processing unit for a sensing data session for receiving sensing data from a RAN node; and generating and transmitting a first request configured to request the RAN node to set up the sensing data session.

[0162] The method may further comprise: generating and transmitting a second request configured to request the sensing data processing unit to set up the sensing data session and to provide, in response, the addressing information for the sensing data session.

[0163] The method may further comprise: generating and transmitting a request configured to request a sensing data forwarding function to set up a sensing data session for transmitting the sensing data between the RAN node and the sensing data processing unit

[0164] The method may further comprise: selecting one or more RAN nodes; transmitting the first request directly to each of the one or more RAN nodes.

[0165] None of the first request and the second request, if any, may comprise any identifier of a terminal.

[0166] None of the first request and the second request, if any, may comprise any context information of a terminal.

[0167] The obtaining the addressing information at the sensing data processing unit for the sensing data session is performed by receiving the addressing information from the sensing data processing unit.

[0168] According to an eighth aspect, there is provided a method comprising: receiving an original request configured to request a sensing data forwarding function and a RAN node to set up a sensing data session for transmitting sensing data from the RAN node to the sensing data forwarding function in the sensing data session; transmitting a first request configured to requesti the sensing data forwarding function to set up the sensing data session; and transmitting a second request configured to request the RAN node to set up the sensing data session.

[0169] The sensing data forwarding function may comprise a user plane function.

[0170] The first request may additionally request the user plane function to forward the sensing data from the user plane function to a sensing data processing unit.

[0171] The first request may be transmitted directly to the sensing data forwarding function.

[0172] The second request may be transmitted directly to the RAN node.

[0173] The method may further comprise: selecting one or more RAN nodes; wherein the second request is transmitted to each of the one or more RAN nodes.

[0174] The method may further comprise: receiving the original request from a sensing data management function.

[0175] None of the original request, the first request, and the second request may comprise any identifier of a terminal.

[0176] None of the original request, the first request, and the second request may comprise any context information of a terminal.

[0177] According to a ninth aspect, there is provided a method comprising: receiving, at a sensing data processing unit, from a sensing data management function or a session management function, a request to set up a sensing data session for receiving sensing data for a session; configuring the sensing data processing unit for the sensing data session in response to receiving the request; and causing the sensing data processing unit to process the sensing data received in the sensing data session.

[0178] The method may further comprise: providing, in a response to the request, an address at the sensing data processing unit for receiving the sensing data in the sensing data session.

[0179] The said addressing information may comprise at least one of:

[0180] - an FQDN of the sensing data processing unit;

[0181] - one or more combinations of IP addresses and ports of the sensing data processing unit for the sensing data session;

[0182] - a fully qualified GTP-u tunnel identifier at the sensing data processing unit for the sensing data session; or

[0183] - a uniform resource locator for the sensing data session on the sensing data processing unit.

[0184] The sensing data may comprise characteristics of a received electromagnetic signal; and the processing the sensing data may comprise determining at least one of a location, a speed, a velocity, a shape, a material, or a dimension of an object, based on characteristics of a received electromagnetic signal comprised in the sensing data. The characteristics may comprise at least one of: a received power, a delay, an angle of arrival, or a Doppler shift of the received electromagnetic signal.

[0185] According to a tenth aspect, there is provided a method comprising: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between a sensing data forwarding function and a RAN node; configuring the sensing data forwarding function for the sensing data session in response to receiving the request; and causing the sensing data forwarding function to forward sensing data received in the sensing data session to a sensing data processing unit.

[0186] The request may not comprise any identifier of a terminal.

[0187] The request may not comprise any context information of a terminal.

[0188] The sensing data forwarding function may comprise a user plane function.

[0189] The method may further comprise: refraining from (e.g., not performing) forwarding data comprised in the packet from the sensing data forwarding function to the sensing data processing unit if the packet does not comprise the indication that the packet comprises at least a portion of the sensing data.

[0190] Each of the methods of the sixth to tenth aspects may be a method of reporting sensing data.

[0191] According to an eleventh aspect, there is provided a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out the method according to any of the sixth to tenth aspects. The computer program product may be embodied as a computer readable medium or directly loadable into a computer.

[0192] According to some example embodiments, any one or more of the following advantages may be achieved:

[0193] • a large volume of data can be transmitted from the RAN nodes to the sensing data processing unit in a continuous way and with specific QoS requirements (e.g., in terms of transfer delay, data rate); thus, sensing data may be transmitted from base station to the processing unit without clogging the control plane and with a shorter transfer delay than transferring the information via the control plane; and / or no (or minimal) specification impact to the UPF.

[0194] Further details, features, and advantages will be apparent to those skilled in the relevant art from this disclosure.

[0195] Brief Description of the Drawings

[0196] In the following, some example embodiments will be described in greater detail, by way of non-limiting and illustrative examples, with reference to the accompanying drawings (Figs.), wherein:

[0197] Fig. 1 (comprising Figs. 1a to 1c) illustrates different example sensing methods of a RAN node; Fig. 2 illustrates sensing data reporting from one or more RAN nodes and processing at an AF or edge application server deployed at an mobile edge computing platform) (SeMF coordinates the sensing functionality);

[0198] Fig. 3 illustrates a message flow according to some example embodiments;

[0199] Fig. 4 illustrates interfaces according to some example embodiments;

[0200] Fig. 5 illustrates a message flow according to some example embodiments;

[0201] Fig. 6 illustrates interfaces according to some example embodiments;

[0202] Fig. 7 illustrates protocol stacks according to some example embodiments;

[0203] Fig. 8 illustrates protocol stacks according to some example embodiments;

[0204] Fig. 9 illustrates protocol stacks according to some example embodiments;

[0205] Fig. 10 illustrates protocol stacks according to some example embodiments;

[0206] Fig. 11 shows an apparatus according to an example embodiment;

[0207] Fig. 12 shows a method according to an example embodiment;

[0208] Fig. 13 shows an apparatus according to an example embodiment;

[0209] Fig. 14 shows a method according to an example embodiment;

[0210] Fig. 15 shows an apparatus according to an example embodiment;

[0211] Fig. 16 shows a method according to an example embodiment;

[0212] Fig. 17 shows an apparatus according to an example embodiment;

[0213] Fig. 18 shows a method according to an example embodiment;

[0214] Fig. 19 shows an apparatus according to an example embodiment;

[0215] Fig. 20 shows a method according to an example embodiment; and

[0216] Fig. 21 shows an apparatus according to an example embodiment.

[0217] Detailed Description

[0218] Herein below, various example embodiments of this are described in detail with reference to the accompanying drawings, wherein the features of the example embodiments can be freely combined with each other unless otherwise described. However, it is to be expressly understood that the description of the various example embodiments is provided, by way of non-limiting and illustrative example only, and that it is by no way intended to be understood as limiting the disclosure to the disclosed details.

[0219] For certain use cases, a goal of a sensing service is to obtain awareness of a vicinity of a location. A sensing service may, for example, enable (or otherwise facilitate) to detect, localize and track objects, to form images, and / or to extract features for recognition / classification purposes, etc.

[0220] The integration of sensing and communication (ISAC) can help to potentially achieve both high-data rate communications and high-resolution sensing data (e.g., for obstacle detection) using the same hardware and spectrum resource. ISAC may increase sensing capabilities, improve sensing accuracy for scenarios or situations that traditional sensing techniques may not perform well (e.g., NLOS conditions, requirements for high velocity resolution, etc.). ISAC also may enhance spectrum efficiency by sharing communication and sensing spectrum band and may also reduce hardware cost by combining sensing and communication equipment / hardware.

[0221] Different types of services and target vertical applications could benefit from providing sensing measurement data (also denoted as sensing data), provided by a sensing device which may or may not use the integrated sensing and communication services:

[0222] - intrusion detection (e.g., intruder detection in smart home, pedestrian / animal intrusion detection on a highway); autonomous driving support (e.g., sensing assisted automotive maneuvering and navigation, sensing for parking space determination, etc.); support unmanned aerial vehicle (UAV) flight (e.g., UAV flight trajectory tracing, network assisted sensing to avoid UAV collision); support automated guided vehicle (AGV) I autonomous mobile robots (AMR) in factories (e.g., AGV detection and tracking in factories I AMR collision avoidance in smart factories) ; environment / weather monitoring (e.g., rain, pollution, flooding);

[0223] Health monitoring (e.g., fall detection, contactless sleep monitoring service, health monitoring at home);

[0224] - XR-relevant.

[0225] In order to enable (or otherwise facilitate) wireless sensing, a sensing management function (SeMF, typically included in 5GC) may be responsible to receive different types of sensing requests from a sensing client (e.g., UE or Application Function (AF) or Network Function (NF)), to coordinate sensing operations, and to control the collecting of sensing measurement (sensing data) and to provide the sensing data and / or sensing outputs (obtained based on the sensing data) to the sensing client either directly or via NEF (via NEF, if the requesting client is a third party external application or AF, for example). The SeMF receives requests that include information about the type of the sensing service, the sensing area, the sensing QoS, optionally UE(s) that should be sensed, optionally information about the objects to be sensed, optionally the UE(s) that may be involved in the sensing operation, etc.

[0226] There are different sensing methods / types that could be used, for example in an integrated sensing and communication system. RAN nodes (e.g., BS) can participate in a sensing session either for monostatic sensing or for bi-static sensing. The meaning of these terms is as follows:

[0227] Monostatic RAN-based sensing (see Fig. 1a): A Base Station (BS) 14 acts as transmitter / sounder (Transmit Sensing Signal) and the same BS 14 acts as a receiver / sensor (Receive Sensing Signal). It employs a system in which the transmit and receive arrays are placed together.

[0228] Bi-static RAN-based sensing (see Fig. 1b): A BS 24 acts as transmitter / sounder (Transmit Sensing Signal) and one or more other BSs 26 act as receiver(s) / sensor(s) (Receive Sensing Signal).

[0229] Bi-static RAN and UE-assisted sensing: o RAN (BS) transmits a sensing signal and UE(s) receives the sensing signal to obtain sensing data. o UE 34 transmits a sensing signal and RAN (e.g., BS 36) receives the sensing signal to obtain sensing data (see Fig. 1c).

[0230] The sensing data (also denoted sensing measurement or sensing measurement information) include data derived from radio signals (e.g., 3GPP, non-3GPP, WiFi, radar, Lidars, etc.) impacted (e.g., reflected, refracted, diffracted) by an object or environment of interest for sensing purposes, and optionally processed (e.g., within a 5G / 6G system, external server, application server, edge server, etc.). The sensing output(s) include processed sensing data (e.g., requested by a service consumer (or sensing client)). For example, the sensing data may be derived from received radio signals that result from transmitted radio signals used for communication of a BS with a UE, or the sensing data may be derived from transmitted radio signals that result from received radio signals not used for communication with a UE. The transmitted radio signals may, in some example embodiments, be dedicated for the sensing only. The BS measuring the characteristics of the received radio signal may be the same or different from the BS transmitting the transmitted radio signal. For the sensing methods, the RAN node (e.g., eNB or gNB) may send the collected sensing data to the sensing data processing unit. The sensing data processing unit may be a standalone entity or integrated in the SeMF or another entity inside and / or outside the PLMN domain.

[0231] In Figs. 1a to 1c, it is assumed that the sensing data processing unit (also denoted “processing unit”) is integrated in SeMF 11 , 21 , 31. Fig. 2 shows an example where RAN nodes 46, 47 send sensing data to processing unit 48 (e.g., as a dedicated AF and / or deployed at an edge application server of a mobile edge computing platform)) that is not collocated with the SeMF 41. In some deployments, the sensing data processing unit may be integrated in a RAN node or be deployed as a dedicated entity at the RAN domain.

[0232] According to some example embodiments, these different sensing methods may be described as follows:

[0233] Fig. 1a is a block diagram showing a monostatic sensing system for a wireless communication system, indicated generally by the reference numeral 10, in accordance with an example embodiment. The monostatic sensing system 10 comprises a first RAN node 14 (a gNB in the example shown). The first RAN node 14 sends out (e.g., transmits) sensing signals (e.g., RF signals) when the first RAN node 14 is configured for a sensing operation (e.g., a monostatic sensing operation). Therefore, the first RAN node 14, when configured for a monostatic sensing, is considered to be (or is acting as) a sensing transmitter. The first RAN node 14 also receives sensing signals (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects (e.g., object 12) in a vicinity of the first RAN node 14 when the first RAN node 14 is configured for a sensing operation (e.g., a monostatic sensing operation). Therefore, the first RAN node 14, when configured for a monostatic sensing operation is also considered to be or is acting as a sensing receiver.

[0234] Fig. 1 b is a block diagram showing a bistatic sensing system for a wireless communication system, indicated generally by the reference numeral 20, in accordance with an example embodiment. The sensing system 20 comprises a first RAN node 24 (a gNB in the example shown) and a second RAN node 26 (also a gNB in the example shown). The first RAN node 24 sends out sensing signals (e.g., radio signals), when configured for a sensing operation (e.g., a bistatic sensing operation). Therefore, the first RAN node 24, when configured for a bistatic sensing operation, is thereby configured to be (or is considered to be acting as) a sensing transmitter. The second RAN node 26 receives sensing signals deflected, reflected or refracted by objects (e.g., object 22) located in a vicinity of the second RAN node 26 when the second RAN node is configured for a sensing operation (e.g., a bistatic sensing operation). Therefore, the second RAN node 26 is configured to be (or is considered to be acting as) a sensing receiver when the second RAN node 26 is configured for a bistatic sensing operation.

[0235] In the sensing system 10, the first RAN node 14 receives sensing data (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects (such as object 12). Similarly, in the sensing system 20, the second RAN node 26 receives sensing data (e.g., radio signals) deflected, reflected or refracted by objects (e.g., object 22).

[0236] In the sensing system 10, the first RAN node 14 receives sensing signals (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects (such as object 12). Similarly, in the sensing system 20, the second RAN node 26 receives sensing signals (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects (such as object 22). In the sensing systems 10 and 20, sensing measurement data (or sensing data / sensing measurement information) include data derived from sensing signals (e.g., radio signals) impacted (e.g., reflected, refracted, diffracted) by an object in an environment of interest when performing a sensing operation (e.g., the objects 12 or 22), and optionally processed (e.g., by a network function within a wireless communication system, such as a 5G and / or 6G system, a server external to the wireless communication system, application server connected to the wireless communication system via, for example, a network exposure function of the wireless communication system, edge server (e.g., a server located near the wireless communication server), etc.). Sensing output(s) may include processed sensing data (e.g., requested by a sensing service consumer (or sensing service client)) of a sensing service provided by the 5G and / or 6G system that includes the sensing system 10 and / or the sensing system 20.

[0237] Examples of sensing data or sensing measurement information comprise information about received electromagnetic signals or electromagnetic signals to be received. Information about a received electromagnetic signal or an electromagnetic signal to be received may include a received power, delay, angle of departure, angle of arrival, Doppler shift, and / or the like of the received electromagnetic signal or the electromagnetic signal to be received.

[0238] The systems 10 and 20, therefore, differ in that in the monostatic sensing system 10, the first RAN node 14 is configured to be (or to act as) both the sensing transmitter and the sensing receiver. In the bistatic sensing system 20, different RAN nodes are configured to be (or to act as) sensing transmitters and receivers. Note also that the bistatic sensing system 20 is a special case of a multi-static sensing system in which one RAN node is configured to be (or to act as) a sensing transmitter and a plurality of RAN entities may be configured to be (or act as) sensing receivers. In the monostatic sensing system 10 and the bistatic sensing system 20, the sensing transmitters and receivers are both RAN entities (e.g., BSs, gNBs); this feature is not present in all example embodiments.

[0239] For example, user devices (e.g., user equipment) for a wireless communication system can be configured as sensing transmitters and / or sensing receivers. Fig. 1c is a block diagram showing such a sensing system for a wireless communication system, indicated generally by the reference numeral 30, in accordance with an example embodiment. The sensing system 30 comprises a transmitter 34 (e.g., a UE, such as a UE on a vehicle in the example shown) and a RAN node 36 (a gNB in the example shown). The transmitter 34 sends out sensing signals (e.g., radio signals), when configured for such a sensing operation. Therefore, the transmitter 34, when configured for such a sensing operation, is thereby configured to be or is considered to be acting as a sensing transmitter. The RAN node 36 receives sensing signals deflected, reflected or refracted by objects (e.g., object 32) located in a vicinity of the RAN node 36 when the RAN node is configured for a sensing operation (e.g., a bistatic sensing operation). Therefore, the RAN node 36 is configured to be (or is considered to be acting as) a sensing receiver when the RAN node 36 is configured for a bistatic sensing operation.

[0240] The sensing data collected at the RAN nodes (with or without any processing at the RAN nodes) should be provided to the sensing data processing unit, which may be located, for example, at the SeMF, or be stand-alone, etc. Often, a RAN node - but not a UE - is the source of these collected sensing data. The sensing data traffic, depending on the sensing configuration determined at the SeMF, can include a large volume of data that is to be transmitted from the RAN node(s) to the processing unit. In some example embodiments, the sensing data is to be transmitted in a continuous way and / or with specific QoS requirements (e.g., in terms of delay, data rate, and so forth).

[0241] For certain use cases, the usage of control plane channels for the reporting may not considered to be an efficient option in view of the QoS requirements and the large amount of data that one or more RAN nodes should report. Hence, according to some example embodiments, a data plane path is be established between the RAN node(s) and the sensing data processing unit. This data plane path (e.g., sensing data session) is designed taking into consideration the features / characteristics of the transmitted sensing data. In particular, according to some example embodiments, at least one of the following technical problems is solved:

[0242] How to realise a data plane transmission between the RAN node and the sensing data processing unit for sensing data reporting? This sensing data processing unit may be located in the 5G Core network and / or located outside thereof, e.g., reachable via N6 interface.

[0243] How is the data traffic path between the RAN node and the sensing data processing unit for the sensing data reporting established and configured?

[0244] Some example embodiments may be implemented in a 5G and / or in a 6G environment, or in 3GPP networks of a higher generation. In the 6G architecture, the example embodiments may use Service-Based Interface(s) (SBI) between the RAN and the Core Network.

[0245] As used herein, sometimes the term “data plane” is used to refer to a type of tunnel / path that is used to report the sensing data. However, the term “user plane” may be also used, considering that current standards sometimes utilize this term to describe the data that traverse the UPF(s) sent by (or to) the UEs.

[0246] According to some example embodiments, one or more of the following functions are involved in the process of reporting the sensing data from the RAN node (e.g., eNB or gNB) to the processing unit:

[0247] - SeMF;

[0248] - RAN node;

[0249] - UPF;

[0250] - SMF; or

[0251] - the sensing data processing unit, which receives the reported sensing data and may process them according to some predefined logic.

[0252] For these functions, some tasks are listed hereinafter. According to some example embodiments, each of the functions may perform at least one of the following listed tasks.

[0253] The Sensing Management Function (SeMF) may, for example:

[0254] Select the RAN nodes involved in the sensing data reporting unless the request from the sensing client defines (explicitly or implicitly) the involved RAN nodes.

[0255] Determine the configuration of the data plane for the sensing data reporting for each RAN node involved in the sensing data session.

[0256] This may induce acquisition (e.g., to Get) from the sensing data processing unit information about the data plane termination for the sensing data session at the sensing data processing unit: this may correspond to sensing data processing unit addressing information and or tunnel information and / or data plane security enforcement information. Select one or more UPFs (sensing data forwarding function) and transmit to the selected UPF(s) a request to establish / modify the tunnels for data plane sensing data reporting from the one or more RAN nodes as well as the tunnels towards the sensing data processing unit, including the determined configuration of the corresponding tunnels. These tunnels, in some example embodiments, are not related to a UE (e.g., terminal). For example, the requests setting up these tunnels do not comprise any UE identifier or UE context information. These tunnels are used to establish the sensing data session for transmitting the sensing data from the RAN node(s) to the sensing data processing unit.

[0257] Where at least an UPF is involved, the SeMF may receive from the UPF a response with the acknowledgement for the establishment / modification of the requested tunnels and information on the tunnels established at the UPF.

[0258] Transmit to the RAN node(s) a request to establish / modify the tunnels for data plane sensing data reporting from each RAN node towards the UPF or directly towards the sensing data processing unit. These tunnels, in some example embodiments, are not related to a UE (terminal). For example, the requests setting up these tunnels do not comprise any UE identifier or UE context information. These tunnels are used to establish the sensing data session for transmitting the sensing data from the RAN node(s) to the sensing data processing unit.

[0259] SeMF and RAN node are typically connected by LAN or WAN, but not by a radio interface (such as, the interface between UE and RAN node), where the RAN node schedules the resources (e.g., time, frequency band). Therefore, SeMF may send the request to the RAN node directly or via the AMF over an interface (e.g., over an NG- C interface) using a non-U E associated mode. The Next Generation Application Protocol (NGAP) protocol, terminated between the AMF and the NG-RAN Node, may be used as a transport protocol for transporting sensing protocol messages over the NG-C interface, but other mechanisms, such as using an HTTP interface from SeMF to RAN, are possible.

[0260] Receive from the RAN node(s) a response with the acknowledgement for the establishment / modification of the requested tunnels and RAN node tunnel information. Transmit to the UPF when an UPF is involved and / or the sensing data processing unit (if not collocated with SeMF) the RAN nodes tunnel information.

[0261] According to some example embodiments, the SeMF may, for example:

[0262] Determine a sensing method (e.g., monostatic sensing, bistatic sensing, or multi-static sensing) and determine a sensing configuration for the RAN nodes (e.g., BSs, such as gNBs) and / or UEs identified or selected to be involved in a sensing session for the determined sensing method taking into consideration a) the information (e.g., requirements) included in a sensing service request received from the sensing serving client (e.g., sensing area for the sensing service, QoS requirements for the sensing service) and b) the static and / or dynamic sensing capabilities of RAN nodes. For instance, in the case the determined sensing method is monostatic sensing, the SeMF may identify or select one or more RAN nodes to be involved in and determine or generate a sensing configuration for the one or more RAN nodes for configuring the one or more RAN nodes as a sensing transmitter (Tx) and a sensing receive (Rx) based on the determined sensing method, and provide the sensing configurations to the one or more RAN nodes. Alternatively, in the case of bistatic sensing and / or multi-static sensing is determined, identify or select one RAN node to be a sensing transmitter and one or more other RAN nodes (e.g., BSs) to be sensing receivers and determine or identify a sensing configuration for configuring the one RAN node to be a sensing transmitter and sensing configurations for configuring the one or more other RAN nodes (e.g., BSs) to be a sensing receiver.

[0263] May optionally execute sensing admission control, which identifies whether the identified or selected RAN nodes have the available sensing resources for the requested sensing service (e.g., sensing requirements) and determine a sensing resources configuration for the identified or selected RAN nodes. The sensing resources configuration may include reference signals and / or pilots and / or user data and control plane resources, depending on the approach or scheme that a selected monostatic, bistatic or multi-static method realizes. Alternatively, as described below the admission control can take place at one or more RAN nodes.

[0264] Transmit a sensing session establishment request to the one or more RAN nodes to establish a sensing session, according to the selected sensing method (monostatic, bistatic or multi-static sensing), including one or more of the following: a sensing configuration for each respective selected RAN node for configuring the respective RAN node as a sensing transmitter and / or sensing receiver and or UE; sensing resources configuration. Each sensing session may comprise one or more (subprocedures. For instance, the RAN node is first requested (first sensing (subprocedure) to issue coarse sensing, and then to issue a more precise sensing (second sensing (sub-)procedure). Or as another example, the RAN conducts sensing using a monostatic sensing method (first sensing (sub-)procedure) and also conducts sensing being the receiver of a bi-static sensing method (second sensing (subprocedure) all in the context of the same request or sensing session.

[0265] If the SEMF is collocated with the sensing data processing function, SeMF may utilize the addressing information of the sensing data processing unit anyway. Otherwise (or in addition), SeMF may access the addressing information of the sensing data processing unit in one or more of the following ways: o it may be preconfigured, o it may be received from a repository, o it may be received from the request for the sensing session.

[0266] Once the SeMF has received base station addressing information and possibly associated tunnel information (that may refer to a tunnel terminated at the base station or at an intermediate UPF), the SeMF may configure the sensing data processing unit with this information.

[0267] A sensing data session is associated to each RAN node that is involved in a sensing session. A sensing data session at a RAN node is used for one or more sensing procedures that are part of a specific sensing session. A sensing procedure corresponds to a request from SeMF at the RAN node to measure sensing data (e.g., at a defined radio resource and by a defined sensing method).

[0268] The Sensing Data Processing Unit (SDPU) may, for example:

[0269] Receive from SeMF a request to establish / modify the tunnels for Data Plane Sensing Data Reporting from each RAN node.

[0270] Transmit, to SeMF, sensing data processing unit’s addressing and possibly tunnel information to be associated with a sensing session.

[0271] Receive base station addressing information and possibly associated tunnel information (that may refer to a tunnel terminated at the base station or at an intermediate UPF) from the SeMF and associate it with the sensing session.

[0272] - Acknowledge the establishment / modification of the sensing data session and the association with the corresponding addressing and possibly tunnel information.

[0273] If the sensing data processing unit is integrated with SeMF, the request and the corresponding acknowledgment may be omitted.

[0274] The addressing and possibly tunnel information may, for example, be used to establish a sensing data session between each RAN node(s) and the sensing data processing unit to exchange the sensing data between the RAN node(s) and the sensing data processing unit (e.g., to transmit the sensing data from the RAN node(s) to the sensing data processing unit).

[0275] According to some example embodiments, any RAN node configured to operate as a sensing receiver may obtain sensing data (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects and are provided to the sensing data processing unit (with or without any initial processing of the sensing data at the RAN node). The sensing data processing unit processes the collected sensing data and specifically information about a received electromagnetic signal or an electromagnetic signal to be received which may include a received power, delay, angle of departure, angle of arrival, Doppler shift, and / or the like of the received electromagnetic signal or electromagnetic signal to be received. This information is transmitted from the RAN node to the sensing data processing unit over the sensing data session. The sensing data processing unit processes the sensing data to generate sensing output data, which is provided to a sensing client / consumer. Sensing output data may include data about the objects in a vicinity of a location (e.g., vicinity of a first RAN node, vicinity of a second RAN node) and / or data about features or data about those objects. For example, one or more of the location, speed, velocity, shape, material, and / or dimensions of the object may be data about the objects in the vicinity of a location.

[0276] The sensing data processing unit can optionally provide to the sensing client / consumer the sensing data.

[0277] RAN node (e.g., NR BS, LTE BS, ...) may, for example:

[0278] Receive from the SeMF the request to establish / modify the tunnels for data plane sensing data reporting via a sensing data session possibly together with the sensing data processing unit addressing information and with possibly associated tunnel information (that may refer to a tunnel terminated at the sensing data processing unit or at an intermediate UPF). The request is typically received via LAN or WAN. Hence, it is not received on a resource (e.g., time, frequency) scheduled by the RAN node for the transmission of the request. The request may, in some example embodiments, not comprise any UE ID or UE context.

[0279] - Associate sensing data processing unit addressing information and possibly associated tunnel information with the local (e.g., at the RAN node) sensing session, acting as a sensing data reporting function. The tunnel is used to establish a sensing data session from the RAN node(s) to the sensing data processing unit and may be used to transmit the sensing data from the RAN node(s) to the sensing data processing unit.

[0280] The sensing data reporting function may be implemented at the RAN node (BS) measuring the characteristics of the radio signal to obtain the sensing data, or at a different RAN node. In the latter case, the characteristics of the radio signal and / or the sensing data derived therefrom are transferred from the former RAN node to the latter RAN node prior to transmitting the sensing data to the sensing data processing unit. Transmit the response to the SeMF acknowledging the establishment / modification of the sensing data reporting session, providing the RAN node addressing information and possibly associated tunnel info related to the RAN node Generate and transmit sensing data packets to the sensing data processing unit via the established sensing data session, indicating relevant, sensing process ID, reporting RAN node ID, sensing data and descriptors of the received and reposted sensing data. The sensing data do not comprise user data to / from a UE. In particular, the generation thereof may typically not comprise any demodulating or decoding a received signal (such as, demodulating and / or decoding a signal received on a resource scheduled for uplink transmission of a UE).

[0281] According to some example embodiments, each involved RAN node may, for example:

[0282] - Configure itself after establishment of the sensing session, according to the received sensing resources configuration and cause the respective RAN nodes to perform a sensing operation.

[0283] - The RAN node (e.g., BS) executes or performs a sensing operation by allocating and / or scheduling resources according to the received sensing configuration. For example, the RAN node (e.g., BS) transmits reference signals and / or pilots or Physical Downlink Channel for user data with frequency, time and spatial (e.g., Tx antenna, beam) resources to satisfy a QoS for the requested sensing service. The RAN node (e.g., BS) may also attempt to receive and measure its own transmitted signal with the sensing configuration received for sensing.

[0284] In some example embodiments, the RAN node may conduct sensing admission control and determine the sensing resources for transmitting or receiving sensing signals, based on the sensing requirements and optionally some resources configuration received from the SeMF. The SeMF may provide to the RAN node (e.g., BS) information, such as a QoS for the requested sensing session, an indication of a type of sensing service that is requested, sensing requirements for the sensing session (e.g., sensing area, sensing duration, sensing update rate etc.) that can allow the one or more RAN nodes (e.g., BSs) to determine the required resources for the sensing session. The RAN node (e.g., BS) configured to be or act as sensing transmitter (e.g., having a sensing transmitting role when, for example, the SeMF selects the RAN node to be involved in a bi-static sensing method) can provide its sensing resource configuration (e.g., sensing signal frequency, bandwidth, the timing when a sensing signal is transmitted by the RAN node (e.g., BS)) and / or the sensing session configuration to: one or more RAN nodes (e.g., BSs) configured to be or acting as sensing receiver (e.g., having a sensing receive role) for the respective sensing session.

[0285] Sensing Data Forwarding Function (e.g„ UPF) may, for example:

[0286] Receive from the SeMF a request to establish / modify the tunnels for data plane sensing data reporting from the one or more RAN nodes as well as the tunnels towards the sensing data processing unit, with the determined configuration of the corresponding tunnels. The tunnels are used to establish a sensing data session from the RAN node(s) to the sensing data processing unit to exchange the sensing data between the RAN node(s) and the sensing data processing unit.

[0287] Transmits to the SeMF a response with the acknowledgement for the establishment / modification of the requested tunnels and information on the tunnels established at the UPF (including for example tunnel identifiers required by the SeMF).

[0288] The GTP-ll header of the sensing data packets may have an extension header type to indicate the usage of the tunnel for the transmission of sensing data and / or the establishment of the data plane connection between the RAN node and the sensing data processing unit for reporting the sensing data.

[0289] Typically, the receiver acknowledges the receipt of a message, such as a request, as outlined in the above list. However, in some example embodiments, the acknowledgment may be omitted. The sender of the message may simply assume that the receiver received the message and acted successfully based on the message.

[0290] The above list assumes that the sensing data is transmitted through tunnels between the RAN node and UPF and UPF and the processing unit (example embodiment 1), or directly through a tunnel between the RAN node and the processing unit (example embodiment 2).

[0291] Some example embodiments are explained in further detail hereinafter.

[0292] Example Embodiment 1 : SeMF-based configuration of the Sensing Data Reporting from RAN to the Sensing Data Processing Unit via UPF

[0293] Fig. 3 presents the establishment of the data plane path for the reporting of sensing data from a RAN node to the sensing data processing unit via UPF according to example embodiment 1 . The actions are as follows:

[0294] - Action 0: The SeMF has received a sensing request from a sensing client (e.g., AF, UE, NF). Typically, in the request the type of the sensing service is described, potentially together with the sensing requirements and / or sensing QoS. The request may include a list of RAN nodes involved. Fig. 3 shows an example that the request is sent from an AF. In another example, if a UE sends the request, the UE may send the request using RRC or NAS signaling. - Action 1 : The SeMF configures the sensing methods and identifies the RAN nodes that are involved. If the request of Action 0 identifies the RAN nodes, SeMF need not to identify the RAN nodes.

[0295] - Action 2:

[0296] Get from the sensing data processing unit information about the data plane termination for the sensing session at the sensing data processing unit: this may correspond to sensing data processing unit addressing information and or tunnel information and / or data plane security enforcement information.

[0297] The SeMF selects and configures the data plane sensing data reporting from each involved RAN node (BS), which includes one or more of the following: o Possibly Selection of UPF(s) when UPF is used between the BS and the sensing data processing unit (SeMF can select one or more UPFs, as described in clause 6.3.3 of 3GPP TS 23.501); UPF may e.g., be used between a BS and a sensing data processing unit in order to isolate the RAN IP network from the 3GPP Core network IP network (e.g., when both use private IP addresses) o determination of the packet detections rules for the packets of sensing data from each RAN node to the UPF and then to the sensing data processing unit o determination of packet forwarding rules of sensing data from each RAN node to the UPF and then to the sensing data processing unit o determination of the QoS requirements for the data plane path (sensing data session) between each RAN node and the sensing data processing unit o Identifier of the sensing data session, to identify the data plane path between the RAN node and the sensing data processing unit.

[0298] - Action 3: (when a UPF is involved) The SeMF transmits the request to the UPF to allocate CN tunnel info for the applicable N3 / N9 reference points providing one or more of the following information. o Addressing and tunnel information of the sensing data processing unit (e.g., IP address) o Identifier of the sensing data session o information for the sensing data session at the UPF (More details are provided below):

[0299] ■ Data packet detection rules: Flow descriptors or packet filters to detect the sensing data packets

[0300] ■ Sensing data packet forwarding rules, to define the forwarding action that should be applied

[0301] ■ QoS rules of the sensing reporting path (sensing data session) that has to be applied. - Action 4: The UPF installs received packet detection, enforcement and reporting rules for the sensing data reporting session from each RAN node.

[0302] - Action 5: The UPF transmits the response to the SeMF acknowledging the establishment / modification of the sensing data reporting session. The UPF provides the CN tunnel info requested by the SeMF e.g., CN tunnel info related with the N3 interface, the CN tunnel info at the sensing data processing unit side.

[0303] - Action 6: The SeMF transmits the sensing reporting establishment request to each RAN node (BS) that collects sensing data, so as to configure the BS with the tunnel, including one or more of the following information: o Sensing session ID (the sensing session is for configuring and / or controlling the RAN node (base station) to obtain the sensing data, for the established sensing session) o RAN node ID and possibly address information (e.g., IP address) may be provided to the AMF if the AMF is used as a signaling relay between SeMF and the RAN node. In that case a new Namf_Communication service operation (3GPP TS 23.502, clause 5.2.2.2) may be defined for the SeMF to request AMF to transfer a request to the RAN node (e.g., sensing reporting establishment request) whose RAN node ID is indicated as input of the AMF service operation. In that case the AMF may be transparent to the content of the sensing reporting establishment request apart from the identifier of the sensing data session o Identifier of the sensing data session o Information on the sensing data to be transmitted in the sensing data session; o Addressing information of the sensing data processing unit (e.g., IP address) o QoS information for the sensing data session, such as QoS Profile(s) for the N3 tunnel that will be used to report / transmit sensing data by the RAN node o CN tunnel info of the core network address(es) of the N3 tunnel corresponding to the sensing data reporting session o Configuration information of the N3 tunnel (e.g., “always on” configuration) o data plane security enforcement information

[0304] - Action 7: The RAN node establishes the N3 tunnel and associates the local sensing application (e.g., the application responsible for the collection of processed or nonprocessed sensing data, also named sensing data reporting function) with the respective sensing session ID and the associated N3 tunnel for the reporting of sensing data, according to the configuration that the SeMF has provided.

[0305] - Action 8: The RAN node transmits the response to the SeMF acknowledging the establishment of the sensing data session (may be denoted as sensing data reporting session, too). The RAN node provides the Access Network (AN) tunnel info related with the RAN node where N3 terminates.

[0306] - Action 9: The SeMF transmits the received AN tunnel information to the involved UPF (if an UPF is involved).

[0307] - Action 10: The SeMF configures the sensing data processing unit with the AN address and, if applicable, remote tunnel info.

[0308] The SeMF with the finalization of the establishment of all sensing data reporting paths, may request the involved RAN nodes to initiate the sensing and / or the reporting of sensing data to the sensing data processing unit via the sensing data session (e.g., SeMF if the sensing data processing unit is integrated with SeMF).

[0309] In action 11 (that may occur multiple times) the sensing data session can be used for one or more sensing procedures, in the context of the same sensing session that may run between the SeMF and the sensing data processing unit on one side and the BS on the other side. Each sensing procedure may correspond to the exchange of sensing data between the RAN node (BS) and the sensing data processing unit and to sensing related actions over the air at the BS side (BS sending sensing related signal over the radio and / or BS measuring sensing related signal over the radio (or receiving from another RAN node or UE their measured sensing related signal over the radio)). The BS may transmit sensing data (e.g., corresponding to measured I received sensing related signal over the radio) to the sensing data forwarding function (e.g., UPF) which forwards them to the sensing data processing unit (“sensing data reporting”). In addition, the sensing data processing unit can also use the established sensing data reporting path (e.g., the sensing data session) to transmit acknowledgement of the successful or not reception of sensing-related information transmitted by the BS(s) (e.g., TCP / QUIC ACK, NACK messages, application layer AKC / NACK, etc). In addition, the sensing data processing unit can use the established sensing data reporting path (e.g., the sensing data session) to transmit configuration information to the BS(s), based on the outcomes of the processed sensing data. Also, the sensing data processing unit can use the established sensing data reporting path (e.g., the sensing data session) to provide specific information to the BS(s) about the radio signals that the BS(s) could transmit to sense the environment (e.g., in the form of data to be included in transmitted data packets used for sensing or configuration of transmitted radio signals used for sensing on specific resources).

[0310] At the end (action 12), the SeMF sends a sensing service response to the requester (of step 0).

[0311] The addressing information of the sensing data processing unit may be one or more of the following: an FQDN of the sensing data processing unit; one or more combinations of IP addresses and ports of the sensing data processing unit for the sensing data session; a uniform resource locator for the data session on the sensing data processing unit. The tunnel information at the sensing data processing unit may correspond to a fully qualified GTP-u tunnel id for the sensing data session.

[0312] The fully qualified GTP-u tunnel id at the UPF can be a fully qualified tunnel id identifying resources at a UPF (e.g., a sensing data forwarding function) that will be used for forwarding traffic (e.g., sensing data) between the base station and the sensing data processing unit.

[0313] A fully qualified GTP-u tunnel id (F-TEID) comprises a GTP-u TEID together with an IP address of the entity using this TEID as a tunnel reference for incoming traffic.

[0314] The addressing information of the RAN node may be one or more of the following: an FQDN of the RAN node; one or more combinations of IP addresses and ports of the RAN node it for the sensing data session; a uniform resource locator for the data session on the RAN node. The tunnel information at the RAN node may correspond to a fully qualified GTP-u tunnel id for the sensing data session. The fully qualified GTP-u tunnel id can be a fully qualified tunnel id identifying resources at a UPF (e.g., a sensing data forwarding function) that will be used for forwarding traffic (e.g., sensing data) between the base station and the sensing data processing unit.

[0315] The information on the sensing data to be transmitted from the BS to the sensing data processing unit, in the sensing data session, can include one or more of the following information: information on which radio signal of the BS to transmit sensing signals; information on which radio signal of the BS to measure and obtain the sensing data; information on the radio signals of the BS to transmit sensing signals and / or receive sensing data, such as time and / or frequency of the respective radio signal; and / or information on the periodicity and / or duration to transmit sensing signals and / or measure the (sensing) radio signal.

[0316] In Action 8, the BS in the response can include addressing information including one or more of the following: an FQDN of the sensing data reporting function; one or more combinations of IP addresses and ports of the sensing data reporting function for the sensing data session; a fully qualified GTP-u tunnel id for the sensing data session at the sensing data reporting function; a uniform resource locator for the data session on the base station. Fig. 4 illustrates the involved interfaces: SeMF interacts with UPF and BS to set up the tunnel between BS (the receiver of the signals on which the sensing data is based) and UPF and the tunnel from UPF to the sensing data processing unit. If the sensing data processing unit is not integrated with SeMF (as shown in the example of Fig. 4), SeMF interacts with the processing unit to set up the tunnel between UPF and the processing unit, too. In Fig. 4, the established tunnels are indicated by bold lines. SeMF may interact with BS directly (e.g., in a 6G network) or via AMF (e.g., in a 5G network, not shown in Fig. 4).

[0317] The parameters over N4 reference point provided from SeMF to UPF (in Action 4) comprises an N4 Session ID and may also comprise:

[0318] Packet Detection Rules (PDR) that comprise information to classify traffic sensing data traffic (e.g., SDU(s)) arriving at the UPF; o N4 Session ID o Source interface (e.g., "access side", "core side", ) o BS address (e.g., IP address) o CN tunnel info (e.g., CN tunnel info on N3, N9 interfaces, such as F-TEID.) o Packet Filter Set (IP or Ethernet Packet Filter Set)

[0319] ■ Source / destination IP address or IPv6 prefix

[0320] ■ Source I destination port number

[0321] ■ Protocol ID of the protocol above IP / Next header type

[0322] ■ Type of Service (TOS) (IPv4) / Traffic class (IPv6) and mask

[0323] ■ Flow Label (IPv6)

[0324] ■ Security parameter index

[0325] ■ Packet filter direction o Forwarding Action Rule ID

[0326] ■ Rule ID

[0327] ■ Action

[0328] ■ Destination interface (e.g., "access side", "core side", and so forth)

[0329] ■ Outer header creation (e.g., comprises the CN tunnel info, N6 tunnel info or AN tunnel info of peer entity (e.g., NG-RAN, another UPF, and so forth)) o List of QoS Enforcement Rules ID

[0330] ■ Each QoS enforcement rules ID comprises information related to QoS enforcement of traffic identified by PDR(s) (e.g., Sensing Related QoS from the BS to the UPF and the UPF to the processing unit):

[0331] • Gate status UL / DL: Instructs the UP function to let the flow pass or to block the flow • Maximum bitrate: The maximum bitrate to be enforced for the sensing data packets

[0332] • Guaranteed bitrate: The guaranteed bitrate authorized for the sensing data packets

[0333] • Averaging window: The time duration over which the maximum and guaranteed bitrate shall be calculated

[0334] • Packet rate: Number of packets per time interval to be enforced.

[0335] The N4 Session ID is assigned by the SeMF and uniquely identifies an N4 session for the establishment of the sensing data reporting from the RAN node and the sensing data processing unit. Additional parameters / services of the N4 interface (as presented in section 5.8.5 of 3GPP TS 23.501 , for example) can be configured by the SeMF (e.g., usage reporting rules, session reporting rules etc...).

[0336] In the case that the sensing data processing unit is not collocated with the SeMF and / or according to the location of the sensing data processing unit the SeMF can indicate to the UPF the type of tunnel / path (e.g., N6) that can be established between the UPF and sensing data processing unit.

[0337] In that case, the SeMF can provide to the sensing data processing unit the sensing session ID, identifier of the sensing data session, the CN tunnel information of the UPF in the interface towards the sensing data processing unit (e.g., N6 or N9 interface) and other configuration information (e.g., Packet Detection Rules, QoS Enforcement Rules) for the each interaction between the sensing data processing unit and the one or more RAN nodes.

[0338] The exchange of messages among the SeMF, UPF, the sensing data processing unit (in case it is inside the domain of a PLM N) and RAN nodes for the establishment, release, modification, and management of the data plane path for the sensing data reporting (a sensing data session) may take place via service-based interfaces, as an option. An an alternative option, the interaction between the one or more RAN nodes and the SeMF for the establishment, release, modification, and management of the sensing data session may be realized via direct interface or via the AMF over an interface (e.g., over an NG-C interface) using a non-UE associated mode.

[0339] Example Embodiment 2: SeMF-based Configuration of the Sensing Data Reporting from RAN to the Sensing Data Processing Unit without the Involvement of a UPF As an alternative option to that of the example embodiment 1 , the SeMF can deploy the path (sensing data session) between the RAN node and the sensing data processing unit without the involvement of a UPF entity. As shown in Fig. 5, in that case the SeMF transmits to the processing unit the request to establish the data plane path with each one of the RAN nodes that will report sensing information (e.g., the sensing data session). To instantiate a session, appropriate tunnels may be set up, for instance a N3 tunnel, between a BS and sensing data processing unit, which has a tunnel endpoint at the BS and another tunnel endpoint at the sensing data processing unit (sensing data processing unit tunnel info). The SeMF can select the configuration of the tunnel at the sensing data processing unit (action 2) and transmit (action 3) to the latter the required information (e.g., BS(S) ID and BS addressing information (e.g., IP address), sensing session ID, sensing data packet detection rules, sensing data packet forwarding rules for packets transmitted from the sensing data processing unit to the RAN node, QoS rules of the sensing reporting path from the sensing data processing unit to the RAN node etc). The sensing data processing unit configures the tunnel(s) according to the provided configuration information (action 4) and sends to the SeMF (action 5) the acknowledgement as well as the tunnel information of the sensing data processing unit (Pll). The other actions in Fig. 5 are similar to those in the Fig. 3 with the difference that the SeMF provides to the one or more RAN nodes the tunnel information of the sensing data processing unit instead of the UPF, including addressing information of the sensing data processing unit (step 6). Also, in step 9 the SeMF transmits to the sensing data processing unit the tunnel information of the AN.

[0340] In action 10 (that may occur multiple times) the sensing data session can be used for one or multiple sensing procedures, in the context of the same sensing session that may run between the SeMF and the sensing data processing unit on one side and the BS on the other side. Each sensing procedure may correspond to the exchange of sensing data between the RAN node (BS) and the sensing data processing unit and to sensing related actions over the air at the BS side (BS sending sensing related signal over the radio and / or BS measuring sensing related signal over the radio (or receiving from another RAN node or UE their measured sensing related signal over the radio). The BS may transmit sensing data (e.g., corresponding to measured I received sensing related signal over the radio) to the sensing data processing unit (“sensing data reporting”). In addition, the sensing data processing unit can also use the established sensing data reporting path (e.g., the sensing data session) to transmit acknowledgement of the successful or not reception of sensing-related information transmitted by the BS(s) (e.g., TCP / QUIC ACK, NACK messages, application layer AKC / NACK etc). In addition, the sensing data processing unit can use the established sensing data reporting path (e.g., the sensing data session) to transmit configuration information to the BS(s), based on the outcomes of the processed sensing data. Also, the sensing data processing unit can use the established sensing data reporting path (e.g., the sensing data session) to provide specific information to the BS(s) about the radio signals that the BS(s) could transmit to sense the environment (e.g., in the form of data to be included in transmitted data packets used for sensing or configuration of transmitted radio signals used for sensing on specific resources).

[0341] At the end (action 11), the SeMF sends a sensing service response to the requester (of step 0)

[0342] In case that the sensing data processing unit and the SeMF are collocated, then actions 3, 4 and 5 of Figure 5 take place at the SeMF, while action 9 is not needed.

[0343] The addressing information of the sensing data processing unit may be one or more of the following: an FQDN of the sensing data processing unit; one or more combinations of IP addresses and ports of the sensing data processing unit for the sensing data session; a uniform resource locator of the sensing data processing unit. The tunnel information at the sensing data processing unit may correspond to a fully qualified GTP-u tunnel id for the sensing data session.

[0344] The addressing information of the RAN node may be one or more of the following: an FQDN of the RAN node; one or more combinations of IP addresses and ports of the RAN node used in the sensing data session; a uniform resource locator for the data session on the RAN node. The tunnel information at the RAN node may correspond to a fully qualified GTP-u tunnel id for the sensing data session.

[0345] Similar to example embodiment 1 , the sensing data session can be used for the exchange of sensing data between the BS(s) and the sensing data processing unit.

[0346] The exchange of messages among the SeMF, RAN nodes and the sensing data processing unit (in case it is inside the domain of a PLMN) for the establishment, modification, release and management of the data plane path for the sensing data reporting (a sensing data session) may take place via service-based interfaces, as an option. An alternative option, the interaction between the one or more RAN nodes and the SeMF for the establishment, release, modification, and management of the sensing data session may be realized via direct interface or via the AMF over an interface (e.g., over an NG-C interface) using a non-UE associated mode. Example Embodiment 3: Configuration of the Sensing Data Reporting from RAN to the Sensing Data Processing Unit with the Involvement of the Session Management Function (SMF)

[0347] As another example embodiment, the SeMF interacts with the SMF for the establishment, modification and the release of the paths for the reporting of the sensing data (sensing data sessions) from one or more RAN nodes towards the sensing data processing unit.

[0348] Actions 0 and 1 are the same as in example embodiment 1. Then, the SeMF provides to the SMF one or more of the following information for the establishment / modification of the paths for the reporting of the sensing data from one or more RAN nodes towards the sensing data processing unit (“an original request”):

[0349] Sensing session ID

[0350] BS(s) ID and addressing information (e,g., IP address) sensing data processing unit addressing information (e.g., IP address).

[0351] QoS requirements of the data plane paths to be established

[0352] The SMF according to the information that the SeMF has transmitted, undertakes to determine the configuration of the tunnels between the RAN nodes and the UPF (N3) as well as the tunnels between the UPF and sensing data processing unit (e.g., N6, N9), as described in actions 2 to 9 of the example embodiment 1 .

[0353] The messages of actions 3 and 6 are transmitted from the SMF to the UPF, while the messages transmitted from the UPF (action 5) and RAN (action 8) are received by the SMF. Actions 4 and 7, are similar as in the example embodiment 1. The message in action 9 of the example embodiment 1 is sent from the SMF to the UPF.

[0354] Then the SMF informs the SeMF whether or not the establishment of the sensing data reporting path (sensing data session) was successful. In case that the SeMF is also the sensing data processing unit, the SeMF will receive from the SMF the CN tunnel information and / or tunnel information for its own interface (in case a UPF is involved, as shown in example embodiment 1).

[0355] Fig. 6 illustrates the control interactions according to the example embodiment 3. Here, SeMF interacts with SMF but not with the BS and the UPF for the configuration of the sensing data session. SMF performs these interactions. The interaction between SMF and BS may or may not go transparently via AMF. Example Embodiment 4 Configuration of the Sensing Data Reporting from RAN to the Sensing Data Processing Unit with the Involvement of the Session Management Function (SMF) but without Involvement of UPF

[0356] Similar as in example embodiment 3, where SMF takes over the interactions of SeMF with BS, UPF, and the processing unit according to the example embodiment 1 , in example embodiment 4, SMF may take over the interactions of SeMF with BS and the processing unit according to the example embodiment 2.

[0357] Example Embodiment 5: Realisation of Data Plane Sensing Data Reporting from RAN to Sensing Data Processing Unit

[0358] The reporting of sensing data from the RAN node to the sensing data processing unit is described. In the present description, it is assumed that the sensing data processing unit is integrated with SeMF. The description is correspondingly applicable for the case that the sensing data processing unit is an independent NF or an AF (trusted or non-trusted) or a M EC or collocated in a RAN.

[0359] Fig. 7 presents the protocol stack for the data plane for the transport of sensing data between the BS and the sensing data processing unit (e.g., in the case that the sensing data processing unit is collocated with the SeMF) in the case where an UPF is used as sensing data forwarder and where the sensing data processing unit terminates GTP-u, which comprises:

[0360] BS - UPF: a GTP-U tunnel is established between the two nodes

[0361] UPF - sensing data processing unit (collocated with SeMF): a GTP-U tunnel is established between the two nodes

[0362] The Sensing Packet Data Unit (S-PDU) layer facilitates the transmission of sensing data and may include one or more of the following information

[0363] Sensing session ID, to distinguish among different sensing sessions take place in the same RAN node ID

[0364] Reporting RAN node ID (e.g., Sensor ID)

[0365] Sensing Data o Examples of sensing data or sensing measurement information comprise one or more of information about received electromagnetic signals or electromagnetic signals to be received. Information about a received electromagnetic signal or electromagnetic signal to be received may include a received power, delay, angle of arrival, Doppler shift, and / or the like of the received or arrived electromagnetic signal. In addition, the sensing data may comprise characteristics of the transmitted electromagnetic signal on which the received electromagnetic signal is based, such as a transmitted power, an angle of departure, etc.

[0366] Descriptors of the received and reposted sensing data (e.g., time, location information)

[0367] The GTP shall encapsulate S-PDlls. It may provide encapsulation on a per S-PDll Session level. This layer can optionally include the marking associated with a QoS Flow between the two end points.

[0368] Fig. 8 presents another option of the protocol stack for the data plane for the transport of sensing data between the BS and the sensing data processing unit (e.g., in the case that the sensing data processing unit is collocated with the SeMF) in the case where an UPF is used as sensing data forwarder and where the sensing data processing unit terminates GTP-u, which comprises:

[0369] BS - UPF: a GTP-U tunnel is established between the two nodes;

[0370] UPF - SeMF: there is no GTP-U tunnel between the two nodes, but an N6 type of tunnel is established (e.g., N6-LAN, L2-TP).

[0371] In some example embodiments, an extension header type of GTP-U may indicate the usage of the tunnel for the transmission of sensing data and / or the establishment of the data plane connection between the RAN node and the sensing data processing unit (e.g., SeMF) In case of Figure 8, the S-PDU layer may correspond to an application protocol above HTTP.

[0372] It should be noted that between the UPF (which is the end point of the N3 tunnel) and the SeMF (or any other sensing data processing unit) one or more intermediate UPF nodes could be used as relays of the S-PDUs.

[0373] In the case of a direct interaction between the RAN node and the SeMF, without any intermediate node (e.g., UPF or another user plane entity), some examples of the protocol stack for the data plane for the transport of sensing data between the BS and the SeMF is presented in Fig. 9 and Fig. 10. In case of Fig. 9 and Fig. 10 the S-PDU layer may correspond to an application protocol above HTTP.

[0374] In the example embodiment 5, the sensing data reporting session can be established / modified / released by the SeMF and / or by the SMF, as in the previous example embodiments. In some example embodiments, the role and the functionalities of the SeMF presented in the various example embodiments may be undertaken by the LMF. For example, the SeMF may be at least partially (or wholly) integrated in the LMF.

[0375] Fig. 11 shows an apparatus according to an example embodiment. The apparatus may be configured to operate as a RAN node (e.g., base station, such as gNB, eNB, and so forth) or an element thereof. In some examples, the apparatus may be configured at least to perform some functionality of a RAN node. Fig. 12 shows a method according to an example embodiment. The apparatus according to Fig. 11 may perform at least the method of Fig. 12, but is not limited to this method. The method of Fig. 12 may be performed by the apparatus of Fig. 11 , but is not limited to being performed by this apparatus.

[0376] The apparatus comprises means for receiving 110, means for configuring 120, and means for associating 130. The means for receiving 110, means for configuring 120, and means for associating 130 may be a receiving means, configuring means, and associating means, respectively. The means for receiving 110, means for configuring 120, and means for associating 130 may be a receiver, configurator, and associator, respectively. The means for receiving 110, means for configuring 120, and means for associating 130 may be a receiving processor, configuring processor, and associating processor, respectively.

[0377] The means for receiving 110 receives, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between a RAN node and a sensing data processing unit (S110).

[0378] In response to receiving the request of S110, the means for configuring 120 configures the RAN node for the sensing data session (S120).

[0379] The means for associating 130 associates the sensing data session with a sensing data reporting function of the RAN node to provide the sensing data for the transmission to the sensing data processing unit (S130). The sensing data is collected by the base station. For example, the collected sensing data is obtained by a sensing procedure from characteristics of a first radio signal measured by the base station. The collected sensing data include one or more of the following: a) the sensing data is obtained by a sensing procedure from characteristics of a first radio signal measured by the RAN node; b) the sensing data is obtained by a sensing procedure from characteristics of a first radio signal measured by another RAN node, which are then provided from the other RAN node to the actual RAN node; c) the sensing data is obtained by a sensing procedure from characteristics of a first radio signal measured by a User equipment (UE), which are then provided from the UE to the RAN node;

[0380] In the options b) and c), the other RAN node and / or the UE, respectively, are configured by the SeMF to transmit the sensing data to the RAN node, as part of the sensing session establishment phase.

[0381] Fig. 13 shows an apparatus according to an example embodiment. The apparatus may be configured to operate as an SeMF or an element thereof. In some examples, the apparatus may be configured at least to perform some functionality of an SeMF. For instance, the apparatus may be configured to instantiate a virtual network function of an SeMF. Fig. 14 shows a method according to an example embodiment. The apparatus according to Fig. 13 may perform at least the method of Fig. 14, but is not limited to this method. The method of Fig. 14 may be performed by the apparatus of Fig. 13, but is not limited to being performed by this apparatus.

[0382] The apparatus comprises means for obtaining 210 and means for generating 220. The means for obtaining 210 and means for transmitting 220 may be an obtaining means and generating means, respectively. The means for obtaining 210 and means for generating 220 may be a obtainer and generating, respectively. The means for obtaining 210 and means for generating 220 may be an obtaining processor and generating processor, respectively.

[0383] The means for obtaining 210 obtains addressing information of a sensing data processing unit for a sensing data session (S210). The sensing data session is for receiving sensing data from a RAN node. The means for generating 220 generates and transmits a first request configured to request the RAN node to set up the sensing data session (S220).

[0384] Fig. 15 shows an apparatus according to an example embodiment. The apparatus may be configured to operate as an SMF or an element thereof. In some examples, the apparatus may be configured at least to perform some functionality of an SMF. For instance, the apparatus may be configured to instantiate a virtual network function of an SMF. Fig. 16 shows a method according to an example embodiment. The apparatus according to Fig. 15 may at least perform the method of Fig. 16, but is not limited to this method. The method of Fig. 16 may be performed by the apparatus of Fig. 15, but is not limited to being performed by this apparatus. The apparatus comprises first means for receiving 310, second means for transmitting 320, and means for transmitting 330. The means for receiving 310, first means for transmitting 320, and second means for transmitting 330 may be a receiving means, first transmitting means, and second transmitting means, respectively. The means for receiving 310, first means for transmitting 320, and second means for transmitting 330 may be a receiver, first transmitter, and second transmitter, respectively. The means for receiving 310, first means for transmitting 320, and second means for transmitting 330 may be a first receiving processor, transmitting processor, and second transmitting processor, respectively.

[0385] The means for receiving 310 receives an original request (S310). The original request requests a sensing data forwarding function and a RAN node to set up a sensing data session for transmitting sensing data from the RAN node to the sensing data forwarding function in the sensing data session.

[0386] Upon receipt of the original request in S310, the first means for transmitting 320 transmits a first request configured to request the sensing data forwarding function to set up the sensing data session (S320), and the second means for transmitting 330 transmits a second request configured to request the RAN node to set up the sensing data session (S330).

[0387] Fig. 17 shows an apparatus according to an example embodiment. The apparatus may be configured to operate as a sensing data processing function or an element thereof. In some examples, the apparatus may be configured at least to perform some functionality of a sensing data processing function. For instance, the apparatus may be configured to instantiate a virtual network function of a sensing data processing function. Fig. 18 shows a method according to an example embodiment. The apparatus according to Fig. 17 may perform at least the method of Fig. 18, but is not limited to this method. The method of Fig. 18 may be performed by the apparatus of Fig. 17, but is not limited to being performed by this apparatus.

[0388] The apparatus comprises means for receiving 410, means for configuring 420, and means for causing 430. The means for receiving 410, means for configuring 420, and means for causing 430 may be a receiving means, configuring means, and causing means, respectively. The means for receiving 410, means for configuring 420, and means for causing 430 may be a receiver, configurator, and causer, respectively. The means for receiving 410, means for configuring 420, and means for causing 430 may be a receiving processor, configuring processor, and causing processor, respectively.

[0389] The means for receiving 410 receives, at a sensing data processing unit, from a sensing data management function or a session management function, a request to set up a sensing data session for receiving sensing data for a session (S410). In response to receiving the request of S410, the means for configuring 420 configures the sensing data processing unit for the sensing data session (S420). The means for causing 430 causes the sensing data processing unit to process the sensing data received in the sensing data session (S430).

[0390] Fig. 19 shows an apparatus according to an example embodiment. The apparatus may be configured to operate as a sensing data forwarding function or an element thereof. In some examples, the apparatus may be configured at least to perform some functionality of a sensing data forwarding function. For instance, the apparatus may be configured to instantiate a virtual network function of a sensing data forwarding function. Fig. 20 shows a method according to an example embodiment. The apparatus according to Fig. 19 may perform at least the method of Fig. 20, but is not limited to this method. The method of Fig. 20 may be performed by the apparatus of Fig. 19, but is not limited to being performed by this apparatus.

[0391] The apparatus comprises means for receiving 510, means for configuring 520, and means for causing 530. The means for receiving 510, means for configuring 520, and means for causing 530 may be a receiving means, configuring means, and causing means, respectively. The means for receiving 510, means for configuring 520, and means for causing 530 may be a receiver, configurator, and causer, respectively. The means for receiving 510, means for configuring 520, and means for causing 530 may be a receiving processor, configuring processor, and causing processor, respectively.

[0392] The means for receiving 510 receives, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between a sensing data forwarding function and a RAN node (S510). In response to receiving the request of S510, the means for configuring 520 configures the sensing data forwarding function for the sensing data session (S520). The means for causing 530 causes the sensing data forwarding function to forward sensing data received in the sensing data session to a sensing data processing unit (S530).

[0393] Fig. 21 shows an apparatus according to an example embodiment. The apparatus comprises at least one processor 810, at least one memory 820 storing instructions that, when executed by the at least one processor 810, cause the apparatus at least to perform the method according to at least one of the following figures and related description: Fig. 12, or Fig. 14, or Fig. 16, or Fig. 18, or Fig. 20.

[0394] Some example embodiments are explained with respect to 5G (NR). However, other example embodiments may be employed in other 3GPP generations, such as 4G, 6G, 7G, etc., in other wireless or wired communication devices, and in other systems employing reporting of sensing data.

[0395] A UE is an example of a terminal. Other examples are MTC devices. Each of the terminals may be implemented as a smartphone, a mobile phone, a drone, a vehicle, a robot, a laptop, a sensor device, and so forth. Typical terminals are cellular communication devices for communicating in a cellular network (such as a 3GPP network), but this is not mandatory.

[0396] One piece of information may be transmitted in one or plural messages from one entity to another entity. Each of these messages may comprise further (e.g., different) pieces of information.

[0397] Names of network elements, network functions, protocols, and methods are based on current standards, or are current proposals. These names are not limiting. For example, in other versions or other technologies, the names of these network elements and / or network functions and / or protocols and / or methods may be different, as long as they provide a corresponding functionality. The same applies correspondingly to the terminal.

[0398] If not otherwise stated or otherwise made clear from the context, the statement that two entities are different means that they perform different functions. It does not necessarily mean that they are based on different hardware. That is, each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described herein may be based on different software, or some or all of the entities may be based on the same software. Each of the entities described herein may be deployed in the cloud.

[0399] According to the above description, it should thus be apparent that example embodiments provide, for example, a RAN node (such as a base station) or an element thereof (which may or may not be actually integrated in the RAN node), an apparatus embodying the same, a method for controlling and / or operating the same, and computer program(s) controlling and / or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s). According to the above description, it should thus be apparent that example embodiments provide, for example, a management function (such as a SeMF or a SMF) or an element thereof (which may or may not be actually integrated in the management function), an apparatus embodying the same, a method for controlling and / or operating the same, and computer program(s) controlling and / or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s). According to the above description, it should thus be apparent that example embodiments provide, for example, a processing function (such as a sensing data processing unit) or an element thereof (which may or may not be actually integrated in the processing function), an apparatus embodying the same, a method for controlling and / or operating the same, and computer program(s) controlling and / or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s).

[0400] Implementations of any of the above described blocks, apparatuses, systems, techniques or methods include, as non-limiting and illustrative examples, implementations as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. Each of the entities described in the description may be embodied at least in part (or entirely) in the cloud.

[0401] Moreover, it is to be understood that the apparatus is configured to perform the corresponding method, although in some cases only the apparatus or only the method are described.

[0402] In general, the various example embodiments may be implemented in hardware or special purpose circuitry, software, logic or any combination thereof. Some example embodiments of the disclosure may be implemented in hardware, while other example embodiments may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various example embodiments of the disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as nonlimiting and illustrative examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0403] As used herein, the term “circuitry” may refer to one or more or all of the following:

[0404] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and

[0405] (b) combinations of hardware circuits and software, such as (as applicable):

[0406] (i) a combination of analog and / or digital hardware circuit(s) with software / firmware; and / or

[0407] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0408] This definition of “circuitry” applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term “circuitry” also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term “circuitry” also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0409] The various example embodiments of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and / or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out any of the example embodiments described herein. The one or more computerexecutable components may be at least one software code or portions of it.

[0410] Further in this regard it should be noted that any blocks of the logic flow as in the Figs, may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a “non-transitory” media.

[0411] The term “non-transitory,” as used herein, is a limitation of the medium itself (e.g., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0412] The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.

[0413] Various example embodiments of the disclosure may be practiced in various components, such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0414] The scope of protection sought for various example embodiments of the disclosure is set out by the independent claims. The example embodiments and features thereof, if any, described in this disclosure that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various example embodiments of the disclosure.

[0415] It is to be understood that what is described above is what is considered the various example embodiments of the disclosure. However, it should be noted that the description of any of the various example embodiments of the disclosure is provided by way of non-limiting and illustrative example only, and that various modifications may be made without departing from the scope of the disclosure.

[0416] As used herein, the terms “first X” and “second X” include the options that “first X” is the same as “second X” and that “first X” is different from “second X”, unless otherwise specified. These terms are merely used to distinguish one element from another without indicating a temporal relationship, unless otherwise apparent from the disclosure.

[0417] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements. Similarly, the expression “and / or” includes any and all combinations of two or more of the listed terms, including any one of the elements, any two or more of the elements, and all of the elements.

[0418] As used herein, the term "or" refers to a non-exclusive “or” unless otherwise indicated (e.g., use of “or else” or “or in the alternative”). As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included. Analogously, performing a step or functionality “based on A” does not indicate that the step or functionality is performed solely based on “A” as one or more additional conditions may be included.

Claims

Claims:

1. An apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between a radio access network (RAN) node and a sensing data processing unit; configuring the RAN node for the sensing data session in response to receiving the request; associating the sensing data session with a sensing data reporting function of the RAN node to provide the sensing data for the transmission to the sensing data processing unit, wherein the RAN node is configured to collect the sensing data.

2. The apparatus according to claim 1 , wherein at least one of the following: the request does not comprise any identifier of a terminal; or the request does not comprise any context information of a terminal.

3. The apparatus according to any of claims 1 and 2, wherein the request to set up the sensing data session comprises at least one of the following:- addressing information of the sensing data processing unit;- information on the sensing data to be transmitted in the sensing data session;- an identifier of the sensing data session; or- QoS information for the sensing data session.

4. The apparatus according to claim 3, wherein the addressing information of the sensing data processing unit comprises at least one of the following:- a fully qualified domain name (FQDN) of the sensing data processing unit;- one or more combinations of IP addresses and ports of the sensing data processing unit for the sensing data session;- a fully qualified GTP-u tunnel identifier for the sensing data session; or- a Uniform Resource Locator (URL) for the sensing data session on the sensing data processing unit.

5. The apparatus according to claim 4, wherein the fully qualified tunnel identifier for the sensing data session corresponds to one of the following:- a fully qualified tunnel identifier configured to identify resources at the sensing data processing unit; or- a fully qualified tunnel identifier configured to identify resources at a sensing data forwarding function for forwarding traffic between the RAN node and the sensing data processing unit.

6. The apparatus according to any of claims 3 to 5, wherein the information on the sensing data to be transmitted in the sensing data session comprises at least one of the following:- an identifier of a sensing session for configuring and / or controlling the RAN node to obtain the sensing data;- information on a trigger radio signal sent to trigger sensing for obtaining the sensing data;- information on the first radio signal measured by the RAN node to obtain the sensing data;- information on at least one radio parameter of the first radio signal and / or the trigger radio signal, such as time and / or frequency of the respective radio signal; or- information on the periodicity and / or duration to send the trigger radio signal and / or to measure the first radio signal.

7. The apparatus according to any of claims 1 to 6, wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform: causing the RAN node to generate the sensing data.

8. The apparatus according to claim 7, wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform: receiving the first radio signal on at least a radio resource assigned to a sensing procedure; and generating the sensing data based on the first radio signal received on the at least one resource assigned to the sensing procedure.

9. The apparatus according to claim 7, wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform, based the received information on which radio signal to measure: the generating the sensing data without demodulating the first radio signal, or the generating the sensing data after demodulating the first radio signal.

10. The apparatus according to any of claims 1 to 9, wherein the sensing data do not comprise any user data received from a terminal in communication with the RAN node.11 . The apparatus according to any of claims 1 to 10, wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform: causing the RAN node to transmit the sensing data in the sensing data session.

12. The apparatus according to claim 11 , wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform: transmitting the sensing data in packets, wherein a header of each of the packets indicates that the respective packet includes at least a portion of the sensing data for the sensing procedure.

13. The apparatus according to any of claims 1 to 12, wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform responding to the request to set up the sensing data session with addressing information allocated to the sensing data session.

14. The apparatus according to claim 13, wherein the response to the request to set up the sensing data session comprises at least one of: an FQDN of the sensing data reporting function; one or more combinations of IP addresses and ports of the sensing data reporting function for the sensing data session; a fully qualified GTP-u Tunnel identifier for the sensing data session at the sensing data reporting function; or a Uniform Resource Locator (URL) for the sensing data session on the RAN node.

15. The apparatus according to any of claims 13 to 14, wherein the response to the request to set up the sensing data session does not comprise a fully qualified GTP-u tunnel identifier for the sensing data session at the sensing data reporting function in the access network when the request to set up the sensing data session does not comprise a fully qualified GTP-u tunnel identifier.

16. The apparatus according to any of claims 1 to 15, wherein the collected sensing data is obtained by a sensing procedure from characteristics of a first radio signal measured by the RAN node.

17. An apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform:obtaining addressing information of a sensing data processing unit for a sensing data session for receiving sensing data from a RAN node; and generating and transmitting a first request configured to request the RAN node to set up the sensing data session.

18. The apparatus according to claim 17, wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform: generating and transmitting a second request configured to request the sensing data processing unit to set up the sensing data session and to provide, in response, the addressing information for the sensing data session.

19. The apparatus according to any of claim 17 to 18, wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform: generating and transmitting a request configured to request a sensing data forwarding function to set up a sensing data session for transmitting the sensing data between the RAN node and the sensing data processing unit.

20. The apparatus according to any of claims 17 to 19, wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform: selecting one or more RAN nodes; and transmitting the first request directly to each of the one or more RAN nodes.

21. The apparatus according to any of claims 17 to 20, wherein at least one of the following: none of the first request and, if dependent on claim 18, the second request comprises any identifier of a terminal; or none of the first request and, if dependent on claim 18, the second request comprises any context information of a terminal.

22. The apparatus according to any of claims 17 to 21 , wherein the instructions, when executed by the one or more processors, further cause the apparatus at least to perform: the obtaining the addressing information at the sensing data processing unit for the sensing data session is by receiving the addressing information from the sensing data processing unit.

23. An apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform:receiving an original request configured to request a sensing data forwarding function and a RAN node to set up a sensing data session for transmitting sensing data from the RAN node to the sensing data forwarding function in the sensing data session; transmitting a first request configured to request the sensing data forwarding function to set up the sensing data session; and transmitting a second request configured to request the RAN node to set up the sensing data session.

24. An apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform: receiving, at a sensing data processing unit, from a sensing data management function or a session management function, a request to set up a sensing data session for receiving sensing data for a session; configuring the sensing data processing unit for the sensing data session in response to receiving the request; and causing the sensing data processing unit to process the sensing data received in the sensing data session.

25. An apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between a sensing data forwarding function and a RAN node; configuring the sensing data forwarding function for the sensing data session in response to receiving the request; and causing the sensing data forwarding function to forward sensing data received in the sensing data session to a sensing data processing unit.

26. A method comprising: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between the RAN node and a sensing data processing unit; configuring the RAN node for the sensing data session in response to receiving the request; andassociating the sensing data session with a sensing data reporting function of the RAN node to provide the sensing data for the transmission to the sensing data processing unit, wherein the sensing data is collected by the RAN node.

27. A method comprising: obtaining addressing information of a sensing data processing unit for a sensing data session for receiving sensing data from a RAN node; and generating and transmitting a first request configured to request the RAN node to set up the sensing data session.

28. A method comprising: receiving an original request configured to request a sensing data forwarding function and a RAN node to set up a sensing data session for transmitting sensing data from the RAN node to the sensing data forwarding function in the sensing data session; transmitting a first request configured to request the sensing data forwarding function to set up the sensing data session; and transmitting a second request configured to request the RAN node to set up the sensing data session.

29. A method comprising: receiving, at a sensing data processing unit, from a sensing data management function or a session management function, a request to set up a sensing data session for receiving sensing data for a session; configuring the sensing data processing unit for the sensing data session in response to receiving the request; and causing the sensing data processing unit to process the sensing data received in the sensing data session.

30. A method comprising: receiving, from a sensing data management function or a session management function, a request to set up a sensing data session for exchanging sensing data between a sensing data forwarding function and a RAN node; configuring the sensing data forwarding function for the sensing data session in response to receiving the request; and causing the sensing data forwarding function to forward sensing data received in the sensing data session to a sensing data processing unit.

31. A computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out the method according to any of claims 26 to 30.

Images