Systems and methods for configuring sensing resources based on target sensing quality of service information

Abstract

A method (800) by a sensing unit (16, 412) performing a sensing operation includes receiving (802) a sensing request The SU receives (804) Quality of Service, QoS, data based on the sensing request. The SU receives (806), from a network function performing a sensing function, one or more configured sensing resources for obtaining a sensing result to satisfy the sensing request. Based on the one or more configured sensing resources, the SU performs (808) a sensing procedure in a sensing session to obtain the sensing result. The SU determines (810) whether the sensing result satisfies at least one criteria and transmits (812) the sensing result to a network.

Description

[0001] SYSTEMS AND METHODS FOR CONFIGURING SENSING RESOURCES BASED ON TARGET SENSING QUALITY OF SERVICE INFORMATION

[0002] TECHNICAL FIELD

[0003] The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for configuring sensing resources based on target sensing Quality of Service (QoS) information.

[0004] BACKGROUND

[0005] Recently, the system architectures (SAI and SA2) groups of the 3rdGeneration Partnership Project (3GPP) have defined study items to identify use cases and architectural enhancements that will enable integrated sensing and communication (ISAC) in cellular networks. The term ISAC corresponds to the internal term joint communication and sensing (JCAS), used for the same technology.

[0006] Within cellular networks, sensing can be performed in a monostatic setting, in which the transmitter and the receiver sensing antennas are located in the same node, and in a multistatic setting, in which the transmitter and the receiver sensing antennas are located in different nodes. FIGURES 1A-1D illustrate different radar settings that can be deployed using NR base station(s) (BS(s)), denoted by gNodeB (gNB), and user equipment(s) (UE(s)). As shown in FIGURES 1A-1D, TX-s and RX-s denote the sensing transmitter node and the sensing receiver node, respectively. Specifically, FIGURE 1A illustrates a base station (gNB)-only based monostatic sensing. FIGURE IB illustrates bi-static settings with base stations (gNBs) as both transmitter and receiver. FIGURE 1C illustrates bi-static settings with UE as a transmitter and a base station as a receiver. FIGURE ID illustrates bi-static sensing with a base station (gNB) as a transmitter and a UE as a receiver. As shown in FIGURES 1A-1D, TX-s and RX-s denote the sensing transmitter node and the sensing receiver node, respectively. The goal is to detect and localize a target(s) which is / are, in general, is a non-connected object (such as a pedestrian, an animal, etc.). Targets can be also connected UEs and in this case sensing is used to improve communication-based positioning of such UEs.

[0007] Next Generation-Radio Access Network (NG-RAN) Architecture FIGURE 2 illustrates the NG-RAN architecture, which consists of a set of gNBs connected to the 5thGeneration Core (5GC) through the NG interface. See, 3GPP TS 38.401, V 17.6.0.

[0008] A disaggregated gNB may consist of a gNB -Centralized Unit (gNB-CU) and one or more gNB-Distributed Unit(s) (gNB-DU(s)). A gNB-CU and a gNB-DU is connected via Fl interface, as shown in FIGURE2. This interface is responsible for possible information and control signaling from the Packet Data Convergence Protocol (PDCP) entity located in Centralized Unit (CU) and Radio Eink Control (RLC) entity located in Distributed Unit (DU).

[0009] Current studies evaluate how to integrate the sensing functions into a NG-RAN architecture and beyond for 6thGeneration (6G) RAN. Specifically, ISAC may introduce new entities and network functions that can be listed in the following:

[0010] 1) Sensing unit (SU) :

[0011] SU or sensing radio unit (SRU) is a logical entity, that can be either a standalone entity in the network, integrated / co-located / co-sited with a UE or a RAN node, capable of at least one of:

[0012] Radio signal transmission used for sensing,

[0013] Radio signal reception used for sensing, Radio measurement used for sensing, Radio antennas used for sensing.

[0014] SUs can have their own internal or external antenna or can share antenna(s) with other radio nodes (UE or RAN node) for JCAS. Multiple SUs can be involved in a sensing session. The relevant SUs need to be selected, configured, etc. by the controlling entity.

[0015] 2) Sensing Management function (SeMF):

[0016] SeMF is a function controlling or managing a sensing session, entities involved in a sensing session, etc. SeMF can be a sensing server that sends the request to RAN to trigger a sensing session, sensing measurements, etc. The sensing session is configured based at least on the sensing task, sensing target information (e.g., object type, weather condition, etc.) and / or sensing area information (e.g., forest, indoor factory, house, area size, etc.). Sensing session is characterized by a set of SUs and aims enabling, configuring, and / or collecting sensing measurements from different SUs, which may include any of RF and non-RF sensors (e.g. from camera sensors, motion sensors, heat sensors, etc.). Example measurements: raw samples, radio measurements, timing measurements, velocity, temperature, sensing event indication such as weather change or motion pattern change, etc. SeMF may or may not comprise Sensing Processing Function (SPF). SeMF can be implemented in one node or distributed over multiple nodes.

[0017] 3) Sensing Processing Function (SPF) :

[0018] SPF is the function that receives the sensing measurements from the SUs and processes sensing measurements to obtain one or more sensing results. The SPF can be a separate entity in the network. SPF can be implemented in one node or distributed over multiple nodes. SPF may be implemented together with or as a part of SeMF. SPF may send the processed sensing results to another function or node, to the SeMF, e.g., to make the results available to the sensing request originator.

[0019] FIGURE 3 illustrates an example how the SeMF entity and SPF can be incorporated into the 3GPP 5G Positioning architecture, which comprises positioning functions (e.g., NR Location Management Function (LMF), Long Term Evolution- Evolved-Serving Mobile Location Centre (LTE-E-SMLC)) and user-plane positioning function (e.g., SUPL (secure user-plane location) Location platform (SLP). SeMF and / or SPF may also interact with a positioning / location function such as, for example LMF. It is also understood that the sensing functions can also be integrated in another radio access technology (RAT), e.g., 6G RAT, comprising the relevant RAT nodes and corresponding interfaces.

[0020] There currently exist certain challenge(s). For example, there is currently no ISAC standardized methods to make network aware of the sensing quality metrics to perform resource configuration to meet sensing demands.

[0021] SUMMARY

[0022] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, according to certain embodiments, methods are provided to enable QoS control for sensing based on a sensing request used to convey the target QoS data for sensing. As another example, according to certain embodiments, methods are provided to configure sensing resources to meet the target QoS for sensing in a radio communications network with sensing support.

[0023] According to certain, embodiments, a method by a sensing unit performing a sensing operation includes receiving a sensing request and receiving QoS data based on the sensing request. The sensing unit receives, from a network function performing a sensing function, one or more configured sensing resources for obtaining a sensing result to satisfy the sensing request. Based on the one or more configured sensing resources, the sensing unit performs a sensing procedure in a sensing session to obtain the sensing result. The sensing unit determines whether the sensing result satisfies at least one criteria and transmits the sensing result to a network.

[0024] According to certain embodiments, a sensing unit for performing a sensing operation is configured to receive a sensing request and receiving QoS data based on the sensing request. The sensing unit is configured to receive, from a network function performing a sensing function, one or more configured sensing resources for obtaining a sensing result to satisfy the sensing request. Based on the one or more configured sensing resources, the sensing unit is configured to perform a sensing procedure in a sensing session to obtain the sensing result. The sensing unit is configured to determine whether the sensing result satisfies at least one criteria and transmit the sensing result to a network.

[0025] According to certain embodiments, a method by a network node operating as a sensing function for configuring sensing resources includes receiving a sensing request and receiving first QoS data based on the sensing request. Based on the first QoS data, the network node determines one or more sensing resources for use by one or more sensing units for obtaining a sensing result to satisfy the sensing request. The network node transmits information indicating the one or more sensing resources for use by the one or more sensing units.

[0026] According to certain embodiments, a network node operating as a sensing function for configuring sensing resources is configured to receive a sensing request and receiving first QoS data based on the sensing request. Based on the first QoS data, the network node is configured to determine one or more sensing resources for use by one or more sensing units for obtaining a sensing result to satisfy the sensing request. The network node is configured to transmit information indicating the one or more sensing resources for use by the one or more sensing units. Certain embodiments may provide one or more of the following technical advantage(s). Possibility to control QoS for sensing, based on a sensing request. Allow sensing to improve communication for the UE.

[0027] BRIEF DESCRIPTION OF THE DRAWINGS

[0028] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0029] FIGURES 1A-1D illustrate different radar settings that can be deployed using NR BS(s) and UE(s);

[0030] FIGURE 2 illustrates the NG-RAN architecture;

[0031] FIGURE 3 illustrates an example how the SeMF entity and SPF can be incorporated into the 3GPP 5G Positioning architecture;

[0032] FIGURE 4 illustrates an example system and signaling for enabling QoS control for sensing based on a sensing request used to convey the target QoS data for sensing and enable configuration of sensing resources to meet the QoS for sensing, according to certain embodiments;

[0033] FIGURE 5 illustrates a method for obtaining and using QoSl, according to certain embodiments;

[0034] FIGURES 6A-6B illustrate an example message flow, comprising configuration of one or more time windows, according to certain embodiments

[0035] FIGURE 7 illustrates an example signaling diagram for the configuration of sensing processing windows to meet target sensing QoS, according to certain embodiments;

[0036] FIGURE 8 illustrates an example communication system, according to certain embodiments;

