Sensing services in wireless communication system

Abstract

A processing system comprises at least one processor and at least one memory storing instructions of a sensing management function. Execution of the instructions by the at least one processor causes the processing system to at least: establish a sensing session with one or more devices of a wireless communication system; determine network resource utilization information comprising one or more parameters of the sensing session; generate a charging sensing session request including the network resource utilization information; and send to a charging function, the charging sensing session request to determine a charging rate for the sensing session based at least on the network resource utilization information.

Description

SENSING SERVICES IN WIRELESS COMMUNICATION SYSTEMFIELD OF TECHNOLOGY

[0001] The present disclosure relates to sensing services in a wireless communication system.BACKGROUND

[0002] The present disclosure relates to the provisioning of sensing services in an integrated sensing communication system. Example sensing services include detection and / or tracking of objects.

[0003] Developments in the provisioning of sensing services by wireless communication systems are desirable.SUMMARY

[0004] According to one aspect, a processing system comprises at least one processor; and at least one memory storing instructions of a sensing management function, wherein execution of the instructions by the at least one processor causes the processing system to at least: establish a sensing session with one or more devices of a wireless communication system; determine network resource utilization information comprising one or more parameters of the sensing session; generate a charging sensing session request including the network resource utilization information; and send to a charging function, the charging sensing session request to determine a charging rate for the sensing session based at least on the network resource utilization information.

[0005] In some examples, execution of the instructions by the at least one processor causes the processing system to, prior to establishing the sensing session, receive, from a sensing service client of the wireless communication system, a sensing session request to perform the sensing session, prior to establishing the sensing session.

[0006] The sensing session request may include a sensing service client identification and location information.

[0007] In some examples, execution of the instructions by the at least one processor causes the processing system to: receive a response from the charging function indicating receipt of the network resource utilization information, along with charging information related to the sensing service client; and utilize the charging information related to the sensingservice client to determine sensing configuration information to configure the sensing session.

[0008] Optionally, the charging information related to the sensing service client comprises at least one of expiry of a time limit for the sensing session; expiry of a data volume limit for the sensing session; a sensing volume quota threshold; or a sensing time quota threshold.

[0009] In some examples, the sensing configuration to configure the sensing session comprises information to configure at least one of adjusting the quality of service of the sensing session; changing the sensing method utilized; changing resources allocated to the sensing session; stopping the sensing session; identifying a release of the sensing session; or sending a notification to the sensing service client.

[0010] In some examples, the one or more parameters comprise at least one of a number of transmissions during the sensing session; amount of data including data transmitted and data received to perform sensing measurements; amount of resources utilized to transmit or receive sensing signals; a duration time of the sensing session; an active transmission time; an active reception time; total bandwidth utilized; a carrier frequency utilized; a number of antenna elements utilized; power consumption; processing time or processing resources utilized at the network; sensing session quality of service; or quality of extracted sensing information, determined by comparing the sensing measurements with measurements from other measuring entities.

[0011] Optionally, the one or more parameters include quality of the sensing session comprising at least one of sensing accuracy; sensing resolution; sensing range; sensing latency; or sensing refresh rate.

[0012] In some examples, execution of the instructions by the at least one processor causes the processing system to send the charging sensing session request upon establishment of the sensing session.

[0013] Optionally, execution of the instructions by the at least one processor causes the processing system to send the charging sensing session request in response to one of expiry of a time period after establishment of the sensing session; a determination that a duration of the sensing session meets a threshold; or a determination of use of a particularnetwork resource or resources.

[0014] In some examples, execution of the instructions by the at least one processor causes the processing system to discontinue the sensing session.

[0015] In some examples, execution of the instructions by the at least one processor causes the processing system to send to the charging function, an indication of completion of the sensing session.

[0016] According to an aspect, a method comprises; establishing, by a sensing management function of a wireless communication system, a sensing session with one or more devices of the wireless communication system; determining network resource utilization information comprising one or more parameters of the sensing session; generate a charging sensing session request including the network resource utilization information; and sending to a charging function, the charging sensing session request to determine a charging rate for the sensing session based at least on the network resource utilization information.

[0017] In some examples, the method includes receiving, at the sensing management function of the wireless communication system, a sensing session request to perform the sensing session and, in response, wherein, the sensing session is established in response to receiving the sensing session request.

[0018] The sensing session request may include a sensing service client identification and location information.

[0019] Optionally, the method includes receiving a response from the charging function indicating receipt of the network resource utilization information, along with charging information related to the sensing service client; and utilizing the charging information related to the sensing service client to configure the sensing session.

[0020] According to another aspect, a processing system comprises: at least one processor; and at least one memory storing instructions of a charging function, wherein execution of the instructions by the at least one processor causes the processing system to at least: receive a charging sensing session request including network resource utilization information comprising one or more parameters of a sensing session; based on the one or more parameters, generate a charging sensing session record for the sensing session; send the charging sensing session record to a billing system to charge based on the sensingsession.

[0021] In some examples, execution of the instructions by the at least one processor causes the processing system to store sensing session related charging data including the one or more parameters of the sensing session prior to generating the charging sensing session record.

[0022] Optionally, execution of the instructions by the at least one processor causes the processing system to determine a charge rate of the sensing session based on the one or more parameters of the sensing session, wherein the charging sensing session record includes the charge rate of the sensing session.

[0023] In some examples, the one or more parameters comprise at least one of: a number of transmissions during the sensing session; amount of data including data transmitted and data received to perform sensing measurements; amount of resources utilized to transmit or receive sensing signals; a duration time of the sensing session; an active transmission time; an active reception time; total bandwidth utilized; a carrier frequency utilized; a number of antenna elements utilized; power consumption; processing time or processing resources utilized at the network; sensing session quality of service; or quality of extracted sensing information, determined by comparing the sensing measurements with measurements from other measuring entities.

[0024] Optionally, the one or more parameters includes quality of the sensing session comprising at least one of: sensing accuracy; sensing resolution; sensing range; sensing latency; or sensing refresh rate.

[0025] In some examples, execution of the instructions by the at least one processor causes the processing system to send a response to a sensing management function, the response indicating receipt of the one or more parameters of the sensing session, along with charging information related to a sensing service client.

[0026] In some examples, the charging information related to the sensing service client comprises at least one of: expiry of a time limit for the sensing session; expiry of a data volume limit for the sensing session; a sensing volume quota threshold; or a sensing time threshold.

[0027] Optionally, the charging sensing session record is generated in response to receipt of an indication of completion of the sensing session.

[0028] Optionally, the charging sensing session request includes an indication of a change to the one or more parameters.

[0029] In some examples, execution of the instructions by the at least one processor causes the processing system to send to a sensing management function, charging information related to the sensing service client to configure the sensing session based on the charging information.

[0030] In another aspect, a method comprises: receiving at a charging function a charging sensing session request including information comprising one or more parameters of a sensing session; based on the one or more parameters, generating a charging sensing session record for the sensing session; and sending the charging sensing session record to a billing system to charge based on the sensing session.

[0031] In yet another aspect, a processing system comprises: at least one processor; and at least one memory storing instructions of a sensing management function, wherein execution of the instructions by the at least one processor causes the processing system to: determine a change to a sensing service configuration based on a sensing event; generate a charging sensing event request including an indication of the change to the sensing service configuration; and send, to a charging function, the charging sensing event request to determine charging information.

[0032] Execution of the instructions by the at least one processor may cause the processing system to receive information including sensing service client identification and location information for the sensing service client.

[0033] In some examples, the change to the sensing service configuration based on the sensing event comprises a change to at least one of: a quality of service of the sensing service; the sensing method utilized; resources allocated to the sensing service; bandwidth utilized; or number of antenna elements utilized.

