Methods and system for distributed sensing

Abstract

An implementation of sensing management function (SeMF) 320 of a communication network includes determining sensing data processing functions (SDPFs) 502 for a sensing session for a sensing service, s

Description

TECHNOLOGICAL FIELD

[0001] The present disclosure relates generally to telecommunications and, in particular, to integrated sensing and communication. BACKGROUND

[0002] A telecommunications system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations and / or other nodes by providing carriers between the various entities involved in the communications path. A telecommunications system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, video, electronic mail (email), text message, multimedia and / or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.

[0003] In a wireless telecommunications system, at least a part of a communication session between at least two stations occurs over a wireless link. Examples of wireless telecommunications systems comprise public land mobile networks (PLMN), satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN). Some wireless systems can be divided into cells, and are therefore often referred to as cellular systems.

[0004] A user can access the telecommunications system by means of an appropriate communication device or terminal. A communication device of a user may be referred to as user equipment (UE) or user device. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by a station, for example a base station of a cell, and transmit and / or receive communications on the carrier.

[0005] The telecommunications system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the communication system are permitted to do and how operations should be achieved. Communication protocols and / or parameters which shall be used for connection of the various entities are also typically defined. One example of a telecommunications system is the Universal Mobile Telecommunications System (UMTS). Other examples of telecommunications systems are Long-Term Evolution (LTE), LTE Advanced and the so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP). BRIEF SUMMARY

[0006] Example implementations of the present disclosure are directed to telecommunications and, in particular, to integrated sensing and communication. The present disclosure includes, without limitation, the following example implementations.

[0007] Some example implementations provide an apparatus implementing a sensing management function (SeMF) of a communication network, the apparatus comprising: means for receiving a request for a sensing service; means for determining, based on the request, one or more sensing data processing functions (SDPFs) for a sensing session for the sensing service, wherein the one or more SDPFs are distinct from the SeMF; means for sending a respective configuration of one of more configurations for collection and processing of sensing measurement data reported by one or more sensing nodes for the sensing session; means for receiving, from at least one SDPF of the one or more SDPFs, feedback on a quality of at least one of the sensing measurement data or one or more outputs of one or more processing operations performed on the sensing measurement data according to the respective configurations of the at least one SDPF; and means for determining whether to perform an adaptation of at least one of the sensing session or the respective configuration of one or more of the at least one SDPF based on the feedback.

[0008] Some example implementations provide a method performed by a sensing management function (SeMF) of a communication network, the method comprising: receiving a request for a sensing service; determining, based on the request, one or more sensing data processing functions (SDPFs) for a sensing session for the sensing service, wherein the one or more SDPFs are distinct from the SeMF; sending a respective configuration of one of more configurations for collection and processing of sensing measurement data reported by one or more sensing nodes for the sensing session; receiving, from at least one SDPF of the one or more SDPFs, feedback on a quality of at least one of the sensing measurement data or one or more outputs of one or more processing operations performed on the sensing measurement data according to the respective configurations of the at least one SDPF; and determining whether to perform an adaptation of at least one of the sensing session or the respective configuration of one or more of the at least one SDPF based on the feedback.

[0009] Some example implementations provide an apparatus implementing a central sensing management function (SeMF), the apparatus comprising: means for receiving a request for a sensing service; means for determining, based on the request, a split of a sensing session among local SeMFs to perform the sensing service, wherein the local SeMFs are distributed from one another and the central SeMF, wherein the split indicates a configuration for the local SeMFs in association with respective sets of one or more sensing data processing functions (SDPFs) for collection and processing of sensing measurement data reported by one or more sensing nodes associated with a respective local SeMF, wherein the respective sets of one or more SDPFs are distinct from one another, the central SeMF and the local SeMFs; and means for sending, to the local SeMFs, requests for a split sensing session for implementing the split of the sensing session.

[0010] Some example implementations provide a method performed by a central sensing management function (SeMF), the method comprising: receiving a request for a sensing service; determining, based on the request, a split of a sensing session among local SeMFs to perform the sensing service, wherein the local SeMFs are distributed from one another and the central SeMF, wherein the split indicates a configuration for the local SeMFs in association with respective sets of one or more sensing data processing functions (SDPFs) for collection and processing of sensing measurement data reported by one or more sensing nodes associated with a respective local SeMF, wherein the respective sets of one or more SDPFs are distinct from one another, the central SeMF and the local SeMFs; and sending, to the local SeMFs, requests for a split sensing session for implementing the split of the sensing session.

[0011] Some example implementations provide an apparatus implementing a sensing data processing function (SDPF), the apparatus comprising: means for receiving, from a sensing management function (SeMF), a configuration of the SDPF for collection and processing of sensing measurement data from one or more sensing nodes for a sensing session, wherein the SDPF is independent, distinct and distributed from the SeMF; means for collecting, according to the configuration, the sensing measurement data; means for performing, according to the configuration, one or more processing operations on the sensing measurement data to produce one or more outputs; means for sending, to the SeMF, feedback on a quality of at least one of the following: the sensing measurement data; or the one or more outputs of the one more processing operations; and means for sending, to the SeMF or a sensing client, one or more sensing reports that include the one or more outputs of the one or more processing operations.

[0012] Some example implementations provide a method performed by a sensing data processing function (SDPF), the method comprising: receiving, from a sensing management function (SeMF), a configuration of the SDPF for collection and processing of sensing measurement data from one or more sensing nodes for a sensing session, wherein the SDPF is independent, distinct and distributed from the SeMF; collecting, according to the configuration, the sensing measurement data; performing, according to the configuration, one or more processing operations on the sensing measurement data to produce one or more outputs; sending, to the SeMF, feedback on a quality of at least one of the following: the sensing measurement data; or the one or more outputs of the one more processing operations; and sending, to the SeMF or a sensing client, one or more sensing reports that include the one or more outputs of the one or more processing operations.

[0013] These and other features, aspects, and advantages of the present disclosure will be apparent from a reading of the following detailed description together with the accompanying figures, which are briefly described below. The present disclosure includes any combination of two, three, four or more features or elements set forth in this disclosure, regardless of whether such features or elements are expressly combined or otherwise recited in a specific example implementation described herein. The present disclosure is intended to be read holistically such that any separable features or elements of the disclosure, in any of its aspects and example implementations, should be viewed as combinable unless the context of the disclosure clearly dictates otherwise.

[0014] It will therefore be appreciated that this Brief Summary is provided merely for purposes of summarizing some example implementations so as to provide a basic understanding of some aspects of the disclosure. Accordingly, it will be appreciated that the above described example implementations are merely examples and should not be construed to narrow the scope or spirit of the disclosure in any way. Other example implementations, aspects and advantages will become apparent from the following detailed description taken in conjunction with the accompanying figures which illustrate, by way of example, the principles of some described example implementations. BRIEF DESCRIPTION OF THE FIGURE(S)

[0015] Having thus described example implementations of the disclosure in general terms, reference will now be made to the accompanying figures, which are not necessarily drawn to scale, and wherein:

[0016] FIG. 1 illustrates a telecommunications system that includes one or more public land mobile networks (PLMNs) coupled to one or more external data networks, according to some example implementations of the present disclosure;

[0017] FIG. 2 illustrates a deployment of a PLMN, according to some example implementations;

[0018] FIG. 3 more particularly depicts aspects of a 5G or 6G deployment that may correspond to the deployment of FIG. 2, according to some example implementations;

[0019] FIGS. 4A and 4B illustrate sensing configurations for a sensing system, according to various example implementations;

[0020] FIGS. 5Aand 5B illustrate respective architectures for a sensing system including a sensing management function (SeMF) and distinct sensing data processing function (SDPF), according to various example implementations;

[0021] FIGS. 6A and 6B illustrate interfaces between the SeMF and SDPF, and between SeMFs, according to various example implementations;

[0022] FIGS. 7Aand 7B illustrate a signaling chart of procedures for sensing session configuration and operation for the architecture of the sensing system of FIG. 5 A, according to some example implementations;

[0023] FIGS. 8A, 8B and 8C illustrate a signaling chart of procedures for sensing session configuration and operation for the architecture of the sensing system of FIG. 5B, according to some example implementations;

[0024] FIG. 9 is a signaling chart of a registration procedure of one or more services of a SeMF or SDPF, according to some example implementations;

[0025] FIGS. 10A, 10B, 10C and 10D are flowcharts illustrating various steps in a method performed by a SeMF, according to various example implementations;

[0026] FIGS. 1 lAand 11B are flowcharts illustrating various steps in a method performed by a central SeMF, according to various example implementations;

[0027] FIG. 12 is a flowchart illustrating various steps in a method performed by a SDPF, according to various example implementations; and

[0028] FIG. 13 illustrates an apparatus according to some example implementations. DETAILED DESCRIPTION

[0029] Some implementations of the present disclosure will now be described more fully hereinafter with reference to the accompanying figures, in which some, but not all implementations of the disclosure are shown. Indeed, various implementations of the disclosure may be embodied in many different forms and should not be construed as limited to the implementations set forth herein; rather, these example implementations are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Like reference numerals refer to like elements throughout.

[0030] Unless specified otherwise or clear from context, references to first, second or the like should not be construed to imply a particular order. A feature described as being above another feature (unless specified otherwise or clear from context) may instead be below, and vice versa; and similarly, features described as being to the left of another feature else may instead be to the right, and vice versa. Also, while reference may be made herein to quantitative measures, values, geometric relationships or the like, unless otherwise stated, any one or more if not all of these may be absolute or approximate to account for acceptable variations that may occur, such as those due to engineering tolerances or the like.

[0031] As used herein, unless specified otherwise or clear from context, the “or” of a set of operands is the “inclusive or” and thereby true if and only if one or more of the operands is true, as opposed to the “exclusive or” which is false when all of the operands are true. Thus, for example, “[A] or [B]” is true if [A] is true, or if [B] is true, or if both [A] and [B] are true. Further, the articles “a” and “an” mean “one or more,” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, it should be understood that unless otherwise specified, the terms “data,” “content,” “digital content,” “information,” and similar terms may be at times used interchangeably. The term “network” may refer to a group of interconnected computers including clients and servers; and within a network, these computers may be interconnected directly or indirectly by various means including via one or more switches, routers, gateways, access points or the like.