[0037] FIGURE 9 illustrates an example UE, according to certain embodiments;

[0038] FIGURE 10 illustrates an example network node, according to certain embodiments;

[0039] FIGURE 11 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;

[0040] FIGURE 12 illustrates a method by a SU performing a sensing operation, according to certain embodiments; and

[0041] FIGURE 13 illustrates a method performed by a network node operating as a sensing function for configuring sensing resources, according to certain embodiments. DETAILED DESCRIPTION

[0042] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0043] The term sensing used herein can comprise sensing based on JCAS or ISAC, e.g., a 3GPP -based 6G communications network.

[0044] The term sensing target can comprise an object, event, a state or condition for which a sensing result needs to be obtained or which is involved in a sensing task. An object can be a passive object, an object not connected to the communications network in which sensing is performed, an object within a sensing area, a background object within a sensing area, an object with no radio transmit or receive capability, or an object whose radio transmit or receive capability is not exploited for obtaining the sensing result. Examples of passive objects: a person not carrying a connected UE, a non-connected vehicle, an animal, etc. Examples of states or conditions are a health condition, a weather condition, a particular condition something or someone is in at a specific time. Examples of events: a gesture, a movement, appearance / disappearance / changing of a sensing target, change of a form or shape. To distinguish an event, a significant difference between two states or conditions can be defined, e.g., a movement occurs when the object location changes by more than X. The difference can be controlled by the QoS data, e.g., resolution or granularity. In some cases, a sensing target can comprise a connected object such as a device or UE for which a sensing task is performed to serve a sensing purpose.

[0045] Sensing processing related capability and availability (SPCA) can comprise any one or more of the following characteristics indicative of the ability to obtain or process sensing data: processing power, number of processors or processing units, memory, storage space, processing speed, capacity, ability to obtain results for a specific type of sensing tasks, support of a specific sensing method or sensing measurements, support of a specific measurement reporting configuration or format, a specific measurement reporting method (e.g., absolute values, differential reporting with only delta reported when delta>epsilon, out-of-sequence measurement reporting, log or merged measurement reports reporting, adaptive message size due to memory characteristics, etc. - all these different methods may require a specific way of handling or pre-processing at SPF and not all SPFs may be able to do this), a set of processing resources, load or resource utilization level, level of processing / related resource availability or occupancy, processing resource availability currently or in time, supported processing configuration(s), etc. The SPCA can comprise any one or combination of:

[0046] • the maximum static capability (e.g., due to hardware limitations),

[0047] • configured or reserved capability (e.g., depending on one or more configurable parameters),

[0048] • currently available or achievable capability (e.g., based on the current resource utilization),

[0049] • expected capability (e.g., based on predicted resource availability at a specific point of time point and / or during a time interval such as in 10 minutes).

[0050] The SPCA information can be SPF-specific or can comprise the SPCA information about two or more SPFs, including a list of SPFs. The SPCA information can be used to decide on whether and how the sensing data can be processed, to schedule processing resources for sensing, etc.

[0051] Sensing data herein can comprise any of: radio measurement for sensing purpose, processed or unprocessed result of receiving radio signal(s) for sensing purpose, including raw sample data, a sensing result, a result of measurement samples or measurement results filtering or processing for sensing purpose, encoded sensing result or indication, sensing a data / measurement or result of processing thereof for sensing purpose or task, an event-triggered report for sensing purpose, an aperiodic or periodic report for sensing purpose. Sensing data can further comprise a quality metric or statistical character! stic(s) associated with the sensing measurement or sensing result, e.g., uncertainty level, standard deviation, variance, average, number of samples, minimum value, maximum value, a range between the minimum and maximum, a delay, measurement time period, accuracy, reliability, confidence level, dispersion, an error, a delay error, an estimation error, CDF, PDF, median, Xth percentile, etc.

[0052] Sensing purpose can comprise determining, obtaining, or monitoring in time one or more characteristics of a sensing target and / or sensing area, e.g.: presence / absence of object(s) or condition(s), speed, velocity, movement pattern, a characteristic or a recognized feature of a sensing target object or obstacle within the sensing area based on sensing measurements, environment characterization based on sensing measurements, a map based on sensing measurements, absolute or relative 2D or 3D location, etc. Sensing target conditions can comprise weather conditions, health conditions, etc.

[0053] The term base station (BS) herein can comprise any of: a radio network node, a RAN node, a radio base station, Transmission Reception Point (TRP), Transmission Point (TP), Reception Point (RP), Remote Radio Unit (RRU), gNB, gNB-DU, gNB-CU, multi-RAT base station operation two or more RATs, sensing unit (SU), etc.

[0054] The terms a processor or a set of tightly connected processing resources, DU, gNB-DU, BS-DU, RRU, TRP, TP, RU, BS-DU, BS-RU, or BS herein can be used interchangeably in some embodiments.

[0055] The term sensing unit (SU) or sensing radio unit (SRU) can comprise or can be comprised in a radio node or device (e.g., UE or radio network node) capable of at least one of: transmitting radio signals for sensing, receiving radio signals for sensing, performing sensing measurements, etc. SU may be equipped with internal or connected to one or more external antennas or antenna panels directly or via one or more external devices (e.g., rx amplifier, Eow Noise Amplifier, ENA, directional coupler, antenna sharing combiner or coupler, rx filter, tx filter, tx / rx filter, etc.) or may share antennas with other nodes (e.g., UE, BS, or gNB). The sharing may be, e.g., via antenna sharing combiner or coupler. SU may be a standalone node or device, may be integrated into or may be comprised in a radio node (e.g.,

[0056] UE, BS, or another radio network node), may be co-located with another radio node (and may even use the other radio node’s signal, without impacting the radio node), or may be co-sited with another radio node sharing the radio facilities at the same site (e.g., the sharing can mean splitting the radio signal, which may also impact the other radio node), or may be co-sited with another radio node. Examples of sensing units include: a standalone sensing unit, UE, TRP,

[0057] TP, RP, a functional block or unit for sensing, a BS, a gNB, and a radio network node.

[0058] SeMF can be as described above.

[0059] Sensing controlling function (SCF) can comprise a UE, a RAN node, or a core network node. In some examples, SCF and SeMF can be used interchangeably.

[0060] SPF can be as described above.

[0061] In some examples, SCF can comprise SeMF or can be used interchangeably with SeMF. The term Radio Access Network (RAN) can comprise, e.g., 5G RAN, 6G RAN, etc.

[0062] The term Radio Access Technology (RAT) can comprise, e.g., 5G RAT, 6G RAT, etc.

[0063] The terms Joint Communication And Sensing (JCAS) and Integrated Sensing And Communication (ISAC) can be used herein interchangeably.

[0064] As described above, there is currently no ISAC standardized methods to make network aware of the sensing quality metrics to perform resource configuration to meet sensing demands. However, there is a need to determine the content of the target QoS data and configure or adjust the sensing resources, based on a sensing request conveying the target QoS data, to meet sensing demands. Accordingly, systems and methods are described herein for one or more of:

[0065] • enabling QoS control for sensing, based on a sensing request used to convey the target QoS data for sensing;

[0066] • configuring target QoS for sensing in a sensing controlling function (SCF);

[0067] • configuring sensing resources to meet the target QoS for sensing in a radio communications network with sensing support;

[0068] • controlling radio or processing resource sharing between sensing and communication during a sensing window that is configured by SCF (in e.g., network node), based on application or sensing client demands and the sensing target QoS;

[0069] • obtaining target QoS data, based on the sensing request, including methods of mapping the Service-Level Agreement and the sensing type determined based on categorizing the sensing request into sensing type (e.g., Monitoring, Tracking, “around me”, one-shot, periodic / streaming).

[0070] FIGURE 4 illustrates an example system 10 and signaling for enabling QoS control for sensing based on a sensing request used to convey the target QoS data for sensing and enable configuration of sensing resources to meet the QoS for sensing, according to certain embodiments. In FIGURE 4, a control command can comprise configuration or a command controlling a sensing-related behavior (e.g., related to transmission, measurement, result reporting, processing, etc.). QoSl is the first target QoS, QoS2 is the second target QoS. The radio communications network with network support can comprise, e.g., an enhanced 5G network, 6G network, or other network implementing the methods described herein.

[0071] As illustrated, the example methods can include one or more of the following steps:

[0072] • Step 1: A sensing controlling function (SCF) 12 receives a sensing request 14 and obtains a first target QoS data (comprising at least one QoS parameter or Key Performance Indicator (KPI) described herein) associated with the sensing request. The SCF 12 can comprise a UE, a RAN node, or a core network node. In some examples, SCF 12 can comprise SeMF.

[0073] The first target QoS data (QoSl) can be comprised in or determined based on the received sensing request. The QoSl can be transmitted to the SCF at 14 and further used in the SCF for its actions / decisions (in Step 2 described below) or can be provided to another node (e.g., Sensing Unit (SU) 16, SPF 18, positioning node 20, or LMF) to control its actions / decisions in Step 2.

[0074] The obtaining can comprise, for example, extracting from the sensing request, determining based on one or more parameters from the sensing request, by mapping of the sensing client type or application type to a QoSl, by categorizing into sensing type and Service-Level Agreement (SLA) which are then mapped to a QoSl data (see FIGURE 5 described below).