[0034] Optionally, the change to the sensing service configuration of the sensing event comprises a change to the quality of service comprising at least one of: sensing accuracy; sensing resolution; sensing range; sensing latency; or sensing refresh rate.

[0035] In yet another aspect, a method comprises receiving at a sensing management function of a wireless communication system, a sensing service client identification andlocation information for the sensing service client; determining a change to a sensing service configuration based on a sensing event; generating a charging sensing event request including an indication of the change to the sensing service configuration; and sending to a charging function, the charging sensing event request to determine charging information.

[0036] In another aspect, a processing system comprises at least one processor; and at least one memory storing instructions of a sensing management function, wherein execution of the instructions by the at least one processor causes the processing system to: receive from one of a user equipment and base station, charging-related information including network resource utilization information comprising one or more parameters of a sensing session; send, to a charging function, a charging sensing session request including the network resource utilization information to determine charging information for the sensing session.

[0037] In still another aspect, a method comprises: receiving at a sensing management function of a wireless communication system, charging-related information including network resource utilization information comprising one or more parameters of a sensing session; and sending to a charging function, a charging sensing session request including the network resource utilization information to determine a charging rate for the sensing session based at least on the network resource utilization information.

[0038] In another aspect, a computer program comprises instructions which, when executed by an apparatus, cause the apparatus to at least perform any of the methods in accordance with aspects and examples as set forth above.

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

[0040] Embodiments of the present disclosure will now be described, by way of example only, with reference to the attached figures.

[0041] FIG. l is a schematic diagram showing a communication network in accordance with an aspect of an embodiment.

[0042] FIG. 2 is a schematic diagram of a processing system for a communication network in accordance with an aspect of an example implementations.

[0043] FIG. 3 through FIG. 6 are flowcharts showing methods in accordance with examples.

[0044] FIG. 7 and FIG. 8 are flowcharts showing methods in accordance with example implementations.

[0045] FIG. 9 through FIG. 11 are diagrams showing signaling and operations of a procedure in accordance with implementations.DETAILED DESCRIPTION

[0046] For simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. Numerous details are set forth to provide an understanding of the examples described herein. The examples may be practiced without these details. In other instances, well-known methods, procedures, and components are not described in detail to avoid obscuring the examples described. The description is not to be considered as limited to the scope of the examples described herein.

[0047] The present disclosure relates to sensing services in a wireless communication system, for example, a sensing service which provides awareness of a scene that surrounds radio access network entities that are configured as sensing devices. Sensing devices include, for example, devices that have the capability to perform one or more of: detection, localization, and / or tracking of objects; forming images of a specific scene or environment; or identifying features of discovered objects for recognition and / or classification.

[0048] 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 potentially achieves both relatively high-data rate communications and relatively high-resolution object detection using at least some of the same hardware and spectrum resources. This is advantageous, for example, in improving sensing accuracy for scenarios or situations where existing sensing techniques do not perform as well (e.g., non-line-of-sight (NLOS) conditions, requirement for high velocity resolution), to enhance spectrum efficiency by sharing communication and sensing spectrum band, and / or to reduce hardware cost by combining sensing and communication equipment / hardware.

[0049] Example scenarios in which an integrated sensing and communication (ISAC) system may be used include (but are not limited to) the following: intrusion detection (e.g., intruder detection in a smart home, pedestrian or animal intrusion detection on a highway); support for autonomous driving (e.g., sensing assisted automotive maneuvering and navigation by providing additional information for detected objects on the roads such as pedestrians, bicycles, or other vehicles, sensing for parking space determination); 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 do not have communication means to indicate their presence); support for automated guided vehicle (AGV) or autonomous mobile robots (AMR) in factories (e.g., AGV detection and tracking in factories), AMR collision avoidance in smart factories); environment and / or weather monitoring (e.g., rain, pollution, flooding); health monitoring (e.g., fall detection, contactless sleep monitoring service); or extended reality (XR) applications.

[0050] Reference is first made to FIG. 1, which shows a schematic representation of a wireless communication system 100 that a user equipment (UE) 102 has access to in order to communicate with application servers (not shown) hosting third party application functions (not shown) via data network 104. The wireless communication system 100 comprises an ISAC system that includes radio access network (RAN) entities 106 (e.g., RAN entities of a NG-RAN) and a core network 108 (e.g., a 5G core network (5GC)) that operate based on the 5th generation radio access technology described in the 3rdGeneration Partnership Project (3 GPP) standard for new radio.

[0051] The radio access network (RAN) entities 106 comprise one or more radio access network (RAN) nodes (otherwise referred to as base stations), such as a gNodeB (gNB). A radio access network node comprises a central unit (e.g., gNB-CU) and one or more distributed units (e.g., one or more gNB-DUs) linked to the central unit (e.g., gNB-CU) by a Fl interface.

[0052] The core network 108 has a service-based architecture and comprises a plurality of network functions, including, inter alia, an access and mobility function (AMF) 112, an application function (AF) 114, an authentication server function (AUSF) 116, a networkexposure function (NEF) 118, a network repository function (NRF) 120, a network slicing selection function (NSSF) 122, a policy control function (PCF) 124, a session management function (SMF) 126, a user plane function (UPF) 128, and a united data repository (UDM) 130. Other network functions of the core network 108, such as a binding support function (BSF) are not illustrated but would be understood by a person skilled in the art. The functionalities of the network functions of the core network are known to a person skilled in the art and hence are not described in detail.

[0053] The network functions of the core network 108 also include a charging function (CHF) 110 that is responsible for the charging operations at the core network 108 and interfaces with a billing domain, such as a billing system or systems utilized for billing.

[0054] In addition to the network functions referred to above, the core network 108 also includes a sensing management function (SeMF) 134 configured to provide sensing services to a sensing service client, such as the UE 102 or one or more RAN entities 106.

[0055] Each network function (NF) of the core network 108 provides one or more services to other network functions of the core network via Application Programming Interfaces (APIs). Each NF can also register itself and the services it supports (e.g., the services it offers other network functions) to the NRF 120 of the core network 108. The NRF 120 is used by any network function to discover other network functions (or instances of NFs) and the services the other NFs support (e.g., services the other NFs provide). Any NF is operable to consume (e.g., use) the services provided and exposed by another NF. A NF that consumes a service of another network function is generally referred to as a network function service consumer. A network function that provides and exposes one or more of its services is referred to as a network function service producer.

[0056] Sensing is carried out in the ISAC system, for example, by a first radio access network entity, such as a gNB. The first radio access network entity transmits sensing signals (e.g., RF signals) when the first radio access network entity is configured for a sensing operation (e.g., a monostatic sensing operation) in which the first radio access network entity acts as a sensing transmitter. The first radio access network entity also receives sensing signals (e.g., radio signals) that are, for example, deflected, reflected, or refracted by objects in a vicinity of the first radio access network entity when the first radio access network entity is configured for a sensing operation (e.g., a monostatic sensing operation) in which the first radio access network entity is also considered to be or is acting as a sensing receiver.

[0057] Alternatively, sensing is carried out in a bistatic sensing system that includes first radio access network entity, such as a gNB, and a second radio access network node, such as another gNB. The first radio access network entity sends out sensing signals (e.g., radio signals), when configured for a sensing operation, therefore acting as a sensing transmitter. The second radio access network entity receives sensing signals deflected, reflected or refracted by objects located in a vicinity of the second radio access network entity when the second radio access network entity is configured for a sensing operation, therefore acting as a sensing receiver.