[0032] The present disclosure discusses systems and architectures that, while specific terms may be used, are broadly applicable across various technologies. For instance, while the present disclosure may reference technologies from 3 GPP such as Global System for Mobile Communications (GSM), UMTS, LTE, LTE Advanced, 5GNR, 5G Advanced, and 6G, the present disclosure is equally relevant to non-3GPP technologies like IEEE 802, Bluetooth, and Bluetooth Low Energy. Example implementations of the present disclosure described herein also mention public land mobile networks (PLMNs) and mobile network operators (MNOs), but example implementations are similarly applicable to standalone non-public networks (SNPNs) and the private entities operating these networks. Furthermore, although some examples and figures focus on radio access networks (RANs) and 3GPP access, example implementations are applicable to any type of network access. This includes not only 5G or 6G 3GPP access but also non-3GPP access, such as wireline access, untrusted non-3GPP access, and trusted non-3GPP access using wireless access gateway function (W-AGF), non-3GPP interworking function (N3IWF), or trusted non-3GPP gateway function (TNGF) to connect to a 5G or 6G core network.

[0033] Further, as used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); or (c) hardware circuit(s) and / or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

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

[0035] FIG. 1 illustrates a telecommunications system 100 according to various example implementations of the present disclosure. The telecommunications system generally includes one or more telecommunications networks. As shown, for example, the system includes one or more PLMNs 102 coupled to one or more other external data networks 104 - notably including a wide area network (WAN) such as the Internet. Each of the PLMNs includes a core network (CN) 106 backbone such as the Evolved Packet Core (EPC) of LTE, the 5G core network (5GC) or the like; and each of the core networks and the Internet are coupled to one or more RANs 108, air interfaces or the like that implement one or more radio access technologies (RATs). As used herein, a “network device” refers to any suitable device at a network side of a telecommunications network. Examples of suitable network devices are described in greater detail below.

[0036] In addition, the system includes one or more radio units that may be varyingly known as user equipment (UE) 110, terminal device, terminal equipment, mobile station or the like. The UE is generally a device configured to communicate with a network device or a further UE in a telecommunications network. The UE may be a portable computer (e.g., laptop, notebook, tablet computer), mobile phone (e.g., cell phone, smartphone), wearable computer (e.g., smartwatch), or the like. In other examples, the UE may be an Internet of things (loT) device, an industrial loT (IIoT device), a vehicle equipped with a vehicle-to-everything (V2X) communication technology, or the like. In some examples, as referenced by 3 GPP, the UE may be a narrowband loT (NB-IoT) device, an enhanced machine-type communication (eMTC) device, a reduced capability (RedCap) device, an ambient loT device, or the like.

[0037] In operation, these UEs 110 may be configured to connect to one or more of the RANs 108 according to their particular radio access technologies to thereby access a particular CN 106 of a PLMN 102, or to access one or more of the external data networks 104 (e.g., the Internet). The external data network may be configured to provide Internet access, operator services, third party services, etc. For example, the International Telecommunication Union (ITU) has classified 5G mobile network services into three categories: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine type communications (mMTC) or massive internet of things (MIoT).

[0038] Examples of radio access technologies include 3 GPP radio access technologies such as GSM, UMTS, LTE, LTE Advanced, 5GNR, 5G Advanced, and 6G. Other examples of radio access technologies include IEEE 802 technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.15 (including 802.15.1 (WPAN / Bluetooth), 802.15.4 (Zigbee) and 802.15.6 (WBAN)), Bluetooth, Bluetooth Low Energy (BLE), ultra wideband (UWB), and the like. Generally, a radio access technology may refer to any 2G, 3G, 4G, 5G, 6G or higher generation mobile communication technology and their different versions, as well as to any other wireless radio access technology that may be arranged to interwork with such a mobile communication technology to provide access to the CN 106 of a mobile network operator (MNO).

[0039] In various examples, a RAN 108 may be configured as one or more macrocells, microcells, picocells, femtocells or the like. The RAN may generally include one or more radio access nodes that are configured to interact with UEs 110. In various examples, a radio access node may be referred to as a base station (BS), access point (AP), base transceiver station (BTS), Node B (NB), evolved NB (eNB), macro BS, NB (MNB) or eNB (MeNB), home BS, NB (HNB) or eNB (HeNB), next generation NB (gNB), enhanced gNB (en-gNB), next generation eNB (ng-eNB), or the like. The RAN may include some type of network controlling / governing entity responsible for control of the radio access nodes. The network controlling / governing entity and radio access node may be separate or integrated into a single apparatus. The network controlling / governing entity may include processing circuity configured to carry out various management functions, etc. The processing circuity may be associated with a memory, computer-readable storage medium or database for maintaining information required in the management functions.

[0040] A RAN 108 may be centralized or distributed. In various examples, components of a RAN may be interconnected by Ethernet, Gigabit Ethernet, Asynchronous Transfer Mode (ATM), optical fiber, dark fiber, passive wavelength division multiplexing (WDM), WDM passive optical network (WDM-PON), optical transport network (OTN), time sensitive networking (TSN) and / or any other data link layer network, possibly including radio links. The RAN may be connected to a CN 106 through one or more gateways, network functions or the like.

[0041] As will be appreciated, a PLMN 102 may be deployed in a number of different manners. FIG. 2 illustrates a deployment 200 of a PLMN, such as a 4G LTE, 5G or 6G deployment, according to some example implementations. As shown, the deployment includes a CN 106, and RAN 108 with one or more radio access nodes 202 configured to interact with UEs 110. In a 4G LTE deployment, the EPC is the CN, and the evolved UMTS terrestrial radio access network (E-UTRAN) is the RAN; and the E-UTRAN includes one or more eNBs (radio access nodes) configured to connect UEs to the E-UTRAN to thereby access the EPC. Similarly, in a 5G deployment, the 5GC is the CN 106, and the next generation (NG) radio access network (NG-RAN) is the RAN 108; and the NG-RAN includes one or more gNBs (radio access nodes 202) configured to connect UEs 110 to the NG-RAN to thereby access the 5GC. The term ‘gNB’ in 5G may correspond to the eNB in 4G LTE.

[0042] Some deployments of 4G LTE and 5G in particular are considered standalone (SA) deployments. Other deployments combine 4G LTE and 5G technologies, and are referred to as non-standalone (NSA) deployments. In some deployments, the E-UTRAN includes one or more ng-eNBs that are configured to communicate with the 5GC, and that may also be configured to communicate with one or more gNBs. Similarly, in another deployment, the NG-RAN may include one or more en-gNBs that are configured to communicate with the EPC, and that may also be configured to communicate with one or more eNBs. In various instances, a single UE 110, a dual-mode or multimode UE, may support multiple (two or more) RANs—thereby being configured to connect to multiple RANs, such as 4G LTE and 5G.

[0043] In some deployments, operations of a radio access node 202 may be distributed or functionally split into components including one or more remote radio head (RRHs) or radio units (RUs), and a baseband unit (BBU); and in some architectures, the BBU may be split into a distributed unit (DU) and a central / centralized unit (CU), such as a server, host or node. In some architectures, the RRH / RU and DU may be co-located. It is also possible that node operations may be distributed among a plurality of servers, hosts or nodes. It should also be understood that the distribution of work between CN 106 operations and radio access node 202 operations may vary depending on implementation.

[0044] FIG. 3 more particularly depicts aspects of a 5G or 6G deployment 300 for a MNO, which may correspond to the deployment 200, according to some example implementations. As shown, for example, the deployment includes a 5GC 302, and a NG-RAN 304 that includes one or more NG-RAN nodes 306 (radio access nodes) configured to connect UEs 110 to the NG-RAN to thereby access the 5GC. In this context, a NG-RAN node may be a gNB or a ng-eNB. The term ‘gNB’ in 5G may correspond to the eNB in 4G LTE.

[0045] In the context of a 3GPP 5G service based architecture (SBA), the 5GC 302 may include a number of network functions (NFs) divided between the control plane and the user plane. The 3GPP 5G SBA facilitates flexible information exchange between NFs via service based interfaces (SBIs) in which the NFs may communicate with each other using representational state transfer application programming interfaces (APIs).

[0046] As shown, for example, the 5GC 302 may include an access and mobility management function (AMF) 308, a session management function (SMF) 310, a user plane function (UPF) 312, a network exposure function (NEF) 314, an application function (AF) 316, and the like. Another example of a suitable NF is a network repository function (NRF) 318 that serves as a central registry for the NFs, allowing the NFs to register their services and discover the services of other NFs. And as explained below, some example implementations of the present disclosure further provide yet example of a suitable NF, referred to at times as a sensing management function (SeMF) 320.

[0047] In the control plane, the AMF 308 is configured to provide UE-based authentication, authorization, mobility management, etc. The SMF 310 is configured to provide various functionality including session management (SM), UE Internet Protocol (IP) address allocation and management, selection and control of UPF(s) 312, control part of policy enforcement and Quality of Service (QoS), lawful intercept, termination of SM parts of NAS messages, Downlink Data Notification (DNN), roaming functionality, handle local enforcement to apply QoS for Service Level Agreements (SLAs), charging data collection and charging interface, etc. If the UE 110 has multiple sessions, different SMFs may be allocated to each session to manage them individually and possibly provide different functionalities per session.

[0048] The UPF 312 supports various user plane operations and functionalities, such as packet routing and forwarding, traffic handling (e.g., QoS enforcement), an anchor point for intra-RAT / inter-RAT mobility (when applicable), packet inspection and policy rule enforcement, lawful intercept (UP collection), traffic accounting and reporting, etc. The UPF is the point of interconnect between the 5GC and at least one external data network (DN) 322 (i.e., point of ingress or egress for a data network), and routes packets to and from the DN. As explained above, the DN may be configured to provide Internet access, operator services, third party services, etc.

[0049] The AF 316 may interact with the 5GC 302 to enable the deployment of specific services and applications. The AF communicates with other NFs to request and manage network resources, ensuring that the network adapts to the requirements of different applications and services. The NEF 314 allows authorized third-party applications and services to access specific network functions and services in a controlled manner. The NEF enables the exposure of network capabilities to external entities, fostering innovation and the development of new services.