[0075] • Step 2: The SCF 12 or the node receiving the QoS 1 data from the SCF 12 (e.g., SPF 18, SU 16, and / or positioning node 20) is using the obtained QoSl for at least one of the below, to enable obtaining one or more sensing results to meet the sensing request:

[0076] 1) Selecting a sensing method, based on the QoS 1.

[0077] 2) Configuring SUs 16, based on the QoSl (via signaling 22 and 24), for at least one of: transmitting or receiving radio signals for sensing, which can also comprise selecting SUs 16, configuring a first list of time windows for transmit / receive / measurements / measurement reporting operations for sensing, configuring dedicated or shared (with communication and / or positioning) resources or resource pools for the transmit / receive / measurements / measurement reporting operations for sensing. An SU can comprise a UE or a RAN node.

[0078] 3) Configuring sensing processing, based on the QoSl, e.g., selecting or configuring one or more SPF(s) 18 (via signaling 26 and 28), and / or configuring a second list of time windows for sensing processing operations, etc.

[0079] 4) Determining a second target QoS data (QoS2), based on QoSl, and using the QoS2 for obtaining or requesting (e.g., via signaling 30 and 32) from a location controlling function, positioning node, or LMF) location information to enable obtaining of one or more sensing results to meet the sensing request. The QoS2 can be further used to select a positioning method, configure at least one positioning reference signal transmission or reception, or for configuring one or more positioning measurements.

[0080] 5) Assessing whether the requirements (e.g., criteria) imposed by the target QoS data are met (for an obtained result) or can be met (from configuration / result feasibility point of view) and performing actions based on the assessment result. The assessing can further comprise sending a response to the sensing request, wherein the response can comprise a result of assessment. The assessment can be done, e.g., by SCF 12, SPF 18, SU 16, or positioning node 20 (based on QoSl or QoS2).

[0081] • Responding to the sender node that sent the sensing request in step 1 with a confirmation or rejection message (via signaling 34) that indicates the successful / unsuccessful controlling operation, based on the target QoS data (e.g., configuring the sensing units, SPFs 18, sensing resources, the time windows for sensing reporting and processing, etc.). The success or no success can depend on whether it is possible or not to meet the requested QoS, e.g., not all necessary SUs 16, SPFs 18, resources, or configurations are available, etc.

[0082] 6) Sending an update message to the sender node, in case the windows (e.g., at least one window from the first or the second list of time windows) for sensing operation and / or windows for sensing processing to meet the target sensing QoS have been modified. This can be, for example, due to varying radio conditions and radio link adaptation. In one case, sending a notification message that the target QoS for sensing can no longer bet met for this sensing target or by this SU 16. The update or notification message can be sent, e.g., to SCF 12 by SPF 18, SU 16, or positioning node 20.

[0083] According to certain embodiments, target QoS data or target QoS can comprise one or more of the required, requested, or expected quality characteristics of a sensing result. A first target QoS data can comprise, for example, at least one of:

[0084] • Sensing QoS class, which can comprise, for example, an associated set of QoS parameters or characteristics, a degree of flexibility in meeting these characteristics (e.g., best effort or strictly met), pre-configured or pre-defined actions or behaviors in relation to sensing configuration or to methods for obtaining, handling or reporting the sensing data or sensing results associated with a given sensing QoS class. o In one example, different Sensing QoS classes can differ in levels of a parameters and / or in sets of parameters. For example, a first sensing QoS class comprises {min horizontal accuracy XI, max delay Y2, confidence level 95%, min refreshing rate Zl, min processing rate Pl, ... }, a second sensing QoS class comprises {min sensitivity level S2, min horizontal accuracy X2, min vertical accuracy XX2, min velocity accuracy XXX2, max delay Y2, confidence level 98%, min refreshing rate Z2, min processing rate P2, . . . }, ... o A sensing QoS class can comprise a set of any one or a combination of the QoS parameters described below. o A sensing QoS class can be pre-defined or pre-configured for a given one or a group / type of applications or sensing clients which can request sensing.

[0085] • Reliability or validity criteria of a sensing result, which may include, for example, minimum number of measurements or measurement samples to be used for obtaining a sensing result.

[0086] • Confidence level or confidence interval, which may include, for example, a level of significance of a sensing result, acceptable probability of the sensing result being wrong / correct or outside / within a confidence interval or a range, a possible range of estimated values, a possible deviation from an estimated reference value, etc.

[0087] • Sensitivity or sensing range, which may include a sensing receiver sensitivity level or range (e.g., in dB or dBm), which can also be determined per SCS (subcarrier spacing), sensing radio range, sensing signal detection threshold related to sensing range, sensing coverage range.

[0088] • Sensing resolution or granularity, e.g., for sensing measurements, sensing data, sensing result, or sensing report, spatial resolution or grid size of the sensing area or sensing target object, a minimum target object size, a distinguishable difference between (close in space or time) objects, states, conditions, or events. • Sensing data range, such as, for example, minimum and / or maximum considered values for sensing measurements, sensing data, sensing result, or sensing report.

[0089] • Delay, which may be a related quality parameter such as latency, response time, delay tolerance, e.g., no delay or delay intolerant, low delay, delay tolerant, max DI delay, etc.

[0090] • Update or refresh rate or speed for sensing data or sensing result,

[0091] • Stability of provided or considered sensing data or sensing result, degree of randomness, filtering level, trend description,

[0092] • Sensing capacity, such as, for example, sensing data capacity or sensing processing capacity.

[0093] • Accuracy of a sensing result, which can comprise horizontal accuracy, vertical accuracy, velocity accuracy, uncertainty, confidence level (e.g., 95% or 98%), sensing target recognition accuracy, sensing target detection accuracy, sensing target location / positioning accuracy, accuracy of detecting of presence / absence of a sensing target, accuracy of sensing target classification, error rate for a sensing result, correct detection or misdetection probability of a sensing target, etc.

[0094] • Positioning target QoS, such as, for example, positioning horizontal and / or vertical accuracy, 3D positioning requirement.

[0095] Methods for Obtaining QoSl

[0096] As described above regarding FIGURE 4, at step 1, a SCF receives a sensing request and obtains QoSl associated with the sensing request.

[0097] In a further example, SCF 12 can obtain two or more of QoSl, based on the same or different sensing requests. In one example, the SCF 12 can select one QoSl, from the list of two or more of QoSl, for the sensing result (e.g., signaling 34). In another example, the SCF 12 can send multiple sensing results (via signaling 34), each associated with one of the QoSl from the list. When reporting the sensing result, the SCF 12 can indicate the target QoS associated with the reported result. The sensing results associated with the different QoS 1 from the list can be obtained in different sensing resources, e.g., in different time windows.

[0098] The sensing request can be received from application or sensing client. The sensing request can be received from a RAN node, a UE, or a network entity. The SCF 12 can comprise a RAN node, a UE, or a core network node.

[0099] The QoSl can be further used in the SCF 12 for its actions / decisions in Step 2 or can be provided to another node (e.g., SU, SPF, positioning node or LMF, etc.) to control its actions / decisions in Step 2.

[0100] The QoSl can be comprised in or determined based on the received sensing request, e.g.:

[0101] • In one example, the sensing request can comprise the QoSl, so obtaining the QoSlcomprises extracting from the sensing request.

[0102] • In one example, the QoSl can be determined based on one or more parameters comprised in the sensing request, such as type of sensing task (e.g., area monitoring, presence / absence detection, object tracking, etc.), type of sensing target (e.g., weather condition such as rain, a person, a dog, a small object such as a key, a moving or non-moving object, a train, a vehicle, etc.), measurement type, area type (e.g., indoor or outdoor), etc.

[0103] • In one example, the QoS lean be determined based on the type of the sensing client or application from which the sensing request is received. The type of application or client can also be mapped to a corresponding sensing QoS class and the associated target QoS data.

[0104] • In one example, the sensing report can be categorized into a sensing type, which can then be mapped to a certain QoSl. The mapping can also consider Service- Level Agreement (SLA).

[0105] FIGURE 5 illustrates a method 100 for obtaining and using QoSl, according to certain embodiments. As illustrated, the method 100 begins at step 102 when the sensing request is received from a client. In a particular embodiment, and as illustrated in FIGURE 4, the sensing request may be received by a SCF from a UE, RAN node, or core network node.

[0106] Returning to FIGURE 5, at 104, the sensing request is categorized into a sensing type, which may include monitoring, tracking, around me, one-shot, periodic, and / or streaming, in particular embodiments.

[0107] At step 106, a Service Level Agreement (SLA) is obtained for the sensing request from the client. The SLA is stored in a network node such as UDM / GMLC. One or more relevant KPI may be identified, which may include target object positioning accuracy, miss / false detection allowed rate (probability) considering the sensing type and SLA, in particular embodiments. At step 108, the sensing resources needed for fulfilling the sensing QoS target are identified.

[0108] At step 110, the method includes indicating to the SPF 18 the determined KPI and the values. A response is received from the SPF if the desired target is met or failed.

[0109] At step 112, the method may include taking steps depending upon the successes / failures and considering the SLA. For example, in a particular embodiment, resources may be increased and sensing may be reattempted. Alternatively, in other example, the method may include responding with failure and / or performing sensing with lower resolution when SLA is flexible.

[0110] Methods for Using the QoSl

[0111] The obtained QoSl is used for at least one of the below, to enable obtaining one or more sensing results to meet the sensing request by doing at least one of the described below.

[0112] • Selecting a Sensing Method, Based on Sensing Target QoS