[0058] In each of the monostatic and bistatic sensing systems, sensing measurement data (or sensing data / sensing measurement information) includes 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. The sensing measurement data is optionally processed (e.g., by a network function within a wireless communication system, such as a 5G and / or 6G system, a server external to the wireless communication system, application server connected to the wireless communication system via, for example, the NEF of the wireless communication system, edge server (e.g., a server located near the wireless communication server.). While sensing output(s) includes processed sensing data e.g., requested by a sensing service consumer, also referred to as a sensing service client, such as the UE, of a sensing service provided by the 5G and / or 6G system that includes the sensing system.

[0059] Examples of sensing data or sensing measurement information comprise one or more of information about received or arrived electromagnetic signals. Information about a received or arrived electromagnetic signal optionally includes a received power, delay, angle of departure, angle of arrival, doppler shift, and / or the like of the received or arrived electromagnetic signal.

[0060] The SeMF 134 shown in FIG. 1 is utilized to provide sensing services to a sensing service client such as the UE 102, the application function (AF) 114, or the network exposure function (NEF) 118 of the wireless communication system. The SeMF 134 is responsible for configuration, coordination, and enablement of network resources such as the RAN entities 106 for a sensing operation.

[0061] The SeMF 134 is implemented by a combination of hardware processing circuitry and software and / or firmware comprising machine-readable instructions that are executable by the hardware processing circuit, or software comprising machine-readableinstructions that are executable by a hardware processing circuit of an apparatus. A hardware processing circuit includes at least one 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 includes 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, a central processing unit, a graphic processing unit, a tensor processing unit. Memory includes 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 stores the machine-executable instructions of the software and / or firmware for execution by the at least one processor of the hardware processing circuit. The machine-executable instructions are executable by the hardware processing circuit to perform the actions or operations of the methods of the SeMF described herein.

[0062] The SeMF 134 receives, from the sensing service client, such as the UE 102, the application function (AF) 114, or the network exposure function (NEF) 118 of the wireless communication system, sensing requests for different types of sensing services provided by the SeMF 134. The SeMF 134 also determines a sensing method to be performed (e.g., whether a monostatic or multistatic (e.g., bistatic) sensing is to be used). In addition, the SeMF 134 determines one or more RAN entities 106 to be involved in a sensing operation based on the sensing method that is determined, and the sensing roles of the respective RAN entities 106. For example, for each of the one or more RAN entities 106, the SeMF 134 implemented or comprised in the sensing management module 32 is operable to 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.

[0063] The SeMF 134 interacts with the one or more RAN entities 106 and transmits to the one or more RAN entities 106 (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 sensing configurations.

[0064] The SeMF 134 is configured to determine or calculate the sensing output as requested. A sensing output optionally comprises processed sensing data e.g., as requested by a sensing service client. For example, the processed sensing data in one example issensing data processed by the SeMF 134. The processed sensing data includes 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 is data about the objects in an area. The SeMF 134 alternatively or additionally is configured to provide the sensing data received or collected from one or more sensing devices as a sensing output. The SeMF 134 is operable to provide to the sensing service client sensing data if the sensing data is requested by the sensing service client.

[0065] The sensing service client, also referred to as the sensing service consumer, is, for example:• an application function (e.g., trusted to the Public Land Mobile Network (PLMN)) and the request is received directly from the sensing service client;• an application function and the request received from the sensing service client via the NEF 118;• a UE, such as the LE 102;• another network entity, such as a RAN node and / or network function of a wireless communication system, such as a network function of the core network of the wireless communication system 100.

[0066] The RAN entities 106 utilized in sensing include a base station as referred to above, include sensing functionalities to provide sensing and / or positioning measurements, transmit the signals for sensing and / or positioning. Optionally, other RAN entities such as a new network node dedicated for sensing purposes or part of an existing network node (e.g., Positioning Reference Unit, Reconfigurable Intelligent Surfaces) are also be utilized.

[0067] In some implementations, a RAN entity validates and realizes the sensing configurations received from the SeMF 134. The RAN entity 106 also conducts 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 RAN entity 106, which is then provided to the SeMF 134 and / or to other RAN entities (e.g., via an Xn interface). Any of the RAN entities 106 that operate as a sensing receiver obtain sensing data and provide that sensing data to the SeMF 134 (with or without processing the sensing data), according to the sensing data reporting configurations for processing the sensing data to derive sensing outputs.

[0068] In the example shown in FIG. 1, the SeMF 134 is a dedicated network function forthe core network 108. Optionally, the SeMF is a dedicated network function for one or more RAN entities 106. In some implementations, the SeMF (e.g., functionality of the SeMF) is integrated into an existing network function for a wireless communication system, such as a location management function (LMF) that provides location services for locating user equipment in a 5GS. In some implementations, the functionalities of the SeMF are distributed across a plurality of different network functions of the core network or are integrated into one or more RAN entities 106.

[0069] In an example implementation, the SeMF is operable to:• Determine the sensing method (e.g., monostatic sensing, or bistatic sensing, or multistatic sensing), and determine a sensing configuration for the RAN entities identified or selected to be involved in a sensing session for the determined sensing method. These determinations are made 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. In the case that the determined sensing method is monostatic sensing, the SeMF identifies or selects one or more RAN entities to be involved in and determine or generate a sensing configuration for the one or more RAN entities for configuring the one or more RAN entities 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. Alternatively, in the case of bistatic sensing and / or multistatic sensing is determined, identify or select one RAN entity to be a sensing transmitter and one or more other RAN entities (e.g., BSs) to be sensing receivers and determine or identify a sensing configuration for configuring the one RAN entity to be a sensing transmitter and sensing configurations for configuring the one or more other RAN entities (e.g., BSs) to be a sensing receiver.• Execute sensing admission control, which identifies whether the identified or selected RAN entities have the available sensing resources for the requested sensing service (e.g., sensing requirements) and determine a sensing resources configuration for the identified or selected RAN entities. The sensing resources configuration includes 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 multistatic method realizes.• Transmit a sensing session establishment request to the one or more RAN entities to establish a sensing session, according to the selected sensing method, including one or more of the following: a sensing configuration for each respective selected RAN entity for configuring the respective RAN 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) 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 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 as well as for transmitting sensing measurements and / or sensing data from the RAN entity (or RAN entities) to the SeMF, that belong to the same sensing session.

[0070] In the context of the same sensing session, one or more monostatic sensing operations or one or more multistatic sensing operations are initiated. Also, the same RAN entity is optionally involved at one or more monostatic sensing operations and at one or more multistatic sensing operations. In addition, in some implementations, a RAN entity is identified or selected as a sensing transmitter and is configured based on the sensing configuration to transmit sensing signals and / or identified or selected as a sensing receiver and can be configured based on a sensing configuration to receive sensing signals. Each of the one or more RAN entities 106 of the system are any suitable 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).

[0071] Each RAN entity 106 is operable to:• 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 also includes 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 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 configuration received from the SeMF.

[0072] The interaction between the SeMF and the RAN entity(-ies) occur through direct interface or though the AMF. The AMF routes the messages between a RAN entity (e.g., an access node) and the SeMF transparently, over an 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), is utilizable as a transport protocol for transporting sensing protocol messages over the NG-C interface.

[0073] In some implementations, admission control is performed by a RAN entity. The SeMF provides to the RAN entity, 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) that allows the one or more RAN entities to determine the required resources for the sensing session. The RAN entity configured as a sensing transmitter having a sensing transmitting role, for example, when the SeMF selects the RAN entity to be involved in a bistatic sensing operation, provides its sensing resource configuration (e.g. sensing signal frequency, bandwidth, the timing when a sensing signal is transmitted by the RAN entity) and / or the sensing session configuration to: one or more RAN entities configured as a sensing receiver having a sensing receive role for the respective sensing session 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.