[0050] In some deployments, operations of the NG-RAN node 306 or other radio access node 202 may be carried out, at least partly, in a central / centralized unit (CU), such as a server, host or node, operationally coupled to a distributed unit (DU), such as a radio head / node. It is also possible that node operations may be distributed among a plurality of servers, hosts or nodes.

[0051] It should also be understood that the distribution of work between CN 106 operations and radio access node 202 (e.g., NG-RAN node 306) operations may vary depending on implementation. Thus, a 5G network architecture may be based on a so-called CU-DU split. One gNB-CU (central node) may control one or more gNB-DUs. The gNB-CU may control a plurality of spatially separated gNB-DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some example implementations, however, the gNB-DUs (also called DU) may include, for example, a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the gNB-CU (also called a CU) may include the layers above the RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC), and an internet protocol (IP) layer. Other functional splits are also possible. It is considered that a skilled person is familiar with the open systems interconnection (OSI) model and the functionalities within each layer.

[0052] In some example implementations, the server or CU may generate a virtual network through which the server communicates with the radio node. In general, virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Such virtual network may provide flexible distribution of operations between the server and the radio head / node. In practice, any digital signal processing task may be performed in either the CU or the DU, and the boundary where the responsibility is shifted between the CU and the DU may be selected according to implementation.

[0053] It has been proposed to convert telecommunications networks to joint physical-biological networks in which a controller is capable of sensing the state and behavior of active and passive nodes, devices, and objects within its environment. The idea behind network sensing is to extend the existing telecommunications infrastructure with radar-like capabilities to gather knowledge about the surroundings, ideally with minimal overhead with respect to communication operations. In this regard, sensing services may use the same physical resources as communication services. Sensing services may be understood as services performing sensing the state and behavior of various active devices and / or objects in an environment, for example, availability of a channel prior to transmission of data. Communication services may be understood as services performing the transmission of data.

[0054] Integrated sensing and communication (ISAC) refers to technologies that combine sensing and communication functionalities in a joint communication and sensing (JCAS) system, which has been recognized as a promising technology for wireless networks. To extend the existing communications infrastructure with radar-like capabilities, ISAC systems may transmit, receive and process radio signals that are reflected by objects in the environment, enabling the estimation of parameters of interest such as range, angle-of-arrival, or velocity.

[0055] The ISAC services offer significant benefits to various types of services and target vertical applications. In 3GPP Release 19, several use cases and their corresponding technical requirements have been outlined to leverage 5G-based sensing services. These use cases include intrusion detection, such as detecting intruders in smart homes or pedestrian and animal intrusions on highways. The technology also supports autonomous driving by assisting in automotive maneuvering and navigation, and determining parking spaces. Additionally, it aids in the flight of unmanned aerial vehicles (UAVs) (also referred to as drones) by tracing flight trajectories and using network-assisted sensing to avoid collisions. In industrial settings, it supports automated guided vehicles (AGVs) and autonomous mobile robots (AMRs) by enabling detection and tracking in factories and collision avoidance in smart factories. Other applications include environment and weather monitoring, such as detecting rain, pollution, and flooding, as well as health monitoring, including fall detection and contactless sleep monitoring services at home. Moreover, extended reality (XR) applications can utilize these sensing capabilities to enhance user experiences.

[0056] In a telecommunications system 100 or deployment 200, 300, various entities may participate in sensing procedures either as transmitters or receivers in different possible sensing configurations. In some sensing configurations, one or more radio access nodes 202 (e.g., NG-RAN nodes 306), UEs 110 and / or non-3GPP sensing devices may participate in sensing procedures as sensing nodes. Examples of suitable sensing configurations include a mono-static sensing configuration of a radio access node (at times more simply referred to as a mono-static RAN-based sensing configuration), a bi- or multi-static sensing configuration of a radio access node (at times referred to as a multi-static RAN-based sensing configuration), and a bi- or multistatic RAN and UE-assisted sensing configuration.

[0057] In a mono-static (RAN-based) sensing configuration, a radio access node 202 (e.g., NG-RAN nodes 306) may act as a transmitter of sensing signals, as well as a receiver of reflected sensing signals. This configuration may employ a system in which transmit and receive antenna arrays are placed together. In a bi- or multi-static (RAN-based) sensing configuration, one radio access node may act as transmitter of sensing signals, while one or more other radio access nodes act as receiver(s) of reflected sensing signals. In a multi-static RAN and UE-assisted sensing configuration, a radio access node may act as transmitter of sensing signals, while one or more UEs 110 receive the reflected sensing signals. Similarly, a UE may act as transmitter of sensing signals, while one or more radio access nodes receive the reflected sensing signals.

[0058] FIGS. 4Aand 4B illustrate sensing configurations 400A, 400B for a sensing system 402, according to various example implementations. As shown, the sensing system includes at least one sensing node 404, such as a NG-RAN node 306 (or other radio access node 202), a UE no, a non-3GPP sensing device, or the like. In FIG. 4A, the single sensing node that is operable in a mono-static sensing mode. In this regard, the single sensing node may include respective antenna arrays 406, 408 for transmission and reception (these antenna arrays also referred to as transmitter and receiver). In some examples, this sensing node may be a full-duplex sensing node used for sensing services, and may also be used for communication services.

[0059] In FIG. 4B, the sensing system 402 includes separate sensing nodes 404 that are jointly operable (when co-located) in a mono-static sensing mode, or separately operable in a bi-or multi-static sensing mode. The first sensing node and the second sensing node may include respective antenna arrays for transmission and reception. These sensing nodes may be halfduplex sensing nodes used for sensing services, where one or both of sensing nodes may also be used for communication services.

[0060] As also shown, the sensing configurations 400A, 400B include aforementioned SeMF 320. The SeMF may be configured to support sensing services in a deployment 200, 300 of a PLMN. As indicated above, these may be services performing sensing the state and behavior of various active devices (e.g., UE 110) and / or objects 410 in an environment. In this regard, the SeMF may be configured to communicate with the sensing system 404, including sensing node(s) 404. As shown in FIG. 3, in some examples, the SeMF may be provided by a NF of the 5GC 302 (or other suitable CN). The SeMF may be a dedicated network function, or the SeMF may be integrated with another network function, such as a location management function (LMF) in the 5GC that supports location or positioning services.

[0061] To illustrate the problem that the example implementations of the present disclosure aim to address, imagine a scenario in which a transportation authority needs to monitor a vast transportation network across a large geographic area, which could cover 100 kilometers or more. The authority seeks to receive notifications about specific events, such as accidents or other incidents occurring on the roadways within this network. A deployment of a PLMN such as deployment 300 could potentially offer this information as a sensing service. In the sensing system 402 shown in FIGS. 4A and 4B, these sensing services might be exposed through the NEF 314. In this deployment, an AF 316 from the transportation authority would send a request to the PLMN (e.g., the SMF 310 or SeMF 410, via the NEF) to monitor the transportation network.

[0062] A single NG-RAN node 306 or other radio access node 202 cannot cover an expansive geographic area of 100 kilometers, while maintaining the same level of accuracy in its output. Consequently, multiple NG-RAN nodes would need to be engaged, each monitoring smaller sections of the area. The data from these various NG-RAN nodes would then be aggregated before being sent as a final report to the AF 316. In this context, several observations emerge. First, the network should be capable of breaking down a single request from a sensing client (e.g., UE 110, NF, AF) into multiple sensing sessions or operations, and aggregate measurement reports from these different sensing sessions into a single result to be provided to the sensing client.

[0063] Second, in large countries like India, China, and Canada, where NFs and NG-RAN nodes 306 / radio access nodes 202 are geographically dispersed over vast distances, it is inefficient to send the raw sensing measurement data (at times more simply referred to as sensing data) to a central SeMF 320, especially given the potentially high volume of data involved. Instead, it is more effective to perform local processing, either at the NG-RAN node or at the network edge, and to send pre-processed data or localized sensing results to the central SeMF.

[0064] Finally, the traditional monolithic architecture, where both sensing control and data processing are handled by a central SeMF in the core network, is not efficient. There is a need to disaggregate the SeMF in such a way that data processing can occur locally, either at or near the NG-RAN node. To achieve this, example implementations provide a solution in which the SeMF is divided into a control function (referred to as the SeMF 320) and a distinct sensing data processing function (SDPF), with standardized interfaces / APIs established between the SeMF and one or more SDPFs, as well as between SEMFs. The solution of example implementations also defines how the SeMF will control the SDPF or manage data collection.

[0065] Another potential use case involves the standardization or regulation of drone corridors. In various countries, regulators and air traffic management systems are working to define specific corridors designated for drone movement. By utilizing sensing capabilities, a PLMN could offer services to monitor these drone corridors. However, because a drone corridor can be vast, potentially spanning an entire city, the issues identified in the first use case are also relevant here. Specifically, having a single SeMF 320 operating from the central data center of the core network may prove inefficient for such large-scale monitoring.

[0066] The observations made in the first use case above related to transportation network monitoring are equally applicable to this scenario.

[0067] In yet another use case, if a sensing operation is conducted in a smaller area, it might involve multiple NG-RAN nodes 306 or SDPFs from different vendors within that area. In such a situation, obtaining sensing results from each system and aggregating them could lead to better sensing accuracy. Here, the sensing request may initially be managed by a central SeMF 320, which may initiate sensing sessions with various NG-RAN nodes, each controlled by different SeMFs from different vendors. The results from all these sessions would then be aggregated before being sent to the AF 316. In this context, it is also observed that if artificial intelligence (AI) / machine learning (ML) are utilized in the sensing operation, particularly for object detection, the performance of the sensing functions provided by different vendors will vary. Therefore, it makes sense to collect and aggregate sensing results from each system to achieve higher accuracy in the final sensing output.