[0113] The term selecting a sensing method can comprise, e.g.:

[0114] • Based on the target QoS data, the selection process is decided by SCF based on at least one parameter in the target QoS data, autonomously or based on pre-defined or configured rules.

[0115] • In one example, the SCF can select a sensing method capable of delivering a fast sensing result if the sensing QoS is set to “no delay” or to a stringent latency requirement or the update / refresh rate is faster than a threshold.

[0116] • In one example, a more accurate sensing method is selected when the first target QoS data includes a higher accuracy requirement for a sensing result.

[0117] • In one example, the selected method is a sensing method relying on non-RF sensing, when the QoS target accuracy is higher than a threshold.

[0118] • In one example, a first sensing method is selected for a first sensing class, a second (different) sensing method is selected for a second sensing class, etc.

[0119] • In one example, a first sensing method delivering also a positioning result is selected for a first sensing class, a second sensing method without sensing target positioning is selected for a second sensing class, etc.

[0120] • In one example, a sensing method delivering also a positioning result is selected when positioning target QoS is comprised in sensing target QoS. If the target positioning QoS indicates the need for 3D positioning, a sensing method with 3D positioning capability is selected. • In one example, bi- / multi-static sensing can be selected when target sensing accuracy is more stringent, and mono-static sensing can be selected when it is less stringent.

[0121] • In one example, when target sensing resolution or a minimum target object size is small oris below a threshold, sensing with UE involvement (e.g., UE measurements or UE transmissions for sensing) is selected.

[0122] • In one example, UL-based sensing (based on sensing signals transmitted by UEs) is selected, when the target object size is small and / or high-accuracy sensing is necessary.

[0123] • In one example, a sensing method generating larger measurement reports can be selected for a larger target sensing capacity.

[0124] • Methods for Configuring Sensing Units, Based on Sensing Target QoS

[0125] • According to certain embodiments, an SU can comprise a UE or a RAN node.

[0126] • According to certain embodiments, methods for configuring sensing units can comprise configuring sensing units for at least one of transmitting or receiving radio signals for sensing, which can also comprise selecting sensing units, configuring a first list of time windows (comprising one or more windows) for transmit / receive / measurements / measurement reporting operations for sensing, configuring SU transmissions of radio signals for sensing, configuring SU reception of radio signals for sensing, configuring SU measurements, configuring SU measurement reporting, configuring dedicated or shared (with communication and / or positioning) resources or resource pools for the transmit / receive / measurements / measurement reporting operations for sensing, etc.

[0127] • According to certain embodiments, the term configuring SUs can comprise, e.g.:

[0128] • Based on the target QoS data, the configuration is controlled by SCF by a control message (and determined by SU based on at least one parameter in the message) or decided by SCF and then provided to SUs.

[0129] • Based on the target QoS data (which can be received from SCF node or can be obtained from SCF comprised in the same node as the SU), the configuration can be determined by SU, autonomously or based on pre-defined or configured rules.

[0130] Methods to Determine Configuration ofSU(s) (a UE or RAN node), Based on the QoSl

[0131] In a particular embodiment, based on the QoSl, one or more SUs are configured with dedicated or shared (with communication and / or positioning) resources or resource pools for the transmit / receive / measurements / measurement reporting operations for sensing, so that the configured resources are adapted to the target QoS. Sensing resources are prioritized (higher priority than for communications) or dedicated sensing resource pool is selected for more stringent target QoS. The resources can comprise time and / or frequency resources, including bandwidth.

[0132] In a particular embodiment, a larger bandwidth (BW) is configured for a more stringent sensing target QoS.

[0133] In a particular embodiment, positioning signals are configured for at least one SU (for transmitting and / or receiving positioning signals), in addition to configuring radio signals for sensing for the at least one SU, when the sensing target QoS includes positioning target QoS.

[0134] In a particular embodiment, based on the QoSl, one or more SUs are configured with a first list of time windows (comprising one or more windows) for transmit / receive / measurements / measurement reporting operations for sensing. FIGURES 6A- 6B illustrate an example message flow 200, comprising configuration of one or more time windows, according to certain embodiments. As illustrated, the message flow 200 includes signaling transmitted and / or received by a UE 202, a RAN-SU 204, a SCF 206, a SPF208, a SeMF 210, and Sensing client 212.

[0135] The method begins at step 220, when a sensing request from the sensing client 212 to a SeMF 210.

[0136] At step 225, the SeMF 210 transmits the sensing information request with sensing QoS information to SCF 206.

[0137] At step 230, the SCF 206 performs configuration of sensing window(s).

[0138] At step 240, the SCF 206 sends a sensing prioritization request to RAN-SU 204.

[0139] At step 245, the RAN-SU 204 configures a prioritized sensing measurements duration based on received sensing window(s).

[0140] At 250, the RAN-SU 204 sends an indication of the sensing window(s) for transmission and configuration to the UE 202. At 255, the RAN-SU 204 sends a sensing prioritization response to SCF 206.

[0141] At 260, sensing measurements reporting is performed during the sensing window(s).

[0142] At 265, the SPF 208 sends a sensing measurement processing result to the SeMF 210.

[0143] At 270, the SeMF 210 sends the sensing result report to the sensing client 212.

[0144] In a particular embodiment, during such a time window, the network / UE will prioritize sensing operation (transmission or reception / measurement) over at least one communication procedure or signal, to meet the target QoS. During such a time window, an SU can perform one or more sensing transmissions or measurements, aperiodic or periodic. Together with the SU sensing operation, there can also be a corresponding configuration of reception / transmissions, respectively, e.g., for SU comprising a UE transmitting sensing signals also RAN nodes are configured to receive these signals, or for SU comprising a UE receiving sensing signals also RAN nodes are configured accordingly to transmit these signals towards the UE (its direction, beam, frequency, BW, etc.), during the same time window. There can be different levels of priority, e.g., absolute priority, equal priority, higher priority for sensing (lower for communication), higher priority for communication (lower for sensing), etc. The prioritization can be set by SCF. When SCF is not in RAN, it can indicate to RAN the need for prioritization of sensing measurements.

[0145] In one example, the UE being an SU can continue communication, while gNB / SCF collects simultaneously sensing measurements in the UL; the UE can even be configured in a special way (e.g., a directed beam) to send its non-sensing signal, to enable sensing based on this signal.

[0146] In one example, during such a time window, the SU is not expected to change, e.g., transmit power or transmit timing for the signal to be used for sensing.

[0147] Methods for Configuring Sensing Processing Based on Sensing Target QoS

[0148] According to certain embodiments, methods for configuring sensing processing, based on sensing target QoS, includes, for example, configuring how or when to process or deliver the result of sensing processing, configuring a second list of time windows for sensing processing operations, etc.

[0149] The term configuring sensing processing or configuring SPFs includes, for example:

[0150] • Based on the target QoS data, the configuration is controlled by SCF by a control message (and determined by SPF based on at least one parameter in the message) or decided by SCF and then provided to SPFs. • Based on the target QoS data (which can be received from SCF node or can be obtained from SCF comprised in the same node as the SPF), the configuration can be determined by SPF, autonomously or based on pre-defined or configured rules.

[0151] In a particular embodiment, the processing can be configured, based on both target QoS and the SPCA information. The SPCA information can be signaled to enable processing control based on the target QoS data:

[0152] • between RAN nodes or between RAN node and SCF / SeMF, and / or

[0153] • between SPFs or between SPF and SCF / SeMF.

[0154] Methods to Determine a Sensing Processing Configuration Based on QoSl

[0155] In a particular embodiment, one or more SPFs are configured with a second list of time windows for sensing processing operations: o Configuring a list of sensing processing windows, where the SPF will process sensing measurements during that time window. The priority of processing for specific measurements or all measurements to be processed to obtain the same sensing result is decided based on the target QoS. o During a configured Sensing Processing Window, the SPF performs processing in certain intervals, performs results reporting to SeMF in certain intervals. o In a particular embodiment, the SPF can send a response message to acknowledge the usage of the indicated sensing processing window. Otherwise, a reject message is sent, for example, in case the sensing processing windows is too stringent for the SPF.

[0156] FIGURE 7 illustrates an example signaling diagram 300 for the configuration of sensing processing windows to meet target sensing QoS, according to certain embodiments. As illustrated, the message flow 300 includes signaling transmitted and / or received by a UE 302, a RAN-SU 304, a SPF 306, a SCF 308, a SeMF 310, and sensing client 312.

[0157] The method begins at step 320, when a sensing request is transmitted from the sensing client 312 to a SeMF 310.

[0158] At step 325, the SeMF 310 transmits the sensing information request with sensing QoS information to SCF 308. At step 330, the SCF 308 performs configuration of sensing processing window(s).

[0159] At step 335, SPF selection is performed.

[0160] At step 340, the SCF 308 sends a sensing prioritization request to the selected SPF 306.

[0161] At step 345, sensing measurement processing is performed during the sensing processing window(s).

[0162] At step 350, SPF 306 sends a sensing measurement processing result to the SeMF 310.

[0163] At 360, the SeMF 310 sends the sensing result report to the sensing client 312.

[0164] In a particular embodiment, a faster processing is configured for a more delay-stringent target QoS.

[0165] In a particular embodiment, a more accurate processing is configured for sensing measurements for a higher target accuracy or higher resolution.