[0074] Although described herein as one or more RAN entities utilized in sensing, the methods and processes described are equally applicable to one or more UEs. Such UEs are similarly configured to operate as sensing devices. UEs may be configured to operate assensing transmitters or sensing receivers, or both sensing transmitters and sensing receivers.

[0075] FIG. 2 is a schematic diagram showing components of one or more of the example implementations, referred to generically as a processing system 200. A processing system such as that shown in FIG. 2 is utilized to implement functionality of any of the network functions referred to above. Thus, a processing system such as the processing system 200 is utilized to implement functionality of the SeMF 134. Similarly, a processing system is utilized to implement functionality of the CHF 110.

[0076] The processing system 200 includes a processor 202, a memory 204 coupled to the processor 202 and including RAM 206 and a ROM 208, and, optionally, a user input 210 and a display 218. The processing system 200 includes one or more network or apparatus interfaces 210 for connection to a network or apparatus, e.g., a modem that is wired or wireless. The one or more network or apparatus interfaces 216 also operate as a connection to other apparatus such as device or apparatus which is not network side apparatus. Thus, direct connection between devices or apparatus without network participation is possible.

[0077] The processor 202 is connected to each of the other components in order to control operation thereof.

[0078] The memory 204 includes a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD). The ROM 208 of the memory 204 stores, amongst other things, an operating system 212 and optionally stores software applications 214. The RAM 206 of the memory 204 is used by the processor 202 for the temporary storage of data. The operating system 212 include processor-executable code which, when executed by the processor 202 implements aspects of the methods and processes described herein.

[0079] The processor 202 is any suitable processor such as a microcontroller, a plurality of microcontrollers, a processor, or a plurality of processors. The processing system 200 is any of a standalone computer, a server, a console, or a network thereof.

[0080] In some example implementations, the processing system 200 is associated with external software applications. These applications are optionally stored on a remote server device or apparatus and optionally run partly or exclusively on the remote server device or apparatus. These applications are termed cloud-hosted applications. The processing system 200 is optionally in communication with the remote server device or apparatus to utilizethe software application stored there.

[0081] Optionally, the processing system 200 is a cloud-based system that delivers services via a network such as the internet.

[0082] FIG. 3 is a flowchart showing a method or process in accordance with one example. The method or process is performed by the SeMF 134. At 302, a sensing service request is received at the SeMF 134 from a sensing service client. The sensing service request is a request for a sensing service supported or provided by SeMF 134. The sensing service request includes information related to the sensing service that is requested by the sensing service client. Example information related to the sensing service that is included in a sensing service request includes at least one of: an indication of a sensing service type for the sensing service; information indicating sensing requirements for the sensing service; an indication of a quality of service for the sensing service; and information indicating a sensing area for the sensing service.

[0083] A sensing method (e.g., a sensing mode) is selected at 304 based, at least in part, on the information related to the sensing service (e.g., as included in the operation 302). The operation 304 involves selecting between one of: monostatic sensing for the sensing service, in which a first RAN entity is used for transmission and reception of radio signals used for sensing, and multistatic sensing (e.g., bistatic sensing), in which one selected RAN entity is used for transmission of radio signals for sensing and one or more other selected RAN entities are used for reception of radio signals used for sensing.

[0084] Sensing configuration information is sent from the SeMF 134 to the RAN entities at 306. For example, if monostatic sensing is selected at 304, the SeMF 134, at 306, sends to the first RAN entity utilized for transmission and reception of radio signals used for sensing, a sensing configuration for the first RAN entity. Such a sensing configuration includes at least one of a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration. For multistatic (e.g., bistatic) sensing selected at 304, the SeMF 134 sends, at 306, to the one selected RAN node utilized for transmission of radio signals used for sensing, a sensing configuration for the one selected RAN node. Such a sensing configuration includes at least one of a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration.

[0085] Moreover, in the event that multistatic sensing is selected at 304, sending the sensing configuration at 306 also includes sending, to each respective other RAN nodesused for reception of radio signals, a sensing configuration for the respective other RAN node(s). Alternatively, the sensing configuration of the respective other RAN node(s) is sent by one of the RAN nodes (e.g., the other node in the bistatic case), rather than by the SeMF 134. In common with the sensing configurations referred to above, the sensing configuration for each respective other RAN node includes at least one of a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration.

[0086] FIG. 4 is a flowchart showing a method or process in accordance with an example. The method or process is implemented at the sensing service client as referred to above. A sensing session is initiated at 402. The initiation of the sensing session is part of the sensing configuration at 306 referred to above. In some examples, initiating of the sensing session is implemented only following a validation process that determines that the respective RAN entity is operable to initiate the sensing session for the requested sensing service. Initiating the sensing session at 402 includes sending, to the respective RAN entity, a request for that RAN entity to initiate sensing.

[0087] Sensing data is received at 404. The sensing data is received from the first selected RAN node used for transmission and reception of radio signals for sensing, in the sensing mode in which the first selected RAN node is configured for monostatic sensing.Alternatively, the sensing data is received from the one or more other selected RAN nodes utilized for reception of radio signals used for sensing in the sensing mode in which the first RAN node and the one or more other RAN nodes are configured for multistatic sensing.

[0088] The sensing data is processed in some way, as referred to below. For example, the sensing data is processed at the respective RAN or at the SeMF 134, with processed data being provided to the sensing service client in response to the original request from the sensing service client.

[0089] FIG. 5 is a flowchart showing a method or process in accordance with an example implementation. The method or process is implemented at one of the one or more RAN entities 106 of the system.

[0090] A sensing configuration for a sensing service is received at a RAN entity at 502, from the SeMF 134. The sensing configuration is sent at 306 as described with reference to FIG. 3 and is used by the RAN entity to configure itself for one of monostatic sensing forthe sensing service in which the RAN node is a first selected RAN node utilized for transmission and reception of radio signals used for sensing, and multistatic sensing in which the RAN node is one selected RAN node utilized for transmission of radio signals for sensing or one of one or more other selected RAN nodes utilized for reception of radio signals used for sensing.

[0091] The RAN entity (e.g., the RAN node) configures itself at 504 in accordance with the sensing configuration received at 502.

[0092] The RAN entity initiates the sensing operation at 506 for the sensing service. As described herein, sensing is by the transmission of sensing signals (e.g., radio signals) for sensing (e.g., by one RAN entity) and the reception of radio signals for sensing (e.g., by the same RAN entity, or one or more different RAN entities).

[0093] FIG. 6 is a flowchart showing a method or process in accordance with an example implementation. The method or process is implemented at one of the one or more RAN entities.

[0094] In some example implementations, sensing signals (e.g., radio signals) for sensing, as received by the respective RAN entity, are processed at 602 to generate sensing data. In other example implementations, the sensing signals are not processed.

[0095] The data is provided at 604 from the respective RAN entity to the SeMF 134. The data is the received sensing signals or other sensing data in the case in which the sensing signals are not processed at the RAN entity. Alternatively, the data is sensing data as processed at 602 in the case in which the sensing signals are proceed at 602 and thus, the data provided at 604 is the output of the processing at 602.

[0096] FIG. 7 is a flowchart showing a method or process in accordance with one example of an implementation. The method or process is performed by the SeMF 134. At 702, sensing service information is received. The sensing service information includes an identification and location information to perform the sensing session. The identification is the ID of the UE 102, for example, in the case in which the sensing service client, such as the UE 102, requests a sensing session or for which a sensing session is provided. The information is received along with a sensing session request or is received in response to, for example, the SeMF 134 sending a request to the sensing service client, such as the UE 102.

