Sensing in a wireless communication system

Abstract

There is herein disclosed an apparatus for a sensing management function. The apparatus is arranged to perform at least: receiving, from a sensing client of a wireless communication system, a sensing

Description

Field The present specification relates to sensing in a wireless communication system, in 5 particular to monitoring quality of service of a sensing service provided by wireless communication system configured for sensing. Background Wireless communication systems configured for sensing are capable of sensing a scene 10 surrounding a sensing device and processing sensor data received from the sensing system to detect or track objects or extract features from the sensor data that are used for object recognition or classification. There remains a need for further developments to wireless communication systems configured for sensing. 15 Summary The scope of protection sought for various embodiments of the invention is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the 20 invention. According to a first aspect, there is described an apparatus comprising at least one processor; and at least one memory storing instructions for a sensing management function, wherein execution of the instructions causes the apparatus to perform at 25 least: receiving, from a sensing client of a wireless communication system, a sensing service request for a sensing service provided by the sensing management function, wherein the sensing service request comprises a requested quality of service for the sensing sendee; determining, a sensing configuration for a sensing session for the sensing sendee based at least on the requested quality of sendee for the sensing sendee; 30 based on the sensing configuration, configuring a sensing system comprising at least one radio access network node and / or at least one user equipment to perform sensing; determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user equipment; and notifying the sensing client, 35 based on the determination that the quality of service of the sensing session for the sensing sendee does not meet the requested quality of sendee. In some embodiments, the sensing sendee request may further comprise at least one threshold for the quality of service. 5 In some embodiments, determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service may comprise determining whether the at least one threshold for the quality of service of the sensing session is met or not met. 10 In some embodiments, execution of the instructions by the at least one processor may further cause the apparatus to perform sending, to the sensing client, a notification that indicates that quality of service of the sensing session has changed based on a determination that the quality of service of the sensing session has changed. 15 In some embodiments, the notification may comprise a measured, computed, or predicted quality of service value for the quality of service of the sensing session. In some embodiments, the notification may comprise an indication that the at least one threshold for the quality of service is met or not met. 20 In some embodiments, execution of the instructions may further cause the apparatus to perform upon determining that the at least one threshold for the quality of service is met or not met, sending, to the sensing client, the notification. 25 In some embodiments, the sensing service request may further comprise an indication whether the notification should be sent to the sensing client, and optionally at least one configuration parameter for triggering sending the notification. In some embodiments, the quality of service comprises a required accuracy for sensing 30 an object, and the required accuracy comprises at least one of an estimate of a position of an object to be sensed, an estimate of a velocity of an object to be sensed, an orientation of an object to be sensed, a range of an object to be sensed and an angular position of an object to be sensed. 35 In some embodiments, the quality of service comprises at least one of the following features of an object a sensing resolution of the sensing system comprising at least one of range resolution, velocity resolution, angular resolution, a maximum sensing range of the sensing system, a maximum sensing velocity range of the sensing system, maximum sensing service latency of the sensing system, a refresh rate of the sensing system and a sensing duration of the sensing system. 5 In some embodiments, execution of the instructions may further cause the apparatus to perform adapting at least one feature of radio access network node and / or user equipment such that the at least one threshold for the quality of service is met or not. 10 In some embodiments, determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user equipment may comprise comparing sensing radio signals received from the at least one radio access network node and / or the least one user equipment to information regarding known 15 sensing data in a sensing area obtained from an object repository. In some embodiments, determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user equipment may 20 comprise comparing a sensing output to information regarding known sensing objects in a sensing area obtained from an object repository. In some embodiments, determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data 25 received from the at least one radio access network node and / or user equipment may comprise comparing the transmission and / or reception of radio signals used for sensing from the at least one radio access network node and / or the least one user equipment to a second set of transmission and / or reception of radio signals used for sensing from another sensing client. 30 In some embodiments, determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user equipment may comprise comparing the transmission and / or reception of radio signals used for 35 sensing from the at least one radio access network node and / or the least one user equipment to a third set of transmission and / or reception of radio signals used for sensing from a dedicated sensing device. In some embodiments, the dedicated sensing device may comprise at least one of: a 5 3GPP compliant sensor device, a non-3GPP compliant sensor device, a light detection and ranging system (LiDAR), and / or a radio detection and ranging system (RADAR). In some embodiments, execution of the instructions further causes the apparatus to perform analysing at least one sensing error of the radio access network node and / or 10 the user equipment to determine at least one quality of service of the sensing sendee. According to a second aspect, there is described an apparatus comprising: at least one processor; and at least one memory storing instructions, wherein execution of the instructions causes the apparatus to perform: determining, at a sensing client of a 15 wireless communication system, a requested quality of service for a sensing client and transmitting, from the sensing client of the wireless communication system to a sensing management function of a wireless communication system, a sensing service request for a sensing service to be provided by the sensing management function, wherein the sensing service request comprises a requested quality of service for the sensing service. 20 In some embodiments, the sensing service request may further comprise at least one threshold for the quality of service. In some embodiments, execution of the instructions further causes the apparatus to 25 perform receiving, from the sensing management function, a notification that indicates that quality of service of the sensing session has changed based on a determination that the quality of service of the sensing session has changed. In some embodiments, the notification may comprise a measured, computed, or 30 predicted quality of service value for the quality of service of the sensing session. In some embodiments, the notification may comprise an indication that the at least one threshold for the quality of service is met or not met. In some embodiments, the sensing sendee request may further comprise an indication whether the notification should be sent to the sensing client, and optionally at least one configuration parameter for triggering sending the notification. 5 In some embodiments, the quality of service may comprise a required accuracy for sensing an object, wherein the required accuracy comprises at least one of: an estimate of a position of an object to be sensed; an estimate of a velocity of an object to be sensed; n orientation of an object to be sensed; a range of an object to be sensed and an angular position of an object to be sensed. 10 According to a third aspect, there is described a method comprising: receiving, from a sensing client of a wireless communication system, a sensing service request for a sensing service provided by a sensing management function, wherein the sensing sendee request comprises a requested quality of service for the sensing service; 15 determining, a sensing configuration for a sensing session for the sensing service based at least on the requested quality of sendee for the sensing sendee; based on the sensing configuration, configuring a sensing system comprising at least one radio access network node and / or user equipment to perform sensing; determining whether a quality of service of the sensing session for the sensing service meets the requested 20 quality of service based on sensing data received from the at least one radio access network node and / or user equipment; and notifying the sensing client, based on the determination that the quality of sendee of the sensing session for the sensing service does not meet the requested quality of service. 25 According to a fourth aspect, there is described a method comprising: determining, at a sensing client of a wireless communication system, a requested quality of service for a sensing client and transmitting, from the sensing client of the wireless communication system to a sensing management function of a w ireless communication system, a sensing sendee request for a sensing service to be provided by the sensing management 30 function, wherein the sensing sendee request comprises a requested quality of sendee for the sensing sendee. According to a fifth aspect, there is provided a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the 35 apparatus to carry out the method of any preceding method definition. According to a sixth aspect, there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing a method, comprising: receiving, from a sensing client of a wireless communication system, a sensing service request for a sensing service provided by a sensing management 5 function, wherein the sensing service request comprises a requested quality of service for the sensing service; determining, a sensing configuration for a sensing session for the sensing service based at least on the requested quality of service for the sensing service; based on the sensing configuration, configuring a sensing system comprising at least one radio access network node and / or user equipment to perform sensing; 10 determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user equipment; and notifying the sensing client, based on the determination that the quality of service of the sensing session for the sensing service does not meet the requested quality of service. 15 According to a seventh aspect, there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing a method, comprising: determining, at a sensing client of a wireless communication system, a requested quality of service for a sensing client and transmitting, from the sensing 20 client of the wireless communication system to a sensing management function of a wireless communication system, a sensing service request for a sensing service to be provided by the sensing management function, wherein the sensing service request comprises a requested quality of service for the sensing service. 25  Brief description of the drawings Example embodiments will now be described, by way of non-limiting examples, with reference to the following schematic drawings, in which: FIG. 1 is a block diagram showing a monostatic sensing system in accordance with an 30 example embodiment; FIG. 2 is a block diagram showing a bistatic sensing system in accordance with an example embodiment; FIG. 3 is a block diagram showing a system in accordance with an example embodiment; 35 FIGS. 4 to 6 are flowcharts showing methods or processes in accordance with example embodiments; FIGS. 7 to 10 show message and operations for procedures in accordance with example embodiments; FIG. 11 is a schematic diagram of components of one or more of the example embodiments described previously; and 5 FIG. 12 shows tangible media for storing computer-readable code which when run by a computer may perform methods according to example embodiments described herein. Detailed description The scope of protection sought for various embodiments of the invention is set out by io the independent claims. The embodiments and features, if any, described in the specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention. 15 In the description and drawings, like reference numerals refer to like elements throughout. The present specification relates to sensing in a wireless communication system, for example to obtain awareness of a scene that surrounds radio access network entities 20 and / or user equipment that are configured as sensing devices. This may, for example, include the capability to perform one or more of the following: • Detection, localization and / or tracking of objects; • Forming images of a specific scene or environment; and / or • Identifying features of discovered objects for recognition and / or classification, etc. 25 A wireless communication system in which sensing and communication are integrated, is generally referred to as an integrated sensing and communication system. An integrated sensing and communication (ISAC) system as described herein may potentially achieve both relatively high-data rate communications and relatively high-30 resolution object detection using at least some of the same hardware and spectrum resources. This may be advantageous, for example, in improving sensing accuracy for scenarios or situations where existing sensing techniques may not perform well (e.g. non-line-of-sight (NLOS) conditions, requirement for high velocity resolution etc), to enhance spectrum efficiency by sharing communication and sensing spectrum band, 35 and / or to reduce hardware cost by combining sensing and communication equipment / hardware. Example scenarios in which an integrated sensing and communication (ISAC) system could be used include (but are not limited to) the following: • Intrusion detection (e.g., intruder detection in a smart home, pedestrian or animal 5 intrusion detection on a highway etc.) • Support for autonomous driving (e.g., sensing assisted automotive manoeuvring and navigation by providing additional information for detected objects on the roads such as pedestrians, bicycles, other vehicles etc, sensing for parking space determination etc.) 10 • Support for unmanned aerial vehicle (UAV) flight (e.g., UAV flight trajectory tracing, network assisted sensing to avoid UAV collision by providing information for detected objects on the air especially those that may not have communication means to indicate their presence) • Support for automated guided vehicle (AGV) or autonomous mobile robots (AMR) 15 in factories (e.g., AGV detection and tracking in factories), AMR collision avoidance in smart factories etc.) • Environment and / or weather monitoring (e.g., rain, pollution, flooding) • Health monitoring (e.g., fall detection, contactless sleep monitoring service) • Extended reality (XR) applications. 20 FIG. 1 is a block diagram showing a monostatic sensing system for a wireless communication system, indicated generally by the reference numeral 10, in accordance with an example embodiment. The monostatic sensing system 10 comprises a first radio access network entity 14 (a gNB in the example shown). The first radio access 25 network entity 14 sends out (e.g., transmits) sensing signals (e.g., RF signals) when the first radio access network entity 14 is configured for a sensing operation (e.g., a monostatic sensing operation). Therefore, the first radio access network entity 14, when configured for a monostatic sensing operation is considered to be acting as (or configured to be) a sensing transmitter. The first radio access network entity 14 also 30 receives sensing signals (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects (e.g., object 12) in a vicinity of the first radio access network entity 14 when the first radio access network entity 14 is configured for a sensing operation (e.g., a monostatic sensing operation). Therefore, the first radio access network entity 14, when configured for a monostatic sensing operation is also 35 considered to be acting as (or configured to be) a sensing receiver. Although FIG. 1 shows a monostatic sensing system for a wireless communication system that includes a radio access network entity configured for a monostatic sensing operation, in some embodiments, the monostatic sensing system may include a user equipment configured for a monostatic sensing operation that is considered to be acting as (or configured to be both a sensing transmitter and a sensing receiver. 5 FIG. 2 is a block diagram showing a bistatic sensing system for a wireless communication system, indicated generally by the reference numeral 20, in accordance w ith an example embodiment. The sensing system 20 comprises a first radio access network entity 24 (a gNB in the example shown) and a second radio access network 10 node 26 (also a gNB in the example shown). The first radio access entity 24 sends out sensing signals (e.g., radio signals), when configured for a sensing operation (e.g., a bistatic sensing operation). Therefore, the first radio access network entity 26, when configured for a bistatic sensing operation, is thereby configured to be or is considered to be acting as a sensing transmitter). The second radio access network entity 26 15 receives sensing signals deflected, reflected or refracted by objects (e.g., object 22) located in a vicinity of the second radio access network entity 26 when the second radio access network entity is configured for a sensing operation (e.g., a bistatic sensing operation). Therefore, the second radio access network entity 26 is configured to be or is considered to be acting as a sensing receiver) when the second radio access network 20 entity 26 is configured for a bistatic sensing operation. In the sensing system 10, the first radio access network entity 24 receives sensing signals (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects (such as object 12). Similarly, in the sensing system 20, the second radio access 25 network entity 26 receives sensing signals. In the sensing systems 10 and 20, sensing measurement data (or sensing data / sensing measurement information) include data derived from sensing signals (e.g., radio signals) impacted (e.g. reflected, refracted, diffracted) by an object in an environment of interest when performing a sensing operation (e.g. the objects 12 or 22), and optionally processed (e.g. by a network 30 function within a wireless communication system, such as a 5G and / or 6G system, a server external to the wireless communication system, application server connected to the wireless communication system via, for example, a network exposure function of the wireless communication system, edge server (e.g., a server located near the wireless communication server), etc.). While sensing output(s) includes processed sensing data 35 e.g., requested by a sensing service consumer (or sensing service client) of a sensing service provided by the 5G and / or 6G system that includes the sensing system 10 and / or the sensing system 20. Examples of sensing data or sensing measurement information comprise one or more of information about received or arrived electromagnetic signals. Information about a 5 received or arrived electromagnetic signal may include a received power, delay, angle of departure, angle of arrival, doppler shift, and / or the like of the received or arrived electromagnetic signal. 10 The systems 10 and 20 therefore differ in that in the monostatic sensing system 10, the first radio access node 14 is configured to be or to act as both the sensing transmitter and the sensing receiver and in the bistatic sensing system 20, different radio access network entities are configured to be or to act as sensing transmitters and receivers. Note also that the bistatic sensing system 20 is a special case of a multi-static sensing 15 system in which one radio access network entity is configured to be or to act as a sensing transmitter and a plurality of radio access network entities are configured to be or act as sensing receivers. In the monostatic sensing system 10 and the bistatic sensing system 20, the sensing 20 transmitters and receivers are both radio access network entities (e.g., BSs, gNBs); however, this is not essential to all example embodiments. For example, in some example embodiments, the bistatic sensing system 20 shown in Figure 2 may comprise a UE and a radio access entity, such as the first radio access entity 24 and / or second radio access entity 26. In such example embodiments, a UE may send sensing signal 25 (e.g., radio signals) and a radio access network entity (e.g., the first radio access entity 24 and / or the second radio access entity7 26) may receive signals (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects (such as object 12). Alternatively, a radio access network entity7 (e.g., the first radio access entity 24 and / or the second radio access entity 26) may send sensing signal (e.g., radio signals) and the 30 UE may receive signals (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects (such as object 12). Sensing operations for a sensing session performed by radio access network entities 35 (and / or UEs) as described herein can be used in the context of a Public Land Mobile Network (PLMN) comprising a communication system comprising radio access network nodes as well as in the context of a Standalone Non-Public Network (SNPM) comprising a communication system comprising radio access network nodes. FIG. 3 is a block diagram showing a wireless communication system, indicated 5 generally by the reference numeral 30, in accordance with an example embodiment which supports or provides sensing services. The wireless communication system 30 comprises a sensing management module 32 that implements or comprises a sensing management function (SeMF) for providing sensing services to a sensing service client 34, and one or more entities 36 such as a radio access network (generally referred to as 10 a RAN entity 36 and collectively as RAN entities 36). As discussed further below, the sensing client 34 may be a user device (e.g., a UE), an application function (AF) or a network exposure function (NEF) of the wireless communication system (e.g., a 5G or similar system). 15 The sensing management module 32 is provided to configure, coordinate and enable the one or more entities 36 for a sensing operation. The sensing management module 32 maybe, may implement, or may comprise a Sensing Management Function (SeMF) as discussed in detail below. 20 As used herein, the term “sensing management module” refers to a combination hardware processing circuit and software and / or firmware comprising machine-readable instructions that are executable by the hardware processing circuit, or software comprising machine-readable instructions that are executable by a hardware processing circuit of an apparatus. A hardware processing circuit includes at least one 25 processor comprising machine-readable instructions that are executable by the hardware processing circuit and at least one memory storing the machine-readable instructions. A processor may include any or some combination of an accelerator, microprocessor, a core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, a digital signal processor, 30 a central processing unit, a graphic processing unit, a tensor processing unit. Memory may include any or some combination of volatile or non-volatile memory (e.g., a flash memory, cache, a random-access memory (RAM), and / or a read-only memory (ROM)). The memory 112 may store the machine-executable instructions of the software and / or firmware for execution by the at least one processor of the hardware processing circuit. 35 The software and / or firmware may implement or comprise the SeMF, and the machine-executable instructions may be executed by the hardware processing circuit to perform the actions or operations of the methods of the SeMF described herein. The SeMF implemented or comprised in the sensing management module 32 may receive, from the sensing client 34, sensing requests for different types of sensing 5 services provided by the SeMF, determine a sensing method to be performed (e.g. whether a monostatic or multistatic (e.g. bistatic) sensing is to be used), determine one or more RAN entities 36 to be involved in a sensing operation based on the sensing method that is determined, and the sensing roles of the respective RAN entities. For example, for each of the one or more RAN entities, the SeMF implemented or 10 comprised in the sensing management module 32 may determine sensing configurations including: sensing resources configurations; sensing session configurations (e.g., RAN entity that transmits sensing signals (sensing transmitter (Tx role) and / or RAN entity (or RAN entities) that receive the respective sensing signals (sensing receiver (Rx) role)); and sensing data reporting configurations. 15 The SeMF implemented or comprised in the sensing management module 32 interacts with the one or more RAN entities 36 and transmits to the one or more RAN entities 36 (e.g., during a sensing session establishment process to establish a session for the sensing service, generally referred to herein as a sensing session) the determined 20 sensing configurations. The SeMF maybe configured to determine or calculate the sensing output as requested. A sensing output may comprise processed sensing data e.g., as requested by a sensing sendee client (e.g., the sensing client 34). For example, the processed sensing data may 25 be sensing data that has been processed by the SeMF. The processed sensing data may include data about the objects in an area and / or data about features or data about those objects. For example, one or more of the location, speed, velocity , shape, material, and / or dimensions of the object maybe data about the objects in an area. The SeMF may alternatively or additionally be configured to provide the sensing data received or 30 collected from one or more sensing devices as a sensing output. The SeMF may provide to the sensing service client sensing data if the sensing data has been requested by the sensing service client. The sensing service client 34 may be for example: • an application function (e.g., trusted to the Public Land Mobile Network (PLMN)) and the request may be received directly from the sensing sendee client. • an application function and the request received from the sensing service client via a network exposure function. 5 • a user equipment. • another network entity, such as a RAN node and / or network function of a wireless communication system, such as a network function of a core network of a wireless communication system. 10 A RAN entity 36 may be, for example, a base station (e.g., an evolved NodeB (eNB) or gNB), or another entity with at least some of the sensing functionalities (i.e. the sensing functionalities may include at least one of the following: provide sensing and / or positioning measurements, transmit the signals for sensing and / or positioning) and could be a new network node (e.g., dedicated for sensing purposes, sensing unit) or part 15 of an existing network node (e.g., Positioning Reference Unit, Reconfigurable Intelligent Surfaces). A RAN entity may validate and realize the sensing configurations received from the sensing management module 32. A RAN entity 36 may also conduct sensing admission control on sensing resources for transmitting (Tx) and / or receiving (Rx) sensing signal(s) and updating and / or selecting the sensing configuration of the 20 RAN entity 36, which is then provided to the sensing management module 32 and / or to other RAN entities (e.g., via an Xn interface). Any RAN entity 36 operating as a sensing receiver may then obtain sensing data and provide that sensing data to the sensing management module 32 (with or without processing the sensing data), according to the sensing data reporting configurations for processing the sensing data to derive sensing 25 outputs. As discussed above, the sensing management module 32 may be, may implement, or may comprise a Sensing Management Function (SeMF). The sensing management module may be provided or included in a communication system, such as 5GS. The 30 SeMF may be a dedicated network function for the core network of the communication system (e.g., a network function for the 5GC (5G core network of the 5GS) or a dedicated network function for one or more RAN entities 36. In some embodiments, the SeMF (e.g., functionality of the SeMF) maybe integrated into an existing network function for a wireless communication system (e.g., an existing network function for the 5GS or for the 5GC of the 5GS), such as a location management function (LMF) which provides location services for locating user equipment in a 5GS. In some embodiments, the functionalities of the SeMF may be distributed across a plurality of different network functions of the core network (e.g., NEF, LMF, GMLC, AMF) or may be integrated into one or more RAN entities 36). In an example implementation, the SeMF may: • Determine a sensing method (e.g., monostatic sensing, bistatic sensing, or mutli-static sensing) and determine a sensing configuration for the RAN entities (e.gBSs, such as gNBs) and / or UEs identified or selected to be involved in a sensing session for the determined sensing method taking into consideration a) the requirements included in a sensing service request received from the sensing serving client 34 (e.g. sensing area for the sensing service, QoS requirements for the sensing service) and b) the static and / or dynamic sensing capabilities of RAN entities and / or UEs. In the case the determined sensing method is monostatic sensing, the SeMF may identify or select one or more RAN entities and / or UEs to be involved in and determine or generate a sensing configuration for the one or more RAN entities and / or UEs for configuring the one or more RAN entities and / or UEs, respectively, as a sensing transmitter (Tx) and a sensing receive (Rx) based on the determined sensing method, and provide the sensing configurations to the one or more RAN entities and / or UEs. Alternatively, in the case of bistatic sensing and / or multi-static sensing is determined, identify or select one RAN entity and / or UE to be a sensing transmitter and one or more other RAN entities (e.g., BSs) an / or UEs to be sensing receivers and determine or identify a sensing configuration for configuring the one RAN entity and / or UE to be a sensing transmitter and sensing configurations for configuring the one or more other RAN entities (e.g., BSs) and / or UEs to be a sensing receiver. • Execute sensing admission control, which identifies whether the identified or selected RAN entities and / or UEs have the available sensing resources for the requested sensing sendee (e.g., sensing requirements) and determine a sensing resources configuration for the identified or selected RAN entities and / or UEs. The sensing resources configuration may include reference signals and / or pilots and / or user data and control plane resources, depending on the approach or scheme that a selected monostatic, bistatic or multi-static method realizes. • Transmit a sensing session establishment request to the one or more RAN entities and / or UEs to establish a sensing session, according to the selected sensing method (monostatic, bistatic or multi-static sensing), including one or more of the following: a sensing configuration for each respective selected RAN entity and / or UE for configuring the respective entity as a sensing transmitter and / or sensing receiver ; sensing resources configuration; sensing session configuration; sensing data reporting configuration i.e. whether control plane-based reporting or user plane (e.g. to or via dedicated server) will be used to transfer the sensing measurements (sensing data) from the RAN entity (e.g., BS) and / or the UE to SeMF, resources and configurations used for reporting; one or more identifiers of sensing sessions. Each identifier of a sensing session identifies the sensing session and is generally referred to as sensing session identifier and collectively referred to as sensing session identifiers). • Generate and allocate to the one or more RAN entities and / or UEs involved in the selected sensing session for the determined sensing method a sensing session identifier (ID) used to uniquely identify and coordinate sensing operations among different RAN entities and / or UEs as well as for transmitting sensing measurements and / or sensing data from the RAN entity' (or RAN entities) and / or from the one or more UEs to the SeMF, that belong to the same sensing session. In the context of the same sensing session, one or more mono-static sensing operations or one or more multi-static sensing operations can be initiated. Also, the same RAN entity and / or UE can be involved at one or more mono-static sensing operations and at one or more multi-static sensing operations. In addition, a RAN entity and / or a UE can identified or selected to be a sensing transmitter and can be configured based on the sensing configuration to transmit sensing signals and / or identified or selected to be sensing receiver and can be configured to based on a sensing configuration to receiver sensing signals. Each of the one or more RAN entities 36 and / or UEs of the wireless communication system 30 may be a base Station (BS) or some other entity with sensing capabilities (e.g., dedicated units or elements to receive sensing signals, Reconfigurable Intelligent Surfaces with integrated sensing capabilities or used to aid in ISAC). Each RAN entity 36 may: • Transmit a response to a sensing session establishment request to the SeMF. The response to the sensing session establishment request comprises an indication of acceptance (success) or failure to provide and / or support and / or establish the sensing session. The response to the sensing session establishment request may also include a cause code indicating a cause of the failure to provide and / or support and / or establish the sensing session. • Configure itself after establishment of the sensing session according to the received sensing resources configuration and sensing session configuration and cause the respective RAN entities to perform a sensing operation. • When involved in a sensing session (e.g., identified by a sensing session ID) and 5 configured to be or as a sensing receiver, transmit to the SeMF the respective sensing data (e.g., measurements obtained when the RAN entity is performing a sensing operation). • Optionally conduct sensing admission control and determine the sensing resources for transmitting or receiving sensing signals based on the sensing resources 10 configuration received from the SeMF. A UE may: • Transmit a response to a sensing session establishment request to the SeMF. The response to the sensing session establishment request comprises an indication of 15 acceptance (success) or failure to provide and / or support and / or establish the sensing session. The response to the sensing session establishment request may also include a cause code indicating a cause of the failure to provide and / or support and / or establish the sensing session. • Configure itself after establishment of the sensing session according to the received 20 sensing resources configuration and sensing session configuration and cause the respective UE to perform a sensing operation. • When involved in a sensing session (e.g., identified by a sensing session ID) and configured to be or as a sensing receiver, transmit to the SeMF the respective sensing data (e.g., measurements obtained when the UE entity is performing a 25 sensing operation). The sensing data from RAN entity or a UE can transmitted to the SeMF or to another network entity or AF, if the SeMF is not configured for processing the sensing data (e.g., functionality for processing sensing data is not collocated with the SeMF). 30 The interaction between the SeMF and the RAN entity(-ies) and / or the UE(s) can happen through direct interface (e.g., in case that RAN entities and core network have a Service based architecture) or though the AMF. The AMF may route the messages between a RAN entity (e.g., an access node) and the SeMF transparently, over an 35 interface (e.g., over an NG-C interface) using a non-UE associated mode. The Next Generation Application Protocol (NGAP) protocol, terminated between the AMF and the RAN entity (e.g.. a NG-RAN node), may be used as a transport protocol for transporting sensing protocol messages over the NG-C interface. In some embodiments, admission control may be performed by a RAN entity (e.g., BS). The SeMF may provide to the RAN entity" (e.g., BS) information such as a QoS for the requested sensing session, an indication of a type of sensing service that is requested, sensing requirements for the sensing session (e.g., sensing area, sensing duration, sensing update rate etc.) that can allow the one or more RAN entities (e.g., BSs) to determine the required resources for the sensing session. The RAN entity (e.g., BS) configured to be or as a sensing transmitter (e.g., having a sensing transmitting role (e.g. when the SeMF selects the RAN entity to be involved in a bi-static sensing method) can provide its sensing resource configuration (e.g. sensing signal frequency, bandwidth, the timing when a sensing signal is transmitted by the RAN entity (e.g., BS)) and / or the sensing session configuration to: one or more RAN entities (e.g., BSs) configured to be or as sensing receiver (e.g., having a sensing receive role) for the respective sensing session e.g. via the Xn interface (inter-RAN entity); or the SeMF e.g. via the NG interface or; the AMF e.g. using similar mechanism as the Remote interference management (RIM) Information Transfer. Different clients of a sensing service have different sensing quality" of service (QoS) requirements for the sensing service, while different sensing QoS parameters may be important for different clients of a sensing service (for instance the sensing accuracy may be important for such as Automated Guided Vehicles (AGVs) collision avoidance systems, while sensing service latency may be important for Intruder detection in a highway etc). The sensing QoS parameters relate to key performance indicators, such as sensing accuracy, sensing resolution, sensing latency, and sensing QoS requirements relate to the required value of a sensing QoS parameter (e.g., positioning accuracy of 2 meters, a maximum sensing range of 50 meters, sensing sendee latency of looms). For several clients of a sensing service (e.g., safety relevant, vehicular, drones) it is important to receive an accurate and reliable sensing QoS (e.g., a QoS for a sensing service) from SeMF as well as notifications on the achieved or expected sensing QoS. Hence, the achieved Sensing QoS or the expected to be achieved sensing QoS needs to be determined for a wireless communication system. The disclosure herein provides how a sensing client (e.g., UE or AF) can request and configure sensing QoS parameters of a sensing sendee. FIG. 4 is a flowchart showing a method or process indicated generally by the reference 5 numeral 40, in accordance with an example embodiment. The method or process 40 may be performed by the SeMF implemented or comprised in the sensing management module 32 described above. Although the method or process 40 is described below as being performed by the SeMF, it will be appreciated that the method or process 40 may also be performed by any network function of a wireless communication system that 10 includes the functionality of the SeMF, such as the LMF. At step 42, the SeMF receives, from a sensing client of a wireless communication system, a sensing service request for a sensing service provided by SeMF. The sensing sendee request may comprise a requested quality of service (QoS) for the sensing 15 service. The requested quality of sendee (QoS) for the sensing sendee may comprise a required accuracy for sensing an object. The required accuracy for sensing an object is a measurement of the accuracy of the sensing system. By way of example, the required 20 accuracy for sensing an object comprises at least one or a combination of following: An estimate of a position of an object to be sensed; An estimate of a velocity7 of an object to be sensed; An orientation of an object to be sensed; 25 - A range of an object to be sensed; An angular position of an object to be sensed; In addition to the required accuracy for sensing an object, the requested quality of service (QoS) for the sensing sendee may also comprise at least one or a combination of 30 following: A maximum sensing range of the sensing system; A maximum sensing velocity range of the r sensing system; A maximum sensing service latency; A refresh rate of the sensing system; 35 A sensing duration of the sensing session. A sensing resolution of a sensing system. The sensing resolution may comprise at least one of range resolution, velocity resolution, angular resolution. The sensing system may include at least one UE and / or at least one radio access node 5 but can include other entities of such as the AMF. At step 44, the SeMF determines a sensing configuration for a sensing session of the sensing service based at least on the requested quality of service (QoS) for the sensing service. io At step 46, the SeMF configures a sensing system based on the sensing configuration determined at step 44. The sensing system comprises at least one radio access network entity and / or user equipment and the SeMF configures the sensing system by sending to the at least one radio access network entity and / or UE of the sensing system, the 15 sensing configuration, and each of the at least one radio access network entity configures itself for performing sensing (e.g., a sensing operation) using the sensing configuration. At step 48, the SeMF determines whether the achieved (or measured, or monitored) 20 quality of service of the sensing session for the sensing service meets the requested quality of service for the sensing service included in the sensing request sent by the sensing client. The determination (or the monitoring or the measurement) of the achieved sensing quality of service for a sensing session is conducted based on sensing data received from the at least one radio access network node and / or user equipment 25 and / or the information received from a sensing device and / or the information received from another sensing client and / or information retrieved from Sensing Data Repository (e.g., a repository7 storing sensing data or sensing measurements) and / or information retrieved from Objects Repository. 30 At step 49, the SeMF notifies the sensing client, based on the determination that the quality of service of the sensing session for the sensing service does not meet the requested quality of service. The sensing service request may optionally comprise at least one threshold for the 35 requested quality of service. If the sensing service request comprises at least one threshold for the requested quality of service, then the method 40 may further comprise determining whether the at least one threshold for the requested quality of service is met or not met for the sensing session for the requested sensing service. FIG. 5 is a flowchart show ing a method or process indicated generally by the reference 5 numeral 50, in accordance with an example embodiment. The method or process 50 may be performed by the SeMF implemented or comprised in the sensing management module 32 described above. Steps 52 to 58 of method 50 correspond to the steps 42 to 48 as mentioned above in relation to FIG.4. Additionally, at step 59 the method 50 comprises transmitting, to the sensing client, a notification that indicates the quality of 10 service of the sensing session has based on a determination that the quality of sendee of the sensing session has changed. Although the method or process 50 is described below as being performed by the SeMF, it will be appreciated that the method or process 50 may also be performed by any network function of a wireless communication system that includes the functionality of the SeMF, such as an LMF. 15 The notification that indicates a change of the quality of sendee of the sensing session for the requested sensing sendee may include a measured quality of service value (e.g., a known value of quality of sendee for the sensing session) or a computed or predicted quality of service value for the quality of service of the sensing session (e.g., predicted 20 value of a quality of service for the sensing session). The known quality of service value may be calculated, computed, or measured by the SeMF. Furthermore, the notification that indicates a change of the quality of service for the sensing session may include a known or predicted indication that the sensing quality of sendee threshold is met or not met. In some embodiments, a threshold for the requested quality of service (generally 25 referred to as a quality of service threshold) is a value of a sensing QoS parameter that may be exceeded or not and will trigger (e.g., cause) the transmission of the notification by the SeMF. A sensing QoS threshold may include, for example, deviation larger than 20cm of the objects’ position calculated or computed by the SeMF, a deviation of 2 m / s or larger in objects’ velocity calculated or computed by the SeMF, a sensing range less 30 than 20 meters, a sensing sendee latency larger than 100 ms. The notification that indicates a change of the quality of service of the sensing session for the requested sensing service may also include an alternative sensing quality of service that could be supported based a known or a predicted value of a quality of 35 service parameter. For instance, objects’ position accuracy of 1 meter can be supported (i.e. or achieved or provided) by the sensing system instead of 0.5 meters that could be supported (i.e., or achieved or provided) before the notification was sent or at a previous moment or even that has been requested by the sensing client. Another example could be that object’s resolution of 2 meters can be provided by the sensing system instead of 1 meter before the notification or at a previous moment or even that 5 has been requested by the sensing client. The sensing service request may further comprise one or more values or levels of the requested quality of service for at least one sensing QoS parameter of the sensing service. For instance, the requested quality- of service for the sensing service may 10 comprise a required accuracy of 0.5 meter and also a second option of a required accuracy of 1 meter for sensing an object. In such a case the SeMF can select the best accuracy that can be achieved at the specific moment (i.e., of the request or during the operation of the sensing service) and in the notification to the sensing client can indicate which one can be supported (i.e., or achieved, or provided) from the one or 15 more requested values for the respective sensing QoS parameter. The sensing service request may further comprise an indication whether the notification that indicates a change of the quality of service for the sensing session should be sent to the sensing client. In some embodiments, the notification that 20 indicates a change of the quality of service of the sensing session for the requested sensing service may include at least one configuration parameter for triggering sending of the notification. ‘Triggering’ sending of a notification is herein defined as the SeMF deciding to send the notification to the sensing client. 25 The methods 40 and 50 may also include adapting at least one feature of the sensing system (e.g., any aspect of the determined sensing configuration such as the amount of resources allocated for sensing, the selected RAN entities for the sensing operation, the selected UEs for the sensing operation, the transmission power for the transmission of sensing signals), such as the transmission power for transmission of radio signals by 30 the selected radio access network entities and / or UEs, such that the at least one threshold for the quality of service is met or not. In other words, in response to a determination that the at least one threshold for the requested quality of service is not met, the SeMF may decide to adapt the sensing features in order to improve the quality of service. FIG. 6 is a flowchart showing a method or process indicated generally by the reference numeral 60, in accordance with an example embodiment. The method or process 60 may be performed by the sensing client 34 described above. 5 Step 62 of the method 60 comprises transmitting, from a sensing client 34 of a wireless communication system to the sensing management function 32 of the wireless communication system, the sensing service request for the sensing service to be provided by the sensing management function. The sensing service request comprises a requested quality of service for the sensing service. Optionally, in response to the 10 request, at step 64, the sensing client 34 may receive a notification of the measured or estimated quality of service of a sensing session for the requested sensing service. The notification may be sent by the sensing management function 32 to the sensing client 34 when the quality of service for the sensing session changes. In other words, the sensing client 34 may receive a notification that indicates a change of the quality of 15 service for the requested sensing session. As previously discussed, the sensing service request may comprise the at least one threshold for the requested quality of service (e.g., the maximum sensing range, the sensing service latency, the accuracy of the position of the sensing objects, the 20 resolution of the sensing range, the resolution of the velocity of the objects), which may have been determined by the sensing client 34. The sensing service request further comprises an indication whether a notification that indicates a change of the quality of service for the sensing session should be sent to the 25 sensing client. In some embodiments, the sensing service request includes at least one configuration parameter for triggering sending of the notification that indicates a change of the quality of service for the sensing session. A method or process 60 may also include comparing sensing radio signals received 30 from at least one radio access network entity and / or UE to an object repository. The method or process 60 may also include comparing a sensing output to sensing objects or known sensing data stored in an object repository, wherein the object repository comprises information regarding known sensing objects in a sensing area and / or information regarding known sensing data in a sensing area. An example of a 35 procedure that includes comparing a sensing output to an object repository is described in FIG. 7. FIG. 7 shows a procedure for monitoring QoS of a sensing session for a requested sensing sendee and for sending notifications that indicate the QoS of the sensing session for a requested sensing sendee has changed using information retrieved from 5 an object repository storing sensing data and / or sensed objects. The information stored in the object repository may be sensing data received from previous sensing procedures that include sensing measurement derived from sensing signals (e.g., radio signals) which have been impacted (e.g., reflected, refracted, diffracted) by objects in the environment of interest. The information stored in the object repository may comprise io identifiers that identify objects that have detected from previous sensing procedures in the environment of interest and information about the objects (e.g., position, size, shape, speed). The procedure 70 shows messages (e.g., signalling) being sent between a UE 71, one or more RAN entities (e.g., base stations (BS) 72), an Access and Mobility Management 15 Function (AMF) 73, a repository 74, a Sensing Management Function (SeMF) 75, a location management function (LMF) 76 of a 5G wireless communication system and a sensing client (e.g., another UE or AF) 77. At Step 1 of the procedure 70, sensing client 77, e.g., UE or AF, sends a sensing service 20 request (e.g., a request for a sensing sendee provided by the SeMF) to the SeMF of the 5GC. The AF, for example, sends a sensing service request either directly to SeMF 75 or via an NEF of the 5GC. The sensing sendee request may include QoS requirements for the requested sensing service, a Sensing QoS, Sensing type, Sensing Requirements (e.g., Sensing Area). The QoS requirements included in the request may include the 25 following: • Sensing QoS Notification Indication to indicate for which QoS parameters a notification is needed (e.g., accuracy of objects position, range resolution, sensing service latency etc.). • Sensing QoS Notification thresholds (e.g., error and / or deviation larger than 20cm 30 of the objects’ position calculated by the SeMF and / or deviation of 2 m / s or larger in objects’ velocity calculated or computed by the SeMF, sensing range less than 20 meters, sensing service latency larger than 100 ms) • Time interval that the Sensing QoS notification thresholds should be met (or not) e.g., 1000 ms, so as to trigger the sending of a notification that the sensing QoS 35 (e.g., the QoS of a sensing session for the requested sensing service) has changed. • Recipient of the notification that QoS of a sensing session (e.g., sensing QoS) has changed (e.g., address or identifier of a UE or an address or identifier of an Application Function). • Sensing QoS requirements and / or sensing QoS parameters that will be included 5 sensing service request and used by the SeMF to generate a sensing configuration for a sensing system that is used to configure the sensing system. Examples of such sensing QoS requirements and / or sensing QoS parameters may include the following: Guaranteed or Non-Guaranteed Sensing QoS (applicable to one or more QoS 10 Parameters) Accuracy of: o Positioning estimate (m): Horizontal and Vertical o Velocity estimate (m / s): Horizontal and Vertical o Orientation (rad) 15 0 Range (m) 0 Angular (rad) Sensing Resolution 0 Range resolution (m) 0 Velocity resolution (m / s) 20 0 Angular (rad) Max Sensing Range (m) Max Sensing Velocity Range (m) Max sensing service latency (ms) Refreshing rate (s or Hz) 25 - Sensing Duration (once request or subscription in seconds or even-based) Confidence Level for one or more Sensing QoS Parameters (e.g., QoS parameters for the sensing service) At Step 2 of the procedure 70, the SeMF 75, according to the information included in 30 the sensing service request, determines the appropriate sensing method and one or more RAN entities (e.g., BSs) and / or one or more UEs that should be involved (as sensors) in the sensing operation, having both Sensing Tx and Rx role. The SeMF 75 also determines a Sensing Service Configuration for a sensing system. At Step 3 of the procedure 70, the SeMF 75 sends a Sensing Service Establishment Request to the involved BSs and / or UEs, including the required Sensing QoS and sensing configuration parameters e.g.. selected frequency, role for the entity in the sensing method (e.g., Tx or Rx role), etc. 5 At Step 4 of the procedure 70, each radio access network entity (e.g., BS 72) and / or UE 71 that has received the Sensing Service Establishment Request to establish a sensing session for the sensing service checks and implements and / or applies the sensing configuration received from the SeMF 75. 10 At Step 5 of the procedure 70, each BS 72 and / or UE 71 allocates and / or schedules resources according to the received sensing configuration. Depending on the provided sensing resource configuration, a UE 71 and / or a radio access network entity (e.g., BS 72) transmits sensing signals with resources required to satisfy sensing QoS. The same 15 (in monostatic) or another (in bi-static) UE 71 or radio access network entity (e.g., BS 72) receives sensing signals. At Step 6 of the procedure 70, the radio access network entity (e.g., BS 72) and / or UE 71 provides, to the SeMF 75, the sensing measurements generated based on the 20 received sensing signals. At Step 7 of the procedure 70, the SeMF 75 based on the received sensing measurements from the one or more BSs 72 and / or UEs 71 processes the collected sensing measurements and determines the sensing output. Steps 5 to 7 of the procedure 25 70 can be repeated and / or iterated, before sending sensing service response. At Step 8 of the procedure 70, the SeMF 75 provides the sensing output to the requesting sensing client 77 e.g., to an AF directly or via the NEF. 30 At Step 9 of the procedure 70, in the case that the Sensing QoS notification indication has been included in the sensing service request by the sensing client, then the SeMF 75 undertakes to check whether (a whole or part of) the objects that have been detected in the specified sensing area, have correctly (or not) discovered. This means that the SeMF 75 has successfully detected (or not) objects known already to the sensing 35 system. For that reason, the SeMF 75 requests to retrieve objects from the repository 74 that are located in a defined sensing area. The request also indicates the sensing configuration including information about the sensing type, the sensing area etc. The repository 74 may be co-located with the SeMF 75 (e.g., the SeMF may include the repository 74), making steps 9 and to unnecessary. 5 At Step 10 of the procedure 70, the repository 74 provides to the SeMF 75 the list of objects and their features (e.g., position, size, shape). At Step 11 of the procedure 70, the SeMF 75 may optionally also request to retrieve from the LMF 76 a list of UEs (i.e., connected devices) located in the defined sensing 10 area. The list of UEs includes identifiers of UEs (generally referred to a UE identifiers) that can be used by the SeMF 75 to compare with the calculated sensing inputs and then to identify if there are objects that may have been successfully detected (i.e., truepositive) or may have been missed (i.e., false-negative). 15 At Step 12 of the procedure 70, the SeMF 75 compares the determined Sensing Outputs according to collected sensing data with the information collected at 11 and 10 that could be used as a “Ground Truth” for the monitoring and estimation of the sensing outputs. 20 At Step 13 of the procedure 70, based on the determination at step 12, the SeMF 75 can determine, and monitor achieved Sensing QoS, including one or more of the following QoS parameters: 0 Sensing Accuracy 0 Sensing Resolution 25 0 Max Sensing Range (m) 0 Missed detection (%) At Step 14 of the procedure 70, in case an estimated QoS parameter of the sensing QoS meets or exceeds the defined Sensing QoS Notification threshold (if specified in step 1) 30 and for a defined time interval (if specified in step 1) then a notification is issued to the defined recipient which could be an AF, a UE, a network function (NF) or any sensing device (e.g., UE, RAN node etc.). The notification can also indicate the achieved Sensing Accuracy, Sensing Resolution, Sensing service latency, Max Sensing Range, Max Sensing, Velocity Range, Missed detection, or whether there is a false alarm. At Step 15 of the procedure 70, the SeMF 35 according to the determined Sensing QoS (step 13) can also determine whether and how sensing configuration should be modified. Different type of configurations can be decided by the SeMF 35 e.g.. change (add, remove) involved sensing devices (e.g., UEs, BSs), change sensing method (e.g., 5 monostatic, bi-static), changed selected frequency, change allocated resources. At Step 16 of the procedure 70, the SeMF 35 triggers an update of the sensing configuration for the respective sensing service (sensing request) and transmits the update configuration to the involved entities. 10 The repository 74 can help to determine true-positive object detections (i.e., SeMF 75 that correctly indicates the presence of an object and / or its features) or false-negative object detections (i.e., SeMF 75 that wrongly indicates the absence of an object and / or its features). The repository 74 can help to evaluate an ongoing sensing procedure and 15 specifically to identify that (some of) known objects can be successfully detected (i.e. used as ground truth), assessing SeMF’s 75 detection capability as well as to compare determined resolution and / or accuracy of discovered objects with the respective features of known objects (i.e. Sensing QoS features). The repository 75 can be updated by registering Objects that are known (e.g., static or semi-static objects) and / or that 20 have been registered by the corresponding stakeholder and / or retrieved by previous successful sensing operations. For instance, the registration to the repository7 can include one or more of the following information: • location of the object • indicate if an object to be sensed is connected or non-connected 25 • object type, for example. In other words, this may define the object to be sensed e.g., a car, a human, a drone, a robot, a pedestrian depending on the service type • size of the object (e.g., magnitude of the object; length of the object; width of the object; height of the object; diameter of the object; perimeter of the object; area of the object; volume of the object; or mass of the object) 30 • shape of the object • mobility of the object • description of the object using part of the sensing data (e.g., sensing measurements). The repository 74 can be a dedicated NF or Repository or database that is part of the communication system or can be owned by a third party (trusted or not to the communication system). In another option the repository- 74 can be collocated with the SeMF 75. 5 A method may include comparing the transmission and / or reception of radio signals used for sensing from the at least one radio access network node to a second set of transmission and / or reception of radio signals used for sensing from another sensing client. An example of such an arrangement is described in FIG. 8. Such arrangement 10 can be achieved independently or in combination with any other embodiment the SeMF can use sensing information that can be received by a sensing client (e.g., UEs in Sensing area). The SeMF 75 can compare the determined Sensing Outputs according to collected sensing data with the collected information of other sensing client that could be used as a “Ground Truth” for the monitoring and estimation of the sensing outputs. 15 The other Sensing clients can be used to assess current or even previous sensing outputs as a reference point for the estimation of the Sensing QoS. FIG. 8 shows a procedure in which QoS of a sensing session for a requested sensing service is monitored and notifications are triggered based using information from other 20 sensing clients. The procedure 80 shows messages (e.g., signalling) being sent between a UE 71, one or more RAN entities (e.g., base stations (BS) 72), an Access and Mobility Management Function (AMF) 73, a Sensing Management Function (SeMF) 75, a location management function (LMF) 76 and other one or more clients (e.g., UE or AF) 78. 25 Steps 1 to 8 of the procedure 80 shown in FIG. 8 are the same as steps 1 to 8 discussed in relation to FIG. 7. At Step 9 of the procedure 80, in case the sensing QoS notification has been initiated by 30 the sensing client then the SeMF 75 undertakes to check wiiether (all or part of) the objects that have been detected in the specified sensing area, have correctly (or not) discovered. Firstly, the SeMF 75 identifies the Sensing Clients 78 that could be used in the specific sensing area. The SeMF 75 can discover the other Sensing Clients 78 using UEs 71 that may be operating in Connected mode in the specified sensing area and have 35 sensing capabilities that match with the specific sensing request. The SeMF 75 can retrieve the sensing capabilities of the sensing clients which may be stored at the SeMF 75 or any other NF or Database. At Step to of the procedure 8o, the SeMF 75 requests to retrieve sensing information 5 from the Sensing Clients 78. The information includes information indicating the defined sensing area, the sensing configuration information e.g., about the type, the location etc. At Step 11 of the procedure 80, each Sensing Client 78 provides to the SeMF 78 the 10 information about the discovered objects and their features (e.g., position, size, shape), according to the sensing configuration. Subsequently, Steps 12 to 17 of procedure 80 are the same as steps 12 to 17 of procedure 70 discussed in relation to FIG. 7. 15 As an alternative option and / or in combination with the above-described procedures 70, 80, the SeMF 75 can use other dedicated sensor devices that may be registered or associated with the communication system (e.g., 5GS) to determine and monitor the achieved Sensing QoS. Such a procedure may comprise comparing the transmission 20 and / or reception of radio signals used for sensing from at least one radio access network node to sensing information received from a dedicated sensing device. The dedicated sensing device comprises at least one of: a 3GPP compliant sensor device, a non-3GPP compliant sensor device, a light detection and ranging system (LiDAR), and / or a radio detection and ranging system (RADAR). An example of such an 25 arrangement is described in FIG. 9. Examples of a 3GPP compliant sensor device includes sensor devices that can use 3GPP-based protocol and / or signalling for sensing related functions e.g., the provision of collected sensing data, the configuration of the sensor device, the transmission or reception of sensing signals. Examples of a non-3GPP sensor include a LiDAR device and / or radar device. An access point may be Wi- 30 Fi access point. FIG. 9 shows a procedure for monitoring sensing QoS of a sensing session and for triggering notifications of sensing QoS for a sensing session using information received from a dedicated sensing device. The procedure 90 shows messages being sent between 35 a UE 71, one or more RAN entities (e.g., base stations (BS) 72), an Access and Mobility Management Function (AMF) 73, a Sensing Management Function (SeMF) 75, a location management function (LMF) 76 and a dedicated sensor device 79. The dedicated sensor device 79 may be registered to the SeMF 75 or another NF or 5 repository and are selected by the SeMF 75 according to the Sensing Service Request requirements (e.g., sensing type, sensing area etc) (step 9). The SeMF 75 requests to retrieve sensing information from the dedicated sensor device(s) 79. The request includes information about a sensing area, sensing configuration information (e.g., about the sensing type, the location) and / or the format that the requested sensing 10 information should be provided (step 10). The one or more dedicated sensor devices 79 provides the sensing information in the requested format, about discovered objects and their features (e.g., position, size, shape), according to the requested sensing configuration information. The other steps, about how the SeMF 75 can determine, and monitor the achieved sensing QoS for a sensing session as well as how to trigger 15 notifications of the sensing QoS for a sensing session are the same as previously described in relation to FIGS. 7 and 8. As an alternative option and / or in combination with the above-described procedures 70, 80, 90, the SeMF 75 can exploit sensing devices (UE, radio network node entity 20 (e.g., BS)) error sources for monitoring a QoS of a sensing session for a requested sensing service and for trigger notifications of changes. This may comprise analysing at least one sensing errors of the radio access network nodes or other features of the sensing system. Analysing the at least one sensing error may comprise determining an upper bound (or a maximum value) of the sensing error for one or more quality of 25 service parameter. QoS parameters, such as, for example, a certainty factor or a sensing protection level, may be used to determine the upper bound (or maximum value) of the sensing error. FIG. 10 shows a procedure 90 that enables monitoring of QoS of a sensing session for a 30 requested sensing service and sending notifications that indicate changes to a QoS of a sensing session for a requested sensing service using sensing devices error sources. The procedure 90 shows messages being sent between a UE 71, one or more RAN entities (e.g., base stations (BS) 72) of a 5G wireless communication system, an Access and Mobility Management Function (AMF) 73, a Sensing Management Function (SeMF) 75, 35 a location management function (LMF) 76 and a sensing client 77. The SeMF 75 can request information about potential error sources of the sensing devices in the sensing system. The information about potential error sources can help the SeMF 75 to estimate the expected sensing QoS level and thus identify whether sensing QoS notifications should be triggered. QoS levels may refer to a range of values 5 e.g., QoS level 1 (sensing latency of 10 ms), QoS level 2 (sensing latency of 20 ms) as known within the field. The sensing device may comprise a user equipment 71 and / or a radio access network entity (e.g., base station 72), depending also on the selected sensing method. The 10 expected Sensing QoS is expressed through the sensing protection level. The sensing protection level is the calculated statistical upper-bound of the sensing error. The SeMF 75 according to the type of the sensing request determines the sensing QoS parameters for which the sensing protection level needs to be determined. Different sensing QoS parameters and / or sensing devices may have different error sources. 15 In the request the SeMF 75 can include the sensing QoS parameters for which information related to sensing integrity for error sources to UE 71 and / or radio access network entity (e.g., base station 72). Examples of error sources are clock synchronization, angle, range, speed measurement error. The respective node provides 20 the sensing integrity related information to the SeMF, which is used for the estimation of Sensing Protection Level for the corresponding sensing QoS parameter. Then the SeMF compares the Sensing Protection Level with Sensing QoS Notification thresholds, and the notifications are sent to the recipients and / or sensing reconfiguration can be triggered. 25 In addition, the Other Clients 78 and Dedicated Sensor 79 entities mentioned in previous embodiments can also be requested by the SeMF 75 to provide the error source in order to being able to compute the sensing protection level and derive notifications also for the sensing data provided by them. 30 The procedure too comprises exploiting sensing error sources for notification triggering, as explained in FIG. 10 and it involves the following steps. Step 1 of procedure too corresponds to step 1 of procedure 700 shown in FIG. 7. At 35 Step 2 of the procedure too, the SeMF 75, according to the type of the sensing request (e.g., sensing service, sensing QoS requirements), determines the Sensing QoS parameters for which the Sensing Protection Level needs to be determined. Subsequently, Step 3 corresponds to steps 2 to 8 of FIG. 7. At Step 4, the SeMF 75 requests to UEs 71 and / or BSs 71 (e.g., gNBs) the assistance information related to error sources contributing to a specific sensing QoS. At Step 5, UEs 71 and / or BSs 72 5 provide to the SeMF 75 the necessary sensing-related error sources assistance information (e.g., statistics of the error sources). At Step 6, the SeMF 75, taking as input all the received assistance information, computes the sensing protection level (i.e., an estimated overbound of the true error) for each QoS parameter. At Step 7, the SeMF compares the just computed sensing protection level with the sensing QoS notification 10 threshold for each QoS parameter. Finally, Steps 8 to 10 of operation too correspond to steps 14 to 16 of operation 70 shown in FIG. 7. The sensing integrity can be calculated in the SeMF 75 as presented in the above embodiment or can be a separate function or could also be part of another NF. The 15 sensing integrity7 can be also estimated by each sensing device and / or by a group of sensing devices (e.g., radio access network entity (e.g., BS 72) or UE 71). The sensing integrity outputs can be provided to the SeMF 75 or any other function that is responsible for the determination of sensing QoS notifications and / or triggering sending of sensing QoS notifications. 20 Optionally, the Sensing QoS for any of the above embodiments can be estimated per one or more of the following parameters: sensing request, sensing area and sensing type. 25 Optionally, the different Sensing QoS parameters (e.g., sensing delay, resolution, accuracy etc) may require different types of Sensing QoS Monitoring method, described in the previous embodiments. The SeMF 75 can select the appropriate monitoring method according to the available information (e.g., existence of repository 74 and stored sensing information), the sensing area, the type of Sensing QoS parameter, 30 availability of Dedicated Sensor Devices 79. Optionally, the SeMF 75 can determine the QoS of a sensing service before the degradation of the sensing QoS and thus predict the expected Sensing QoS for one or more QoS parameters that have been requested, providing statistical information about 35 the estimated sensing QoS. Optionally, the Sensing Sendee Request can be sent from a UE 71 to the SeMF 75 using non access stratum (NAS) (and / or radio resource control RRC) signalling. Also, the notifications about the Sensing QoS from the SeMF 75 can be transmitted to the UE 71 using NAS (and / or RRC) signalling. 5 For completeness, FIG. 13 is a schematic diagram of components of one or more of the example embodiments described previously, which hereafter are referred to generically as a processing system 300. The processing system 300 may, for example, be the apparatus referred to in the claims below. For example, the processing system 300 10 may be used to implement functionality of a sensing management function (e.g., implemented by an SeMF), or features implemented at a sensing client or a RAN entity (e.g., base station) as discussed in detail above. The processing system 300 may have a processor 302, a memory 304 closely coupled to 15 the processor and comprised of a RAM 314 and a ROM 312, and, optionally, a user input 310 and a display 318. The processing system 300 may comprise one or more network or apparatus interfaces 308 for connection to a network or apparatus, e.g., a modem which may be wired or wireless. The network or apparatus interface 308 may also operate as a connection to other apparatus such as device or apparatus which is not 20 network side apparatus. Thus, direct connection between devices or apparatus without network participation is possible. The processor 302 is connected to each of the other components in order to control operation thereof. 25 The memory 304 may comprise a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD). The ROM 312 of the memory 304 stores, amongst other things, an operating system 315 and may store software applications 316. The RAM 314 of the memory 304 is used by the processor 302 for the temporary storage of 30 data. The operating system 315 may contain code which, when executed by the processor implements aspects of the methods, processes and sequences 40,50, 60, 70, 80, 90, too, no and 120 described above. Note that in the case of small device or apparatus the memory can be most suitable for small size usage i.e., not always a hard disk drive (HDD) or a solid state drive (SSD) is used. The processor 302 may take any suitable form. For instance, it may be a microcontroller, a plurality of microcontrollers, a processor, or a plurality of processors. 5 The processing system 300 may be a standalone computer, a server, a console, or a network thereof. The processing system 300 and needed structural parts may be all inside apparatus such as loT apparatus i.e., embedded to very small size. In some example embodiments, the processing system 300 may also be associated with 10 external software applications. These may be applications stored on a remote server apparatus and may run partly or exclusively on the remote server apparatus. These applications may be termed cloud-hosted applications. The processing system 300 may be in communication with the remote server apparatus in order to utilize the software application stored there. 15 FIG. 14 shows a tangible media, in the form of a removable memory unit 365, storing computer-readable code which when run by a computer may perform methods according to example embodiments described above. The removable memory unit 365 may be a memory stick, e.g., a USB memory stick, having internal memory 366 storing 20 the computer-readable code. The internal memory 366 may be accessed by a computer system via a connector 367. Of course, other forms of tangible storage media may be used, as will be readily apparent to those of ordinary skilled in the art. Tangible media can be any apparatus capable of storing data and / or information which data and / or information can be exchanged between apparatus and / or network. 25 Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and / or hardware may reside on memory, or any computer media. In an example embodiment, the application logic, software or an instruction set 30 is maintained on any one of various conventional computer-readable media. In the context of this document, a “memory” or “computer-readable medium” may be any non-transitory media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. Reference to, where relevant, “computer-readable medium”, “computer program product”, “tangibly embodied computer program” etc., or a “processor” or “processing circuitry" etc. should be understood to encompass not only computers having differing architectures such as single / multi-processor architectures and sequencers and / or 5 parallel architectures, but also specialised circuits such as field programmable gate arrays FPGA, application specify circuits ASIC, signal processing devices / apparatus and other devices / apparatus. References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device / apparatus as instructions for a 10 processor or configured or configuration settings for a fixed function device / apparatus, gate array, programmable logic device / apparatus, etc. If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the 15 above-described functions may be optional or may be combined. Similarly, it will also be appreciated that the flow diagrams and sequences of Figures 4 to 12 are examples only and that various operations depicted therein may be omitted, reordered and / or combined. 20 It will be appreciated that the above described example embodiments are purely illustrative and are not limiting on the scope of the invention. Other variations and modifications w ill be apparent to persons skilled in the art upon reading the present specification. 25 Moreover, the disclosure of the present application should be understood to include any novel features or any novel combination of features either explicitly or implicitly disclosed herein or any generalization thereof and during the prosecution of the present application or of any application derived therefrom, new claims maybe formulated to cover any such features and / or combination of such features. 30 Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described example embodiments and / or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. It is also noted herein that while the above describes various examples, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

1. An apparatus comprising:at least one processor; and5 at least one memory storing instructions for a sensing management function,wherein execution of the instructions causes the apparatus to perform at least: receiving, from a sensing client of a wireless communication system, a sensing service request for a sensing service provided by the sensing management function, wherein the sensing service request comprises aio requested quality of service for the sensing service;determining, a sensing configuration for a sensing session for the sensing service based at least on the requested quality of service for the sensing service;based on the sensing configuration, configuring a sensing system15 comprising at least one radio access network node and / or at least one userequipment to perform sensing;determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user20 equipment; andnotifying the sensing client, based on the determination that the quality of service of the sensing session for the sensing service does not meet the requested quality of service.25 2. The apparatus of claim 1, wherein the sensing service request further comprises atleast one threshold for the quality of service.

3. The apparatus of claim 2, determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service comprises:30 determining whether the at least one threshold for the quality of service of thesensing session is met or not met.

4. The apparatus of any preceding claim, wherein execution of the instructions by the at least one processor further causes the apparatus to perform:sending, to the sensing client, a notification that indicates that quality of service of the sensing session has changed based on a determination that the quality of service of the sensing session has changed.5 5. The apparatus of claim 4, wherein the notification comprises a measured, computed,or predicted quality of service value for the quality of service of the sensing session.

6. The apparatus of claims 4 or 5, wherein the notification comprises an indication that the at least one threshold for the quality of service is met or not met.

107. The apparatus of claims 4 to 6, wherein execution of the instructions further causes the apparatus to perform:upon determining that the at least one threshold for the quality of service is met or not met, sending, to the sensing client, the notification.

158. The apparatus of any of claims 4 to 7, wherein the sensing service request further comprises an indication whether the notification should be sent to the sensing client, and optionally at least one configuration parameter for triggering sending the notification.

209. The apparatus of any preceding claim, wherein the quality of service comprises a required accuracy for sensing an object, wherein the required accuracy comprises at least one of:- An estimate of a position of an object to be sensed;25 - An estimate of a velocity of an object to be sensed;- An orientation of an object to be sensed;- A range of an object to be sensed;- An angular position of an object to be sensed.30 10. The apparatus of any preceding claim, wherein the quality of service comprises atleast one of the following features of an object- A sensing resolution of the sensing system comprising at least one of range resolution, velocity7 resolution, angular resolution;A maximum sensing range of the sensing system;35 - A maximum sensing velocity7 range of the sensing system;- A maximum sensing sendee latency of the sensing system;A refresh rate of the sensing system;- A sensing duration of the sensing system.it. The apparatus of any of claims 2 to io, wherein execution of the instructions further causes the apparatus to perform:adapting at least one feature of radio access network node and / or user equipment such that the at least one threshold for the quality of service is met or not.

12. The apparatus of any one of claims 1 to 11. wherein determining whether a quality of service of the sensing session for the sensing service meets the requested quality of sendee based on sensing data received from the at least one radio access network node and / or user equipment comprises:comparing sensing radio signals received from the at least one radio access network node and / or the least one user equipment to information regarding known sensing data in a sensing area obtained from an object repository7.

13. The apparatus of any one of claims 1 to 11, wherein determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user equipment comprises:comparing a sensing output to information regarding known sensing objects in a sensing area obtained from an object repository.

14. The apparatus of any one of claims 1 to 11, wherein determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user equipment comprises:comparing the transmission and / or reception of radio signals used for sensing from the at least one radio access network node and / or the least one user equipment to a second set of transmission and / or reception of radio signals used for sensing from another sensing client.

15. The apparatus of any one of claims 1 to 11, determining whether a quality of service of the sensing session for the sensing sendee meets the requested quality of service based on sensing data received from the at least one radio access network node and / or user equipment comprises:comparing the transmission and / or reception of radio signals used for sensing from the at least one radio access network node and / or the least one user equipment to a third set of transmission and / or reception of radio signals used for sensing from a dedicated sensing device.

516. The apparatus of claim 15, wherein the dedicated sensing device comprises at least one of: a 3GPP compliant sensor device, a non-3GPP compliant sensor device, a light detection and ranging system (LiDAR), and / or a radio detection and ranging system (RADAR).1017. The apparatus of any preceding claim, wherein execution of the instructions further causes the apparatus to perform:analysing at least one sensing error of the radio access network node and / or the user equipment to determine at least one quality of service of the sensing sendee.1518. An apparatus comprising:at least one processor; andat least one memory storing instructions, wherein execution of the instructions causes the apparatus to perform:20 determining, at a sensing client of a wireless communication system, arequested quality of service for a sensing client;transmitting, from the sensing client of the wireless communication system to a sensing management function of a wireless communication system, a sensing sendee request for a sensing service to be provided by the sensing 25 management function, wherein the sensing sendee request comprises arequested quality of service for the sensing service.

19. The apparatus of claim 18, wherein the sensing service request further comprises at least one threshold for the quality of sendee.3020. The apparatus of any of claims 18 to 19, wherein execution of the instructions further causes the apparatus to perform:receiving, from the sensing management function, a notification that indicates that quality of sendee of the sensing session has changed based on a determination that 35 the quality of sendee of the sensing session has changed.

21. The apparatus of claim 20, wherein the notification comprises a measured, computed, or predicted quality of sendee value for the quality7 of sendee of the sensing session.5 22. The apparatus of claims 20 or 21, wherein the notification comprises an indicationthat the at least one threshold for the quality of service is met or not met.

23. The apparatus of any of claims 21 to 22, wherein the sensing sendee request further comprises an indication whether the notification should be sent to the sensing client, 10 and optionally at least one configuration parameter for triggering sending the notification.

24. The apparatus of any of claims 18 to 23, wherein the quality of service comprises a required accuracy7 for sensing an object, wherein the required accuracy comprises at 15 least one ofi- An estimate of a position of an object to be sensed;- An estimate of a velocity of an object to be sensed;- An orientation of an object to be sensed;- A range of an object to be sensed;20 - An angular position of an object to be sensed.

25. A method, comprising:receiving, from a sensing client of a wireless communication system, a sensing service request for a sensing service provided by a sensing management 25 function, wherein the sensing service request comprises a requested quality ofservice for the sensing service;determining, a sensing configuration for a sensing session for the sensing service based at least on the requested quality of service for the sensing service;30 based on the sensing configuration, configuring a sensing systemcomprising at least one radio access network node and / or user equipment to perform sensing;determining whether a quality of service of the sensing session for the sensing service meets the requested quality of service based on sensing data 35 received from the at least one radio access network node and / or userequipment; andnotifying the sensing client, based on the determination that the quality of sendee of the sensing session for the sensing service does not meet the requested quality of service.43

Images