[0166] In a particular embodiment, configuration of sensing processing window at SPF and sensing window at RAN-SU can be jointly performed.

[0167] In a particular embodiment, if sensing QoS requires low latency for sensing measurements report, SCF requests to setup a centralized SPF that is deployed closer to CN and can provide measurement faster.

[0168] In another embodiment, a list of sensing target QoS sets can be received by the SCF, and the SCF configures different windows for each sensing target QoS. The SCF also indicates which one it is attempting to meet when sending the reporting sensing result to SeMF.

[0169] Methods for Determining and Using a Second Target QoS Data Based on QoSl

[0170] According to certain embodiments, QoS2 is determined based on QoSl and using the QoS2 for obtaining or requesting (e.g., from a location controlling function, positioning node, or LMF) location information to enable obtaining of one or more sensing results to meet the sensing request.

[0171] In a particular embodiment, the QoS2 is further used to select a positioning method, configure at least one positioning reference signal transmission or reception, and / or for configuring one or more positioning measurements or measurement reports.

[0172] In a particular embodiment, the positioning result is obtained based on the QoS2 so that the final sensing result can be obtained based on the QoSl. Thus, more accurate positioning can be requested (based on the QoS2) and configured when higher accuracy is required also for sensing (based on the QoSl). In a further embodiment, when a sensing result is to be obtained in a specific set of time resources or periodically, the positioning resources are configured adaptively to the time resources for sensing, for example, in the same or close time resources and the relation between sensing and positioning resources is determined by the QoS2.

[0173] Methods of Assessing Sensing Performance with Respect to the Target QoS Data

[0174] According to certain embodiments, methods of assessing sensing performance with respect to the target QoS data include assessing whether the requirements (e.g., criteria) imposed by the target QoS data are met (for an obtained sensing result) or can be met (from the configuration / result feasibility point of view, even when no sensing result is yet available) and performing actions based on the assessment result. The assessing can further include sending a response to the sensing request, which includes a result of assessment. In various particular embodiments, the assessment includes one or a combination of methods described below:

[0175] • In one example embodiment, the assessment includes responding to the sender node that sent the sensing request in step 1 (described above with respect to FIGURE 4) with a confirmation or rejection message that indicates the successfiil / unsuccessfiil controlling operation, based on the target QoS data (e.g., configuring the sensing units, SPFs, sensing resources, the time windows for sensing reporting and processing, etc.). The success or no success can depend on whether it is possible or not to meet the requested QoS, e.g., not all necessary SUs, SPFs, resources, or configurations are available, etc.

[0176] • In one example embodiment, the assessment can comprise checking whether the obtained results are adequate for the requested QoS, or the assessment can be based on the obtained sensing result and its quality characteristics, while comparing the quality of the obtained result to the required quality according to the QoS requirements (e.g., criteria). If the QoS requirements are not met or the sensing result is not adequate, the sensing controlling function triggers another measurement or sensing data request, possibly with an updated configuration, in attempt to obtain a second sensing result meeting the QoS requirements, or it indicates to the entity, from which the sensing request was obtained, that the QoS requirements are not met, possibly also including the obtained (first) sensing result. • In another example embodiment, a list of sensing target QoS sets are received by the SCF, and the SCF configures different windows for each sensing target QoS. The SCF also indicates which one it is attempting to meet, when sending the assessment indication (with or prior to obtaining the result) or reporting sensing result to SeMF. In one example, the assessment can be performed or indicated separately for each of the first target QoS data set in the list or for a selected. In another example embodiment, the assessment is for one selected first target QoS data set from the list (e.g., most relaxed or the closest to the obtained sensing result quality).

[0177] • In another example embodiment, the assessment is based on sensing processing related capability and availability (SPCA). If the available processing resources are not sufficient to meet the QoS requirements (e.g., the needed processing resources are occupied, slower than needed, etc.), the sensing controlling function can indicate to the entity, from which the sensing request was obtained, that the QoS requirements cannot be met, possibly also indicating the cause. The SPCA information can be acquired by the node performing assessment from the node owing the SPCA information.

[0178] • In another example embodiment, the assessment is based on SU capabilities and availability. If the available SUs and their sensing transmit / receive resources are not sufficient to meet the QoS requirements (e.g., the receiver is not capable of performing measurements needed, the resources are occupied and the necessary transmit configurations are not possible, the number of available sensing units is below a threshold associated with the QoS requirements, etc.), the sensing controlling function indicates to the entity from which the sensing request was obtained that the QoS requirements cannot be met, possibly also indicating the cause.

[0179] • In one example embodiment, in case of actual or potential failure (to meet the target QoS), a failure message is sent with a cause value indicating the reason of unsuccessful operation. In a particular embodiment, the message is sent by the SCF to the sender of the sensing request or by the node determining the failure such as, for example, by SU to SCF or by SPF to SCF.

[0180] FIGURE 8 shows an example of a communication system 400 in accordance with some embodiments. In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410a and 410b (one or more of which may be generally referred to as network nodes 410), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 402 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 402, including one or more network nodes 410 and / or core network nodes 408.

[0181] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 412a, 412b, 412c, and 412d (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

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

[0183] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 406 includes one more core network nodes (e.g., core network node 408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 408. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0184] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and / or the telecommunication network 402 and may be operated by the service provider or on behalf of the service provider. The host 416 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0185] As a whole, the communication system 400 of FIGURE 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0186] In some examples, the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunications network 402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0187] In some examples, the UEs 412 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

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

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

[0190] FIGURE 9 shows a UE 500 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0191] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0192] The UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input / output interface 506, a power source 508, a memory 510, a communication interface 512, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 9. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0193] The processing circuitry 502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 510. The processing circuitry 502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 502 may include multiple central processing units (CPUs).

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

[0195] In some embodiments, the power source 508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 508 may further include power circuitry for delivering power from the power source 508 itself, and / or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied.

[0196] The memory 510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems. The memory 510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 510 may allow the UE 500 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 510, which may be or comprise a device-readable storage medium.

[0197] The processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 518 and / or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., antenna 522) and may share circuit components, software or firmware, or alternatively be implemented separately.

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

[0199] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0200] As another example, a UE includes an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0201] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device includes circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 500 shown in FIGURE 9.

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

[0203] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0204] FIGURE 10 shows a network node 600 in accordance with some embodiments.

[0205] As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0206] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0207] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0208] The network node 600 includes a processing circuitry 602, a memory 604, a communication interface 606, and a power source 608. The network node 600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 600 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 600.

[0209] The processing circuitry 602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 600 components, such as the memory 604, to provide network node 600 functionality.

[0210] In some embodiments, the processing circuitry 602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of radio frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the radio frequency (RF) transceiver circuitry 612 and the baseband processing circuitry 614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0211] The memory 604 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 602. The memory 604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and / or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and memory 604 is integrated.

[0212] The communication interface 606 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 606 comprises port(s) / terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. The communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. Radio front-end circuitry 618 comprises fdters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to an antenna 610 and processing circuitry 602. The radio front-end circuitry may be configured to condition signals communicated between antenna 610 and processing circuitry 602. The radio front-end circuitry 618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of fdters 620 and / or amplifiers 622. The radio signal may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0213] In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618, instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612, as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

[0214] The antenna 610 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 610 may be coupled to the radio front-end circuitry 618 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 610 is separate from the network node 600 and connectable to the network node 600 through an interface or port.

[0215] The antenna 610, communication interface 606, and / or the processing circuitry 602 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 610, the communication interface 606, and / or the processing circuitry 602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0216] The power source 608 provides power to the various components of network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 608. As a further example, the power source 608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0217] Embodiments of the network node 600 may include additional components beyond those shown in FIGURE 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.

[0218] FIGURE 11 is a block diagram illustrating a virtualization environment 700 in which functions implemented by some embodiments may be virtualized.

[0219] In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 700 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 700 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0220] Applications 702 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Hardware 704 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 708a and 708b (one or more of which may be generally referred to as VMs 708), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to the VMs 708.

[0221] The VMs 708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of VMs 708, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0222] In the context of NFV, a VM 708 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 708, and that part of hardware 704 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 708 on top of the hardware 704 and corresponds to the application 702.

[0223] Hardware 704 may be implemented in a standalone network node with generic or specific components. Hardware 704 may implement some functions via virtualization. Alternatively, hardware 704 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 710, which, among others, oversees lifecycle management of applications 702. In some embodiments, hardware 704 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 712 which may alternatively be used for communication between hardware nodes and radio units.

[0224] FIGURE 12 illustrates a method 800 by a SU 16, 410, 412 performing a sensing operation, according to certain embodiments. As illustrated, the method begins at step 802 when the SU receives a sensing request. At step 804, the SU receives QoSl based on the sensing request. At step 806, the SU receives, from a network function performing a sensing function, one or more configured sensing resources for obtaining a sensing result to satisfy the sensing request. Based on the one or more configured sensing resources, the SU performs a sensing procedure in a sensing session to obtain the sensing result, at step 808. At step 810, the SU determines whether the sensing result satisfies at least one criteria. At step 812, the Su transmits the sensing result to a network.

[0225] In a particular embodiment, the SU includes a UE, a radio network node, or a TRP.

[0226] In a particular embodiment, the UE performs the sensing operation, and the sensing operation includes at least one of: transmitting radio signals for sensing; receiving radio signals for sensing; and performing sensing measurements based on received radio signals for sensing.