[0068] Example implementations of the present disclosure therefore define an interface between a SeMF and one or more distinct SDPFs (referred to at times as a SeMF-SDPF interface). FIG. 5A illustrates one architecture for a sensing system 500A, according to some example implementations. In this architecture, the sensing system includes a SeMF 320 to provide sensing coordination functionality, and one or more SDPFs 502 to provide sensing data processing functionality for sensing measurement data reported by sensing nodes 504 (e.g., sensing nodes 404). In this regard, the SDPF may perform data processing functionality, such as to process, merge and combine sensing measurement data received from one or more sensing nodes. One or more SDPFs may be located in the 5GC 302 (or other CN 106), and / or in the NG-RAN 204 (or other RAN 108). Additionally or alternatively, in some examples, one or more SDPFs may be deployed at the edge of a deployment 200, 300 or PLMN 102 as an independent entity, or even deployed outside the PLMN domain (e.g., industrial scenarios), depending on the business case.

[0069] The architecture of the sensing system 500 illustrated in FIG. 5A may be referred to as a distributed SDPF architecture. FIG. 5B illustrates another architecture for a sensing system 500B, referred to as a distributed SeMF architecture, according to some example implementations. In the distributed SeMF architecture, the SeMF 320 is a central SeMF, and the sensing system includes one or more local SeMFs 320’. In this architecture, the central SeMF interfaces with the local SeMFs, and the local SeMFs interface with the SDPFs. In various examples, the local SeMFs may be separate from the SDPFs, or co-located with respective SDPFs. The interface between the central SeMF and local SeMF may be referred to as a SeMF-SeMF interface.

[0070] FIGS. 6Aand 6B illustrate the SeMF-SDPF interface 602 and the SeMF-SeMF interface 604 of respectively the architectures of the sensing systems 500A and 500B shown in FIGS. 5Aand 5B, according to some example implementations. Also shown are interfaces between the SeMF 320 and sensing node(s) 504, and between the sensing node(s) and SDPF 502.

[0071] According to example implementations, the SeMF-SDPF interface 602 may be used by a SeMF 320 to configure and control SDPF(s) 502 to perform one or more sensing processing operations on sensing measurement data, and thereby provide information on a decided sensing configuration of sensing nodes, and a determined configuration of the sensing processing operation(s). The sensing configuration may include, for example, involved sensing nodes, type of sensing measurement data, radio resource configuration, sensing session configuration perception area etc. The configuration of the sensing processing operation(s) may include, for example, sensing object type(s), type of sensing output, merging, correlation and / or combination of sensing measurement data from different sensing nodes etc.

[0072] In some examples, the SeMF-SDPF interface 602 may be used by a SDPF 502 to provide feedback to a SeMF 320, 320’ on the quality of the sensing measurement data and / or outputs of each sensing processing operation (e.g., achieved sensing QoS in terms of sensing accuracy, sensing range, sensing resolution etc., confidence level on estimated sensing outputs, certainty factor on calculated objects’ attributes etc.) that can allow re-configuration and adaptation of the SeMF procedures.

[0073] In the case of a distributed SeMF architecture (FIG. 5B) including the central SeMF 320 and local SeMF(s) 320’, the central SeMF may determine how to split a sensing session among the local SeMFs. For example, the central SeMF may determine to split a sensing session using area / geographic criteria, or according to sensing service type. As shown in FIG. 6B, the SeMF-SeMF interface 604 between central SeMF and local SeMFs may be defined to enable the configuration and coordination of the sensing session at each local SeMF (e.g., sensing requirements, handover suppression indication), with indications for notifications to be provided by a local SeMF to the central for sensing QoS parameters (e.g., based on thresholds provided from the central SeMF to the local SeMFs).

[0074] According to some example implementations, the SeMF 320, 320’ is enhanced to support the SeMF-SDPF interface 602 to control the SDPF 502 to perform the processing of the sensing measurement data, and receive sensing reports from the SDPF. In the context of the distributed SeMF architecture (FIG. 5B), a central SeMF may also be enhanced to support breaking a request received from a sensing client (e.g., UE 110, NF, AF 316) into multiple requests covering smaller (more granular) sensing areas. The central SeMF may support an enhanced sensing service request to local SeMF(s) 320’ that includes additional information, such as indication of a client mode of the SeMF, an indication to suppress handover (a local (edge) SeMF should not perform handover), an indication to report when sensing QoS goes below a certain threshold, or the like. The central SeMF may also be enhanced to aggregate sensing results from different local SeMFs, and send a single result to the sensing client.

[0075] In some example implementations, the SDPF 502 is provided for the processing of sensing measurement data. In various examples, the SDPF may be co-located with a NG-RAN node 306, co-located with an SeMF 320, 320’, or deployed at the edge as an independent entity. The SDPF supports the SeMF-SDPF interface 602 to receive requests from the SeMF to perform processing of the sensing measurement data of a sensing session, and report the sensing measurement data and / or output of the processing to the SeMF, and / or to the sensing client when indicated by the SeMF.

[0076] The SeMF-SDPF interface 602 may provide configurations for sensing. These configurations may include a sensing configuration that includes, for example, what to sense (e.g., object details), a NG-RAN node identity (ID) from where sensing measurement data may be collected and sent to the SDPF 502. The configurations may include a sensing reporting configuration that includes, for example, periodic or one-time reporting, event information for event-based reporting (e.g., event detected or (periodic) map), event filters, or the like. In this regard, sensing reports may include an event report or periodic report, complete sensing measurement data or a perception map, confidence level, achieved sensing QoS (e.g., accuracy, resolution), or the like.

[0077] In some example implementations, the SDPF 502 supports capability and mode registration to the NRF 318. The SDPF may also be able to discover the other SeMF / SDPF based on the capability and supporting mode. In this regard, a SeMF mode may indicate only control function, only data processing function, or both). SeMF / SDPF capability may indicate capability for object detection, object detection and tracking, environment monitoring, capability to provide pre-processed data e.g. perceived 3D MAP. Discovery of other SeMF / SDPF may also be based on, e.g., area, region, tracking area identity (TAI), connected NG-RAN nodes 306, or the like.

[0078] FIGS. 7Aand 8B illustrate a signaling chart 700 of procedures for sensing session configuration and operation for the architecture of the sensing system 500A of FIG. 5 A, according to some example implementations. As shown in FIG. 7A, a sensing client (e.g., AF 316) at step 701 sends a sensing service request to the network, and in particular the SeMF 320. This service request may be sent via the NEF 314. The sensing service request includes information related to a sensing service type, sensing area, sensing configuration / filters information, sensing QoS requirements, etc. The SeMF at step 702 uses the information in the sensing service request, as well as network capabilities, availability of resources etc., to determine or select a sensing mode, and candidate sensing nodes such as UE(s) 110 and / or NG-RAN nodes 306 to involve in the sensing process. The SeMF at step 703 determines a configuration of the sensing procedure and / or an allocation of the sensing resources.

[0079] The SeMF 320 at step 704 sends a sensing session establishment request to the selected candidate sensing nodes or UE 110 (directly or via the AMF 308), indicating the sensing session ID, generated by the SeMF to facilitate the coordination and handling of the sensing operations about the specific sensing service request, NG-RAN node ID (e.g., global gNB ID, the cell ID), UE(s) ID (e.g., subscriber permanent identifier (SUPI), subscription concealed identifier (SUCI)), sensing configuration used for NG-RAN nodes 306 / UEs 110 as Tx and UE as Rx, sensing QoS, radio resources of NG-RAN node and UE(s) for the sensing procedure.

[0080] The UEs 110 and / or NG-RAN nodes 306 at step 705 receive the configuration request, validate the configuration, and appropriately configure the transmitter and or receivers of sensing signals. The UE and / or NG-RAN nodes at step 706 send, to the SeMF 320, a sensing session establishment response that includes an indication whether the configuration has been successful or not, and in case the configuration is not successful, the reason / cause may be described.

[0081] The SeMF 320 at step 707 identifies the SDPFs 502 that will be involved in the specific sensing session, especially, if that serving area is distributed among multiple regions / areas, then the SeMF discovers and selects the SDPFs available in those areas. In some examples, step 707 may be combined with step 703, or initialized in step 703, and then finalized after the transmission of the responses from the UEs and / or NG-RAN nodes 306.

[0082] As shown in FIG. 7B, the SeMF 320 at step 708 sends a configure processing functions request to the one or more SDPFs 502 for the configuration of collection and processing of sensing measurement data. The request indicates the sensing session ID, the IDs of NG-RAN nodes 306 and / or UEs that are reporting their sensing measurement data to the specific SDPF.