[0097] The sensing session is performed at 704. The sensing session is performed as setout hereinabove with reference to FIG. 3 through FIG. 6 and the associated description and includes the selection and setup of the sensing configuration in addition to carrying out the sensing.

[0098] Network resource utilization information is obtained at 706. The network resource utilization information includes one or more parameters of the sensing session. In some implementations, the parameters of the sensing session are obtained by sensing or monitoring network resource utilization by the SeMF 134 to use in charging for the sensing service. In particular implementations, the SeMF 134 determines a change in network resource utilization based the sensing or monitoring, and based on the change, proceeds to 708. Thus, in these particular implementations, specific events that are determined by sensing or monitoring by the SeMF 134, cause the process to continue at 708. Examples of these specific events include changes in a quality of service of the sensing session, a change in the sensing method utilized, a change in resources allocated to the sensing session, a change in bandwidth utilized, and a change in number of antenna elements utilized.

[0099] In other implementations, the parameters are obtained upon receipt from, for example, a UE or base station entity. For example, a UE or a base station provides charging related information to the SeMF 134. The UE or base station provides the charging related information in the event that: the UE conducts UE-based sensing and selects sensing related resources; or the UE is, for example, a Server-UE that supports and coordinates sensing procedures involving the UE; or the base station selects sensing related resources used by the same or another base station, for example, for monostatic or multistatic base station based sensing, or bistatic RAN and UE sensing.

[0100] A charging sensing service request is generated at 708. The charging sensing service request is a charging sensing session request or a charging sensing event request. In both cases, the charging sensing service request includes the one or more parameters of the sensing session or event.

[0101] The charging sensing service request is sent at 710 to the CHF 110. Thus, the parameters of the sensing session that are utilized to determine the charging rate are sent to the CHF 110. The charging sensing service request is a request for the CHF 110 to store the service-related charging data to generate a charging data record that is provided to thebilling domain to bill for the service.

[0102] The SeMF 134 receives a response from the CHF 110 at 712. The response includes an acknowledgement that the sensing related charging data is stored. In example implementations, the response also includes charging information related to the sensing service client, such as the UE 102. The charging information related to the sensing service client includes information associated with the ID of the sensing service client. Examples of such information include expiry of a time limit for the sensing service, expiry of a data volume limit for the sensing service, a sensing volume quota threshold, and a sensing time quota threshold.

[0103] In the example implementations in which the response includes the charging information related to the sensing service client, the SeMF 134 prepares and sends sensing configuration information to configure the sensing session at 714. For example, the SeMF 134 sends configuration information to one or more of the network resources, including the RAN entities, to change the quality of service of the sensing session, or change the sensing method utilized, or change the network resources utilized, or stop the sensing session, or identify a release of the sensing session, or send a notification to the sensing service client, or any combination thereof.

[0104] FIG. 8 is a flowchart showing a method or process in accordance with one example of an implementation. The method or process is performed by the CHF 110. At 802, the charging sensing service request is received at the CHF 110. The charging sensing service request is a charging sensing session request or a charging sensing event request. In both cases, the charging sensing service request includes the network resource utilization information including the one or more parameters of the sensing session to use in charging for the sensing service.

[0105] The CHF 110 determines a charging rate for the sensing service based on the parameters of the sensing session, a charging policy for the sensing service, and a specific tariff (if any) to the sensing service client, e.g., the UE 102. The CHF 110 generates the charging sensing service record at 804.

[0106] The CHF 110 sends a response at 806. The response includes an acknowledgement that the sensing related charging data is stored. In example implementations, the response also includes the charging information related to the sensing service client, such as the UE 102. The charging information related to the sensing serviceclient includes information associated with the ID of the sensing service client, such as expiry of a time limit for the sensing service, expiry of a data volume limit for the sensing service, a sensing volume quota threshold, or a sensing time quota threshold. Optionally, the charging information related to the sensing service client is sent to the SeMF 134 to reconfigure the sensing session based on the charging information.

[0107] The CHF 110 also sends the charging sensing service record to the billing domain 112 at 808 to charge based on the identification of the sensing service client and the sensing service provided.

[0108] FIG. 9 shows signaling and operations of a procedure in accordance with an example implementation. Signaling (e.g., messages) sent between a UE, such as the UE 102, a SeMF 134, a UDR 900 at which the UDM stores subscription data, and a CHF 110, are also illustrated. The UE may be a UE 102 that is a sensing client or consumer that requests the sensing session and that is optionally involved in performing the sensing. Alternatively, the UE may be a UE that is not the sensing client but involved in performing the sensing. Alternatively or together with one or more UEs, one or more BSs, such as a gNB, may be involved in the sensing session. It should be noted that the principles of the procedure are applicable to other communication systems.

[0109] In the example shown in FIG. 9, a sensing session is carried out. The sensing session is requested, either by the UE 102 or by the SeMF 134. One or more RAN nodes (BSs), or one or more UEs, or both, may be involved in performing the sensing. The one or more RAN nodes (BSs) and or one or more UEs be selected and configured by the SeMF for a sensing session. In the event that the UE 102 requests the sensing session as shown in 901(a), information including the ID of the UE 102 and location information of the UE 102 is provided by the UE 102 to the SeMF 134 to facilitate retrieval of information to initiate the sensing session. The location information may be retrieved by the UE requesting its’ location from a Location Management Function (LMF). In this example, the UE 102 is the sensing client or consumer that requests the sensing session. Optionally, the same UE 102 may be involved in performing the sensing to receive or transmit sensing signals.

[0110] Alternatively, the location or position of the UE is retrieved by the SeMF, after receipt of the ID of the UE from the UE, via a LMF.

[0111] Alternatively, the SeMF 134 transmits the sensing session request to a UE at901(b) and receives a response to the sensing session request from the UE. The sensing session request is a request for the UE to establish a sensing session with the SeMF and perform sensing. The response includes an indication that the UE will participate in the sensing session, and the ID and location information indicative of a location or position of the UE. The location or position of the UE is either requested to the UE or is retrieved by the SeMF, after receipt of the ID of the UE from the UE, via a LMF. The UE in this alternative is a UE that is involved in performing the sensing to receive or transmit sensing signals and is not the sensing client. In the response, the UE indicates acceptance or rejection of the sensing session request.

[0112] In the case in which the UE 102 does not have the capability to request or accept the sensing service, an AF is utilized as a proxy for that UE 102 emulating the application process running at the UE, requesting the sensing information. Information including the ID and location of the UE 102 is still provided to the SeMF 134.

[0113] At 902, the SeMF 134 checks in the UDR 902 to confirm that the UE 102 is registered to the communication network and thus is authorized to access the sensing services. This verification is carried out before the instantiation of the sensing session with the UE 102.

[0114] In the example in 901(a) in which the UE is involved in performing the sensing to receive or transmit sensing signals, and in the alternative described above with reference to 901(b), the SeMF 134 sends configuration information or signals to the UE to configure the UE for sensing and to begin the sensing session at 903.

[0115] In the alternative in which one or more BSs, such as a gNB, are involved in the sensing session, the SeMF 134 sends configuration information or signals to the BS to configure for sensing and to begin the sensing session.

[0116] The sensing session is carried out at 904. The sensing session may include one or more UEs involved in performing the sensing by receiving or transmitting sensing signals, a UE as a requesting or sensing client in which case the UE is optionally involved in performing the sensing, or one or more BS (e.g., gNB) performing the sensing.