[0227] In a particular embodiment, the sensing request includes at least one of: a sensing request from a Sensing Client, a sensing measurement request, or a sensing radio signal transmission request.

[0228] In a particular embodiment, the one or more criteria includes at least one of: a latency requirement, an accuracy requirement, sensitivity requirement, delay requirement, and refresh rate.

[0229] In a particular embodiment, the QoS data includes at least one of: sensing QoS class data, reliability criteria, validity criteria, confidence level, confidence interval, sensitivity or sensing range, sensing resolution, sensing granularity, sensing data range, delay, update or refresh rate or speed, stability of sensing data, sensing capacity, accuracy of a sensing result, and positioning accuracy or requirement.

[0230] In a particular embodiment, the QoS info is used by the SU to make the assessment as to whether the sensing operation quality (measurement and configuration) can be met and / or adapt the measurements configuration, reporting configuration, or sensing signal transmissions configuration accordingly, to ensure that the desired QoS is met. If the QoS is not met, in a particular embodiment, the SU transmits an indication that it is not met. The measurement or sensing result may or may not be reported. If the QoS is met, the result is reported without indication, in a particular embodiment.

[0231] In a particular embodiment, the sensing result includes sensing data that comprises at least one of: at least one radio measurement associated with sensing, a sensing indication, a sensing report, and a quality metric associated with at least one radio measurement or sensing result.

[0232] In a particular embodiment, the one or more configured resources comprise at least one of: one or more periodic resources, one or more semi-persistent resources, one or more on - demand resources, and one or more one-shot resources.

[0233] In a particular embodiment, receiving the one or more configured sensing resources includes receiving the one or more configured sensing resources from a Radio Access Network node 410 performing the sensing function.

[0234] In a particular embodiment, performing the sensing procedure in the sensing session to obtain the sensing result includes receiving, from a network sensing function at least one of: a sensing method, configuration, sensing measurements configuration, and a sensing reference signal transmission configuration to be performed to meet the QoS data.

[0235] In a particular embodiment, receiving the one or more configured sensing resources includes receiving the one or more configured sensing resources from a core network node performing the sensing controlling function.

[0236] In a particular embodiment, the SU determines an assessment result based on whether the QoS data met the one or more criteria.

[0237] In a further particular embodiment, based on the assessment result, the SU performs at least one of: transmitting a confirmation message associated with the sensing request; transmitting a rejection message associated with the sensing request; performing an additional sensing session to obtain an additional sensing result; and transmitting a failure message comprising a cause value that indicates a reason associated with sensing request failure.

[0238] FIGURE 13 illustrates a method 900 performed by a network node 410, 408 operating as a sensing function for configuring sensing resources, according to certain embodiments. As illustrated, the method includes receiving a sensing request, at step 902. At step 904, the network node receives QoSl based on the sensing request. Based on the QoSl, the network node determines one or more sensing resources for use by one or more sensing units for obtaining a sensing result to satisfy the sensing request, at step 906. At step 908, the network node transmits information indicating the one or more sensing resources for use by the one or more sensing units.

[0239] In a particular embodiment, the sensing request is received from a Sensing Client.

[0240] In a particular embodiment, the network node includes a RAN node 410 and the information is transmitted to a UE 412.

[0241] In a particular embodiment, the network node is a core network node 408 and the information is transmitted to a RAN node 410 and / or a UE 412.

[0242] In a particular embodiment, the network node transmits the first QoS data to a UE or to the one or more sensing units.

[0243] In a particular embodiment, configuring the one or more sensing resources includes at least one of: selecting a sensing method for a sensing session; configuring the one or more sensing units; transmitting one or more control messages to the one or more sensing units; configuring sensing processing; determining a second QoS data; determining whether one or more criteria associated with the first QoS Data and / or second QoS data is met; and receiving an update message.

[0244] In a particular embodiment, selecting the sensing method includes at least one of: selecting the sensing method based on a latency requirement; selecting the sensing method based on an accuracy requirement; selecting the sensing method based on a sensitivity requirement; selecting the sensing method based on a delay requirement; selecting the sensing method based on a refresh rate; selecting the sensing method associated with non-RF sensing; selecting the sensing method associated with a positioning result; and selecting the sensing method associated with at least one User Equipment measurement.

[0245] In a particular embodiment, configuring the one or more sensing units includes at least one of: configuring the one or more sensing units for transmitting radio signals; configuring the one or more sensing units for receiving radio signals; selecting the one or more sensing units for a sensing session; configuring a list of time windows; configuring at least one radio signal transmission for the one or more sensing units; configuring at least one radio signal reception for the one or more sensing units; configuring one or more measurements; configuring measurement reporting associated with the one or more sensing units; and configuring positioning signals for the one or more sensing units.

[0246] In a particular embodiment, configuring the list of time windows includes at least one of: configuring a transmitting operation associated with a first time window of the list of time windows; configuring a receiving operation associated with a second time window of the list of time windows; configuring a measurement operation associated with a third time window of the list of time windows; and configuring a measurement reporting operation associated with a fourth time window of the list of time windows.

[0247] In a particular embodiment, configuring sensing processing includes at least one of: configuring a second list of time windows associated with one or more sensing processing operations; determining a sensing processing configuration; configuring one or more sensing processing units; and selecting one or more sensing processing units for performing the one or more sensing processing operations.

[0248] In a particular embodiment, determining the sensing processing configuration includes at least one of: configuring a list of sensing processing windows, wherein processing of sensing measurements is performed during the sensing processing windows; and selecting a sensing processing method.

[0249] In a particular embodiment, the network node performs at least one of: requesting location information based on the sensing request; receiving the location information; selecting a positioning method based on the second QoS data; configuring a positioning reference signal transmission and / or a positioning reference signal reception; configuring one or more positioning measurements based on the second QoS data; configuring one or more positioning measurement reports based on the second QoS data; receiving one or more positioning results based on the second QoS data; and receiving the sensing result based on the one or more positioning results.

[0250] In a particular embodiment, determining whether the one or more criteria associated with the first QoS data and / or the second QoS data is met comprises at least one of: determining whether the sensing result satisfies at least one of the one or more criteria; and determining an assessment result based on whether the first QoS data and / or the second QoS data met the one or more criteria.

[0251] In a particular embodiment, determining the assessment result includes at least one of: transmitting a confirmation message associated with the sensing request; transmitting a rejection message associated with the sensing request; transmitting the sensing result; performing an additional sensing session to obtain an additional sensing result; and transmitting a failure message comprising a cause value that indicates a reason associated with sensing request failure.

[0252] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0253] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0254] EXAMPLE EMBODIMENTS

[0255] Group A Embodiments

[0256] Example Embodiment 1. A method performed by a user equipment for configuring sensing resources, the method comprising: receiving a sensing request; receiving QoS data based on the sensing request; and based on the QoS data, configuring one or more sensing resources for obtaining a sensing result to satisfy the sensing request.

[0257] Example Embodiment 2. The method of any of the previous embodiments, further comprising the step of: performing a sensing session to obtain the sensing result.

[0258] Example Embodiment 3. The method of any of the previous embodiments, further comprising the step of: transmitting the QoS data.

[0259] Example Embodiment 4. The method of any of the previous embodiments, wherein configuring the one or more sensing resources comprises at least one of: selecting a sensing method for a sensing session; configuring one or more sensing units; configuring sensing processing; determining a second QoS data; determining whether one or more criteria associated with the QoS Data is met; and receiving an update message.

[0260] Example Embodiment 5. The method of any of the previous embodiments, wherein selecting a sensing method comprises at least one of: selecting the sensing method based on a latency requirement; selecting the sensing method based on an accuracy requirement; selecting the sensing method associated with non-RF sensing; selecting the sensing method associated with a positioning result; and selecting the sensing method associated with UE measurements.

[0261] Example Embodiment 6. The method of any of the previous embodiments, wherein configuring one or more sensing units comprises at least one of: configuring the one or more sensing units for transmitting radio signals; configuring the one or more sensing units for receiving radio signals; selecting the one or more sensing units for a sensing session; configuring a list of time windows; configuring radio signal transmissions for the one or more sensing units; configuring radio signal receptions for the one or more sensing units; configuring one or more measurements; configuring measurement reporting associated with the one or more sensing units; and configuring positioning signals for the one or more sensing units.

[0262] Example Embodiment 7. The method of any of the previous embodiments, further comprising the step of: transmitting one or more control messages to the sensing units.

[0263] Example Embodiment 8. The method of any of the previous embodiments, wherein configuring the list of time windows comprises at least one of: configuring a transmitting operation associated with a first time window of the list of time windows; configuring a receiving operation associated with a second time window of the list of time windows; configuring a measurement operation associated with a third time window of the list of time windows; and configuring a measurement reporting operation associated with a fourth time window of the list of time windows. Example Embodiment 9. The method of any of the previous embodiments, wherein configuring sensing processing comprises at least one of: configuring a second list of time windows associated with one or more sensing processing operations; determining a sensing processing configuration; configuring one or more sensing processing units; and selecting one or more sensing processing units for performing the one or more sensing processing operations.

[0264] Example Embodiment 10. The method of any of the previous embodiments, wherein determining the sensing processing configuration comprises at least one of: configuring a list of sensing processing windows, wherein processing of sensing measurements is performed during the sensing processing windows; and selecting a sensing processing method.