[0083] For each sensing node (UE 110 and / or NG-RAN node 306), a group of sensing nodes, or all involved sensing nodes, the configure processing functions request may include a sensing reporting configuration (at times more simply referred to as a reporting configuration, which includes information so that the SDPF 502 may be aware about which inputs are expected to be received by the SDPF for the respective sensing session ID. In this regard, the sensing reporting configuration may include, for example, the type of the sensing measurement data that will be provided from each sensing node (e.g., in-phase / quadrature (I / Q) samples, periodogram, point clouds, map of objects), the periodicity (update rate) of the reported data, the duration (e.g., could be continuous with determined ending time), the perception area that is supported by each sensing node, or the like.

[0084] Additionally or alternatively, the sensing reporting configuration may include radio resource configuration information (e.g., selected frequency, selected bandwidth, selected beams) to facilitate processing of received data. For example, channel information collected using Frequency Range 2 (FR2) instead of Frequency Range 1 (FR1) may require different a processing configuration, and including this information in the sensing reporting configuration may be useful for processing, merging and analyses of sensing measurement data. Even further, for example, the sensing reporting configuration may include information about capabilities and / or features of one or more sensing nodes (e.g., location of the NG-RAN node 306, speed / velocity of the UE 110, etc.). In other examples, this information may be indicated to the SDPF 502 by the sensing node (e.g., UE, NG-RAN node).

[0085] In some examples, the configure processing functions request sent by the SeMF 320 at step 708 may include a processing configuration, which includes information so that the SDPF 502 may be aware about how to process and / or merge collected sensing measurement data, and for the SDPF to know the target sensing output. The processing configuration may include, for example, sensing object type(s) via object class identifier or explicitly via expected characteristics of the target(s) that form the object. The processing configuration may include a target sensing area. The processing configuration may include a target / desired / expected sensing QoS (e.g., accuracy, resolution, false alarm probability) for one or more parameters, such as speed / velocity, range, location, etc.

[0086] As another example, the processing configuration may include a type of output(s) (e.g., map of objects, periodograms, etc.) to be derived from the processing at the SDPF 502. Even further, the processing configuration may include information that indicates how the merging and / or correlation and / or combination of sensing measurement data from different sensing nodes may be conducted, such as using space( / location) criteria, timing criteria, object signature, object type criteria, and / or other object attributes. And the processing configuration may include information that indicates whether a single output need to be prepared or multiple outputs according to time and / or space criteria.

[0087] The SDPF 502 at step 709 validates the received configuration and informs the SeMF 320 about acceptance or rejection of the configuration and consequently of the processing task. In case of rejection, the SDPF may also indicate the reason for the rejection, such as due to limited computational resources for requested processing, insufficient capacity for receiving reports from sensing nodes (e.g., UE 110, NG-RAN node 306).

[0088] Once the processing method has been defined, the SeMF 320 at step 710 undertakes to configure the sensing nodes, such as NG-RAN nodes 306 and / or UEs 110, involved in the sensing session about how to send the measurement data to respective SDPF(s) 502.

[0089] The sensing operation is initiated at step 711 according to the defined sensing configuration and receiving entities at the sensing nodes, including UEs 110 and / or NG-RAN nodes 306, collect sensing measurement data. Each sensing node (e.g., NG-RAN node, UE) at step 712 prepares sensing reports including the sensing measurement data, and sends sensing reports to the SDPF 502. In some examples, the reporting to the SDPF may be realized via control plane signaling (e.g., NG-AP) or user plane signaling, as may be determined at step 710.

[0090] The SDPF 502 at step 713 collects the sensing reports (including sensing measurement data) from the sensing nodes (e.g., UEs 110, NG-RAN nodes 306), and merges, combines and / or processes the sensing measurement data to the processing configuration received from the SeMF 320 to determine sensing output(s) to provide to the sensing client (e.g., AF 316).

[0091] The SDPF 502 at step 714 may determine the quality of the processed sensing measurement data and provide feedback to the SeMF 320 about the quality of the collected and processing data. In some examples, the quality of the processed sensing measurement data may be determined based unreliable sensing measurement data, conflicting sensing measurement data from different sensing nodes, thresholds and / or criteria that are provided by the SeMF, 0AM and / or external source(s). Examples of suitable thresholds may include confidence for the presence of one or more detected objects (e.g., due to noisy channel information, average power in relation to a specific range / distance value from a sensing node), and / or confidence level for at least one parameter (e.g., range, angle, Doppler, radial speed, power). Additionally or alternatively, examples of suitable thresholds may include confidence level for at least one of the following object’s attributes, object’s location / position information, object’s velocity, object’s acceleration, object’s dimension / size, object’s type. Even further, additionally or alternatively, examples of suitable thresholds may include probability of a false alarm.

[0092] The SDPF 502 at step 715 sends to the SeMF 320 the feedback for the quality of the sensing measurement data and / or sensing output after the processing of the sensing measurement data. This feedback may be provided periodically or when an event is fulfilled. In some examples, the feedback may refer to a specific sensing session ID or determined from more than one sensing sessions, a specific sensing area or a part of it (e.g., SDPF 502 detected low confidence in a part of the sensing area), a specific type of object, a specific sensing service, a specific sensing QoS parameter, or the like. In some examples, the feedback may be provided with a certainty factor, and / or a confidence about the accuracy and quality of derived outputs.

[0093] Based on the received feedback, the SeMF 320 may at step 716 decide and trigger an adaptation of the sensing operation. In various examples, the adaptation may involve one or more sensing nodes (UE 110, NG-RAN node 306), such as the selection and addition of at least one new sensing node, and / or the removal of at least one sensing node. Additionally or alternatively, for example, the adaptation may involve the processing at the SDPF 502, such as selection of another processing method, modification on the merging of the sensing measurement data, and / or modification of the sensing measurement data that is collected.

[0094] The SeMF 320 may at step 717.1 send to the sensing nodes (UEs 110, NG-RAN nodes 306) an updated sensing configuration for the specific sensing session ID. The updated sensing configuration for the sensing nodes may include, for example, updated sensing resources (e.g., change frequency, increase / decrease bandwidth, odify number of antennas involved, Tx power) and / or sensing configuration (e.g., update / refresh rate, burst rate).

[0095] The SeMF 320 may at step 717.2 send to the SDPF 502 an updated sensing reporting configuration and / or an updated processing configuration. For example, the SeMF may send an update in which the SeMF may modify criteria for merging and / or combination of sensing measurement data from different sensing nodes, use data from external sources, etc.

[0096] The SDPF 502 at step 718 sends the sensing output(s) to the sensing client (e.g., AF 316). The sensing output(s) may be sent to the sensing client directly or via the SeMF 320, according to the deployment. Notably, steps 715-717 and 718 may not be co-related. In this regard, steps 715-717 may be triggered upon an event, while step 718 may occur once or periodically, or even upon an event, according to the sensing service request parameters (in step 701).

[0097] FIGS. 8A, 8B and 8C illustrate a signaling chart 800 of procedures for sensing session configuration and operation for the distributed SeMF architecture (FIG. 5B), according to some example implementations. Similar to before, as shown in FIG. 8A, a sensing client (e.g., AF 316) at step 701 sends a sensing service request to the network, and in particular a central SeMF 320.

[0098] The central SeMF 320 at step 802 decides to split / assign the sensing service request to one or more local SeMFs 320’. This may be the case, for example, when the central SeMF does not have access to local sensing nodes (UEs 110, NG-RAN nodes 306). The central SeMF may also decide to split / assign the sensing service request to local SeMFs when the central SeMF cannot decide the most appropriate sensing configuration and / or mode (mono / bi / multi static) in a local radio environment / area controlled in some cases by another stakeholder, or when the central SeMF wants to avoid violating some local enterprise privacy or regulation for the local access.

[0099] The central SeMF 320 may decide how to split a sensing session among local SeMF(s) 320’, such as using area / geographical criteria, or according to sensing service type etc. The central SeMF then at step 803 sends sensing service request(s) to the local SeMF(s), (each of these sensing service request(s) at times referred to as a sensing service split request) which may include the relevant sensing service requirements and sensing QoS requirements according to the request received from the sensing client (e.g., AF 316). The sensing service split request may also include an indication for notifications that a local SeMF may trigger to the central SeMF for sensing QoS parameters (e.g., thresholds may be provided from the central SeMF). Also, information about the type and / or periodicity / update rate of sensing output(s) may be provided.

[0100] In some examples, the sensing service split request sent by the central SeMF 320 may also include an indication for suppression or not of a handover procedure from one local SeMF 320’ to another local SeMF. This indication may be useful so that a local SeMF' does not perform handover to another SeMF (e.g., due to mobility events) on its own. The handover in this case may instead be controlled by the central SeMF.

[0101] As shown in FIG. 8B, upon receipt of the sensing service split request from the central SeMF 320, each local SeMF 320’ performs local checks and configurations at steps 804, 805, 806, 807, 808 and 809, which correspond to steps 702-709 (step 809 corresponding to steps 707-709). Each local SeMF then at step 810 sends a sensing service response (the sensing service response at times referred to as a sensing sendee split response) to inform the central SeMF 320 about the acceptance or not of the split. In some examples in which the split is rejected by a local SeMF, the sensing service split response may include information that indicates a cause (e.g., limited sensing resources, limited computation resources for the local processing, etc.). Also, in some examples, the sensing service split response from a local SeMF may include a recommendation of the local SeMF for an alternative configuration.

[0102] Each local SeMF 320’ configures respective sensing nodes (e.g., UEs 110, NG-RAN nodes 306) for performing a sensing operation to collect sensing measurement data., which is reported back to the local SeMF for sensing data processing, as shown at blocks 811, 812, 813, 814 and 815 (of FIGS. 8B and 8C) that correspond to steps 710-713. The local SeMF at step 816 reports the sensing output(s) to the central SeMF 320, according to the received configuration by the central SeMF. As shown in FIG. 8C, the local SeMF and respective SDPF(s) 502 (or a central SDPF) for the local SeMFs may also determine the quality of the processed sensing measurement data, and perform one or more adaptations, as shown at step 817 that corresponds to steps 714-717.2.

[0103] The central SeMF 320 (or a central SDPF 502) at steps 818 and 819 undertakes to merge the sensing data / reports received from the local SeMF(s) 320’, and then provide the output to the sensing client (e.g., AF 316).

[0104] Some example implementations provide procedures by which an SeMF 320, 320’ and SDPF 502 may be discovered and selected as per a sensing request from a sensing client (e.g., AF 316). In some of these examples, a SeMF and / or a SDPF may have one or more modes of operation. In this regard, a SeMF may operate as a central SeMF (C-SeMF) that plays a central role of function interacting with a sensing client (via NEF 314) and multiple local SeMFs (L-SeMF), which manage respective parts of a sensing request from a sensing client. A central SDPF (C-SDPF) plays a central role of function to produce a final sensing result for a sensing client as per request, and a local SDPF (L-SDPF) processes sensing measurement data obtained locally and delivers an intermediate sensing result to the C-SDPF. In some examples, a SeMF or SDPF may have a capability / mode that based on implementation and deployment may be selectable from only sensing control, only sensing data processing, or both sensing control and data processing.

[0105] To further illustrate some example implementations, FIG. 9 is a signaling chart 900 of a registration procedure of one or more services of a SeMF 320, 320’ or SDPF 502, according to some example implementations. As shown, the SeMF / SDPF at step 901 sends a request message (Nnrf_NFManageinent_NFRegister_request) to the NRF 31S to inform the NRF of the SeMF / SDPF’s NF profile, and register the mode of operations of the SeMF / SDPF per sensing service. The NRF at step 902 stores the NF profile of the SeMF / SDPF, including storing the mode of SeMF / SDPF operations per sensing service. The NRF then at step 903 acknowledges the NF registration via a response message (Nnrf_NFManagement_NFRegister_response) to the SeMF / SDPF. For each, mode (central, local or both) per sensing service, a supported geographical area may be requested and registered in the NRF. The supported geographical area may be denoted in a number of different manners, such as by a list of cells, as, e.g., the list of cells, tracking area (TA), RAN-based notification area (RNA), etc.

[0106] A similar procedure may be carried out for NF service update of a SeMF 320, 320’ or SDPF 502. In this procedure, the SeMF / SDPF may send a NF update request to the NRF 318, such as to register an updated mode of operations of the SeMF / SDPF. The NRF may update the NF profile of the SeMF / SDPF, including the updated mode of SeMF / SDPF operations. The NRF may then send an NF update response back to the SeMF / SDPF.

[0107] FIGS. 10A -- 10D are flowcharts illustrating various steps in a method 1000 performed by a sensing management function (SeMF) of a communication network, according to various example implementations. The method includes receiving a request for a sensing service, as shown at block 1002 of FIG. 10A. The method includes determining, based on the request, one or more sensing data processing functions (SDPFs) for a sensing session for the sensing service, wherein the one or more SDPFs are distinct from the SeMF, as shown at block 1004. The method includes sending a respective configuration of one of more configurations for collection and processing of sensing measurement data reported by one or more sensing nodes for the sensing session, as shown at block 1006. The method includes receiving, from at least one SDPF of the one or more SDPFs, feedback on a quality of at least one of the sensing measurement data or one or more outputs of one or more processing operations performed on the sensing measurement data according to the respective configurations of the at least one SDPF, as shown at block 1008. And the method includes determining whether to perform an adaptation of at least one of the sensing session or the respective configuration of one or more of the at least one SDPF based on the feedback, as shown at block 1010.

[0108] In some examples, the determining the one or more SDPFs at block 1004 comprises determining a plurality of SDPFs that are independent, distinct and distributed to respective sets of one or more sensing nodes. In some of these examples, the sending the respective configuration at block 1006 comprises sending to each of the plurality of SDPFs a respective configuration, and the receiving the feedback at block 1008 comprises receiving the feedback from at least one of the plurality of SDPFs.

[0109] In some examples, the respective configuration comprises a reporting configuration that includes information regarding the one or more sensing nodes and the sensing measurement data to be reported by the one or more sensing nodes.

[0110] In some examples, the respective configuration comprises a processing configuration that includes information regarding the one or more processing operations to be performed on the sensing measurement data.

[0111] In some examples, the determining whether to perform the adaptation at block 1010 comprises determining to perform the adaptation of a sensing configuration of at least one of the one or more SDPFs for the sensing session, as shown in FIG. 10B. In some of these examples, the method 1000 further comprises performing an adaptation of the sensing configuration of the at least one of the one or more SDPFs to produce an updated sensing configuration, as shown at block 1012. And the method includes sending, to the at least one of the one or more sensing nodes, the updated sensing configuration, as shown at block 1014.

[0112] In some examples, the determining whether to perform the adaptation at block 1010 comprises determining to perform the adaptation of the respective configuration of at least one of the one or more SDPFs, as shown in FIG, 10C. In some of these examples, the method 1000 further comprises performing an adaptation of the respective configuration of the at least one of the one or more SDPFs to produce an updated configuration, as shown at block 1016. And the method includes sending, to the at least one of the one or more SDPFs, the updated configuration, as shown at block 1018.

[0113] In some examples, the request comprises a request for a split sensing session to perform the sensing service. In some of these examples, the request is received from a central SeMF, and the SeMF is a local SeMF of one or more local SeMFs that are distributed from one another and the central SeMF in the telecommunications system.

[0114] In some examples, the method 1000 further comprises receiving, from the one or more SDPFs, one or more sensing reports that include the one or more outputs of the one or more processing operations, as shown at block 1020 of FIG. 10D. And the method includes sending the one or more sensing reports to the central SeMF, as shown at block 1022.

[0115] In some examples, the request comprises a quality of sendee (QoS) threshold. In some of these examples, the feedback further includes a sensing QoS, and the method further includes notifying the central SeMF that the sensing QoS is below the QoS threshold m an instance the sensing QoS is below the QoS threshold.

[0116] In some examples, the receiving the request at block 1002 comprises receiving the request from a sensing client or a central SeMF. In some of these examples, the method 1000 further includes registering, with a network repository function, a registration of the SeMF. The registration comprises information that indicates one or more modes of operation for one or more sensing services of the SeMF for discover}' by the sensing client or the central SeMF.