[0117] At 905, the SeMF 134 monitors network resource utilization of the sensing session. One or more parameters are sensed or detected to inform the CHF 110 about the charging related information related to that UE 102. The one or more parameters that are sensed or detected include any one or combination of:• number of transmissions during the sensing session (e.g., transmissions using reference signals);• amount of data (e.g., expressed in bytes or bits-per-second) transmitted / received to perform the sensing measurements;• amount of resources (e.g., number of RBs, or number of reference signals) used by the BS (e.g., gNB) to transmit or receive sensing signals;• amount of resources (e.g., number of RBs, or number of reference signals) used by the UE requesting the sensing service to other UEs in case of UE-based sensing methods;• total duration time of the sensing session (e.g., in msecs or seconds);• active transmission time (e.g., in msecs or seconds);• active reception time (e.g., in msecs or seconds);• total bandwidth used (e.g., in Hz);• carrier Frequency (e.g., FR1, FR2, FR3);• number of antenna elements;• power consumption (e.g., in watts);• processing time and / or processing resources that have been used at the network side;• sensing session QoS requirements such as o sensing accuracy e.g., Positioning accuracy [meters] (horizontal / vertical), Velocity accuracy [m / s] (horizontal / vertical)• sensing resolution e.g., Range resolution [meters], velocity resolution [m / s]• maximum sensing latency (seconds)• sensing refresh rate (seconds); and• Quality of the extracted sensing information, determined by matching the sensing measurements with the other measurements incoming to the SeMF by other measuring entities.

[0118] At 906, the SeMF 134 transmits a charging sensing session request, with the sensed or detected parameters as well as UE 102 ID to evaluate the charging rate. By this request, the SeMF 134 requests the CHF 110 to store sensing session related charging data for Charging Data Record (CDR) generation purposes. The request message is sent with the establishment of the session. Alternatively, or additionally, the request message is sent during the operation of the session, for example, in response to an expiration of a timer to report information, specific duration of sensing session, specific resources usage, or other suitable events.

[0119] At 907, the CHF 110 determines the charging rate to the UE 102, depending onthe charging policy of the operator for the sensing service, the specific tariff dedicated to the UE 102 and on the evaluation of the one or more parameters sensed or detected by the SeMF 134 while monitoring the network resource utilization for the sensing session. The CHF 110 generates the charging sensing session record. The CHF 110 stores received information and determines whether a CDR is generated or not depending on a charging data record generation configuration.

[0120] At 908 the CHF 110 transmits the charging sensing session response to the SeMF 134 with an indication that the sensing related charging data has been stored. Based on the response, the SeMF 134 is notified either that the sensing related charging data has been successfully stored or not. In the event that the sensing related charging data has not been successfully stored, a retransmission is scheduled, depending on the cause of the rejection or failure cause.

[0121] In addition, charging information related to the ID of the UE 102 and the sensing session ID is included in the charging sensing session response. This information is utilized by the SeMF 134 to configure or reconfigure the sensing session. Some examples of charging related information include: expiry of time limit for sensing; expiry of data volume limit for sensing; sensing volume quota threshold; and sensing time quota threshold.

[0122] Based on this charging related information received at the SeMF 134, the SeMF 134 configures or reconfigures the sensing session by one or more of: adapting the QoS of the sensing procedure (upgrade, downgrade); changing the sensing method (e.g., to BS-based); adapting resources allocated to the sensing procedure; stopping / releasing the sensing procedure; planning the release of the sensing procedure; and sending a notification to the sensing client.

[0123] Optionally, at 909, the SeMF 134 informs the UE 102 that the sensing session is released. Alternatively, the sensing session is considered closed after a previously agreed waiting time window. Optionally, the sensed or detected parameters are included in the message informing of session release.

[0124] The operations 905 through 908 are optionally repeated, for example, at regular time intervals until termination of the sensing session. At 910, the SeMF 134 sends a message to the CHF to release and store the charging sensing session record for that session in response to or at the sensing session termination.

[0125] At 911, the CHF 110 releases and stores the charging sensing session record.

[0126] At 912 the CHF 110 transmits the charging sensing session response to theSeMF 134 with an indication that the sensing related charging data has been stored. The CDR is generated and sent to the billing domain to charge for the sensing session.

[0127] The session-based charging referred to with reference to FIG. 9 is applicable also for the case that another consumer (e.g., an application function) requests a sensing session. The application function in such a case is a third -party application server (trusted or not trusted to the PLMN) and the sensing session is requested via the NEF 118.

[0128] FIG. 10 shows signaling and operations of a procedure in accordance with an example implementation. Signaling (e.g., messages) sent between a UE 102, a SeMF 134, a UDR 1000 at which the UDM stores subscription data, and a charging function 110, are illustrated. It should be noted, however, that the principles of the procedure are applicable to other communication networks.

[0129] In the example shown in FIG. 10, a sensing event occurs. In one example shown at 1001, the sensing event is shown as a one-time sensing request either by the UE 102 or by the SeMF 134 and accepted by the UE 102. Alternatively, the sensing event is a change or adaptation to the sensing procedure at 1002. Examples of such sensing events include a change of Sensing QoS (e.g., as determined or decided at the SeMF 134), the addition of one more UEs to support the sensing procedure (added either as a transmitter or as a receiver of sensing signals), or any other suitable information or parameter.

[0130] The sensing event is detected or determined at the SeMF 134 at 1003. In response to detection or determination of the sensing event at 1003, the SeMF 134 sends a charging sensing event request at 1004 to the CHF 110. The charging sensing event request includes the ID of the UE 102 and sensing service configuration information related to the event, for example, the updated QoS level, updated bandwidth, increase or decrease of number of used UEs in the sensing procedure, or any other suitable sensing service configuration information.

[0131] At 1005, the CHF 110 generates the charging sensing event record based on thesensing event. The CHF 110 stores received information to generate a CDR.

[0132] At 1006 the CHF 110 transmits the charging sensing event response to the SeMF 134 with an indication that the sensing related charging data has been stored. The CHF also sends the CDR to the billing domain to charge for the sensing services.

[0133] Optionally, charging information related to the ID of the UE 102 and the sensing event is included in the charging sensing event response. This information is utilized by the SeMF 134 to configure or reconfigure the sensing event. Some examples of charging related information include: expiry of time limit for sensing; expiry of data volume limit for sensing; sensing volume quota threshold; and sensing time quota threshold.

[0134] FIG. 11 shows signaling and operations of a procedure in accordance with another example implementation. Signaling (e.g., messages) sent between a user equipment 1140, such as the UE 102 referred to above, or a UE server or other UE, a base station (BS) 1150, which in this example is a gNB, a SeMF 134, a UDR 1100 at which the UDM stores subscription data, and a charging function (CHF) 110, are illustrated. It should be noted, however, that the principles of the procedure are applicable to other communication systems. The procedure shown in FIG. 11 is applicable to both sessionbased charging and event-based charging.

[0135] In the implementation shown in FIG. 11, the sensing session is established and carried out at 1101. In one example of the implementation shown in FIG. 11, the user equipment 1140 conducts UE-based sensing and selects sensing related resources, rather than the BS or the SeMF selecting sensing related resources. In another example, the user equipment 1140 is a Server-UE that supports and coordinates sensing procedures involving the UE. In still another example, the BS selects sensing related resources used by the same or another base station, for example, for monostatic or multistatic base station-based sensing, or bistatic RAN and UE sensing.

[0136] In the example in which the BS 1150 selects sensing related resources, the BS 1150 provides the network resource utilization information of the sensing session, including the one or more parameters at 1102(a) and the network resource utilization information including the one or more parameters are reported by the BS 1150 to the SeMF134 at 1103(a). Although shown as a BS 1150 reporting the one or more parameters, optionally more than one BS reports the one or more parameters. In addition, the BS 1150 sends UE-related information if this information is provided by the user equipment 1140 to the BS 1150, via Radio Resource Control (RRC) messages.