[0265] Example Embodiment 11. The method of any of the previous embodiments, further comprising at least one of: requesting location information based on the sensing request; receiving the location information; selecting a positioning method based on the second QoS data; configuring a positioning reference signal transmission and / or a positioning reference signal reception; configuring one or more positioning measurements based on the second QoS data; configuring one or more positioning measurement reports based on the second QoS data; receiving one or more positioning results based on the second QoS data; and receiving the sensing result based on the one or more positioning results.

[0266] Example Embodiment 12. The method of any of the previous embodiments, wherein determining whether one or more criteria associated with the QoS data is met comprises at least one of: determining whether the sensing result satisfies at least one of the one or more criteria; and determining an assessment result.

[0267] Example Embodiment 13. The method of any of the previous embodiments, wherein determining the assessment result comprises at least one of: transmitting a confirmation message associated with the sensing request; transmitting a rejection message associated with the sensing request; transmitting the sensing result; performing an additional sensing session to obtain an additional sensing result; transmitting a failure message comprising a cause value that indicates a reason associated with sensing request failure.

[0268] Example Embodiment 14. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

[0269] Group B Embodiments

[0270] Example Embodiment 15. A method performed by a network node for configuring sensing resources, the method comprising: receiving a sensing request; receiving QoS data based on the sensing request; and based on the QoS data, configuring one or more sensing resources for obtaining a sensing result to satisfy the sensing request.

[0271] Example Embodiment 16. The method of any of the previous embodiments, further comprising the step of: performing a sensing session to obtain the sensing result.

[0272] Example Embodiment 17. The method of any of the previous embodiments, further comprising the step of: transmitting the QoS data.

[0273] Example Embodiment 18. The method of any of the previous embodiments, wherein configuring the one or more sensing resources comprises at least one of: selecting a sensing method for a sensing session; configuring one or more sensing units; configuring sensing processing; determining a second QoS data; determining whether one or more criteria associated with the QoS Data is met; and receiving an update message.

[0274] Example Embodiment 19. The method of any of the previous embodiments, wherein selecting a sensing method comprises at least one of: selecting the sensing method based on a latency requirement; selecting the sensing method based on an accuracy requirement; selecting the sensing method associated with non-RF sensing; selecting the sensing method associated with a positioning result; and selecting the sensing method associated with UE measurements.

[0275] Example Embodiment 20. The method of any of the previous embodiments, wherein configuring one or more sensing units comprises at least one of: configuring the one or more sensing units for transmitting radio signals; configuring the one or more sensing units for receiving radio signals; selecting the one or more sensing units for a sensing session; configuring a list of time windows; configuring radio signal transmissions for the one or more sensing units; configuring radio signal receptions for the one or more sensing units; configuring one or more measurements; configuring measurement reporting associated with the one or more sensing units; and configuring positioning signals for the one or more sensing units.

[0276] Example Embodiment 21. The method of any of the previous embodiments, further comprising the step of: transmitting one or more control messages to the sensing units.

[0277] Example Embodiment 22. The method of any of the previous embodiments, wherein configuring the list of time windows comprises at least one of: configuring a transmitting operation associated with a first time window of the list of time windows; configuring a receiving operation associated with a second time window of the list of time windows; configuring a measurement operation associated with a third time window of the list of time windows; and configuring a measurement reporting operation associated with a fourth time window of the list of time windows.

[0278] Example Embodiment 23. The method of any of the previous embodiments, wherein configuring sensing processing comprises at least one of: configuring a second list of time windows associated with one or more sensing processing operations; determining a sensing processing configuration; configuring one or more sensing processing units; and selecting one or more sensing processing units for performing the one or more sensing processing operations.

[0279] Example Embodiment 24. The method of any of the previous embodiments, wherein determining the sensing processing configuration comprises at least one of: configuring a list of sensing processing windows, wherein processing of sensing measurements is performed during the sensing processing windows; and selecting a sensing processing method.

[0280] Example Embodiment 25. The method of any of the previous embodiments, further comprising at least one of: requesting location information based on the sensing request; receiving the location information; selecting a positioning method based on the second QoS data; configuring a positioning reference signal transmission and / or a positioning reference signal reception; configuring one or more positioning measurements based on the second QoS data; configuring one or more positioning measurement reports based on the second QoS data; receiving one or more positioning results based on the second QoS data; and receiving the sensing result based on the one or more positioning results.

[0281] Example Embodiment 26. The method of any of the previous embodiments, wherein determining whether one or more criteria associated with the QoS data is met comprises at least one of: determining whether the sensing result satisfies at least one of the one or more criteria; and determining an assessment result.

[0282] Example Embodiment 27. The method of any of the previous embodiments, wherein determining the assessment result comprises at least one of: transmitting a confirmation message associated with the sensing request; transmitting a rejection message associated with the sensing request; transmitting the sensing result; performing an additional sensing session to obtain an additional sensing result; transmitting a failure message comprising a cause value that indicates a reason associated with sensing request failure.

[0283] Example Embodiment 28. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0284] Group C Embodiments

[0285] Example Embodiment 29. A user equipment for configuring sensing resources, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0286] Example Embodiment 30. A network node for configuring sensing resources, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

[0287] Example Embodiment 31. A user equipment (UE) for configuring sensing resources, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0288] Example Embodiment 32. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0289] Example Embodiment 33. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0290] Example Embodiment 34. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0291] Example Embodiment 35. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0292] Example Embodiment 36. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0293] Example Embodiment 37. A communication system configured to provide an over- the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0294] Example Embodiment 38. The communication system of the previous embodiment, further comprising: the network node; and / or the UE.

[0295] Example Embodiment 39. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

[0296] Example Embodiment 40. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0297] Example Embodiment 41. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

[0298] Example Embodiment 42. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.

[0299] Example Embodiment 43. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

[0300] Example Embodiment 44. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host.

[0301] Example Embodiment 45. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

[0302] Example Embodiment 46. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0303] Example Embodiment 47. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

[0304] Example Embodiment 48. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.

[0305] Example Embodiment 49. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0306] Example Embodiment 50. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0307] Example Embodiment 51. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0308] Example Embodiment 52. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0309] Example Embodiment 53. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising : at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0310] Example Embodiment 54. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0311] Example Embodiment 55. The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Claims

CLAIMS1. A method (800) by a sensing unit (412) performing a sensing operation, the method comprising: receiving (802) a sensing request; receiving (804) Quality of Service, QoS, data based on the sensing request; receiving (806), from a network function performing a sensing function, one or more configured sensing resources for obtaining a sensing result to satisfy the sensing request; based on the one or more configured sensing resources, performing (808) a sensing procedure in a sensing session to obtain the sensing result; determining (810) whether the sensing result satisfies at least one criteria; and transmitting (812) the sensing result to a network.

2. The method of Claim 1, wherein the sensing unit comprises: a User Equipment, UE, a radio network node, or a Transmission-Reception Point, TRP.

3. The method of any of Claims 1 to 2, comprising performing the sensing operation, and wherein the sensing operation comprises at least one of: transmitting radio signals for sensing; receiving radio signals for sensing; and performing sensing measurements based on received radio signals for sensing.

4. The method of any of Claims 1 to 3, wherein the sensing request comprises at least one of: a sensing request from a Sensing Client, a sensing measurement request, or a sensing radio signal transmission request.

5. The method of any of Claims 1 to 4, wherein the one or more criteria comprises at least one of: a latency requirement, an accuracy requirement, sensitivity requirement, delay requirement, and refresh rate.

6. The method of any one of Claims 1 to 5, wherein the QoS data comprises at least one of: sensing QoS class data, reliability criteria, validity criteria, confidence level, confidence interval, sensitivity or sensing range, sensing resolution, sensing granularity, sensing data range, delay, update or refresh rate or speed, stability of sensing data, sensing capacity, accuracy of a sensing result, and positioning accuracy or requirement.

7. The method of any one of Claims 1 to 6, wherein the sensing result comprises sensing data that comprises at least one of: at least one radio measurement associated with sensing, a sensing indication, a sensing report, and a quality metric associated with at least one radio measurement or sensing result.

8. The method of any one of Claims 1 to 7, wherein the one or more configured resources comprise at least one of: one or more periodic resources, one or more semi-persistent resources, one or more on -demand resources, and one or more one-shot resources.

9. The method of any one of Claims 1 to 8, wherein receiving the one or more configured sensing resources comprises receiving the one or more configured sensing resources from a Radio Access Network node (410) performing the sensing function.

10. The method of any one of Claims 1 to 9, wherein performing the sensing procedure in the sensing session to obtain the sensing result comprises receiving, from a network sensing function at least one of: a sensing method, configuration, sensing measurements configuration, and a sensing reference signal transmission configuration to be performed to meet the QoS data.

11. The method of any one of Claims 1 to 10, wherein receiving the one or more configured sensing resources comprises receiving the one or more configured sensing resources from a core network node performing the sensing controlling function.

12. The method of any one of Claims 1 to 11, comprising: determining an assessment result based on whether the QoS data met the one or more criteria.

13. The method of Claim 12, wherein based on the assessment result, the method comprises at least one of: transmitting a confirmation message associated with the sensing request; transmitting a rejection message associated with the sensing request; performing an additional sensing session to obtain an additional sensing result; and transmitting a failure message comprising a cause value that indicates a reason associated with sensing request failure.