[0117] FIGS. 11A and 1 IB are flowcharts illustrating various steps in a method 1100 performed by a central sensing management function (SeMF), according to various example implementations. The method includes receiving a request for a sensing service, as shown at block 1102 of FIG. 11 A. The method includes determining, based on the request, a split of a sensing session among local SeMFs to perform the sensing service, as shown at block 1104. The local SeMFs are distributed from one another and the central SeMF. The split indicates a configuration for the local SeMFs in association with respective sets of one or more sensing data processing functions (SDPFs) for collection and processing of sensing measurement data reported by one or more sensing nodes associated with a respective local SeMF, wherein the respective sets of one or more SDPFs are distinct from one another, the central SeMF and the local SeMFs. And the method includes sending, to the local SeMFs, requests for a split sensing session for implementing the split of the sensing session, as shown at block 1106.

[0118] In some examples, the receiving the request at block 1102 comprises receiving the request from a sensing client, as shown in FIG. 1 IB. In some of these examples, the method 1100 further comprises receiving, from the local SeMFs, sensing reports comprising one or more outputs of one or more sensing processing operations performed by the respective sets of one or more SDPFs, as shown at block 1108. The method includes merging the sensing reports from the local SeMFs to produce a merged sensing report, as shown at block 1110. And the method includes sending, to the sensing client, the merged sensing report, as shown at block 1112.

[0119] In some examples, the requests for the split sensing session comprise a quality of service (QoS) threshold. In some of these examples, the method 1100 further includes receiving, from one or more of the local SeMFs, a notification that a sensing QoS at the one or more SeMFs is below the QoS threshold in an instance the sensing QoS is below the QoS threshold.

[0120] In some examples, the receiving the request at block 1102 comprises receiving the request from a sensing client. In some of these examples, the method 1100 further includes registering, with a network repository function, a registration of the central SeMF. the registration comprises information that indicates one or more modes of operation for one or more sensing services of the central SeMF for discovery’ by the sensing client.

[0121] FIG. 12 is a flowchart illustrating various steps in a method 1200 performed by a sensing data processing function (SDPF), according to various example implementations. The method includes receiving, from a sensing management function (SeMF), a configuration of the SDPF for collection and processing of sensing measurement data from one or more sensing nodes for a sensing session, In some of these examples, the SDPF is independent, distinct and distributed from the SeMF, as shown at block 1202. The method includes collecting, according to the configuration, the sensing measurement data, as shown at block 1204. The method includes performing, according to the configuration, one or more processing operations on the sensing measurement data, to produce one or more outputs, as shown at block 1206. The method includes sending, to the SeMF, feedback on a quality of at least one of the following: the sensing measurement data, or the one or more outputs of the one more processing operations, as shown at block 1208. And the method includes sending, to the SeMF or a sensing client, one or more sensing reports that include the one or more outputs of the one or more processing operations, as shown at block 1210.

[0122] In some examples, the configuration comprises a reporting configuration that includes information regarding the one or more sensing nodes and the sensing measurement data to be reported by the one or more sensing nodes.

[0123] In some examples, the configuration comprises a processing configuration that includes information regarding the one or more processing operations to be performed on the sensing measurement data.

[0124] In some examples, the method 1200 further includes receiving, from the SeMF, based on the feedback sent to the SeMF, an updated configuration of the SDPF. In some of these examples, at least one of: the sensing measurement data to be collected, or the one or more processing operations to be performed on the sensing measurement data is based on the updated configuration.

[0125] In some examples, the method 1200 further includes registering, with a network repository function, a registration of the SDPF. In some of these examples, the registration comprises information that indicates one or more modes of operation for one or more sensing services of the SDPF for discovery by the SeMF.

[0126] According to example implementations of the present disclosure, a telecommunications system 100 or PLMN 102, and its components such as a UE 110, CN 106, RAN 108, radio access node 202, 5GC 302, NG-RAN 304, AMF 308, SMF 310, UPF 312, NEF 314, AF 316, NRF 318, SeMF 320, SeMF 320’, sensing node 404, SDPF 502 and / or sensing node 504. Means for implementing the system and its components may include hardware, firmware, software, or combinations thereof. In some examples, one or more apparatuses may be configured to function as or otherwise implement the system and its components shown and described herein. In examples involving more than one apparatus, the respective apparatuses may be connected to or otherwise in communication with one another in a number of different manners, such as directly or indirectly via a wired or wireless network or the like.

[0127] According to some example implementations, at least some of the method 1000 described with respect to FIGS. 10A - 10D may be carried out by an apparatus comprising means for performing functions corresponding steps of the method. Similarly, at least some of the method 1100 described with respect to FIGS. 11A. and 1 IB may be carried out by an apparatus comprising means for performing functions corresponding steps of the method. And at least some of the method 1200 described with respect to FIG. 12 may be carried out by an apparatus comprising means for performing functions corresponding steps of the method. Examples of a suitable apparatus may include a radio access node, gNB (e.g., gNB-DU, gNB-CU), ng-eNB, NF, SeMF, SDPF, or any suitable apparatus, such as a server, host or node.

[0128] FIG. 13 illustrates an apparatus 1300 in which means for performing various functions includes hardware, alone or under direction of one or more computer programs from a computer-readable storage medium or other memory, such as computer memory, according to some example implementations of the present disclosure. The apparatus may include one or more of each of a number of components such as, for example, processing circuitry 1302 connected to computer-readable storage medium or other memory 1304.

[0129] The processing circuitry 1302 may be composed of one or more processors alone or in combination with one or more computer-readable storage media. The processing circuitry is generally any piece of computer hardware that is capable of processing information such as, for example, data, computer programs and / or other suitable electronic information. The processing circuitry is composed of a collection of electronic circuits some of which may be packaged as an integrated circuit or multiple interconnected integrated circuits (an integrated circuit at times more commonly referred to as a “chip”). The processing circuitry may be configured to execute computer programs, which may be stored onboard the processing circuitry or otherwise stored in the memory 1304 (of the same or another apparatus).