[0137] In the examples in which the user equipment 1140 conducts UE-based sensing or supports and coordinates sensing procedures, the user equipment 1140 provides the network resource utilization information of the sensing session, including the one or more parameters at 1102(b) and the network resource utilization information including the one or more parameters are reported by the user equipment 1140 to the SeMF 134 at 1103(b). Although shown as a user equipment 1140 reporting the one or more parameters, optionally, more than one user equipment device reports the one or more parameters.

[0138] Rather than reporting the network resource utilization information including the one or more parameters, to the SeMF 134 as shown in FIG. 11, in other implementations, the network resource utilization information including the one or more parameters is reported directly to the CHF 110, rather than the SeMF 134 as shown in FIG. 11.

[0139] At 1104, the SeMF 134 transmits a charging sensing session request, with the one or more parameters, along with the user equipment ID for charging purposes.

[0140] At 1105, the CHF 110 determines the charging rate to the user equipment 1140, depending on the charging policy of the operator for the sensing service, the specific tariff dedicated to the user equipment 1140 and on the evaluation of the one or more parameters sensed or detected by the SeMF 134 while monitoring the network resource utilization for the sensing session. The CHF 110 generates the charging sensing session record. The CHF 110 stores received information and determines whether a CDR is generated or not depending on a charging data record generation configuration.

[0141] At 1106 the CHF 110 transmits the charging sensing session response to the SeMF 134 with an indication that the sensing-related charging data has been stored.

[0142] The procedures illustrated and described herein are applicable for online or offline charging.

[0143] For the procedures illustrated in FIG. 9 through FIG. 11, the AMF is not illustrated for the purpose of simplicity. It will be appreciated, however, that the messages or signals between the SeMF and the UE and BS are transmitted through the AMF.

[0144] implementations of the present invention including functions, processes, and operations, 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 implementation, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this application, a “memory” or “computer-readable medium” may be any non-transitory media or means that contains, stores, communicates, propagates or transports the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0145] Reference to, where relevant, “computer-readable medium”, “computer program product”, “tangibly embodied computer program”, or a “processor” or “processing circuitry” should be understood to encompass not only computers having differing architectures such as single / multi-processor architectures and sequencers / parallel architectures, but also specialized 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, or code 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 processor or configured or configuration settings for a fixed function device / apparatus, gate array, programmable logic device / apparatus.

[0146] The functions, processes, and operations described herein may be performed in a different order, or may be performed concurrently with each other, or a combination thereof. Furthermore, one or more of the functions, processes, and operations may be optional or may be combined. It will be appreciated that the flow diagrams shown in FIG.3 through FIG. 8 and the procedures illustrated in FIG. 9 through FIG. 11 are examples only. Various operations and processes depicted therein may be omitted, may be reordered, may be combined, or a combination of reordered and combined.

[0147] Advantageously, sensing in a wireless communication system, for example, to obtain awareness of a scene is carried out and charging sensing session or event records are generated based on network resource utilization. Additional information related to the sensing service client is utilized to configure or reconfigure the sensing service.

[0148]

[0149] The scope of the claims should not be limited by the implementations set forth in the examples but should be given the broadest interpretation consistent with the description as a whole.

Claims

Claims1. A processing system comprising: at least one processor; and at least one memory storing instructions of a sensing management function, wherein execution of the instructions by the at least one processor causes the processing system to at least: establish a sensing session with one or more devices of a wireless communication system; determine network resource utilization information comprising one or more parameters of the sensing session; generate a charging sensing session request including the network resource utilization information; send to a charging function, the charging sensing session request to determine a charging rate for the sensing session based at least on the network resource utilization information.

2. The processing system according to claim 1, wherein execution of the instructions by the at least one processor causes the processing system to receive, from a sensing service client of the wireless communication system, a sensing session request to perform the sensing session, prior to establishing the sensing session.

3. The processing system according to claim 2, wherein execution of the instructions by the at least one processor causes the processing system to: receive a response from the charging function indicating receipt of the network resource utilization information, along with charging information related to the sensing service client; utilize the charging information related to the sensing service client to determine sensing configuration information to configure the sensing session.

4. The processing system according to claim 3, wherein the charging information related to the sensing service client comprises at least one of: expiry of a time limit for the sensing session; expiry of a data volume limit for the sensing session;a sensing volume quota threshold; or a sensing time quota threshold.

5. The processing system according to any one of claim 3 or claim 4, wherein the sensing configuration information to configure the sensing session comprises information to configure at least one of: adjusting the quality of service of the sensing session; changing the sensing method utilized; changing resources allocated to the sensing session; stopping the sensing session; identifying a release of the sensing session; or sending a notification to the sensing service client.

6. The processing system according to any one of claims 1 to 5, wherein the one or more parameters comprise at least one of: a number of transmissions during the sensing session; amount of data including data transmitted and data received to perform sensing measurements; amount of resources utilized to transmit or receive sensing signals; a duration time of the sensing session; an active transmission time; an active reception time; total bandwidth utilized; a carrier frequency utilized; a number of antenna elements utilized; power consumption; processing time or processing resources utilized at the network; sensing session quality of service; or quality of extracted sensing information, determined by comparing the sensing measurements with measurements from other measuring entities.

7. The processing system according to any one of claims 1 to 6, wherein the one or more parameters include quality of the sensing session comprising at least one of: sensing accuracy;sensing resolution; sensing range; sensing latency; or sensing refresh rate.

8. The processing system according to any one of claims 1 to 7, wherein execution of the instructions by the at least one processor causes the processing system to send the charging sensing session request upon establishment of the sensing session.

9. The processing system according to any one of claims 1 to 8, wherein execution of the instructions by the at least one processor causes the processing system to send the charging sensing session request in response to one of: expiry of a time period after establishment of the sensing session; a determination that a duration of the sensing session meets a threshold; or a determination of use of a particular network resource or resources.

10. The processing system according to any one of claims 1 to 9, wherein execution of the instructions by the at least one processor causes the processing system to discontinue the sensing session.

11. The processing system according to claim 10, wherein execution of the instructions by the at least one processor causes the processing system to send to the charging function, an indication of completion of the sensing session.

12. A processing system comprising: at least one processor; and at least one memory storing instructions of a charging function, wherein execution of the instructions by the at least one processor causes the processing system to at least: receive a charging sensing session request including network resource utilization information comprising one or more parameters of a sensing session; based on the one or more parameters, generate a charging sensing session record for the sensing session;send the charging sensing session record to a billing system to charge based on the sensing session.

13. The processing system of claim 12, wherein execution of the instructions by the at least one processor causes the processing system to store sensing session related charging data including the one or more parameters of the sensing session prior to generating the charging sensing session record.

14. The processing system of claim 12 or claim 13, wherein execution of the instructions by the at least one processor causes the processing system to: determine a charge rate of the sensing session based on the one or more parameters of the sensing session, wherein the charging sensing session record includes the charge rate of the sensing session.

15. The processing system according to any one of claims 12 to 14, wherein the one or more parameters comprise one or more of: a number of transmissions during the sensing session; amount of data including data transmitted and data received to perform sensing measurements; amount of resources utilized to transmit or receive sensing signals; a duration time of the sensing session; an active transmission time; an active reception time; total bandwidth utilized; a carrier frequency utilized; a number of antenna elements utilized; power consumption; processing time or processing resources utilized at the network; sensing session quality of service; or quality of extracted sensing information, determined by comparing the sensing measurements with measurements from other measuring entities.