14. A method (900) performed by a network node (410, 408) operating as a sensing function for configuring sensing resources, the method comprising: receiving (902) a sensing request; receiving (904) first Quality of Service, QoS, data based on the sensing request; based on the first QoS data, determining (906) one or more sensing resources for use by one or more sensing units for obtaining a sensing result to satisfy the sensing request; and transmitting (908) information indicating the one or more sensing resources for use by the one or more sensing units.

15. The method of Claim 14, wherein the sensing request is received from a Sensing Client.

16. The method of any one of Claims 14 to 15, wherein the network node comprises a Radio Access Network node (410) and wherein the information is transmitted to a User Equipment, UE (412).

17. The method of any one of Claims 14 to 15, wherein the network node comprises a core network node (408) and wherein the information is transmitted to a Radio Access Network node (410) and / or a User Equipment, UE (412).

18. The method of any one of Claims 14 to 17, comprising the step of: transmitting the first QoS data to a UE or to the one or more sensing units.

19. The method of any one of Claims 14 to 18, wherein configuring the one or more sensing resources comprises at least one of: selecting a sensing method for a sensing session; configuring the one or more sensing units; transmitting one or more control messages to the one or more sensing units; configuring sensing processing; determining a second QoS data; determining whether one or more criteria associated with the first QoS Data and / or second QoS data is met; and receiving an update message.

20. The method of Claim 29, wherein selecting the sensing method comprises at least one of: selecting the sensing method based on a latency requirement; selecting the sensing method based on an accuracy requirement; selecting the sensing method based on a sensitivity requirement; selecting the sensing method based on a delay requirement; selecting the sensing method based on a refresh rate; selecting the sensing method associated with non-RF sensing; selecting the sensing method associated with a positioning result; and selecting the sensing method associated with at least one User Equipment measurement.

21. The method of any one of Claims 19 to 20, wherein configuring the one or more sensing units comprises at least one of: configuring the one or more sensing units for transmitting radio signals; configuring the one or more sensing units for receiving radio signals; selecting the one or more sensing units for a sensing session; configuring a list of time windows; configuring at least one radio signal transmission for the one or more sensing units;configuring at least one radio signal reception for the one or more sensing units; configuring one or more measurements; configuring measurement reporting associated with the one or more sensing units; and configuring positioning signals for the one or more sensing units.

22. The method of any Claim 16, wherein configuring the list of time windows comprises at least one of: configuring a transmitting operation associated with a first time window of the list of time windows; configuring a receiving operation associated with a second time window of the list of time windows; configuring a measurement operation associated with a third time window of the list of time windows; and configuring a measurement reporting operation associated with a fourth time window of the list of time windows.

23. The method of any one of Claims 19 to 22, wherein configuring sensing processing comprises at least one of: configuring a second list of time windows associated with one or more sensing processing operations; determining a sensing processing configuration; configuring one or more sensing processing units; and selecting one or more sensing processing units for performing the one or more sensing processing operations.

24. The method of Claim 23, wherein determining the sensing processing configuration comprises at least one of: configuring a list of sensing processing windows, wherein processing of sensing measurements is performed during the sensing processing windows; and selecting a sensing processing method.

25. The method of any one of Claims 19 to 24, comprising at least one of: requesting location information based on the sensing request; receiving the location information; selecting a positioning method based on the second QoS data; configuring a positioning reference signal transmission and / or a positioning referencesignal reception; configuring one or more positioning measurements based on the second QoS data; configuring one or more positioning measurement reports based on the second QoS data; receiving one or more positioning results based on the second QoS data; and receiving the sensing result based on the one or more positioning results.

26. The method of any one of Claims 19 to 25, wherein determining whether the one or more criteria associated with the first QoS data and / or the second QoS data is met comprises at least one of: determining whether the sensing result satisfies at least one of the one or more criteria; and determining an assessment result based on whether the first QoS data and / or the second QoS data met the one or more criteria.

27. The method of Claim 26, wherein determining the assessment result comprises at least one of: transmitting a confirmation message associated with the sensing request; transmitting a rejection message associated with the sensing request; transmitting the sensing result; performing an additional sensing session to obtain an additional sensing result; and transmitting a failure message comprising a cause value that indicates a reason associated with sensing request failure.

28. A sensing unit (412) for performing a sensing function, the sensing unit configured to: receive (802) a sensing request; receive (804) Quality of Service, QoS, data based on the sensing request; receive (806), from a network function performing a sensing function, one or more configured sensing resources for obtaining a sensing result to satisfy the sensing request; based on the one or more configured sensing resources, perform (808) a sensing procedure in a sensing session to obtain the sensing result; determine (810) whether the sensing result satisfies at least one criteria; and transmit (812) the sensing result to a network.

29. The sensing unit of Claim 28, comprising: a User Equipment, UE,a radio network node, or a Transmission-Reception Point, TRP.

30. The sensing unit of any of Claims 28 to 29, configured to perform the sensing operation, and wherein the sensing operation comprises at least one of: transmitting radio signals for sensing; receiving radio signals for sensing; and performing sensing measurements based on received radio signals for sensing.

31. The sensing unit of any of Claims 28 to 30, wherein the sensing request comprises at least one of: a sensing request from a Sensing Client, a sensing measurement request, or a sensing radio signal transmission request.

32. The sensing unit of any of Claims 28 to 31, wherein the one or more criteria comprises at least one of: a latency requirement, an accuracy requirement, sensitivity requirement, delay requirement, and refresh rate.

33. The sensing unit of any one of Claims 28to 32, wherein the QoS data comprises at least one of: sensing QoS class data, reliability criteria, validity criteria, confidence level, confidence interval sensitivity or sensing range, sensing resolution, sensing granularity, sensing data range, delay, update or refresh rate or speed,stability of sensing data, sensing capacity, accuracy of a sensing result, and positioning accuracy or requirement.

34. The sensing unit of any one of Claims 28 to 33, wherein the sensing result comprises sensing data that comprises at least one of: at least one radio measurement associated with sensing, a sensing indication, a sensing report, and a quality metric associated with at least one radio measurement or sensing result.

35. The sensing unit of any one of Claims 28 to 34, wherein the one or more configured resources comprise at least one of: one or more periodic resources, one or more semi-persistent resources, one or more on-demand resources, and one or more one-shot resources.

36. The sensing unit of any one of Claims 28 to 35, wherein: when receiving the one or more configured sensing resources, the sensing unit is configured to receive the one or more configured sensing resources from a Radio Access Network node (410) or a core network node.

37. The sensing unit of any one of Claims 28 to 36, wherein the sensing unit is configured to receive, from a network sensing function at least one of: a sensing method configuration sensing measurements configuration, and a sensing reference signal transmission configuration to be performed to meet the QoS data.

38. The sensing unit of any one of Claims 28 to 37, wherein: the sensing unit is configured to determine an assessment result based on whether the QoS data met the one or more criteria, and based on the assessment result, the sensing unit is configured to perform at least one of: transmit a confirmation message associated with the sensing request; transmit a rejection message associated with the sensing request;perform an additional sensing session to obtain an additional sensing result; and transmit a failure message comprising a cause value that indicates a reason associated with sensing request failure.

39. A network node (410, 408) operating as a sensing function for configuring sensing resources, the network node configured to: receive (902) a sensing request; receive (904) first Quality of Service, QoS, data based on the sensing request; based on the first QoS data, determine (906) one or more sensing resources for use by one or more sensing units for obtaining a sensing result to satisfy the sensing request; and transmit (908) information indicating the one or more sensing resources for use by the one or more sensing units.

40. The network node of Claim 39, wherein the sensing request is received from a Sensing Client.

41. The network node of any one of Claims 39 to 40, wherein: the network node comprises a Radio Access Network node (410) and the information is transmitted to a User Equipment, UE (412), or the network node comprises a core network node (408) and the information is transmitted to a RAN node and / or a UE.

42. The network node of any one of Claims 39 to 41, wherein the network node is configured to transmit the first QoS data to a UE or to the one or more sensing units.

43. The network node of any one of Claims 39 to 42, wherein when configuring the one or more sensing resources, the network node is configured to perform at least one of: selecting a sensing method for a sensing session; configuring the one or more sensing units; transmitting one or more control messages to the one or more sensing units; configuring sensing processing; determining a second QoS data; determining whether one or more criteria associated with the first QoS Data and / or second QoS data is met; and receiving an update message.

44. The network node of Claim 43, wherein when selecting the sensing method, the network node is configured to perform at least one of:selecting the sensing method based on a latency requirement; selecting the sensing method based on an accuracy requirement; selecting the sensing method based on a sensitivity requirement; selecting the sensing method based on a delay requirement; selecting the sensing method based on a refresh rate; selecting the sensing method associated with non-RF sensing; selecting the sensing method associated with a positioning result; and selecting the sensing method associated with at least one User Equipment measurement.

45. The network node of any one of Claims 39 to 44, wherein when determining whether the one or more criteria associated with the first QoS data is met comprises at least one of: determining whether the sensing result satisfies at least one of the one or more criteria; and determining an assessment result based on whether the first QoS data met the one or more criteria.

46. The network node of Claim 45, wherein when determining the assessment result, the network node is configured to perform at least one of: transmitting a confirmation message associated with the sensing request; transmitting a rejection message associated with the sensing request; transmitting the sensing result; performing an additional sensing session to obtain an additional sensing result; and transmitting a failure message comprising a cause value that indicates a reason associated with sensing request failure.

Images