[0130] The processing circuitry 1302 may be a number of processors, a multi-core processor or some other type of processor, depending on the particular implementation. Further, the processing circuitry may be implemented using a number of heterogeneous processor systems in which a main processor is present with one or more secondary processors on a single chip. As another illustrative example, the processing circuitry may be a symmetric multi-processor system containing multiple processors of the same type. In yet another example, the processing circuitry may be embodied as or otherwise include one or more ASICs, FPGAs or the like. Thus, although the processing circuitry may be capable of executing a computer program to perform one or more functions, the processing circuitry of various examples may be capable of performing one or more functions without the aid of a computer program. In either instance, the processing circuitry may be appropriately programmed to perform functions or operations according to example implementations of the present disclosure.

[0131] The memory 1304 is generally any piece of computer hardware that is capable of storing information such as, for example, data, computer programs, instructions 1306 (e.g., computer-readable program code) and / or other suitable information either on a temporary basis and / or a permanent basis. The memory may include volatile and / or non-volatile memory, and may be fixed or removable. Examples of suitable memory include recording media, random access memory (RAM), read-only memory (ROM), a hard drive, a flash memory, a thumb drive, a removable computer diskette, an optical disk or some combination thereof.

[0132] The memory 1304 is a non-transitory device capable of storing information. One example of a suitable memory is a computer-readable storage medium, which is distinguishable from a computer-readable transmission medium capable of carrying information from one location to another. Examples of suitable computer-readable transmission media comprise electronic carrier signals, telecommunications signals, or some combination thereof. As used herein, the term “non-transitory” 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 versus ROM). A computer-readable medium as described herein generally refers to a computer-readable storage medium or computer-readable transmission medium. A computer-readable medium is any entity or device capable in which information, such as one or more computer programs or portions thereof, may be stored and carried.

[0133] In addition to the memory 1304 (e.g., computer-readable storage medium), the processing circuitry 1302 may also be connected to one or more interfaces for displaying, transmitting and / or receiving information. The interfaces may include a communications interface 1308 and / or one or more user interfaces (e.g., display, user input interface). The communications interface may be configured to transmit and / or receive information, such as to and / or from other apparatus(es), network(s) or the like. The communications interface may be configured to transmit and / or receive information by physical (wired) and / or wireless communications links. Examples of suitable communication interfaces include a network interface controller (NIC), wireless NIC (WNIC) or the like.

[0134] Execution of the instructions 1306 by the processing circuitry 1302, or storage of the instructions in the memory 1304, supports combinations of operations for implementing example implementations of the present disclosure. In this manner, an apparatus 1300 may comprise at least one processing circuitry and at least one memory coupled to the at least one processing circuitry, where the at least one processing circuitry is configured to execute instructions stored in the at least one memory. It will also be understood that one or more functions, and combinations of functions, may be implemented by special purpose hardware-based computer systems and / or processing circuitry which perform the specified functions, or combinations of special purpose hardware and program code instructions.

[0135] Some example implementations of the present disclosure may also be earned out in the form of a computer process defined by one or more computer programs or portions thereof. Example implementations of the present disclosure may be carried out by executing at least one portion of a computer program comprising instructions. The computer program may be in source code form, object code form, or in some intermediate form. The computer program may be stored in a computer-readable medium that is readable by a computer, processing circuitry or other suitable apparatus. As indicated above, for example, the computer program may be stored in a memory, such as a computer-readable storage medium. Additionally or alternatively, for example, the computer program may be stored in a computer-readable transmission medium. The coding of software for carrying out example implementations of the present disclosure is well within the scope of a person of ordinary skill in the art.

[0136] As will be appreciated, any suitable instructions may be loaded onto a computer, a processing circuitry or other programmable apparatus from a memory or a computer-readable medium (e.g., computer-readable storage medium, computer-readable transmission medium) to produce a particular machine, such that the particular machine becomes a means for implementing the functions specified herein. The instructions may also be stored in a computer-readable medium that can direct a computer, a processing circuitry or other programmable apparatus to function in a particular manner to thereby generate a particular machine or particular article of manufacture. In some examples, the instructions stored in the computer-readable medium may produce an article of manufacture, where the article of manufacture becomes a means for implementing functions described herein. The instructions may be retrieved from a computer-readable medium and loaded into a computer, processing circuitry or other programmable apparatus to configure the computer, processing circuitry or other programmable apparatus to execute operations to be performed on or by the computer, processing circuitry or other programmable apparatus.

[0137] Retrieval, loading and execution of instructions comprising program code instructions may be performed sequentially such that one instruction is retrieved, loaded and executed at a time. In some example implementations, retrieval, loading and / or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and / or executed together. Execution of the program code instructions may produce a computer-implemented process such that the instructions executed by the computer, processing circuitry or other programmable apparatus provide operations for implementing functions described herein.

[0138] As explained above and reiterated below, the present disclosure includes, without limitation, the following example implementations.

[0139] Clause 1. A method performed by a sensing management function (SeMF) of a communication network, the method comprising: receiving a request for a sensing service; determining, based on the request, one or more sensing data processing functions (SDPFs) for a sensing session for the sensing service, wherein the one or more SDPFs are distinct from the SeMF; sending a respective configuration of one of more configurations for collection and processing of sensing measurement data reported by one or more sensing nodes for the sensing session; receiving, from at least one SDPF of the one or more SDPFs, feedback on a quality of at least one of the sensing measurement data or one or more outputs of one or more processing operations performed on the sensing measurement data according to the respective configurations of the at least one SDPF; and determining whether to perform an adaptation of at leas t one of the sensing session or the respec tive configuration of one or more of the at least one SDPF based on the feedback.

[0140] Clause 2. The method of clause 1, wherein the determining the one or more SDPFs comprises determining a plurality of SDPFs that are independent, distinct and distributed to respective sets of one or more sensing nodes, and wherein the sending the respective configuration comprises sending to each of the plurality' of SDPFs a respective configuration, and the receiving the feedback comprises receiving the feedback from at least one of the plurality of SDPFs.

[0141] Clause 3. The method of clause 1 or clause 2, wherein the respective configuration comprises a reporting configuration that includes information regarding the one or more sensing nodes and the sensing measurement data to be reported by the one or more sensing nodes.

[0142] Clause 4. The method of any of clauses 1 to 3, wherein the respective configuration comprises a processing configuration that includes information regarding the one or more processing operations to be performed on the sensing measurement data.

[0143] Clause 5. The method of any of clauses 1 to 4, wherein the determining whether to perform the adaptation comprises determining to perform the adaptation of a sensing configuration of at least one of the one or more SDPFs for the sensing session, and wherein the method further comprises: performing an adaptation of the sensing configuration of the at least one of the one or more SDPFs to produce an updated sensing configuration, and sending, to the at least one of the one or more sensing nodes, the updated sensing configuration.

[0144] Clause 6. The method of any of clauses 1 to 5, wherein the determining whether to perform the adaptation comprises determining to perform the adaptation of the respective configuration of at least one of the one or more SDPFs, and wherein the method further comprises: performing an adaptation of the respective configuration of the at least one of the one or more SDPFs to produce an updated configuration; and sending, to the at least one of the one or more SDPFs, the updated configuration.

[0145] Clause 7. The method of any of clauses 1 to 6, wherein the request comprises a request for a split sensing session to perform the sensing service, wherein the request is received from a central SeMF, and wherein the SeMF is a local SeMF of one or more local SeMFs that are distributed from one another and the central SeMF in the telecommunications system.

[0146] Clause 8. The method of clause 7, wherein the method further comprises: receiving, from the one or more SDPFs, one or more sensing reports that include the one or more outputs of the one or more processing operations; and sending the one or more sensing reports to the central SeMF.

[0147] Clause 9. The method of clause 7 or clause 8, wherein the request comprises a quality of service (QoS) threshold, and wherein the feedback further includes a sensing QoS, and wherein the method further comprises notifying the central SeMF that the sensing QoS is below the QoS threshold in an instance the sensing QoS is below the QoS threshold.

[0148] Clause 10. The method of any of clauses 1 to 9, wherein the receiving the request comprises receiving the request from a sensing client or a central SeMF, wherein the method further comprises registering, with a network repository function, a registration of the SeMF, and wherein the registration comprises information that indicates one or more modes of operation for one or more sensing services of the SeMF' for discovery by the sensing client or the central SeMF.

[0149] Clause 11. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of clauses 1 to 10.

[0150] Clause 12. An apparatus comprising means for performing the method of any of clauses 1 to 10.

[0151] Clause 13. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry', causes an apparatus to perform the method of any of clauses 1 to 10.

[0152] Clause 14. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 1 to 10.

[0153] Clause 15. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 1 to 10.

[0154] Clause 16. A method performed by a central sensing management function (SeMF), the method comprising: receiving a request for a sensing service; determining, based on the request, a split of a sensing session among local SeMFs to perform the sensing service, wherein the local SeMFs are distributed from one another and the central SeMF, wherein the split indicates a configuration for the local SeMFs in association with respective sets of one or more sensing data processing functions (SDPFs) for collection and processing of sensing measurement data reported by one or more sensing nodes associated with a respective local SeMF, wherein the respective sets of one or more SDPFs are distinct from one another, the central SeMF and the local SeMFs: and sending, to the local SeMFs, requests for a split sensing session for implementing the split of the sensing session.

[0155] Clause 17. The method of clause 16, wherein the receiving the request comprises receiving the request from a sensing client, and wherein the method further comprises: receiving, from the local SeMFs, sensing reports comprising one or more outputs of one or more sensing processing operations performed by the respective sets of one or more SDPFs; merging the sensing reports from the local SeMFs to produce a merged sensing report; and sending, to the sensing client, the merged sensing report,

[0156] Clause 18. The method of clause 16 or clause 17, wherein the requests for the split sensing session comprise a quality of service (QoS) threshold, and wherein the method further comprises receiving, from one or more of the local SeMFs, a notification that a sensing QoS at the one or more SeMFs is below the QoS threshold in an instance the sensing QoS is below the QoS threshold.