16. The processing system according to any one of claims 12 to 15, wherein the one or more parameters includes quality of the sensing session comprising at least one of: sensing accuracy; sensing resolution; sensing range; sensing latency; or sensing refresh rate.

17. The processing system of any one of claims 12 to 16, wherein execution of the instructions by the at least one processor causes the processing system to: send a response to a sensing management function, the response indicating receipt of the one or more parameters of the sensing session, along with charging information related to a sensing service client.

18. The processing system according to claim 17, wherein the charging information related to the sensing service client comprises at least one of: expiry of a time limit for the sensing session; expiry of a data volume limit for the sensing session; a sensing volume quota threshold; or a sensing time quota threshold.

19. The processing system according to any one of claims 12 to 18, wherein the charging sensing session record is generated in response to receipt of an indication of completion of the sensing session.

20. The processing system according to any one of claims 12 to 19, wherein the charging sensing session request includes an indication of a change to the one or more parameters.

21. The processing system according to claim 20, wherein execution of the instructions by the at least one processor causes the processing system to generate the charging sensing service record for the sensing session based on the change to the one or more parameters.

22. The processing system according to any one of claims 12 to 21, wherein execution of the instructions by the at least one processor causes the processing system to send to asensing management function, charging information related to the sensing service client to configure the sensing session based on the charging information.

23. A processing system comprising: at least one processor; and at least one memory storing instructions of a sensing management function, wherein execution of the instructions by the at least one processor causes the processing system to: determine a change to a sensing service configuration based on a sensing event; generate a charging sensing event request including an indication of the change to the sensing service configuration; send, to a charging function, the charging sensing event request to determine charging information.

24. The processing system according to claim 23, wherein the change to the sensing service configuration based on the sensing event comprises a change to at least one of: a quality of service of the sensing service; the sensing method utilized; resources allocated to the sensing service; bandwidth utilized; or number of antenna elements utilized.

25. A processing system comprising: at least one processor; and at least one memory storing instructions of a sensing management function, wherein execution of the instructions by the at least one processor causes the processing system to: receive from one of a user equipment and base station, charging-related information including network resource utilization information comprising one or more parameters of a sensing session; send, to a charging function, a charging sensing session request including the network resource utilization information to determine charging information for the sensing session.

26. A method of a sensing management function for a communication network, the method comprising: establishing a sensing session with one or more devices of a wireless communication system; determining network resource utilization information comprising one or more parameters of the sensing session; generating a charging sensing session request including the network resource utilization information; sending to a charging function, the charging sensing session request to determine a charging rate for the sensing session based at least on the network resource utilization information.

27. The method according to claim 26, further comprising: receiving, from a sensing service client of the wireless communication system, a sensing session request to perform the sensing session, prior to establishing the sensing session.

28. The method according to claim 27, further comprising: receiving a response from the charging function indicating receipt of the network resource utilization information, along with charging information related to the sensing service client; utilizing the charging information related to the sensing service client to determine sensing configuration information to configure the sensing session.

29. The method according to claim 28, wherein the charging information related to the sensing service client comprises at least one of: expiry of a time limit for the sensing session; expiry of a data volume limit for the sensing session; a sensing volume quota threshold; or a sensing time quota threshold.

30. The method according to any one of claim 28 or claim 29, wherein the sensing configuration information to configure the sensing session comprises information to configure at least one of: adjusting the quality of service of the sensing session; changing the sensing method utilized; changing resources allocated to the sensing session; stopping the sensing session; identifying a release of the sensing session; or sending a notification to the sensing service client.

31. The method according to any one of claims 26 to 30, wherein the one or more parameters comprise at least one of: a number of transmissions during the sensing session; amount of data including data transmitted and data received to perform sensing measurements; amount of resources utilized to transmit or receive sensing signals; a duration time of the sensing session; an active transmission time; an active reception time; total bandwidth utilized; a carrier frequency utilized; a number of antenna elements utilized; power consumption; processing time or processing resources utilized at the network; sensing session quality of service; or quality of extracted sensing information, determined by comparing the sensing measurements with measurements from other measuring entities.

32. The method according to any one of claims 26 to 31, wherein the one or more parameters include quality of the sensing session comprising at least one of: sensing accuracy; sensing resolution; sensing range; sensing latency; orsensing refresh rate.

33. The method according to any one of claims 26 to 32, further comprising sending the charging sensing session request upon establishment of the sensing session.

34. The method according to any one of claims 26 to 33, further comprising sending the charging sensing session request in response to one of: expiry of a time period after establishment of the sensing session; a determination that a duration of the sensing session meets a threshold; or a determination of use of a particular network resource or resources.

35. The method according to any one of claims 26 to 34, further comprising discontinuing the sensing session.

36. The method according to claim 35, further comprising sending to the charging function, an indication of completion of the sensing session.

37. A computer program comprising instructions, wherein execution of the computer program by at least one processor of a processing system causes the processing system to perform the method of any of claims 26 to 36.

38. A computer-readable medium comprising instructions which, when executed by least one processor of a processing system causes the processing system to perform the method of any of claims 26 to 36.

39. A method of a charging function for a communication network, the method comprising: receiving a charging sensing session request including network resource utilization information comprising one or more parameters of a sensing session; based on the one or more parameters, generating a charging sensing session record for the sensing session; sending the charging sensing session record to a billing system to charge based on the sensing session.

40. The method of claim 39, further comprising storing sensing session related charging data including the one or more parameters of the sensing session prior to generating the charging sensing session record.

41. The method of claim 39 or claim 40, further comprising determine a charge rate of the sensing session based on the one or more parameters of the sensing session, wherein the charging sensing session record includes the charge rate of the sensing session.

42. The method according to any one of claims 39 to 41, wherein the one or more parameters comprise one or more of: a number of transmissions during the sensing session; amount of data including data transmitted and data received to perform sensing measurements; amount of resources utilized to transmit or receive sensing signals; a duration time of the sensing session; an active transmission time; an active reception time; total bandwidth utilized; a carrier frequency utilized; a number of antenna elements utilized; power consumption; processing time or processing resources utilized at the network; sensing session quality of service; or quality of extracted sensing information, determined by comparing the sensing measurements with measurements from other measuring entities.

43. The method according to any one of claims 39 to 42, wherein the one or more parameters includes quality of the sensing session comprising at least one of: sensing accuracy; sensing resolution; sensing range; sensing latency; orsensing refresh rate.

44. The method of any one of claims 39 to 43, further comprising: sending a response to a sensing management function, the response indicating receipt of the one or more parameters of the sensing session, along with charging information related to a sensing service client.

45. The method according to claim 44, wherein the charging information related to the sensing service client comprises at least one of: expiry of a time limit for the sensing session; expiry of a data volume limit for the sensing session; a sensing volume quota threshold; or a sensing time quota threshold.

46. The method according to any one of claims 39 to 45, wherein the charging sensing session record is generated in response to receipt of an indication of completion of the sensing session.

47. The method according to any one of claims 39 to 46, wherein the charging sensing session request includes an indication of a change to the one or more parameters.

48. The method according to claim 47, further comprising generating the charging sensing service record for the sensing session based on the change to the one or more parameters.

49. The method according to any one of claims 39 to 48, further comprising sending to a sensing management function, charging information related to the sensing service client to configure the sensing session based on the charging information.

50. A computer program comprising instructions, wherein execution of the computer program by at least one processor of a processing system causes the processing system to perform the method of any of claims 39 to 49.

51. A computer-readable medium comprising instructions which, when executed by least one processor of a processing system causes the processing system to perform the method of any of claims 39 to 49.

Images