[0157] Clause 19. The method of any of clauses 16 to 18, wherein the receiving the request comprises receiving the request from a sensing client, wherein the method further comprises registering, with a network repository function, a registration of the central SeMF, and wherein the registration comprises information that indicates one or more modes of operation for one or more sensing services of the central SeMF for discovery by the sensing client.

[0158] Clause 20. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of clauses 16 to 19.

[0159] Clause 21. An apparatus comprising means for performing the method of any of clauses 16 to 19.

[0160] Clause 22. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 16 to 19.

[0161] Clause 23. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 16 to 19.

[0162] Clause 24. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 16 to 19.

[0163] Clause 25. A method performed by a sensing data processing function (SDPF), the method comprising: receiving, from a sensing management function (SeMF), a configuration of the SDPF for collection and processing of sensing measurement data, from one or more sensing nodes for a sensing session, wherein the SDPF is independent, distinct and distributed from the SeMF; collecting, according to the configuration, the sensing measurement data.; performing, according to the configuration, one or more processing operations on the sensing measurement data to produce one or more outputs; sending, to the SeMF, feedback on a quality of at least one of the following: the sensing measurement data; or the one or more outputs of the one more processing operations; and sending, to the SeMF or a sensing client, one or more sensing reports that include the one or more outputs of the one or more processing operations.

[0164] Clause 26. The method of clause 25, wherein the configuration comprises a reporting configuration that includes information regarding the one or more sensing nodes and the sensing measurement data to be reported by the one or more sensing nodes.

[0165] Clause 27. The method of clause 25 or clause 26, wherein the configuration comprises a processing configuration that includes information regarding the one or more processing operations to be performed on the sensing measurement data.

[0166] Clause 28. The method of any of clauses 25 to 27, wherein the method further comprises receiving, from the SeMF, based on the feedback sent to the SeMF, an updated configuration of the SDPF, and wherein at least one of: the sensing measurement data to be collected; or the one or more processing operations to be performed on the sensing measurement data is based on the updated configuration.

[0167] Clause 29. The method of any of clauses 25 to 28, wherein the method further comprises registering, with a network repository function, a registration of the SDPF, and wherein the registration comprises information that indicates one or more modes of operation for one or more sensing services of the SDPF for discovery by the SeMF.

[0168] Clause 30. An apparatus comprising: at least one memory’ configured to store instructions; and at least one processing circuitry' configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of clauses 25 to 29.

[0169] Clause 31. An apparatus comprising means for performing the method of any of clauses 25 to 29.

[0170] Clause 32. A. computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry', causes an apparatus to perform the method of any of clauses 25 to 29.

[0171] Clause 33. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 25 to 29.

[0172] Clause 34. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 25 to 29.

[0173] Many modifications and other implementations of the disclosure set forth herein will come to mind to one skilled in the art to which the disclosure pertains having the benefit of the teachings presented in the foregoing description and the associated figures. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Moreover, although the foregoing description and the associated figures describe example implementations in the context of certain example combinations of elements and / or functions, it should be appreciated that different combinations of elements and / or functions may be provided by alternative implementations without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. An apparatus implementing a sensing management function (SeMF) of a communication network, the apparatus comprising:means for receiving a request for a sensing service;means for determining, based on the request, one or more sensing data processing functions (SDPFs) for a sensing session for the sensing service, wherein the one or more SDPFs are distinct from the SeMF;means for sending a respective configuration of one of more configurations for collection and processing of sensing measurement data reported by one or more sensing nodes for the sensing session;means for receiving, from at least one SDPF of the one or more SDPFs, feedback on a quality of at least one of the sensing measurement data or one or more outputs of one or more processing operations performed on the sensing measurement data according to the respective configurations of the at least one SDPF; andmeans for determining whether to perform an adaptation of at least one of the sensing session or the respective configuration of one or more of the at least one SDPF based on the feedback.

2. The apparatus as claimed in claim 1, wherein the means for determining the one or more SDPFs comprises means for determining a plurality of SDPFs that are independent, distinct and distributed to respective sets of one or more sensing nodes, andwherein the means for sending the respective configuration comprises means for sending to each of the plurality of SDPFs a respective configuration, and the means for receiving the feedback comprises means for receiving the feedback from at least one of the plurality of SDPFs.

3. The apparatus as claimed in claim 1 or claim 2, wherein the respective configuration comprises a reporting configuration that includes information regarding the one or more sensing nodes and the sensing measurement data to be reported by the one or more sensing nodes.

4. The apparatus as claimed in any of claims 1 to 3, wherein the respective configuration comprises a processing configuration that includes information regarding the one or more processing operations to be performed on the sensing measurement data.

5. The apparatus as claimed in any of claims 1 to 4, wherein the means for determining whether to perform the adaptation comprises means for determining to perform the adaptation of a sensing configuration of at least one of the one or more SDPFs for the sensing session, and wherein the apparatus further comprises:means for performing an adaptation of the sensing configuration of the at least one of the one or more SDPFs to produce an updated sensing configuration; andmeans for sending, to the at least one of the one or more sensing nodes, the updated sensing configuration.

6. The apparatus as claimed in any of claims 1 to 5, wherein the means for determining whether to perform the adaptation comprises means for determining to perform the adaptation of the respective configuration of at least one of the one or more SDPFs, and wherein the apparatus further comprises:means for performing an adaptation of the respective configuration of the at least one of the one or more SDPFs to produce an updated configuration; andmeans for sending, to the at least one of the one or more SDPFs, the updated configuration.

7. The apparatus as claimed in any of claims 1 to 6, wherein the request comprises a request for a split sensing session to perform the sensing service, wherein the request is received from a central SeMF, and wherein the SeMF is a local SeMF of one or more local SeMFs that are distributed from one another and the central SeMF in the telecommunications system.

8. The apparatus as claimed in claim 7, wherein the apparatus further comprises: means for receiving, from the one or more SDPFs, one or more sensing reports that include the one or more outputs of the one or more processing operations; andmeans for sending the one or more sensing reports to the central SeMF.

9. The apparatus as claimed in claim 7 or claim 8, wherein the request comprises a quality of service (QoS) threshold, and wherein the feedback further includes a sensing QoS, andwherein the apparatus further comprises means for notifying the central SeMF that the sensing QoS is below the QoS threshold in an instance the sensing QoS is below the QoS threshold.

10. The apparatus as claimed in any of claims 1 to 9, wherein the means for receiving the request comprises means for receiving the request from a sensing client or a central SeMF, wherein the apparatus further comprises means for registering, with a network repository function, a registration of the SeMF, and wherein the registration comprises information that indicates one or more modes of operation for one or more sensing services of the SeMF for discovery by the sensing client or the central SeMF.

11. An apparatus implementing a central sensing management function (SeMF), the apparatus comprising:means for receiving a request for a sensing service;means for determining, based on the request, a split of a sensing session among local SeMFs to perform the sensing service, wherein the local SeMFs are distributed from one another and the central SeMF, wherein the split indicates a configuration for the local SeMFs in association with respective sets of one or more sensing data processing functions (SDPFs) for collection and processing of sensing measurement data reported by one or more sensing nodes associated with a respective local SeMF, wherein the respective sets of one or more SDPFs are distinct from one another, the central SeMF and the local SeMFs; andmeans for sending, to the local SeMFs, requests for a split sensing session for implementing the split of the sensing session.

12. The apparatus as claimed in claim 11, wherein the means for receiving the request comprises means for receiving the request from a sensing client, and wherein the apparatus further comprises:means for receiving, from the local SeMFs, sensing reports comprising one or more outputs of one or more sensing processing operations performed by the respective sets of one or more SDPFs;means for merging the sensing reports from the local SeMFs to produce a merged sensing report; andmeans for sending, to the sensing client, the merged sensing report.

13. The apparatus as claimed in claim 11 or claim 12, wherein the requests for the split sensing session comprise a quality of service (QoS) threshold, and wherein the apparatus further comprises means for receiving, from one or more of the local SeMFs, a notification that a sensing QoS at the one or more SeMFs is below the QoS threshold in an instance the sensing QoS is below the QoS threshold.

14. The apparatus as claimed in any of claims 11 to 13, wherein the means for receiving the request comprises means for receiving the request from a sensing client, wherein the apparatus further comprises means for registering, with a network repository function, a registration of the central SeMF, and wherein the registration comprises information that indicates one or more modes of operation for one or more sensing services of the central SeMF for discovery by the sensing client.

15. An apparatus implementing a sensing data processing function (SDPF), the apparatus comprising:means for receiving, from a sensing management function (SeMF), a configuration of the SDPF for collection and processing of sensing measurement data from one or more sensing nodes for a sensing session, wherein the SDPF is independent, distinct and distributed from the SeMF;means for collecting, according to the configuration, the sensing measurement data;means for performing, according to the configuration, one or more processing operations on the sensing measurement data to produce one or more outputs;means for sending, to the SeMF, feedback on a quality of at least one of the following: the sensing measurement data; or the one or more outputs of the one more processing operations; andmeans for sending, to the SeMF or a sensing client, one or more sensing reports that include the one or more outputs of the one or more processing operations.

16. The apparatus as claimed in claim 15, wherein the configuration comprises a reporting configuration that includes information regarding the one or more sensing nodes and the sensing measurement data to be reported by the one or more sensing nodes.

17. The apparatus as claimed in claim 15 or claim 16, wherein the configuration comprises a processing configuration that includes information regarding the one or more processing operations to be performed on the sensing measurement data.

18. The apparatus as claimed in any of claims 15 to 17, wherein the apparatus further comprises means for receiving, from the SeMF, based on the feedback sent to the SeMF, an updated configuration of the SDPF, andwherein at least one of: the sensing measurement data to be collected; or the one or more processing operations to be performed on the sensing measurement data is based on the updated configuration.

19. The apparatus as claimed in any of claims 15 to 18, wherein the apparatus further comprises means for registering, with a network repository function, a registration of the SDPF, and wherein the registration comprises information that indicates one or more modes of operation for one or more sensing services of the SDPF for discovery by the SeMF.

Images